52. Channelization and LBT for 52.6 GHz and above NR unlicensed bands

Abstract

Methods, systems, and devices can facilitate channelization and LBT for NR unlicensed bands. This can apply to NR-U from 52.6 GHz to 71 GHz and above. In one example, a method can include configuring a listen-before-talk (LBT) bandwidth (BW) and channel occupancy time (COT) sharing scheme when there is a simultaneous channel BW for other radio access technologies (RATs) for NR-U from 52.6 GHz to 71 GHz and above, and performing LBT for each component carrier (CC) when an LBT or resource block (RB) set BW is set equal to each CC BW or transmission BW, a primary cell (PCell), a primary secondary cell (PSCell), or a scheduling secondary cell (SCell) can coordinate scheduling other CCs’ LBT results.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 048,854, filed July 7, 2020, entitled “Channelization and LBT for NR Unlicensed Band From 52.6GHz and Above,” the contents of which are incorporated herein by reference. Background Technology

[0003] Version 16NR-U

[0004] In Release 16 New Radio Unlicensed (NR-U), the supported digitization (i.e., SCS) can be set to 15 kHz, 30 kHz, or 60 kHz within Frequency Range 1 (FR1). This is because 802.11 channels can be 20 MHz, 40 MHz, 80 MHz, and 160 MHz below 7 GHz. Therefore, the pre-talk listening (LBT) bandwidth is set to 20 MHz in Release 16 NR-U. Based on the minimum LBT bandwidth that must be supported, the initial BWP for the DL in Release 16 NR-U is nominally 20 MHz. The maximum supported channel bandwidth is set to 100 MHz. The UE channel bandwidth (or active BWP) can be set to an integer multiple of the LBT bandwidth (i.e., 20 MHz) in Frequency Range 1 (FR1), as shown in Table 1. For example, for SCS = 30 kHz, the total number of PRBs allocated for 20 MHz, 40 MHz, and 80 MHz bandwidths are equal to 48, 102, and 214, respectively.

[0005] Table 1 shows the numeric / SCS supported in version 16NR-U.

[0006] numerology μ = 0 μ = 1 μ = 2 Subcarrier spacing (SCS) [kHz] 15 30 60 Sampling frequency [MHz] 61.44 122.88 245.76 Maximum FFT size 4096 4096 4096 Maximum number of PRBs 270 273 264 Maximum allocated bandwidth [MHz] 48.6 98.28 190.08 Maximum channel bandwidth [MHz] 50 100 200

[0007] In version 16, DCI format 2_0 introduces notifications of COT duration, available RB set, and search space group switching. The size of DCI format 2_0 can be configured by higher layers up to 128 bits. The following information is transmitted via DCI format 2_0 with a CRC scrambled by SFI-RNTI:

[0008] -Slot format indicator 1, slot format indicator 2, ..., slot format indicator N.

[0009] -If the higher-level parameter availableRB-SetPerCell-r16 is configured,

[0010] - Available RB set indicator 1, available RB set indicator 2, ..., available RB set indicator N1,

[0011] -If the higher-level parameter COT-DurationPerCell-r16 is configured

[0012] -COT duration indicator 1, COT duration indicator 2, ..., COT duration indicator N2.

[0013] - If the higher-level parameter searchSpaceSwitchTrigger-r16 is configured

[0014] -Monitor group marker 1, monitor group marker 2, ..., monitor group marker [M].

[0015] In version 16NR-U, the PRB allocated by frequencyDomainResources in the CORESET configuration is restricted to one LBT bandwidth within the LBT bandwidth of the BWP corresponding to the CORESET. In this way, the PDCCH is restricted to the LBT bandwidth to avoid partial puncturing of the DCI. After learning the transmission LBT bandwidth from the GC-PDCCH, the UE can stop monitoring the PDCCH search space that is unavailable on the LBT bandwidth. Within the search space set configuration associated with the CORESET, each of one or more monitoring locations in the frequency domain corresponds to (and is restricted to) the LBT bandwidth and has a frequency domain resource allocation pattern copied from the pattern configured in the CORESET. In this way, the CORESET parameters, except for the frequency domain resource allocation pattern, are the same for each of one or more monitoring locations in the frequency domain.

[0016] 802.11ad and 802.11ay

[0017] Wireless Gigabit—WiGig (IEEE 802.11ad)—is a technology for achieving short-range wireless connections of up to 6.75 Gbps. The IEEE 802.11ad physical layer uses 2.16 GHz wide channels, theoretically providing data rates of up to 6.76 Gbps per single channel. WiGig signals operate in the 60 GHz band (57 GHz–66 GHz), which varies slightly in specifications around the world. To compensate for path loss, IEEE 802.11ad devices use high-gain antenna arrays. WiGig allows the use of four wide channels, each approximately 2.16 GHz wide, supporting both OFDM (for longer distances and higher data rates) and single-carrier (for low-power handheld devices) modulation schemes. Utilizing such wide channels enables data rates up to three times faster than today's Wi-Fi speeds.

[0018] IEEE 802.11ay is an enhanced specification of 802.11ad. The unlicensed frequency band allocated around 60 GHz has a bandwidth of approximately 14 GHz, which is divided into channels with bandwidths of 2.16 GHz, 4.32 GHz, 6.48 GHz, and 8.64 GHz. The 2.16 GHz and 4.32 GHz channel bandwidths are mandatory. Figure 1 As shown, for channel numbers 1 to 6, the center frequencies of the 2.16 GHz channels are 58.32 GHz, 60.48 GHz, 62.64 GHz, 64.80 GHz, 66.96 GHz, and 69.12 GHz, respectively. Unlike IEEE 802.11ad, which only allows transmission on a single (2.16 GHz) channel, 802.11ay includes mechanisms for channel bonding and aggregation. Thus, 802.11ay allows channel access on multiple channels. When using multiple channels, an access point (AP) can simultaneously transmit to multiple stations (STAs) assigned to different channels. In channel bonding, a single waveform covers at least two consecutive 2.16 GHz channels, while channel aggregation has a separate waveform for each aggregated channel. IEEE 802.11ay mandates that Enhanced Directed Multi-Gigabit (EDMG) stations (STAs) must support operation on 2.16 GHz channels and channel bonding of two 2.16 GHz channels. Channel bonding typically refers to combining multiple consecutive channels into a single wideband channel, without channel spacing (or guard bands) between the channels. It can be used as an entire frequency band to form a single (wider) channel, such as... Figure 2A As shown in Figure 2(b). Conversely, channel aggregation is typically used as a combination of two or more contiguous or discontinuous channels, and regardless of whether the channels are contiguous or discontinuous, there is a channel spacing or guard band between these aggregated channels. In 802.11ay, channel aggregation of two 2.16 GHz or two 4.32 GHz (contiguous or discontinuous) channels, as shown in Figure 2(b), and aggregation of three or four 2.16 GHz channels are optional. Multichannel operation can significantly improve channel utilization efficiency.

[0019] In 802.11ay, a 512 FFT size, along with a 5.15625 MHz SCS, is used to achieve a channel bandwidth of 2.16 GHz. This channel bandwidth can be extended to a maximum continuous bandwidth of up to 4.32 GHz using channel bonding. The 802.11ay sampling rate can be expressed as 512 × N. CB ×5.15625MHz, where N CB=1,2. The sampling frequency of 802.11ay must be greater than 5.28 GHz. 802.11ay supports high QAM modulation such as 64QAM modulation, therefore requiring a sampling bits per second (SBPS) of up to 42.24 Gsbps (e.g., 42.24 Gsbps = 8 bits / sample, and the sampling rate equals 5.28 gigabits per second). This high sampling rate and high number of bits per sample pose design challenges for WiFi 802.11ad / ay. Therefore, NR-U from 52.6 GHz to 71 GHz and above requires consideration of sampling strategies.

[0020] The rules for 802.11ad channels are as follows: For both OFDM and single-carrier modulation, the spectral shielding of 802.11ad is maintained at 0 dBBr up to + / -0.94 GHz, and the first breakpoint at -20 dBBr occurs at + / -1.2 GHz. The maximum permissible transmitter power varies by country, but generally +10 dBm can be considered a practical limit.

[0021] NR channel bandwidth (BW), guard band, and channel aggregation

[0022] In NR, the relationship between channel bandwidth, guard band, and maximum transmission bandwidth configuration is as follows: Figure 3 As shown in the diagram. The UE channel bandwidth supports a single NR RF carrier in either the uplink or downlink at the UE. Figure 3 In this context, the network (e.g., gNB) determines the active resource block for the actual resources (e.g., transport BW) used for transmission. In practice, the maximum transport BW is equal to the transport BW configured.

[0023] For a given channel bandwidth, the guard band value varies with the supported SCS. For example, when the channel bandwidth is 100 MHz, the (minimum) guard band is 2450 kHz when the SCS is 60 kHz, and the guard band is 2420 kHz when the SCS is 120 kHz, as shown in Table 3[4] ([4] refers to 3GPP TS 38.101-2 User Equipment (UE) Radio Transmission and Reception; Part 2: Range 2 Independent (Version 16), V16.2.0). The minimum guard band has been calculated using the following equation:

[0024]

[0025] Where N RB Given from Table 2[4]. Note that in Equation 1, BW channel The units for SCS are based on kHz.

[0026] Table 2: UE channel bandwidth, transmission bandwidth, and SCS (kHz) in FR2 .

[0027]

[0028] Table 3: Minimum Guard Bandwidth for Each UE Channel Bandwidth and SCS (KHz) in FR2 .

[0029]

[0030] In NR, for a given channel bandwidth BW channel， When the subcarrier spacing (SCS) is doubled, the number of available resource blocks (i.e., N) RB (Proportionally reduced by half or more than half. For example, according to Table 2, for BW) channel =100MHz (e.g., 100000KHz), when SCS = 60kHz, N RB =132, and N when SCS = 120kHz RB =66.

[0031] Four main types of carrier aggregation have been defined in 3GPP to meet the spectrum scenarios of different operators.

[0032] ●In-band continuous carrier aggregation

[0033] ●In-band discontinuous carrier aggregation

[0034] ●Inter-band continuous carrier aggregation

[0035] ●Inter-band discontinuous carrier aggregation

[0036] For in-band contiguous carrier aggregation with two or more component carriers, the nominal channel spacing between two adjacent NR component carriers is defined as follows:

[0037] For example, in frequency range 2 (FR2) [4], for the NR operating band with a 60 kHz channel grating:

[0038]

[0039] Where n = μ0 - 2 and μ0 = max{μ channel(1) μ channel(2)}

[0040] For in-band continuous CA, the UE's CA bandwidth category is determined by the number of CCs they support and the number of aggregated resource blocks (N). RB The corresponding aggregated transmission bandwidth is defined.

[0041] This background information is provided to disclose information that the applicant deems potentially relevant. It is not necessary to acknowledge, nor should it be construed, that any of the aforementioned information constitutes prior art. Summary of the Invention

[0042] This paper discloses methods, systems, and devices that can facilitate channelization and LBT in unlicensed NR bands. For example, this can be applied to NR-U from 52.6 GHz to 71 GHz and above.

[0043] In one example, the channelization method and guard band configuration can be used for (in-band) carrier aggregation, and the aggregated channel bandwidth is an integer multiple of the channel bandwidth B (e.g., 2.16) GHz of other RATs. Furthermore, in another example, the channelization method and guard band configuration can be (in-band) carrier aggregation, and the reused legacy NR channel BW and aggregated channel bandwidth are not integer multiples of the channel bandwidth B (e.g., 2.16) GHz of other RATs.

[0044] In another example, this document discloses an LBT and COT sharing scheme when the channel BW (e.g., B) of other RATs is an integer multiple of the RB set size, such as the LBT bandwidth of NR-Us from 52.6 GHz to 71 GHz and above. Furthermore, in another example, this document discloses an LBT and COT sharing scheme when the channel BW of other RATs is (almost) equal to the RB set size of NR-Us from 52.6 GHz to 71 GHz. (Almost equal to B) This refers to the maximum supported channel bandwidth within B.

[0045] The purpose of providing this summary is to introduce selected concepts in a simplified form, which are further described in the following detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to addressing any or all of the shortcomings pointed out in any part of this disclosure. Attached Figure Description

[0046] A more detailed understanding can be obtained from the following description, given by way of example in conjunction with the accompanying drawings, in which:

[0047] Figure 1 An exemplary 802.11ay channelization scheme is shown;

[0048] Figure 2A An example of 802.11ay multichannel allocation channel bonding is shown;

[0049] Figure 2B An exemplary 802.11ay multichannel allocation channel aggregation with the primary channel (PCH) is shown;

[0050] Figure 3 An exemplary definition of the channel bandwidth and maximum transmission bandwidth configuration for an NR channel is shown;

[0051] Figure 4 An exemplary definition of the aggregation channel bandwidth for in-band carrier aggregation is shown;

[0052] Figure 5A An exemplary aggregation channel BW with continuous intra-band CC is shown at B = 2.16 GHz;

[0053] Figure 5B Exemplary aggregation channels (BW) with consecutive intraband CCs are shown in each cell group, and different cell groups have non-consecutive CCs;

[0054] Figure 5C An exemplary aggregation channel BW with in-band non-continuous CC is shown, and for NR-U from 52.6 GHz to 71 GHz and above, a portion of the aggregation channel BW is B = 2.16 GHz;

