Method and equipment for indicating channel access related information in carrier aggregation scene

Abstract

The embodiment of the invention relates to a method and equipment for indicating channel access related information in a carrier aggregation (CA) scene. According to some embodiments of the present disclosure, a UE may: receive, from a base station (BS), a downlink control information (DCI) format that schedules a plurality of physical uplink shared channels (PUSCHs) over a plurality of cells of the UE; determining a channel access type, a channel access priority class (CAPC) value, and a cyclic prefix extension (CPE) length for each of the plurality of PUSCHs; performing a channel access procedure on each of the plurality of PUSCHs according to the determined channel access type and a CAPC value; and in response to a corresponding channel access procedure for a first PUSCH of the plurality of PUSCHs being successful, transmitting a CPE having a duration equal to the determined CPE length of the first PUSCH and the first PUSCH to the BS.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to wireless communication techniques, and more particularly, to channel access related information indication in a carrier aggregation (CA) scenario. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. Wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources such as time, frequency, and power. Examples of wireless communication systems may include fourth generation (4G) systems such as long term evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems (which may also be referred to as new radio (NR) systems).

[0003] In a wireless communication system, a base station (BS) and a user equipment (UE) may communicate via a downlink (DL) channel and an uplink (UL) channel. For example, a UE may monitor a physical downlink control channel (PDCCH) in one or more search spaces. The PDCCH may carry downlink control information (DCI), which may schedule an uplink channel (e.g., a physical uplink shared channel (PUSCH)) or a downlink channel (e.g., a physical downlink shared channel (PDSCH)). The BS and the UE may communicate via a licensed spectrum or an unlicensed spectrum.

[0004] CA technology can be used in wireless communication systems to, for example, increase data rates. For example, CA technology may refer to aggregating spectrum resources (e.g., carriers or cells) from the same frequency band or different frequency bands. In a CA scenario, multiple cells may be configured for a UE and a DL or UL channel may be carried on one or more of the multiple cells.

[0005] There is a need to facilitate communications on unlicensed spectrum in CA scenarios. Summary of the invention

[0006] Some embodiments of the present disclosure provide a user equipment (UE). The UE may include: a transceiver; and a processor coupled to the transceiver. The processor may be configured to: receive a downlink control information (DCI) format for scheduling multiple physical uplink shared channels (PUSCHs) on multiple cells of the UE from a base station (BS); determine a channel access type, a channel access priority class (CAPC) value, and a cyclic prefix extension (CPE) length for each of the multiple PUSCHs; perform a channel access procedure for each of the multiple PUSCHs according to the determined channel access type, CAPC value, and CPE length; and in response to a corresponding channel access procedure for a first PUSCH among the multiple PUSCHs being successful, transmit a CPE having a duration equal to the determined CPE length of the first PUSCH and the first PUSCH to the BS.

[0007] In some embodiments of the present disclosure, the predefined CPE length is applied to all of the multiple PUSCHs.

[0008] In some embodiments of the present disclosure, the DCI format indicates at least one of the following: CPE length; CAPC value; a first indicator for indicating the channel access type, CAPC value and CPE length of each of the multiple PUSCHs; a second indicator for indicating the channel access type, CAPC value and CPE length of a predefined PUSCH among the multiple PUSCHs; or a third indicator for indicating a single channel access type, a single CAPC value and a single CPE length for all of the multiple PUSCHs.

[0009] In some embodiments of the present disclosure, if the DCI format indicates a CAPC value, then: the indicated CAPC value is a first CAPC value used by the BS to start a channel occupancy time (COT); the indicated CAPC value is a second CAPC value used by the UE to perform a channel access procedure for transmitting a PUSCH; or the indicated CAPC value includes the first CAPC value and the second CAPC value.

[0010] In some embodiments of the present disclosure, if more than one PUSCH among the plurality of PUSCHs is scheduled within a plurality of BS-initiated COTs, then the first CAPC value is a minimum value of CAPC values ​​used by the BS to initiate the plurality of BS-initiated COTs.

[0011] In some embodiments of the present disclosure, performing a channel access procedure on each of the plurality of PUSCHs according to the determined CAPC value includes performing a first type of channel access procedure on a PUSCH of the plurality of PUSCHs according to the second CAPC value.

[0012] In some embodiments of the present disclosure, if the DCI format indicates both a CAPC value and a CPE length, the CAPC value and the CPE length are indicated by separate fields in the DCI format or jointly indicated by a single field in the DCI format.

[0013] In some embodiments of the present disclosure, if the first, second or third indicator indicates a first type of channel access procedure for a PUSCH among the multiple PUSCHs, then the associated CAPC value indicated by the first, second or third indicator is a CAPC value used by the UE to transmit the PUSCH. In some embodiments of the present disclosure, if the first, second or third indicator indicates a second type of channel access procedure for a PUSCH among the multiple PUSCHs, then the associated CAPC value indicated by the first, second or third indicator is a CAPC value used by the BS to start a channel occupancy time (COT).

[0014] In some embodiments of the present disclosure, performing a channel access procedure on each of the plurality of PUSCHs according to the determined CAPC value includes performing a first type of channel access procedure on the PUSCH according to the associated CAPC value when the PUSCH is scheduled outside of a BS-initiated COT.

[0015] In some embodiments of the present disclosure, the first indicator indicates an entry of a table, and each entry of the table indicates a channel access type, a CAPC value, and a CPE length for each of the plurality of PUSCHs.

[0016] In some embodiments of the present disclosure, the second indicator indicates an entry of a table, and each entry of the table indicates a single channel access type, a single CAPC value, and a single CPE length of a predefined PUSCH in a PUSCH scheduled by a single DCI format.

[0017] In some embodiments of the present disclosure, the third indicator indicates an entry of a table, and each entry of the table indicates a single channel access type, a single CAPC value, and a single CPE length for all PUSCHs scheduled by a single DCI format.

[0018] In some embodiments of the present disclosure, the size of the first, second or third indicator in the DCI format depends on the number of entries in the table.

[0019] In some embodiments of the present disclosure, if a PUSCH among the multiple PUSCHs is scheduled within a BS-initiated channel occupancy time (COT), then the CAPC value used by the BS to initiate the BS-initiated COT is greater than or equal to the CAPC value of UL traffic data carried on the PUSCH.

[0020] Some embodiments of the present disclosure provide a BS. The BS may include: a transceiver; and a processor coupled to the transceiver. The processor may be configured to: transmit a DCI format for scheduling multiple PUSCHs on multiple cells of the UE to a UE; and receive the first PUSCH from the UE in response to a channel access procedure for a first PUSCH among the multiple PUSCHs being successful, wherein the channel access procedure for the first PUSCH is performed by the UE according to a channel access type and a channel access priority class (CAPC) value, and wherein a cyclic prefix extension (CPE) is transmitted by the UE before the first PUSCH.

[0021] In some embodiments of the present disclosure, the DCI format indicates at least one of the following: CPE length; CAPC value; a first indicator for indicating the channel access type, CAPC value and CPE length of each of the multiple PUSCHs; a second indicator for indicating the channel access type, CAPC value and CPE length of a predefined PUSCH among the multiple PUSCHs; or a third indicator for indicating a single channel access type, a single CAPC value and a single CPE length for all of the multiple PUSCHs.

[0022] In some embodiments of the present disclosure, if the DCI format indicates a CPE length, then: the indicated CPE length is applied to all of the multiple PUSCHs; the indicated CPE length is applied to all PUSCHs in the multiple PUSCHs that require a first type of channel access procedure and the predefined CPE length is applied to the remaining PUSCHs in the multiple PUSCHs; the indicated CPE length is applied to all PUSCHs in the multiple PUSCHs that require a second type of channel access procedure and the predefined CPE length is applied to the remaining PUSCHs in the multiple PUSCHs; the indicated CPE length is applied to the predefined PUSCHs in the multiple PUSCHs and the predefined CPE length is applied to the remaining PUSCHs in the multiple PUSCHs; or the indicated CPE length includes a first CPE length applied to all PUSCHs in the multiple PUSCHs that require a first type of channel access procedure and a second CPE length applied to all PUSCHs in the multiple PUSCHs that require a second type of channel access procedure.

[0023] In some embodiments of the present disclosure, the predefined CPE length is applied to all of the multiple PUSCHs.

[0024] In some embodiments of the present disclosure, if the DCI format indicates a CAPC value, then: the indicated CAPC value is a first CAPC value used by the BS to start COT; the indicated CAPC value is a second CAPC value used by the UE to perform a channel access procedure for transmitting PUSCH; or the indicated CAPC value includes the first CAPC value and the second CAPC value.

[0025] In some embodiments of the present disclosure, the processor is further configured to: attempt to receive the PUSCH if the first CAPC value is greater than or equal to the CAPC value of UL traffic data carried on the PUSCH of the plurality of PUSCHs requiring a second type of channel access procedure. In some embodiments of the present disclosure, the processor is further configured to: determine that the transmission of the PUSCH is terminated if the first CAPC value is less than the CAPC value of the UL traffic data carried on the PUSCH.

[0026] In some embodiments of the present disclosure, if more than one PUSCH among the plurality of PUSCHs is scheduled within a plurality of BS-initiated COTs, then the first CAPC value is a minimum value of CAPC values ​​used by the BS to initiate the plurality of BS-initiated COTs.

[0027] In some embodiments of the present disclosure, if a PUSCH among the plurality of PUSCHs requires a first type channel access procedure, then the first type channel access procedure is performed by the UE according to the second CAPC value for transmitting the PUSCH.

[0028] In some embodiments of the present disclosure, if the DCI format indicates both a CAPC value and a CPE length, the CAPC value and the CPE length are indicated by separate fields in the DCI format or jointly indicated by a single field in the DCI format.

[0029] In some embodiments of the present disclosure, if a PUSCH among the plurality of PUSCHs requires a first type channel access procedure, then a CAPC value of the PUSCH is determined according to UL traffic data carried on the PUSCH.

[0030] In some embodiments of the present disclosure, all of the multiple PUSCHs require a first type channel access procedure. In some embodiments of the present disclosure, if a PUSCH among the multiple PUSCHs is scheduled outside a COT initiated by a BS, then the UE requires a first type channel access procedure for transmitting the PUSCH. In some embodiments of the present disclosure, if the PUSCH is scheduled within a COT initiated by a BS, then the UE requires a second type channel access procedure for transmitting the PUSCH.

[0031] In some embodiments of the present disclosure, if the first, second or third indicator indicates a first type of channel access procedure for a PUSCH among the multiple PUSCHs, then the associated CAPC value indicated by the first, second or third indicator is a CAPC value used by the UE to transmit the PUSCH. In some embodiments of the present disclosure, if the first, second or third indicator indicates a second type of channel access procedure for a PUSCH among the multiple PUSCHs, then the associated CAPC value indicated by the first, second or third indicator is a CAPC value used by the BS to start COT.

[0032] In some embodiments of the present disclosure, if the PUSCH is scheduled outside the COT initiated by the BS, then the channel access procedure of the PUSCH is a first type channel access procedure performed according to the associated CAPC value.

[0033] In some embodiments of the present disclosure, the processor is further configured to: if the PUSCH is scheduled within a BS-initiated COT, attempt to receive the PUSCH when the associated CAPC value is greater than or equal to the CAPC value of the UL traffic data carried on the PUSCH. In some embodiments of the present disclosure, the processor is further configured to: if the PUSCH is scheduled within a BS-initiated COT, determine that the transmission of the PUSCH is terminated when the associated CAPC value is less than the CAPC value of the UL traffic data carried on the PUSCH.

[0034] In some embodiments of the present disclosure, the predefined CPE length is applied to all of the plurality of PUSCHs except the predefined PUSCH.

[0035] In some embodiments of the present disclosure, all of the plurality of PUSCHs except the predefined PUSCH require a first type channel access procedure.

