Pusch transmission method and apparatus, pusch reception method and apparatus, and communication system

Abstract

Embodiments of the present application provide a PUSCH transmission method and apparatus, a PUSCH reception method and apparatus, and a communication system. The PUSCH transmission method comprises: a terminal device receiving information for configuring a first frequency domain resource and / or information for configuring a second frequency domain resource; and transmitting, on an uplink BWP, a PUSCH scheduled or activated by a random access response (RAR) or downlink control information (DCI), wherein the PUSCH is repeated, and a plurality of slots for the PUSCH are determined at least on the basis of a first uplink-downlink configuration and an SSB configuration.

Description

PUSCH transmission and reception methods, apparatus, and communication systems Technical Field

[0001] This application relates to the field of communication technology. Background Technology

[0002] In traditional technologies, for Time Division Duplex (TDD) frequency bands, uplink transmission can only occur during uplink time periods. When limited or few uplink time periods are allocated, there will be problems such as small uplink coverage, small capacity, and large latency.

[0003] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention

[0004] To improve uplink capacity and coverage, and reduce uplink latency, network devices in the TDD band can operate in full-duplex mode at certain times. For example, at these times, the network device can simultaneously receive and transmit on different frequency domain resources within the corresponding carrier of the TDD band. This operating mode is called, for example, Subband non-overlapping Full Duplex (SBFD), but is not limited to this.

[0005] On the other hand, the Physical Uplink Shared Channel (PUSCH) can be scheduled by Downlink Control Information (DCI) or Random Access Response (RAR) Uplink Grant (UL grant). However, even if the above operating modes are supported, there is still no solution for how the UE transmits the PUSCH.

[0006] To address at least one of the above-mentioned problems, embodiments of this application provide a PUSCH transmission and reception method, apparatus, and communication system.

[0007] According to one aspect of the embodiments of this application, a PUSCH transmission method is provided, including:

[0008] The terminal device receives information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0009] The (activated) uplink BWP sends a PUSCH scheduled or activated by a random access response (RAR) in (CBRA or CFRA or in response to PRACH in CBRA or CFRA) or by (CRC scrambled by TC-RNTI or C-RNTI or MCS-RNTI or CS-RNTI).

[0010] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

[0011] According to another aspect of the embodiments of this application, a PUSCH transmitting apparatus is provided, comprising:

[0012] A receiver that receives information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0013] The transmitter, in the (activated) uplink BWP, sends a PUSCH scheduled or activated by a random access response (RAR) in (CBRA or CFRA, or in response to a PRACH in CBRA or CFRA) or by (CRC scrambled by TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI) downlink control information (DCI).

[0014] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

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

[0016] The network device sends information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0017] The (active) uplink BWP receives a PUSCH scheduled or activated by a random access response (RAR) in (CBRA or CFRA or in response to PRACH in CBRA or CFRA) or by (CRC scrambled by TC-RNTI or C-RNTI or MCS-RNTI or CS-RNTI).

[0018] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

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

[0020] A transmitter that transmits information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0021] The receiver, in the (activated) uplink BWP, receives a PUSCH scheduled or activated by a random access response (RAR) in (CBRA or CFRA) (or in response to a PRACH in CBRA or CFRA) or by (CRC scrambled by TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI).

[0022] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

[0023] According to another aspect of the embodiments of this application, a communication system is provided, including:

[0024] Network devices that transmit information for configuring (for one or more SCSs) a first frequency domain resource (UL subband) and / or for configuring (for one or more SCSs) a second frequency domain resource (DL subband); and receive, on the (activated) uplink BWP, a PUSCH scheduled or activated by a random access response (RAR) in a CBRA or CFRA (or in response to a PRACH in a CBRA or CFRA) or by downlink control information (DCI) scrambled by TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI.

[0025] The terminal device receives information for configuring the first frequency domain resource (UL subband) and / or information for configuring the second frequency domain resource (DL subband); and transmits a PUSCH scheduled or activated by the Random Access Response (RAR) or the Downlink Control Information (DCI) in the (activated) uplink BWP.

[0026] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

[0027] One of the beneficial effects of the embodiments of this application includes: the network device can work in full-duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to send and receive signals when the network device is working in full-duplex mode, which can improve the uplink transmission capacity and coverage, reduce the uplink transmission latency, and improve the flexibility of resource allocation and resource utilization.

[0028] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

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

[0030] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0031] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0032] The accompanying drawings, which form part of the specification, are used to provide a further understanding of the embodiments of this application and illustrate the implementation methods of this application, together with the textual description, to explain the principles of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without creative effort. In the drawings:

[0033] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0034] Figure 2 is a schematic diagram of a PUSCH transmission method according to an embodiment of this application;

[0035] Figure 3 is an example diagram of time-domain resources according to an embodiment of this application;

[0036] Figure 4 is an example diagram of uplink available PRB according to an embodiment of this application;

[0037] Figure 5 is an example diagram of downlink available PRB according to an embodiment of this application;

[0038] Figure 6 is a schematic diagram of a PUSCH receiving method according to an embodiment of this application;

[0039] Figure 7 is a schematic diagram of a PUSCH transmitting device according to an embodiment of this application;

[0040] Figure 8 is a schematic diagram of a PUSCH receiving device according to an embodiment of this application;

[0041] Figure 9 is a schematic diagram of a network device according to an embodiment of this application;

[0042] Figure 10 is a schematic diagram of a terminal device according to an embodiment of this application. Detailed Implementation

[0043] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0044] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0045] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly interpreted as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," the term "based on" should be understood as "at least partially based on…," and the term "related to…" should be understood as "at least partially related to…," unless the context explicitly indicates otherwise. In some embodiments, "according to," "based on," and "related to…" can be used interchangeably, but this application is not limited thereto.

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

[0047] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), 6G, etc., and / or other currently known or future communication protocols.

[0048] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transceiver node (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0049] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" can include some or all of their functions, and each base station can provide communication coverage to 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.

[0050] In the embodiments of this application, the term "User Equipment" (UE) refers to a device that accesses a communication network and receives network services through a network device, and can also be called "Terminal Equipment" (TE). Terminal equipment can be fixed or mobile, and can also be called a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, mobile terminal (MT), etc.

[0051] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0052] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0053] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0054] In the following description, without causing confusion, the terms “uplink control signal” and “uplink control information (UCI)” or “physical uplink control channel (PUCCH)” are used interchangeably, as are the terms “uplink data signal” and “uplink data information” or “physical uplink shared channel (PUSCH)”.

[0055] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, as are the terms “downlink data signal” and “downlink data information (PDSCH)” or “physical downlink shared channel (PDSCH)”.

[0056] Additionally, uplink signals can include uplink data signals and / or uplink control signals and / or PRACH and / or SRS, etc., and can also be referred to as uplink transmission (UL transmission), uplink information, or uplink channel. Sending / receiving uplink transmission on uplink resources can be understood as using that uplink resource to send / receive the uplink transmission. Downlink signals can include downlink data signals and / or downlink control signals and / or synchronization signals (SS, such as PSS / SSS) and / or broadcast channel (PBCH) and / or SSB (SS / PBCH block, including PSS, SSS, and PBCH and their DMRS) and / or CSI-RS, etc., and can also be referred to as downlink transmission (DL transmission), downlink information, or downlink channel. Sending / receiving downlink transmission on downlink resources can be understood as using that downlink resource to send / receive the downlink transmission.

[0057] In the embodiments of this application, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling; RRC signaling may include, for example, RRC messages, such as broadcast / public RRC messages / signaling (e.g., Master Information Block (MIB), system information), dedicated RRC messages / signaling; or RRC information elements (RRC IE); or information fields (or information fields included in information fields) included in RRC messages or RRC information elements. Higher-layer signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as MAC control elements (MAC CE). However, this application is not limited to these. The names of signaling (e.g., RRC message, information element IE, information field, higher-layer parameters, etc.) used in the embodiments of this application are only examples and may be other names, and the embodiments of this application are not intended to limit them.

[0058] In the embodiments of this application, "multiple" refers to at least two, or two or more.

[0059] In this application embodiment, "predefined" refers to what is specified by the protocol or determined according to the rules specified by the protocol, and does not require additional configuration. "Configuration / instruction" refers to what the network device directly or indirectly configures / instructs through higher-layer signaling and / or physical layer signaling. Configuration / instruction can be achieved by introducing higher-layer parameters into the higher-layer signaling. Higher-layer parameters refer to information fields and / or information elements / information units / information cells (IEs) in the higher-layer signaling. Physical layer signaling refers to, for example, control information (DCI) carried by the physical downlink control channel or control information carried by the sequence, but is not limited to these.

[0060] For ease of description, the following description uses a base station as an example of an access network device. In the following descriptions, "if…", "in the case of…", and "when…" are used interchangeably unless there is confusion. For resources in the frequency domain, "carrier" and "resource grid" are interchangeable; "subcarrier spacing configuration (μ)" and "subcarrier spacing (SCS) (Δf)" are interchangeable; "subcarrier spacing" and "numerology" are interchangeable; "resource block," "RB," and "PRB," "physical resource block," and "common resource block (CRB)" are interchangeable; "configuration / indication / providance / given" are interchangeable; "index" and "identifier (ID)" are interchangeable.

[0061] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0062] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

[0063] In this embodiment of the application, network device 101 and terminal devices 102 and 103 can transmit existing services or services that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0064] Terminal device 102 can send data to network device 101, for example, using authorized or unauthorized transmission methods. Network device 101 can receive data sent by one or more terminal devices 102 and provide feedback to terminal devices 102, such as ACK / NACK confirmation information. Based on the feedback information, terminal device 102 can confirm the end of the transmission process, or can initiate new data transmission, or can retransmit the data.

[0065] Network device 101 can send data to terminal device 102 and / or terminal device 103 using unicast, multicast, or broadcast. Terminal device 102 can receive data sent by one or more network devices (e.g., dual-connection or multi-connection) via a downlink or by terminal device 103 via a sidelink.

[0066] It is worth noting that Figure 1 shows that both terminal devices 102 and 103 are within the coverage area of ​​network device 101, but this application is not limited to this. Both terminal devices 102 and 103 may be outside the coverage area of ​​network device 101, or one terminal device 102 may be within the coverage area of ​​network device 101 while the other terminal device 103 may be outside the coverage area of ​​network device 101.

[0067] In the following explanation, 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.

[0068] Furthermore, the content within parentheses is explanatory, exemplary, or optional. For example, in some embodiments, the expressions or limitations within parentheses may be included, while in other embodiments, they may be omitted. " / " indicates "and / or," and this application is not limited thereto. Various embodiments of this application will be described below with reference to the accompanying drawings. These embodiments are merely exemplary and not intended to limit the scope of this application.

[0069] First aspect of the embodiments

[0070] This application provides a PUSCH transmission method, which is described from the perspective of the terminal device.

[0071] Figure 2 is a schematic diagram of a PUSCH transmission method according to an embodiment of this application. As shown in Figure 2, the method includes:

[0072] 201. The terminal device receives information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs);

[0073] 202, the terminal device transmits a PUSCH scheduled or activated by (CBRA or CFRA in response to PRACH in CBRA or CFRA) RAR or (CRC scrambled by TC-RNTI or C-RNTI or MCS-RNTI or CS-RNTI) DCI in the (activated) uplink BWP.

[0074] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

[0075] In some embodiments, the third frequency domain resources (UL usable PRBs) of the uplink BWP include / are determined to be the intersection of the first frequency domain resources and the uplink BWP (configured for the SCS of the uplink BWP).

[0076] It is worth noting that Figure 2 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 2 above.

[0077] In some embodiments, the uplink BWP is an initial UL BWP or other UL BWP (e.g., referred to as a non-initial UL BWP). For information on first frequency domain resources, third frequency domain resources, etc., please refer to the following embodiments.

[0078] In some embodiments, the terminal device may be an SBFD-aware device; however, this application is not limited thereto. For example, in the initial access procedure (from RRC_IDLE to RRC_Connected state, including CBRA) and / or in the random access procedure (e.g., CBRA) and / or in the RRCSetupComplete message and / or in the capability information (e.g., UECapabilityInformation), the terminal device indicates to the network device that the terminal device is an SBFD-aware device (SBFD-aware UE) and / or whether the terminal device supports Msg3 repeating.

[0079] For example, during random access, the terminal device is indicated to be an SBFD-aware device via the RO and / or Msg3 used to send the preamble / PRACH. For instance, some ROs (first ROs, different from the second ROs described below) are not limited to use by SBFD-aware UEs (other UEs may also use them), while some ROs (second ROs, e.g., referred to as additional ROs, but not limited to them) are limited to use by SBFD-aware devices. Therefore, when a UE uses a second RO to send the preamble / PRACH, the base station knows that the UE is an SBFD-aware device (and consequently, the subsequent Msg3 and / or RRCSetupComplete message and / or capability information may include / not include information indicating that the UE is an SBFD-aware device). For example, (when a UE uses a first RO to send the preamble / PRACH,) the Msg3 and / or RRCSetupComplete message and / or capability information include information indicating that the UE is an SBFD-aware device.