[0055] Figure 6 An exemplary five CCs with consecutive in-band CAs are shown, and the lowest CCj=1 and / or the highest CCj=5 can reserve (additional) guard bands;

[0056] Figure 7A An exemplary guard band configuration is shown: In-band continuous CA within bandwidth B: lowest CC1 and highest CC J (e.g., J=3), the lowest CC1 channel BW is equal to two LBT BW (or two RB set sizes), and the highest CC J is configured with one LBT BW (or RB set size);

[0057] Figure 7B An exemplary guard band configuration is shown: multiple CCs are arranged in LBT BW / RB set sizes (e.g., Aggregation, and channels for each CC.

[0058] Figure 8 This shows when the channel BW bandwidth is based on multiples of integers and (a) 1 RB set (b) 2 RB sets (3) 3 RB sets (4) 4 RB sets) Exemplary guard band configurations for RB sets;

[0059] Figure 9 This shows that when the aggregation channel BW bandwidth is based on multiples of integers and (a) Example guard band configuration for RB sets when there is 1 RB set (b) 2 RB sets;

[0060] Figure 10 This shows that when the aggregation channel BW bandwidth is based on multiples of integers and An example guard band configuration used for RB sets;

[0061] Figure 11A An exemplary multi-channel cell allocation for a UE is shown, and the channel BW or aggregated channel BW is limited to a channel cell: two channel cells and LBT BW = 0.4 GHz;

[0062] Figure 11B An exemplary multi-channel cell allocation for a UE is shown, and the channel BW or aggregated channel BW is limited to a channel cell: two channel cells and LBT BW = 2 GHz;

[0063] Figure 12 This shows an exemplary LBT result when a gNB initiates an LBT and multicasts to a UE;

[0064] Figure 13 This shows an exemplary LBT result multicast to the UE when the gNB initiates an LBT, as well as the coordinated scheduling when the gNB initiates an LBT.

[0065] Figure 14 An exemplary LBT is shown, which utilizes wideband operation and carrier aggregation to multicast to the UE when the gNB initiates an LBT.

[0066] Figure 15 An exemplary LBT result is shown, which uses broadband operation to multicast to the UE when the gNB initiates an LBT.

[0067] Figure 16 An exemplary LBT result is shown, which uses broadband operation to multicast to the UE when the gNB initiates an LBT.

[0068] Figure 17 Exemplary displays (e.g., graphical user interfaces) that can be generated based on methods, systems, and devices for channelization and LBT for unlicensed NR bands of 52.6 GHz and above are shown.

[0069] Figure 18A An exemplary communication system is shown;

[0070] Figure 18B An exemplary system including the RAN and core network is shown;

[0071] Figure 18C An exemplary system including the RAN and core network is shown;

[0072] Figure 18D An exemplary system including the RAN and core network is shown;

[0073] Figure 18E Another exemplary communication system is shown;

[0074] Figure 18F This is a block diagram of an exemplary device or apparatus (such as a WTRU);

[0075] Figure 18G This is a block diagram of an exemplary computing system; and

[0076] Figure 19 An exemplary method for channelization and LBT for NR is shown.

[0077] Detailed implementation description

[0078] Statement 1

[0079] For NR from 52.6 GHz to 71 GHz, the supported channel bandwidth can be {400, 800, 1600, 3200, ...} MHz. The NR channel bandwidth is calculated based on a maximum Fast Fourier Transform (FFT) size of 4096 (the same as in versions 15 / 16), where the scalable subcarrier spacing is {120, 240, 480, 960, 1920, ...} kHz. However, the WiFi 802.11ad / ay channel bandwidth can be an integer multiple of 2.16 GHz (e.g., 2.16 GHz, 4.32 GHz, 6.48 GHz, and 8.64 GHz), and it is not the typical channel bandwidth consistent with that used in traditional NR. Regardless of whether the LBT bandwidth B (e.g., B = 2.16) GHz is used for unlicensed NR (NR-U) LBT operations from 52.6 GHz to 71 GHz, a channelization approach needs to be addressed to support the coexistence of NR-U with other RATs (e.g., 802.11ad / ay) from 52.6 GHz to 71 GHz to meet regulatory requirements, achieve better spectrum utilization, and reduce co-channel interference. This is because there should be a method for devices to identify situations where the NR RAT overlaps with other RATs (e.g., 802.11).

[0080] This document discloses in more detail channelization methods and guard band configurations for: 1) (in-band) carrier aggregation, wherein the aggregated channel bandwidth is an integer multiple of the channel bandwidth B (e.g., 2.16) GHz of other RATs; or 2) (in-band) carrier aggregation, wherein the reused conventional NR channel BW and the aggregated channel bandwidth are not an integer multiple of the channel bandwidth B (e.g., 2.16) GHz of other RATs.

[0081] Statement 2

[0082] In version 16NR-U, LBT can be performed in 20MHz increments. Furthermore, LBT can be performed on a single carrier with a bandwidth greater than 20MHz (e.g., an integer multiple of 20MHz). In other words, the channel bandwidth can be an integer multiple of 20MHz in version 16NR-U. This condition can be met for the frequencies supported in Frequency Range 1 (FR1) (e.g., SCS = 15kHz, 30kHz, and 60kHz). However, assuming an LBT channel bandwidth of 2.16GHz as in WiFi 802.11ad / ay, for some supported frequencies (e.g., when the maximum BW...), channel =400MHz, SCS=120KHz; when the maximum BW channel =800MHz, SCS=240KHz; and when the maximum BW channel When the frequency is 1600MHz and the SCS is 480KHz, the condition that the channel bandwidth must be an integer multiple of the LBT channel bandwidth cannot be met.

[0083] If NR-U from 52.6 GHz to 71 GHz and above allows channel bandwidths smaller than the nominal channel bandwidth of WiFi 802.11ad / ay (2.16 GHz) (e.g., 400 MHz, 800 MHz, 1600 MHz), then the LBT method discussed in Release 16 NR-U cannot be directly applied to this condition. More specifically, the minimum supported channel bandwidth (BW) is 20 MHz, and LBTBW is defined as 20 MHz in Release 16 NR-U. However, the channel bandwidth (BW) of other RATs (e.g., B = 2.16 GHz) is wider than the NR-U channel bandwidths considered from 52.6 GHz to 71 GHz (e.g., 100 MHz, 200 MHz, 400 MHz, 800 MHz, 1600 MHz). Therefore, when the smaller channel BW used for NR-U from 52.6 GHz to 71 GHz and above is smaller than the channel BW B of other RATs (e.g., 802.11ad / ay) (e.g., B = 2.16 GHz), it is necessary to address the LBT subband indication and channel occupancy time (COT) sharing method.

[0084] This article discloses in more detail the LBT and COT sharing schemes in the following situations.

[0085] ○ The channel BW (e.g., B) of other RATs is an integer multiple of the RB set size (e.g., the bandwidth of the LBT of NR-U from 52.6 GHz to 71 GHz and above).

[0086] ○ The channel BW of other RATs is (almost) equal to the RB set size used for NR-U from 52.6 GHz to 71 GHz. (Almost equal to B) This refers to the maximum supported channel bandwidth within B.

[0087] Channelization details

[0088] Channelization methods for NR-U from 52.6 GHz to 71 GHz and above

[0089] The (minimum) channel bandwidth of 802.11ad / ay is equal to 2.16 GHz. The LBT bandwidth of NR-U from 52.6 GHz to 71 GHz can depend on the following factors: 1) WiFi 802.11ad / ay channel BWB = 2.16 GHz or the bandwidth occupied by the WiFi 802.11ad / ay channel; 2) NR channel BW with digital support from 52.6 GHz to 71 GHz and above.

[0090] NRs at 52.6 GHz and above should support generalized scalable digitization (SCS) for frequency range 1 (FR1 (below 7 GHz)) and frequency range 2 (FR2 (24 GHz–52.6 GHz) as defined in Releases 15 and 16. Accordingly, the scalable SCS in the NR can be represented as a scalable subcarrier spacing factor, such as 2... μ Δf, where Δf = 15 kHz, is the minimum subcarrier spacing used in NR frequency range 1 (e.g., FR1) where μ = 0, 1, 2 and FR2 where μ = 3, 4. Another factor used to determine the supported SCS for NR from 52.6 GHz to 71 GHz is phase noise (PN), especially for higher quadrature modulation (QAM), such as 64QAM and 256QAM. In practice, a larger SCS can mitigate PN and improve demodulation performance. Therefore, the subcarrier spacing for NR from 52.6 GHz to 71 GHz and above can be considered to be increased compared to the SCS supported in the FR1 and FR2 bands. Based on the conventionally supported channel bandwidths in FR1 and FR2, the corresponding SCS and channel bandwidth (BW) that may support the digitization in the 52.6 GHz–71 GHz band are derived, as shown in Table 4:

[0091] Table 4: Potentially Supported Digital Technologies for NR from 52.6 GHz to 71 GHz

[0092]

[0093] However, supporting larger channel bandwidth may also reduce coverage. This is because thermal noise power increases with a factor of 10log(BW). channelThe bandwidth increases by dB. For digital μ = 3, 4, and 5, the corresponding SCS are 120 kHz, 240 kHz, and 480 kHz, respectively. Conversely, if a smaller channel bandwidth (BW) is considered, better coverage can be achieved compared to using a larger channel bandwidth (BW). For a smaller channel bandwidth (BW), assuming a fixed maximum FFT size, SCSs of 120 kHz, 240 kHz, and 480 kHz can also be used. However, for digital μ = 3, 4, and 5, the maximum supported channel bandwidth (BW) is [not specified in the original text]. channel (As shown in Table 4) is less than the LBT bandwidth, for example, B = 2.16 GHz.

[0094] In Release 16 NR-U, three operations utilizing carrier aggregation (CA) are discussed. The first operation is carrier aggregation between a licensed NR primary cell (PCell) and an NR-U secondary cell (SCell). The second operation is dual connectivity (DC) between a licensed LTE (PCell) and an NR-U primary / secondary cell group (PSCG). The third operation is for standalone NR-U. Release 16 NR-U supports an operating mode where, for the carrier and at least for the serving cell on unlicensed bands, in-band CA, DL, and UL channels / signals can only be operated using the same digits. Additionally, wideband operation (in multiples of 20 MHz) for DL ​​and UL in NR-U is supported by both multiple aggregated serving cells and a single serving cell with a bandwidth > 20 MHz.

[0095] Similarly, for NR-U from 52.6 GHz to 71 GHz and above, carrier aggregation can be supported. The UE can simultaneously receive or transmit on one or more component carriers (CCs) depending on its capabilities. Here, carrier aggregation (CA) refers to aggregating two or more component carriers (CCs), and for NR-U from 52.6 GHz to 71 GHz and above, CA is supported for both continuous and discontinuous CCs (in-band or inter-band). Support for both continuous and discontinuous aggregated CCs can be analogous to scenarios where channel access opportunities do not need to be continuous but can be distributed from 52.6 GHz to 71 GHz and above. Furthermore, for NR-U channelization from 52.6 GHz to 71 GHz and above, CA is advantageous for using smaller numerators, such as μ = 3, 4, and 5.

[0096] This document discloses several options for NR-U channelization from 52.6 GHz to 71 GHz and above. Option 1: Use (in-band) carrier aggregation with the aggregated channel bandwidth consistent with an integer multiple of B (e.g., 2.16) GHz. Option 2: Use (in-band) carrier aggregation, reuse the legacy channel BW, and the aggregated channel bandwidth is not consistent with an integer multiple of B (e.g., 2.16) GHz.

[0097] Carrier aggregation is used, and the aggregation channel bandwidth is an integer multiple of B.

[0098] The disclosed subject matter corresponds to the use of multiple component carriers (CCs). The number of aggregated component carriers (or cells) can depend on the capabilities of the UE. It is disclosed herein that the channel bandwidth of the CC (e.g., <B or ≥B) can have carrier aggregation, and the aggregated channel bandwidth can have an integer multiple of B’ (e.g., 2.16 GHz) to account for coexistence with other RATs (e.g., 802.11ad / ay).

[0099] The UE can be configured with one cell group or multiple cell groups and is allowed to transmit and receive simultaneously within the same cell group. Each cell / component carrier in the cell group can be configured for TDD or DL / UL cells. The slot format can be indicated by DCI format 2_0 as version 16 NR-U. The slot format can be indicated independently for each CC / cell in the cell group. For each cell group, the aggregated channel bandwidth can be an integer multiple of, where M is a positive integer. It can allow one or more aggregated cells (or component carriers), and each channel bandwidth can be equal to BW channel = an integer multiple of, where M is a positive integer. For NR-U from 52.6 GHz to 71 GHz and above, the minimum numerology for CA is μ = 3 (e.g., SCS = 120 kHz).

[0100] For example, the supported numerologies and the channel bandwidths (integer multiples of B) for the aggregated channel BW are shown in Table 5. Different from the channel BW shown in Table 4, the disclosed channel BW B W channel presented in Table 5 is consistent with an integer multiple of B.

[0101] Table 5: Digital and Channel Capabilities Supported by NR from 52.6 GHz to 71 GHz, Considering the Aggregated Channel BW BW can be an integer multiple of B.

[0102]

[0103] For example, the UE is configured with a cell group (in-band CA) and the aggregated channel bandwidth is equal to B, as Figure 5A shown. In Figure 5A , three in-band component carriers (CCs) / cells are aggregated. The first CC channel BW is configured to 432 MHz, where μ = 3 (SCS = 120 KHz), and the other two CC channel bandwidths are equal to 864 MHz, where μ = 4 (SCS = 240 KHz). The aggregated CC is within the frequency range of WiFi channel 2 from 59.4 GHz to 61.56 GHz. As Figure 5A shown, the aggregated channel bandwidth is equal to 2.16 GHz.

[0104] The second example demonstrates a UE configured with two cell groups (in-band CAs), such as... Figure 5B As shown. In cell group 1, the CCs are contiguous CAs within the band, and five CCs (each CC channel BW is 400MHz, where SCS = 400MHz) are aggregated in cell group 1. In cell group 2, five CCs (each CC channel BW is 400MHz, where SCS = 400MHz) are also aggregated in cell group 2. The aggregated CCs in cell group 1 are in the frequency range of WiFi channel 2 from 59.4GHz to 61.56GHz, and the aggregated CCs in cell group 2 are in the frequency range of WiFi channel 4 from 63.72GHz to 61.56GHz. Cell groups 1 and 2 have non-contiguous CAs within the band. Figure 5B As shown, the aggregation channel BW is equal to 4.32 GHz.

[0105] The third example shows that the UE is configured with a cell group (in-band continuous / discontinuous CA), such as Figure 5C As shown. In Figure 5C In this configuration, three in-band component carriers (CCs) / cells are aggregated. The channel BW of the CCs is configured at 432 MHz, where μ = 3 (SCS = 120 kHz). The aggregated (e.g., continuous or discontinuous) CCs are distributed within the frequency range of WiFi Channel 2 from 59.4 GHz to 61.56 GHz. Figure 5C As shown, the aggregation channel BW is equal to 3 / 5 of 2.16 GHz.

[0106] It can be based on transmission bandwidth (e.g., N) RB ×SCS) and BW channel The default (or pre-configured) guard band for the channel BW is calculated as described in Equation 1. Furthermore, the guard band information for aggregated CCs / cells is further considered when needed, allowing the UE to determine the number of available PRBs in the transmission band of the CC / cell. This is because WiFi 802.11ad supports channel aggregation, and 802.11ay supports both channel binding and aggregation. Therefore, the NR-U UE can increase spectral efficiency and reduce interference with the availability of guard band information. More specifically, the NR-U channel BW is considered to be consistent with an integer multiple of B (e.g., 2.16 GHz). The channel BW is already increased compared to the classic / traditional channel BW supported in NR. Note: The actual transmission BW can be increased to improve spectral efficiency.

