CHANNEL ACCESS FOR NR IN 52.6-71 GHZ

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This Application claims the benefit of U.S. Provisional Patent Application Serial No. 63/001,619 filed March 30, 2020, the disclosure of which is hereby incorporated by reference as if set forth in its entirety herein.

BACKGROUND

Release- 16 NR-U

[0002] In Release- 16 New Radio Unlicensed (NR-U), the supported numerology (i.e. SCS) can be set as 15, 30 and 60 KHz. respectively. The listen before talk (LBT) bandwidth is set to 20 MHz in Release-16 NR-U. Based on the minimum LBT bandwidth that must be supported, the DL initial BWP is nominally 20 MHz for Rel-16 NR-U. The maximum supported channel bandwidth is set to 100 MHz. The UE channel bandwidth (or an activated BWP) can be set as an integer multiple of LBT bandwidth (i.e. 20 MHz). For instance, for SCS = 30 KHz, the total allocated PRB numbers for 20 MHz, 40 MHz and 80 MHz bandwidth is equal to 48, 102, and 214, respectively.

[0003] In Release- 16 NR-U, the PRBs allocated by frequencyDomainResources in the CORESET configuration are confined within one of LBT bandwidths within the BWP corresponding to the CORESET. In this way, a PDCCH is confined within an LBT bandwidth in order to avoid partial puncturing of a DCI. A UE can stop monitoring PDCCH search spaces on LBT bandwidth not available after acquiring the knowledge of transmitted LBT bandwidth(s) from GC-PDCCH. Within the search space set configuration associated with the CORESET, each of the one or more monitoring locations in the frequency domain corresponds to (and is confined within) an LBT bandwidth and has a frequency domain resource allocation pattern that is replicated from the pattern configured in the CORESET. In this way, CORESET parameters other than frequency domain resource allocation pattern is identical for each of the one or more monitoring locations in the frequency domain.

802. Had and 802.1 lay

[0004] Wireless Gigabit - WiGig (IEEE 802.1 lad) is a technology used to enable a close-range wireless connectivity of up to 6.75 Gbps. The IEEE 802. llad physical layer uses

2.16 GHz-width channels that theoretically provide data rate up to 6.76 GBPs per single channel.

WiGig signals are operating at the 60GHz frequency band (57-66GHz) which is regulated slightly differently in various parts of the world. To compensate for the path loss, the IEEE 802.1 lad device uses high gain antenna arrays. WiGig allows the use of four wide channels, each channel about 2.16GHz wide, can support OFDM (for longer distances & higher data rates) as well as Single carrier (for low power handheld devices) modulation schemes. With such wide channeling, it enables data rates up to 3 times faster than today’s Wi-Fi speeds.

[0005] IEEE 802.1 lay, is an enhancement specification of 802.1 lad. The band allocated to unlicensed use around 60 GHz has approximately 14 GHz of bandwidth, which is divided into channels of 2.16, 4.32, 6.48, and 8.64 GHz bandwidth. The channel bandwidth of 2.16 and 4.32 GHz is mandatory supported. The channel center frequencies for the 2.16 GHz channels are: 58.32, 60.48, 62.64, 64.80, 66.96, and 69.12 GHz for channel numbers 1 through 6, respectively as shown in FIG. 1. Unlike IEEE 802.11 ad, which only allows for single (2.16 GHz) channel transmission, 802.11 ay includes mechanisms for channel bonding and aggregation. In this way, 802.1 lay allows channel access over multiple channels. When using multiple channels, an access point (AP) can simultaneously transmit to multiple STAs allocated to different channels individually. In channel bonding, a single waveform covers at least two contiguous 2.16 GHz channels, whereas channel aggregation has a separate waveform for each aggregated channel. IEEE 802.1 lay mandates that enhanced Directional Multi Gigabit (EDMG) stations (STA)s must support operation in 2.16 GHz channels as well as channel bonding of two 2.16 GHz channels. Channel aggregation of two 2.16 GHz or two 4.32 GHz (contiguous or non contiguous) channels and bonding of three or four 2.16 GHz channels are optional. A bonded channel usually comprises one primary channel and one or more secondary channels. In order to guarantee the coexistence and backward compatibility with the legacy 802.1 lad devices that do not support channel bonding, all control and management frames must be transmitted over a single 2.16 GHz channel, which is called the primary channel. The rest of the channels are referred to as secondary channels. Primary channel is the common control channel of operations for all STAs that are members of the basic service set (BSS). There is only one channel serving as the primary channel and the position of the primary channel may be different. This means that the AP can dynamically choose a channel as the primary channel.

[0006] In 802.1 lay, FFT size of 512 together with SCS of 5.15625 MHz is used to achieve channel bandwidth of 2.16GHz, which can be extended with channel bonding up to maximum contiguous bandwidth of 4.32 GHz. The 802.11 ay sampling rate can be expressed as 512 x N _{CB X} 5.15625 MHz, where N _CB = 1, 2. The sampling frequency for 802.11 ay must be greater than 5.28 GHz. 802.11 ay supports high QAM modulation such as 64 QAM modulation, so the sampling bits per second (SBPS) requirement is up to 42.24 Gbs. This impose a stringent condition for Analog-to-digital (ADC) design for 802.11 ay standard specification.

[0007] This background information is provided to reveal information believed by the applicant to be of possible relevance. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art.

SUMMARY

[0008] Disclosed herein are methods, systems, and devices associated with channel access for NR in 52.6-71 GHz. In an aspect, multiple channel access schemes may be implemented. In an example, channel access may be based on multiple BWP(s) adaption, in which multiple BWP may be activated at a same time via DCI format 0 1. In another example, channel access may be based on carrier aggregation (CA).

[0009] In another aspect, enhancement for PDCCH monitoring COT are disclosed. In an example, the bitmap modification for the SearchSpace IE freqMonitorLocations may be achieved via MAC-CE or DCI. In another example, the PDCCH symbol duration may be set longer than the maximum number specified in FR1 (e.g., 3) and the channel BW is far less than the LBT BW.

[0010] In another aspect, after the UE receive the GC -PDCCH carrying LBT subband information, the UE may perform LBT on all available LBT subbands indicated by the gNB and send the LBT results or feedback via the following options. In a first option, PUCCH: a special PUCCH (PUCCH-LBT) can be used to carry LBT feedbacks. In a second option, configured grant (CG)-PUSCH can be used to carry LBT feedbacks. In a third option, physical random- access channel (PRACH) via either two-step or four-step RACH procedure can be used to carry LBT feedbacks.

[0011] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not constrained to limitations that solve any or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS [0012] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:

[0013] FIG. 1 illustrates an exemplary 802.11 ay channelization scheme;

[0014] FIG. 2 illustrates exemplary BWP configuration for UE 1 with numerology m=7 with maximum channel BW = 6 GHz and UE 102B with numerology m=8 with channel BW = 10 GHz;

[0015] FIG. 3 illustrates an exemplary carrier C for a serving cell that can be expressed in terms of LBT bandwidth B and number of LBT subbands 0, ... , M — 1;

[0016] FIG. 4 illustrates an exemplary effective channel bandwidth in a carrier C for a serving cell with 5 LBT subbands and the available LBT subbands are 1 and 4 at a time instance;

[0017] FIG. 5A illustrates exemplary multi-branches sampling circuits for contiguous multiple LBT subbands, such as a BWP is across 2 LBT subbands;

[0018] FIG. 5B illustrates exemplary multi -branches sampling circuits for contiguous multiple LBT subbands, such as a receiver with two-branches sampling circuits;

[0019] FIG. 6 A illustrates exemplary multi -branches sampling circuits for non contiguous multiple LBT subbands, such as 2 non-contiguous LBT subbands;

[0020] FIG. 6B illustrates exemplary multi-branches sampling circuits for non contiguous multiple LBT subbands, such as a receiver with two-branches sampling circuits;

[0021] FIG. 7A illustrates an exemplary multi-BWP groups, such as the contiguous

BWPs;

[0022] FIG. 7B illustrates exemplary multi-BWP groups, such as non-contiguous

BWPs;

[0023] FIG. 8 illustrates an exemplary UE configured with two BWP’s groups (BWP group ID=1, 2) and a BWP is activated for switching from the default BWP ID = 1 to the BWP ID = 2 in BWP group ID = 2;

[0024] FIG. 9 illustrates an exemplary two non-overlapped BWPs (e.g., BWP ID =2 and 3) are activated at a time instance;

[0025] FIG. 10A illustrates an exemplary UE support two cell aggregation, such as (frequency)- contiguous CCs;

[0026] FIG. 10B illustrates an exemplary UE support two cell aggregation, such as non- contiguous CCs;

[0027] FIG. 11 A illustrates an exemplary Guard band insertion in a configured BWP at a BWP with B GHz; [0028] FIG. 1 IB illustrates an exemplary Guard band insertion in a configured BWP at the both side of a BWP with hB GHz;

[0029] FIG. llC illustrates an exemplary Guard band insertion in a configured BWP at one of subband in a BWP with hB GHz;

[0030] FIG. 12 illustrates an exemplary UE feedbacks the sensing LBT subbands via PUCCH at a subband m,

[0031] FIG. 13 illustrates an exemplary display that may be generated based on the methods, systems, and devices of channel access for NR in 52.6-71 GHz;

[0032] FIG. 14A illustrates an example communications system;

[0033] FIG. 14B illustrates an exemplary system that includes RANs and core networks;

[0034] FIG. 14C illustrates an exemplary system that includes RANs and core networks;

[0035] FIG. 14D illustrates an exemplary system that includes RANs and core networks;

[0036] FIG. 14E illustrates another example communications system;

[0037] FIG. 14F is a block diagram of an example apparatus or device, such as a WTRU; and

[0038] FIG. 14G is a block diagram of an exemplary computing system.

[0039] FIG. 15 illustrates an exemplary method for channel access for NR in 52.6-71

GHz.

DETAILED DESCRIPTION

Statement 1

[0040] There may be a scenario in which at 52.6-71 GHz, a UE is capable of handling very high data rate processing, e.g. frequency sampling, battery, etc. In such scenario, there may be a question on how to support channel accessing opportunities across very wide channel bandwidth, for example, 4 GHz, 6 GHz, 8 GHz, and 10 GHz, if we assume the LBT bandwidth is equal to 2 GHz for co-existing with WiFi.