[0080] For example, an SBFD-aware UE has capabilities related to SBFD operation (e.g., basic features / capabilities of an SBFD-aware UE) including one or more of the following: being able to know the SBFD configuration, such as the configuration of the first time domain resources and / or the second time domain resources and / or the first frequency domain resources and / or the second frequency domain resources (i.e., the cell common configuration supporting the time-frequency location of the SBFD subband); being able to transmit and receive signals according to the SBFD configuration (e.g., supporting uplink transmission in (one) uplink subband and downlink reception in (one or two) downlink subbands); and being able to transmit uplink signals on (DL)SBFD symbols.

[0081] In some embodiments, Msg3 repetition refers to the repetition of a PUSCH scheduled by a RAR UL grant or a DCI (e.g., DCI format 0_0) with a CRC scrambled by TC-RNTI, which includes a first type of Msg3 repetition and / or a second type of Msg3 repetition. Specifically, for the first type of Msg3 repetition, the UE does not determine the time slot where the PUSCH repetition occurs based on the first time domain resources and / or the second time domain resources; for the second type of Msg3 repetition, the UE determines the time slot where the PUSCH repetition occurs based on the first time domain resources and / or the second time domain resources.

[0082] For example, for Msg3 repetition, the UE needs to determine multiple time slots for PUSCHs scheduled by a RAR UL grant or with a DCI (e.g., DCI format 0_0) scrambled by TC-RNTI, each of which corresponds to one or more PUSCH repetitions. For the first type of Msg3 repetition, the UE determines these multiple time slots only based on the first uplink / downlink configuration and SSB configuration (ssb-PositionsInBurst), without based on SBFD symbols and / or non-SBFD symbols. For the second type of Msg3 repetition, the UE determines these multiple time slots based on the first uplink / downlink configuration and SSB configuration, as well as SBFD symbols and / or non-SBFD symbols.

[0083] In some embodiments, for a PUSCH scheduled by a RAR UL grant or a DCI (e.g., DCI format 0_0) with a CRC scrambled by TC-RNTI, if the UE requests a repetition for the PUSCH (i.e., requests a Msg3 repetition), the UE transmits the PUSCH in multiple time slots. The number of repetitions of the PUSCH / the number of the multiple time slots is indicated by the two most significant bits (MSBs) of the MCS field in the RAR UL grant or the DCI with a CRC scrambled by TC-RNTI from a value provided by a parameter for configuring the set of repetitions for the PUSCH or from {1,2,3,4} (if the above parameters are not provided). Specifically, if the UE uses the first RO to indicate / trigger / request the repetition of the PUSCH, the multiple time slots (i.e., the time slots where the corresponding PUSCH repetition is located) are determined according to the first type Msg3 repetition method. If the UE uses the second RO to indicate / trigger / request the repetition of the PUSCH, the multiple time slots (i.e., the time slots where the corresponding PUSCH repetition is located) are determined according to the second type Msg3 repetition method.

[0084] In some embodiments, the first type of Msg3 repeat is referred to as (in the non-SBFD symbol) Msg3 repeat or Msg3 repeat for non-SBFD, and the second type of Msg3 repeat is referred to as Msg3 repeat in the SBFD symbol or Msg3 repeat based on the first configuration (configuration 1) or Msg3 repeat based on the SBFD / non-SBFD symbol or Msg3 repeat for SBFD.

[0085] In some embodiments, a UE supporting Type II Msg3 repetition requires at least one of the following (a UE supporting Type II Msg3 repetition should also support at least one of the following): the UE is an SBFD-aware UE, supports the basic features / capabilities of an SBFD-aware UE, supports Type I Msg3 repetition, supports SBFD random access (in RRC_IDLE / INACTIVE / CONNECTED mode), and supports preamble / PRACH repetition in the second ROs. For example, if the UE supports Type II Msg3 repetition, the UE should support the basic features / capabilities of an SBFD-aware UE and SBFD random access. For example, if the UE supports Type II Msg3 repetition, the UE should support the basic features / capabilities of an SBFD-aware UE, SBFD random access, and Type I Msg3 repetition.

[0086] For example, the basic features / capabilities supporting SBFD-aware UEs include at least one of the following: support for cell common configuration of time-frequency location of SBFD subbands; support for uplink transmission in (one) uplink subband and downlink reception in (one or two) downlink subbands; support for link direction determination based on configuration or scheduling of transmissions or receptions and collision handling; support for uplink transmission or downlink reception across SBFD symbols and non-SBFD symbols in different time slots (wherein, these uplink transmissions or downlink receptions are restricted to SBFD symbols or non-SBFD symbols); support for separate CSI reporting for SBFD and non-SBFD symbols; support for independent PUCCH frequency domain resource configuration in SBFD symbols and non-SBFD symbols; support for independent UL power control parameters in SBFD symbols and non-SBFD symbols based on a unified TCI framework; and support for independent SRS resource set configuration in SBFD symbols and non-SBFD symbols.

[0087] For example, supporting SBFD random access includes supporting SBFD random access based on a single RACH configuration and / or supporting SBFD random access based on two separate RACH configurations. In SBFD random access, the UE can use a second RO to transmit PRACH. For SBFD random access based on a single RACH configuration, the UE determines the first RO and the second RO according to that single RACH configuration. For SBFD random access based on two separate RACH configurations, the UE determines the first RO according to one RACH configuration and the second RO according to the other RACH configuration.

[0088] For example, supporting preamble / PRACH repetition in the second ROs includes supporting preamble / PRACH repetition in the second ROs determined according to the single RACH configuration described above (UEs supporting this capability should also support SBFD random access based on a single RACH configuration) and / or supporting preamble / PRACH repetition in the second ROs determined according to one of the two independent RACH configurations described above (UEs supporting this capability should also support SBFD random access based on two independent RACH configurations).

[0089] In some embodiments, in the UE capability information (e.g., UECapabilityInformation), the UE may indicate whether it supports Type II Msg3 repetition through one or more of the following combinations, and / or, at least one of the following may also be used to indicate whether the UE supports Type II Msg3 repetition; or, the UE may indicate / report whether it supports Type II Msg3 repetition through a first parameter or information field different from one or more of the following:

[0090] ● Used to indicate whether the UE supports the (second) parameter / information field for repeating the first type of Msg3 (e.g., pusch-RepetitionMsg3-r17);

[0091] ● A (third) parameter / information field used to indicate whether the UE is an SBFD-aware UE and / or whether it supports the basic characteristics / capabilities of SBFD-aware UE;

[0092] ● The fourth parameter / information field used to indicate whether the UE supports SBFD random access (in RRC_IDLE / INACTIVE / CONNECTED mode);

[0093] ● The fifth parameter / information field used to indicate support for preamble / PRACH repetition in the second ROs.

[0094] The following combinations indicate whether the UE supports Type 2 Msg3 repeat: For example, when the UE indicates via a third parameter that it is an SBFD-aware UE and supports the basic characteristics / capabilities of an SBFD-aware UE and / or via a fourth parameter that it supports SBFD random access, the second parameter indicates whether the UE supports both Type 1 and Type 2 Msg3 repeat. As another example, when the UE indicates via a third parameter that it is an SBFD-aware UE and supports the basic characteristics / capabilities of an SBFD-aware UE and / or via a second parameter that it supports Type 1 Msg3 repeat, the fourth parameter indicates that the UE supports both SBFD random access and Type 2 Msg3 repeat. As yet another example, when the UE indicates via a third parameter that it is an SBFD-aware UE and supports the basic characteristics / capabilities of an SBFD-aware UE and / or via a second parameter that it supports Type 1 Msg3 repeat and / or via a fourth parameter that it supports SBFD random access, it means that the UE supports Type 2 Msg3 repeat.

[0095] Indicate / report whether the UE supports Type 2 Msg3 repeat by using the first parameter or information field: For example, if the UE indicates support for Type 2 Msg3 repeat by using the first parameter, it should also indicate support for Type 1 Msg3 repeat by using the corresponding parameter and / or the UE should support the basic features / capabilities of SBFD-aware UEs and / or SBFD random access.

[0096] In some embodiments, it is assumed that the first RO and the second RO each include ROs for requesting Msg3 repetition, and the UE switches the RO type during a random access procedure, for example, switching from the first RO to the second RO or vice versa: For a UE that supports both type I and type II Msg3 repetition, if an RO for requesting Msg3 repetition was selected before / initially, an RO for requesting Msg3 repetition should also be selected after the switch; if an RO not for requesting Msg3 repetition was selected before the switch, an RO not for requesting Msg3 repetition should also be selected after the switch. For a UE that supports type I Msg3 repetition but not type II Msg3 repetition, or supports type II Msg3 repetition but not type I Msg3 repetition, if an RO for requesting Msg3 repetition was selected before the switch, an RO not for requesting Msg3 repetition can be selected after the switch; if an RO not for requesting Msg3 repetition was selected before the switch, an RO not for requesting Msg3 repetition should also be selected after the switch.

[0097] The following is an illustrative description of the time-domain resources involved in the embodiments of this application.

[0098] In some embodiments, for a cell or carrier, in the first time domain resources, different frequency domain resources are respectively (only) used for (network device receiving) uplink (e.g., corresponding to the first frequency domain resources described below) and (only) used for (network device transmitting) downlink (e.g., corresponding to the second frequency domain resources described below). For example, the network device can simultaneously receive (uplink signals) in the frequency domain resources (only) used for uplink and transmit (downlink signals) in the frequency domain resources (only) used for downlink. The second time domain resources are outside the first time domain resources. For example, in the second time domain resources, different frequency domain resources are all used for uplink or all used for downlink. That is, the frequency domain resources are not divided into frequency domain resources (only) used for uplink and (only) used for downlink, and the network device does not receive and transmit at the same time.

[0099] In some embodiments, the first time-domain resource includes, for example, SBFD time slots and / or SBFD symbols (or first symbols, or other names), and the second time-domain resource includes, for example, non-SBFD time slots and / or non-SBFD symbols (or second symbols, or other names). Here, SBFD time slots refer to time slots where all symbols are SBFD symbols, and non-SBFD time slots refer to time slots where all symbols are non-SBFD symbols. For ease of description, SBFD symbols and non-SBFD symbols will be used in the following description.

[0100] In some embodiments, information for configuring SBFD symbols and / or non-SBFD symbols is provided by higher-layer signaling. For example, higher-layer parameters for configuring SBFD symbols may optionally exist in SIB1 and / or the SIB ServingCellConfigCommonSIB IE and / or the ServingCellConfigCommon IE (within the ServingTDD-UL-DL-ConfigCommon IE, which contains the TDD-UL-DL-Pattern IE), and / or, higher-layer parameters for configuring SBFD symbols may optionally exist in the ServingCellConfig.

[0101] In some embodiments, a cell / carrier can be configured with one or more (e.g., two) TDD uplink / downlink patterns. When multiple patterns are configured, different patterns may or may not have corresponding SBFD symbols, and different patterns are independently configured with corresponding SBFD symbols.

[0102] For example, for each pattern with SBFD symbols, the configured SBFD symbols are continuous within the corresponding period of the pattern. The high-level parameters for configuring SBFD symbols mentioned above include, for example, one or more parameters for configuring SBFD symbols in that period, such as: start slot index, start symbol index (in the start slot), end slot index, and end symbol index (in the end slot).

[0103] For example, the start and end slots are the first and last slots containing SBFD symbols, respectively. The start and end symbols are the first and last SBFD symbols in the start slot and the last SBFD symbol in the end slot, respectively. All symbols from the start symbol of the start slot to the end symbol of the end slot are SBFD symbols. The slot index is the number of the slots included in the period, which increments by 1, for example, starting from 0 or 1. For example, when the start slot index is 0, the start slot is the first slot in the period; when the start slot index is 1, the start slot is the second slot in the period, and so on. Similarly, the symbol index is the number of the symbols within a slot. The aforementioned slots / symbols use the SCS configured in the reference subcarrier spacing field of the Common TDD Uplink / Downlink Configuration (TDD-UL-DL-Config Common) IE.

[0104] For example, each / different pattern is configured with a period independently, for example, by the corresponding ((TDD-UL-DL-Pattern)IE)dl-UL-TransmissionPeriodicity. When only one pattern is configured, the period of the SBFD symbol is the same as the period corresponding to that pattern; when multiple patterns (e.g., two) are configured, the period of the SBFD symbol is the same as the sum of the periods corresponding to all patterns.

[0105] In some embodiments, a downlink symbol is, for example, a symbol indicated as downlink by the first uplink / downlink configuration, an uplink symbol is, for example, a symbol indicated as uplink by the first uplink / downlink configuration, and a flexible symbol is, for example, a symbol that is neither indicated as downlink nor as uplink by the first uplink / downlink configuration, or a symbol indicated as flexible by the configuration. The first uplink / downlink configuration is used to provide cell-specific uplink / downlink configurations, such as tdd-UL-DL-ConfigurationCommon, or the common TDD uplink / downlink configuration (TDD-UL-DL-ConfigCommon)IE or (TDD-UL-DL-Pattern)IE, but is not limited thereto.

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