[0107] Let us denote the classical / traditional channel BW = B associated with a specific numeral μ (e.g., μ = 3). 1，μ (For example, B) 1，μ =400MHz), then the classic / traditional channel BW from B 1，μ Add to channel BW = B′ 1，μ(For example, B′) 1，μ =432MHz) and meets the conditions M is a positive integer (e.g., 2.16 / 0.432 = 5). In the first proposal, N RB Increasing QRB to Q' ≥ Q (e.g., from Q = 264 to Q′ = 285) RB increases spectral efficiency and meets regulatory requirements. In practice, the actual occupied bandwidth (BW) of the 802.11ad / ay primary / secondary channels is 1.76 GHz with guard bands of 0.2 GHz on both sides. Figure 6 As shown. Therefore, for carrier j in NR-U from 56.2 GHz to 71 GHz, the (additional) guard band of the highest component carrier and / or the lower edge of the lowest carrier component can be configured, as shown. Figure 6 As shown. In Figure 6 In the given information, there exist five consecutive CCs with in-band CAs, and the channel BW of each CC is equal to 432MHz (satisfying the condition). In this example, the lowest CCj = 1 and the highest CCj = 5. The lowest and highest channel edges are equal to the lower and upper edges of the aggregation channel, respectively. Figure 6 As shown. Therefore, the lowest CCj=1 and / or the highest CCj=5 can be configured to reserve (additional) guard bands (note: guard band units are based on RBs) to reduce interference to other RATs (e.g., 802.11ad / ay).

[0108] In version 16NR-U, the UE can determine the number of RB sets in a cell (corresponding to integer multiples of 20 MHz) and the guard band information for each RB set i. The guard band information for each RB set in the cell is configured by RRC. However, the version 16NR-U RRC configuration for the guard band information for each RB set (e.g., LBT BW = 20 MHz) cannot be directly applied to NR from 52.6 GHz to 71 GHz and above. This is because when NR-U from 52.6 GHz to 71 GHz is considered to coexist with other RATs (e.g., 802.11ad / ay), the LBT bandwidth may have conditions as shown in the following cases (e.g., case 1 or case 2 below).

[0109] Case 1: The LBT BW of NR_U from 52.6 GHz to 71 GHz and above is set as a fraction of B (e.g., 2.16 MHz), for example, LBT BW represents Where M (note: M can be equal to 1) is a positive integer, and for NR-U from 52.6 GHz to 71 GHz and above, the channel BW supported by any component carrier cannot be less than (or equal to) B′. A CC with its channel BW can be an integer multiple of B′. The RB set size is equal to LBT BW. The channel BW of a CC can be equal to the RB set size (i.e., B') or an integer multiple of B'.

[0110] Case 2: Channel BW is set to The bandwidth (or LBT BW) of the RB set size is a multiple of NB' GHz, where M is a positive integer and B is the 802.11ad / ay channel BW. B_CAP = NB' GHz, where N is a positive integer. For example, let M = 4, then the supported channel BW is... If N is an integer multiple of N, and N = 4, then LBT BW equals

[0111] This document discloses the following options for guard band configuration based on Case 1 and Case 2:

[0112] ●The description of the protected frequency band information can be defined as {GB offset，i，j GB len，i，j}, where i represents the i-th guard band in component carrier j. GB offset，i，j Is with N RB，low The offset (denoted by CRB), where N RB，low This is the transmission bandwidth configuration for the lowest allocated component carrier. (GB) len，i，j This refers to the guard band length in units of RBs. Guard band configurations can be provided for each CC / cell separately for DL ​​and UL. The number of guard band configurations for each CC / cell is represented by N. j (For example, N) j =1), and the total number of aggregated CCs / cells is represented as J.

[0113] ○ If intraCellGuardBandDL-r17 or intraCellGuardBandUL-r17 is given, then the UE is determined.

[0114] ■For j = 1 to J

[0115] For i = 1 to N j

[0116] Configuration based on guard band i {GB offset，i，j GB len，i， , j Available PRB in CC / cell. When {GB offset，i，j GBlen，i，j When} is set to {0, 0}, no additional guard band needs to be reserved.

[0117] ○ If intraCellGuardBandDL-r17 and / or intraCellGuardBandUL-r17 are not configured for CC, the protection band is derived from a predefined specification (e.g., based on a predefined / preconfigured N). RB SCS and BW channel Equation 1).

[0118] Figure 7A An example of guard band configuration 1 is shown, where the bandwidth of the RB set is defined as a fraction of B (e.g., ),and This is the minimum support channel width (BW) for NR-U from 52.6 GHz to 71 GHz. For example... Figure 7A As shown, there exist J (e.g., J = 3) CCs with in-band consecutive carrier aggregation, and the aggregation channel BW equals B. The lowest carrier CC 1 channel BW equals two LBT BWs, and the highest CC J = 3 channel BW equals the LBT BW, as shown. Figure 7A As shown. In this example, the total number of RB sets with the lowest CC 1 is M1 = 2, and the highest CCJM J＝3 =1. The UE can determine the number of RB sets used for each CC.

[0119] When the bandwidth of the LBT BW / RB set size is equal to B_CAP and as... Figure 7B As shown, when aggregating multiple CCs within the LBT BW / RB set size, then as follows: Figure 7B The diagram shows the application of guard band configurations for the lowest carrier with a lower edge and the highest carrier with an upper edge.

[0120] When multiple consecutive 802.11ad / ay channels are available, a guard band between two consecutive channels may not be necessary. Therefore, this document discloses that the enabling or disabling of a guard band for a CC / cell can be indicated by a DCI (DCI format 20). When a bit in the guard band indicator (bit mapper, the length of which depends on the amount of guard band information for each CC / cell) is set to "1" (e.g., enabled) or "0" (e.g., disabled), the UE can determine the indication of the corresponding configured guard band. Note:

[0121] - If the higher-level parameter intraCellGuardBand(DL / UL)-r17 is configured, the following list shows the indicators for enabling or disabling the protection band:

[0122] - Guard band indicator 1, guard band indicator 2, ..., guard band indicator J, where J is the total number of aggregated CCs / cells in the cell group.

[0123] Carrier aggregation is used, and the aggregation channel bandwidth is not an integer multiple of B.

[0124] The rule mandates the use of LBT in Europe and Japan, but not in the United States. Therefore, the methodology used for channel bandwidth design (e.g., as shown in Table 4) in NR can be reused for coexistence with other RATs (e.g., 802.11ad / ay), regardless of whether LBT is mandatory for NR from 52.6 GHz to 71 GHz and above. The channel bandwidth design methodology for the NR rule is essentially determined by the supported digitization, FFT size, spectral efficiency, and rule requirements. In version 16NR-U, the LBT bandwidth / RB set is set to 20 MHz, and the NR channel bandwidth can be an integer multiple of the LBT bandwidth / RB set.

[0125] The channel bandwidth (BW) supported by NR from 52.6 GHz to 71 GHz may not need to be an integer multiple of the channel BW used by WiFi 802.11ad / ay. For example, based on the design principles from Table 4, Table 6 lists the possible supported channel BWs. In Table 6, the possible supported bandwidths can range from 200 MHz, 400 MHz, 800 MHz to 4000 MHz, etc. However, when the supported channel BWs in Table 6 do not precisely coincide with other RATs (e.g., 802.11ad / ay), co-channel interference (e.g., out-of-band transmission) may occur. Therefore, it is necessary to disclose certain methods for resolving interference from coexistence with other RATs.

[0126] Table 6 shows the channels that may be supported: BW Digital / SCS.

[0127]

[0128] The following is a method for considering coexistence with other RATs (e.g., 802.11ad / ay) where the channel bandwidth or aggregated channel bandwidth (which may be less than B or greater than or equal to B) does not need to be an integer multiple of B (e.g., 2.16 GHz). Consider the following case.

[0129] Case 1: For NR-U ranging from 52.6 GHz to 71 GHz and above, the channel BW and / or aggregated channel BW is the size of the LBT BW / RB set. The BW of any CC is an integer multiple of the channel width and height and is greater than or equal to the channel width and height of the channel width. (For example, LBT BW / RB set size). The channel BW or aggregate BW is an integer multiple of the LBT BW / RB set size. The LBT BW / RB set size can be based on... or fractions (e.g.) Where M is a positive integer). Assuming it is the maximum supported channel bandwidth or the aggregated channel bandwidth within B, it can satisfy the condition. For example, This can be equal to 2 GHz as mentioned in Table 6, and B equals 2.16 GHz. In this case, it is disclosed that the LBT BW can be set to be equal to the channel BW or an integer fraction of the channel BW. For example, the LBT BW (or RB set size) can be set to be equal to its carrier channel BW, so the gNB or UE performs LBT for each active component carrier (CC), as... Figure 8 A to Figure 8 As shown in D. Note: If a transport BW is defined in CC (e.g., ...), Figure 3 The N shown RB,low and N RB,high If the gNB or UE performs LBT for each transmission BW in the CC, then this proposal also applies.

[0130] Case 2: Channel BW is set to A multiple of M, where M is a positive integer, and It is almost equal to the bandwidth (or LBT BW) of the RB set size discussed in case 1. Where N is a positive integer. For example, let M = 10, then the supported channel BW is If N is an integer multiple of N, and N = 10, then LBT BW equals In other words, the LBT BW can span several (or all) CCs, so the gNB or UE can perform LBT for several (or all) CCs. Note: This also applies if a defined transport BW exists for each CC. The gNB or UE performs a single LBT over the transport bandwidth across all CCs (starting from N in the lowest CC). RB,low To be used Figure 3 The highest CC in the transmission shown is N RB,high ).

[0131] Based on the aggregated channel band (BW) and by utilizing appropriate frequency offset settings for the lower edge of the channel, the configured guard band information elements defined in version 16NR can be reused for NR-U from 52.6 GHz to 71 GHz. Therefore, the workload for standard specifications can be reduced.

[0132] For example, four possible channel BW (or aggregated channel BW) configurations for the UE are listed, such as {2, 4, 6, 8} GHz with frequency offsets of {0.08, 0.16, 0.24, 0.32} GHz, etc. Figure 8 A to Figure 8 D and Figure 9 A to Figure 9 As shown in B. The frequency offset is based on the (maximum) channel supported by NR. (e.g., 2GHz) as well as It is calculated using integer multiples of the factor m (e.g., m = 2, 3, ...). Figure 8 A to Figure 8 D and Figure 9 A to Figure 9 As shown in B, by setting an appropriate frequency offset for the starting point of the lower edge of the channel (or aggregated CC), the guard band information configured at the lower and upper edges of each RB set i can be preserved. Figure 9 A to Figure 9 As shown in B, each CC has a 1 GHz channel BW, and the two CCs have consecutive in-band CAs.