[0041] Conventionally in Rel-16, the channel occupation time (COT) CORESET is duplicated in each subband. Therefore, a UE can monitor COT CORESET in each subband to figure which subband is available and which subband is not. In Rel-17, each LBT subband may be up to 2 GHz, so UE still needs to monitor each subband to figure which subband available or not. This may require significant computation overhead and therefore high power consumption. How does a UE monitor COT indication within a wide band BWP with discontinuous PRB allocation while keeping the power consumption low?

Statement 2

[0042] An activated bandwidth part (BWP) can be split into multiple LBT subbands. Some successful LBT subbands may be indicated by gNB but may not be decoded successfully by a UE because of the hidden node issue. Therefore, when considering the hidden node effects, the channel may not be further utilized when a UE is activated with a wide BWP. For example, an activated BWP is composited of 5 contiguous LBT subbands where each LBT bandwidth assumes being equal to ~2 GHz. In an instance, gNB performs LBT for 5 LBT subbands and indicates the channel number 2, 4, and 6 are idle as shown in FIG. 2. In Release- 16, gNB may inform those available LBT subbands information to a group of UEs via the group common PDCCH (GC-PDCCH). However, the LBT results may be different at the UE due to the hidden node issue, so few of available LBT subbands sensed by the gNB may be noisy at the UE side. Therefore, the true available LBT subbands may be reduced and make the unlicensed spectrum sparser.

[0043] Below are some observations when a UE is activated with a wide BWP which is composed by several contiguous LBT subbands in 52.6-71 GHz.

[0044] First, in Release-16 NR-U, the unlicensed spectrum is based on sub-7 GHz band (e.g., FR1), therefore, the sampling frequency is around a hundred MHz (e.g. 100 MHz) even a UE activated with a maximum bandwidth needs to be supported, e.g., when a BWP bandwidth is equals to 5 LBT subbands. However, the unlicensed spectrum in 52.6-71 GHz (e.g., 6-10 GHz bandwidth) is much wider than the maximum unlicensed spectrum supported in the sub-7GHz (FR1), so in this case, the sampling frequency increases about 60-100 times than the sub-7GHz. Although gNB may signal the available LBT subbands for a group of UEs and UEs may avoid monitoring those unavailable LBT subbands, the UE operating at 52.6-71 GHz still may require larger sampling frequency than the UEs in the sub-7GHz when it is activated with an activated BWP composed by multiple contiguous LBT subbands.

[0045] Second, if a NR UE is capable of simultaneously accessing the whole unlicensed channel bandwidth (e.g. 12 GHz in FIG. 2) or all channel number (e.g. the channel number from 1 to 6 as shown in FIG. 1 and FIG. 2) in 52.6-71 GHz, then conventionally the UE has to support large subcarrier spacing (e.g. 3840 KHz) and the UE has to stay at an activated wide BWP (e.g. at least greater than 12 GHz as shown in FIG. 2). In this way, the UE may consume more power on transmitting/receiving (TX/RX) because it needs to use a large sampling rate to keep monitoring the whole unlicensed spectrum for GC-PDCCH to indicate the available LBT subbands (e.g., RB sets). Plus, according to the hidden node issue, the channel opportunities may become sparse or scattered into large separated non-contiguous channel numbers. Hence, for a UE constantly activated for a wide BWP may not be the optimal solution for channel access in this scenario.

[0046] Based on the above observations, how to reduce the power consumption or improve TX/RX power efficiency when a UE is activated for a wider BWP in a high frequency band with considering the hidden nodes issues?

Channel Access in 52.6-71 GHz

[0047] The minimum channel bandwidth of 802.11 ad/ay is equal to 2.16 GHz. Therefore, the LBT bandwidth for NR-U in 52.6-71 GHz band may be assumed around 2 GHz for co-existing with 802.1 lad/ay. NR 52.6-71 GHz frequency bands should support a generalized scalable numerology (SCS) as frequency range 1, FR1 (sub 7 GHz) and frequency range 2, FR2 (24-52.6 GHz) defined in Release- 15/16. The scalable SCS in NR can be expressed as a scalable subcarrier spacing factor as 2 ^m D/. where Af = 15 kHz is the minimum subcarrier spacing used in NR frequency range 1 (e.g., FR1) with m = 0,1,2 and FR2 with m = 3,4, correspondingly. Another factor for determining the supported SCS in 52.6-71 GHz may be the phase noise. The phase noise will increase with the carrier frequency increasing. Therefore, the subcarrier spacing for 52.6-71 GHz and beyond 52.6-71 GHz frequency band may be enlarged compared to the supported SCS in FR1 and FR2 band. Possible numerologies and the corresponding SCS in 52.6-71 GHz frequency bands are shown in Table 1.

Table 1: Possible supported numerologies for NR beyond 52.6-71 GHz.

[0048] For the numerology m = 3, 4 the corresponding SCS may be equal to 120, and 240 KHz, respectively. In these two cases, the SCS may be large enough to overcome the phase noise for OFDM transmission in 52.6-71 GHz frequency band. However, the maximum channel bandwidth that may be supported is less than the LBT bandwidth, e.g B = 2 GHz. Therefore, m = 5, 6, 7, 8 may be more suitable in terms of occupied channel bandwidth (OCB) requirement for NR-U co-existing with 802.11 ad/ay in 52.6-71 GHz frequency band. Therefore, there may be an assumption that the channel bandwidth in 52.6-71 GHz as multiple integer of B, e.g., B =

2 GHz.

[0049] In NR, different UE channel bandwidths may be supported within a spectrum band for transmitting to and receiving from UEs (e.g., UE 102 A of FIG. 14 A) connected to the gNB (e.g., base station 114a of FIG. 14A). For operations with carrier aggregation (CA), transmission with multiple carriers to the same UE or multiple carriers to different UEs within the gNB channel bandwidth can be supported. The UE 102A can report its physical layer parameters like BandCombinationList (a carrier aggregation parameters), BandNR (including DL and UL channel bandwidths parameters), etc. In 52.6-71 GHz frequency band, the channel bandwidth for unlicensed access can be very wide. For example, United States allocates 57-71 GHz frequency band and European Union allocates 57-66 GHz for unlicensed access.

[0050] From Table 1, the maximum channel bandwidth for numerology m = 6, 7 are equal to 3.2 GHz and 6.4 GHz, respectively. According to the current NR and NR-U specification, it only supports contiguous bandwidth part. In NR, UE 102A can report its capability through higher layer (e.g. RRC) like the physical layer, medium access control (MAC), radio link control (RLC), etc. In the physical layer parameters, UE 102A can report its channelBWs-DL or channelBWs-UL (channel bandwidth, supported numerologies) and BWP related information ( bwp-DiffNumerology , bwp-SameNumerology, etc,) in BandNR parameters to the network. The UE 102a operating at 52.6-71 GHz may report its capability as legacy UE in Release- 15 and 16.

[0051] For example, a UE (e.g. UE 102A in FIG. 2) supports numerology m = 7 thus the maximum channel bandwidth it can support is 6 GHz. In this case, the UE may be configured with 4 BWPs (BWP id = 1, 2, 3 and 4) and each BWP is equal to 6 GHz bandwidth to cover unlicensed frequency band from 57-69 GHz as depicted in FIG. 2. In FIG. 2, we demonstrate two UEs (e.g. UE 102 A and UE 102B) with different capability. The UE 102A is configured with 4 BWPs (e.g., each BWP is 6 GHz, numerology m = 7) and each BWP associated with different offsetToPointA. The UE 102B is configured with 4 BWPs (e.g. each BWP is 6 GHz, numerology m = 7) and each BWP associated with different offsetToPointA. When there are channel access opportunities from frequency bands 59-61, 63-65, 67-69 GHz, the UE 102A is not able to simultaneously access all those channel opportunities because the constraint of BWP adaption. When the allocated frequency band for unlicensed access for a serving cell is greater than the maximum channel bandwidth a UE can support, the current BWP operation defined in NR may not be able to fully utilize all of channel access opportunities to co-exist with 802.11ad/ay radio access technologies (RATs). To access the possible available channel opportunities, aUE (e.g. UE 102B shown in FIG. 2) may need to be configured with a BWP which it (almost) covers the whole unlicensed bandwidth (e.g. BWP = 10 GHz shown in FIG. 2). However, this may result in the UE 102b staying in a very wide BWP most of time, but the actual available channel opportunities may be sparse.

[0052] Disclosed in the following subsection are multiple channel access schemes based on multiple BWP(s) adaption and carrier aggregation (CA) respectively.

Channel access with multiple BWP(s) adaption

[0053] For WiFi 802.11 ad/ay operating in 52.6-71 GHz, it is mandatory to support at least two non-contiguous or contiguous channel numbers (e.g., channel number 1-6 as shown in FIG. 1 and FIG. 2). For example, an 802.1 lad/ay STP is capable to access three non-contiguous channel numbers (e.g. channel number 2, 4 and 6) simultaneously as shown in FIG. 2 with sampling rate around 6 GHz. However, if a NR UE is capable to support the maximum 6 GHz channel bandwidth with the subcarrier spacing (e.g., 1920 KHz) in 52.6-71 GHz with the 6 GHz sampling rate, then this NR UE still cannot simultaneously access some non-contiguous channel numbers when the channel number distance (e.g., the frequency separation from the biggest channel number to the minimum channel number) is greater than the maximum channel bandwidth of a UE (e.g., UE 102A in FIG. 2) can support. This is mainly because the current NR specification only allows contiguous allocation of physical radio blocks (PRBs) in a bandwidth part (BWP).