[0107] In some embodiments, SBFD symbols include DL SBFD symbols and / or Flexible SBFD symbols, and non-SBFD symbols include Full-DL symbols and / or Full-Flexible symbols and / or Full-UL symbols (or UL symbols). Other representations may also be used for these symbols, and are not limited thereto.

[0108] Figure 3 is an example diagram of the time-domain resources of an embodiment of this application. As shown in Figure 3, a period may include multiple different symbols. Among them, the SBFD symbol is within the range of downlink symbols and flexible symbols. The SBFD symbol that overlaps with the DL symbol is represented as a DL SBFD symbol, the SBFD symbol that overlaps with the flexible symbol is represented as a Flexible SBFD symbol, the downlink symbol that does not overlap with the SBFD symbol is represented as a Full-DL symbol, the flexible symbol that does not overlap with the SBFD symbol is represented as a Full-Flexible symbol, and the UL symbol that does not overlap with the SBFD symbol is represented as a Full-UL symbol (assuming that the UL symbol cannot be used as an SBFD symbol, the Full-UL symbol is equivalent to the UL symbol). Figure 3 illustrates the time-domain resources of an embodiment of this application, but is not limited thereto.

[0109] The frequency domain resources involved in the embodiments of this application will be illustrated below.

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

[0111] For example, the first frequency domain resource includes the uplink subband (UL subband), and the second frequency domain resource includes the downlink subband (DL subband). Other names may also be used, and this is not a limitation. For convenience, the following descriptions will use UL subband and DL subband.

[0112] In some embodiments, the UE receives information for configuring the UL subband and DL subband. For example, the uplink subband and downlink subband each include an integer number of PRBs, and the information for configuring the UL subband and DL subband includes information indicating the corresponding starting PRB and bandwidth / size (including the number of PRBs).

[0113] In some embodiments, information for configuring the UL subband and DL subband is provided by higher-level signaling.

[0114] For example, the higher-layer parameters used to configure the DL subband may optionally exist in SIB1 (the SIB Public Service Cell Configuration (ServingCellConfigCommonSIB) IE (the SIB Common Downlink Configuration (DownlinkConfig Common SIB) IE (the SIB Downlink Frequency Domain Information (FrequencyInfoDL-SIB) IE (the SCS Specific Carrier (SCS-SpecificCarrier) IE))). For instance, the inclusion relationship of these parameters can be expressed as: SIB1 > ServingCellConfigCommonSIB > DownlinkConfigCommonSIB > FrequencyInfoDL-SIB > SCS-SpecificCarrier; and / or,

[0115] The higher-layer parameters used to configure the DL subband may optionally exist in the ServingCellConfigCommon IE (which contains the DownlinkConfigCommon IE, which contains the DownlinkFrequencyInfoDL IE, which contains the SCS-SpecificCarrier IE)). For example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > DownlinkConfigCommon > FrequencyInfoDL > SCS-SpecificCarrier, and / or, optionally, in the ServingCellConfig. That is, the higher-layer parameters used to configure the DL subband may optionally exist in one or more of the above parameters.

[0116] For example, the higher-layer parameters used to configure the UL subband may optionally exist in SIB1 (the SIB ServingCellConfigCommonSIB IE, the SIB UplinkConfigCommonSIB IE, the SIB UplinkFrequencyInfoUL-SIB IE, and the SCS-SpecificCarrier IE). For instance, the inclusion relationship of these parameters can be expressed as: SIB1 > ServingCellConfigCommonSIB > UplinkConfigCommonSIB > FrequencyInfoUL-SIB > SCS-SpecificCarrier, and / or...

[0117] The higher-layer parameters used to configure the UL subband may optionally exist in the ServingCellConfigCommon IE (which contains the CommonUplinkConfigCommon IE, which contains the UplinkFrequencyInfoUL IE, which contains the SCS-SpecificCarrier IE)). For example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > UplinkConfigCommon > FrequencyInfoUL > SCS-SpecificCarrier, and / or, optionally, in the ServingCellConfig. That is, the higher-layer parameters used to configure the UL subband may optionally exist in one or more of the above parameters.

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

[0119] For example, resource indicator values ​​can be defined as shown in Table 1 below.

[0120] Table 1

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

[0122] In some embodiments, within a cell, the scs-SpecificCarrierList of UL and DL may each include one or more SCS-SpecificCarrier IEs, and each SCS-SpecificCarrier IE corresponds to / includes one SCS configuration (subcarrierSpacing). That is, the scs-SpecificCarrierList of UL and DL may each include one or more SCS configurations.

[0123] For example, each SCS configuration in the UL scs-SpecificCarrierList is configured with a UL subband, or each corresponds to a UL subband, for example, each corresponds to an independent high-level parameter mentioned above for configuring the UL subband. Each SCS configuration in the DL scs-SpecificCarrierList is configured with one or more (e.g., two) DL subbands, or each corresponds to one or more DL subbands, for example, each corresponds to an independent high-level parameter mentioned above for configuring the DL subband. If an SCS configuration is configured with multiple DL subbands, the corresponding high-level parameter for configuring the DL subband includes multiple RIVs mentioned above.

[0124] In some embodiments, a first time-domain resource, a first frequency-domain resource, and / or a third frequency-domain resource (UL usable PRBs for the active UL BWP) are used for uplink, and a second frequency-domain resource and / or a fourth frequency-domain resource (DL usable PRBs for the active DL BWP) are used for downlink, wherein the second time-domain resource is outside the first time-domain resource. For convenience, UL usable PRBs and DL usable PRBs will be used in the following description.

[0125] In some embodiments, for a UL BWP, its UL usable PRBs include / are determined as (in the SBFD symbol / corresponding to the SBFD symbol,) the intersection of the UL subband (PRBs) and the uplink BWP (PRBs) (i.e., PRBs that are both in the UL subband and in the uplink BWP) (configured for the SCS of the uplink BWP, or, corresponding to the SCS of the UL BWP), or the PRBs in the intersection are referred to as UL usable PRBs.

[0126] For example, for a UL BWP, the intersection is determined based on the uplink subband corresponding to the SCS of that UL BWP. For instance, if the SCS of a UL BWP is 15kHz, then its corresponding UL available PRB is the intersection of that UL BWP and the corresponding uplink subband with SCS = 15kHz. If the SCS of a UL BWP is 30kHz, then its corresponding UL available PRB is the intersection of that UL BWP and the corresponding uplink subband with SCS = 15kHz.

[0127] Figure 4 is an example diagram of uplink usable PRBs according to an embodiment of this application. As shown in Figure 4, the UL BWP and UL subband overlap, and the UL usable PRBs are the intersection between them. The UL subband, for example, represents the uplink subband corresponding to the SCS of the UL BWP, but this application is not limited to this.

[0128] In some embodiments, for a DL BWP, its DL usable PRBs include / are determined as (in SBFD symbols / corresponding to SBFD symbols,) the intersection of (PRBs in the DL subband) and (PRBs in the downlink BWP) with (the SCS configured for the downlink BWP, or, corresponding to the SCS of the DL BWP), or, the PRBs in the intersection are referred to as DL usable PRBs.

[0129] For example, if a DL BWP has an SCS of 15kHz, then its corresponding DL can be represented by a PRB as the intersection of the DL BWP and the corresponding downlink subband with an SCS of 15kHz. If a DL BWP has an SCS of 30kHz, then its corresponding DL can be represented by a PRB as the intersection of the DL BWP and the corresponding uplink subband with an SCS of 15kHz.

[0130] Figure 5 is an example diagram of downlink usable PRBs according to an embodiment of this application. As shown in Figure 5, DL BWP and DL subband overlap, and DL usable PRBs are the intersection of the two. The DL subband, for example, represents the downlink subband corresponding to the SCS of the DL BWP, but this application is not limited thereto.

[0131] The above provides an illustrative description of time and frequency resources. The following provides an illustrative description of embodiments of this application.

[0132] In this embodiment of the application, PUSCH is sent in the (activated) uplink BWP.

[0133] For ease of description, the UL BWP where the PUSCH is located, is scheduled, or is sent will be referred to as the active UL BWP. An active UL BWP may be an initial UL BWP or a non-initial UL BWP.

[0134] In this application embodiment, the relationship between the activated UL BWP and the initial UL BWP is considered, including the following cases:

[0135] Case A: The activated UL BWP is the initial UL BWP.

[0136] Case B: The activated UL BWP is not the initial UL BWP, or the activated UL BWP is a non-initial UL BWP.

[0137] Case B-1: The activated UL BWP (the non-initial UL BWP mentioned above) and the initial UL BWP have the same SCS and the same CP length, and the activated UL BWP includes all RBs of the initial UL BWP;

[0138] Case B-2: The relationship between the activated UL BWP (the non-initial UL BWP mentioned above) and the initial UL BWP does not satisfy Case B-1, for example: the SCS of the activated UL BWP and the initial UL BWP are different, and / or, the CP lengths of the activated UL BWP and the initial UL BWP are different, and / or, the activated UL BWP does not include all RBs of the initial UL BWP.

[0139] In the embodiments of this application, overlap with the SBFD symbol includes partial overlap (i.e., the part is within the SBFD symbol and a part is within the non-SBFD symbol) and / or complete overlap (also, it can be said that it is within the SBFD symbol). Overlap with the non-SBFD symbol includes partial overlap (i.e., the part is within the non-SBFD symbol and a part is within the SBFD symbol) and / or complete overlap (also, it can be said that it is within the non-SBFD symbol).

[0140] In some embodiments, overlap with SBFD symbols and overlap with non-SBFD symbols do not both include the aforementioned partial overlap. For example, if overlap with SBFD symbols includes partial overlap, then overlap with non-SBFD symbols does not include partial overlap, and vice versa; this application is not limited thereto.

[0141] In this application embodiment, the relationship between the scheduled PUSCH and SBFD symbols and non-SBFD symbols is considered, including the following cases:

[0142] Case C: PUSCH and SBFD symbols (completely overlap).

[0143] Case D: PUSCH and non-SBFD symbols (completely overlap).

[0144] Case E:PUSCH overlaps with both SBFD and non-SBFD symbols.

[0145] In this application embodiment, the relationship between PUSCH and repetition is considered, including the following cases:

[0146] Case F: PUSCH does not have repeatability.

[0147] Case G:PUSCH has repetition.

[0148] In some embodiments, for Case G, Case C means that all repetitions of PUSCH completely overlap with the SBFD symbol, Case D means that all repetitions of PUSCH completely overlap with the non-SBFD symbol, and Case E means that at least some repetitions of PUSCH completely overlap with the SBFD symbol and at least some repetitions completely overlap with the non-SBFD symbol.

[0149] In this application embodiment, valid / invalid symbol types are considered, including the following cases:

[0150] Case H: One of the SBFD symbols and non-SBFD symbols is an invalid symbol (type), and the other is a valid symbol (type).

[0151] Case H-1: SBFD symbols are invalid symbols (type), and non-SBFD symbols are valid symbols (type).

[0152] Case H-2: Non-SBFD symbols are invalid symbols (type), while SBFD symbols are valid symbols (type).

[0153] Case I: There is no invalid symbol type, or both SBFD symbols and non-SBFD symbols are valid symbols (types).

[0154] In some embodiments, for Case H, it can also be said that PUSCH transmission is limited to SBFD symbols (when SBFD symbols are valid and non-SBFD symbols are invalid, Case H-2) or limited to non-SBFD symbols (when non-SBFD symbols are valid and SBFD symbols are invalid, Case H-1). For PUSCHs with repetitions, only the repetitions overlapping with SBFD symbols (for repetition Type B: actual) are transmitted, or only the repetitions overlapping with non-SBFD symbols (for repetition Type B: actual) are transmitted.

[0155] In this application embodiment, the downlink signal for scheduling / activating PUSCH is considered, including the following cases:

[0156] Case J: Scheduled by RAR (or RAR UL grant).

[0157] Case J-1: The RAR is a RAR in CBRA, or a RAR in response to a PRACH / preamble (for) CBRA, or a RAR in response to a preamble selected by the MAC layer (from the preamble for CBRA).

[0158] Case J-2: The RAR is a RAR in CFRA, or a RAR in response to a PRACH / preamble (for) CFRA, or a RAR in response to a preamble (for CFRA) indicated by a PDCCH order or RRC layer.

[0159] Case K: Scheduled / activated by DCI (format 0_0)

[0160] Case K-1: The DCI (format 0_0) has a CRC scrambled by TC-RNTI.

[0161] Case K-2: The DCI (format 0_0) has a CRC scrambled by C-RNTI / MCS-C-RNTI.

[0162] Case K-3: The DCI (format 0_0) has a CRC scrambled by CS-RNTI.

[0163] In some embodiments, in Case K-3, the PUSCH is a retransmission of the (first) (CG) PUSCH scheduled by the DCI, or an active CG PUSCH, or a scheduled CG PUSCH.

[0164] In some embodiments, the PUSCH in Case J-1 and / or Case J-2 and / or Case K-1 may be referred to as Msg3PUSCH((re-)transmission), wherein the PUSCH in Case K-1 may also be referred to as Msg3 PUSCH retransmission. The DCI in Case K-1 is in CSS, and the DCI in Case K-2 and / or Case K-3 may be in USS or in CSS.