[0133] exist Figure 8 A to Figure 8 In B, we first assume that the bandwidth of the RB set is defined as (For example, 2GHz) and it is shown that the disclosed method can also be extended to an RB set size (RB set bandwidth) equal to In the case of M, where M is a positive integer. For example... Figures 11A to 11B As shown, the aggregation channel BW is equal to and And the size of the RB set is equal to

[0134] The guard band configuration method described herein for cases 1 and 2 (e.g., using carrier aggregation with the aggregation channel bandwidth being an integer multiple of B) can be reused in this case. The only modification is to replace B with

[0135] This document discloses the following options for guard band configuration when the channel BW or aggregated channel BW is an integer multiple of the RB set:

[0136] ●Case 1: If the size of the LBT BW / RB set is The fraction or equal to it, that is Where M is a positive integer, the RRC parameters intraCellGuardBandDL-r17 and intraCellGuardBandUL-r17 (if UL is configured) are used to configure the list of in-band / carrier guard band CCs / cells for DL ​​and / or UL, for example:

[0137] ○ The remaining sub-items in this paper that are associated with carrier aggregation and whose aggregation channel bandwidth is an integer multiple of B are reused.

[0138] ●Case 2: If the size of the LBT BW / RB set is For GHz, the RRC parameters intraCellGuardBandDL-r17 and intraCellGuardBandUL-r17 (if UL is configured) are used to configure a list of in-band / carrier guard band CCs / cells for DL ​​and / or UL, for example:

[0139] ○ The remaining sub-items in this paper that are associated with carrier aggregation and whose aggregation channel bandwidth is an integer multiple of B are reused.

[0140] Additionally, the enabling or disabling of the guard band in each RB set can be indicated by a DCI (e.g., DCI format 2_0). The RB set indicator is set to "1" (e.g., enabled) or "0" (e.g., disabled).

[0141] This article discloses another channelization method referred to below as "channel unit".

[0142] Channel unit

[0143] When the channel BW of a CC / cell or the aggregation channel BW of a CC is limited to BW B (e.g., B = 2.16 GHz), the “channel cell” defined herein is as follows. For example, multiple aggregated CCs can be supported in a channel cell, and the aggregation channel BW is limited by the channel bandwidth B (e.g., B = 2.16 GHz). In another example, a channel cell can support in-band contiguous or non-contiguous carrier aggregation.

[0144] like Figure 11A and Figure 11B As shown, multiple channel elements can be configured for a UE. In this way, the channel bandwidth (BW) or aggregated channel bandwidth (BW) of the CC / cell is confined to a channel element. According to the definition of a channel element, no set of RBs can span more than one channel element. The bandwidth of an RB set can be based on... (For example, )or Where M is a positive integer. The guard band configuration method described herein for cases 1 and 2 (e.g., regarding carrier aggregation with the aggregated channel bandwidth being an integer multiple of B) can be reused in this case. The only modification is to replace B with