[0054] For simplicity without losing the generality, there may be an assumption that an allocated unlicensed carrier bandwidth C within 52.6-71 GHz can be expressed as C = B x M GHz for a serving cell, where B denotes the LBT bandwidth (in terms of GHz) and M is a positive integer denotes the total number of consecutive LBT subbands in C as shown in FIG. 3. Note, each LBT subband bandwidth is equivalent to the (primary) channel bandwidth defined in 802.11 ad/ay (e.g., 2.16 - 2 GHz). Therefore, each LBT subband ID can be mapped to a channel number defined in 802.1 lad/ay. In addition, we further assume that f _m denotes the center frequency of m-th LBT subband m e (0, ... , M — 1}. Here, the subband/channel distance between the subband/channel m ₁ and m ₂ is equal to (m ₂ — m^ x B. For an instance, we can assume B = 2 GHz and M = 6 for the unlicensed frequency band ranging from 57-69 GHz as shown in FIG. 3.

[0055] In practice, the channel opportunities in 52.6-71 GHz may be scattered into some LBT subbands as shown in FIG. 2 and the subband distance between two available subbands may be wide. In unlicensed band, a UE 102A may access those available subbands in C for transmission and reception for a certain time interval. The simplest way to access those available subbands for TX/RX is to sample the entire unlicensed bandwidth C then extract out those available subbands. This implementation scheme is suitable when the carrier bandwidth C is relative narrow. For example, the carrier bandwidth is C = 100 MHz for Release 16 NR-U, However, this kind of sampling approach may not be suitable when the carrier bandwidth C is wide (e.g. C from 6 to 10 GHz. Here, the effective channel bandwidth may be defined as follows.

[0056] First, the effective channel bandwidth is expressed as the sum of available LBT subband bandwidth at a time instance. For example, as shown in FIG. 4, if a carrier bandwidth C has M (e.g. M = 6) subbands and the subband m = 1 and 4 are available for a time instance, then the effective channel bandwidth is equal to x B = 2 x B (e.g. 2 x 2 = 4 ) GHz.

[0057] Second, if a UE 102A supports the maximum channel bandwidth for a certain numerology is greater than the effective channel bandwidth, then the UE 102A can access all available channel opportunities and the maximum sampling rate is equal to the effective channel bandwidth.

[0058] For example, as shown in FIG. 4, the LBT subband m = 0 and 3 may used by groups of UEs and 802.11 ad/ay primary channel 3 and 6 may be used by 802.11 ad/ay users at a time instance. In this example, the available LBT subbands are the the subband m = 1 and 4. If a UE 102A is assigned to access the the subband m = 1 and 4, then the effective channel bandwidth is equal to 2 x B (e.g. 2 x 2 = 4 ) GHz and the effective sampling frequency /rate is equal to 2 x B GHz as well. Based on the effective channel bandwidth, the effective sampling frequency may be lower than the actual carrier bandwidth C. Hence, the TX/RX efficiency may be improved because the effective sampling frequency /rate can be further reduced.

[0059] In sampling design, very high sampling rate can be implemented via several approaches. One of the sampling approaches implement the high sampling rate design via using the “multi-branches” sampling circuits as shown in FIG. 5. In FIG. 5, a BWP is configured with two LBT subbands, e.g., subband m — 1 and subband m. As shown in FIG. 5 (a), a contiguous BWP may include two distinct frequencies f _m-1 and f _m , where f _m- ± and f _m are the central frequency of subband m — 1 and m, respectively. In other words, the multi-branches sampling circuits are equipped with multiple sampling circuits to aggregate the effective sampling rate. For example, as shown in FIG. 5, each sampling branch performs the direct conversion with the frequency (e.g., f _m , etc.) then each frequency down-converted BWP is applied with a low pass filter (LPF) with bandwidth B and digitized by sampling rate B Gs. Therefore, the wide BWP may be restored via the digital domain after multi-branch sampling.

The effective (or aggregated) sampling rate may be equal to the sum of each sampling branch sample per second. B Gs.

[0060] Multi -branches sampling circuits also can be used for sampling the non contiguous LBT subbands as shown in FIG. 6. Here, the non-contiguous LBT subbands refer to two LBT subbands being separated by at least more than one LBT bandwidth, e.g., the BW separation between two LBT subbands can be expressed as q x B GHz, q > 1. In FIG. 6 example, there are two sampling branches and each sampling branch can sample an LBT subband with the sampling rate B Gs. The effective sampling rate is equivalent to 2 x B = 2B Gs for this example. It is clear to see that multiple-branches sampling design can be generalized for sampling Q E (1, , M] contiguous and non-contiguous LBT subbands simultaneously when the effective (or aggregated) sampling rate is equivalent to Q x B = QB Gs. [0061] The first method is based on partitioning multiple BWPs into different BWP’s group. For example, a UE 102A can be configured with N (e.g. N= 2) BWP’ groups denote as G ₀ , G . ... , G _n _1 and for a BWP’s group G _L . it can be configured with M BWPs where each BWP in the BWP’s group G _t is denoted as p _{G 0} , ... P _GUM-I · The UE 102A can be activated more than one BWPs when there is a need. For this method, BWP aggregation may be defined as when an activated BWP (e.g. p _{Gl j} ) in a BWP’s group (e.g. G ₍ ) is aggregated with at least another activated BWP (e.g. p _{Gk l} ) in different BWP’s group (e.g. G _k ). Note in this method, it doesn’t allow the aggregation of two different BWPs in a same BWP’s group. Plus, the activated BWP BWP’s group (e.g. G _L ) is not overlapped in the frequency-domain with other activated BWP (e.g. p _{Gk l} ) in the different BWP’s group (e.g. G _k ) for a serving cell. In other word, a UE 102A may be configured with multiple BWP’s groups (e.g. G ₀ , G . ... , G _N-1 ) and each BWP (e.g. p _Gl ) in a BWP’s group (e.g. G _L ) can be independently activated. Therefore, the BWP aggregation occurs when there are more than two BWPs activated from two different BWP’s groups. The BWP’s group (e.g. G _j ) with associated BWPs (e.g. p _{G 0} , ... p _{GhM- I} ) ^can be configured by the higher layer (e.g. RRC). For example, a UE 102A supports two aggregated number of BWP and the aggregated BWPs are from two BWP groups (e.g. BWP group ID = 1 and BWP group ID = 2). The need for the BWP aggregation is dependent on the channel opportunities.

- gNB (e.g., base station 114A) can configure multiple BWP’s group for a UE 102A. Each BWP’s group G _l . it can be configured with number of BWP M _L . each BWP in a BWP’s group G _t can be configured as multiple integer number of LBT subbands. Moreover, the sum of number of BWP M _j may not exceed the maximum number of BWP that the UE 102A can support. Each BWP (e.g. p _Gl ) in a BWP’s group (e.g. G _j ) can be operated as same as the BWP operation as Rel-15. In addition, any BWP (e.g. p _{Gl j} ) in a BWP’s group (e.g. G _j ) is non-overlapped with any BWP (e.g. p _{k j} ) in a BWP’s group (e.g. G _k ).

In this way, each BWP in a BWP’s group can be always independent operated without interference with other BWPs in the different BWP group. Configuration parameters for each BWP in a BWP’s group includes numerology, bandwidth size, frequency location, or CORESET. The BWP in a BWP’s group may be modified (including the default BWP) by higher layer (e.g., RRC) signaling.

- For each BWP’s group, a default BWP ( defaultDownlinkBWP-Id) may be configured for this BWP’ group. In this way, multiple default BWP can be supported as well. The UE may monitor the default BWP in the activated BWP’s group and the BWP activation and deactivation can be independently activated/deactivated for each BWP’s group. The BWP switching can be based on the DCI indication or the timer in each BWP’s group thus the activated BWP can fall back to its default BWP in each BWP’s group. The UE can keep track which default BWP can be fall back because the UE 102A know the BWP is activated from which BWP’s group. If the network doesn’t configure a default DL BWP for a BWP’s group, then the default DL BWP is the initial DL BWP for this BWP’s group. The gNB configures the defaultDownlinkBWP-Id which is one of the BWP Id of configured downlink BWPs in a BWP’s group. The UE 102A will switch to the default downlink/uplink BWP in a BWP’s group upon certain amount of inactivity on the current active downlink/uplink BWP. The BWP switching procedure for a BWP’s group in a serving cell is used to activate an inactive BWP and deactivate an active BWP at the same time. In FDD and within a BWP’s group, downlink and uplink can switch BWP independently but for TDD or flexible frame, both downlink and uplink should switch BWP simultaneously.

- Each BWP’s group can be independently enabled or disabled. If a BWP’s group is disabled then all configured BWP (including the default BWP for this BWP’s group) in this group may be disabled. Enabling or disabling of a BWP’s group may be signaled via DCI (the UE-specific PDCCH).

- The same or different COT indication (e.g. the DCI format 2 0 field CO- DurationPerCeU) may be independently transmitted or indicated for each BWP’s group. [0062] For example, a UE 102A supports the numerology m = 7, the maximum channel bandwidth = 4 GHz, the aggregated BWP bandwidth = 8 GHz and the number of aggregated BWP = 2. In this example, the UE may support the aggregated bandwidth up to 8 GHz. The aggregated bandwidth may be the contiguous BWPs or the non-contiguous BWP as shown in FIG. 5A or FIG. 6A, respectively. To support the contiguous BWPs or the non-contiguous BWP adaption, the multi-branches sampling circuits introduced in FIG. 5 and FIG. 6 as an example can be applied for the high sampling rate implementation. If the UE is equipped two (multiple) independent sampling branch as shown in FIG. 5 and FIG. 6, then the UE can support two BWP’s group (e.g., BWP group ID = 1 and 2) and each BWP’s group can be associated to one sampling branch as shown in FIG. 7A-7B. In each BWP’s group, it can be configured with several BWPs (e.g., = 4, M ₂ = 4). The configured BWP in each BWP’s group can be independently operated, e.g., each BWP can be activated by DCI and BWP switching can base on DCI, timer or higher layer (e.g. RRC) signaling.

[0063] If a UE can support multiple BWP’s groups, then monitoring the GC-PDCCH carrying the subband indication may be reduced. As shown in FIG. 8, a UE is configured with two BWP’s groups, e.g. BWP group ID = 1 and 2, each BWP group associate with M _t = 4 BWP, i = 1, 2, and with two default BWPs, one default BWP for each BWP’s group. In FIG. 8, the default BWP (e.g. BWP ID = 1) in BWP’s group ID = 1 and 2 is confined in an LBT subband. Therefore, the UE only monitors the GC-PDCCH carrying COT information for each BWP’s group and don’t have to monitor other LBT subbands for PDCCH. After the UE acquire the COT information, if there is a scheduled data for the UE 102A, gNB (e.g., base station 114A) may activate one BWP’s group or both of BWP’s group (in practice, the activated BWP (in a BWP’s group) is across contiguous LBT subbands). UEs can monitor the default BWP in a BWP’s group with the bandwidth being confined within an LBT bandwidth, e.g., B for (GC-)PDCCH. Since gNB performs LBT before sending the subband information thus gNB can activate the BWP (the BWP with success LBT) for the scheduled data when there is a need. In this way, GC- PDCCH carrying subband indication may not require so the UE can save the effort for the detection of GC-PDCCH carrying subband information.

[0064] The second method is based on activating multiple non-overlapping BWPs.

First, the UE can report its capability parameters bwp-BandwidthClassDL/UL-NR and the bwp- BandwidthClassDL/UL-NR defines for DL/UL, the class defined by the activated (transmission) BWP configuration and the maximum number of activated BWPs supported by the UE, respectively. Here, multiple BWP activation means that multiple (distinct) non-overlapping BWPs in the frequency-domain (FD) can be activated. For example, a UE may be configured with M different non-overlapped BWPs denotes as BWP p ₀ , ... p _M-i and each BWP can be independently configured with its own numerology, bandwidth (in terms of multiple of LBT subbands), switching timer ( bwp-InactivityTimer ), etc. In general, for any BWP p _L and p _y . i e (1, ... M], j e (1, ... M] and i ¹ j can be activated when p ₍ and p ₇ are non-overlapped in the FD.

[0065] Each BWP p ₀ , ... p _M-i can be independently enabled or disabled and a same or different COT indication (e.g. the DCI format 2_0 field CO-DurationPerCell ) can be independently transmitted or indicated for each BWP (e.g. p; i e (1, ... M}).

[0066] If there is more than one BWPs activated (e.g., BWP p _t and p _y are activated), then in this case, the UE 102A may switch back to the default BWP (if configured) or the initial BWP when the longest COT duration among those activated BWPs (e.g. the maximum COT duration of p _t and p _j ) is expired.

[0067] Multiple (up to Q ) BWPs can be activated by multiple BWP indicators in DCI Format 0_1. The information {BWP-Id 1, BWP-Id 2, , BWP-Id Q} is transmitted by means of the DCI format 1 0. The value Q is the parts of the RRC configuration.

As shown in FIG. 9, there are two non-overlapped BWPs (e.g., BWP ID = 2 and 3) are activated at a time instance.

Channel access with carrier aggregation (CA)

[0068] In NR, a UE 102 A may simultaneously receive or transmit on one or multiple component carriers (CCs) depending on its capabilities. Also, carrier aggregation (CA) refers to two or more component carriers (CCs) are aggregated and CA is supported for both contiguous and non-contiguous CCs in NR. To support the contiguous CCs or non-contiguous CCs, the multi-branches sampling circuits introduced in FIG. 5 and FIG. 6 (e.g., FIG. 5A-5B, FIG. 6A- 6B) may be applied for the high sampling rate implementation. Support of both contiguous and non-contiguous aggregated CCs may be analog to the scenario where the channel access opportunities do not have to be contiguous but may be dispersed in 52.6-71 GHz frequency bands. Therefore, we can map the channel access opportunities to the carrier aggregation (CA) framework for unlicensed spectrum in 52.6-71 GHz. Examples for channel access opportunities via carrier aggregation (CA) are below:

- The UE 102 A can report its capability e.g. ca-BandwidthClassDL-NR/· ca- BandwidthClassUL-NR for the aggregated DL/UL transmission bandwidth configuration and maximum number of component carriers (CCs) supported by the UE 102 A.

- The primary cell (PCell) (e.g., primary carrier) may transmit synchronization signal Block (SSB) or discovery reference signal (DRS) so the UE 102A can discover the primary component, e.g., the DL sync raster is within PCell (e.g., primary carrier). One or more secondary cells (SCells) (e.g., secondary carrier) can be configured once the UE 102 A is in connected mode. In addition, gNB can signal the UE 102 A to re-select the PCell.

- The channel bandwidth for the PCell and SCell can be set as multiple integer of LBT bandwidth, e.g., the channel bandwidth of PCell and SCell can be expressed as M x B GHz, where is M is a positive integer. Note: the channel BW of SCell can be independent indicated by the PCell. - The SCells (e.g. secondary component carriers) can be rapidly activated or deactivated to meet the variations of the load pattern and channel availability. The activation and deactivation can be done by MAC CE or DCI.

- CA (e.g. intra-band aggregation) in 52.6-71 GHz is supported for (frequency -)contiguous CCs (or cells) or non-contiguous CCs (or cells).

- Different UEs may switch to (e.g., camp on) different cells (or component carrier) as their PCell or primary component carrier, the configuration of the PCell or primary component carrier (CC) can be UE-specific. The configuration of candidate CC can be configured by RRC and switching of primary CC can be done via MAC-CE. In addition, the secondary CC can be switched as well.

- In case of FDD, the number of carriers (or cells) does not have to be the same in uplink and downlink.

- Cross-carrier scheduling and joint feedback are supported. In this case, PCell can perform cross-carrier scheduling and joint feedback. As NR Release- 16, both COT and LBT subbands/RB sets can indicate multiple Cells (PCell and SCells). Therefore, when cross carrier scheduling and feedback are supported, in this case, UE won’t expect the COT duration in a SCell is longer than in the PCell. However, if one of the aggregated SCell COT’s duration is longer than the PCell then the UE 102A may assume no cross scheduling for this SCell once PCell’s COT expired.

- Carriers (or cells) can be configured with different numerologies (e.g., SCS, slots, cyclic prefix (CP) etc.), For example, primary CC use SCS = 15 KHz and secondary use SCS = 30 KHz.

[0069] For example, as shown in FIG. 10A - FIG. 10B, UE 102A supports the numerology m = 7. the maximum channel bandwidth = 4 GHz, and the number of aggregated Cell = 2. In this example, the UE can support the aggregated bandwidth up to 8 GHz. The aggregated bandwidth can be the contiguous CCs (or cells) or the non-contiguous intra-band CCs (or cells) as shown in FIG. 10A and FIG. 10B, respectively. To support the contiguous CCs or the non-contiguous CCs, the multi-branches sampling circuits introduced FIG. 5 and FIG. 6, can be applied for the high sampling rate implementation. When the UE 102 A is equipped two (e.g., multiple) independent sampling branch as shown in FIG. 5 and FIG. 6, then the UE 102A can support at least two cell aggregation (e.g., one PCell and one SCell) and each CC can be associated to one sampling branch as shown in FIG. 5 and FIG. 6. The SCell can be activated or deactivated by MAC CE. The activation or deactivation can be depending on the channel access opportunities.

[0070] FIG. 15 illustrates an exemplary method associated with carrier aggregation.

One or more devices in the network may execute the method. For example, at step 201, based on receiving the SSB or DR, a user equipment may camp on a primary cell (PCell). At step 202, a device may receive first information about a user equipment, the first information may include a capability of the user equipment to perform carrier aggregation for an uplink transmission or carrier aggregation for a downlink transmission. At step 203, the device may send a configuration to the user equipment, the configuration may include the component carrier information to enable carrier aggregation based on the first information. The capability may include a maximum aggregated number of component carriers (CCs) or maximum bandwidth configuration. At step 204, the device may detect that the user equipment is in connected mode and based on the detecting the user equipment is in connected mode, configure one or more secondary cells (SCells). This configuration of step 204 may be based on the carrier aggregation capability of the user equipment or the base station. The device may provide instructions for activating or deactivating the one or more secondary cells (SCells) based on variations of a load pattern or channel availability associated with the user equipment. The activating or deactivating the one or more secondary cells (SCells) may be based on an indication from a medium access control control element (MAC CE) or downlink control indicator (DCI). a. Channel access in a wideband BWP

[0071] It may be assumed that the same principle applying the usage of guard band in BWP defined in NR Release- 16 to the BWP in 52.6-71 GHz unlicensed spectrum. The minimum bandwidth (BW) for a configured BWP can be assumed equal to B GHz with respect to a numerology m, which refers the minimum BW for a configured BWP being equal to the LBT bandwidth B GHz. In this case, guard bands [GB ^l0W , GB ^high } can be inserted at both side of the BWP as show in FIG. 11 A. The guard band { GB ^l0W , GB ^high can be configured by the higher layer (e.g., RRC) parameters. The bandwidth of a configured BWP for a UE 102A can be equal to h LBT bandwidths, e.g., h x B GHz, with respect to a numerology m. where integer h satisfies h £ M and B GHz is a LBT bandwidth or a LBT subband. When a configured BWP is equal to multiple LBT subbands, the guard bands can be inserted at the both side of the BWP or at both sides of a subband in the BWP as shown in FIG. 1 IB and FIG. 11C, respectively. [0072] For example, by allocating 180 PRBs with 960 kHz SCS, the allocation bandwidth corresponds to 2.07 GHz (~ 2 GHz) which is well suited to the 2.16 GHz channel bandwidth, corresponding to wireless local area network (WLAN) 802.1 lad/ay channel spacing. In Table 2, possible channel bandwidth as multiple of 2 GHz are listed. UE 102A can indicate its supported channel bandwidth (CBW) via high-level (RRC) signaling channelBWs-DL and channelB Ws-UL.

Table 2: Possible channel bandwidth as multiple integer of 2 GHz for NR-U in 52.6-71

GHz frequency band.

[0073] From Table 1 and Table 2, the minimum sampling rate (or Nyquist rate) for supporting channel bandwidth 12 GHz with the numerology m = 8 is equal to 15.728 GHz (or 15.728 Gs, sample per second). Since high sampling rate is used to support sampling the channel bandwidth (CBW) range from 2-12 GHz in 52.6-71 GHz frequency band. With such a high sampling rate, the analog-to-digital converter (ADC) and digital-to-analog converter (DAC) may consume more power than at FR1 and FR2. Therefore, power consumption is more critical than in FR1.

Channel access with LBT subband COT monitoring

[0074] In NR Release- 15, the PDCCH monitoring information per search space is configured via RRC, such as PDCCH monitoring periodicity, offset and symbols for PDCCH monitoring in the slots. In NR Release- 16, a UE 102A may be provided a group index for a respective search space set by searchSpaceGroupIdList-r 16 for PDCCH monitoring on a serving cell. For example, a UE 102A is configured with two groups of search space sets for monitoring PDCCH. gNB (e.g., gNB 114a of FIG. 14A) may signal the switching of monitoring PDCCH occasions via search space group (e.g., group 1 and group 2). For each search space a UE 102A may be configured with a search space outside a COT so that the UE 102A may only monitor the search space (e.g. group 1) with a configured monitoring occasion before receiving any indication in GC-PDCCH. Once, the UE 102A receive the first GC -PDCCH with the search space switching flag (SearchSpaceSwitchTrigger-r 16), the UE 102A may switch to another search space (e.g. group 2, inside the COT) for PDCCH monitoring. In practice, mini-slot level PDCCH monitoring (or PDCCH search space monitoring in any symbol within the slot) may be applied to the outside the COT of search space (e.g. group 1), thus it has shorter period than another search space (e.g. group 2). Therefore, the UE 102A can relax the PDCCH search effort after receiving the COT indication. In addition, a search space set configuration associated with multiple monitoring locations in the frequency domain (freqMonitorLocations-r 16). The freqMonitorLocations-r 16 provides a bitmap where the first bit in the bitmap corresponds to the first LBT subband (RB set) in the BWP, and the second bit corresponds to the second LBT subband (RB set), and so on.

[0075] However, the UE 102A may still search all possible LBT subbands/RB sets to detect the GC-PDCCH for COT and available subbands/RB sets indication in NR Release- 16. In FR1, this kind of intense PDCCH monitoring before obtaining the COT in the wideband operation is manageable in terms of power consumption. The power consumption for PDCCH searching effort wideband operation may become unmanageable in in 52.6-71 GHz and beyond because ultra-high sampling rate (at least 60-100 times more than in FR1) is required. To reduce the PDCCH monitoring computation complexity and efforts, we disclose a type of PDCCH channel design which allows UE 102A to lower the required bandwidth for the COT monitoring.

[0076] The bitmap modification for the SearchSpace IE freqMonitorLocations introduced in NR Release- 16 can be enhanced. The modification of freqMonitorLocations for a search space can only be done via RRC reconfiguration in Release- 16. There are some advantages if the freqMonitorLocations bitmap can be adjusted quicker in 52.6-71 GHz (FR4) and beyond. For example, if gNB (e.g., base station 114a of FIG. 14A) can predict the LBT results (e.g. by statistic or load pattern) and then it may adjust bitmap of freqMonitorLocations for a UE or group of UEs so UE 102A can perform the PDCCH monitoring COT more efficiency. Therefore, we disclose the bitmap modification for the SearchSpace IE freqMonitorLocations can be achieved via MAC-CE or DCI (e.g DCI format 2 _x, x=7). For example, RRC can configure multiple (or a set) bitmaps for SearchSpace IE freqMonitorLocations and choose one initial bitmap from the set. Then later on, dependent on necessarily, gNB can send an indication via MAC-CE or DCI to indicate which bitmap in the set to be used for the search space.

[0077] The PDCCH symbol duration (RRC IE duration ) in RRC ControlResourceSet parameter can be set to greater than the maximum number of symbols used in FR1 (e.g. 3 symbols). This are two motivations: first, when the bandwidth B _PDCCH for a CORESET monitoring the COT (GC-PDCCH) is « B, to carry certain payload (e.g. control channel elements, CCE) of DCI, the PDCCH symbol duration can be prolonged. Second, the symbol duration in FR4 is relative short than the symbol duration in FR1. For example, the symbol duration in 52.6-71 GHz (or FR4) is much shorter when the larger m is used, e.g., 0.559 us for m = 7 and 0.278 us for m = 8. The shortest slot symbol duration (e.g. m = 2) support in FR1 is equal 17.85 us. Therefore, even the PDCCH channel duration with 14 symbols (one slot) with m = 7 in FR4 is around 7.82 us which the PDCCH channel duration is less than the PDCCH channel in FR1.

[0078] The PRBs allocated by frequencyDomainResources for a CORESET monitoring the COT in an activated wide BWP are confined within the (sub)bandwidth B _PDCCH and Bp _D cc _H « B GHz. Assuming the bandwidth of the activated BWP is equal to M x B _PDCCH GHz, where M is the (integer) number of LBT subbands configured for this activated BWP. Disclosed is a channel bandwidth B from 52.6-71 GHz and above can be sub-partitioned to several subbands (e.g., B _PDCCH ) or LBT bandwidth. One of design example to sub-partitioned a channel bandwidth from B to several subbands is described as follows: let FFT size for this activated BWP denote as N _FFT , in Table 2, e.g., N _FFT = 2048 for an activated BWP with 132 PRBs, the bandwidth is around 6 GHz when numerology m = 8 /SCC = 3840. If the bandwidth B _PDCCH for a CORESET monitoring the COT is far less than the LBT subband bandwidth B i.e., B _PDCCH «

B then it can find a suitable smaller FFT size (denotes as N _{FFT PDCCH} ) to decode the PDCCH without using the whole FFT size (i.e., N _FFT ) and N _{FFT PDCCH} satisfy N _{FFT PDCCH} = N _FFT /2 ⁿ .

The UE 102A may not expect to monitor the UE-specific search space (USS) before the COT is available and the UE may use a configured shorter period of search space to monitor PDCCH. Hence, with narrow subband B _PDCCH , the UE can save more computation complexity and reduce the sampling frequency since UE only monitor fewer subband for power saving. gNB also signal a minimal K ₀ value for scheduled a or multiple PDSCH(s). Therefore, UE can further save power. [0079] When the numerology is greater than x, i.e., m ³ x (e.g., x = 6), the slot duration is relatively short compared to the slot duration used in FR1, therefore, the support of mini-slot monitoring occasion for search space in a slot may not be required when the numerology is greater than x in 52.6-71 GHz/FR4. That is the UE 102A may not be expected to be configured a search space with mini-slot.

[0080] Once the UE 102A receive the GC-PDCCH carrying COT and LBT subband (available RB sets) information, the UE 102A may perform LBT on all available LBT subbands indicated by the gNB and feedback the sensing LBT results via the following options, such as PUCCH-LBT, configured grant (CG) PUSCH LBT, or PRACH via two step RACH as disclosed herein.

[0081] PUCCH-LBT. A special PUCCH for carrying LBT results can be used. The feedback information (e.g. a bitmap) includes the available sensed LBT subbands/RB sets. If the information for LBT feedback is less than 2 bits then short PUCCH format otherwise long PUCCH format can be used for PUCCH-LBT. The priority of PUCCH-LBT can be lower than PUCCH transmission with HARQ-ACK information, beam failure request (PUCCH-BFR) or SR. The PUCCH resource can be confined in an LBT subband/RB set m and gNB can configure the resource for PUCCH-LBT. The PUCCH-LBT transmission can be done when UE performs the category-2 (cat-2) LBT while the UE is COT-sharing with the gNB.

[0082] Configured-grant (CG)-PUSCH-LBT. If there is a nearest CG-PUSCH occasion in an LBT subband/RB set m when UE 102A perform Cat-2 LBT then UE 102A can transmit LBT feedback via CG-PUSCH (piggyback).

[0083] The contention-free or contention based physical random-access channel (PRACH) via either two-step RACH. The gNB may assign the random-access channel occasion (RO) for each LBT subband and the UE can feedback the LBT results in an LBT subband m where the UE 102A receive the GC-PDCCH carrying subband indication information. Since COT-sharing has been proposed in Release- 16, so the UE 102 A may not need to perform the category -4 (cat-4) LBT and instead, UE 102A performs the category -2 (cat-2) LBT while the UE 102A is COT-sharing with the gNB. The feedback information may include the LBT results from performing sensing all available LBT subbands indicated by gNB. If the feedback LBT result is equal to one bit then only the PRACH preamble is transmitted. If UE 102A use the two- step RACH for LBT feedback, then the feedback information is transmitted in the PUSCH when the LBT feedback information is greater one bit. The selection of RO (e.g., preamble and PUSCH resources) can be based on the TCI state of GC-PDCCH.

[0084] The above method can also apply when UE perform Cat-4 LBT with initiating an uplink transmission.

[0085] It is understood that the entities performing the steps illustrated herein, such as FIG. 1 - FIG. 15, may be logical entities. The steps may be stored in a memory of, and executing on a processor of, a device, server, or computer system such as those illustrated in FIG. 14F or FIG. 14G. Skipping steps, combining steps, or adding steps between exemplary methods disclosed herein (e.g., FIG. 1 - FIG. 15) is contemplated.

[0086] As shown in FIG. 12, gNB (e.g., base station 114A) may send burst transmission for COT and subband indication information via GC-PDCCH. Once the UE 102A successfully decode the GC-PDCCH carrying subband indication in an LBT subband m (e.g., m = 2), then the UE 102A may perform LBT for other LBT subbands (e.g., subband 1, 2 and 4). After the UE 102A finishes sensing available subbands indicated by gNB (e.g., subband 1, 2 and 4), UE 102A may feedback the LBT results (e.g. subband 2 and 4) to gNB. In practice, the LBT results sensed by the UE 102A (e.g., subband 2 and 4) may not exactly equal to the available subbands indicated by gNB (e.g., subband 1, 2 and 4) as shown in FIG. 12. This is because the LBT results sensed by the UE 102A may not be same as the LBT results sensed by gNB.

Table 3 - Abbreviations and Definitions

[0087] The disclosed subject matter may promote channel access using carrier aggregation (CA). Also disclosed is a channel bandwidth B that can be further partitioned into several subbands when subband bandwidth Bs = B/M where M is an integer. In addition, disclosed herein is a prompting UE can be enabled by more than one bandwidth part, among other things.

[0088] FIG. 13 illustrates an exemplary display (e.g., graphical user interface) that may be generated based on the methods, systems, and devices of channel access for NR in 52.6-71 GHz, as discussed herein. Display interface 901 (e.g., touch screen display) may provide text in block 902 associated with of channel access for NR in 52.6-71 GHz method flow, architecture, or parameters. Progress of any of the steps (e.g., sent messages or success of steps) discussed herein may be displayed in block 902. In addition, graphical output 902 may be displayed on display interface 901.

[0089] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, the core transport network, and service capabilities - including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred as 3G), LTE (commonly referred as 4G), LTE- Advanced standards, and New Radio (NR), which is also referred to as “5G”. 3GPP NR standards development is expected to continue and include the definition of next generation radio access technology (new RAT), which is expected to include the provision of new flexible radio access below 7 GHz, and the provision of new ultra-mobile broadband radio access above 7 GHz. The flexible radio access is expected to consist of a new, non-backwards compatible radio access in new spectrum below 6 GHz, and it is expected to include different operating modes that may be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with diverging requirements. The ultra-mobile broadband is expected to include cmWave and mmWave spectrum that will provide the opportunity for ultra-mobile broadband access for, e.g., indoor applications and hotspots. In particular, the ultra-mobile broadband is expected to share a common design framework with the flexible radio access below 7 GHz, with cmWave and mmWave specific design optimizations.

[0090] 3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide variety of user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (eMBB) ultra-reliable low-latency Communication (URLLC), massive machine type communications (mMTC), network operation (e.g., network slicing, routing, migration and interworking, energy savings), and enhanced vehicle-to-every thing (eV2X) communications, which may include any of Vehicle-to-Vehicle Communication (V2V), Vehicle-to-Infrastructure Communication (V2I), Vehicle-to-Network Communication (V2N), Vehicle-to-Pedestrian Communication (V2P), and vehicle communications with other entities. Specific service and applications in these categories include, e.g., monitoring and sensor networks, device remote controlling, bi-directional remote controlling, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity, automotive ecall, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile internet, virtual reality, home automation, robotics, and aerial drones to name a few. All of these use cases and others are contemplated herein.

[0091] FIG. 14A illustrates an example communications system 100 in which the methods and apparatuses of channel access for NR in 52.6-71 GHz, such as the systems and methods illustrated in FIG. 1 through FIG. 12 described and claimed herein may be used. The communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, or 102g (which generally or collectively may be referred to as WTRU 102 or WTRUs 102 or also known as a UE). The communications system 100 may include, a radio access network (RAN) 103/104/105/103b/104b/105b, a core network 106/107/109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and Network Services 113. Network Services 113 may include, for example, a V2X server, V2X functions, a ProSe server, ProSe functions, IoT services, video streaming, or edge computing, etc.

[0092] It will be appreciated that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, orl02g may be any type of apparatus or device configured to operate or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be depicted in FIG. 14 A, FIG. 14B, FIG. 14C, FIG. 14D, FIG. 14E, or FIG. 14F as a hand-held wireless communications apparatus, it is understood that with the wide variety of use cases contemplated for 5G wireless communications, each WTRU may comprise or be embodied in any type of apparatus or device configured to transmit or receive wireless signals, including, by way of example only, user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, bus, truck, train, or airplane, and the like.

[0093] The communications system 100 may also include a base station 114a and a base station 114b. In the example of FIG. 14A, each base stations 114a and 114b is depicted as a single element. In practice, the base stations 114a and 114b may include any number of interconnected base stations or network elements. Base stations 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks, such as the core network 106/107/109, the Internet 110, Network Services 113, or the other networks 112. Similarly, base station 114b may be any type of device configured to wiredly or wirelessly interface with at least one of the Remote Radio Heads (RRHs) 118a, 118b, Transmission and Reception Points (TRPs) 119a,

119b, or Roadside Units (RSUs) 120a and 120b to facilitate access to one or more communication networks, such as the core network 106/107/109, the Internet 110, other networks 112, or Network Services 113. RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102, e.g., WTRU 102c, to facilitate access to one or more communication networks, such as the core network 106/107/109, the Internet 110, Network Services 113, or other networks 112

[0094] TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRU 102d, to facilitate access to one or more communication networks, such as the core network 106/107/109, the Internet 110, Network Services 113, or other networks 112. RSUs 120a and 120b may be any type of device configured to wirelessly interface with at least one of the WTRU 102e or 102f, to facilitate access to one or more communication networks, such as the core network 106/107/109, the Internet 110, other networks 112, or Network Services 113. By way of example, the base stations 114a, 114b may be a Base Transceiver Station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a Next Generation Node-B (gNode B), a satellite, a site controller, an access point (AP), a wireless router, and the like.

[0095] The base station 114a may be part of the RAN 103/104/105, which may also include other base stations or network elements (not shown), such as a Base Station Controller (BSC), a Radio Network Controller (RNC), relay nodes, etc. Similarly, the base station 114b may be part of the RAN 103b/104b/105b, which may also include other base stations or network elements (not shown), such as a BSC, a RNC, relay nodes, etc. The base station 114a may be configured to transmit or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). Similarly, the base station 114b may be configured to transmit or receive wired or wireless signals within a particular geographic region, which may be referred to as a cell (not shown) for methods, systems, and devices of channel access for NR in 52.6-71 GHz, as disclosed herein. Similarly, the base station 114b may be configured to transmit or receive wired or wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an example, the base station 114a may include three transceivers, e.g., one for each sector of the cell. In an example, the base station 114a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

[0096] The base stations 114a may communicate with one or more of the WTRUs 102a, 102b, 102c, or 102g over an air interface 115/116/117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115/116/117 may be established using any suitable radio access technology (RAT).

[0097] The base stations 114b may communicate with one or more of the RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b, over a wired or air interface 115b/ 116b/ 117b, which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115b/l 16b/l 17b may be established using any suitable radio access technology (RAT).

[0098] The RRHs 118a, 118b, TRPs 119a, 119b or RSUs 120a, 120b, may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f over an air interface 115c/l 16c/l 17c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c/116c/117c may be established using any suitable radio access technology (RAT).

[0099] The WTRUs 102a, 102b, 102c,102d, 102e, or 102f may communicate with one another over an air interface 115d/l 16d/l 17d, such as Sidelink communication, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115d/l 16d/l 17d may be established using any suitable radio access technology (RAT). [00100] The communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC- FDMA, and the like. For example, the base station 114a in the RAN 103/104/105 and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b,TRPs 119a, 119b and RSUs 120a, 120b, in the RAN 103b/104b/105b and the WTRUs 102c, 102d, 102e, 102f, may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 or 115c/l 16c/l 17c respectively using wideband CDMA (WCDMA). 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).