[0036] In some embodiments of the present disclosure, for a corresponding PUSCH among the multiple PUSCHs other than the predefined PUSCH, if the corresponding PUSCH is scheduled outside the COT initiated by the BS, then the corresponding PUSCH requires a first type channel access procedure and a CAPC value of the corresponding PUSCH is determined according to UL traffic data carried on the corresponding PUSCH. In some embodiments of the present disclosure, for a corresponding PUSCH among the multiple PUSCHs other than the predefined PUSCH, if the corresponding PUSCH is scheduled within the COT initiated by the BS, then the corresponding PUSCH requires a second type channel access procedure.

[0037] In some embodiments of the present disclosure, the predefined PUSCH is: the first scheduled PUSCH among the multiple PUSCHs; the last scheduled PUSCH among the multiple PUSCHs; the PUSCH among the multiple PUSCHs scheduled on the cell with the lowest cell index among the multiple cells; the PUSCH among the multiple PUSCHs scheduled on the cell with the largest cell index among the multiple cells; the first scheduled PUSCH among the PUSCHs that require a first type of channel access procedure among the multiple PUSCHs; the last scheduled PUSCH among the PUSCHs that require a first type of channel access procedure among the multiple PUSCHs; the PUSCH among the multiple PUSCHs that require a first type of channel access procedure the PUSCH on the cell with the lowest cell index among the PUSCHs requiring the first type of channel access procedure among the multiple PUSCHs; the PUSCH on the cell with the largest cell index among the PUSCHs requiring the first type of channel access procedure among the multiple PUSCHs; the first scheduled PUSCH among the PUSCHs requiring the second type of channel access procedure among the multiple PUSCHs; the last scheduled PUSCH among the PUSCHs requiring the second type of channel access procedure among the multiple PUSCHs; the PUSCH on the cell with the lowest cell index among the PUSCHs requiring the second type of channel access procedure among the multiple PUSCHs; or the PUSCH on the cell with the largest cell index among the PUSCHs requiring the second type of channel access procedure among the multiple PUSCHs.

[0038] In some embodiments of the present disclosure, the first indicator indicates an entry of a table, and each entry of the table indicates a channel access type, a CAPC value, and a CPE length for each of the plurality of PUSCHs.

[0039] In some embodiments of the present disclosure, the second indicator indicates an entry of a table, and each entry of the table indicates a single channel access type, a single CAPC value, and a single CPE length of a predefined PUSCH in a PUSCH scheduled by a single DCI format.

[0040] In some embodiments of the present disclosure, the third indicator indicates an entry of a table, and each entry of the table indicates a single channel access type, a single CAPC value, and a single CPE length for all PUSCHs scheduled by a single DCI format.

[0041] In some embodiments of the present disclosure, the size of the first, second or third indicator in the DCI format depends on the number of entries in the table.

[0042] In some embodiments of the present disclosure, if a PUSCH among the multiple PUSCHs is scheduled within a BS-initiated COT, then the CAPC value used by the BS to initiate the BS-initiated COT is greater than or equal to a CAPC value of UL traffic data carried on the PUSCH.

[0043] Some embodiments of the present disclosure provide a method performed by a UE. The method may include: receiving a DCI format for scheduling multiple PUSCHs on multiple cells of the UE from a BS; determining a channel access type, a CAPC value, and a CPE length for each of the multiple PUSCHs; performing a channel access procedure for each of the multiple PUSCHs according to the determined channel access type, CAPC value, and CPE length; and in response to a corresponding channel access procedure for a first PUSCH among the multiple PUSCHs being successful, transmitting a CPE having a duration equal to the determined CPE length of the first PUSCH and the first PUSCH to the BS.

[0044] Some embodiments of the present disclosure provide a method performed by a BS. The method may include: transmitting a DCI format for scheduling multiple PUSCHs on multiple cells of the UE to a UE; and receiving the first PUSCH from the UE in response to a channel access procedure for a first PUSCH among the multiple PUSCHs being successful, wherein the channel access procedure for the first PUSCH is performed by the UE according to a channel access type and a channel access priority class (CAPC) value, and wherein a cyclic prefix extension (CPE) is transmitted by the UE before the first PUSCH.

[0045] Some embodiments of the present disclosure provide a device. According to some embodiments of the present disclosure, the device may include: at least one non-transitory computer-readable medium having computer-executable instructions stored thereon; at least one receiving circuit system; at least one transmitting circuit system; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuit system, and the at least one transmitting circuit system, wherein the at least one non-transitory computer-readable medium and the computer-executable instructions may be configured to cause the device to perform the method according to some embodiments of the present disclosure with the at least one processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented by reference to specific embodiments of the present disclosure illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present disclosure and therefore should not be considered to limit its scope.

[0047] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present disclosure;

[0048] Figure 2 and 3 A schematic diagram illustrating a DCI format for scheduling multiple transmissions according to some embodiments of the present disclosure;

[0049] Figure 4 A schematic diagram illustrating a DCI format for scheduling multiple PUSCHs on an unlicensed spectrum according to some embodiments of the present disclosure;

[0050] Figure 5 and 6 A flowchart illustrating an exemplary wireless communication procedure according to some embodiments of the present disclosure; and

[0051] Figure 7 A block diagram illustrating an exemplary apparatus according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0052] The detailed description of the drawings is intended as a description of the preferred embodiments of the present disclosure and is not intended to represent the only form in which the present disclosure can be practiced. It should be understood that the same or equivalent functions can be achieved by different embodiments that are intended to be encompassed within the spirit and scope of the present disclosure.

[0053] Reference will now be made in detail to some embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3rd Generation Partnership Project (3GPP) 5G (NR), 3GPP Long Term Evolution (LTE) Release 8, etc.). It is expected that, as network architectures and new service scenarios evolve, all embodiments in the present disclosure are also applicable to similar technical issues; and in addition, the terms cited in the present disclosure may be changed, which should not affect the principles of the present disclosure.

[0054] Figure 1 A schematic diagram illustrating a wireless communication system 100 according to some embodiments of the present disclosure.

[0055] like Figure 1 As shown in FIG. 1 , wireless communication system 100 may include some UEs 101 (eg, UE 101a and UE 101b) and base stations (eg, BS 102). Figure 1 A specific number of UEs 101 and BSs 102 are depicted in FIG. 1 , but it is contemplated that any number of UEs and BSs may be included in the wireless communication system 100 .

[0056] UE 101 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (such as a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a car computer, a network device (such as a router, a switch and a modem), or the like. According to some embodiments of the present disclosure, UE 101 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identification module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals on a wireless network. In some embodiments of the present disclosure, UE 101 includes a wearable device, such as a smart watch, a fitness bracelet, an optical head-mounted display, or the like. In addition, UE 101 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal or a device or described using other terms used in the art. UE 101 may communicate with BS102 via an uplink (UL) communication signal.

[0057] BS 102 may be distributed throughout a geographic area. In certain embodiments of the present disclosure, BS 102 may also be referred to as an access point, access terminal, base, base unit, macro cell, Node B, evolved Node B (eNB), gNB, home Node B, relay node or device or described using other terms used in the art. BS 102 is typically part of a radio access network that may include one or more controllers communicatively coupled to one or more corresponding BS 102. BS 102 may communicate with UE 101 via downlink (DL) communication signals.

[0058] The wireless communication system 100 may be compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a network based on time division multiple access (TDMA), a network based on code division multiple access (CDMA), a network based on orthogonal frequency division multiple access (OFDMA), an LTE network, a network based on 3GPP, a 3GPP 5G network, a satellite communication network, a high altitude platform network, and / or other communication networks.

[0059] In some embodiments of the present disclosure, the wireless communication system 100 is compatible with 5G NR of the 3GPP protocol. For example, the BS 102 may transmit data using an orthogonal frequency division multiple access (OFDM) modulation scheme on the DL, and the UE 101 may transmit data using a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-S-OFDM) or cyclic prefix-OFDM (CP-OFDM) scheme on the UL. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocols, such as WiMAX and other protocols.

[0060] In some embodiments of the present disclosure, BS 102 and UE 101 may communicate using other communication protocols, such as the IEEE 802.11 series of wireless communication protocols. In addition, in some embodiments of the present disclosure, BS 102 and UE 101 may communicate via licensed spectrum, while in some other embodiments, BS 102 and UE 101 may communicate via unlicensed spectrum. The present disclosure is not intended to be limited to implementing any particular wireless communication system architecture or protocol.

[0061] Communication technologies (such as NR) can support a wide range of spectrum in different frequency ranges. For example, in the 5G advanced market, the availability of spectrum is expected to increase, which may be due to the re-division of frequency bands originally used for previous generation cellular networks. For example, for some low-frequency bands in frequency range 1 (FR1) (such as 410 MHz to 7125 MHz), the available spectrum bands tend to be more fragmented and dispersed with narrower bandwidths. In addition, for frequency bands in frequency range 2 (such as 24250 MHz to 52600 MHz) and some frequency bands in FR1, the available spectrum may be wider, making intra-band multi-carrier operation necessary.

[0062] In order to meet different spectrum demands, it is important to ensure that these fragmented or dispersed spectrum bands or spectrum with wider bandwidth are utilized in a more spectrally and power efficient and flexible manner, thereby providing higher throughput and appropriate coverage in the network.

[0063] For example, one motivation is to improve the spectrum / power efficiency and flexibility of scheduling data on multiple cells including intra-band cells and inter-band cells. In some instances, the scheduling mechanism may only allow scheduling of a single PUSCH or PDSCH on a single cell according to the scheduling DCI. As more dispersed spectrum bands or wider bandwidth spectrum become available, it is desirable to allow multiple cells to be scheduled simultaneously.

[0064] A communication system (e.g., NR) may be designed to support up to 16 component carriers (CCs) in the case of carrier aggregation (CA) or up to 32 CCs in the case of dual connectivity (DC). In some embodiments of the present application, in the case of CA, one DCI format may schedule up to one carrier through cross-carrier scheduling or self-scheduling. When the number of carriers configured for a UE is large, a large amount of signaling overhead is required for the PDCCH to schedule the PDSCH or PUSCH. In order to reduce the signaling overhead, it would be beneficial to schedule multiple PDSCHs or PUSCHs on multiple carriers configured for the UE using a single DCI format, which is referred to as multi-cell or multi-carrier scheduling in the context of the present disclosure. At the same time, the trade-off between signaling overhead reduction and scheduling restrictions must be considered.

[0065] In the context of the present disclosure, for simplicity, a DCI format that schedules multiple PUSCHs on multiple cells is referred to as DCI format 0_X, and a DCI format that schedules multiple PDSCHs on multiple cells is referred to as DCI format 1_X. In some embodiments of the present disclosure, DCI format 0_X / 1_X may schedule a single PDSCH per cell.

[0066] Figure 2 A diagram illustrating a DCI format for scheduling multiple transmissions according to some embodiments of the present disclosure.

[0067] In some embodiments of the present disclosure, multiple CCs (for example, including but not limited to Figure 2 231 to 234 in the UE). It should be understood that the subcarrier spacing (SCS) of the carriers configured for the UE may be the same or different. Each of the multiple CCs may correspond to a corresponding cell (e.g., a serving cell) or carrier of the UE. Each cell (serving cell) may be associated with a (serving) cell index.

[0068] In some embodiments of the present disclosure, instead of using separate DCI formats to schedule multiple transmissions on multiple carriers respectively, the BS may transmit a single DCI format to schedule multiple transmissions on multiple carriers. Figure 2 , DCI format 211 may schedule transmissions 221 - 224 on CCs 231 - 234, with each CC carrying a single transmission.

[0069] In some examples, transmissions 221-224 may be uplink transmissions, such as uplink physical data channels, such as PUSCH. In some examples, transmissions 221-224 may be downlink transmissions, such as downlink physical data channels, such as PDSCH.