[0165] In some embodiments, only certain combinations of Case A to Case K-3 considering different aspects are supported or exist, or certain combinations of Case A to Case K-3 considering different aspects are not supported or exist.

[0166] For example, the UE does not expect some combinations of Case A to Case K-3 mentioned above to occur.

[0167] For example, for Case F, the UE does not expect Case E, or does not support Case E, that is, the UE does not expect the situation to meet both Case F and Case E at the same time.

[0168] For example, Case K-2 is not supported for Case G.

[0169] For example, for Case G and / or Case K-3, the valid / invalid symbol type needs to be considered, that is, the combination with one or more of Case H to Case I needs to be considered. For Case F and / or Case J-1 and / or Case K-2, the valid / invalid symbol type does not need to be considered, that is, the combination with Case H to Case I does not need to be considered.

[0170] The above provides illustrative examples of various cases in the embodiments of this application, but this application is not limited thereto. The various cases described above can be implemented independently, or can be combined in any way, depending on the actual application situation. Other cases can also be added.

[0171] The following explains how to determine the frequency domain resources of this PUSCH.

[0172] In some embodiments, the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol) (for transmitting the PUSCH's PRBs) are associated with at least one of the following, and / or the UE determines the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) based on one or more of the following:

[0173] -Initial uplink BWP (starting PRB and / or ending PRB and / or size);

[0174] - The third frequency domain resources of the initial uplink BWP (the start PRB and / or end PRB and / or size);

[0175] -The (activated) uplink BWP (starting PRB and / or ending PRB and / or size);

[0176] - The third frequency domain resources of the (activated) uplink BWP (the start PRB and / or end PRB and / or size);

[0177] - Frequency domain offset.

[0178] In some embodiments, the third frequency domain resource of the initial uplink BWP includes the intersection of the first frequency domain resource (configured for the SCS of the initial UL BWP) and the initial uplink BWP.

[0179] In some embodiments, the third frequency domain resources of the initial uplink BWP are determined based on information used to configure the third frequency domain resources of the uplink BWP.

[0180] In some embodiments, the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol) (for transmitting the PRBs of the PUSCH (located in / corresponding to the SBFD symbol)) are associated with at least one of the above, including:

[0181] The frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol) (for transmitting the PUSCH PRBs) are determined by the FDRA field (provided RIV) in the RAR or DCI based on at least one indication, and / or, the UE determines the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol) (for transmitting the PUSCH PRBs) indicated by the FDRA field (provided RIV) in the RAR or DCI based on at least one indication.

[0182] In some embodiments, the FDRA field in RAR (or RAR(UL)grant) can also be called the PUSCH frequency resource allocation field. The TDRA field in RAR (or RAR(UL)grant) can also be called the PUSCH time resource allocation field.

[0183] In some embodiments, the FDRA domain / RIV indicates the frequency domain resources (located in / corresponding to the SBFD symbol) of the PUSCH based on at least one of the above, including: the length of the PRB (located in / corresponding to the SBFD symbol) indicated by the FDRA domain / RIV for the PUSCH is limited to a value associated with or determined by at least one of the above, or the maximum number of RBs allocated for the frequency domain resources (located in / corresponding to the SBFD symbol) of the PUSCH is equal to a value associated with or determined by at least one of the above.

[0184] For example, the maximum number of RBs for the frequency domain resource allocation (FDRA) for this PUSCH (located in / corresponding to the SBFD symbol) is equal to one of the following:

[0185] - The number of RBs in the initial uplink BWP (i.e., the size of the initial UL BWP);

[0186] - The number of available uplink PRBs in the initial uplink BWP;

[0187] - The number of RBs in the activated uplink BWP;

[0188] - The number of available uplink PRBs in the activated uplink BWP

[0189] - The largest of the following: the number of RBs in the initial uplink BWP and / or the number of RBs in the UL usable PRBs of the uplink BWP and / or the number of remaining RBs in the activated uplink BWP (including the number of PRBs from the first PRB of the UL usable PRBs to the last PRB of the activated UL BWP).

[0190] For example, in Table 1 It equals the maximum number of RBs for the frequency domain resource allocation (FDRA) used for this PUSCH (located in / corresponding to the SBFD symbol).

[0191] For example, in Table 1 The value of is related to the size of at least one of the terms. For example, The size of the initial UL BWP, or the size of the UL usable PRBs of the initial UL BWP, or the size of the UL usable PRBs of the activated UL BWP, or the largest / smallest value of the size of the initial UL BWP and the UL usable PRBs of the activated UL BWP, or the size from the start / first PRB of the UL usable PRBs of the activated UL BWP to the last PRB of the activated UL BWP (or the number of PRBs included).

[0192] For example, for different combinations of Case A to Case K-3 or different cases mentioned above, The definitions are different.

[0193] For example, regarding Case J / J-1( / J-2)+Case A( / B-1)(+Case C / D / E)(+Case F / G)(+Case H / H-1 / H-2 / I), This is the initial size of the UL BWP.

[0194] For example, regarding Case J / J-1( / J-2)+Case(B-1 / )B-2(+Case C / D / E)(+Case F / G)(+Case H / H-1 / H-2 / I), The size of the UL usable PRBs for the activated UL BWP.

[0195] For example, for Case K-1(+Case A / B / B-1 / B-2)(+Case C / D / E)(+Case F / G)(+Case H / H-1 / H-2 / I), This is the initial size of the UL BWP.

[0196] In some embodiments, the FDRA domain / RIV indicates the frequency domain resources of the PUSCH (located in / corresponding to the SBFD symbol) based on at least one of the above, including: the FDRA domain / RIV indicates the frequency domain resources of the PUSCH (located in / corresponding to the SBFD symbol) based on the RB number associated with at least one of the above, or the RB number allocated for the frequency domain resources of the PUSCH (located in / corresponding to the SBFD symbol) is associated with at least one of the above.

[0197] For example, (for Case J / J-1 / J-2 + Case A / B-1 (+ Case C / D / E)(+ Case H / I / E), and / or Case K / K-1 / K-2 / K-3 + Case A, and / or Case D / E) RB numbering (in ascending order of frequency domain position) starts from the first RB of the initial UL BWP (e.g., incrementing by 1 from 0 until the above). ).

[0198] For example, (for Case J / J-1 / J-2 + Case B-1 (+ Case C),) the RB numbers (in ascending order of frequency domain position) start from the RB in the active UL BWP that is the same as the first RB (frequency domain position) of the initial UL BWP (e.g., starting from 0 and incrementing by 1 until the above). ).

[0199] For example, (for Case J / J-1 / J-2 + Case A / B-1 + Case C / H-2, and / or Case K / K-1 / K-2 / K-3 + Case A, and / or Case D / E) RB numbering (in ascending order of frequency domain position) starts from the first RB of the initial UL BWP (e.g., starting from 0 and incrementing by 1 until the above). ).

[0200] For example, (for Case J / J-1 / J-2 + Case A / B / B-1 / B-2, and / or Case K / K-1 / K-2 / K-3) the RB numbering (in ascending order of frequency domain position) starts from the first RB of the active UL BWP (e.g., incrementing by 1 from 0 until the above). ).

[0201] For example, (for Case J / J-1 / J-2 + Case A + Case C, and / or Case K / K-1 / K-2 / K-3) RB numbering (in ascending order of frequency domain position) starts from the first RB of the UL usable PRB of the initial UL BWP (e.g., starting from 0 and incrementing by 1 until the above). ).

[0202] For example, RB in Table 1 start Corresponding to the RB number mentioned above. For example, RB start =0 corresponds to RB with number 0, RB start =1 corresponds to RB with number 1, and so on.

[0203] For example, the frequency domain resources of a PUSCH are indicated by the FDRA field (provided RIV) in the RAR or DCI based on the initial uplink BWP (the start PRB and / or end PRB and / or size). For example, this RIV indicates the frequency domain resources of the PUSCH (including the start RB and the number / length of RBs) based on the start RB and / or size of the initial uplink BWP. For example, assuming the values ​​in Table 1... This is the size of the initial UL BWP. Additionally, the RB numbering starts from the first PRB of this initial UL BWP.

[0204] For example, the frequency domain resources of a PUSCH are indicated by the FDRA field (provided RIV) in the RAR or DCI based on the third frequency domain resources (starting PRB and / or ending PRB and / or size) of the active uplink BWP. For example, the RIV indicates the frequency domain resources of the PUSCH based on the starting RB and / or size of the third frequency domain resources of the active uplink BWP, the number / length of the starting RB, and the RBs. For example, assuming the values ​​in Table 1... This represents the size of the third frequency domain resource. Additionally, the RB numbering starts from the first PRB of this third frequency domain resource.

[0205] For example, the frequency domain resources of a PUSCH are indicated by the FDRA field (provided RIV) in the RAR or DCI based on the initial uplink BWP (the start PRB and / or end PRB and / or size) and the third frequency domain resources of the active uplink BWP (the start PRB and / or end PRB and / or size). For example, the RIV indicates the frequency domain resources of the PUSCH based on the start RB and the size of the initial ULBWP of the third frequency domain resources of the active uplink BWP, the number / length of the start RB and RB. For example, assuming the values ​​in Table 1... This is the initial UL BWP size. Additionally, the RB numbering starts from the first PRB of this third frequency domain resource.

[0206] The following is an exemplary description of the frequency domain resources (allocation) (located in / corresponding SBFD symbols) of PUSCH (i.e., Case J / J-1 / J-2) scheduled by RAR.

[0207] In some embodiments, if the activated uplink BWP and the initial uplink BWP have the same subcarrier spacing (SCS) and the same cyclic prefix length (CP length) and the activated uplink BWP includes all resource blocks (RBs) of the initial uplink BWP (i.e., for Case B-1), or the activated uplink BWP is the initial uplink BWP (i.e., for Case A), the initial uplink BWP (its start and size) is used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol); for example, the RB numbering starts from the first RB of the initial uplink BWP (for Case A / B-1) or from the RB in the activated UL BWP that is the same as the first RB (frequency domain position) of the initial uplink BWP (for Case A / B-1), the maximum number of RBs used for frequency domain resource allocation (FDRA) is equal to the number of RBs in the initial uplink BWP.

[0208] Otherwise (i.e., for Case B-2), the active uplink BWP (start) and the initial UL BWP (size) are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol). For example, the RB numbering above starts from the first RB of the active uplink BWP, and the maximum number of RBs used for frequency domain resource allocation (FDRA) is equal to the number of RBs in the initial uplink BWP (i.e., the size of the initial uplink BWP).

[0209] In some embodiments, for Case A, the initial uplink BWP (start and size) is used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol). For Case B, i.e., Case B-1 / B-2, the active uplink BWP (start) and the initial UL BWP (size) are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol).

[0210] In some embodiments, for Case A and Case B, the activated uplink BWP (start) and the initial UL BWP (size) are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol).

[0211] In some embodiments, if the activated uplink BWP and the initial uplink BWP have the same subcarrier spacing (SCS) and the same cyclic prefix length (CP length) and the activated uplink BWP includes all resource blocks (RBs) of the initial uplink BWP (i.e., for Case B-1), or the activated uplink BWP is the initial uplink BWP (i.e., for Case A), the initial uplink BWP (its start and size) is used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol); for example, the RB numbering starts from the first RB of the initial uplink BWP (for Case A / Case B-1) or from the RB in the activated UL BWP that is the same as the first RB (frequency domain position) of the initial uplink BWP (for Case A / Case B-1), the maximum number of RBs used for frequency domain resource allocation (FDRA) is equal to the number of RBs in the initial uplink BWP.

[0212] Otherwise (i.e., for Case B-2), (when the size of the UL usable PRBs of the active uplink BWP is not greater than the size of the initial UL BWP), the start of the UL usable PRBs of the active uplink BWP and the size of the initial UL BWP are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol). For example, the above RB numbering starts from the first RB of the UL usable PRBs of the active uplink BWP, and the maximum number of RBs used for frequency domain resource allocation (FDRA) is equal to the number of RBs of the initial uplink BWP (i.e., the size of the initial uplink BWP). Alternatively, (when the size of the UL usable PRBs of the active uplink BWP is greater than the size of the initial UL BWP), the start and / or size of the UL usable PRBs of the active uplink BWP are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol). For example, the RB numbering mentioned above starts from the first RB of the UL usable PRBs of the active uplink BWP, and the maximum number of RBs used for frequency domain resource allocation (FDRA) is equal to the number of RBs of the UL usable PRBs of the active uplink BWP (i.e., the size of the UL usable PRBs of the active uplink BWP).

[0213] In some embodiments, for Case A, the initial uplink BWP (its start and size) is used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol). For Case B, i.e., Case B-1 / Case B-2, (when the size of the UL usable PRBs of the activated uplink BWP is not greater than the size of the initial UL BWP), the start of the UL usable PRBs of the activated uplink BWP and the size of the initial UL BWP are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol). Alternatively, (when the size of the UL usable PRBs of the activated uplink BWP is greater than the size of the initial UL BWP), the start and / or size of the UL usable PRBs of the activated uplink BWP are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol).