[00101] In an example, the base station 114a and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b in the RAN 103b/104b/105b and the WTRUs 102c, 102d, may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 115/116/117 or 115c/l 16c/l 17c respectively using Long Term Evolution (LTE) or LTE- Advanced (LTE-A). In the future, the air interface 115/116/117 or 115c/l 16c/l 17c may implement 3GPP NR technology. The LTE and LTE-A technology may include LTE D2D and V2X technologies and interfaces (such as Sidelink communications, etc.). Similarly, the 3GPP NR technology includes NR V2X technologies and interface (such as Sidelink communications, etc.).

[00102] The base station 114a in the RAN 103/104/105 and the WTRUs 102a, 102b, 102c, and 102g or RRHs 118a, 118b, TRPs 119a, 119b or RSUs 120a, 120b in the RAN 103b/104b/105b and the WTRUs 102c, 102d, 102e, 102f may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[00103] The base station 114c in FIG. 14A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a train, an aerial, a satellite, a manufactory, a campus, and the like, for implementing the methods, systems, and devices of channel access for NR in 52.6-71 GHz, as disclosed herein. In an example, the base station 114c and the WTRUs 102, e.g., WTRU 102e, may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN) similarly, the base station 114c and the WTRUs 102d, may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another example, the base station 114c and the WTRUs 102, e.g., WTRU 102e, may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a picocell or femtocell. As shown in FIG. 14A, the base station 114cmay have a direct connection to the Internet 110. Thus, the base station 114c may not be required to access the Internet 110 via the core network 106/107/109.