[0145] like Figure 11A As shown, the UE is configured with two "channel units," and in the first channel unit, three CCs (with two 0.8GHz channel BWs and one 0.4GHz channel BW) are aggregated, and in the second channel unit, two CCs (with 0.8GHz channel BWs) are aggregated. Figure 11A In the example, assume the size of the RB set is equal to... (e.g., 0.4GHz). Therefore, there are 5 RB sets in the first channel unit and four channel units in the second channel unit. In other words, an LBT BW is formed in each CC, and the gNB or UE performs LBT in all LBT units (to be transmitted) in the channel bandwidth of each CC within the channel unit, as follows. Figure 11A As shown. Figure 11A The same CA configuration is applied. Figure 11B However, the size of the RB set is equal to (For example, Therefore, there are three CCs and one RB set in channel unit 1, and two CCs and one RB set in channel unit 2. In this case, LBT BW units can be formed on multiple CCs, and the gNB or UE performs LBT in all LBT units (to be transmitted) within the channel bandwidth of the channel unit.

[0146] LTB schemes and COT sharing for NR from 52.6 GHz to 71 GHz and above

[0147] A UE can be configured with a single or multiple cell groups, and each CC in a cell group can be configured for TDD or FDD. Continuous and discontinuous (in-band) aggregated CCs can be applied in scenarios where channel access opportunities can be continuous for continuous aggregated CCs over a wide bandwidth, and / or dispersed for discontinuous aggregated CCs over a wide bandwidth. Therefore, channel access opportunities can be achieved via continuous and discontinuous carrier aggregation. If LBT is mandated for NR-Us in the 52.6 GHz to 71 GHz and above to achieve coexistence with other RATs (e.g., 802.11ad / ay), the LBT and COT sharing methods need to be considered in conjunction with carrier aggregation, especially when the carrier / channel BW of the aggregated CC is smaller than the channel bandwidth of other RATs (e.g., 802.11ad / ay).

[0148] This paper addresses at least the following cases. For example, case 1: The channel BW of other RATs is an integer multiple of the LBT BW / RB set for NR-U from 52.6 GHz to 71 GHz (almost equal to B). This refers to the maximum supported channel bandwidth B. Note: This is not limited to the number of carriers aggregated in the channel number. The number of aggregated cells can be equal to or greater than 1.

[0149] Case 1 :

[0150] First of all, let Let B represent the LBT BW (RB set size or CC channel / transmission BW) of NR-U, and let B represent the channel BW of other RATs (e.g., 802.11ad / ay), and assume that... make Therefore, η is a positive integer. According to the definition of η, it can be guaranteed that there are at most η RB sets in the channel BW B. For example, when the size of the NR-U RB set... And when B = 2.16 GHz, η = 5. If the gNB or UE initiates LBT, the gNB or UE is responsible for performing LBT based on all or part of channel BW B. If an available channel exists after the gNB performs LBT (e.g., one of WiFi 802.11ad / ay channel numbers 1 to 4), the LBT result for that channel can be multicast or unicast to the UE via DCI format 2_0. When the gNB or UE initiates LBT for a channel number and once the gNB or UE receives the LBT result, if the SCell has self-scheduling, the LBT result can be copied η times, or if the RB set size is equal to the CC channel or transmission BW, the LBT result can be independently based on each RB set or CC.

[0151] For example, the UE is configured with two cell groups. Figure 12 As shown, the first cell group is configured for the channel with channel number 2, and the second cell group is configured for the channel with channel number 4. Each cell group may include five aggregated component carriers, and the channel BW for each CC is equal to 0.4 GHz (or 400 MHz), as shown. Figure 12 As shown. Figure 12As shown, the LBT result (e.g., initiated by the gNB) determines that channel number 2 is available and channel number 4 is busy. Further assuming the RB set size is equal to 0.4 GHz, therefore, when each CC channel / carrier BW equals the RB set size, the LBT result in channel BW B can be replicated (at most) η (e.g., = 5) times. When the network assumes that each CC is configured with self-scheduling (e.g., no cross-scheduling), the UE can monitor each CC individually for its own DCI format 2_0 and other DCI formats, and the gNB can transmit DCI for these CCs.

[0152] When the LBT BW / RB set size or the CC channel BW is smaller than other RAT channel BWs, DCI format 2_0 needs to carry (all) the COT of the configured cell / CC and the RB set information with self-scheduling. The DCI format (e.g., 2_0) can be used to indicate the RB set availability for each CC / SCell in a group of cells with self-scheduling. In this scenario, signaling overhead for COT and RB set availability may be wasted for each CC / SCell with self-scheduling. Therefore, this document discloses that the gNB can transmit COT and RB set availability for CCs / cells within a channel, and not transmit RB set availability to other CCs / cells within the same channel, where a CC / cell within a channel means that the channel edge of the CC is within the channel BW (e.g., as shown in the image). Figure 12 (e.g., CC#1 within channel number 2). Therefore, once the UE receives DCI format 2_0 from a cell in the channel, the UE can apply the COT and RB availability information to other CCs within the same channel number. Otherwise, when the COT information differs between CCs / cells in the same channel, the COT and RB availability can be independent for CCs / cells within the same channel.

[0153] Another approach is for the UE to monitor only the DCI format 2_0 in the primary / secondary cell group (e.g., PCell / PSCell) or scheduling SCell, thus reducing the number of PDCCH monitoring operations. Therefore, cross-scheduling is preferred for NR-U UEs in this scenario for operation in broadband scenarios from 52.6 GHz to 71 GHz and above. Similar to version 16NR-U, the UE needs to frequently monitor COT and LBT results from the GC-PDCCH using the configured CORESET in the PCell / PSCell / scheduling SCell (to reduce lost channel access opportunities). Therefore, the UE can be configured to use a shorter search space period to monitor the DCI format (e.g., 2_0) and then switch to a longer search space period to monitor the UE-specific search space in the PCell / PSCell / scheduling SCell. The UE can monitor the DCI format (e.g., 2_0) in the PSCell / PCell / scheduling SCell, and once a corresponding DCI format (e.g., 2_0) is detected, the UE can switch to monitoring one or more longer-period search spaces for UE-specific PDCCH reception. In other words, after the UE obtains the COT and available RB set indication from the DCI format (e.g., 2_0), the UE can switch to monitoring one or more UE-specific PDCCHs for dynamic scheduling of other non-scheduled SCells. The COT and RB set availability indication can be indicated only for the PSCell / PCell / scheduled SCell, and once the PSCell / PCell / scheduled SCell receives the COT and RB set indication, the UE can apply the received RB set indication to other CCs / cells within the same channel. Therefore, the signaling overhead of LBT results / RB sets can be reduced. Alternatively, when the COT information differs between CCs / cells within the same channel, the COT and RB availability can be indicated independently for each CC / cell within the same channel. In this scenario, the UE still monitors a single GC-PDCCH in the PCell / PSCell / scheduled SCell.

[0154] The maximum number of PDCCHs used for the configured cell group can be based on the carrier aggregation capability of version 17 (e.g., UE-NR-Capability-r17) or it can be based on pdcch-BlindDetectionCA-r17 (e.g., The quantity provided.

[0155] However, PSCell or PCell may be affected by a specific channel already occupied by another RAT (e.g., 802.11ad / ay). Figure 12The LBT result of channel 4) shown is blocked. Therefore, if the UE's (aggregated) channel BW is greater than channel BWB and the UE is configured with a single PSCell or PCell, or scheduling SCell, then when one of the channels is occupied by another RAT and the occupied channel blocks the PSCell / PCell / scheduling SCell used for coordinated scheduling, the UE cannot perform coordinated scheduling PDCCH (including group common PDCCH and UE-specific PDCCH) and PDSCH on the aggregated CC. To overcome this problem, the following method is disclosed.

[0156] In one exemplary method, where a channel refers to a channel number used by another RAT (e.g., 802.11ad / ay), a SCell can be configured for coordinated scheduling within the same channel. In other words, if the UE is allocated m (e.g., m=2) channels (e.g., ... Figure 13 As shown in channels 2 and 4, in this case there are m (e.g., m=2) SCells for coordinated scheduling, and the SCells can be configured to coordinate the scheduling of PDCCH and PDSCH for each assigned channel. Note that the channel edge for scheduling the SCell is within the channel.

[0157] In another exemplary method, the UE can be configured with multiple cell groups, and each cell group is associated with a channel number. One SCell is configured for coordinated scheduling within each cell group. If the UE is configured with m channels, then in this case, m (e.g., m=2) cell groups are configured, and one SCell in each cell group is configured for coordinated scheduling, thus m (e.g., m=2) SCells are used for coordinated scheduling. Note that the channel edge for scheduling the SCell is within the channel.

[0158] For example, such as Figure 13 As shown, the UE is configured with two channels (e.g., one channel has channel number 2 and the other has channel number 4), and within each channel, it has in-band contiguous carrier aggregation, but between channels, it has in-band non-contiguous carrier aggregation. Since the use of each channel must compete with other RATs (e.g., 802.11ad / ay), a serving cell needs to be allocated to each assigned channel for cooperative scheduling purposes. For example, as... Figure 13 As shown, CC1 is configured for coordinating the scheduling of CC2, CC3, CC4, and CC5, and CC6 is configured for coordinating the scheduling of CC7, CC8, CC9, and CC10. If channel 4 is already occupied, the gNB can still perform coordinating scheduling on channel 2.

[0159] This scheme can be extended to cases where the aggregated channel bandwidth (BW) of the UE is greater than B or an integer multiple of B. The channel bandwidth of each CC can be set to an integer multiple of the size of the RB set; for example, the channel bandwidth of a CC can be expressed as... Where M is a positive integer. For example, if a UE is configured with two CCs / cells in a cell group, and M equals 5 and the two CCs / cells are in-band non-contiguous carrier aggregation, then the channel BW of each CC / cell is equal to... like Figure 14 As shown. In other words, the RB set configuration can be equivalent to the network-defined LBT BW unit and LBT is performed in all LBT units within the channel bandwidth of each CC for the gNB / UE. It can be further assumed that the UE is configured with an active bandwidth portion (BWP) and the BWP bandwidth is equal to For example, a BWP can be divided into 5 RB sets. According to the 16NR-U specification, when a wideband BWP has an integer multiple of the number of RB sets, each RB set can have independent signaling via DCI format 2_0 for COT sharing indication, available RB sets, etc. Therefore, RB sets within the same channel number can share the GC-PDCCH for DCI format 2_0 reception. In this case, the UE does not need to monitor the RB sets within the same channel number used for monitoring DCI format 2_0. Therefore, the UE can be configured with a CORESET, and its PRB, allocated by frequencyDomainResources, is within an RB set or BWP whose bandwidth is equal to the size of the RB set used for DCI format (e.g., 2_0) reception (e.g., narrow BWP BW = RB set size). If a scheduling PDSCH with BWP switching exists, the DCI format can be monitored at the active BWP (e.g., 2_0).

[0160] Figure 15 Another example is shown. In this example, a CC is configured to have an equal to A BW (Blocking Warp) of 10 RB sets (e.g., 10 RB sets). In this example, RB sets 1 through 5 are allocated in channel number 2, and RB sets 6 through 10 are allocated in channel number 3. If channel number 3 is used by another RAT (e.g., 802.11ad / ay), RB sets 6 through 10 are blocked. However, when channel number 2 is available, RB set 1 can be used to schedule DCI and DCI formats (e.g., 2_0).

[0161] The topic disclosed for Case 1 (e.g., the channel BW of other RATs is an integer multiple of the RB set size) is summarized in the following scenario.

[0162] In the first scenario, if the UE is configured with multiple CCs (cells) in a channel, one CC (cell) can be configured as the scheduling cell for each channel. If the CC is used for coordinated scheduling in the channel (e.g., its BW < B) and its carrier BW is an integer multiple of the RB size, the UE can be configured to monitor the DCI format (e.g., 2_0) in the RB set.

[0163] In the second scenario, if the UE is configured with a broadband BWP in a CC, e.g., the BW of the BWP is an integer multiple of the RB set size, and the carrier / channel BW is greater than the bandwidth of the channel number (e.g., B), the UE can monitor an RB set for the DCI format (e.g., 2_0) in the channel.

[0164] If the UE initiates LBT, the UE can perform LBT for each RB set, and the UE can use one of the following options to report the LBT result.

[0165] Option 1: The UE reports the LBT result for each RB set in the configuration. The gNB can calculate the total number N of RB sets in the configuration. The reporting sequence can be based on {RB set #1, RB set #2,..., RB set #N}. The threshold (e.g., energy detection ED) can be configured or indicated by the network.

[0166] Option 2: The UE reports the LBT result for each channel. Note that the BW of the channel can be an integer multiple of the RB set size. If multiple CCs are configured in the channel, the UE only reports the LBT result for that channel because the gNB and the UE know how many channels are allocated. The reporting sequence can be based on {channel #1, channel #2,..., channel #Q}, where Q is the total number of channels configured for the UE.

[0167] Case 2 :

[0168] denotes the RB set size and where B is the channel BW of other RATs (e.g., 802.11ad / ay). For example, for the RB set size, and B is 2.16 GHz. In this scenario, LBT BW can be performed on multiple RB sets or CCs. A special case is that the LBT BW is equal to the CC BW or the transmission BW.

[0169] If the gNB initiates LBT, the gNB can signal the available RB set indication in the form of {RB set #1, RB set #2,..., RB set N1} of the UE.

[0170] ● The UE can determine the total number N1 of RB sets based on the configuration.

[0171] ● If multiple CCs exist within an LBT BW (or RB set), such as RB set i, then CCs within RB set i can share the same indicator. For example, LBT results and COT information can be applied to CCs in RB set i. Furthermore, the UE can be configured to use CCs in RB set i for coordinated scheduling. The DCI format (e.g., 2_0) can be monitored in the scheduling SCell (or PSCell / PCell).

[0172] ●If the channel BW of CC can be equal to or If the value is an integer multiple of the value of the RB set, then the network can divide each RB set into several sub-RB sets within the CC. The size of the sub-RB sets... Can be based on expressions Where M is a positive integer. The UE can monitor the DCI format (e.g., 2_0) in the sub-RB set and configure CORESET in the sub-RB set.

[0173] If the UE initiates LBT, the UE can perform LBT for each RB set, and the UE can report the LBT results in the form of {RB set #1, RB set #2, ..., RB set #N2}.

[0174] ●The UE can determine the total number N2 of the RB set based on the configuration.

[0175] ●If multiple CCs are in RB set i, the UE can report the LBT results of RB set i.

[0176] ●If CC exists and its channel BW can be equal to or If the value is an integer multiple of the value of the RB set, and each RB set is divided into several sub-RB sets in the CC, then the UE reports the LBT result of that CC.

[0177] For example, the UE is configured with a cell group, and there are 10 CCs in the cell group, such as Figure 16 As shown. Each CC has a channel. (e.g., 0.4GHz), and the size of the RB set. Equal to 2 GHz. In this configuration (e.g., gNB / UE performs LBT on all CCs), the UE can determine that the total number of RB sets is equal to 2, such as... Figure 16As shown. This is based on CCs 1 to 5 being configured for the channel with channel number 2, and CCs 6 to 10 being configured for the channel with channel number 4. The aggregated channel BW is equal to 4 GHz. The gNB can transmit LBT results {RB set #1, RB set #2} to the UE based on channel availability (e.g., RB set #1 is available, but RB set #2 is not available). There are 5 CCs in RB set #1, so the CCs (e.g., CCs 1 to CC 5) share the same RB set and COT information. Furthermore, the CCs in RB set i (i = 1, 2) can be configured to monitor DCI format 2_0 to save power, because only a portion of the RB set size is used to detect DCI format 2_0 before the UE obtains the COT and RB set information.

[0178] In addition, the following method for NR-U with cooperative scheduling for CA is also disclosed.

[0179] In the first approach, for a non-scheduled SCell (e.g., an SCell not responsible for coordinated scheduling), it can be rapidly activated or deactivated (e.g., transition to sleep behavior / out of sleep behavior) from a PSCell, PCell, or scheduled SCell via scheduled DCI format 1_1 (non-fallback DCI). A non-scheduled SCell can be configured with at least two BWPs, one for receiving and / or transmitting, and the other configured as a sleep BWP, meaning the BWP is configured without any search space associated with the CORESET (if configured). Therefore, when there is no scheduled data or when a signal is sent from a PCell / PSCell / scheduled SCell via DCI format (e.g., DCI format 0_1, 1_1) to a sleep BWP, the UE is not required to monitor any DCI for the non-scheduled SCell. When the UE switches to a sleep BWP, it can save power by not monitoring the PDCCH, thus its behavior is similar to deactivating the SCell. However, the actual deactivation for the non-scheduled SCell is still based on MAC-CE.

[0180] In the second approach, more than one BWP can be configured for each scheduling SCell, PSCell, or PCell, as in versions 15 / 16. If a BWP is configured, it can be set as the initial BWP; otherwise, when COT and RB set information is unavailable to the UE, the default BWP can be used to monitor DCI format 2_0.

[0181] Figure 19An exemplary method for channelization and LBT for NR is illustrated. At step 201, the talk-before-sound (LBT) bandwidth (BW) can be configured for carrier aggregation or aggregated channel bandwidth within the channel bandwidth of the radio access technology. At step 202, the LBT BW or resource block (RB) set BW can be set equal to the BW of each component carrier (CC) or transport BW. At step 203, the LBT BW or RB set BW can be set to aggregated CC BW or aggregated transport BW. At step 204, the LBT BW or RB set BW is set equal to the unit of BW, where the unit of BW can be represented by an RB.

[0182] It should be understood that the entity performing the steps shown in this document can be a logical entity. These steps can be stored in, for example, Figure 18C or Figure 18D The methods described herein are executed in the memory of the device, server, or computer system shown and on its processor. Skipping, combining, or adding steps between the exemplary methods disclosed herein are contemplated. Table 7 provides exemplary abbreviations and definitions for the subjects disclosed herein.

[0183] Table 7 - Abbreviations and Definitions

[0184]

[0185]

[0186]

[0187] Figure 17 An exemplary display (e.g., a graphical user interface) is shown that can be generated based on methods, systems, and devices for channelization and LBT in unlicensed NR bands of 52.6 GHz and above, as discussed herein. Display interface 901 (e.g., a touchscreen display) may provide text associated with channelization and LBT in unlicensed NR bands of 52.6 GHz and above in box 902. Progress of any step discussed herein (e.g., messages sent or success of a step) may be displayed in box 902. Furthermore, graphical output 902 may be displayed on display interface 901. Graphical output 903 may be a graphical output of the device topology implementing methods, systems, and devices for channelization and LBT in unlicensed NR bands of 52.6 GHz and above, the progress of any method or system discussed herein, etc.

[0188] The 3rd Generation Partnership Project (3GPP) developed technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities, encompassing studies on codecs, security, and quality of service. Recent Radio Access Technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE Advanced, and New Radio (NR) (also referred to as "5G"). It is hoped that the 3GPP NR standard will continue to evolve and include definitions for next-generation radio access technologies (new RATs), providing new flexible radio access below 7 GHz and new ultra-mobile broadband radio access above 7 GHz. This flexible radio access is expected to include new non-backward-compatible radio access in new spectrum below 6 GHz and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide range of 3GPP NR use cases with varying needs. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectrum, which will provide opportunities for ultra-mobile broadband access, such as for indoor applications and hotspots. Specifically, it is anticipated that ultra-mobile broadband and flexible radio access below 7 GHz will share a common design framework with centimeter-wave and millimeter-wave-specific design optimizations.

[0189] 3GPP has identified a variety of use cases that NR is expected to support, resulting in diverse user experience requirements regarding data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine-type communications (mMTC), network operations (e.g., network slicing, routing, migration and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications, which can include any of vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P), and vehicle-to-vehicle communications with other entities. Specific services and applications within these categories include, for example, surveillance and sensor networks, remote device control, two-way remote control, personal cloud computing, video streaming, cloud-based wireless offices, first responder connectivity, car emergency calls, disaster alarms, real-time gaming, multi-person video calling, autonomous driving, augmented reality, haptic internet, virtual reality, home automation, robotics, and drones. This article considers all of these and other use cases.

[0190] Figure 18A An exemplary communication system 100 is shown, in which methods and apparatuses for channelization and LBT for unlicensed NR bands of 52.6 GHz and above, such as those described and claimed herein, can be used. Figures 1 to 16The system and method are illustrated. Communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, or 102g (which may generally or collectively be referred to as WTRU 102 or WTRUs 102). Communication system 100 may include radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, core networks 106 / 107 / 109, public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and network services 113. Network services 113 may include, for example, V2X servers, V2X functions, ProSe servers, ProSe functions, IoT services, video streaming, or edge computing.

[0191] It should be understood that the concepts disclosed herein can be used with any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g can be any type of device or equipment configured to operate or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d, 102e, 102f, or 102g may... Figure 18A , Figure 18B , Figure 18C , Figure 18D , Figure 18E or Figure 18F While described as a handheld wireless communication device, it should be understood that each WTRU may include or embody any type of device or equipment configured to transmit or receive wireless signals in various envisioned use cases for 5G wireless communication, including by way of example only, user equipment (UE), mobile station, fixed or mobile user unit, pager, cellular phone, personal digital assistant (PDA), smartphone, laptop, tablet, netbook, notebook computer, personal computer, wireless sensor, consumer electronics, wearable devices (such as smartwatches or smart clothing), medical or e-health devices, robots, industrial equipment, drones, vehicles (such as cars, buses, trucks, trains, or airplanes), etc.

[0192] The communication system 100 may also include base station 114a and base station 114b. Figure 18AIn the example, each base station 114a and 114b is depicted as a single element. In practice, base stations 114a and 114b may include any number of interconnected base stations or network elements. Base station 114a may be any type of device configured to connect to the wireless interface of at least one of WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, the Internet 110, network services 113, or other networks 112). Similarly, base station 114b may be any type of device configured to connect to the wired or wireless interface of at least one of Remote Radio Headers (RRHs) 118a and 118b, Transmit and Receive Points (TRPs) 119a and 119b, or Roadside Units (RSUs) 120a and 120b to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, the Internet 110, other networks 112, or network services 113). RRH 118a, 118b can be any type of device configured to connect to the wireless interface of at least one of WTRU 102 (e.g., WTRU 102c) to facilitate access to one or more communication networks (such as core network 106 / 107 / 109, Internet 110, network service 113, or other network 112).

[0193] TRPs 119a and 119b can be any type of device configured to connect to at least one of the radio interfaces of WTRU 102d to facilitate access to one or more communication networks (such as core network 106 / 107 / 109, Internet 110, network service 113, or other network 112). RSUs 120a and 120b can be any type of device configured to connect to at least one of the radio interfaces of WTRU 102e or 102f to facilitate access to one or more communication networks (such as core network 106 / 107 / 109, Internet 110, other network 112, or network service 113). As an example, base stations 114a and 114b can be base transceiver stations (BTS), Node Bs, evolved Node Bs, home Node Bs, home evolved Node Bs, next-generation Node Bs (gNode Bs), satellites, site controllers, access points (APs), wireless routers, etc.

[0194] Base station 114a may be part of RAN 103 / 104 / 105, which may also include other base stations or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Similarly, base station 114b may be part of RAN 103b / 104b / 105b, which may also include other base stations or network elements (not shown), such as BSCs, RNCs, relay nodes, etc. Base station 114a may be configured to transmit or receive radio signals within a specific geographic area, which may be referred to herein as a cell (not shown). Similarly, base station 114b may be configured to transmit or receive wired or radio signals within a specific geographic area, which may be referred to herein as a cell (not shown) of the methods, systems, and apparatuses for channelization and LBT in unlicensed NR bands of 52.6 GHz and above. Similarly, base station 114b may be configured to transmit or receive wired or radio signals within a specific geographic area, which may be referred to herein as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one example, base station 114a may include three transceivers, for example, one transceiver per sector of the cell. In one example, base station 114a may employ multiple-input multiple-output (MIMO) technology and thus may utilize multiple transceivers for each sector of the cell.

[0195] Base station 114a can communicate with one or more of WTRUs 102a, 102b, 102c, or 102g via air interface 115 / 116 / 117, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 115 / 116 / 117.

[0196] Base station 114b can communicate with one or more of RRH 118a, 118b, TRP 119a, 119b, or RSU 120a, 120b via wired or air interfaces 115b / 116b / 117b. These wired or air interfaces can be any suitable wired communication link (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interfaces 115b / 116b / 117b.

[0197] RRH 118a, 118b, TRP 119a, 119b, or RSU 120a, 120b can communicate with one or more of WTRU 102c, 102d, 102e, 102f via air interface 115c / 116c / 117c, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 115c / 116c / 117c.

[0198] WTRUs 102a, 102b, 102c, 102d, 102e, or 102f can communicate with each other via air interface 115d / 116d / 117d, such as sidelink communication. This air interface can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 115d / 116d / 117d.

[0199] The communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN103 / 104 / 105 and WTRU 102a, 102b, 102c or RRH 118a, 118b, TRP 119a, 119b and RSU 120a, 120b and WTRU 102c, 102d, 102e, 102f in RAN 103b / 104b / 105b can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively. WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink Packet Access (HSDPA) or High-Speed ​​Uplink Packet Access (HSUPA).

[0200] In one example, base station 114a and WTRUs 102a, 102b, 102c or RAN103b / 104b / 105b, specifically RRH 118a, 118b, TRP 119a, 119b or RSU 120a, 120b and WTRUs 102c, 102d, can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c using Long Term Evolution (LTE) or LTE-A, respectively. In the future, air interfaces 115 / 116 / 117 or 115c / 116c / 117c can implement 3GPP NR technology. LTE and LTE-A technologies may include LTE D2D and V2X technologies and interfaces (such as sidelink communication). Similarly, 3GPP NR technology includes NR V2X technology and interfaces (such as sidelink communication).

[0201] Base stations 114a and WTRUs 102a, 102b, 102c and 102g in RAN 103 / 104 / 105, or RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b and WTRUs 102c, 102d, 102e, 102f in RAN 103b / 104b / 105b, can implement radio technologies such as IEEE 802.16 (e.g., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0202] Figure 18ABase station 114c can be, for example, a wireless router, a home node B, a home evolution node B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial areas, homes, vehicles, trains, aircraft, satellites, manufacturing plants, campuses, etc., to achieve channelization and LBT methods, systems, and apparatuses for unlicensed NR bands of 52.6 GHz and above, as disclosed herein. In one example, base station 114c and WTRU 102 (e.g., WTRU102e) can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). Similarly, base station 114c and WTRU102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another example, base station 114c and WTRU 102 (e.g., WTRU 102e) can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish picocells or femtocells. Figure 18A As shown, base station 114c may have a direct connection to Internet 110. Therefore, base station 114c may not need to access Internet 110 via core network 106 / 107 / 109.

[0203] RAN 103 / 104 / 105 or RAN 103b / 104b / 105b can communicate with core network 106 / 107 / 109, which can be any type of network configured to provide voice, data, messaging, authorization and authentication, application and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. For example, core network 106 / 107 / 109 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, etc., or perform advanced security functions such as user authentication.

[0204] Although not in Figure 18A As shown, but it should be understood, RAN 103 / 104 / 105 or RAN103b / 104b / 105b or core network 106 / 107 / 109 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 103 / 104 / 105 or RAN103b / 104b / 105b. For example, in addition to being connected to RAN 103 / 104 / 105 or RAN103b / 104b / 105b that can utilize E-UTRA radio technology, core network 106 / 107 / 109 can also communicate with another RAN (not shown) that uses GSM or NR radio technology.

[0205] Core networks 106 / 107 / 109 can also serve as gateways for WTRUs 102a, 102b, 102c, 102d, and 102e to access PSTN 108, the Internet 110, or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired or wireless communication networks owned or operated by other service providers. For example, network 112 may include any type of packet data network (e.g., IEEE 802.3 Ethernet) or another core network connected to one or more RANs, which may use the same RAT as or a different RAT than RAN 103 / 104 / 105 or RAN 103b / 104b / 105b.

[0206] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may include multi-mode capabilities. For example, WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks via different wireless links to implement the methods, systems, and apparatuses disclosed herein for channelization and LBT in unlicensed NR bands of 52.6 GHz and above. Figure 18A The WTRU 102g shown can be configured to communicate with a base station 114a that can employ cellular-based radio technology and with a base station 114c that can employ IEEE 802 radio technology.

[0207] Despite Figure 18A Although not shown, it should be understood that user equipment can be wired to a gateway. The gateway can be a residential gateway (RG). The RG can provide connectivity to the core network 106 / 107 / 109. It should be understood that many of the topics included herein are equally applicable to UEs acting as WTRUs and UEs using wired connections to the network. For example, topics applicable to radio interfaces 115, 116, 117, and 115c / 116c / 117c are equally applicable to wired connections.

[0208] Figure 18BThis is a system diagram of an exemplary RAN 103 and core network 106 for implementing the methods, systems, and apparatuses disclosed herein for channelization and LBT in unlicensed NR bands of 52.6 GHz and above. As described above, RAN 103 can communicate with WTRUs 102a, 102b, and 102c via air interface 115 using UTRA radio technology. RAN 103 can also communicate with core network 106. Figure 18B As shown, RAN 103 may include nodes B 140a, 140b, and 140c, each of which may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 115. Nodes B 140a, 140b, and 140c may each be associated with a specific cell (not shown) within RAN 103. RAN 103 may also include RNCs 142a and 142b. It should be understood that RAN 103 may include any number of node Bs and radio network controllers (RNCs).

[0209] like Figure 18B As shown, nodes B 140a and 140b can communicate with RNC 142a. Additionally, node B 140c can communicate with RNC 142b. Nodes B 140a, 140b, and 140c can communicate with their respective RNCs 142a and 142b via the Iub interface. RNCs 142a and 142b can communicate with each other via the Iur interface. Each of RNCs 142a and 142b can be configured to control the corresponding nodes B 140a, 140b, and 140c to which it is connected. Furthermore, each of RNCs 142a and 142b can be configured to perform or support other functionalities such as outer-loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, and data encryption.

[0210] Figure 18B The core network 106 shown may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, or a gateway GPRS support node (GGSN) 150. Although each of the foregoing elements is depicted as part of the core network 106, it should be understood that any of these elements may be owned or operated by an entity other than the core network operator.

[0211] RNC 142a in RAN 103 can connect to MSC 146 in core network 106 via IuCS interface. MSC 146 can connect to MGW 144. MSC 146 and MGW 144 provide WTRU 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRU 102a, 102b, and 102c and legacy landline communication equipment.

[0212] The RNC 142a in RAN 103 can also be connected to the SGSN 148 in core network 106 via the IuPS interface. The SGSN 148 can be connected to the GGSN 150. The SGSN 148 and GGSN 150 provide WTRUs 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0213] The core network 106 can also be connected to other networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0214] Figure 18C This is a system diagram of an exemplary RAN 104 and core network 107 that enables channelization and LBT for unlicensed NR bands of 52.6 GHz and above, as disclosed herein. As noted above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with core network 107.

[0215] RAN 104 may include evolved Node Bs 160a, 160b, and 160c, but it should be understood that RAN 104 may include any number of evolved Node Bs. Evolved Node Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. For example, evolved Node Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, evolved Node B 160a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a.

[0216] Each of the evolved nodes B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink or downlink, etc. Figure 18CAs shown, evolution nodes B 160a, 160b and 160c can communicate with each other via the X2 interface.

[0217] Figure 18C The core network 107 shown may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the foregoing elements is depicted as part of the core network 107, it should be understood that any of these elements may be owned or operated by an entity other than the core network operator.

[0218] The MME 162 can connect to each of the evolved nodes B 160a, 160b, and 160c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can also provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM or WCDMA.

[0219] Serving Gateway 164 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. Serving Gateway 164 typically routes and forwards user data packets to / from WTRUs 102a, 102b, and 102c. Serving Gateway 164 may also perform other functions, such as anchoring the user plane during inter-evolved Node-B handover, triggering paging when downlink data is available to WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0220] Service gateway 164 can also be connected to PDN gateway 166, which provides WTRUs 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0221] Core network 107 can facilitate communication with other networks. For example, core network 107 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. For example, core network 107 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between core network 107 and PSTN 108, or be able to communicate with such an IP gateway. Additionally, core network 107 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0222] Figure 18D This is a system diagram of an exemplary RAN 105 and core network 109 for implementing the methods, systems, and apparatuses disclosed herein for channelization and LBT in unlicensed NR bands of 52.6 GHz and above. RAN 105 may communicate with WTRUs 102a and 102b via air interface 117 using NR radio technology. RAN 105 may also communicate with core network 109. Non-3GPP Interoperability Function (N3IWF) 199 may communicate with WTRU 102c via air interface 198 using non-3GPP radio technology. N3IWF 199 may also communicate with core network 109.

[0223] RAN 105 may include Next Generation Node Bs 180a and 180b. It should be understood that RAN 105 may include any number of Next Generation Node Bs. Next Generation Node Bs 180a and 180b may each include one or more transceivers for communicating with WTRUs 102a and 102b via air interface 117. When using integrated access and backhaul connectivity, the same air interface may be used between the WTRU and the Next Generation Node Bs, which may be via the core network 109 of one or more gNBs. Next Generation Node Bs 180a and 180b may implement MIMO, MU-MIMO, or digital beamforming technologies. Therefore, Next Generation Node B 180a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a. It should be understood that RAN 105 may employ other types of base stations, such as Evolved Node Bs. It should also be understood that RAN 105 may employ more than one type of base station. For example, the RAN may employ both Evolved Node Bs and Next Generation Node Bs.

[0224] N3IWF 199 may include a non-3GPP access point 180c. It should be understood that N3IWF 199 may include any number of non-3GPP access points. The non-3GPP access point 180c may include one or more transceivers for communicating with WTRU 102c via air interface 198. The non-3GPP access point 180c may communicate with WTRU 102c via air interface 198 using the 802.11 protocol.

[0225] Each of the next-generation nodes B 180a and 180b can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink or downlink, etc. Figure 18D As shown, next-generation nodes B 180a and 180b can communicate with each other, for example, via the Xn interface.

[0226] Figure 18D The core network 109 shown may be a 5G core network (5GC). Core network 109 can provide various communication services to customers interconnected via a radio access network. Core network 109 includes multiple entities that perform the functionality of the core network. As used herein, the terms "core network entity" or "network function" refer to any entity that performs one or more functions of the core network. It should be understood that such core network entities may be logical entities implemented in the form of computer-executable instructions (software), which are stored in a device or computer system configured for wireless or network communication (such as...). Figure 18G The system 90 shown is stored in its memory and executed on its processor.

[0227] exist Figure 18D In the example, the 5G core network 109 may include Access and Mobility Management Functions (AMF) 172, Session Management Functions (SMF) 174, User Plane Functions (UPF) 176a and 176b, User Data Management Functions (UDM) 197, Authentication Server Functions (AUSF) 190, Network Exposure Functions (NEF) 196, Policy Control Functions (PCF) 184, Non-3GPP Interoperability Functions (N3IWF) 199, and User Data Repository (UDR) 178. While each of the foregoing elements is depicted as part of the 5G core network 109, it should be understood that any of these elements may be owned or operated by an entity other than the core network operator. It should also be understood that the 5G core network may not include all of these elements, may include additional elements, and may include multiple instances of each of these elements. Figure 18D The network functions are shown to be directly connected to each other; however, it should be understood that they may communicate via routing agents such as diameter routing agents or message buses.

[0228] exist Figure 18DIn the example, connections between network functions are achieved through a set of interfaces or reference points. It should be understood that a network function can be modeled, described, or implemented as a set of services invoked or called by other network functions or services. Invocation of network function services can be achieved through direct connections between network functions, message exchange on a message bus, invoking software functions, etc.

[0229] The AMF 172 can connect to RAN 105 via the N2 interface and can be used as a control node. For example, the AMF 172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. The AMF can forward user plane tunnel configuration information to RAN 105 via the N2 interface. The AMF 172 can receive user plane tunnel configuration information from the SMF via the N11 interface. The AMF 172 can typically route and forward NAS packets to / from WTRUs 102a, 102b, and 102c via the N1 interface. The N1 interface... Figure 18D Not shown in the image.

[0230] SMF 174 can connect to AMF 172 via interface N11. Similarly, SMF 174 can connect to PCF184 via interface N7 and to UPF 176a and 176b via interface N4. SMF 174 can be used as a control node. For example, SMF 174 can be responsible for session management, IP address allocation for WTRU 102a, 102b, and 102c, management and configuration of traffic redirection rules in UPF 176a and UPF 176b, and generation of downlink data notifications to AMF 172.

[0231] UPF 176a and UPF 176b provide WTRU 102a, 102b, and 102c with access to a packet data network (PDN) (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and other devices. UPF 176a and UPF 176b also provide WTRU 102a, 102b, and 102c with access to other types of packet data networks. For example, other networks 112 can be any type of network, such as Ethernet or switched data packets. UPF 176a and UPF 176b can receive traffic redirection rules from SMF 174 via the N4 interface. UPF 176a and UPF 176b can provide access to packet data networks by connecting to a packet data network via the N6 interface or by connecting to each other and other UPFs via the N9 interface. In addition to providing access to packet data networks, UPF 176 is also responsible for packet routing and forwarding, policy rule enforcement, quality of service for user plane traffic, and downlink packet buffering.

[0232] The AMF 172 can also connect to the N3IWF 199, for example, via the N2 interface. The N3IWF facilitates the connection between the WTRU 102c and the 5G core network 170, for example, via a radio interface technology not defined by 3GPP. The AMF can interact with the N3IWF 199 in the same or similar manner as it interacts with the RAN 105.

[0233] The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF172 via the N15 interface, and to the Application Function (AF) 188 via the N5 interface. The N15 and N5 interfaces are... Figure 18D Not shown in the diagram. PCF 184 can provide policy rules to control plane nodes such as AMF 172 and SMF 174, thereby allowing the control plane nodes to enforce these rules. PCF 184 can send policies for WTRUs 102a, 102b, and 102c to AMF 172, enabling AMF to deliver policies to WTRUs 102a, 102b, and 102c via the N1 interface. The policies can then be enforced or applied at WTRUs 102a, 102b, and 102c.

[0234] The UDR 178 can act as a repository for authentication credentials and subscription information. The UDR can connect to network functions, allowing them to add, read, and modify data in the repository. For example, the UDR 178 can connect to the PCF 184 via the N36 interface. Similarly, the UDR 178 can connect to the NEF 196 via the N37 interface, and the UDR 178 can connect to the UDM 197 via the N35 interface.

[0235] The UDM 197 serves as an interface between the UDR 178 and other network functions. The UDM 197 can authorize network functions to access the UDR 178. For example, the UDM 197 can connect to the AMF 172 via the N8 interface, and to the SMF 174 via the N10 interface. Similarly, the UDM 197 can connect to the AUSF 190 via the N13 interface. The UDR 178 and UDM 197 can be tightly integrated.

[0236] The AUSF 190 performs authentication-related operations and connects to the UDM 178 via the N13 interface and to the AMF 172 via the N12 interface.

[0237] NEF 196 exposes the capabilities and services of the 5G core network 109 to Application Function (AF) 188. Exposure may occur on the N33 API interface. NEF can connect to AF 188 via the N33 interface, and NEF can connect to other network functions to demonstrate the capabilities and services of the 5G core network 109.

[0238] Application function 188 can interact with network functions in the 5G core network 109. The interaction between application function 188 and network functions can occur via a direct interface or via NEF 196. Application function 188 can be considered part of the 5G core network 109, or it can be deployed outside the 5G core network 109 by an enterprise with a business relationship with the mobile network operator.

[0239] Network slicing is a mechanism that mobile network operators can use to support one or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types operating across a single RAN. Network slicing enables operators to create customized networks to provide optimized solutions for different market scenarios that require diverse requirements in terms of functionality, performance, and isolation.

[0240] 3GPP has designed the 5G core network to support network slicing. Network slicing is a valuable tool for network operators to support a wide range of 5G use cases with highly diverse and sometimes extreme requirements, such as massive IoT, critical communications, V2X, and enhanced mobile broadband. Without network slicing, the flexibility and scalability of the network architecture may be insufficient to effectively support a broader range of use case needs when each use case has its own specific set of requirements for performance, scalability, and availability. Furthermore, new network services should be introduced more efficiently.

[0241] See you again Figure 18D In a network slicing scenario, WTRU 102a, 102b, or 102c can connect to AMF172 via the N1 interface. AMF can be a logical part of one or more slices. AMF coordinates the connection or communication between WTRU 102a, 102b, or 102c and one or more of UPF176a and 176b, SMF174, and other network functions. Each of UPF176a and 176b, SMF174, and other network functions can be part of the same slice or different slices. When they are part of different slices, they can be isolated from each other in terms of their access to different computing resources, security credentials, etc.

[0242] Core network 109 may facilitate communication with other networks. For example, core network 109 may include an IP gateway (such as an IP Multimedia Subsystem (IMS) server) that serves as an interface between 5G core network 109 and PSTN 108, or may communicate with such an IP gateway. For example, core network 109 may include a Short Message Service (SMS) service center that facilitates communication via Short Message Service, or may communicate with such an SMS service center. For example, 5G core network 109 may facilitate the exchange of non-IP data packets between WTRUs 102a, 102b, and 102c and server or application function 188. Additionally, core network 170 may provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0243] This article describes and Figure 18A , Figure 18C , Figure 18D or Figure 18E The core network entities shown are identified by the names given to those entities in certain existing 3GPP specifications. However, it should be understood that in the future, those entities and functions may be identified by other names, and some entities or functions may be combined in future specifications released by 3GPP, including future 3GPP NR specifications. Therefore, in Figure 18A , Figure 18B , Figure 18C , Figure 18D or Figure 18E The specific network entities and functions described and illustrated herein are provided by way of example only, and it should be understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system (whether currently defined or to be defined in the future).

[0244] Figure 18E An exemplary communication system 111 is illustrated, in which the systems, methods, and apparatuses described herein for implementing channelization and LBT for unlicensed NR bands of 52.6 GHz and above can be used. Communication system 111 may include radio transmit / receive units (WTRUs) A, B, C, D, E, F, a base station gNB 121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein can be applied to any number of WTRUs, base station gNBs, V2X networks, or other network elements. One or more or all WTRUs A, B, C, D, E, and F may be outside the coverage area of ​​the access network 131. WTRUs A, B, and C form a V2X group, where WTRU A is the group leader and WTRUs B and C are group members.

[0245] If WTRUs A, B, C, D, E, and F are within the access network coverage 131, they can communicate with each other via gNB 121 through Uu interface 129. Figure 18E In the example, WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F can communicate directly with each other via side link interfaces (e.g., PC5 or NR PC5) (such as interfaces 125a, 125b, or 128), regardless of whether they are within or outside access network coverage 131. For example, in Figure 18E In the example, WRTU D outside the access network coverage 131 communicates with WTRU F inside the coverage 131.

[0246] WTRUs A, B, C, D, E, and F can communicate with RSUs 123a or 123b via Vehicle-to-Network (V2N) 133 or sidelink interface 125b. WTRUs A, B, C, D, E, and F can communicate with V2X server 124 via Vehicle-to-Infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F can communicate with another UE via Vehicle-to-Pedestrian (V2P) interface 128.

[0247] Figure 18F This is a block diagram of an exemplary apparatus or device WTRU 102, configurable for wireless communication and operation, based on the systems, methods, and apparatuses for reducing mobility signaling load described herein, such as... Figure 18A , Figure 18B , Figure 18C , Figure 18D or Figure 18E or Figures 1 to 16 WTRU102. For example... Figure 18F As shown, the exemplary WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripheral devices 138. It should be understood that the WTRU 102 may include any sub-combination of the foregoing elements. Furthermore, base stations 114a and 114b, or base stations 114a and 114b, may represent nodes (such as, but not limited to, transceiver stations (BTS), node B, site controllers, access points (APs), home node B, evolved home node B (eNodeB), home evolved node B (HeNB), home evolved node B gateway, next-generation node B (gNode-B), and proxy nodes, etc.) that may be included. Figure 18FSome or all of the elements depicted may be exemplary implementations of the disclosed systems and methods for channelization and LBT in unlicensed NR bands of 52.6 GHz and above, as described herein.

[0248] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, or any other function that enables WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, which can be coupled to transmitting / receiving element 122. Although Figure 18F While the processor 118 and transceiver 120 are depicted as separate components, it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0249] The UE's transmit / receive element 122 can be configured to transmit data to a base station (e.g., via air interface 115 / 116 / 117). Figure 18A The base station 114a) transmits signals or receives signals from the base station, or transmits signals to or receives signals from another UE via air interface 115d / 116d / 117d. For example, the transmit / receive element 122 may be an antenna configured to transmit or receive RF signals. The transmit / receive element 122 may be a transmitter / detector configured to transmit or receive, for example, IR signals, UV signals, or visible light signals. The transmit / receive element 122 may be configured to transmit and receive both RF signals and optical signals. It should be understood that the transmit / receive element 122 may be configured to transmit or receive any combination of wireless signals or wired signals.