[0214] In some embodiments, for Case A and Case B, the UL usable PRBs (start and / or size) of the activated uplink BWP are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol).

[0215] In some embodiments, addressable PRBs include the aforementioned PRBs starting from the first PRB (i.e., the PRB numbered 0). RB.

[0216] The above provides an exemplary description of the frequency domain resources (allocation) (located in / corresponding to SBFD symbols) of PUSCH (i.e., Case J / J-1 / J-2) scheduled by RAR. The following provides an exemplary description of PUSCH scheduled by DCI.

[0217] In some embodiments, the same method as described above for Case J / J-1 / J-2 is used for Case K-1. Alternatively, in other embodiments, a different method is used for Case K-1 than that described above for Case J / J-1 / J-2.

[0218] In some embodiments, for Case K-2 / K-3, the same method as described above for Case J / J-1 / J-2 is used when determining the size of the DCI / FDRA domain based on the initial UL BWP. Alternatively, in other embodiments, for Case K-2 / K-3, a different method is used when determining the size of the DCI / FDRA domain based on the initial UL BWP than described above for Case J / J-1 / J-2.

[0219] In some embodiments, for Case K-1, and / or for Case K-2 / K-3 (and when the size of the DCI / FDRA domain is determined based on the initial UL BWP), the active uplink BWP (start) and the initial UL BWP (size) are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol).

[0220] In some embodiments, for Case K-1, and / or for Case K-2 / K-3 (and when the size of the DCI / FDRA domain is determined based on the initial UL BWP), (when the size of the UL usable PRBs of the activated uplink BWP is not greater than the size of the initial UL BWP), the start of the UL usable PRBs of the activated uplink BWP and the size of the initial UL BWP are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol). Alternatively, (when the size of the UL usable PRBs of the activated uplink BWP is greater than the size of the initial UL BWP), the start and / or size of the UL usable PRBs of the activated uplink BWP are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol).

[0221] In some embodiments, the frequency domain resources (allocation) of the PUSCH (corresponding to / located in the SBFD symbol) (for transmitting the PUSCH's PRBs) are associated with at least one of the following, including:

[0222] The frequency domain resources (allocation) of the PUSCH (corresponding to / located in the SBFD symbol) (PRBs for transmitting the PUSCH) are determined according to the PRBs (initial PRBs and / or number) indicated by the FDRA field (provided RIV) in the RAR or DCI and the at least one of them.

[0223] For example, the FDRA field (provided RIV) in RAR or DCI is based on at least one of the following indications for PRBs:

[0224] -Initial uplink BWP (starting RB and / or ending RB and / or size);

[0225] - The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0226] -The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0227] - The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0228] - Frequency domain offset.

[0229] For example, how the FDRA field (provided RIV) in the RAR or DCI is based on at least one of the above-mentioned indications for PRBs can be referred to the foregoing description, and this application is not limited thereto. For example, for a PUSCH scheduled by RAR, for Case A / Case B-1, the initial uplink BWP (start and size) is used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol); for Case B-2, the active uplink BWP (start) and the initial UL BWP (size) are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol). For example, for a PUSCH scheduled by DCI, for Case K-1, and / or, for Case K-2 / K-3 (and when the size of the DCI / FDRA field is determined according to the initial UL BWP), the active uplink BWP (start) and the initial UL BWP (size) are used to determine the frequency domain resources (allocation) of the PUSCH (located in / corresponding to the SBFD symbol).

[0230] In some embodiments, the frequency domain resources (allocation) of the PUSCH (corresponding to / located in the SBFD symbol) (PRBs for transmitting the PUSCH) are determined based on the PRBs (initial PRBs and / or number) indicated by the FDRA field (provided RIV) in the RAR or DCI and at least one of the above, including: the first / initial PRB (or the RB of the RIV) indicated by the UE according to the FDRA field (provided RIV). start The corresponding PRB and at least one of the above determine the first PRB of PUSCH.

[0231] In some embodiments, the RB offset is an offset relative to the start of the initial UL BWP (for Case J + Case A / B-1) or the start of the activated UL BWP (for Case J + Case B / B-1 / B-2). For example, this offset is the offset between the start and the first / starting PRB indicated by the RIV.

[0232] In some examples, explicit RB offsets can be used, such as those that are predefined or indicated by higher-layer signaling and / or physical-layer signaling.

[0233] In some embodiments, higher-layer signaling (e.g., SIB1 or dedicated signaling) includes information indicating one or more RB offsets. When multiple RB offsets are indicated, the RAR or DCI includes information indicating one of the RB offsets, and the RB offset indicated by the RAR / DCI is applied to the scheduled / activated PUSCH. For example, the starting PRB index of the PUSCH references the start position of the uplink BWP, and the starting PRB of the PUSCH in the first time-domain resource (SBFD symbol) is determined based on at least one of the following:

[0234] in, It is the starting PRB index of the UL BWP start (RB) reference active (in the SBFD symbol, or located at / corresponding to the SBFD symbol) (e.g., This is the starting PRB index of PUSCH in the SBFD symbol with reference to the start of the UL BWP; for example, the PRBs in the active UL BWP (in ascending order of frequency domain position) are numbered / indexed starting from the first RB (e.g., incrementing by 1 from 0). This is equal to the number / index of the starting PRB of the PUSCH. The RB offset is a predefined or indicated value, which may be a positive integer, a negative integer, or zero.

[0235] This is the starting PRB index of the reference active UL BWP start (RB) indicated by the FDRA field (provided RIV) of the RAR or DCI, or the index of the reference active UL BWP start (RB) corresponding to the first / starting PRB indicated by the FDRA field (provided RIV) of the RAR or DCI. For example, PRBs in the active UL BWP (in ascending order of frequency domain position) are numbered / indexed starting from the first RB (e.g., incrementing by 1 from 0). This is equal to the number / index corresponding to the starting PRB indicated by the FDRA field (provided RIV) of the RAR or DCI. Specifically, the starting PRB index of the reference active UL BWP start (RB) is the same as the aforementioned RIV-based RB number, or the starting PRB index of the reference active UL BWP start (RB) is different from the aforementioned RIV-based RB number. For example, when the aforementioned RIV-based RB number starts from the start of the active UL BWP, they are the same. For example, for Case B, when the aforementioned RIV-based RB number starts from the start of the initial UL BWP, and the start of the initial UL BWP is different from the start of the active UL BWP, they are different.

[0236] It is the reference index of the starting PRB of the active UL BWP (either the active UL BWP or the initial UL BWP).

[0237] It is the number of PRBs in UL usable PRBs (either active UL BWP or initial UL BWP).

[0238] In some embodiments, when frequency hopping (FH) is enabled, the UE can also refer to the start of the UL BWP to determine the corresponding starting PRB index for the PUSCH.

[0239] In some embodiments, the frequency domain resources (allocation) of the PUSCH (corresponding to / located in the SBFD symbol) (PRBs for transmitting the PUSCH) are associated with at least one of the following: the UE processes the FDRA field in the RAR or DCI according to one or more of the following, the processing including truncation and / or insertion of bits.

[0240] In some embodiments, the UE does not expect the PRBs of the PUSCH in the SBFD symbol to overlap with the PRBs other than the UL usable PRBs of the activated UL BWP.

[0241] The following is a schematic explanation of frequency hopping (FH).

[0242] In some embodiments, the RAR or DCI includes a frequency hopping flag field.

[0243] For example, the frequency hopping flag includes 1 bit. If the value of the frequency hopping flag is 0, then PUSCH does not hop; otherwise, if the value of the frequency hopping flag is 1, then PUSCH hops.

[0244] The following description uses the example of PUSCH being used for uplink grant (UL grant) scheduling in the random access response (RAR) (Case J), ​​or PUSCH being scheduled by downlink control information (CRC scrambled by TC-RNTI) (Case K-1); this application is not limited to these examples.

[0245] In some embodiments (for Case C / E / H-2 / I), (when the PUSCH has frequency hopping), the number of bits included in the RAR or DCI (in the FDRA field) for indicating the frequency hopping offset and / or the frequency hopping offset indicated by the RAR or DCI (in the FDRA field) and / or the starting frequency domain resources of the PUSCH (corresponding to / located in the SBFD symbol) for the (corresponding) second hop are related to at least one of the following:

[0246] -Initial uplink BWP (starting RB and / or ending RB and / or size);

[0247] - The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0248] -The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0249] - The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0250] - Frequency offset.

[0251] In some embodiments, (for Case D / E / I), the frequency offset of the PUSCH (corresponding to / located in the SBFD symbol), i.e., the frequency hopping offset, is determined based on the size of the initial uplink BWP, or, for non-SBFD symbols, the frequency hopping offset is determined based on the size of the initial uplink BWP. For example, in the last column of Table 2... This indicates the initial size of the UL BWP.

[0252] In some embodiments (for Case C / E / I), the frequency offset of the PUSCH (corresponding to / located in the SBFD symbol) is determined based on the size of the UL usable PRBs (of the initial uplink BWP or the active UL BWP), or the frequency offset for the SBFD symbol is determined based on the size of the UL usable PRBs (of the initial uplink BWP or the active UL BWP), for example, in the last column of Table 2. This indicates the size of UL usable PRBs (for the initial uplink BWP or the active UL BWP).

[0253] In some embodiments, the PUSCH in the first time domain resource (SBFD symbol) determines the number of bits for frequency hopping and / or the corresponding frequency offset based on the size of UL usable PRBs in the (activated) uplink BWP, or the number of bits for frequency hopping and / or the corresponding frequency offset is determined based on the size of UL usable PRBs in the initial uplink BWP.

[0254] For example, for PUSCH in the SBFD symbol, the second hop (2) is determined based on the size (range) of the UL usable PRBs of the (activated) uplink BWP. nd The corresponding frequency offset of the hop; for example, for PUSCH in the SBFD symbol, the second hop (2 hops) is determined based on the size (range) of the UL usable PRBs of the initial uplink BWP. nd The corresponding frequency shift of (hop).

[0255] Table 2

[0256] The following is a further explanation of the initial RB.

[0257] For example, the following RB UL S B start It can also be replaced with the aforementioned

[0258] For example, the following RB start For example, the starting PRB index of the PUSCH located at / corresponding SBFD symbol (referencing the start of the active UL BWP) determined by the aforementioned method.

[0259] For example, the following RB offset It refers to the frequency hopping offset for the SBFD symbol, or the frequency hopping offset for the corresponding SBFD symbol of the PUSCH.

[0260] In some examples (for J / K-1+F), for intra-slot frequency hopping in the PUSCH time slot of an SBFD symbol, the starting RB in each hop can be given by the following formula:

[0261] In some examples (for J / K-1+G), for inter-slot frequency hopping of PUSCH in SBFD symbols, when pusch-DMRS-Bundling is not enabled, the slot... The initial RB during the period is given by the following formula:

[0262] The frequency domain resources have been illustrated above; the time domain resources will now be discussed. The following explanation uses the cases where the PUSCH is used for uplink grant scheduling in the Random Access Response (RAR), and / or where the PUSCH is scheduled by downlink control information (e.g., DCI format 0_0 with CRC scrambled by TC-RNTI). PUSCH repetition is possible, such as PUSCH repetition in Msg 3 transmission (which can be referred to as Msg.3repepition).

[0263] In some embodiments, for a first-type Msg3 repetition, when determining multiple slots (N·K slots) for a PUSCH scheduled by a RAR UL grant or a DCI (e.g., DCI format 0_0) with a CRC scrambled by TC-RNTI, if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a downlink symbol indicated by tdd-UL-DL-ConfigurationCommon (if provided), or overlaps with a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, then that slot is not counted in the total number of N·K slots for a PUSCH transmission of a PUSCH repetition Type A scheduled by RAR UL grant. tdd-UL-DL-ConfigurationCommon if provided, or a symbol of an SS / PBCH block with index provided by ssb-PositionsInBurst).

[0264] The following description focuses on the second type, Msg3. In some embodiments, only Case H / H-1 / H-2 is supported for Case J / J-1 / J-2 / K-1+Case G.

[0265] In some embodiments, for Case H, the UE determines the time slot based on the RAR and / or DCI and / or reference repetition (e.g., the first repetition) and / or reference time slot (e.g., the time slot determined by the time slot offset k2 indicated by the RAR / DCI, such as slot n+k2+Δ+2). μ ·K cell,offset ,whereΔis a pre-defined / indicated value,eg0,1,2,K cell,offsetis provided by cellSpecificKoffset; otherwise, if not provided, K cell,offset The determination of whether to apply Case H-1 or Case H-2 for symbols allocated in (=0) (for PUSCH of RAR / DCI scheduling). For example, determining whether the valid symbol type is SBFD symbol or non-SBFD symbol.

[0266] For example, for PUSCH with repetition, if the symbol allocated in the reference repetition or reference slot (or symbol allocation) overlaps with the non-SBFD symbol, it is Case H-1; if the symbol allocated in the reference repetition or reference slot (or symbol allocation) overlaps with the SBFD symbol, it is Case H-2.