[0070] exist Figure 2 In the embodiment of the present invention, the carrier on which the DCI format 211 is detected (i.e., CC 231) may carry one of the scheduled transmissions (e.g., transmission 221). This may be referred to as self-scheduling. The other transmissions in the scheduled transmissions (e.g., transmissions 222 to 224) are scheduled on a different carrier than the carrier on which the DCI format 211 is detected (i.e., CC 231). This may be referred to as cross-carrier scheduling.

[0071] Despite Figure 2 In the embodiment, the DCI format 211 schedules multiple transmissions via both self-scheduling and cross-carrier scheduling, but it should be understood that the DCI format may schedule multiple transmissions via only cross-carrier scheduling. Figure 3 This example is shown. It should also be understood that in some other embodiments of the present disclosure, a carrier (eg, CC) scheduled by a DCI format may carry more than one transmission (eg, PDSCH or PUSCH).

[0072] Figure 3 A diagram illustrating a DCI format for scheduling multiple transmissions according to some embodiments of the present disclosure.

[0073] In some embodiments of the present disclosure, multiple CCs (for example, including but not limited to Figure 3331 to 335 in the UE). It should be understood that the subcarrier spacing (SCS) of the carriers configured for the UE may be the same or different. Each of the multiple CCs may correspond to a corresponding cell (e.g., a serving cell) or carrier of the UE. Each cell (serving cell) may be associated with a (serving) cell index.

[0074] like Figure 3 , DCI format 311 may be transmitted on CC 331 and transmissions 321-324 may be scheduled on CCs 332-335, with each CC carrying a single transmission. In some examples, transmissions 321-324 may be uplink transmissions, such as an uplink physical data channel, such as a PUSCH. In some examples, transmissions 321-324 may be downlink transmissions, such as a downlink physical data channel, such as a PDSCH.

[0075] The payload size of a single DCI may be limited, for example, a maximum payload size of 140 bits may be required. When a single DCI is used to schedule multiple cells, the payload size of the DCI may easily exceed the payload size limit (e.g., 140 bits) due to the fact that many fields in the DCI are cell-specific (including, for example, but not limited to, modulation and coding scheme (MCS), hybrid automatic repeat request (HARQ) process number, new data indicator (NDI), redundancy version (RV), and / or frequency domain resource assignment (FDRA)). Therefore, it may be necessary to reduce the payload size to ensure that the total payload size of the DCI does not exceed the payload size limit (e.g., 140 bits).

[0076] In some embodiments of the present disclosure, for unlicensed spectrum operation, the DCI format needs to indicate channel access related information. For example, a DCI format (e.g., DCI format 0_1) may include a field indicating the channel access type, CAPC value, and CPE length of a transmission (e.g., PUSCH) scheduled by the DCI format (hereinafter referred to as "channel access information related field"). For example, before transmitting the scheduled PUSCH, the UE needs to perform a channel access procedure (also known as a listen-before-talk (LBT) test or procedure) according to the indicated channel access type and CAPC, and in response to a successful channel access procedure, the UE may transmit a CPE with a duration equal to the indicated CPE length and the scheduled PUSCH.

[0077] The channel access type may indicate a first type of channel access procedure (e.g., a Type 1 UL channel access procedure specified in the 3GPP specification) and a second type of channel access procedure (e.g., a Type 2 UL channel access procedure specified in the 3GPP specification). In some examples, depending on the sensing time, the second type of channel access procedure may include more than one channel access procedure, such as a Type 2A UL channel access procedure, a Type 2B UL channel access procedure, and a Type 2C UL channel access procedure specified in the 3GPP specification.

[0078] In some embodiments of the present disclosure, the channel access information related field may indicate an entry in a table that may be configured or predefined for the UE. The table may include multiple entries, each indicating a channel access type, a CAPC, and a CPE length. As an example, the table may be defined as follows.

[0079] Table A

[0080]

[0081]

[0082] Since 44 entries are defined in the above exemplary table, the DCI format contains a maximum of 6 bits for indicating the channel access related information for scheduling the PUSCH.

[0083] In the case of multi-cell scheduling, considering that the scheduled PUSCHs on different cells may have different settings, it may be desirable to indicate the dedicated channel access information related fields for each scheduled PUSCH to ensure scheduling flexibility. However, in the example of Table A, assuming that a maximum of 4 PUSCHs can be scheduled by a single DCI, a maximum of 24 (i.e., 6×4) bits will be required in the multi-cell scheduling DCI. This solution therefore results in too much payload being included in the DCI and will result in the total payload size of the DCI easily exceeding the payload size limit (e.g., 140 bits).

[0084] Figure 4 A schematic diagram illustrating a DCI format for scheduling multiple PUSCHs on an unlicensed spectrum according to some embodiments of the present disclosure.