[0250] Furthermore, although the transmitting / receiving element 122 is in Figure 18F While depicted as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. More specifically, WTRU 102 may employ MIMO technology. Therefore, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interfaces 115 / 116 / 117.

[0251] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As noted above, WTRU 102 may have multi-mode capability. Therefore, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11 or NR and E-UTRA), or via multiple beams to the same RAT at different RRHs, TRPs, RSUs, or nodes.

[0252] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data from them. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, or display / touchpad / indicator 128. Furthermore, the processor 118 can access information in any type of suitable memory (such as non-removable memory 130 or removable memory 132) and store data in any type of suitable memory. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a Subscriber Identity Module (SIM) card, a Memory Stick, a Secure Digital (SD) memory card, etc. Processor 118 may access memory information that is not physically located on WTRU 102 (e.g., on a server hosted in the cloud, on an edge computing platform, or on a home computer (not shown), and store data in that memory. Processor 118 may be configured to control lighting patterns, images, or colors on display or indicator 128 in response to whether the channelization and LBT setup of unlicensed NR bands of 52.6 GHz and above is successful or unsuccessful in some of the examples described herein, or otherwise indicate the status of channelization and LBT of unlicensed NR bands of 52.6 GHz and above, and associated components. The control lighting patterns, images, or colors on display or indicator 128 may reflect the status of any method flow or component shown or discussed in the accompanying drawings. Messages and procedures for channelization and LBT of unlicensed NR bands of 52.6 GHz and above are disclosed herein. These messages and procedures can be extended to provide interfaces / APIs for users to request resources via input sources (e.g., speaker / microphone 124, keypad 126, or display / touchpad / indicator 128), as well as to request, configure, or query channelization and LBT-related information for unlicensed NR bands at and above 52.6 GHz, and other information that can be displayed on display 128.

[0253] The processor 118 may receive power from the power supply 134 and may be configured to distribute or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0254] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or instead of the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interface 115 / 116 / 117 or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method.