[00104] The RAN 103/104/105 or RAN 103b/104b/105b may be in communication with the core network 106/107/109, which may be any type of network configured to provide voice, data, messaging, authorization and authentication, applications, or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106/107/109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, etc., or perform high-level security functions, such as user authentication.

[00105] Although not shown in FIG. 14A, it will be appreciated that the RAN 103/104/105 or RAN 103b/104b/105b or the core network 106/107/109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103/104/105 or RAN 103b/104b/105b or a different RAT. For example, in addition to being connected to the RAN 103/104/105 or RAN 103b/104b/105b, which may be utilizing an E-UTRA radio technology, the core network 106/107/109 may also be in communication with another RAN (not shown) employing a GSM or NR radio technology.

[00106] The core network 106/107/109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired or wireless communications networks owned or operated by other service providers. For example, the networks 112 may include any type of packet data network (e.g., an IEEE 802.3 Ethernet network) or another core network connected to one or more RANs, which may employ the same RAT as the RAN 103/104/105 or RAN 103b/104b/105b or a different RAT.

[00107] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communications system 100 may include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks over different wireless links for implementing methods, systems, and devices of channel access for NR in 52.6-71 GHz, as disclosed herein. For example, the WTRU 102g shown in FIG. 14A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.

[00108] Although not shown in FIG. 14A, it will be appreciated that a User Equipment may make a wired connection to a gateway. The gateway maybe a Residential Gateway (RG). The RG may provide connectivity to a Core Network 106/107/109. It will be appreciated that much of the subject matter included herein may equally apply to UEs that are WTRUs and UEs that use a wired connection to connect with a network. For example, the subject matter that applies to the wireless interfaces 115, 116, 117 and 115c/l 16c/l 17c may equally apply to a wired connection.