[0085] In some embodiments of the present disclosure, multiple CCs (for example, including but not limited to Figure 4 It should be understood that the subcarrier spacing (SCS) of the carriers configured for the UE may be the same or different. Each of the multiple CCs may correspond to a respective cell (e.g., a serving cell) or carrier of the UE. Each cell (serving cell) may be associated with a (serving) cell index. Figure 4, DCI format 411 may be transmitted on CC 431 and PUSCH 421 - 424 may be scheduled on CCs 432 - 435 , with each CC carrying a single PUSCH.

[0086] The PUSCH 421 may be located within the BS-initiated COT 442 and separated by a gap between a DL burst and a UL burst, and thus the UE requires a second type of channel access procedure (e.g., a Type 2A channel access procedure) to transmit the PUSCH 421. The PUSCH 422 may be located within the BS-initiated COT 443 and follow another UL transmission within a UL burst, and thus the UE requires a second type of channel access procedure (e.g., a Type 2B or Type 2C channel access procedure) to transmit the PUSCH 422. The PUSCH 423 may be located within the UE-initiated COT 444 and follow another UL transmission. Therefore, if the channel access procedure for UL transmission before PUSCH 423 fails, the UE needs a first type of channel access procedure (e.g., Type 1 channel access procedure) to transmit PUSCH 423; or if the channel access procedure for UL transmission before PUSCH 423 succeeds and PUSCH 423 is within the UE-initiated COT 444, the UE needs a second type of channel access procedure (e.g., Type 2A, 2B, or 2C channel access procedure) or no channel access procedure (i.e., no LBT) to transmit PUSCH 423. PUSCH 424 may be located within the UE-initiated COT 445 and does not follow UL transmission, and therefore the UE needs a first type of channel access procedure (e.g., Type 1 channel access procedure) to transmit PUSCH 424.

[0087] exist Figure 4 In the example of , if separate channel access information related fields (each of which corresponds to one PUSCH) are included in the DCI format 411, it may result in too much payload being included in the DCI format and will cause the total payload size of the DCI format to exceed the payload size limit, because each field requires up to, for example, 6 bits in the DCI format. Therefore, the trade-off between payload size overhead reduction and scheduling constraints must be considered.

[0088] Embodiments of the present disclosure provide a solution for indicating channel access related information in the case of multi-cell scheduling. The disclosed solution avoids excessive payload size overhead in the multi-cell scheduling DCI format. More details about the embodiments of the present disclosure will be described below in conjunction with the accompanying drawings.

[0089] In some embodiments of the present disclosure, when a DCI format schedules multiple PUSCHs on multiple cells, the DCI format may only indicate the CPE length of the PUSCHs co-scheduled by the DCI format. Neither the channel access type nor the CAPC value is indicated in the DCI format.

[0090] In the context of the present disclosure, the CPE length of PUSCH, applying the CPE length to PUSCH or other similar expressions may indicate that before PUSCH is transmitted by the UE, the UE may transmit a CPE with a duration equal to the CPE length. However, from the perspective of the BS, it can only receive PUSCH.

[0091] In some embodiments, the CAPC value used to perform the first channel access procedure for a PUSCH scheduled by a DCI format may be associated with the UL traffic data carried on the PUSCH. For example, for a PUSCH scheduled by a DCI format and requiring a first channel access procedure, the UE may determine the corresponding CAPC value based on the UL traffic data transmitted on the PUSCH. If the PUSCH is scheduled or requires or may use a second channel access procedure within a BS-initiated COT, the BS shall ensure that the CAPC value used by the BS to initiate the COT is greater than or equal to the CAPC value associated with the UL traffic data carried on the PUSCH.

[0092] In some embodiments of the present disclosure, all multiple PUSCHs require the first type channel access procedure. That is, the first type channel access procedure is mandatory for transmitting multiple PUSCHs on multiple cells.

[0093] In some other embodiments of the present disclosure, for each of a plurality of co-scheduled PUSCHs, a channel access type of the corresponding PUSCH may be determined based on whether the corresponding PUSCH is scheduled within or outside the BS-initiated COT.

[0094] For example, for a specific PUSCH among a plurality of co-scheduled PUSCHs, the UE may determine whether the PUSCH is scheduled within a BS-initiated COT or outside a BS-initiated COT. In response to determining that the PUSCH is scheduled outside a BS-initiated COT, it is determined that the PUSCH requires a first type of channel access procedure. Otherwise, in response to determining that the PUSCH is scheduled within a BS-initiated COT, it is determined that the PUSCH requires or may use a second type of channel access procedure.

[0095] For example, the UE may receive a DCI format (e.g., DCI format 2_0) indicating a COT duration (e.g., a remaining COT duration indicator). Based on the remaining COT duration indicator and the time domain resource allocation information indicated in the DCI format for scheduling multiple PUSCHs, the UE may determine whether the scheduled PUSCH is located within the BS-initiated COT or outside the BS-initiated COT. In response to determining that the scheduled PUSCH is located outside the BS-initiated COT, the UE may perform a first type of channel access procedure before transmitting the scheduled PUSCH. Otherwise, in response to determining that the scheduled PUSCH is located within the BS-initiated COT, the UE may perform a second type of channel access procedure before transmitting the scheduled PUSCH.

[0096] In addition, if the scheduled PUSCH is positioned within the COT initiated by the BS, the UE may further determine the duration of the gap between the scheduled PUSCH and the DL or UL transmission (if any) immediately preceding the scheduled PUSCH. If the duration of the gap is greater than 25 μs, the UE may perform a Type 2A channel access procedure before transmitting the scheduled PUSCH. If the duration of the gap is equal to 16 μs, the UE may perform a Type 2B channel access procedure before transmitting the scheduled PUSCH. If the duration of the gap is less than 16 μs, the UE may perform a Type 2C channel access procedure before transmitting the scheduled PUSCH.

[0097] The CPU length indication in the DCI format may be implemented in various ways.

[0098] For example, in some embodiments of the present disclosure, the CPE length indicated in the DCI format for scheduling multiple PUSCHs may be applied to all multiple PUSCHs. For example, a single CPE length may be indicated in a multi-cell scheduling DCI format and may be applied to all co-scheduled PUSCHs. In other words, all PUSCHs co-scheduled by the same DCI format have the same CPE length.

[0099] In some embodiments of the present disclosure, the indicated CPE length may be applied to all PUSCHs that require a first type of channel access procedure among multiple PUSCHs co-scheduled by a DCI format. For example, a single CPE length may be indicated in a multi-cell scheduling DCI format and may be applied to all co-scheduled PUSCHs that will perform a first type of channel access procedure. That is, for a co-scheduled PUSCH that requires a first type of channel access procedure, the indicated CPE length is used (if the corresponding first type of channel access procedure is successful). A predefined CPE length (e.g., "0") may be applied to the remaining PUSCHs among multiple PUSCHs. For example, for a co-scheduled PUSCH that requires or may use a second type of channel access procedure, a predefined CPE is used (if the corresponding second type of channel access procedure is successful).

[0100] In some embodiments of the present disclosure, the indicated CPE length may be applied to all PUSCHs in a plurality of PUSCHs co-scheduled by a DCI format that require or may use a second type of channel access procedure. For example, a single CPE length may be indicated in a multi-cell scheduling DCI format and may be applied to all co-scheduled PUSCHs that will perform a second type of channel access procedure. That is, for a co-scheduled PUSCH that requires or may use a second type of channel access procedure, the indicated CPE length is used (if the corresponding second type of channel access procedure is successful). A predefined CPE length (e.g., "0") may be applied to the remaining PUSCHs in a plurality of PUSCHs. For example, for a co-scheduled PUSCH that requires a first type of channel access procedure, a predefined CPE is used (if the corresponding first type of channel access procedure is successful).

[0101] In some embodiments of the present disclosure, the indicated CPE length may be applied to a predefined PUSCH among a plurality of PUSCHs co-scheduled by a DCI format. The predefined CPE length (eg, "0") may be applied to the remaining PUSCHs among the plurality of PUSCHs.

[0102] For example, the predefined PUSCH may be: the first scheduled PUSCH among multiple PUSCHs scheduled by the DCI format; the last scheduled PUSCH among multiple PUSCHs; the PUSCH among multiple PUSCHs scheduled on a cell with a lowest cell index among multiple cells scheduled by the DCI format; the PUSCH among multiple PUSCHs scheduled on a cell with a maximum cell index among multiple cells; the first scheduled PUSCH among multiple PUSCHs that require a first type of channel access procedure; the last scheduled PUSCH among multiple PUSCHs that require a first type of channel access procedure; the first scheduled PUSCH among multiple PUSCHs that require a first type of channel access procedure The PUSCH on the cell with the lowest cell index among the scheduled PUSCHs; the PUSCH on the cell with the largest cell index among the PUSCHs that require the first type of channel access procedure among multiple PUSCHs; the first scheduled PUSCH among the PUSCHs that require the second type of channel access procedure among multiple PUSCHs; the last scheduled PUSCH among the PUSCHs that require the second type of channel access procedure among multiple PUSCHs; the PUSCH on the cell with the lowest cell index among the PUSCHs that require the second type of channel access procedure among multiple PUSCHs; or the PUSCH on the cell with the largest cell index among the PUSCHs that require the second type of channel access procedure among multiple PUSCHs.

[0103] In some embodiments of the present disclosure, an indication of a CPE length may include two CPE lengths, one of which may be applied to all PUSCHs in a plurality of PUSCHs co-scheduled by a DCI format that require a first type of channel access procedure, and the other may be applied to all PUSCHs in a plurality of PUSCHs that require a second type of channel access procedure. For example, a DCI format may include two separate CPE length fields. One of the CPE length fields may be applied to all co-scheduled PUSCHs that have performed a first type of channel access procedure, i.e., to those co-scheduled PUSCHs that require a first type of channel access procedure; and the other field may be applied to all co-scheduled PUSCHs that have performed a second type of channel access procedure, i.e., to those co-scheduled PUSCHs that require or may use a second type of channel access procedure.

[0104] In some embodiments of the present disclosure, in addition to the channel access type and the CAPC value, the CPE length may not be indicated in the DCI format for scheduling multiple PUSCHs. The predefined CPE length may be applied to all multiple co-scheduled PUSCHs. For example, a CPE length of "0" may be used to transmit each of the co-scheduled PUSCHs.

[0105] In some embodiments of the present disclosure, when a DCI format schedules multiple PUSCHs on multiple cells, the DCI format may indicate the CAPC value or both the CPE length and the CAPC value of the PUSCHs co-scheduled by the DCI format. The channel access type may not be indicated in the DCI format.

[0106] If both the CPE length and the CAPC value are indicated in the DCI format, the CPE length and the CAPC value may be indicated separately or jointly. For example, the CAPC value and the CPE length may be indicated by separate fields in the DCI format or jointly indicated by a single field in the DCI format. In the case of joint indication, the single field in the DCI format may point to an entry of a table, where each entry of the table indicates both the CAPC value and the CPE length. The table may be configured by the BS (e.g., via radio resource control (RRC) signaling) or predefined. If the CPE length is not indicated in the DCI format, the predefined CPE length (e.g., "0") may be applied to all multiple PUSCHs scheduled by the DCI format.

[0107] In some embodiments of the present disclosure, all multiple PUSCHs require the first type channel access procedure. That is, the first type channel access procedure is mandatory for transmitting multiple PUSCHs scheduled by the DCI format on multiple cells.

[0108] In some other embodiments of the present disclosure, for each of a plurality of co-scheduled PUSCHs, a channel access type of the corresponding PUSCH may be determined based on whether the corresponding PUSCH is scheduled within or outside the BS-initiated COT.

[0109] For example, for a specific PUSCH among a plurality of co-scheduled PUSCHs, the UE may determine whether the PUSCH is scheduled within a BS-initiated COT or outside a BS-initiated COT. In response to determining that the PUSCH is scheduled outside a BS-initiated COT, it is determined that the PUSCH requires a first type of channel access procedure. Otherwise, in response to determining that the PUSCH is scheduled within a BS-initiated COT, it is determined that the PUSCH requires or may use a second type of channel access procedure.

[0110] For example, as described above, based on the remaining COT duration indicator in DCI format 2_0 and the time domain resource allocation information indicated in the DCI format for scheduling multiple PUSCHs, the UE may determine whether the scheduled PUSCH is located within the BS-initiated COT or outside the BS-initiated COT. If the scheduled PUSCH is located within the BS-initiated COT, the UE may further determine the duration of the gap between the scheduled PUSCH and the DL or UL transmission (if any) immediately before the scheduled PUSCH. The UE may determine whether to perform a first type of channel access procedure (e.g., a type 1 channel access procedure) or a second type of channel access procedure (e.g., a type 2 channel access procedure, such as a type 2A, 2B, or 2C channel access procedure) before transmitting the scheduled PUSCH.

[0111] The CAPC value indication in the DCI format may be implemented in various ways.

[0112] For example, in some embodiments of the present disclosure, the CAPC value indicated in the DCI format for scheduling multiple PUSCHs (simply represented as CAPC#1) may be the CAPC value used by the BS to activate COT.

[0113] For example, a single CAPC value may be indicated in a multi-cell scheduling DCI format and may be the CAPC value used by the BS to initiate the COT. In some embodiments, if more than one of the multiple PUSCHs scheduled by the DCI format is scheduled within multiple BS-initiated COTs, then CAPC#1 may be the minimum value of the CAPC values ​​used by the BS to initiate the multiple BS-initiated COTs.

[0114] In some embodiments, for a PUSCH scheduled by a DCI format that requires or may use a second type of channel access procedure (e.g., when the PUSCH is scheduled within a COT initiated by the BS), the UE may transmit the scheduled PUSCH in response to CAPC#1 being greater than or equal to the CAPC value associated with the UL traffic data carried on the scheduled PUSCH (also when the second type of channel access procedure for the scheduled PUSCH is successful). Otherwise, in response to CAPC#1 being less than the CAPC value associated with the uplink traffic data carried on the scheduled PUSCH, the UE may terminate the transmission of the scheduled PUSC.

[0115] In some embodiments of the present disclosure, the CAPC value (simply represented as CAPC#2) indicated in the DCI format for scheduling multiple PUSCHs may be the CAPC value used by the UE to perform the channel access procedure. For example, a single CAPC value may be indicated in the multi-cell scheduling DCI format and may be the CAPC value used by the UE to transmit the co-scheduled PUSCH.

[0116] In some embodiments, for a PUSCH scheduled by a DCI format that requires a first type channel access procedure (e.g., when the PUSCH is scheduled outside the COT initiated by the BS), the UE may perform the first type channel access procedure on the scheduled PUSCH according to CAPC#2 before transmitting the scheduled PUSCH. If more than one PUSCH requires a first type channel access procedure (e.g., when more than one PUSCH is scheduled outside the COT initiated by the BS), the UE may perform the first type channel access procedure on each of the more than one PUSCH according to CAPC#2.

[0117] If the PUSCH scheduled by the DCI format requires or can use the second type of channel access procedure (for example, when the PUSCH is scheduled within a COT initiated by the BS), then the BS should ensure that the CAPC value used by the BS to initiate the COT is greater than or equal to the CAPC value associated with the UL traffic data carried on the scheduled PUSCH.

[0118] In some embodiments of the present disclosure, the CAPC value indicated in the DCI format for scheduling multiple PUSCHs may include two separate CAPC values. One CAPC value may be a CAPC value used by the BS to start COT, such as CAPC#1; and the other CAPC value may be a CAPC value used by the UE to perform a channel access procedure, such as CAPC#2.

[0119] The above description about CAPC#1 and CAPC#2 is applicable here. For example, the DCI format may indicate the CAPC value (e.g., CAPC#1) used by the BS when the COT is activated, so that the UE can determine whether the second type of channel access procedure is applicable to those co-scheduled PUSCHs located within the COT activated by the BS (i.e., the second type of channel access procedure can be used). The DCI format may further indicate the CAPC value (e.g., CAPC#2) used by the UE to transmit all co-scheduled PUSCHs for which the first type of channel access procedure is performed, i.e., for those co-scheduled PUSCHs that require the first type of channel access procedure.

[0120] For example, if more than one PUSCH among the multiple PUSCHs scheduled by the DCI format is scheduled within the COTs initiated by the multiple BSs, then CAPC#1 may be the minimum value of the CAPC values ​​used by the BS to initiate the multiple BS-initiated COTs. For example, if more than one PUSCH requires a first type channel access procedure (e.g., when more than one PUSCH is scheduled outside the COT initiated by the BS), then the UE may perform the first type channel access procedure for each of the more than one PUSCHs according to CAPC#2.

[0121] The aforementioned embodiments for implementing the CPE length indication in the DCI format may be applicable here. For example, the CPE length indicated in the DCI format for scheduling multiple PUSCHs may be applied to all multiple PUSCHs. For example, the indicated CPE length may be applied to all PUSCHs in the multiple PUSCHs that require the first type of channel access procedure and the predefined CPE length may be applied to the remaining PUSCHs in the multiple PUSCHs. For example, the indicated CPE length may be applied to all PUSCHs in the multiple PUSCHs that require or can use the second type of channel access procedure and the predefined CPE length may be applied to the remaining PUSCHs in the multiple PUSCHs. For example, the indicated CPE length may be applied to the predefined PUSCHs in the multiple PUSCHs and the predefined CPE length may be applied to the remaining PUSCHs in the multiple PUSCHs. For example, the indicated CPE length may include two CPE lengths, one of which may be applied to all PUSCHs in the multiple PUSCHs that require the first type of channel access procedure, and the other CPE length will be applied to all PUSCHs in the multiple PUSCHs that require or can use the second type of channel access procedure. The aforementioned definition of predefined PUSCH is applicable here.

[0122] In some embodiments of the present disclosure, when a DCI format schedules multiple PUSCHs on multiple cells, the DCI format may indicate the channel access type, CAPC value, and CPE length of each of the multiple PUSCHs. For example, the DCI format may include an indicator or field for indicating the above information, which is referred to as indicator #1 hereinafter.

[0123] In some embodiments of the present disclosure, indicator #1 may indicate an entry (or row) of a table, and each entry of the table may indicate a channel access type, a CAPC value, and a CPE length for each of a plurality of PUSCHs. The table (simply denoted as table #1) may be configured by the BS to the UE (e.g., via RRC) or may be predefined. The size of indicator #1 (e.g., the number of bits required for indicator #1) may depend on the number of entries in table #1.

[0124] In some embodiments of the present disclosure, each entry of Table #1 may indicate one or more channel access information related indicators for jointly indicating the channel access type, CAPC value, and CPE length of the PUSCH co-scheduled by the multi-cell scheduling DCI. For example, assuming that N represents the maximum number of cells co-scheduled by a single multi-cell scheduling DCI, each entry of Table #1 may include N channel access information related indicators, each of which corresponds to one of the co-scheduled PUSCHs.

[0125] For example, each channel access information related indicator may indicate a combination of a channel access type, a CAPC value, and a CPE length from another table defined for uplink channel access procedures that may be configured by the BS to the UE (e.g., via RRC) or predefined, such as Table A. For example, this table may be configured via higher layer parameters ul-AccessConfigListDCI-0-1 or ul-AccessConfigListDCI-0-X.

[0126] Assuming N=4, exemplary table #1 is shown below:

[0127] Exemplary Table #1: Maximum 4 indicators in one entry (corresponding to 4 PUSCHs)

[0128]

[0129] In some examples, in the above exemplary table #1, each of channel access information related indicator 1, channel access information related indicator 2, channel access information related indicator 3, and channel access information related 4 may indicate one entry of table A.

[0130] In some embodiments of the present disclosure, if indicator #1 indicates a first type channel access procedure for a PUSCH among multiple PUSCHs scheduled by a DCI format, then the associated CAPC value indicated by indicator #1 is the CAPC value used by the UE to transmit the PUSCH.

[0131] For example, indicator #1 in the DCI format may indicate a channel access information related indicator #n1 of PUSCH #n1 among multiple PUSCHs, and if the channel access information related indicator #n1 indicates a first type of channel access procedure for PUSCH #n1, then the CAPC value indicated by the channel access information related indicator #n1 is the CAPC value used by the UE to transmit PUSCH #n1.

[0132] For example, for PUSCH#n1, the UE may determine whether PUSCH#n1 is scheduled within or outside the BS-initiated COT. For example, as described above, based on the remaining COT duration indicator in DCI format 2_0 and the time domain resource allocation information indicated in the DCI format for scheduling multiple PUSCHs, the UE may determine whether PUSCH#n1 is positioned within or outside the BS-initiated COT.

[0133] In response to determining that PUSCH#n1 is scheduled outside the COT initiated by the BS, the UE may perform a first type channel access procedure on PUSCH#n1 according to an associated CAPC value.

[0134] Otherwise, in response to determining that PUSCH #n1 is scheduled within the COT initiated by the BS, it is determined that PUSCH #n1 requires or may use a second type of channel access procedure. In this case, the BS should ensure that the CAPC value used by the BS to initiate the COT is greater than or equal to the CAPC value associated with the UL traffic data carried on PUSCH #n1. In some examples, the UE may further determine the duration of the gap between PUSCH #n1 and the DL or UL transmission (if any) immediately preceding PUSCH #n1, and further determine whether a 2A, 2B, or 2C type channel access procedure is performed before transmitting PUSCH #n1.

[0135] In some embodiments of the present disclosure, if indicator #1 indicates a second type channel access procedure for a PUSCH among multiple PUSCHs scheduled by a DCI format, then the associated CAPC value indicated by indicator #1 is a CAPC value used by the BS to start COT.

[0136] For example, indicator #1 in the DCI format may indicate a channel access information related indicator #n1' of PUSCH #n1' among multiple PUSCHs, and if the channel access information related indicator #n1' indicates a second type of channel access procedure for PUSCH #n1', then the CAPC value indicated by the channel access information related indicator #n1' is the CAPC value used by the BS to activate COT.

[0137] For example, for PUSCH#n1', the UE may determine whether PUSCH#n1' is scheduled within or outside the BS-initiated COT. For example, as described above, based on the remaining COT duration indicator in DCI format 2_0 and the time domain resource allocation information indicated in the DCI format for scheduling multiple PUSCHs, the UE may determine whether PUSCH#n1' is positioned within or outside the BS-initiated COT.

[0138] In response to determining that PUSCH#n1' is scheduled within the COT initiated by the BS, the UE may determine whether the CAPC value of PUSCH#n1' indicated by indicator #1 is greater than or equal to the CAPC value associated with the UL traffic data carried on PUSCH#n1'. When the indicated CAPC value is greater than or equal to the CAPC value associated with the UL traffic data carried on PUSCH#n1', the UE may transmit PUSCH#n1' in response to the second type channel access procedure for PUSCH#n1' being successful. Otherwise, when the indicated CAPC value is less than the CAPC value associated with the UL traffic data carried on PUSCH#n1', the UE may terminate the transmission of PUSCH#n1'.

[0139] In response to determining that PUSCH #n1' is scheduled outside of the COT initiated by the BS, the UE may perform a first type channel access procedure on PUSCH #n1' according to a CAPC value associated with UL traffic data carried on PUSCH #n1'.

[0140] In some embodiments of the present disclosure, when a DCI format schedules multiple PUSCHs on multiple cells, the DCI format may indicate the channel access type, CAPC value, and CPE length of a predefined PUSCH in the multiple PUSCHs. For example, the DCI format may include an indicator or field for indicating the above information, which is referred to as indicator #2 hereinafter.

[0141] In some embodiments of the present disclosure, indicator #2 may indicate an entry (or row) of a table, and each entry of the table may indicate a single channel access type, a single CAPC value, and a single CPE length of a predefined PUSCH in multiple PUSCHs. The table (simply represented as Table #2) may be configured by the BS to the UE (e.g., via RRC) or be predefined. For example, Table #2 may be configured via higher layer parameters ul-AccessConfigListDCI-0-1 or ul-AccessConfigListDCI-0-X. The size of indicator #2 (e.g., the number of bits required for indicator #2) may depend on the number of entries in Table #2. In some instances, the definition of Table #2 may be similar to Table A.

[0142] The aforementioned definition of predefined PUSCH is applicable here. For example, the predefined PUSCH may be: the first scheduled PUSCH among multiple PUSCHs scheduled by the DCI format; the last scheduled PUSCH among multiple PUSCHs; the PUSCH among multiple PUSCHs scheduled on a cell with the lowest cell index among multiple cells scheduled by the DCI format; the PUSCH among multiple PUSCHs scheduled on a cell with the largest cell index among multiple cells; the first scheduled PUSCH among multiple PUSCHs that requires a first type of channel access procedure; the last scheduled PUSCH among multiple PUSCHs that requires a first type of channel access procedure; the first scheduled PUSCH among multiple PUSCHs that requires a first type of channel access procedure The PUSCH on the cell with the lowest cell index among the scheduled PUSCHs; the PUSCH on the cell with the largest cell index among the PUSCHs that require the first type of channel access procedure among multiple PUSCHs; the first scheduled PUSCH among the PUSCHs that require the second type of channel access procedure among multiple PUSCHs; the last scheduled PUSCH among the PUSCHs that require the second type of channel access procedure among multiple PUSCHs; the PUSCH on the cell with the lowest cell index among the PUSCHs that require the second type of channel access procedure among multiple PUSCHs; or the PUSCH on the cell with the largest cell index among the PUSCHs that require the second type of channel access procedure among multiple PUSCHs.

[0143] In some embodiments of the present disclosure, if indicator #2 indicates a first type channel access procedure for a predefined PUSCH, then the associated CAPC value indicated by indicator #2 is a CAPC value used by the UE to transmit the predefined PUSCH. In some embodiments of the present disclosure, if indicator #2 indicates a second type channel access procedure for a predefined PUSCH, then the associated CAPC value indicated by indicator #2 is a CAPC value used by the BS to start COT.

[0144] For example, indicator #2 in the DCI format may indicate the channel access type, CAPC value, and CPE length of a predefined PUSCH (denoted as PUSCH #n2) among multiple PUSCHs scheduled by the DCI format.

[0145] If the indicated channel access type is a first type channel access procedure, then the indicated CAPC value is a CAPC value used by the UE to transmit PUSCH#n2. If PUSCH#n2 is scheduled outside the BS-initiated COT, then the UE may perform a first type channel access procedure on PUSCH#n2 according to the indicated CAPC value. For example, as described above, based on the remaining COT duration indicator in DCI format 2_0 and the time domain resource allocation information indicated in the DCI format for scheduling multiple PUSCHs, the UE may determine whether PUSCH#n2 is located within the BS-initiated COT or outside the BS-initiated COT. On the other hand, in response to determining that PUSCH#n2 is scheduled within the BS-initiated COT, PUSCH#n2 requires or may use a second type channel access procedure. In this case, the BS should ensure that the CAPC value used by the BS to initiate the COT is greater than or equal to the CAPC value associated with the UL traffic data carried on PUSCH#n2. In some examples, the UE may further determine the duration of the gap between PUSCH #n2 and the DL or UL transmission (if any) immediately preceding PUSCH #n2, and further determine whether a type 2A, 2B, or 2C channel access procedure is performed prior to transmitting PUSCH #n2.

[0146] If the indicated channel access type is a second type channel access procedure, then the indicated CAPC value is the CAPC value used by the BS to initiate the COT. If it is determined that PUSCH#n2 is scheduled within the COT initiated by the BS and the indicated CAPC value is greater than or equal to the CAPC value of the UL traffic carried on PUSCH#n2, then the UE may transmit PUSCH#n2 in response to the success of the second type channel access procedure for PUSCH#n2. If it is determined that PUSCH#n2 is scheduled within the COT initiated by the BS and the indicated CAPC value is less than the CAPC value of the UL traffic carried on PUSCH#n2, then the UE may terminate the transmission of PUSCH#n2. If it is determined that PUSCH#n2 is scheduled outside the COT initiated by the BS, then the UE may perform the first type channel access procedure for PUSCH#n2 according to the CAPC value associated with the UL traffic data carried on PUSCH#n2.

[0147] Regarding the remaining co-scheduled PUSCHs, in some embodiments of the present disclosure, each of them requires a first type channel access procedure. That is, the first type channel access procedure may be mandatory for transmitting multiple PUSCHs other than the predefined PUSCH. The CAPC value of a PUSCH in the multiple PUSCHs other than the predefined PUSCH may be determined based on the UL traffic data carried on the corresponding PUSCH. For example, the CAPC value used by the first type channel access procedure is a CAPC value associated with the UL traffic data carried on the corresponding PUSCH.

[0148] In some other embodiments of the present disclosure, for each of a plurality of PUSCHs other than a predefined PUSCH, a channel access type of the corresponding PUSCH may be determined based on whether the corresponding PUSCH is scheduled within or outside the BS-initiated COT.

[0149] For example, for a corresponding PUSCH among a plurality of PUSCHs other than a predefined PUSCH, the UE may determine whether the corresponding PUSCH is scheduled within or outside the BS-initiated COT. The method described above for determining whether a PUSCH is scheduled within or outside the BS-initiated COT is applicable here.

[0150] In response to determining that the corresponding PUSCH is scheduled outside the COT initiated by the BS, it is determined that the corresponding PUSCH requires a first type of channel access procedure and the CAPC value of the corresponding PUSCH can be determined based on the UL traffic carried on the corresponding PUSCH. For example, the UE may perform the first type of channel access procedure using the CAPC value associated with the UL traffic carried on the corresponding PUSCH before transmitting the corresponding PUSCH. Otherwise, in response to determining that the corresponding PUSCH is scheduled within the COT initiated by the BS, it is determined that the corresponding PUSCH requires or can use a second type of channel access procedure. The UE may perform the second type of channel access procedure before transmitting the corresponding PUSCH in the COT. In this case, the BS should ensure that the CAPC value used by the BS to initiate the COT is greater than or equal to the CAPC value associated with the UL traffic data carried on the corresponding PUSCH. The method described above for determining which of the second type of channel access procedures (e.g., 2A, 2B, or 2C type channel access procedures) should be performed is applicable here.

[0151] The predefined CPE length may be applied to all multiple PUSCHs except the predefined PUSCH. For example, a CPE length of "0" may be used to transmit each of the multiple PUSCHs except the predefined PUSCH.

[0152] In some embodiments of the present disclosure, when a DCI format schedules multiple PUSCHs on multiple cells, the DCI format may indicate a single channel access type, a single CAPC value, and a single CPE length for all multiple PUSCHs. For example, the DCI format may include an indicator or field for indicating the above information, which is referred to as indicator #3 hereinafter.

[0153] In some embodiments of the present disclosure, indicator #3 may indicate an entry (or row) of a table, and each entry of the table may indicate a single channel access type, a single CAPC value, and a single CPE length for all multiple PUSCHs. That is, all co-scheduled PUSCHs correspond to the same channel access type, CAPC value, and CPE length. The table (simply represented as Table #3) may be configured by the BS to the UE (e.g., via RRC) or be predefined. For example, Table #3 may be configured via a higher layer parameter ul-AccessConfigListDCI-0-1 or ul-AccessConfigListDCI-0-X. The size of indicator #3 (e.g., the number of bits required for indicator #3) may depend on the number of entries in Table #3. In some instances, the definition of Table #3 may be similar to Table A.

[0154] In some embodiments of the present disclosure, if indicator #3 indicates a first type channel access procedure for all co-scheduled PUSCHs, then the associated CAPC value indicated by indicator #3 is a CAPC value used by the UE to transmit the co-scheduled PUSCHs. In some embodiments of the present disclosure, if indicator #3 indicates a second type channel access procedure for all co-scheduled PUSCHs, then the associated CAPC value indicated by indicator #3 is a CAPC value used by the BS to start COT.

[0155] For example, indicator #3 in the DCI format may indicate the channel access type, CAPC value, and CPE length of all multiple PUSCHs scheduled by the DCI format.

[0156] If the indicated channel access type is a first type channel access procedure, then the indicated CAPC value is a CAPC value used by the UE to transmit multiple PUSCHs. If PUSCH#n3 is scheduled outside the BS-initiated COT, the UE may perform a first type channel access procedure on a PUSCH (denoted as PUSCH#n3) among multiple PUSCHs according to the indicated CAPC value. For example, as described above, based on the remaining COT duration indicator in DCI format 2_0 and the time domain resource allocation information indicated in the DCI format for scheduling multiple PUSCHs, the UE may determine whether PUSCH#n3 is located within the BS-initiated COT or outside the BS-initiated COT. On the other hand, in response to determining that PUSCH#n3 is scheduled within the BS-initiated COT, PUSCH#n3 requires or may use a second type channel access procedure. In this case, the BS should ensure that the CAPC value used by the BS to initiate the COT is greater than or equal to the CAPC value associated with the UL traffic data carried on PUSCH#n3. In some examples, the UE may further determine the duration of the gap between PUSCH #n3 and the DL or UL transmission (if any) immediately preceding PUSCH #n3, and further determine whether a type 2A, 2B, or 2C channel access procedure is performed prior to transmitting PUSCH #n3.

[0157] If the indicated channel access type is a second type channel access procedure, then the indicated CAPC value is the CAPC value used by the BS to initiate the COT. If it is determined that PUSCH#n3 is scheduled within the COT initiated by the BS and the indicated CAPC value is greater than or equal to the CAPC value of the UL traffic carried on PUSCH#n3, then the UE may transmit PUSCH#n3 in response to the success of the second type channel access procedure for PUSCH#n3. If it is determined that PUSCH#n3 is scheduled within the COT initiated by the BS and the indicated CAPC value is less than the CAPC value of the UL traffic carried on PUSCH#n3, then the UE may terminate the transmission of PUSCH#n3. If it is determined that PUSCH#n3 is scheduled outside the COT initiated by the BS, then the UE may perform the first type channel access procedure for PUSCH#n3 according to the CAPC value associated with the UL traffic data carried on PUSCH#n3.

[0158] Figure 5 A flowchart illustrating an exemplary wireless communication procedure 500 according to some embodiments of the present disclosure. The details described in all the above embodiments of the present disclosure apply to Figure 5 In some examples, the program may be performed by a UE (e.g. Figure 1 UE 101 in executes.

[0159] refer to Figure 5In operation 511, the UE may receive a DCI format for scheduling a plurality of PUSCHs on a plurality of cells of the UE from the BS. In operation 513, the UE may determine a channel access type, a CAPC value, and a CPE length for each of the plurality of PUSCHs. For example, the UE may determine a channel access type, a CAPC value, and a CPE length for each of the plurality of PUSCHs using the method described in the foregoing embodiments of the present disclosure or any combination thereof.

[0160] In operation 515, the UE may perform a channel access procedure for each of the plurality of PUSCHs according to the determined channel access type, CAPC value, and CPE length. In operation 517, the UE may transmit a CPE having a duration equal to the determined CPE length of the first PUSCH and the first PUSCH to the BS in response to a corresponding channel access procedure for the first PUSCH among the plurality of PUSCHs being successful.

[0161] In some embodiments of the present disclosure, a predefined CPE length (eg, 0) may be applied to all multiple PUSCHs. For example, in response to a successful channel access procedure for a specific PUSCH, the UE may transmit the PUSCH using the predefined CPE length.

[0162] In some embodiments of the present disclosure, determining a CAPC value for each of a plurality of PUSCHs may include determining a CAPC value for a PUSCH requiring a first type channel access procedure among the plurality of PUSCHs according to UL traffic data carried on the PUSCH.

[0163] In some embodiments of the present disclosure, all of the multiple PUSCHs require a first type of channel access procedure. In some embodiments of the present disclosure, determining the channel access type of each of the multiple PUSCHs may include: for a corresponding PUSCH among the multiple PUSCHs, determining whether the corresponding PUSCH is scheduled within the BS-initiated COT or outside the BS-initiated COT; and in response to determining that the corresponding PUSCH is scheduled outside the BS-initiated COT, determining that the corresponding PUSCH requires a first type of channel access procedure. In some embodiments of the present disclosure, determining the channel access type of each of the multiple PUSCHs may include: for a corresponding PUSCH among the multiple PUSCHs, determining whether the corresponding PUSCH is scheduled within the BS-initiated COT or outside the BS-initiated COT; and in response to determining that the corresponding PUSCH is scheduled within the BS-initiated COT, determining that the corresponding PUSCH requires a second type of channel access procedure.

[0164] In some embodiments of the present disclosure, the DCI format may indicate at least one of the following: CPE length; CAPC value; a first indicator (e.g., indicator #1) used to indicate the channel access type, CAPC value, and CPE length of each of multiple PUSCHs; a second indicator (e.g., indicator #2) used to indicate the channel access type, CAPC value, and CPE length of a predefined PUSCH among multiple PUSCHs; or a third indicator (e.g., indicator #3) used to indicate a single channel access type, a single CAPC value, and a single CPE length for all multiple PUSCHs.

[0165] In some embodiments of the present disclosure, if the DCI format indicates a CPE length, then: indicating that the CPE length is applicable to all multiple PUSCHs; indicating that the CPE length is applicable to all PUSCHs in multiple PUSCHs that require a first type of channel access procedure and a predefined CPE length is applicable to the remaining PUSCHs in multiple PUSCHs; indicating that the CPE length is applicable to all PUSCHs in multiple PUSCHs that require a second type of channel access procedure and a predefined CPE length is applicable to the remaining PUSCHs in multiple PUSCHs; indicating that the CPE length is applicable to a predefined PUSCH in multiple PUSCHs and the predefined CPE length is applicable to the remaining PUSCHs in multiple PUSCHs; or indicating that the CPE length may include a first CPE length applied to all PUSCHs in multiple PUSCHs that require a first type of channel access procedure and a second CPE length applied to all PUSCHs in multiple PUSCHs that require a second type of channel access procedure.

[0166] In some embodiments of the present disclosure, if the DCI format indicates a CAPC value, then: the indicated CAPC value may be a first CAPC value (e.g., CAPC#1) used by the BS to initiate COT; the indicated CAPC value may be a second CAPC value (e.g., CAPC#2) used by the UE to perform a channel access procedure for transmitting PUSCH; or the indicated CAPC value may include a first CAPC value and a second CAPC value.

[0167] In some embodiments of the present disclosure, if a PUSCH among multiple PUSCHs is scheduled within a COT initiated by a BS, the UE may transmit the PUSCH in response to a first CAPC value being greater than or equal to a CAPC value associated with uplink traffic data carried on the PUSCH and a second type channel access procedure for the PUSCH being successful. In some embodiments of the present disclosure, if a PUSCH among multiple PUSCHs is scheduled within a COT initiated by a BS, the UE may terminate transmission of the PUSCH in response to a first CAPC value being less than a CAPC value associated with uplink traffic data carried on the PUSCH.

[0168] In some embodiments of the present disclosure, if more than one PUSCH among the plurality of PUSCHs is scheduled within a plurality of BS-enabled COTs, the first CAPC value may be a minimum value of CAPC values ​​used by the BS to enable the plurality of BS-enabled COTs.

[0169] In some embodiments of the present disclosure, performing a channel access procedure on each of the plurality of PUSCHs according to the determined CAPC value may include performing a first type of channel access procedure on a PUSCH of the plurality of PUSCHs according to a second CAPC value.

[0170] In some embodiments of the present disclosure, if the DCI format indicates both the CAPC value and the CPE length, the CAPC value and the CPE length may be indicated by separate fields in the DCI format or jointly indicated by a single field in the DCI format.

[0171] In some embodiments of the present disclosure, if the first, second, or third indicator indicates a first type of channel access procedure for a PUSCH among multiple PUSCHs, then the associated CAPC value indicated by the first, second, or third indicator may be a CAPC value used by the UE to transmit the PUSCH. In some embodiments of the present disclosure, if the first, second, or third indicator indicates a second type of channel access procedure for a PUSCH among multiple PUSCHs, then the associated CAPC value indicated by the first, second, or third indicator may be a CAPC value used by the BS to start the COT.

[0172] In some embodiments of the present disclosure, performing a channel access procedure on each of the plurality of PUSCHs according to the determined CAPC value may include: if the PUSCH is scheduled outside the BS-initiated COT, performing a first type of channel access procedure on the PUSCH according to the associated CAPC value.

[0173] In some embodiments of the present disclosure, if the PUSCH is scheduled within the BS-initiated COT, then when the associated CAPC value is greater than or equal to the CAPC value of the uplink (UL) traffic data carried on the PUSCH, the UE may transmit the PUSCH in response to the success of the second type channel access procedure for the PUSCH. In some embodiments of the present disclosure, if the PUSCH is scheduled within the BS-initiated COT, then when the associated CAPC value is less than the CAPC value of the UL traffic data carried on the PUSCH, the UE may terminate the transmission of the PUSCH.

[0174] In some embodiments of the present disclosure, if the DCI format indicates a second indicator, the UE may use the method described in the aforementioned embodiments of the present disclosure or any combination thereof to determine the channel access type, CAPC value and CPE length of multiple PUSCHs other than the predefined PUSCH.

[0175] For example, in some embodiments of the present disclosure, the predefined CPE length is applied to all multiple PUSCHs except the predefined PUSCH.

[0176] For example, in some embodiments of the present disclosure, all multiple PUSCHs other than the predefined PUSCH require a first type channel access procedure. For a corresponding PUSCH in the multiple PUSCHs other than the predefined PUSCH, the UE may determine a CAPC value for the corresponding PUSCH based on UL traffic data carried on the corresponding PUSCH. For example, the UE may use a CAPC value associated with UL traffic data carried on the corresponding PUSCH to perform a first type channel access procedure on the corresponding PUSCH.

[0177] For example, in some embodiments of the present disclosure, determining the channel access type and CAPC value of each of multiple PUSCHs may include: for a corresponding PUSCH among multiple PUSCHs other than a predefined PUSCH, determining whether the corresponding PUSCH is scheduled within the COT initiated by the BS or outside the COT initiated by the BS; and in response to determining that the corresponding PUSCH is scheduled outside the COT initiated by the BS, determining that the corresponding PUSCH requires a first type of channel access procedure and determining the CAPC value of the corresponding PUSCH based on the UL traffic data carried on the corresponding PUSCH.

[0178] For example, in some embodiments of the present disclosure, determining the channel access type and CAPC value of each of multiple PUSCHs may include: for a corresponding PUSCH among multiple PUSCHs other than a predefined PUSCH, determining whether the corresponding PUSCH is scheduled within the BS-initiated COT or outside the BS-initiated COT; and in response to determining that the corresponding PUSCH is scheduled within the BS-initiated COT, determining that the corresponding PUSCH requires a second type of channel access procedure.

[0179] The aforementioned definition of predefined PUSCH is applicable here. For example, the predefined PUSCH may be: the first scheduled PUSCH among multiple PUSCHs; the last scheduled PUSCH among multiple PUSCHs; a PUSCH among multiple PUSCHs scheduled on a cell with a lowest cell index among multiple cells; a PUSCH among multiple PUSCHs scheduled on a cell with a maximum cell index among multiple cells; the first scheduled PUSCH among multiple PUSCHs that require a first type of channel access procedure; the last scheduled PUSCH among multiple PUSCHs that require a first type of channel access procedure; the PUSCH with the maximum cell index among multiple PUSCHs that require a first type of channel access procedure PUSCH on a cell with a low cell index; PUSCH on a cell with the largest cell index among PUSCHs that require a first type of channel access procedure among multiple PUSCHs; the first scheduled PUSCH among PUSCHs that require a second type of channel access procedure among multiple PUSCHs; the last scheduled PUSCH among PUSCHs that require a second type of channel access procedure among multiple PUSCHs; PUSCH on a cell with the lowest cell index among PUSCHs that require a second type of channel access procedure among multiple PUSCHs; or PUSCH on a cell with the largest cell index among PUSCHs that require a second type of channel access procedure among multiple PUSCHs.

[0180] In some embodiments of the present disclosure, the first indicator may indicate an entry of a table, and each entry of the table may indicate a channel access type, a CAPC value, and a CPE length for each of a plurality of PUSCHs.

[0181] In some embodiments of the present disclosure, the second indicator may indicate an entry of a table, and each entry of the table may indicate a single channel access type, a single CAPC value, and a single CPE length of a predefined PUSCH in a PUSCH scheduled by a single DCI format.

[0182] In some embodiments of the present disclosure, the third indicator may indicate an entry of a table, and each entry of the table may indicate a single channel access type, a single CAPC value, and a single CPE length for all PUSCHs scheduled by a single DCI format.

[0183] In some embodiments of the present disclosure, the size of the first, second or third indicator in the DCI format may depend on the number of entries in the table.

[0184] In some embodiments of the present disclosure, if a PUSCH among multiple PUSCHs is scheduled within a BS-initiated COT, the CAPC value used by the BS to initiate the BS-initiated COT may be greater than or equal to the CAPC value of UL traffic data carried on the PUSCH.

[0185] Those skilled in the art will appreciate that the sequence of operations in the exemplary process 500 may be changed and some operations in the exemplary process 500 may be eliminated or modified without departing from the spirit and scope of the present disclosure.

[0186] Figure 6 A flowchart illustrating an exemplary wireless communication procedure 600 according to some embodiments of the present disclosure. The details described in all the previous embodiments of the present disclosure apply to Figure 6 In some examples, the program may be performed by a BS (e.g. Figure 1 BS102) in .

[0187] refer to Figure 6 In operation 611, the BS may transmit a DCI format for scheduling a plurality of PUSCHs on a plurality of cells of the UE to the UE.

[0188] In operation 613, the BS may receive a first PUSCH from the UE in response to a successful channel access procedure for a first PUSCH among multiple PUSCHs, wherein the channel access procedure for the first PUSCH is performed by the UE according to a channel access type and a channel access priority category (CAPC) value, and wherein a cyclic prefix extension (CPE) is transmitted by the UE before the first PUSCH.

[0189] In some embodiments of the present disclosure, the predefined CPE length is applied to all multiple PUSCHs.

[0190] In some embodiments of the present disclosure, if a PUSCH among multiple PUSCHs requires a first type channel access procedure, the CAPC value of the PUSCH is determined by the UE according to UL traffic data carried on the PUSCH.

[0191] In some embodiments of the present disclosure, all multiple PUSCHs require a first type channel access procedure. In some embodiments of the present disclosure, if a PUSCH among multiple PUSCHs is scheduled outside the COT initiated by the BS, then the UE requires a first type channel access procedure for transmitting the PUSCH. In some embodiments of the present disclosure, if the PUSCH is scheduled within the COT initiated by the BS, then the UE requires a second type channel access procedure for transmitting the PUSCH.

[0192] In some embodiments of the present disclosure, the DCI format indicates at least one of the following: CPE length; CAPC value; a first indicator for indicating the channel access type, CAPC value and CPE length of each of multiple PUSCHs; a second indicator for indicating the channel access type, CAPC value and CPE length of a predefined PUSCH among the multiple PUSCHs; or a third indicator for indicating a single channel access type, a single CAPC value and a single CPE length for all multiple PUSCHs.

[0193] In some embodiments of the present disclosure, if the DCI format indicates a CPE length, then: indicating that the CPE length applies to all multiple PUSCHs; indicating that the CPE length applies to all PUSCHs in multiple PUSCHs that require a first type of channel access procedure and a predefined CPE length applies to the remaining PUSCHs in multiple PUSCHs; indicating that the CPE length applies to all PUSCHs in multiple PUSCHs that require a second type of channel access procedure and a predefined CPE length applies to the remaining PUSCHs in multiple PUSCHs; indicating that the CPE length applies to a predefined PUSCH in multiple PUSCHs and a predefined CPE length applies to the remaining PUSCHs in multiple PUSCHs; or indicating that the CPE length includes a first CPE length applied to all PUSCHs in multiple PUSCHs that require a first type of channel access procedure and a second CPE length applied to all PUSCHs in multiple PUSCHs that require a second type of channel access procedure.

[0194] In some embodiments of the present disclosure, if the DCI format indicates a CAPC value, then: the indicated CAPC value is a first CAPC value used by the BS to initiate COT; the indicated CAPC value is a second CAPC value used by the UE to perform a channel access procedure for transmitting PUSCH; or the indicated CAPC value includes a first CAPC value and a second CAPC value.

[0195] In some embodiments of the present disclosure, if the first CAPC value is greater than or equal to the CAPC value of UL traffic data carried on the PUSCH among the plurality of PUSCHs requiring the second type channel access procedure, the BS may attempt to receive the PUSCH. In some embodiments of the present disclosure, if the first CAPC value is less than the CAPC value of UL traffic data carried on the PUSCH, the BS may determine that transmission of the PUSCH is terminated.

[0196] In some embodiments of the present disclosure, if more than one PUSCH among the plurality of PUSCHs is scheduled within the plurality of BS-enabled COTs, the first CAPC value is a minimum value of the CAPC values ​​used by the BS to enable the plurality of BS-enabled COTs.

[0197] In some embodiments of the present disclosure, if a PUSCH among the plurality of PUSCHs requires a first type channel access procedure, the first type channel access procedure is performed by the UE according to the second CAPC value for transmitting the PUSCH.

[0198] In some embodiments of the present disclosure, if the DCI format indicates both the CAPC value and the CPE length, the CAPC value and the CPE length are indicated by separate fields in the DCI format or jointly indicated by a single field in the DCI format.

[0199] In some embodiments of the present disclosure, if the first, second, or third indicator indicates a first type of channel access procedure for a PUSCH among multiple PUSCHs, then the associated CAPC value indicated by the first, second, or third indicator is a CAPC value used by the UE to transmit the PUSCH. In some embodiments of the present disclosure, if the first, second, or third indicator indicates a second type of channel access procedure for a PUSCH among multiple PUSCHs, then the associated CAPC value indicated by the first, second, or third indicator is a CAPC value used by the BS to start the COT.

[0200] In some embodiments of the present disclosure, if the PUSCH is scheduled outside the COT initiated by the BS, the channel access procedure of the PUSCH is a first type channel access procedure performed according to the associated CAPC value.

[0201] In some embodiments of the present disclosure, if the PUSCH is scheduled within the BS-initiated COT, the BS may attempt to receive the PUSCH when the associated CAPC value is greater than or equal to the CAPC value of the UL traffic data carried on the PUSCH. In some embodiments of the present disclosure, if the PUSCH is scheduled within the BS-initiated COT, the BS may determine that the transmission of the PUSCH is terminated when the associated CAPC value is less than the CAPC value of the UL traffic data carried on the PUSCH.

[0202] In some embodiments of the present disclosure, the predefined CPE length is applied to all multiple PUSCHs except the predefined PUSCH.

[0203] In some embodiments of the present disclosure, all multiple PUSCHs except the predefined PUSCH require a first type channel access procedure.

[0204] In some embodiments of the present disclosure, for a corresponding PUSCH among multiple PUSCHs other than the predefined PUSCH, if the corresponding PUSCH is scheduled outside the COT initiated by the BS, then the corresponding PUSCH requires a first type channel access procedure and the CAPC value of the corresponding PUSCH is determined according to the UL traffic data carried on the corresponding PUSCH. In some embodiments of the present disclosure, for a corresponding PUSCH among multiple PUSCHs other than the predefined PUSCH, if the corresponding PUSCH is scheduled within the COT initiated by the BS, then the corresponding PUSCH requires a second type channel access procedure.

[0205] In some embodiments of the present disclosure, the predefined PUSCH is: the first scheduled PUSCH among multiple PUSCHs; the last scheduled PUSCH among multiple PUSCHs; a PUSCH among multiple PUSCHs scheduled on a cell with a lowest cell index among multiple cells; a PUSCH among multiple PUSCHs scheduled on a cell with a maximum cell index among multiple cells; the first scheduled PUSCH among multiple PUSCHs that require a first type of channel access procedure; the last scheduled PUSCH among multiple PUSCHs that require a first type of channel access procedure; the PUSCH among multiple PUSCHs that require a first type of channel access procedure PUSCH on the cell with the lowest cell index; PUSCH on the cell with the largest cell index among PUSCHs that require a first type of channel access procedure among multiple PUSCHs; the first scheduled PUSCH among PUSCHs that require a second type of channel access procedure among multiple PUSCHs; the last scheduled PUSCH among PUSCHs that require a second type of channel access procedure among multiple PUSCHs; PUSCH on the cell with the lowest cell index among PUSCHs that require a second type of channel access procedure among multiple PUSCHs; or PUSCH on the cell with the largest cell index among PUSCHs that require a second type of channel access procedure among multiple PUSCHs.

[0206] In some embodiments of the present disclosure, the first indicator indicates an entry of a table, and each entry of the table indicates a channel access type, a CAPC value, and a CPE length for each of a plurality of PUSCHs.

[0207] In some embodiments of the present disclosure, the second indicator indicates an entry of a table, and each entry of the table indicates a single channel access type, a single CAPC value, and a single CPE length of a predefined PUSCH in a PUSCH scheduled by a single DCI format.

[0208] In some embodiments of the present disclosure, the third indicator indicates an entry of a table, and each entry of the table indicates a single channel access type, a single CAPC value, and a single CPE length for all PUSCHs scheduled by a single DCI format.

[0209] In some embodiments of the present disclosure, the size of the first, second or third indicator in the DCI format depends on the number of entries in the table.

[0210] In some embodiments of the present disclosure, if a PUSCH among multiple PUSCHs is scheduled within a BS-initiated COT, then the CAPC value used by the BS to initiate the BS-initiated COT is greater than or equal to the CAPC value of UL traffic data carried on the PUSCH.

[0211] Those skilled in the art will appreciate that the sequence of operations in the exemplary process 600 may be changed and some operations in the exemplary process 600 may be eliminated or modified without departing from the spirit and scope of the present disclosure.

[0212] Figure 7 700 according to some embodiments of the present disclosure. Figure 7 , the apparatus 700 may include at least one processor 706 and at least one transceiver 702 coupled to the processor 706. The apparatus 700 may be a UE or a BS.

[0213] Although elements such as at least one transceiver 702 and processor 706 are described in the singular form in this figure, the plural form may be considered unless explicitly stated to be limited to the singular form. In some embodiments of the present application, the transceiver 702 may be divided into two devices, such as a receiving circuit system and a transmitting circuit system. In some embodiments of the present application, the device 700 may further include an input device, a memory and / or other components.

[0214] In some embodiments of the present application, the device 700 may be a UE. The transceiver 702 and the processor 706 may interact with each other to perform Figures 1 to 6 In some embodiments of the present application, the device 700 may be a BS. The transceiver 702 and the processor 706 may interact with each other to perform the operations described in Figures 1 to 6 The operation of BS is described in .

[0215] In some embodiments of the present application, the apparatus 700 may further include at least one non-transitory computer-readable medium.

[0216] For example, in some embodiments of the present disclosure, a non-transitory computer-readable medium may store computer-executable instructions to cause the processor 706 to implement the method described above with respect to the UE. For example, when the computer-executable instructions are executed, the processor 706 interacts with the transceiver 702 to perform the Figures 1 to 6 The operations of the UE are described in .

[0217] In some embodiments of the present disclosure, a non-transitory computer-readable medium may store computer-executable instructions to cause the processor 706 to implement the method described above with respect to the BS. For example, when the computer-executable instructions are executed, the processor 706 interacts with the transceiver 702 to perform the Figures 1 to 6 The operation of BS is described in .

[0218] It will be appreciated by those of ordinary skill in the art that the operations or steps of the methods described in conjunction with the aspects disclosed herein may be directly embodied in hardware, a software module executed by a processor, or a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the operations or steps of the methods may reside as one or any combination or set of codes and / or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.

[0219] Although the present disclosure has been described with reference to specific embodiments of the present disclosure, it is apparent that many substitutions, modifications, and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added, or substituted in other embodiments. Moreover, the operation of the disclosed embodiments does not necessarily require all elements of each figure. For example, it will enable a person of ordinary skill in the art of the disclosed embodiments to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure set forth herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0220] In this archive, the term "comprising" or any other variation thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment comprising a series of elements not only comprises these elements but also may comprise other elements that are not explicitly listed or inherent to this process, method, article or equipment. The element starting with "one" or the like does not exclude the existence of additional identical elements in the process, method, article or equipment comprising the element without more constraints. Moreover, the term "another" is defined as at least the second or more. As used herein, the term "having" and the like are defined as "comprising". For example, the expression of "A and / or B" or "at least one of A and B" may include any and all combinations of the words listed together with the expression. For example, the expression "A and / or B" or "at least one of A and B" may include A, B or both A and B. The wording "first", "second" or the like is only used to clearly illustrate the embodiments of the present application, and is not used to limit the essence of the present application.

Claims

1. A user equipment UE, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receiving, from a base station BS, a downlink control information DCI format for scheduling a plurality of physical uplink shared channels PUSCH on a plurality of cells of the UE; determining a channel access type, a channel access priority class CAPC value, and a cyclic prefix extension CPE length for each of the plurality of PUSCHs; performing a channel access procedure for each of the plurality of PUSCHs according to the determined channel access type and CAPC value; and In response to a corresponding channel access procedure for a first PUSCH among the plurality of PUSCHs being successful, a CPE having a duration equal to the determined CPE length of the first PUSCH and the first PUSCH are transmitted to the BS.

2. The UE according to claim 1, wherein the DCI format indicates at least one of the following: CPE length; CAPC value; a first indicator for indicating a channel access type, a CAPC value, and a CPE length for each of the plurality of PUSCHs; A second indicator, which is used to indicate the channel access type, CAPC value and CPE length of a predefined PUSCH among the multiple PUSCHs; or A third indicator is used to indicate a single channel access type, a single CAPC value, and a single CPE length of all the multiple PUSCHs.

3. The UE according to claim 2, wherein if the DCI format indicates a CPE length, then: The indicated CPE length is applied to all of the plurality of PUSCHs; The indicated CPE length is applied to all PUSCHs of the plurality of PUSCHs that require a first type of channel access procedure and the predefined CPE length is applied to the remaining PUSCHs of the plurality of PUSCHs; The indicated CPE length is applied to all PUSCHs of the plurality of PUSCHs that require a second type of channel access procedure and the predefined CPE length is applied to the remaining PUSCHs of the plurality of PUSCHs; The indicated CPE length applies to a predefined PUSCH in the plurality of PUSCHs and the predefined CPE length applies to the remaining PUSCHs in the plurality of PUSCHs; or The indicated CPE length includes a first CPE length applied to all PUSCHs in the multiple PUSCHs that require a first type of channel access procedure and a second CPE length applied to all PUSCHs in the multiple PUSCHs that require a second type of channel access procedure. The UE according to claim 1 , wherein the predefined CPE length is applied to all of the plurality of PUSCHs.

5. The UE of claim 2, wherein if the DCI format indicates a CAPC value, then: The indicated CAPC value is a first CAPC value used by the BS to start a channel occupancy time COT; The indicated CAPC value is a second CAPC value used by the UE to perform a channel access procedure for transmitting a PUSCH; or The indicated CAPC value includes the first CAPC value and the second CAPC value.

6. The UE of claim 5, wherein the processor is further configured to: If a PUSCH among the plurality of PUSCHs is scheduled within the COT initiated by the BS, then: transmitting the PUSCH in response to the first CAPC value being greater than or equal to a CAPC value associated with uplink (UL) traffic data carried on the PUSCH and a second type channel access procedure for the PUSCH being successful; or Transmission of the PUSCH is terminated in response to the first CAPC value being less than the CAPC value associated with the UL traffic data carried on the PUSCH.

7. The UE of claim 1, wherein determining the CAPC value for each of the plurality of PUSCHs comprises determining a CAPC value for a PUSCH requiring a first type channel access procedure among the plurality of PUSCHs according to uplink (UL) traffic data carried on the PUSCH.

8. The UE according to claim 1, wherein all of the plurality of PUSCHs require a first type channel access procedure; or wherein determining the channel access type for each of the plurality of PUSCHs comprises for a corresponding PUSCH in the plurality of PUSCHs, Determine whether the corresponding PUSCH is scheduled within a BS-initiated channel occupation time COT or outside the BS-initiated COT; and Determining that the corresponding PUSCH requires a first type channel access procedure in response to determining that the corresponding PUSCH is scheduled out-of-COT initiated by the BS; or In response to determining that the corresponding PUSCH is scheduled within the COT initiated by the BS, it is determined that the corresponding PUSCH requires a second type channel access procedure.

9. The UE of claim 2, wherein if the first, second, or third indicator indicates a first type of channel access procedure for a PUSCH among the plurality of PUSCHs, then the associated CAPC value indicated by the first, second, or third indicator is a CAPC value used by the UE to transmit the PUSCH; and Wherein if the first, second or third indicator indicates a second type channel access procedure for a PUSCH among the plurality of PUSCHs, then the associated CAPC value indicated by the first, second or third indicator is a CAPC value used by the BS to start a channel occupancy time COT.

10. The UE of claim 9, wherein the processor is further configured to: if the PUSCH is scheduled within a BS-initiated COT, then: transmitting the PUSCH in response to a success of a second type channel access procedure for the PUSCH when the associated CAPC value is greater than or equal to a CAPC value of uplink UL traffic data carried on the PUSCH; or When the associated CAPC value is less than the CAPC value of the UL traffic data carried on the PUSCH, transmission of the PUSCH is terminated.

11. The UE according to claim 2, wherein a predefined CPE length is applied to all of the plurality of PUSCHs except the predefined PUSCH; and wherein all of the plurality of PUSCHs except the predefined PUSCH require a first type channel access procedure; or Wherein determining the channel access type and CAPC value of each of the plurality of PUSCHs comprises: For a corresponding PUSCH in the plurality of PUSCHs other than the predefined PUSCH, Determine whether the corresponding PUSCH is scheduled within a BS-initiated channel occupation time COT or outside the COT; and In response to determining that the corresponding PUSCH is scheduled outside the COT initiated by the BS, determining that the corresponding PUSCH requires a first type channel access procedure and determining a CAPC value of the corresponding PUSCH according to uplink UL traffic data carried on the corresponding PUSCH; or In response to determining that the corresponding PUSCH is scheduled within the COT initiated by the BS, it is determined that the corresponding PUSCH requires a second type channel access procedure.

12. The UE according to any one of claims 2, 3 and 11, wherein the predefined PUSCH is: a first scheduled PUSCH among the plurality of PUSCHs; A last scheduled PUSCH among the plurality of PUSCHs; a PUSCH among the plurality of PUSCHs scheduled on a cell having a lowest cell index among the plurality of cells; a PUSCH among the plurality of PUSCHs scheduled on a cell having a maximum cell index among the plurality of cells; a first scheduled PUSCH among the PUSCHs requiring a first type of channel access procedure among the plurality of PUSCHs; a last scheduled PUSCH among the PUSCHs requiring a first type of channel access procedure among the plurality of PUSCHs; a PUSCH on a cell having a lowest cell index among the PUSCHs requiring a first type of channel access procedure among the plurality of PUSCHs; a PUSCH on a cell having a maximum cell index among the PUSCHs requiring a first type of channel access procedure among the plurality of PUSCHs; a first scheduled PUSCH among the PUSCHs requiring a second type of channel access procedure among the plurality of PUSCHs; a last scheduled PUSCH among the PUSCHs requiring a second type channel access procedure among the plurality of PUSCHs; a PUSCH on a cell having a lowest cell index among the PUSCHs requiring a second type of channel access procedure among the plurality of PUSCHs; or A PUSCH on a cell having a maximum cell index among the PUSCHs requiring a second type channel access procedure among the plurality of PUSCHs.

13. The UE according to claim 2, wherein the first indicator indicates an entry of a table, and each entry of the table indicates a channel access type, a CAPC value, and a CPE length for each of the plurality of PUSCHs; or wherein the second indicator indicates an entry of a table, and each entry of the table indicates a single channel access type, a single CAPC value, and a single CPE length for a predefined PUSCH in a PUSCH scheduled by a single DCI format; or Wherein the third indicator indicates an entry of a table, and each entry of the table indicates a single channel access type, a single CAPC value, and a single CPE length for all PUSCHs scheduled by a single DCI format.

14. A base station BS, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: Transmitting a downlink control information DCI format for scheduling multiple physical uplink shared channels PUSCH on multiple cells of a user equipment UE; and The first PUSCH is received from the UE in response to a successful channel access procedure for the first PUSCH among the multiple PUSCHs, wherein the channel access procedure for the first PUSCH is performed by the UE according to a channel access type and a channel access priority category CAPC value, and wherein a cyclic prefix extension CPE is transmitted by the UE before the first PUSCH.

15. A method performed by a user equipment UE, comprising: receiving, from a base station BS, a downlink control information DCI format for scheduling a plurality of physical uplink shared channels PUSCH on a plurality of cells of the UE; determining a channel access type, a channel access priority class CAPC value, and a cyclic prefix extension CPE length for each of the plurality of PUSCHs; performing a channel access procedure for each of the plurality of PUSCHs according to the determined channel access type and CAPC value; and In response to a corresponding channel access procedure for a first PUSCH among the plurality of PUSCHs being successful, a CPE having a duration equal to the determined CPE length of the first PUSCH and the first PUSCH are transmitted to the BS.

Images