[0255] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software or hardware modules that provide additional features, functions, or wired or wireless connectivity. For example, peripheral device 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), Universal Serial Bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, etc. Modules, FM radio units, digital music players, media players, video game player modules, internet browsers, and so on.

[0256] WTRU 102 may be included in other devices or equipment, such as sensors, consumer electronics, wearable devices (such as smartwatches or smart clothing), medical or e-health devices, robots, industrial equipment, drones, or vehicles (such as cars, trucks, trains, or airplanes). WTRU 102 may be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces, such as interconnect interfaces that may include one of the peripheral devices 138.

[0257] Figure 18G This is a block diagram of an exemplary computing system 90, which can illustrate... Figure 18A , Figure 18C , Figure 18D and Figure 18E One or more devices of the communication network shown herein, and such as those described and claimed herein. Figures 1 to 16The systems and methods shown are for channelization and LBT in unlicensed NR bands of 52.6 GHz and above, such as certain nodes or functional entities in RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, other networks 112, or network services 113. The computing system 90 may include a computer or server and may be controlled primarily by computer-readable instructions, which may be in the form of software, regardless of where or by what means such software is stored or accessed. Such computer-readable instructions may be executed within a processor 91 to enable the computing system 90 to function. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables the computing system 90 to function in a communication network. The coprocessor 81 is an optional processor, distinct from the main processor 91, that can perform additional functions or assist the processor 91. The processor 91 or the coprocessor 81 can receive, generate, and process data relating to the methods and apparatus disclosed herein for channelization and LBT in unlicensed NR bands of 52.6 GHz and above.

[0258] In operation, processor 91 fetches instructions, decodes and executes them, and transfers information to and from other resources via the main data transfer path (system bus 80) of the computing system. This system bus connects components within the computing system 90 and defines the medium for data exchange. System bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0259] The memory coupled to the system bus 80 includes random access memory (RAM) 82 and read-only memory (ROM) 93. This type of memory includes circuitry that allows information to be stored and retrieved. ROM 93 typically contains stored data that cannot be easily modified. Data stored in RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to RAM 82 or ROM 93 can be controlled by the memory controller 92. The memory controller 92 provides address translation functionality, converting virtual addresses to physical addresses as instructions are executed. The memory controller 92 also provides memory protection functionality that isolates processes within the system and separates system processes from user processes. Therefore, a program running in first mode can only access memory mapped through its own process virtual address space; it cannot access memory in another process's virtual address space unless inter-process memory sharing is configured.