[00109] FIG. 14B is a system diagram of an example RAN 103 and core network 106 that may implement methods, systems, and devices of channel access for NR in 52.6-71 GHz, as disclosed herein. As noted above, the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also be in communication with the core network 106. As shown in FIG. 14B, the RAN 103 may include Node-Bs 140a, 140b, and 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 115. The Node- Bs 140a, 140b, and 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and Radio Network Controllers (RNCs.)

[00110] As shown in FIG. 14B, the Node-Bs 140a, 140b may be in communication with the RNC 142a. Additionally, the Node-B 140c may be in communication with the RNC 142b. The Node-Bs 140a, 140b, and 140c may communicate with the respective RNCs 142a and 142b via an Iub interface. The RNCs 142a and 142b may be in communication with one another via an Iur interface. Each of the RNCs 142aand 142b may be configured to control the respective Node-Bs 140a, 140b, and 140c to which it is connected. In addition, each of the RNCs 142aand 142b may be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, and the like.

[00111] The core network 106 shown in FIG. 14B 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. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned or operated by an entity other than the core network operator.

[00112] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c, and traditional land-line communications devices.

[00113] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150.

The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, and 102c, and IP-enabled devices.

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

[00115] FIG. 14C is a system diagram of an example RAN 104 and core network 107 that may implement methods, systems, and devices of channel access for NR in 52.6-71 GHz, as disclosed herein. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.