[0267] For example, the valid symbol type is the symbol type of the first PUSCH transmission opportunity (i.e., the first repetition) indicated by the RAR UL grant or DCI that schedules the PUSCH. The UE does not expect the first PUSCH transmission opportunity to be mapped to both SBFD and non-SBFD symbols; that is, the first PUSCH transmission opportunity should be in an SBFD symbol (the symbol type of the first PUSCH transmission opportunity is SBFD) or in a non-SBFD symbol (the symbol type of the first PUSCH transmission opportunity is non-SBFD).

[0268] In some embodiments, (when the PUSCH has repetitions) (when the PUSCH is associated with a PRACH using a second RO) the UE determines the time slot in which the PUSCH repetitions based on a first time domain resource and / or a second time domain resource.

[0269] For example, for a PUSCH transmission associated with a PRACH transmission using additional RO, the time slots in which the PUSCH repetitions occur can be determined based on SBFD symbols and / or non-SBFD symbols. For example, for a Type 2 Msg3 repetition, the UE determines multiple time slots for PUSCHs scheduled by RAR UL grant or with a DCI (e.g., DCI format 0_0) that has a CRC scrambled by TC-RNTI, based on whether the valid symbol type is an SBFD symbol or a non-SBFD symbol.

[0270] The above explanation pertains to the second type of Msg3 repetition.

[0271] The following examples illustrate how to determine multiple time slots for a PUSCH using various types of PUSCH repetition.

[0272] Table 3 is an example of how to determine the slot (N·K slots) where the repeat of PUSCH is located for the second type of Msg3 repeat.

[0273] Table 3

[0274] Table 4 provides another example of how to determine the N·K slots for the repetition of PUSCH for the second type of Msg3 repetition. Case J is used as an example; a similar method can also be applied to Case K-1.

[0275] Table 4

[0276] Table 5 provides another example of how to determine the slots (N·K slots) for PUSCH repetitions in the second type of Msg3 repetition. Case J is used as an example; a similar method can also be applied to Case K-1.

[0277] Table 5

[0278] Table 6 is an example of how to determine the time slot of a PUSCH repetition for the second type of Msg3 repetition and for other PUSCHs different from Msg3 PUSCHs.

[0279] Table 6

[0280] The conditions in the above examples can be separated or combined, and this application is not limited to this.

[0281] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0282] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0283] As can be seen from the above embodiments, network devices can operate in full-duplex mode (simultaneous reception and transmission), and terminal devices can also use corresponding resources to send and receive signals when the network devices are operating in full-duplex mode. This can improve uplink transmission capacity and coverage, reduce uplink transmission latency, and increase resource allocation flexibility and resource utilization.

[0284] Second aspect of the embodiments

[0285] This application provides a PUSCH receiving method, which is described from the perspective of the network device. The content that is the same as that in the first aspect of the embodiment will not be repeated.

[0286] Figure 6 is a schematic diagram of a PUSCH receiving method according to an embodiment of this application. As shown in Figure 6, the method includes:

[0287] 601, The network device sends information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0288] 602. A network device receives a PUSCH scheduled or activated by a Random Access Response (RAR) in a CBRA or CFRA (or in response to a PRACH in a CBRA or CFRA) or by a Downlink Control Information (DCI) scrambled by a TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI.

[0289] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

[0290] In some embodiments, the third frequency domain resources (UL usable PRBs) of the (activated) uplink BWP include / are determined to be the intersection of the first frequency domain resources (configured for the SCS of the (activated) uplink BWP) and the (activated) uplink BWP.

[0291] It is worth noting that Figure 6 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 6 above.

[0292] In some embodiments, (when the PUSCH is in the first time domain resource,) the frequency domain resource (allocation) of the PUSCH (for transmitting the PUSCH PRBs) is associated with at least one of the following (the network device determines the frequency domain resource (allocation) of the PUSCH (for transmitting the PUSCH PRBs) based on at least one of the following):

[0293] Initial uplink BWP (starting RB and / or ending RB and / or size);

[0294] The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0295] The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0296] The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0297] Frequency domain offset.

[0298] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0299] The frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH PRBs) are determined by the Frequency Domain Resource Allocation (FDRA) field (provided RIV) in the Random Access Response (RAR) or the Downlink Control Information (DCI) based on at least one indication (the network device determines the frequency domain resource allocation (for transmitting the PUSCH PRBs) indicated by the FDRA field (provided RIV) in the RAR or DCI according to at least one indication).

[0300] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0301] The frequency domain resources (allocation) of the PUSCH (PRBs for transmitting the PUSCH) are determined by the PRBs (initial PRBs and / or number) indicated by the Frequency Domain Resource Allocation (FDRA) field (provided RIV) in the Random Access Response (RAR) or the Downlink Control Information (DCI) and at least one of them (the network device determines the frequency domain resource allocation (PRBs for transmitting the PUSCH) based on the frequency domain resources (initial PRBs and / or number / length) indicated by the Frequency Domain Resource Allocation (FDRA) field (provided RIV) in the Random Access Response (RAR) or the Downlink Control Information (DCI) and at least one of them).

[0302] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0303] The FDRA field in the RAR or DCI is processed according to at least one of the above methods, the processing including truncating and / or inserting bits.

[0304] In some embodiments, (when the PUSCH is in a first time domain resource,) (when the PUSCH has frequency hopping,) the number of bits included in the RAR or DCI (in the FDRA field) for indicating frequency hopping offset and / or the frequency hopping offset indicated by the RAR or DCI (in the FDRA field) and / or the starting frequency domain resource of the corresponding second hop of the PUSCH is related to at least one of the following (the network device determines, based on the at least one, the number of bits included in the RAR or DCI (in the FDRA field) for indicating frequency hopping offset and / or the frequency hopping offset indicated by the RAR or DCI (in the FDRA field) and / or the starting frequency domain resource of the corresponding second hop of the PUSCH):

[0305] Initial uplink BWP (starting RB and / or ending RB and / or size);

[0306] The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0307] The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0308] The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0309] Frequency domain offset.

[0310] In some embodiments, the effective symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the random access response or downlink control information (DCI) that schedules the PUSCH.

[0311] In some embodiments, multiple time slots for PUSCH scheduled by random access response or downlink control information (DCI) with cyclic redundancy check (CRC) scrambled by TC-RNTI are determined based on whether the valid symbol type is a first time domain resource or a second time domain resource.

[0312] In some embodiments, the frequency hopping offset indicated by the random access response or downlink control information and / or the starting frequency domain resources of the corresponding second hop of the PUSCH are related to at least one of the following:

[0313] Initial uplink BWP;

[0314] The third frequency domain resources of the initial uplink BWP;

[0315] The uplink BWP;

[0316] The third frequency domain resources of the uplink BWP;

[0317] Frequency domain offset.

[0318] In some embodiments, the time slot in which the PUSCH repeats is associated with a first time-domain resource and / or a second time-domain resource.

[0319] In some embodiments, the time slot in which the PUSCH is repeated is associated with a first time domain resource and / or a second time domain resource, including: determining multiple time slots for the PUSCH based on whether the valid symbol type is a first time domain resource or a second time domain resource.

[0320] In some embodiments, the effective symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the random access response or DCI that schedules the PUSCH.

[0321] In some embodiments, the terminal device sends the PUSCH only in the valid symbol type.

[0322] In some embodiments, the plurality of time slots are determined in the following manner:

[0323] If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0324] When the valid symbol type is a second time-domain resource: when the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI and associated with a PRACH transmission in a second RO, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and symbols that do not include SSBs, then the time slot is one of the plurality of time slots; when the PUSCH is scheduled by a DCI different from the DCI with a CRC scrambled by TC-RNTI, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and downlink symbols indicated by the second uplink / downlink configuration (tdd-UL-DL-ConfigurationDedicated) and symbols that do not include SSBs, then the time slot is one of the plurality of time slots.

[0325] In some embodiments, when the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI, and the PUSCH associated PRACH transmission is in the first RO, the time slot in which the PUSCH repeats is independent of the first time domain resource and / or the second time domain resource; and when the PUSCH associated PRACH transmission is in the second RO, the time slot in which the PUSCH repeats is related to the first time domain resource and / or the second time domain resource.

[0326] In some embodiments, when the PUSCH is dispatched by a random access response or a DCI with a CRC scrambled by TC-RNTI,

[0327] In the case where the PUSCH is associated with a PRACH transmission in the first RO, if at least one symbol in a time slot, indicated by an index row of the resource allocation table, overlaps with a downlink symbol indicated by the first uplink / downlink configuration, or overlaps with a symbol of an SSB with an index provided by the SSB configuration, then the time slot is not one of the plurality of time slots (this time slot is not counted in the plurality of time slots for the PUSCH scheduled by the random access response or DCI).

[0328] In the case where the PUSCH is associated with a PRACH transmission in the second RO:

[0329] If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0330] In the case where the valid symbol type is a second time domain resource: if all symbols allocated for a PUSCH transmission opportunity in a time slot are second time domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0331] In some embodiments, the terminal device indicates / reports whether the UE supports second-type Msg3 repetition via a first parameter or information field in the UE capability information, or a combination of one or more of the following:

[0332] Used to indicate whether the terminal device supports the first type of Msg3 repeating (second) parameter / information field (e.g., pusch-RepetitionMsg3-r17);

[0333] (Third) parameter / information field used to indicate whether the terminal device is an SBFD-aware UE and / or whether it supports the basic characteristics / capabilities of SBFD-aware UE;

[0334] The (fourth) parameter / information field used to indicate whether the terminal device supports SBFD random access (in RRC_IDLE / INACTIVE / CONNECTED mode);

[0335] The (fifth) parameter / information field is used to indicate support for the repeating of the leading / PRACH in the second RO.

[0336] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0337] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0338] As can be seen from the above embodiments, network devices can operate in full-duplex mode (simultaneous reception and transmission), and terminal devices can also use corresponding resources to send and receive signals when the network devices are operating in full-duplex mode. This can improve uplink transmission capacity and coverage, reduce uplink transmission latency, and increase resource allocation flexibility and resource utilization.

[0339] Third aspect of the embodiments

[0340] This application provides a PUSCH transmitting device. This device may be, for example, a terminal device, or one or more components or parts configured within a terminal device; details identical to those in the first aspect of the embodiment will not be repeated.

[0341] Figure 7 is a schematic diagram of a PUSCH transmitting device according to an embodiment of this application. Since the principle of this device in solving the problem is the same as the method of the embodiment of the first aspect, its specific implementation can refer to the embodiment of the first aspect, and the contents that are the same will not be repeated. As shown in Figure 7, the PUSCH transmitting device 700 includes: a receiver 701 and a transmitter 702; it may also include a processor 703.

[0342] Receiver 701 receives information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0343] Transmitter 702 transmits a PUSCH scheduled or activated by a Random Access Response (RAR) in a CBRA or CFRA (or in response to a PRACH in a CBRA or CFRA) or by a Downlink Control Information (DCI) scrambled by a TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI.

[0344] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

[0345] In some embodiments, the third frequency domain resources (UL usable PRBs) of the (activated) uplink BWP include / are determined to be the intersection of the first frequency domain resources (configured for the SCS of the (activated) uplink BWP) and the (activated) uplink BWP.

[0346] In some embodiments, for cases where the terminal device is not provided with information for configuring the third frequency domain resources of the (activated) uplink BWP, and / or for PUSCH (aka.Msg.3PUSCH(re)transmission) scheduled by a random access response (RAR) and / or CRC scrambled by TC-RNTI with a PRA (or in response to a PRA's PRACH), and / or for (contention-based) random access (PUSCH in process), and / or for cases where the UL BWP is an initial UL BWP, the third frequency domain resources (UL usable PRBs) of the (activated) uplink BWP include / are determined to be the intersection of the first frequency domain resources and the (activated) uplink BWP (configured for the SCS of the (activated) uplink BWP).

[0347] In some embodiments, in a first time domain resource, the first frequency domain resource and / or the third frequency domain resource ((active UL BWP) UL usable PRBs) are used for uplink and a second frequency domain resource and / or a fourth frequency domain resource ((active DL BWP) DL usable PRBs)) are used for downlink, the second time domain resource is outside the first time domain resource.

[0348] In some embodiments, the (activated) uplink BWP and the initial uplink BWP have the same subcarrier spacing (SCS) and the same cyclic prefix length (CP length), and the (activated) uplink BWP includes all resource blocks (RBs) of the initial uplink BWP; or, the (activated) uplink BWP is the initial uplink BWP, then the initial uplink BWP is used to determine the frequency domain resources of the PUSCH; otherwise, the (activated) uplink BWP is used to determine the frequency domain resources of the PUSCH.

[0349] or,

[0350] If the (activated) uplink BWP is the initial uplink BWP, then the initial uplink BWP is used to determine the frequency domain resources of the PUSCH; otherwise, the (activated) uplink BWP is used to determine the frequency domain resources of the PUSCH.

[0351] In some embodiments, in the frequency domain resource allocation of the PUSCH, the RB numbering starts from the first RB of the (activated) uplink BWP, and the maximum number of RBs used for frequency domain resource allocation (FDRA) is equal to the number of RBs in the initial uplink BWP.