[0260] In addition, the computing system 90 may include a peripheral device controller 83 responsible for transmitting instructions from the processor 91 to peripheral devices such as a printer 94, a keyboard 84, a mouse 95, and a disk drive 85.

[0261] A display 86, controlled by a display controller 96, is used to display visual output generated by a computing system 90. This visual output may include text, graphics, animated graphics, and video. The visual output can be provided in the form of a graphical user interface (GUI). The display 86 can be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touchpad. The display controller 96 includes the electronic components required to generate the video signals sent to the display 86.

[0262] Furthermore, the computing system 90 may include communication circuitry, such as, for example, a wireless or wired network adapter 97, which can be used to connect the computing system 90 to an external communication network or device, such as... Figure 18A , Figure 18B , Figure 18C , Figure 18D or Figure 18E The RAN103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, WTRU 102, or other networks 112 are configured to enable the computing system 90 to communicate with other nodes or functional entities in these networks. A communication circuitry system, either separately or in conjunction with the processor 91, can be used to perform the transmit and receive steps of certain means, nodes, or functional entities described herein.

[0263] It should be understood that any or all of the apparatuses, systems, methods, and processes described herein may be embodied in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), cause the processor to perform or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer-executable instructions that execute on a processor of an apparatus or computing system configured for wireless or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented using any non-transitory (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical disc storage devices, magnetic tape cassettes, magnetic tape, disk storage devices or other magnetic storage devices, or any other tangible or physical medium that can be used to store desired information and is accessible by a computing system.

[0264] In describing preferred methods, systems, or apparatuses for the subject matter of this disclosure (channelization and LBT in unlicensed NR bands of 52.6 GHz and above) as shown in the accompanying drawings, specific terminology has been used for clarity. However, the claimed subject matter is not intended to be limited to the specific terminology chosen in this way.

[0265] The various techniques described herein can be implemented in combination of hardware, firmware, or software, or, where appropriate, in combination thereof. Such hardware, firmware, and software can reside in devices located at various nodes of a communication network. These devices can operate individually or in combination with each other to implement the methods described herein. As used herein, the terms “device,” “network device,” “node,” “equipment,” “network node,” etc., are used interchangeably. Furthermore, unless otherwise provided herein, the word “or” is generally used in a manner that includes the end value.

[0266] This written specification uses examples of the subject matter disclosed in this invention (including the best mode) and also enables any person skilled in the art to practice the disclosed subject matter, including making and using any device or system and performing any incorporated methods. The disclosed subject matter may include other examples that will occur to those skilled in the art (e.g., skipped steps, combined steps, or added steps between exemplary methods disclosed herein).

[0267] The methods, systems, and apparatuses described herein provide methods for channelization and LBT for unlicensed NR bands of 52.6 GHz and above. A method, system, computer-readable storage medium, or apparatus provides carrier aggregation or aggregated channel bandwidth that is consistent with an integer multiple of the channel bandwidth B (e.g., 2.16) GHz of other RATs. A method, system, computer-readable storage medium, or apparatus provides carrier aggregation or reuse of conventional NR channel BW or aggregated channel bandwidth that is inconsistent with an integer multiple of the channel bandwidth B (e.g., 2.16) GHz of other RATs. A method, system, computer-readable storage medium, or apparatus provides a method for configuring LBT and COT sharing schemes when the channel BW (e.g., B) of other RATs is an integer multiple of the RB set size (e.g., the LBT bandwidth of NR-Us from 52.6 GHz to 71 GHz and above). A method, system, computer-readable storage medium, or apparatus provides a method for configuring LBT and COT sharing schemes when the channel BW of other RATs is (nearly) equal to the RB set size of NR-Us from 52.6 GHz to 71 GHz. This refers to the maximum supported channel bandwidth within B. Methods, systems, and apparatuses described herein can provide a way to configure the pre-call listening (LBT) bandwidth (BW) for carrier aggregation or aggregated channel bandwidth within the channel bandwidth of the RAT; the LBT or resource block (RB) set BW can be set (e.g., configured) to be equal to the BW of each component carrier (CC) or transport BW, and the gNB or user equipment (UE) can perform LBT for each CC; the LBT or RB set BW can be set to aggregate CC BW or aggregate transport BW, wherein the gNB or UE can perform LBT on multiple / aggregated CCs; the LBT or RB set BW can be configured or set to be equal to a unit of BW (e.g., denoted by RB), wherein the gNB or UE performs LBT across all units of the channel bandwidth in each CC. See, for example... Figure 8 A, Figure 9 A, Figure 11A or Figure 19 All combinations (including the deletion or addition of steps) in this paragraph and the following paragraphs can be contemplated in a manner consistent with the other parts of the specific implementation.

[0268] A method, system, computer-readable storage medium, or apparatus provides a scheme for configuring a pre-talk listen-through (LBT) bandwidth (BW) and channel occupancy time (COT) sharing scheme when a channel BW (e.g., B) for other radio access technologies (RATs) for NR-U from 52.6 GHz to 71 GHz and above is simultaneously present; when the LBT or RB set BW is set equal to each CC BW or transmission BW, the gNB or UE can perform LBT for each CC, and the PCell, PSCell, or scheduling SCell can coordinate the LBT results of other CCs; when the LBT or RB set BW is set equal to each CC BW or transmission BW, the gNB or UE can perform LBT for each CC, and can independently schedule the LBT results of each CC for each active CC; when the LBT or RB set BW is set to aggregate CCs... When using a BW or aggregated transmission BW, the gNB or UE performs LBT across multiple / aggregated CCs, or the LBT result is replicated on all CCs and transmitted on PCell, PSCell, or scheduling SCell; or when the LBT or RB set BW is set as a unit (e.g., denoted by RB), the gNB or UE performs LBT across all units of the channel bandwidth in each CC, or the LBT result can be transmitted in the RB set within the CC. A method, system, computer-readable storage medium, or apparatus can provide for configuring a pre-talk listen-before (LBT) bandwidth (BW) for carrier aggregation or an aggregated channel bandwidth within the channel bandwidth for configuring radio access technologies; or setting the LBT BW or resource block (RB) set BW equal to the BW of each component carrier (CC) or transmission BW. A method, system, computer-readable storage medium, or apparatus can provide for configuring a pre-talk listen-before (LBT) bandwidth (BW) for carrier aggregation or an aggregated channel bandwidth within the channel bandwidth for configuring radio access technologies; or setting the LBT BW or RB set BW as an aggregated CC BW or an aggregated transmission BW. A method, system, computer-readable storage medium, or apparatus may provide for configuring a pre-talk listen-before (LBT) bandwidth (BW) for carrier aggregation or an aggregated channel bandwidth within a channel bandwidth for configuring a radio access technology; or setting an LBT BW or RB set BW to a unit equal to BW. All combinations (including deletions or additions of steps) in this and the preceding paragraphs are contemplated in a manner consistent with other parts of the detailed embodiments.

Claims

1. A base station, the base station comprising: The processor is configured as follows: Information is received from the wireless transmit / receive unit (WTRU), wherein the information is used to determine the pre-talk listen-before (LBT) configuration for carrier aggregation; Based on the information, an LBT configuration for carrier aggregation is determined, wherein the LBT configuration indicates multiple LBT bandwidths, each of the multiple LBT bandwidths corresponds to a subset of two or more CCs among multiple component carriers (CCs), and each LBT bandwidth is used to perform a single LBT for the corresponding CC subset. Send an instruction to the WTRU, wherein the instruction instructs to perform a single LBT for each LBT bandwidth for a corresponding subset of two or more CCs; as well as Based on the LBT configuration, a single LBT is performed for the corresponding subset of two or more CCs.

2. The base station according to claim 1, wherein a plurality of CCs are included in a first cell group of a plurality of cell groups, wherein each CC in the plurality of component carriers of the first cell group shares the same resource block set channel occupancy time (COT) information.

3. The base station according to claim 1, wherein each of the plurality of LBT bandwidths is indicated by one or more guard bands.

4. The base station according to claim 1, wherein the single LBT is used for a first cell group in a plurality of cell groups, wherein each cell group in the plurality of cell groups includes a plurality of component carriers and a corresponding single LBT.

5. The base station of claim 1, wherein the information includes WTRU capability information, and wherein the processor is configured to group two or more CCs based on the WTRU capability information to determine each corresponding subset of the two or more CCs.

6. The base station according to claim 1, wherein the carrier aggregation includes in-band non-continuous carrier aggregation.

7. The base station of claim 1, wherein the WTRU is configured with an activated bandwidth portion (BWP).

8. The base station of claim 1, wherein the indication is transmitted via Radio Resource Control (RRC) signaling.

9. A method performed by a base station, the method comprising: Information is received from the wireless transmit / receive unit (WTRU), wherein the information is used to determine the pre-talk listen-before (LBT) configuration for carrier aggregation; Based on the information, an LBT configuration for carrier aggregation is determined, wherein the LBT configuration indicates multiple LBT bandwidths, each of the multiple LBT bandwidths corresponds to a subset of two or more CCs among multiple component carriers (CCs), and each LBT bandwidth is used to perform a single LBT for the corresponding CC subset. Send an instruction to the WTRU, wherein the instruction instructs to perform a single LBT for each LBT bandwidth for a corresponding subset of two or more CCs; as well as Based on the LBT configuration, a single LBT is performed for the corresponding subset of two or more CCs.

10. The method of claim 9, wherein a plurality of CCs are included in a first cell group of a plurality of cell groups, wherein each CC in a plurality of component carriers of the first cell group shares the same resource block set channel occupancy time (COT) information.

11. The method of claim 9, wherein each of the plurality of LBT bandwidths is indicated by one or more guard bands.

12. The method of claim 9, wherein the single LBT is used for a first cell group in a plurality of cell groups, wherein each cell group in the plurality of cell groups includes a plurality of component carriers and a corresponding single LBT.

13. The method of claim 9, wherein the carrier aggregation includes in-band discontinuous carrier aggregation.

14. The method of claim 9, wherein the WTRU is configured with an active bandwidth portion (BWP).

15. The method of claim 9, wherein the information includes WTRU capability information, and wherein the method further comprises grouping two or more CCs based on the WTRU capability information to determine each corresponding subset of the two or more CCs.

16. A non-transitory computer-readable storage medium having program instructions stored thereon, which, when executed by a control circuit, cause the control circuit to perform the method of any one of claims 9-15.

17. A wireless transmit / receive unit (WTRU), comprising: The processor is configured as follows: Send information associated with the WTRU to the base station; Receive an instruction from the base station, wherein the instruction indicates an LBT configuration for the pre-talk listen-to (LBT) bandwidth for carrier aggregation, to perform a single LBT for each of the multiple component carriers (CCs); as well as Based on the LBT configuration information, determine the LBT configuration for carrier aggregation and perform a single LBT for the corresponding subset of two or more CCs.

18. The WTRU of claim 17, wherein the carrier aggregation includes in-band discontinuous carrier aggregation.

19. The WTRU of claim 17, wherein the WTRU is configured with an active bandwidth portion (BWP).

20. The WTRU of claim 17, wherein each of the plurality of LBT bandwidths is indicated by one or more guard bands.

21. The WTRU of claim 17, wherein the instruction is received via Radio Resource Control (RRC) signaling.

22. The WTRU of claim 17, wherein a plurality of CCs are included in a first cell group of a plurality of cell groups, wherein each CC in the plurality of CCs in the first cell group shares the same resource block set channel occupancy time (COT) information.

23. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: Send information associated with the WTRU to the base station, wherein the information is used to determine the pre-talk listen-before (LBT) configuration for carrier aggregation; Receive an indication from the base station, wherein the indication LBT configuration indicates a plurality of LBT bandwidths, each of the plurality of LBT bandwidths corresponding to a subset of two or more component carriers (CCs), and each LBT bandwidth is used to perform a single LBT for the corresponding subset of the two or more CCs. as well as Based on the LBT configuration information, determine the LBT configuration for carrier aggregation and perform a single LBT for the corresponding CC subset.

24. The method of claim 23, wherein a plurality of CCs are included in a first cell group of a plurality of cell groups, wherein each CC in the plurality of CCs in the first cell group shares the same resource block set channel occupancy time (COT) information.

25. The method of claim 23, wherein each of the plurality of LBT bandwidths is indicated by one or more guard bands.

26. The method of claim 23, wherein the single LBT is used for a first cell group in a plurality of cell groups, wherein each cell group in the plurality of cell groups includes a plurality of CCs and a corresponding single LBT.

27. The method of claim 23, wherein the information includes WTRU capability information, and wherein each corresponding subset of two or more CCs is configured to be determined based on grouping of one or more CCs, wherein grouping is configured to be determined based on WTRU capability information.

28. The method of claim 23, wherein the carrier aggregation includes in-band discontinuous carrier aggregation.

29. The method of claim 23, wherein the WTRU is configured with an active bandwidth portion (BWP).

30. The method of claim 23, wherein the indication is received via Radio Resource Control (RRC) signaling.

31. A non-transitory computer-readable storage medium having program instructions stored thereon, which, when executed by a control circuit, cause the control circuit to perform the method of any one of claims 23-30.

Images