[00116] The RAN 104 may include eNode-Bs 160a, 160b, and 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs. The eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. For example, the eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. [00117] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink or downlink, and the like. As shown in FIG. 14C, the eNode-Bs 160a, 160b, and 160c may communicate with one another over an X2 interface.

[00118] The core network 107 shown in FIG. 14C may include a Mobility Management Gateway (MME) 162, a serving gateway 164, and a Packet Data Network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 107, it will be appreciated that any one of these elements may be owned or operated by an entity other than the core network operator.

[00119] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, and 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, and 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[00120] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via the SI interface. The serving gateway 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, and 102c. The serving gateway 164 may also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, and 102c, managing and storing contexts of the WTRUs 102a, 102b, and 102c, and the like.

[00121] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c, and IP-enabled devices.

[00122] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices. For example, the core network 107 may include, or may communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may include other wired or wireless networks that are owned or operated by other service providers.

[00123] FIG. 14D is a system diagram of an example RAN 105 and core network 109 that may implement methods, systems, and devices of channel access for NR in 52.6-71 GHz, as disclosed herein. The RAN 105 may employ an NR radio technology to communicate with the WTRUs 102a and 102b over the air interface 117. The RAN 105 may also be in communication with the core network 109. A Non-3GPP Interworking Function (N3IWF) 199 may employ a non-3GPP radio technology to communicate with the WTRU 102c over the air interface 198.

The N3IWF 199 may also be in communication with the core network 109.

[00124] The RAN 105 may include gNode-Bs 180a and 180b (which may also be generally referred to as base station 114A). It will be appreciated that the RAN 105 may include any number of gNode-Bs. The gNode-Bs 180a and 180b may each include one or more transceivers for communicating with the WTRUs 102a and 102b over the air interface 117.

When integrated access and backhaul connection are used, the same air interface may be used between the WTRUs and gNode-Bs, which may be the core network 109 via one or multiple gNBs. The gNode-Bs 180a and 180b may implement MIMO, MU-MIMO, or digital beamforming technology. Thus, the gNode-B 180a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. It should be appreciated that the RAN 105 may employ of other types of base stations such as an eNode-B. It will also be appreciated the RAN 105 may employ more than one type of base station. For example, the RAN may employ eNode-Bs and gNode-Bs.

[00125] The N3IWF 199 may include a non-3GPP Access Point 180c. It will be appreciated that the 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 the WTRUs 102c over the air interface 198. The non-3GPP Access Point 180c may use the 802.11 protocol to communicate with the WTRU 102c over the air interface 198.

[00126] Each of the gNode-Bs 180a and 180b may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink or downlink, and the like. As shown in FIG. 14D, the gNode-Bs 180a and 180b may communicate with one another over an Xn interface, for example. [00127] The core network 109 shown in FIG. 14D may be a 5G core network (5GC). The core network 109 may offer numerous communication services to customers who are interconnected by the radio access network. The core network 109 comprises a number of entities that perform the functionality of the core network. As used herein, the term “core network entity” or “network function” refers to any entity that performs one or more functionalities of a core network. It is understood that such core network entities may be logical entities that are implemented in the form of computer-executable instructions (software) stored in a memory of, and executing on a processor of, an apparatus configured for wireless or network communications or a computer system, such as system 90 illustrated in FIG. 14G.

[00128] In the example of FIG. 14D, the 5G Core Network 109 may include an access and mobility management function (AMF) 172, a Session Management Function (SMF) 174, User Plane Functions (UPFs) 176a and 176b, a User Data Management Function (UDM) 197, an Authentication Server Function (AUSF) 190, a Network Exposure Function (NEF) 196, a Policy Control Function (PCF) 184, aNon-3GPP Interworking Function (N3IWF) 199, a User Data Repository (UDR) 178. While each of the foregoing elements are depicted as part of the 5G core network 109, it will be appreciated that any one of these elements may be owned or operated by an entity other than the core network operator. It will also be appreciated that a 5G core network may not consist of all of these elements, may consist of additional elements, and may consist of multiple instances of each of these elements. FIG. 14D shows that network functions directly connect with one another, however, it should be appreciated that they may communicate via routing agents such as a diameter routing agent or message buses.

[00129] In the example of FIG. 14D, connectivity between network functions is achieved via a set of interfaces, or reference points. It will be appreciated that network functions could be modeled, described, or implemented as a set of services that are invoked, or called, by other network functions or services. Invocation of a Network Function service may be achieved via a direct connection between network functions, an exchange of messaging on a message bus, calling a software function, etc.

[00130] The AMF 172 may be connected to the RAN 105 via an N2 interface and may serve as a control node. For example, the AMF 172 may be responsible for registration management, connection management, reachability management, access authentication, access authorization. The AMF may be responsible forwarding user plane tunnel configuration information to the RAN 105 via the N2 interface. The AMF 172 may receive the user plane tunnel configuration information from the SMF via an N11 interface. The AMF 172 may generally route and forward NAS packets to/from the WTRUs 102a, 102b, and 102c via an N1 interface. The N1 interface is not shown in FIG. 14D.

[00131] The SMF 174 may be connected to the AMF 172 via an N11 interface. Similarly the SMF may be connected to the PCF 184 via an N7 interface, and to the UPFs 176a and 176b via an N4 interface. The SMF 174 may serve as a control node. For example, the SMF 174 may be responsible for Session Management, IP address allocation for the WTRUs 102a, 102b, and 102c, management and configuration of traffic steering rules in the UPF 176a and UPF 176b, and generation of downlink data notifications to the AMF 172.

[00132] The UPF 176a and UPF176b may provide the WTRUs 102a, 102b, and 102c with access to a Packet Data Network (PDN), such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and other devices. The UPF 176a and UPF 176b may also provide the WTRUs 102a, 102b, and 102c with access to other types of packet data networks. For example, Other Networks 112 may be Ethernet Networks or any type of network that exchanges packets of data. The UPF 176a and UPF 176b may receive traffic steering rules from the SMF 174 via the N4 interface. The UPF 176a and UPF 176b may provide access to a packet data network by connecting a packet data network with an N6 interface or by connecting to each other and to other UPFs via an N9 interface. In addition to providing access to packet data networks, the UPF 176 may be responsible packet routing and forwarding, policy rule enforcement, quality of service handling for user plane traffic, downlink packet buffering.

[00133] The AMF 172 may also be connected to the N3IWF 199, for example, via an N2 interface. The N3IWF facilitates a connection between the WTRU 102c and the 5G core network 170, for example, via radio interface technologies that are not defined by 3GPP. The AMF may interact with the N3IWF 199 in the same, or similar, manner that it interacts with the RAN 105.

[00134] The PCF 184 may be connected to the SMF 174 via an N7 interface, connected to the AMF 172 via an N15 interface, and to an Application Function (AF) 188 via an N5 interface. The N15 and N5 interfaces are not shown in FIG. 14D. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and SMF 174, allowing the control plane nodes to enforce these rules. The PCF 184, may send policies to the AMF 172 for the WTRUs 102a, 102b, and 102c so that the AMF may deliver the policies to the WTRUs 102a, 102b, and 102c via an N1 interface. Policies may then be enforced, or applied, at the WTRUs 102a, 102b, and 102c. [00135] The UDR 178 may act as a repository for authentication credentials and subscription information. The UDR may connect with network functions, so that network function can add to, read from, and modify the data that is in the repository. For example, the UDR 178 may connect with the PCF 184 via an N36 interface. Similarly, the UDR 178 may connect with the NEF 196 via an N37 interface, and the UDR 178 may connect with the UDM 197 via an N35 interface.

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

[00137] The AUSF 190 performs authentication related operations and connect with the UDM 178 via an N13 interface and to the AMF 172 via an N12 interface.

[00138] The NEF 196 exposes capabilities and services in the 5G core network 109 to Application Functions (AF) 188. Exposure may occur on the N33 API interface. The NEF may connect with an AF 188 via an N33 interface and it may connect with other network functions in order to expose the capabilities and services of the 5G core network 109.

[00139] Application Functions 188 may interact with network functions in the 5G Core Network 109. Interaction between the Application Functions 188 and network functions may be via a direct interface or may occur via the NEF 196. The Application Functions 188 may be considered part of the 5G Core Network 109 or may be external to the 5G Core Network 109 and deployed by enterprises that have a business relationship with the mobile network operator.

[00140] Network Slicing is a mechanism that could be used by mobile network operators 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 running across a single RAN. Network slicing enables the operator to create networks customized to provide optimized solutions for different market scenarios which demands diverse requirements, e.g. in the areas of functionality, performance and isolation.

[00141] 3GPP has designed the 5G core network to support Network Slicing. Network Slicing is a good tool that network operators can use to support the diverse set of 5G use cases (e.g., massive IoT, critical communications, V2X, and enhanced mobile broadband) which demand very diverse and sometimes extreme requirements. Without the use of network slicing techniques, it is likely that the network architecture would not be flexible and scalable enough to efficiently support a wider range of use cases need when each use case has its own specific set of performance, scalability, and availability requirements. Furthermore, introduction of new network services should be made more efficient.

[00142] Referring again to FIG. 14D, in a network slicing scenario, a WTRU 102a, 102b, or 102c may connect with an AMF 172, via an N1 interface. The AMF may be logically part of one or more slices. The AMF may coordinate the connection or communication of WTRU 102a, 102b, or 102c with one or more UPF 176a and 176b, SMF 174, and other network functions. Each of the UPFs 176a and 176b, SMF 174, and other network functions may be part of the same slice or different slices. When they are part of different slices, they may be isolated from each other in the sense that they may utilize different computing resources, security credentials, etc.

[00143] The core network 109 may facilitate communications with other networks. For example, the core network 109 may include, or may communicate with, an IP gateway, such as an IP Multimedia Subsystem (IMS) server, that serves as an interface between the 5G core network 109 and a PSTN 108. For example, the core network 109 may include, or communicate with a short message service (SMS) service center that facilities communication via the short message service. For example, the 5G core network 109 may facilitate the exchange of non-IP data packets between the WTRUs 102a, 102b, and 102c and servers or applications functions 188. In addition, the core network 170 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may include other wired or wireless networks that are owned or operated by other service providers.