[0352] or,

[0353] In the frequency domain resource allocation of the PUSCH, the RB numbering starts from the first RB of the third frequency domain resource (UL usable PRBs) of the (activated) uplink BWP, and the maximum number of RBs used for frequency domain resource allocation (FDRA) is equal to one of the following: the maximum value of the number of RBs in the initial uplink BWP, the number of uplink available PRBs in the initial uplink BWP, the number of RBs in the initial uplink BWP and / or the number of RBs in the third frequency domain resource (UL usable PRBs) and / or the remaining number of RBs in the (activated) uplink BWP.

[0354] In some embodiments, (when the PUSCH is in the first time domain resource,) the frequency domain resource (allocation) of the PUSCH (for transmitting the PUSCH PRBs) is associated with at least one of the following (the terminal device determines the frequency domain resource (allocation) of the PUSCH (for transmitting the PUSCH PRBs) based on at least one of the following):

[0355] Initial uplink BWP (starting RB and / or ending RB and / or size);

[0356] The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0357] The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0358] The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0359] Frequency domain offset.

[0360] In some embodiments, the third frequency domain resource of the initial uplink BWP includes the intersection of the first frequency domain resource and the initial uplink BWP (configured for the SCS of the initial uplink BWP).

[0361] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0362] The frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH PRBs) are determined by the Frequency Domain Resource Allocation (FDRA) field (provided RIV) in the Random Access Response (RAR) or the Downlink Control Information (DCI) based on at least one indication (the terminal device determines the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH PRBs) indicated by the FDRA field (provided RIV) in the RAR or DCI according to at least one indication).

[0363] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0364] The frequency domain resources (allocation) of the PUSCH (PRBs for transmitting the PUSCH) are determined by the PRBs (initial PRBs and / or quantity / length) indicated by the Frequency Domain Resource Allocation (FDRA) field (provided RIV) in the Random Access Response (RAR) or the Downlink Control Information (DCI) and at least one of them (the terminal device determines the frequency domain resource allocation (PRBs for transmitting the PUSCH) based on the frequency domain resources (initial PRBs and / or quantity / length) indicated by the Frequency Domain Resource Allocation (FDRA) field (provided RIV) in the Random Access Response (RAR) or the Downlink Control Information (DCI) and at least one of them).

[0365] In some embodiments, the FDRA field (provided RIV) in the RAR or DCI indicates frequency domain resources based on at least one of the following:

[0366] Initial uplink BWP (starting RB and / or ending RB and / or size);

[0367] The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0368] The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0369] The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0370] Frequency domain offset.

[0371] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0372] The FDRA field in the RAR or DCI is processed according to at least one of the above methods, the processing including truncating and / or inserting bits.

[0373] In some embodiments, (when the PUSCH is in a first time domain resource,) (when the PUSCH has frequency hopping,) the number of bits included in the RAR or DCI (in the FDRA field) for indicating frequency hopping offset and / or the frequency hopping offset indicated by the RAR or DCI (in the FDRA field) and / or the starting frequency domain resource of the corresponding second hop of the PUSCH is related to at least one of the following (the terminal device determines, based on the at least one, the number of bits included in the RAR or DCI (in the FDRA field) for indicating frequency hopping offset and / or the frequency hopping offset indicated by the RAR or DCI (in the FDRA field) and / or the starting frequency domain resource of the corresponding second hop of the PUSCH):

[0374] Initial uplink BWP (starting RB and / or ending RB and / or size);

[0375] The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0376] The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0377] The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0378] Frequency domain offset.

[0379] In some embodiments, the PUSCH has repetition (when the PUSCH is associated with a PRACH using a second RO), and the time slot in which the PUSCH repetition occurs is related to a first time domain resource and / or a second time domain resource (processor 1703 determines the time slot in which the PUSCH repetition occurs based on the first time domain resource and / or the second time domain resource).

[0380] In some embodiments, the effective symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the random access response or downlink control information (DCI) that schedules the PUSCH.

[0381] In some embodiments, multiple time slots for PUSCH scheduled by random access response or downlink control information (DCI) with cyclic redundancy check (CRC) scrambled by TC-RNTI are determined based on whether the valid symbol type is a first time domain resource or a second time domain resource.

[0382] In some embodiments, the frequency hopping offset indicated by the random access response or downlink control information and / or the starting frequency domain resources of the corresponding second hop of the PUSCH are related to at least one of the following:

[0383] Initial uplink BWP;

[0384] The third frequency domain resources of the initial uplink BWP;

[0385] The uplink BWP;

[0386] The third frequency domain resources of the uplink BWP;

[0387] Frequency domain offset.

[0388] In some embodiments, the time slot in which the PUSCH repeats is associated with a first time-domain resource and / or a second time-domain resource.

[0389] In some embodiments, the time slot in which the PUSCH is repeated is associated with a first time domain resource and / or a second time domain resource, including: determining multiple time slots for the PUSCH based on whether the valid symbol type is a first time domain resource or a second time domain resource.

[0390] In some embodiments, the effective symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the random access response or DCI that schedules the PUSCH.

[0391] In some embodiments, the terminal device sends the PUSCH only in the valid symbol type.

[0392] In some embodiments, the plurality of time slots are determined in the following manner:

[0393] If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0394] When the valid symbol type is a second time-domain resource: when the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI and associated with a PRACH transmission in a second RO, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and symbols that do not include SSBs, then the time slot is one of the plurality of time slots; when the PUSCH is scheduled by a DCI different from the DCI with a CRC scrambled by TC-RNTI, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and downlink symbols indicated by the second uplink / downlink configuration (tdd-UL-DL-ConfigurationDedicated) and symbols that do not include SSBs, then the time slot is one of the plurality of time slots.

[0395] In some embodiments, when the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI, and the PUSCH associated PRACH transmission is in the first RO, the time slot in which the PUSCH repeats is independent of the first time domain resource and / or the second time domain resource; and when the PUSCH associated PRACH transmission is in the second RO, the time slot in which the PUSCH repeats is related to the first time domain resource and / or the second time domain resource.

[0396] In some embodiments, when the PUSCH is dispatched by a random access response or a DCI with a CRC scrambled by TC-RNTI,

[0397] In the case where the PUSCH is associated with a PRACH transmission in the first RO, if at least one symbol in a time slot, indicated by an index row of the resource allocation table, overlaps with a downlink symbol indicated by the first uplink / downlink configuration, or overlaps with a symbol of an SSB with an index provided by the SSB configuration, then the time slot is not one of the plurality of time slots (this time slot is not counted in the plurality of time slots for the PUSCH scheduled by the random access response or DCI).

[0398] In the case where the PUSCH is associated with a PRACH transmission in the second RO:

[0399] If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0400] In the case where the valid symbol type is a second time domain resource: if all symbols allocated for a PUSCH transmission opportunity in a time slot are second time domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0401] In some embodiments, the terminal device indicates / reports whether the UE supports second-type Msg3 repetition via a first parameter or information field in the UE capability information, or a combination of one or more of the following:

[0402] Used to indicate whether the terminal device supports the first type of Msg3 repeating (second) parameter / information field (e.g., pusch-RepetitionMsg3-r17);

[0403] (Third) parameter / information field used to indicate whether the terminal device is an SBFD-aware UE and / or whether it supports the basic characteristics / capabilities of SBFD-aware UE;

[0404] The (fourth) parameter / information field used to indicate whether the terminal device supports SBFD random access (in RRC_IDLE / INACTIVE / CONNECTED mode);

[0405] The (fifth) parameter / information field is used to indicate support for the repeating of the leading / PRACH in the second RO.

[0406] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The PUSCH transmitting device 1700 of this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0407] Furthermore, for simplicity, Figure 7 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0408] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0409] As can be seen from the above embodiments, network devices can operate in full-duplex mode (simultaneous reception and transmission), and terminal devices can also use corresponding resources to send and receive signals when the network devices are operating in full-duplex mode. This can improve uplink transmission capacity and coverage, reduce uplink transmission latency, and increase resource allocation flexibility and resource utilization.

[0410] Fourth aspect of the embodiment

[0411] This application provides a PUSCH receiving device. This device may be, for example, a network device, or one or more components or parts configured within a network device; details identical to those in the third aspect of the embodiment will not be repeated.

[0412] Figure 8 is a schematic diagram of a PUSCH receiving device according to an embodiment of this application. Since the principle of this device in solving the problem is the same as the method in the embodiments of the first and second aspects, its specific implementation can refer to the embodiments of the first and second aspects, and the contents that are the same will not be repeated. As shown in Figure 8, the PUSCH receiving device 800 includes: a transmitter 801 and a receiver 802; it may also include a processor 803.

[0413] Transmitter 801 transmits information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0414] Receiver 802 receives, on the (activated) uplink BWP, a PUSCH scheduled or activated by a random access response (RAR) in a CBRA or CFRA (or in response to a PRACH in a CBRA or CFRA) or by downlink control information (DCI) scrambled by TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI.

[0415] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

[0416] In some embodiments, the third frequency domain resources (UL usable PRBs) of the (activated) uplink BWP include / are determined to be the intersection of the first frequency domain resources (configured for the SCS of the (activated) uplink BWP) and the (activated) uplink BWP.

[0417] In some embodiments, (when the PUSCH is in the first time domain resource) the frequency domain resource (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) is associated with at least one of the following:

[0418] Initial uplink BWP (starting RB and / or ending RB and / or size);

[0419] The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0420] The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0421] The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0422] Frequency domain offset.

[0423] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0424] The frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH PRBs) are determined by the Frequency Domain Resource Allocation (FDRA) field (provided RIV) in the Random Access Response (RAR) or the Downlink Control Information (DCI) based on at least one indication (the terminal device determines the frequency domain resource allocation (for transmitting the PUSCH PRBs) indicated by the FDRA field (provided RIV) in the RAR or DCI according to at least one indication).

[0425] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0426] The frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH) are determined based on the PRBs (starting PRB and / or number / length) indicated in the Frequency Domain Resource Allocation (FDRA) field (provided RIV) of the Random Access Response (RAR) or the Downlink Control Information (DCI) and at least one of the above.

[0427] In some embodiments, the frequency domain resources (allocation) of the PUSCH (for transmitting the PUSCH's PRBs) are associated with at least one of the following:

[0428] The FDRA field in the RAR or DCI is processed according to at least one of the above methods, the processing including truncating and / or inserting bits.

[0429] In some embodiments, (when the PUSCH is in a first time-domain resource), (when the PUSCH has frequency hopping), the number of bits included in the RAR or DCI (in the FDRA field) for indicating the frequency hopping offset and / or the frequency hopping offset indicated by the RAR or DCI (in the FDRA field) and / or the starting frequency-domain resource of the corresponding second hop of the PUSCH are related to at least one of the following:

[0430] Initial uplink BWP (starting RB and / or ending RB and / or size);

[0431] The third frequency domain resources of the initial uplink BWP (the start RB and / or end RB and / or size);

[0432] The (activated) uplink BWP (starting RB and / or ending RB and / or size);

[0433] The third frequency domain resources of the (activated) uplink BWP (the start RB and / or end RB and / or size);

[0434] Frequency domain offset.

[0435] In some embodiments, the effective symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the random access response or downlink control information (DCI) that schedules the PUSCH.

[0436] In some embodiments, multiple time slots for PUSCH scheduled by random access response or downlink control information (DCI) with cyclic redundancy check (CRC) scrambled by TC-RNTI are determined based on whether the valid symbol type is a first time domain resource or a second time domain resource.

[0437] In some embodiments, the frequency hopping offset indicated by the random access response or downlink control information and / or the starting frequency domain resources of the corresponding second hop of the PUSCH are related to at least one of the following:

[0438] Initial uplink BWP;

[0439] The third frequency domain resources of the initial uplink BWP;

[0440] The uplink BWP;

[0441] The third frequency domain resources of the uplink BWP;

[0442] Frequency domain offset.

[0443] In some embodiments, the time slot in which the PUSCH repeats is associated with a first time-domain resource and / or a second time-domain resource.

[0444] In some embodiments, the time slot in which the PUSCH is repeated is associated with a first time domain resource and / or a second time domain resource, including: determining multiple time slots for the PUSCH based on whether the valid symbol type is a first time domain resource or a second time domain resource.

[0445] In some embodiments, the effective symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the random access response or DCI that schedules the PUSCH.

[0446] In some embodiments, the terminal device sends the PUSCH only in the valid symbol type.

[0447] In some embodiments, the plurality of time slots are determined in the following manner:

[0448] If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0449] When the valid symbol type is a second time-domain resource: when the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI and associated with a PRACH transmission in a second RO, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and symbols that do not include SSBs, then the time slot is one of the plurality of time slots; when the PUSCH is scheduled by a DCI different from the DCI with a CRC scrambled by TC-RNTI, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and downlink symbols indicated by the second uplink / downlink configuration (tdd-UL-DL-ConfigurationDedicated) and symbols that do not include SSBs, then the time slot is one of the plurality of time slots.