[00144] The core network entities described herein and illustrated in FIG. 14A, FIG. 14C, FIG. 14D, or FIG. 14E are identified by the names given to those entities in certain existing 3GPP specifications, but it is understood that in the future those entities and functionalities may be identified by other names and certain entities or functions may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Thus, the particular network entities and functionalities described and illustrated in FIG. 14A, FIG. 14B, FIG. 14C, FIG. 14D, or FIG. 14E are provided by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether presently defined or defined in the future.

[00145] FIG. 14E illustrates an example communications system 111 in which the systems, methods, apparatuses that implement channel access for NR in 52.6-71 GHz, described herein, may be used. Communications system 111 may include Wireless Transmit/Receive Units (WTRUs) A, B, C, D, E, F, a base station gNB 121, a V2X server 124, and Road Side Units (RSUs) 123a and 123b. In practice, the concepts presented herein may be applied to any number of WTRUs, base station gNBs, V2X networks, or other network elements. One or several or all WTRUs A, B, C, D, E, and F may be out of range of the access network coverage 131. WTRUs A, B, and C form a V2X group, among which WTRU A is the group lead and WTRUs B and C are group members.

[00146] WTRUs A, B, C, D, E, and F may communicate with each other over a Uu interface 129 via the gNB 121 if they are within the access network coverage 131. In the example of FIG. 14E, WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F may communicate with each other directly via a Sidelink interface (e.g.,

PC5 or NR PC5) such as interface 125a, 125b, or 128, whether they are under the access network coverage 131 or out of the access network coverage 131. For instance, in the example of FIG. 14E, WRTU D, which is outside of the access network coverage 131, communicates with WTRU F, which is inside the coverage 131.

[00147] WTRUs A, B, C, D, E, and F may communicate with RSU 123a or 123b via a Vehicle-to-Network (V2N) 133 or Sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate to a V2X Server 124 via a Vehicle-to-Infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F may communicate to another UE via a Vehicle-to-Person (V2P) interface 128.

[00148] FIG. 14F is a block diagram of an example apparatus or device WTRU 102 that may be configured for wireless communications and operations in accordance with the systems, methods, and apparatuses that implement channel access for NR in 52.6-71 GHz, described herein, such as a WTRU 102 of FIG. 14A, FIG. 14B, FIG. 14C, FIG. 14D, or FIG.

14E. As shown in FIG. 14F, the example 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/indicators 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements. Also, the base stations 114a and 114b, or the nodes that base stations 114a and 114b may represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node-B gateway, a next generation node-B (gNode-B), and proxy nodes, among others, may include some or all of the elements depicted in FIG. 14F and may be an exemplary implementation that performs the disclosed systems and methods for described herein.

[00149] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 14F depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[00150] The transmit/receive element 122 of a UE may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a of FIG. 14A) over the air interface 115/116/117 or another UE over the air interface 115d/l 16d/l 17d. 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 an emitter/detector configured to transmit or receive IR, UV, or visible light signals, for example. The transmit/receive element 122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit or receive any combination of wireless or wired signals.

[00151] In addition, although the transmit/receive element 122 is depicted in FIG. 14F as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115/116/117.

[00152] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, for example NR and IEEE 802.11 or NR and E-UTRA, or to communicate with the same RAT via multiple beams to different RRHs, TRPs, RSUs, or nodes.

[00153] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, or the display/touchpad/indicators 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit. The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, or the display/touchpad/indicators 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 or the removable memory 132. The 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. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. The processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server that is hosted in the cloud or in an edge computing platform or in a home computer (not shown). The processor 118 may be configured to control lighting patterns, images, or colors on the display or indicators 128 in response to whether the setup of the examples described herein are successful or unsuccessful, or otherwise indicate a status of channel access for NR in 52.6-71 GHz and associated components. The control lighting patterns, images, or colors on the display or indicators 128 may be reflective of the status of any of the method flows or components in the FIG.’s illustrated or discussed herein (e.g., FIG. 1 -FIG. 12, etc). Disclosed herein are messages and procedures of channel access for NR in 52.6-71 GHz. The messages and procedures may be extended to provide interface/ API for users to request resources via an input source (e.g., speaker/microphone 124, keypad 126, or display/touchpad/indicators 128) and request, configure, or query channel access for NR in 52.6- 71 GHz related information, among other things that may be displayed on display 128.

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

[00155] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 115/116/117 from a base station (e.g., base stations 114a, 114b) or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method.

[00156] The processor 118 may further be coupled to other peripherals 138, which may include one or more software or hardware modules that provide additional features, functionality, or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[00157] The WTRU 102 may be included in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or an airplane. The WTRU 102 may connect with other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of the peripherals 138.

[00158] FIG. 14G is a block diagram of an exemplary computing system 90 in which one or more apparatuses of the communications networks illustrated in FIG. 14A, FIG. 14C,

FIG. 14D and FIG. 14E as well as channel access for NR in 52.6-71 GHz, such as the systems and methods illustrated in FIG. 1 through FIG. 12 described and claimed herein may be embodied, such as certain nodes or functional entities in the RAN 103/104/105, Core Network 106/107/109, PSTN 108, Internet 110, Other Networks 112, or Network Services 113.

Computing system 90 may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within a processor 91, to cause computing system 90 to do work. The processor 91 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 91 may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the computing system 90 to operate in a communications network. Coprocessor 81 is an optional processor, distinct from main processor 91, that may perform additional functions or assist processor 91. Processor 91 or coprocessor 81 may receive, generate, and process data related to the methods and apparatuses disclosed herein.

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

[00160] Memories coupled to system bus 80 include random access memory (RAM) 82 and read only memory (ROM) 93. Such memories include circuitry that allows information to be stored and retrieved. ROMs 93 generally include stored data that cannot easily be modified. Data stored in RAM 82 may be read or changed by processor 91 or other hardware devices. Access to RAM 82 or ROM 93 may be controlled by memory controller 92. Memory controller 92 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode may access only memory mapped by its own process virtual address space; it cannot access memory within another process’s virtual address space unless memory sharing between the processes has been set up.

[00161] In addition, computing system 90 may include peripherals controller 83 responsible for communicating instructions from processor 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.

[00162] Display 86, which is controlled by display controller 96, is used to display visual output generated by computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). Display 86 may be implemented with a CRT-based video display, an LCD- based flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller 96 includes electronic components required to generate a video signal that is sent to display 86. [00163] Further, computing system 90 may include communication circuitry, such as for example a wireless or wired network adapter 97, that may be used to connect computing system 90 to an external communications network or devices, such as the RAN 103/104/105, Core Network 106/107/109, PSTN 108, Internet 110, WTRUs 102, or Other Networks 112 of FIG. 14A, FIG. 14B, FIG. 14C, FIG. 14D, or FIG. 14E, to enable the computing system 90 to communicate with other nodes or functional entities of those networks. The communication circuitry, alone or in combination with the processor 91, may be used to perform the transmitting and receiving steps of certain apparatuses, nodes, or functional entities described herein.

[00164] It is 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 instructions, when executed by a processor, such as processors 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, executing on the processor of an apparatus or computing system configured for wireless or wired network communications. Computer readable storage media includes volatile and nonvolatile, removable and non-removable media implemented in any non- transitory (e.g., tangible or physical) method or technology for storage of 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 technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible or physical medium which may be used to store the desired information and which may be accessed by a computing system.

[00165] In describing preferred methods, systems, or apparatuses of the subject matter of the present disclosure - channel access for NR in 52.6-71 GHz - as illustrated in the Figures, specific terminology is employed for the sake of clarity. The claimed subject matter, however, is not intended to be limited to the specific terminology so selected.

[00166] The various techniques described herein may be implemented in connection with hardware, firmware, software or, where appropriate, combinations thereof. Such hardware, firmware, and software may reside in apparatuses located at various nodes of a communication network. The apparatuses may operate singly or in combination with each other to effectuate the methods described herein. As used herein, the terms “apparatus,” “network apparatus,” “node,” “device,” “network node,” or the like may be used interchangeably. In addition, the use of the word “or” is generally used inclusively unless otherwise provided herein.

[00167] This written description uses examples for the disclosed subject matter, including the best mode, and also to enable any person skilled in the art to practice the disclosed subject matter, including making and using any devices or systems and performing any incorporated methods. The disclosed subject matter may include other examples that occur to those skilled in the art (e.g., skipping steps, combining steps, or adding steps between exemplary methods disclosed herein).

[00168] Methods, systems, and apparatuses, among other things, as described herein may provide for channel access for NR in 52.6-71 GHz. A method, system, computer readable storage medium, or apparatus may provide for based on multiple BWP(s) adaption, multiple BWP may be activated at a same time via DCI format 0 1. In another example, modifying bitmap for the SearchSpace IE freqMonitorLocations based on MAC-CE or DCI. All combinations in this paragraph or the following paragraph (including the removal or addition of steps) are contemplated in a manner that is consistent with the other portions of the detailed description.

[00169] Methods, systems, and apparatuses, among other things, as described herein for channel access may provide for receiving first information about the apparatus, the first information may include a capability of the user equipment to perform carrier aggregation for an uplink transmission or carrier aggregation for a downlink transmission; and sending a configuration to the user equipment, the configuration comprising the component carrier information to enable carrier aggregation based on the first information. The capability may include a maximum aggregated number of component carriers (CCs) or maximum bandwidth configuration. The method, system, computer readable storage medium, or apparatus may provide for determining the user equipment is in connected mode; and configuring one or more secondary cells (SCells), which may be based on the first information. The method, system, computer readable storage medium, or apparatus may provide for activating or deactivating the one or more secondary cells (SCells) based on variations of a load pattern or channel availability associated with the user equipment. The activating or deactivating the one or more secondary cells (SCells) based on an indication from a medium access control control element (MAC CE) or downlink control indicator (DCI). The numerology for a carrier may be different for cyclic prefix (CP), SCS, or slots. A base station, a core network device, or user equipment may execute the steps herein. All combinations in this paragraph and the previous paragraph (including the removal or addition of steps) are contemplated in a manner that is consistent with the other portions of the detailed description.