[0450] In some embodiments, when the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI, and the PUSCH associated PRACH transmission is in the first RO, the time slot in which the PUSCH repeats is independent of the first time domain resource and / or the second time domain resource; and when the PUSCH associated PRACH transmission is in the second RO, the time slot in which the PUSCH repeats is related to the first time domain resource and / or the second time domain resource.

[0451] In some embodiments, when the PUSCH is dispatched by a random access response or a DCI with a CRC scrambled by TC-RNTI,

[0452] In the case where the PUSCH is associated with a PRACH transmission in the first RO, if at least one symbol in a time slot, indicated by an index row of the resource allocation table, overlaps with a downlink symbol indicated by the first uplink / downlink configuration, or overlaps with a symbol of an SSB with an index provided by the SSB configuration, then the time slot is not one of the plurality of time slots (this time slot is not counted in the plurality of time slots for the PUSCH scheduled by the random access response or DCI).

[0453] In the case where the PUSCH is associated with a PRACH transmission in the second RO:

[0454] If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0455] In the case where the valid symbol type is a second time domain resource: if all symbols allocated for a PUSCH transmission opportunity in a time slot are second time domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and do not include SSB symbols, then the time slot is one of the plurality of time slots.

[0456] In some embodiments, the terminal device indicates / reports whether the UE supports second-type Msg3 repetition via a first parameter or information field in the UE capability information, or a combination of one or more of the following:

[0457] Used to indicate whether the terminal device supports the first type of Msg3 repeating (second) parameter / information field (e.g., pusch-RepetitionMsg3-r17);

[0458] (Third) parameter / information field used to indicate whether the terminal device is an SBFD-aware UE and / or whether it supports the basic characteristics / capabilities of SBFD-aware UE;

[0459] The (fourth) parameter / information field used to indicate whether the terminal device supports SBFD random access (in RRC_IDLE / INACTIVE / CONNECTED mode);

[0460] The (fifth) parameter / information field is used to indicate support for the repeating of the leading / PRACH in the second RO.

[0461] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The PUSCH receiving device 800 of this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0462] Furthermore, for simplicity, Figure 8 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0463] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0464] As can be seen from the above embodiments, network devices can operate in full-duplex mode (simultaneous reception and transmission), and terminal devices can also use corresponding resources to send and receive signals when the network devices are operating in full-duplex mode. This can improve uplink transmission capacity and coverage, reduce uplink transmission latency, and increase resource allocation flexibility and resource utilization.

[0465] Fifth aspect of the embodiment

[0466] This application also provides a communication system, which can be referred to FIG1. ​​The contents that are the same as those in the embodiments of the first to fourth aspects will not be repeated.

[0467] In some embodiments, the communication system 100 may include at least:

[0468] Network devices that transmit information for configuring (for one or more SCSs) a first frequency domain resource (UL subband) and / or for configuring (for one or more SCSs) a second frequency domain resource (DL subband); and receive, on the (activated) uplink BWP, a PUSCH scheduled or activated by a random access response (RAR) in a CBRA or CFRA (or in response to a PRACH in a CBRA or CFRA) or by downlink control information (DCI) scrambled by TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI.

[0469] The terminal device receives information for configuring the first frequency domain resource (UL subband) and / or information for configuring the second frequency domain resource (DL subband); and transmits a PUSCH scheduled or activated by the Random Access Response (RAR) or the Downlink Control Information (DCI) in the (activated) uplink BWP.

[0470] The third frequency domain resources (UL usable PRBs) of the (activated) uplink BWP include / are determined to be the intersection of the first frequency domain resources and the (activated) uplink BWP (configured for the SCS of the (activated) uplink BWP).

[0471] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

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

[0473] For example, processor 910 can be configured to execute a program to implement the method as described in the embodiments of the second aspect.

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

[0475] This application also provides a terminal device, but the application is not limited thereto and may also include other devices.

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

[0477] For example, processor 1010 can be configured to execute a program to implement the method as described in the embodiment of the first aspect.

[0478] As shown in Figure 10, the terminal device 1000 may further include: a communication module 1030, an input device 1040, a display 1050, and a power supply 1060. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the terminal device 1000 does not necessarily include all the components shown in Figure 10; these components are not essential. Furthermore, the terminal device 1000 may also include components not shown in Figure 10, which can be referred to in the prior art.

[0479] This application also provides a computer-readable program, wherein when the program is executed in a network device, the program causes the computer to perform the method described in the second aspect of the embodiment in the network device.

[0480] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer in a network device to perform the methods described in the second aspect of the embodiments.

[0481] This application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program causes the computer to perform the method described in the first aspect of the embodiment in the terminal device.

[0482] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer in a terminal device to perform the method described in the first aspect of the embodiments.

[0483] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. Logic components include, for example, field-programmable logic devices (FPGAs), microprocessors, and processors used in computers. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, and flash memory.

[0484] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0485] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

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

[0487] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0488] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0489] 1. A method for sending a PUSCH, comprising:

[0490] The terminal device receives information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0491] The terminal device sends a PUSCH scheduled or activated by a random access response (RAR) in (CBRA or CFRA) (or in response to a PRACH in CBRA or CFRA) or by (CRC scrambled by TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI) in the (activated) uplink BWP.

[0492] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

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

[0494] The network device sends information for configuring a first frequency domain resource (UL subband) (configured for one or more SCSs) and / or information for configuring a second frequency domain resource (DL subband) (configured for one or more SCSs); and

[0495] The network device receives a PUSCH scheduled or activated by a random access response (RAR) in a CBRA or CFRA (or in response to a PRACH in a CBRA or CFRA) or by downlink control information (DCI) scrambled by TC-RNTI, C-RNTI, MCS-RNTI, or CS-RNTI in a CRC-scrambled manner in the (activated) uplink BWP.

[0496] The PUSCH is repeated, and multiple time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

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

[0498] 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 as described in Appendix 2.

[0499] 5. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform the PUSCH transmission method as described in Appendix 1.

[0500] 6. A computer program product comprising at least a computer program that, when executed by a processor, causes a network device to perform the PUSCH receiving method as described in Appendix 2.

Claims

1. A PUSCH transmitting device, configured in a terminal device, the device comprising: A receiver that receives information for configuring a first frequency domain resource and / or information for configuring a second frequency domain resource; as well as A transmitter that transmits a PUSCH scheduled or activated by a random access response or downlink control information in an uplink BWP; wherein the PUSCH is repeated and a plurality of time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

2. The apparatus according to claim 1, wherein, The frequency domain resources of the PUSCH are related to at least one of the following: Initial uplink BWP; The third frequency domain resources of the initial uplink BWP; The uplink BWP; The third frequency domain resources of the uplink BWP; Frequency domain offset.

3. The apparatus according to claim 1, wherein, The valid symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the random access response or downlink control information that schedules the PUSCH.

4. The apparatus according to claim 1, wherein, Multiple time slots for PUSCH scheduled by random access response or downlink control information with cyclic redundancy check scrambled by TC-RNTI are determined based on whether the valid symbol type is a first time domain resource or a second time domain resource.

5. The apparatus according to claim 1, wherein, The frequency hopping offset indicated by the random access response or downlink control information and / or the starting frequency domain resources of the corresponding second hop of the PUSCH are related to at least one of the following: Initial uplink BWP; The third frequency domain resources of the initial uplink BWP; The uplink BWP; The third frequency domain resources of the uplink BWP; Frequency domain offset.

6. The apparatus according to claim 1, wherein, The time slot in which the PUSCH repeats is associated with the first time domain resource and / or the second time domain resource.

7. The apparatus according to claim 6, wherein, The time slot in which the PUSCH is repeated is related to a first time domain resource and / or a second time domain resource, including: determining multiple time slots for the PUSCH based on whether the valid symbol type is a first time domain resource or a second time domain resource.

8. The apparatus according to claim 7, wherein, The valid symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the random access response or DCI that schedules the PUSCH.

9. The apparatus according to claim 1, wherein, The terminal device only sends the PUSCH in the valid symbol type.

10. The apparatus according to claim 1, wherein, The multiple time slots are determined in the following manner: If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots. When the valid symbol type is a second time-domain resource: when the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI and associated with a PRACH transmission in a second RO, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and symbols that do not include SSBs, then the time slot is one of the plurality of time slots; when the PUSCH is scheduled by a DCI different from the DCI with a CRC scrambled by TC-RNTI, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and downlink symbols indicated by the second uplink / downlink configuration and symbols that do not include SSBs, then the time slot is one of the plurality of time slots.

11. The apparatus according to claim 1, wherein, When the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI, in the case that the PUSCH-associated PRACH transmission is in the first RO, the time slot in which the PUSCH repeats is independent of the first time domain resource and / or the second time domain resource; in the case that the PUSCH-associated PRACH transmission is in the second RO, the time slot in which the PUSCH repeats is related to the first time domain resource and / or the second time domain resource.

12. The apparatus according to claim 11, wherein, When the PUSCH is dispatched by a random access response or a DCI with a CRC scrambled by TC-RNTI, In the case where the PUSCH is associated with a PRACH transmission in the first RO, if at least one symbol in a time slot is indicated by an index row of the resource allocation table and overlaps with a downlink symbol indicated by the first uplink / downlink configuration, or overlaps with a symbol of an SSB with an index provided by the SSB configuration, then the time slot is not one of the plurality of time slots. In the case where the PUSCH is associated with a PRACH transmission in the second RO: If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots. In the case where the valid symbol type is a second time domain resource: if all symbols allocated for a PUSCH transmission opportunity in a time slot are second time domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and do not include SSB symbols, then the time slot is one of the plurality of time slots.

13. The apparatus according to claim 11, wherein, The terminal device indicates / reports that the UE supports the second type of Msg3 repetition through a first parameter or information field in the UE capability information, or a combination of one or more of the following: Used to indicate that the terminal device supports the first type of Msg3 repeating parameter / information field; Parameter / information fields used to indicate that the terminal device is an SBFD-aware UE and / or supports the basic characteristics / capabilities of SBFD-aware UE; Parameter / information fields used to indicate that the terminal device supports SBFD random access; The parameter / information field used to indicate support for leading / PRACH repetition in the second RO.

14. A PUSCH receiving device configured in a network device, the device comprising: A transmitter that transmits information for configuring a first frequency domain resource and / or information for configuring a second frequency domain resource; as well as A receiver that receives a PUSCH scheduled or activated by a random access response or downlink control information in an uplink BWP; wherein the PUSCH is repeated and a plurality of time slots for the PUSCH are determined at least according to a first uplink / downlink configuration and an SSB configuration.

15. The apparatus according to claim 14, wherein, The frequency domain resources of the PUSCH are related to at least one of the following: Initial uplink BWP; The third frequency domain resources of the initial uplink BWP; The uplink BWP; The third frequency domain resources of the uplink BWP; Frequency domain offset.

16. The apparatus according to claim 14, wherein, The number of bits used to indicate the frequency hopping offset included in the random access response or the downlink control information and / or the frequency hopping offset indicated by the random access response or the downlink control information and / or the starting frequency domain resources of the corresponding second hop of the PUSCH are related to at least one of the following: Initial uplink BWP; The third frequency domain resources of the initial uplink BWP; The uplink BWP; The third frequency domain resources of the uplink BWP.

17. The apparatus according to claim 14, wherein, The time slot in which the PUSCH repeats is associated with the first time domain resource and / or the second time domain resource.

18. The apparatus according to claim 17, wherein, The time slot in which the PUSCH is repeated is related to a first time domain resource and / or a second time domain resource, including: determining multiple time slots for the PUSCH based on whether the valid symbol type is a first time domain resource or a second time domain resource.

19. The apparatus according to claim 14, wherein, The multiple time slots are determined in the following manner: If the valid symbol type is a first time domain resource, and all symbols allocated for a PUSCH transmission opportunity in a time slot are first time domain resources and do not include SSB symbols, then the time slot is one of the plurality of time slots. When the valid symbol type is a second time-domain resource: when the PUSCH is scheduled by a random access response or a DCI with a CRC scrambled by TC-RNTI and associated with a PRACH transmission in a second RO, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and symbols that do not include SSBs, then the time slot is one of the plurality of time slots; when the PUSCH is scheduled by a DCI different from the DCI with a CRC scrambled by TC-RNTI, if the symbols allocated for a PUSCH transmission opportunity in a time slot are all second time-domain resources and do not include downlink symbols indicated by the first uplink / downlink configuration and downlink symbols indicated by the second uplink / downlink configuration and symbols that do not include SSBs, then the time slot is one of the plurality of time slots.

20. A communication system, comprising: A network device that sends information for configuring a first frequency domain resource and / or information for configuring a second frequency domain resource; And in the uplink BWP reception, the PUSCH is scheduled or activated by a random access response or downlink control information. The terminal device receives the information for configuring the first frequency domain resources and / or the information for configuring the second frequency domain resources; And transmit a PUSCH scheduled or activated by the random access response or the downlink control information in the uplink BWP; wherein the PUSCH is repeated and multiple time slots for the PUSCH are determined at least according to the first uplink / downlink configuration and the SSB configuration.

Images