Channelization and BWP

By using composite carrier indicators and bandwidth adaptive technology, the problems of insufficient spectrum utilization and unfair channel access caused by carrier aggregation in unlicensed spectrum are solved, achieving more efficient spectrum utilization and channel management.

CN118890700APending Publication Date: 2024-11-01INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410927906.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2018-05-10
Filing Date
2019-03-28
Publication Date
2024-11-01

AI Technical Summary

Technical Problem

When operating in unlicensed spectrum, existing technologies suffer from insufficient spectrum utilization due to carrier aggregation, and channel access mechanisms such as LBT and VCS suffer from interference unfairness and low spectrum efficiency.

Method used

By employing composite carrier indicator (CCI) and bandwidth adaptive (BA) technology, the carrier bandwidth is dynamically adjusted through the synthesis of anchor carrier and auxiliary carrier, enabling flexible carrier band combination and channel sensing, and optimizing spectrum utilization.

Benefits of technology

It improves spectrum utilization efficiency, ensures coexistence with existing technologies, reduces interference, and achieves more efficient channel access and resource management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118890700A_ABST
    Figure CN118890700A_ABST
Patent Text Reader

Abstract

The invention relates to channelization and BWP. Methods, systems, and apparatus designed to support flexible carrier bandwidth in new radios. Multiple carrier bands may be combined into a single composite carrier according to channel availability in the carrier bands. A composite carrier indicator (CCI) indicates to a network device an available carrier band within a channel occupancy time. Further, when channel access is unavailable, bandwidth portion inactivity times are suspended.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the patent application with international application number PCT / US2019 / 024620 and national application number 201980031519.7, entitled “Channelization and BWP”, filed on March 28, 2019.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 669,728, filed on May 10, 2018, entitled “Channelization and BWP,” and U.S. Provisional Patent Application No. 62 / 687,598, filed on June 20, 2018, entitled “Channelization and BWP,” the contents of both of which are incorporated herein by reference. Background Art

[0004] Carrier aggregation with at least one SCell operating in unlicensed spectrum is called Licensed Assisted Access (LAA). Therefore, in LAA, the set of serving cells configured for a UE always includes at least one SCell operating in unlicensed spectrum according to frame structure type 3, also called LAA SCell. Unless otherwise specified, the LAA SCell acts as a regular SCell.

[0005] The LAA eNB and UE apply Listen Before Talk (LBT) before performing transmissions on the LAA SCell. LBT is a process by which a radio transmitter first senses the medium and then transmits only when the medium is sensed to be idle. When LBT is applied, the transmitter listens / senses the channel to determine whether the channel is idle or busy. If the channel is determined to be idle, then the transmitter may perform a transmission; otherwise, it does not perform a transmission. If the LAA eNB uses channel access signaling of other technologies for LAA channel access, then it should continue to meet the LAA maximum energy detection threshold requirement.

[0006] There are various LBT methods, but the one recommended by 3GPP is called Equipment Category 4 based on LBT load. This adds a random access protocol similar to WiFi, which not only ensures LTE / WiFi coexistence, but is a standardized way to ensure LTE / LTE coexistence. In Release 14, several channel access procedures were introduced that are performed by the eNB and UE for both downlink (DL) and uplink (UL) transmissions, respectively. The main channel access procedures are described in Section 15 of TS 36.21335n (Release 15), V15.0.0.

[0007] LTE frame structure type 3 is only applicable for LAA auxiliary cell operation with normal cyclic prefix. Each radio frame is T f =307200·T s = 10ms long and consists of 20 segments of length T slot =15360·T s =0.5 ms slots, which are numbered from 0 to 19. A subframe is defined as two consecutive slots, where subframe i consists of slots i and 2i+1. The 10 subframes within a radio frame can be used for downlink or uplink transmissions. Downlink transmissions occupy one or more consecutive subframes, starting anywhere within a subframe and ending with the last subframe either fully occupied or following one of the DwPTS durations specified in Table 4.2-1 of TS 36.21335n (Release 15), V15.0.0. Uplink transmissions occupy one or more consecutive subframes.

[0008] 3GPP TR 38.913 defines the solutions and requirements for next generation access technologies. Table 1 summarizes the key performance indicators (KPIs) for eMBB, URLLC, and mMTC devices.

[0009] Table 1: KPIs for eMBB, URLLC, and mMTC devices

[0010]

[0011]

[0012]

[0013] In order to coordinate inter-technology spectrum access in a distributed and simple manner, the transmitter must first detect the energy across the intended transmission band. This energy detection (ED) mechanism informs the transmitter of ongoing transmissions by other nodes and helps it decide whether to transmit. However, although simple, this scheme, also known as listen before talk (LBT), does not work in all situations, for example, when the information is encoded to be received below the background noise level, or when the nodes are far away and the signal at the receiver is weak. Therefore, a node wishing to transmit can sense the channel as unoccupied based on the received energy being below a certain ED threshold, but still interfere with nearby nodes that are receiving.

[0014] Nevertheless, LBT is the starting point for coexistence and is mandatory in unlicensed band regulations in many countries. The ED threshold cannot be lowered too much because false detections will occur due to noise. Therefore, additional information is needed for efficient inter-technology and intra-technology wireless medium access.

[0015] The 802.11 medium access control (MAC) protocol augments the ED mechanism with a virtual carrier sensing (VCS) mechanism, so that the 802.11 packet header is received and decoded at the lowest power level due to the use of the most robust modulation and decoding. The network allocation vector (NAV), i.e., a timeline at each station (STA) when the channel is idle or occupied, which indicates how long the channel will be used, is updated based on the content of such headers or control packets. For example, the request to send / clear to send (RTS / CTS) mechanism reserves the channel by having the NAV updated by all nodes that receive RTS around the transmitter and CTS around the receiver. However, even VCS has problems due to the capture effect (which causes stronger overlapping packets to be captured before weaker packets), resulting in unfairness because stronger nodes do not experience collisions and weaker nodes will back off.

[0016] Virtual carrier sensing is a logical abstraction that limits the need for physical carrier sensing at the air interface in order to save power. The MAC layer frame header includes a duration field that specifies the transmission time required for the frame, during which the medium will be busy. A station listening to the wireless medium reads the Duration field and sets its NAV, which is an indicator of how long the station must defer accessing the medium. The NAV can be thought of as a counter that counts down to zero at a uniform rate. When the counter is zero, the virtual CS indicates that the medium is idle; when non-zero, the indication is busy.

[0017] There are two types of LTE access on unlicensed frequencies: LAA, which acts as a supplemental downlink to the licensed LTE carrier (note: the unlicensed uplink eLAA is still attached to the licensed carrier), and MulteFire, which features fully independent operation in the unlicensed band. See MulteFire version 1.0.1. https: / / www.multefire.org / specification. In LAA, both the licensed and unlicensed bands operate simultaneously, i.e., data can be received on both bands at the same time. PBCH is carried only on licensed carriers. However, the Rel-12 Discovery Reference Signal (DRS), including the PSS, is transmitted at 40ms intervals on the unlicensed carrier. Detecting the DRS alone does not provide further information, i.e., cell id, or even determine the operator. MulteFire transmissions do include PBCH / PDSCH in their downlink transmissions, now called ePBCH, which doubles the energy in the PSS and Secondary Synchronization Signal (SSS) sequences to improve detectability.

[0018] With bandwidth adaptation (BA), the UE's receive and transmit bandwidth does not have to be as large as the cell's bandwidth and can be adjusted: the width can be commanded to change (e.g., shrink during low activity periods to save power); the location can be moved in the frequency domain (e.g., to increase scheduling flexibility); and the subcarrier spacing can be commanded to change (e.g., to allow different services). A subset of the total cell bandwidth of a cell is called a bandwidth part (BWP), and BA is implemented by configuring the UE with (one or more) BWPs and telling the UE which of the configured BWPs is currently the active BWP.

[0019] Figure 1 The case of configuring 3 different BWPs is described: 1) BWP1 has a width of 40 MHz and a subcarrier spacing of 15 kHz; 2) BWP2 has a width of 10 MHz and a subcarrier spacing of 15 kHz; and 3) BWP3 has a width of 20 MHz and a subcarrier spacing of 60 kHz.

[0020] A serving cell can be configured with up to four BWPs, and for an activated serving cell, there is always one active BWP at any point in time. BWP switching for a serving cell is used to activate an inactive BWP and deactivate an active BWP at a time, and is controlled by the Physical Downlink Control Channel (PDCCH) indicating a downlink assignment or uplink grant. When adding a SpCell (special cell) or activating an SCell, one BWP is initially active without receiving a PDCCH indicating a downlink assignment or uplink grant. The active BWP for a serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common to both UL and DL. Summary of the invention

[0021] Disclosed herein are methods, systems, and devices that can address one or more of the NR issues disclosed above. Methods, systems, and devices can support flexible carrier bandwidth in new radio. Multiple carrier bands can be combined into a single composite carrier based on channel availability in the carrier bands. A composite carrier indicator (CCI) indicates to network devices the available carrier bands within a channel occupancy time (COT). In addition, BWP management is disclosed herein.

[0022] This summary is provided to introduce some concepts in a simplified form, which are further described in the detailed description below. This summary is neither 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 limited to limitations that address any or all disadvantages noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 1 is an exemplary illustration of bandwidth adaptation;

[0025] Figure 2A is an exemplary illustration of channelization of unlicensed spectrum - an example of LTE channelization;

[0026] Figure 2B is an exemplary illustration of channelization of unlicensed spectrum - proposed channelization for NR-U with minimum guard band between cells;

[0027] Figure 3A is an exemplary illustration of the minimum CBW for NR-U - 20 MHz;

[0028] Figure 3B is an exemplary illustration of the minimum CBW for NR-U - 5 MHz at the center of a 20 MHz carrier;

[0029] Figure 4A is an exemplary illustration of a composite cell - an illustration of anchor and subsidiary carriers;

[0030] Figure 4B is an exemplary illustration of a composite cell - dynamically changing CBW for a composite cell (with anchor points);

[0031] Figure 5A is an exemplary illustration of a synthetic continuous spectrum;

[0032] Figure 5B is an exemplary illustration of a synthetic non-continuous spectrum;

[0033] Figure 6 It is the signaling information in the anchor cell, such as SS / PBCH, RACH, etc.

[0034] Fig. 7A is an exemplary illustration that the composite CBW is fixed for the duration of the anchor's MCOT;

[0035] Figure 7B is an exemplary illustration of the variation of the composite CBW during the MCOT of the anchor;

[0036] Fig. 8A is an exemplary illustration of CCA / LBT for different composite methods - when all composite carriers have successful CCA / LBT, access the channel; WBLT may be used;

[0037] Figure 8Bis an exemplary illustration of CCA / LBT for different synthesis methods - accessing the channel with WLBT, but subordinates can be released before the anchor carrier;

[0038] Figure 8C is an exemplary illustration of CCA / LBT for different synthesis methods - adding attachments as they become available;

[0039] Fig.8D is an exemplary illustration of CCA / LBT for different synthesis methods - a satellite with channel access rights is added to the anchor; the satellite may lose the channel access rights because its MCOT may terminate faster than the MCOT of the anchor carrier;

[0040] Fig. 9 is an exemplary illustration of the process used for compositing. Composite channels are acquired and released together;

[0041] Fig.10 is an exemplary illustration of the process used for synthesis. The composite channel is acquired all at once, but the attachment is released earlier than the anchor;

[0042] Fig.11 is an exemplary illustration of a process for synthesis. Accessories are synthesized as they become available;

[0043] Fig.12 is an exemplary illustration of the process used to synthesize. A subsidiary is released when its MCOT expires;

[0044] Fig.13 is an exemplary illustration of CCI signaled in an anchor cell;

[0045] Fig.14 is an exemplary diagram of the UE synthesizing the anchor with subordinate2 and subordinate3;

[0046] Fig.15 is an exemplary illustration of a gNB performing CAT 4 LBT with random backoff and accessing a channel for a composite channel;

[0047] Fig.16A is an exemplary illustration of LBT for a composite anchor and attachment - obtaining high priority access to the attachment after LBT for the anchor succeeds;

[0048] Fig. 16B is an exemplary illustration of the LBT for synthesizing anchors and affiliates - using the same random backoff for the anchor and all affiliates;

[0049] Fig. 16Cis an exemplary illustration of LBT for composite anchor and attachment - LBT for each carrier uses different random backoff, but channel access is aligned with maximum backoff;

[0050] Fig.17 is an exemplary illustration of a carrier serving as an anchor for one cell and as a subsidiary for another cell;

[0051] Fig.18A is an exemplary illustration of the UE behavior when Cell1 and Cell2 are received (t1, t2, t3 represent time instances of the process) - the CCI from Cell1 deactivates Cell2 from the UE's perspective;

[0052] Fig.18B is an exemplary illustration of UE behavior when receiving Cell1 and Cell2 - Cell1 transmission in subordinate2 is rate matched around some Cell2 resources;

[0053] Fig.19A is an exemplary illustration of a process in which the UE synthesizes subordinate2 into Cell1 and stops monitoring cell2 upon receiving CCI;

[0054] Fig.19B is an exemplary illustration of a process in which the UE synthesizes subordinate2 into Cell1 and performs rate matching around resources of Cell2 upon receiving CCI;

[0055] Fig. 20A is an exemplary illustration of BWPs for a composite cell - initial, default, anchor active BWP;

[0056] Fig. 20B is an exemplary illustration of a BWP for a composite cell - an example of an Active-Other-BWP;

[0057] Fig.21A is an exemplary illustration of UE behavior in Active-Other-BWP - the UE monitors the grant in the default BWP, switches to the active-other BWP for PDSCH transmission, returns to the default BWP when the grant is completed;

[0058] Fig.21B is an exemplary illustration of UE behavior in Active-Other-BWP - UE monitors grant in active-anchorBWP, switches to active-other BWP for PDSCH transmission, returns to default BWP when grant completes;

[0059] Fig. 21Cis an exemplary illustration of UE behavior in Active-Other-BWP - the UE monitors the grant in the default active-anchor BWP, switches to the active-other BWP for PDSCH transmission, and returns to the active-anchor BWP when the grant is completed;

[0060] Fig.21D is an exemplary illustration of UE behavior in Active-Other-BWP - the UE monitors the control signals in active-otherBWP;

[0061] Fig.22A is an exemplary illustration of a UL grant to a UE;

[0062] Fig. 22B is an exemplary illustration of sensing on granted UL resources;

[0063] Fig. 22C is an exemplary illustration of sensing in a frequency band between the maximum and minimum PRBs in a grant;

[0064] Fig.22D is an exemplary illustration of sensing across the BWP;

[0065] Fig.23A illustrates an exemplary BWP operation during channel access unavailability in NR, wherein BWPInactivityTimer decreases when COT is unavailable;

[0066] Fig. 23B illustrates an exemplary BWP operation during channel access unavailability in NR, wherein the BWP is deactivated due to expiration of a BWPInactivityTimer;

[0067] Fig.24A illustrates an exemplary periodic CCI transmission in an active BWP, which indicates that a node has channel access (valid BWP), where the periodicity has the same frequency resource;

[0068] Fig. 24B illustrates an exemplary periodic CCI transmission in an active BWP, which indicates that a node has channel access (valid BWP), where different frequency resources are used periodically;

[0069] Fig.25 illustrates an exemplary operation of using ValidBWPWindowTimer to identify valid BWP and invalid BWP states;

[0070] Fig.26illustrates an exemplary process for entering and exiting valid BWP and invalid BWP states using validBWPWindowTimer;

[0071] Fig.27A illustrates an example for transitioning to a valid BWP using an invalidBWPTimer before the invalidBWPTimer expires;

[0072] Fig.27B illustrates an example of using invalidBWPTimer to deactivate an active BWP after an extended period of invalid BWP (expiration of invalidBWPTimer);

[0073] Fig.28 illustrates an exemplary process for deactivating an active BWP when a UE experiences an extended invalid BWP state;

[0074] Fig.29 An example for freezing BWPInactivityTimer based on expiration of cotExpiryTimer is illustrated;

[0075] Fig.30 illustrates an exemplary process for identifying an invalid BWP using a cotExpiryTimer and suspending a BWPInactivityTimer;

[0076] Fig.31 An example for freezing BWPInactivityTimer during channel access of a UE is illustrated;

[0077] Fig.32 illustrates an example in which the UE restarts the BWPInactivityTimer after a successful LBT;

[0078] Fig.33A An example of where the BWP in each ChAxOp is changed is shown: BWP2 is activated via CCI on the default BWP;

[0079] Fig.33B Examples of BWP changes in each ChAxOp are shown: BWP2 is activated by BWP1;

[0080] Fig.34 An illustrative example of switching from BWP1 to the default BWP and activating BWP2 through the CCI upon COT expiration is illustrated;

[0081] Fig.35 illustrates an exemplary periodic transmission of CCI over multiple candidate BWPs of a UE;

[0082] Fig.36 An exemplary process of obtaining CCI by searching multiple BWP candidates is illustrated;

[0083] Fig.37A An exemplary BWP deactivation due to expiration of cotExpiryTimer is illustrated: the gNB indicates the COT to the UE;

[0084] Fig.37B An exemplary BWP deactivation due to expiration of cotExpiryTimer is illustrated: UE knows its COT;

[0085] Fig.38 An example is shown in which the gNB indicates the COT to the UE using CCI;

[0086] Fig.39 illustrates an exemplary process of deactivating a BWP when cotExpiryTimer expires;

[0087] Fig.40A Illustrated are example operations in which the BWPActivityTimer value is updated based on cotExpiry: when the gNB gains channel access and indicates COT;

[0088] Fig.40B Illustrated are exemplary operations in which the BWPActivityTimer value is updated based on cotExpiry: when the UE has channel access and knows its COT;

[0089] Fig.41 An exemplary process of updating BWPInactivityTimer with a cotExpiryAdj value is illustrated;

[0090] Fig.42 illustrates an exemplary display (e.g., a graphical user interface) that may be generated based on methods and systems for mobility signaling load reduction;

[0091] Fig.43A An exemplary communication system is illustrated;

[0092] Fig.43B An exemplary system including a RAN and a core network is illustrated;

[0093] Fig.43C An exemplary system including a RAN and a core network is illustrated;

[0094] Fig.43D An exemplary system including a RAN and a core network is illustrated;

[0095] Fig.43E Another example communication system is illustrated;

[0096] Fig.43F is a block diagram of an example apparatus or device, such as a WTRU;

[0097] Figure 43G is a block diagram of an exemplary computing system;

[0098] Fig.44A illustrates an example where a UE performs CAT4 LBT for PUSCH transmissions - the UE performs LBT on a U-SCBW spanning its UL grant;

[0099] Fig.44B illustrates an example where a UE performs CAT4 LBT for PUSCH transmissions - the UE performs LBT on U-SCBWs spanning its active BWP;

[0100] Fig.45A illustrates an example where the UE performs CAT2 LBT in the COT acquired by the gNB when its BWP is less than or equal to the bandwidth of the COT acquired by the gNB - the UE performs LBT on the U-SCBW corresponding to the COT acquired by the gNB;

[0101] Fig.45B illustrates an example where the UE performs CAT2 LBT in the COT acquired by the gNB when its BWP is less than or equal to the bandwidth of the COT acquired by the gNB - the UE performs LBT on the U-SCBW that spans its active BWP;

[0102] Fig.45C illustrates an example where the UE performs CAT2 LBT in the COT acquired by the gNB when its BWP is less than or equal to the bandwidth of the COT acquired by the gNB - the UE performs LBT on the U-SCBW that spans its UL grant;

[0103] Fig.46A illustrates an example where the UE performs CAT2 LBT in the COT acquired by the gNB when its BWP is larger than the bandwidth of the COT acquired by the gNB - the UE performs LBT on the U-SCBW that spans its active BWP;

[0104] Fig.46B illustrates an example in which the UE performs CAT2 LBT in the COT acquired by the gNB when its BWP is greater than the bandwidth of the COT acquired by the gNB - the UE performs LBT on the U-SCBW corresponding to the COT acquired by the gNB;

[0105] Fig.46C illustrates an example where the UE performs CAT2 LBT in the COT acquired by the gNB when its BWP is larger than the bandwidth of the COT acquired by the gNB - the UE performs LBT on the U-SCBW that spans its UL grant;

[0106] Fig.47 An example of puncturing of PUSCH by a UE in a shared COT when its granted resources exceed the bandwidth of the gNB’s COT is shown;

[0107] Fig.48A illustrates an example UE LBT procedure when consecutive PUSCH resources are different in frequency - joint LBT across PUSCH resources;

[0108] Fig.48B illustrates an example UE LBT procedure when the frequencies of successive PUSCH resources are different - separate LBT for each PUSCH if the frequency resource in the frequency band was not included in the previous PUSCH;

[0109] Fig.48C illustrates an example UE LBT procedure when the frequencies of consecutive PUSCH resources are different - LBT across the frequency band for PUSCH2, no LBT before PUSCH3;

[0110] Fig.48D illustrates an example UE LBT procedure when the frequencies of consecutive PUSCH resources are different - CAT4 LBT before PUSCH2 due to large gap between DL and UL;

[0111] Fig.49A An example of CCI monitoring with respect to a DRX cycle is illustrated - CCI is received before the DRX OnDuration;

[0112] Fig.49B An example of CCI monitoring with respect to a DRX cycle is illustrated - CCI is received during OnDuration;

[0113] Fig.50A An example of SSB / DRS transmission following CAT2 LBT is shown. Following wideband LBT, SSB / DRS is transmitted on multiple raster points across multiple U-SCBWs;

[0114] Fig.50B An example of SSB / DRS transmission following CAT2 LBT is illustrated - SSB / DRS transmission at predetermined raster points following broadband LBT;

[0115] Fig.50C illustrates an example of SSB / DRS transmission following CAT2 LBT - SSB / DRS repetition required for OCB within U-SCBW;

[0116] Fig.50DAn example of SSB / DRS transmission following CAT2 LBT is illustrated - staggered transmission opportunities of SSB / DRS across different U-SCBWs;

[0117] Fig.51 An exemplary method flow for channelizing a BWP as disclosed herein is illustrated;

[0118] Fig.52A An exemplary UE LBT is illustrated when the UE shares the COT acquired by the gNB. The UE performs CAT2 LBT-signaling between gNB and UE in certain frequency bands that may correspond to the UE's BWP or the UE's authorized resources or the gNB's composite carrier BW;

[0119] Fig.52B An exemplary UE LBT is illustrated when the UE shares the COT acquired by the gNB. The UE performs CAT2 LBT-UE procedures in certain frequency bands that may correspond to the UE's BWP or the UE's authorized resources or the composite carrier BW of the gNB;

[0120] Fig.53A illustrates an exemplary UE procedure for detecting frequency bands in a composite carrier - detection by a two-step process;

[0121] Fig.53B illustrates an exemplary UE process for detecting frequency bands in a composite carrier - detection performed in a single step;

[0122] Fig.53C illustrates an exemplary UE process for detecting frequency bands in a composite carrier - detecting CCI in each frequency band; and

[0123] Fig.54 An example process for UE reporting of measurements is illustrated. The UE identifies one or more frequency bands in the COT of the gNB and performs measurements with CSI-RS in those frequency bands. It may report the measurements and the frequency bands used in the measurements. DETAILED DESCRIPTION

[0124] New Radio (NR) can be designed to support flexible carrier bandwidths (CBW). When channelizing the unlicensed spectrum for NR-U (creating NR-U carriers), there are limitations due to regulatory requirements for unlicensed spectrum and existing technologies. For example, the ETSI harmonized standard for 5GHz requires the use of 20MHz channels, but also allows operation in smaller bands (as small as 5MHz) centered around the center of the 20MHz band. See ETSI EN 301.893, 5GHz RAN; harmonized standard covering the essential requirements of Directive 2014 / 53 / EU V2.1.1, 2017-05, section 3.2. NR-U channelization should ensure that WiFi nodes in the unlicensed band do not need to change their existing sensing processes.

[0125] The following methods and systems disclosed herein may address one or more of the NR issues disclosed above: 1) a method of channelizing NR-U spectrum into a cell; 2) a method of forming a composite cell using an anchor carrier; 3) introducing a composite carrier indicator (CCI) to indicate the configuration of carriers in a composite cell; 4) an LBT process for creating a composite carrier; 5) BWP configuration and process in a composite cell; 6) UE channel sensing for BWP operation; 7) synthesizing carriers without an anchor carrier; or 8) BWP management based on channel availability.

[0126] In carrier aggregation in LTE-A, unlicensed spectrum is supported in a maximum carrier bandwidth (CBW) of 20 MHz. Each 20 MHz NR-U spectrum is an SCell. Providing guard bands between adjacent carriers (e.g., bands) loses some spectrum. Therefore, even if the SCells are contiguous, they cannot take full advantage of larger bandwidth blocks and utilize guard bands. NR-U operation should take full advantage of the flexibility of NR CBW operation and provide better spectrum utilization while ensuring coexistence with existing technologies.

[0127] The following is a discussion of channelization in NR-U. In carrier aggregation in LTE-A, up to 20 MHz of spectrum can be allocated to SCells, such as Figure 2A As shown in , some of the spectrum is lost in the guard band between adjacent carriers. On the other hand, NR has the flexibility to operate over a wide spectrum. In order to fully utilize the flexibility in NR-U disclosed in this article, unlicensed NR-U cells should support operation in the maximum available carrier bandwidth to avoid spectrum loss in the guard band. Figure 2B An example is shown in , where SCell1 uses a 60MHz CBW; therefore, the spectrum used for the guard band within this cell is now used for in-band transmissions. Note that this is just an example, and another example may use a single cell with an 80mHz CBW.

[0128] The unlicensed minimum carrier bandwidth (U-SCBW Hz) is defined as the minimum carrier bandwidth (CBW) used for a channel or cell in NR-U. An NR-U cell can create a composite carrier of one or more U-SCBWs, resulting in Figure 2B We refer to the creation of a channel composed of multiple U-SCBWs as "carrier synthesis" and the resulting carrier as the "composite carrier".

[0129] To be compatible with the ETSI unified standard for 5 GHz, NR-U can support the following: 1) U-SCBW = 20 MHz, so the channelization is similar to WiFi, such as Figure 3A As seen in , multiple 20MHz carriers can be combined into one cell; and 2) if the carrier is located in the center of a 20MHz channel, a smaller U-SCBW (>=5MHz) can be supported, such as Figure 3B The smaller U-SCBW cannot be synthesized because they are located in the center of the 20MHz carrier and have no adjacent U-SCBW.

[0130] Disclosed below is carrier synthesis in NR-U. A NR-U cell can be defined by a U-SCBW carrier which can be referred to as the NR-U "anchor carrier". This NR-U cell can be an SCell in CA or a PCell in SA. When other U-SCBW carriers are synthesized with the anchor carrier, a composite carrier is obtained; a candidate U-SCBW that can be synthesized with the first carrier (e.g., anchor carrier) is called an "ancillary carrier". This concept is described in Figure 4A The NR-U cell has one anchor and three satellites. Figure 4B Some ways in which a composite carrier may be obtained are shown - a cell may consist of just the anchor, or a cell may include the anchor composited with direct neighbors and even those neighbors beyond the direct neighbors (example: subordinate3 is composited with anchor and subordinate2). The composite may be dynamic and change over time. It is contemplated herein that channel access for a common beam (spatial direction) may be used for anchor and subsidiary carriers, or that channel access to each carrier may correspond to different beams in different spatial directions. For simplicity, this embodiment may use the same beam on the composite carrier. The following subsidiaries may be composited with the anchor cell: 1) neighboring subsidiaries that are direct neighbors of the anchor; 2) subsidiaries that are adjacent to direct neighbors; or 3) other subsidiaries in the spectrum.

[0131] An NR-U composite cell may use the following process when synthesizing an attachment. The channel should at least be available to the anchor, e.g., CCA / LBT should be successful for the anchor of the cell to perform synthesis or access the channel. In the event that the attachment is not present or unavailable, the cell functions only with the anchor carrier. CCA may be performed as a single interval LBT or short duration sensing (such as sensing for DRS in eLAA). If CCA / LBT on that carrier is successful, then the direct neighbors may be synthesized. If CCA / LBT is successful for an attachment adjacent to the synthesized neighbor, then it may be synthesized. Synthesis may be performed in one of the following ways: allowing bandwidth gaps or not allowing bandwidth gaps. Synthesis may not be allowed in synthesis Figure 5A For example, the composite carrier should include a continuous set of frequency resources. Therefore, subordinate3 cannot be synthesized with anchor. Bandwidth gaps or discontinuous spectrum can be allowed in the synthesis. Figure 5B In this case, however, a guard band is required at the edge of the anchor and subordinate3.

[0132] An NR-U composite cell may additionally use the following process when synthesizing an auxiliary. Up to N auxiliary carriers may be synthesized with the anchor carrier. If a cell has two auxiliary carriers available for synthesis with the anchor carrier, but only requires one, then it can select the auxiliary carrier closest to the anchor because those carriers are more closely synchronized with the anchor cell. A node may synthesize only when a minimum of S U-SCBW carriers are available. For example, in the case of a 5 MHz of 20 MHz U-SCBW, synthesis may only occur if channel access is available for a 40 MHz block of spectrum in addition to the anchor cell. This ensures that the synthesized spectrum provides higher spectral efficiency than the spectrum loss caused by the added overhead due to synthesis; overhead may come from having to signal the configuration of the synthesized carriers.

[0133] When the carriers are combined, if the nodes perform omni-directional transmission channel sensing on all carriers, they should obtain channel access in all spatial directions. Nodes can also obtain channel access for different spatial directions on each combined carrier.

[0134] Disclosed below is the signaling in the anchor carrier. For NR-U cells, an anchor carrier should exist to have channel access. If present (in SA / DC), key information such as DRS or SS / PBCH, RMSI CORESET, SI, paging and RACH resources can be provided in the anchor cell. At least the cell-defined SSB can be present in the anchor carrier for SA and DC. Even if the composite CBW changes, the anchor is available at least during channel access, so that the UE performs RACH (for SA / DC or RRC in BFR, etc.) or performs synchronization and receives paging (for example, in SA / DC) on resources within the anchor carrier. These resources may be different from potential guard band resources in the anchor carrier, which may or may not be available depending on the affiliated channel availability. Figure 6 The concept of having these PHY signals within the bandwidth of the anchor carrier is shown.The secondary carrier may also include other cell-defined SSBs and non-cell-defined SSBs for measurements.

[0135] Disclosed below is signaling information about a composite carrier in an NR-U cell. Since the channel availability on a carrier can be dynamic, the availability of the attached cells can change dynamically, and therefore the bandwidth of the composite carrier can change dynamically. The composite carrier can be formed both by the gNB in ​​the DL and by the UE in the UL. The node that synthesizes the carrier should indicate the configuration of the composite carrier so that the receiver recognizes how the carrier bandwidth affects its resources. On the DL, the UE's BWP can change due to changes in the CBW. Guard bands PRBs can become available for transmission.

[0136] A composite carrier may be formed in one of the following ways. An attachment is selected at channel access of the anchor. All synthesized carriers have the same MCOT. Additionally, attachments may be released in one of the following ways: simultaneously or sequentially. In one instance, the composite channel may be released as a whole, for example, all carriers may be released simultaneously. To change the composite carrier, the node performs CCA / LBT again to access the channel. CCA may be short duration sensing, such as 25μs sensing for DRS in eLAA. The composite carrier may remain unchanged until the maximum channel occupancy time (MCOT) of the anchor. Fig. 7A An example is shown where subordinate2 and subordinate3 are synthesized with the anchor for the entire MCOT. Fig. 8A An example case of performing LBT with random backoff is shown. Channel access may be obtained for anchor and subordinate2 and subordinate3 combined together. Wideband LBT (WLBT) may be performed to obtain channel access for a carrier (anchor or subordinate). Wideband may mean a configuration where the channel exceeds 20 MHz, possibly across multiple 20 MHz bands. Fig. 9 An example process for compositing is shown. Attachments can be released earlier than anchors. Once a compositing node is finished using an attachment, it is released so that other users can use it. This ensures fair coexistence. Figure 8B This situation is shown. Fig.10 An example process for synthesis is shown. The composite carrier can be changed dynamically during the channel access of the anchor carrier. Therefore, the composite carrier can be changed during the MCOT, but at least the anchor carrier must be available for the duration of the MCOT. Figure 7B An example is shown where the availability of subordinate2 and subordinate3 varies by the MCOT of the anchor. The available bandwidth is different at different time instances.

[0137] refer to Fig. 9 , at step 211, an anchor or multiple satellites are selected as candidates to be synthesized. At step 212, CAT4 WLBT is performed on the anchor and multiple satellites with a random window. When WLBT is successful at step 213, the composite channel can then be accessed (step 214), and then the composite channel is released within the MCOT of the anchor carrier. When WLBT is unsuccessful at step 213, the carrier is not synthesized in the cell (at step 216). Further at step 217, the candidate set of carriers to be synthesized can be changed, or at step 218, the contention window size for LBT can be changed. WLBT is then checked again at step 213.

[0138] refer to Fig.10 , at step 221, an anchor or multiple satellites are selected as candidates to be synthesized. At step 222, CAT4 WLBT is performed on the anchor or multiple satellites with a random window. When WLBT is successful at step 223, the composite channel can then be accessed (step 224). Then at step 225, the satellite carriers can be released before releasing the anchor carrier (so that other users can access these carriers). Alternatively, at step 225, the satellites can be released before their corresponding MCOT ends. At step 226, the anchor or remaining satellites can be released within the anchor carrier MCOT. When WLBT is unsuccessful at step 223, the carrier is not synthesized in the cell (at step 227). Further at step 228, the candidate set of carriers to be synthesized can be changed, or at step 229, the contention window size for LBT can be changed. Then at step 223, WLBT is checked again.

[0139] Additional design considerations may be applied to synthesize attachments, such as the following, such as not dropping during MCOT and dropping during MCOT. In an example, attachments can only be added and they cannot be dropped during the MCOT of the anchor carrier. This provides the flexibility to increase available resources as resources become available. Figure 8C This situation is shown. Additional attachments are added as they become available. LBT or at least CCA can be performed on the attachments. Fig.11 An example process for synthesis is shown. In an alternative, the auxiliary can only be dropped, for example, the auxiliary stops channel access after its MCOT is completed, but the anchor carrier's MCOT is still within its MCOT. This provides the flexibility to take advantage of carriers that become available before the anchor carrier (so the auxiliary's MCOT ends before the anchor carrier's MCOT). Fig.8D This situation is shown in Figure 1. If the gNB has no self-interference, then it can perform this process, for example, it can listen and transmit simultaneously. Fig.12 An example process for synthesis is shown.

[0140] refer to Fig.11 , at step 231, CAT4 LBT is performed on the anchor of the cell with a random window size. When SLBT is successful at step 232, the anchor can then be accessed (step 233). Then at step 234, a satellite for the candidate composite cell can be selected. At step 235, if SLBT on a satellite or a group of satellites is successful, then at step 236, the anchor can be synthesized with these carriers and access to the synthesized carrier can be allowed. At step 237, if more carriers need to be synthesized, then at step 238, the remaining satellites or anchors within the anchor carrier MCOT can be released. At step 237, if more carriers do not need to be synthesized, then at step 234, there can be satellites selected for the candidate composite cell. Alternatively, at step 232, if SLBT is unsuccessful, then the contention window size can be changed and SLBT can be performed on the anchor at step 239. It will then be determined whether SLBT was successful.

[0141] refer to Fig.12At step 241, CAT4 LBT is performed on the anchor of the cell with a random window size. When SLBT is successful at step 242, the anchor can then be accessed (step 243). Then at step 244, it is determined whether the gNB can synthesize the auxiliary with the anchor. If so, then at step 245, the anchor can be synthesized with these carriers and access to the synthesized carrier is allowed. At step 246, if more carriers need to be synthesized, then at step 247, each carrier can be released within its corresponding MCOT. At step 246, if more carriers do not need to be synthesized, then at step 244, it is additionally determined whether the gNB can synthesize the auxiliary. Alternatively, at step 242, if SLBT is not successful, then at step 248, the contention window size can be changed and SLBT can be performed on the anchor. It will then be determined whether the SLBT is successful.

[0142] In this case (regarding the composite carrier change during MCOT), LBT can be performed on each U-SCBW carrier separately. We call this sub-band LBT (SLBT).

[0143] In the synthesis of the carrier described in Figure 8 and Fig. 9 During the association process, if LBT fails, the node can try again by changing the contention window size to improve its chances of acquiring the channel. Fig. 9 – Fig.12 The process can take place at the gNB or the UE.

[0144] Since channel access is dynamic, the indication of information on the composite carrier should be dynamic. This indication can be provided by a PHY signal called composite carrier indicator (CCI). CCI can also provide the expected occupancy time.

[0145] Disclosed below is the transmission of CCI on DL. The gNB can indicate CCI on DL in one of the following ways. In the first way, there can be an indication of CCI on DL within the resources of the anchor carrier so that UEs in that cell can receive it unambiguously. For FR1 (Frequency Range – 1 (0.45 GHz to 6 GHz)), the concept of transmitting this information is Fig.13The CCI is located in the cell's 20 MHz anchor carrier. It can be included in the minimum carrier size such as 5 MHz supported by NR. A UE in the initial BWP of the anchor carrier can monitor the CCI without having to increase its BW. In a second approach, there may be an indication of CCI on the DL in an active BWP that does not overlap with the anchor carrier. If the UE's BWP does not include a portion of the anchor cell where CCI can be transmitted, an additional transmission may be required within the UE's active BWP. In a third approach, if the NR-U carrier is a carrier aggregated with a licensed PCell, there may be an indication of CCI on the DL and CCI may be sent on the PCell for the SCell.

[0146] The gNB may transmit CCI in one of the following ways. In the first way, CCI may be broadcasted via downlink control information (DCI) scrambled with CCFI-RNTI (composite carrier format indicator) in a common search space such as Type0-PDCCH common search space so that UEs can find and decode the DCI. The CCFI-RNTI may be given in the specification so that the UE knows its value before receiving the DCI. In the second way, UEs in their initial BWP or default BWP may remain in the anchor carrier. It may be required to signal the composite carrier to UEs in the active BWP. In this case, DCI scrambled with CCFI-RNTI may be transmitted as a group common PDCCH. The CCFI-RNTI is configured to the UE through higher layer signaling. In the third way, UE-specific DCI (such as DL or UL grants of the format 0_0, 0_1, 1_1, 1_0) scrambled with C-RNTI or CS-RNTI may provide information about the composite carrier. In the fourth approach, CCI may be transmitted on a preamble (such as a Zadoff-Chu sequence (ZC) sequence or an m-sequence) in the anchor carrier immediately after channel access. The preamble may be used as a reserved signal. It may be asynchronous with the symbol boundary and may be detected by the UE through time correlation. The preamble may be synchronized with the symbol boundary and sent in the first time slot after channel access.

[0147] The UE can be configured with carrier information of a list of B candidate attachments for the anchor carrier through SI. DCI can carry the status of these attachment cells in a B-bit bitmap. When the bit corresponding to an attachment is set to 1, it implies that the attachment is composited with the anchor carrier. An attachment with a bit set to zero is not part of the composite carrier. If CCI uses DCI, then the B bit is part of its payload. If CCI uses a preamble, then the B bit can be the root of a Zadoff-Chu sequence (ZC) or initialize the sequence (m sequence). For Figure 4AIn the example in , the UE is configured with a 3-bit bitmap corresponding to subordinate1, subordinate2 and subordinate3.

[0148] Alternatively, a set of possible configurations for synthesis can be configured to the node. The CCI can indicate an index to this set. If the number of possible configurations is small, then the index may require less than B bits to indicate the configuration. Regarding the configuration set, as seen in the following examples, this set can be configured to the UE via RRC signaling. In the first example, the set of configurations for synthesis is broadcast via the remaining minimum system information (RMSI) or other system information (OSI). In the second example, the set of configurations for synthesis is configured to the UE via UE-specific RRC signaling; this alternative allows configuration based on UE capabilities. If the UE does not have the ability to receive synthesized carriers exceeding X Hz (e.g., a predetermined Hz threshold), then it should be configured to have a configuration for synthesis not exceeding X Hz, but other UEs can receive transmissions on bandwidths exceeding X Hz, depending on their capabilities. This approach can work for cases where DL CCI is transmitted in UE-specific DCI or group-common PDCCH.

[0149] The CCI may be signaled multiple times during the channel occupancy time of the anchor carrier, especially if the attachment changes during this duration.

[0150] Disclosed below is the transmission of CCI on UL. The UE may synthesize channels in the following scenarios regarding the UE and the gNB.

[0151] In the first scenario, the UE is configured with resources for autonomous uplink (AUL) on multiple candidate composite cells using anchor1. Examples of candidate composite carriers are – a) anchor carrier alone, b) anchor and subordinate1, c) anchor, subordinate1 and subordinate2, etc. The UE may perform LBT to find the largest composite channel and transmit the AUL on it. The UE may also indicate the transmission of CCI via transmission on resources in the anchor carrier. When the gNB receives the CCI, it identifies the composite carrier and proceeds with detection of the AUL. Fig.14An example is shown where the UE composites the anchor with subordinate2 and subordinate3. It transmits a reservation signal across the composite channel until resources for its CCI appear. It transmits CCI in the anchor cell. It then switches its portion of bandwidth to the AUL resources for that composite cell and transmits on them. After completing the AUL transmission, the UE may do one of the following: 1) the UE returns to the default BWP, which may be in the anchor cell where it monitors DL; 2) the UE may release the composite channel; or 3) the UE may simply release one or more of the subsidiary carriers and continue to transmit PUCCH or SRS as needed. Note that, as Fig.14 As shown in , CCI can indicate the U-SCBW bands synthesized by the UE. The UE can occupy these bands (partially or fully) in the configured grant. Therefore, CCI can indicate the bands corresponding to the UE's grant.

[0152] In the second scenario, the gNB provides a new type of UL grant to the UE, which may be referred to as an "opportunistic UL grant". This grant may provide resources for each candidate composite carrier. The UE may transmit on the composite carrier channel that is available and has the most resources. This may allow efficient resource usage, as the UE may be able to empty its buffer faster when more spectrum is available. Additionally, hidden nodes near the UE may only affect certain U-SCBW carriers. Opportunistic synthesis on the UE side allows UL transmissions while avoiding hidden nodes. DCI formats such as 0_1 may be modified to support opportunistic UL grants - fields used for signaling for multiple component carriers may be reused for candidate grants. Fig.15 An example is shown where the gNB performs CAT 4 LBT with random backoff and accesses a channel for a composite channel containing the anchor and subordinate2 and subordinate3. It sends a UL grant to the UE. The UE may perform a short interval CCA (such as 25μs) (if it is within the gNB's MCOT, then the gNB may indicate in the grant the type of CCA / LBT to be performed for the UL). It will synthesize for the carriers available to it and use the grant for that composite carrier for UL resources. The gNB reads the CCI from the anchor carrier. After completing the AUL transmission, the UE may do one of the following: 1) the UE returns to the default BWP, which may be in the anchor cell where it monitors DL; 2) the UE may release the composite channel; 3) the UE may release only one or more of the subsidiary carriers and continue to transmit PUCCH or SRS as needed. Note that, as Fig.15 As shown in FIG, CORESET carries DCI indicating UL grant (PUSCH) to UE. DL / UL arrows indicate gaps (white areas) where UE performs CCA.

[0153] Since the payload of the bitmap indicating the synthesized attachment is small, the CCI can be transmitted on short PUCCH resources. The PUCCH resources can be in the anchor cell and before the UL transmission scheduled by the grant. Alternatively, the CCI can be transmitted on the RACH in a contention-free manner. The RACH resources and preambles can be configured to the UE through higher layer signaling. Multiple preambles can be configured to the UE, each preamble indicating one of the candidates for synthesis.

[0154] Disclosed below is channel sensing for synthesis. Sensing of anchors and satellites can be performed by: random windows, a single random backoff, or different random backoffs, all of which are described in more detail herein.

[0155] CAT 4 LBT with a random window can be performed on the anchor carrier. Once the channel for the anchor is acquired, higher priority access can be used for the auxiliary carriers so that transmissions can occur synchronously on the synthesized cell. And self-interference is avoided by not sensing and transmitting at the same time. Fig.16A An example for a composite anchor and attachment is shown, where high priority access to the attachment is obtained after LBT to the anchor is successful.

[0156] A single random backoff is generated for the anchor carrier and the same backoff is applied to the secondary cells in the CAT 4 LBT procedure. If successful, the carrier is synthesized. Fig. 16B An example for synthesizing anchors and attachments is shown, where the same random backoff is used for the anchor and all attachments.

[0157] Each U-SCBW may have a different random backoff. When the maximum backoff timer expires, if LBT is successful, then the U-SCBW is synthesized. A short CCA (e.g., 25 μs) may be applied to the U-SCBW that completed the random backoff earlier. Fig. 16C An example for composite anchor and attachment is shown, where LBT for each carrier uses a different random backoff, but channel access is aligned with a maximum backoff.

[0158] Discussed below are operations in flexible broadband operation. Here, the synthesized node cannot use an anchor carrier, but can synthesize the available U-SCBW bands together in a carrier. Synthesis can be done dynamically (e.g., the synthesized U-SCBW can be different each time the node gains channel access). The anchor U-SCBW is not required to be present in the synthesized carrier.

[0159] The node transmits CCI about the synthesized U-SCBW band to the receiver via the described method for anchor carrier based synthesis (such as via a preamble or a signal similar to PSS / SSS, or an RS such as DMRS or DCI, which may be UE-specific or common to all or multiple UEs).

[0160] The receiver may be configured to receive CCI on certain resources. The receiver monitors these resources and identifies the U-SCBW obtained by the transmitter upon receiving the indication.

[0161] Discussed below are multiple composite cells in NR-U. The UE can support carrier aggregation of multiple NR-U cells with a licensed PCell. Alternatively, the UE can access the NR-U channel as an SA cell, with which multiple other NR-U cells can be aggregated. In these cases, the UE can have multiple Rx chains to receive multiple carriers. It is configured with multiple anchor carriers and monitors each anchor carrier with one Rx chain. When the UE has carrier aggregation, an affiliate in one cell can be the anchor of another cell. Fig.17 An example where the anchor of Cell1 is subordinate2 of Cell2 is shown in . Similarly, a subsidiary carrier may be a subsidiary in more than one cell.

[0162] In idle or connected state, the UE can monitor the anchor of the cell for synchronization, SI, paging or RACH. When it receives CCI on the anchor, it can obtain information about the composite carrier. Fig.17 , the UE is monitoring anchor1 of Cell1 on one of its Rx chains. If the CCI from Cell1 indicates to the UE that the cell includes subordinate2 (which is the same carrier as anchor2 of Cell2), then the UE can follow one of the following procedures to access resources on the carrier. Figure 18 illustrates the UE behavior when monitoring both Cell1 and Cell2. (Notes t1, t2, and t3 show time instances in the process of comparing the behavior on these two cells).

[0163] Regarding the first process for accessing resources, a given U-SCBW belongs to only one cell at a time. In this case, the UE assumes that only Cell1 is active. Then from the UE's perspective, it is assumed that Cell2 with anchor2 will be deactivated. Even though the UE can have an Rx chain to receive Cell2, it is assumed that Cell2 is deactivated and no monitoring on Cell2 is performed until its UL / DL grant on Cell1 is completed or until Cell1 releases subordinate2. Cell1 can indicate the channel occupancy time on the CCI, so the UE can know when Cell1 releases subordinate2. This concept is described in Fig.18A is shown in Fig.19A Note that, if applicable Figures 18A-18B As shown in the figure, CCI indicates the composite of the subsidiary and the anchor. Since the x-axis is time, Fig.18A In the example, when receiving CCI at t2, the UE starts monitoring the composite cell after t2. The CCI indication of the composite carrier triggers this behavior. Fig.18B In the example, the CCI on cell1 indicates that the attachment is synthesized into cell1. Therefore, cell2 is deactivated. When synthesized into Cell1, the UE rate matches around the key resources of Cell2 so that Cell2 can still transmit some important signals (such as SSB) for discovery.

[0164] refer to Fig.19A , at step 251, the UE monitors NR-U anchor1 and anchor2 for CCI. If CCI is received at step 252, then at step 253, based on reception on anchor1, if reception of Cell1 with subordinate2 is required, the BW on RX chain1 is increased. At step 254, Cell2 on another RX chain2 is not monitored until Cell1 grant is completed or Cell1 releases subordinate2.

[0165] Regarding the second procedure for accessing resources, the UE can monitor multiple NR-U anchor cells simultaneously using different Rx chains even if the cells are configured with some common dependencies. When the UE receives a grant from Cell1 using resources on subordinate2, it can follow these procedures. The UE rate matches around certain resources, such as SSB / DRS and RACH of anchor2 in Cell2, to use for its grant on Cell1. This concept is described in Fig.18B The general process is shown in Fig.19BThe UE assumes that the SFI of Cell1 covers the SFI of Cell2 (in subordinate2) during the grant duration.

[0166] refer to Fig.19B , at step 261, the UE monitors NR-U anchor1 and anchor2 for CCI. If CCI is received at step 262, then at step 263, based on reception on anchor1, if reception of Cell1 with subordinate2 is required, the BW on RX chain1 is increased. Rate matching is also performed around the critical resources of Cell2. At step 264, Cell2 is continued to be monitored on another RX chain2.

[0167] As described in more detail herein, the UE may decide how to use resources on a carrier (as part of Cell1 or Cell2) based on the most recent CCI, the most recent grant, or based on conflicting cells. In the first example, the most recent CCI takes precedence. The UE uses the composite channel from the cell that transmitted the most recent CCI. If the attachment from Cell2 is synthesized into Cell1, the UE returns from monitoring the composite Cell2 to monitoring the anchor of Cell2. In the second example, the most recent grant takes precedence. If the UE is monitoring the anchor cell of Cell2, it receives the grant after the CCI on Cell1. In this case, the UE follows the grant of Cell2 because it is the most recent. In the third example, if the grants from Cell1 and Cell2 conflict in terms of resources on the anchor of Cell2 (which is the same as the attachment of Cell1), the UE may ignore the grant.

[0168] Discussed below is the process for BWP operation of a UE. In NR, a UE can be configured with 4 BWPs per carrier. For a composite cell in NR-U, the way to configure BWP can include W i BWPs or W BWPs, as described in more detail herein.

[0169] For example, if a cell has P candidate configurations (examples - a) anchor only, b) anchor and subordinate2, c) anchor and subordinate1, d) anchor and subordinate1 and subordinate2, e) anchor and subordinate1, subordinate2 and subordinate3, etc.), then the UE may be configured to have W for each of the ,th composite configurations of the cell. i BWPs, each candidate supports a certain number of BWPs. Higher-layer signaling configures P composite cell configurations for the UE. For W i = 1...Pi i=1 may be designated as representing an anchor. For i>2, a single BWP may be sufficient, e.g., for i>2, W i =1,

[0170] A UE may be configured with W BWPs for a cell. The gNB ensures that the UE uses the appropriate BWP for a given composite cell.

[0171] A UE may have one or more BWPs defined below. Example BWPs are shown in Figure 20. Initial BWP (especially for SA and DC) to perform synchronization, RACH transmissions, received paging, etc. Active-Anchor BWP - This is the active BWP within the anchor cell. The UE monitors the control information in this BWP and transmits PUSCH and receives PDSCH. This is similar to the "active BWP" in NR. Default BWP - This BWP is within the resources of the anchor cell. An RRC connected UE can stay in the default BWP and monitor control signaling. Active-Other-BWP - This is the active BWP, which includes resources within the attachment. It may also include resources within the anchor. Typically, the Active-Other-BWP is larger than the Active-Anchor BWP and is expected to provide more frequency resources to the UE.

[0172] One of the following procedures may be used to design an Active-Other-BWP. For the first procedure, no control monitoring occurs in the Active-Other-BWP. Control signal monitoring occurs in the Active-Anchor BWP or the Default BWP for grant. The grant may switch the UE to the Active-Other-BWP where the UE receives or transmits PDSCH or PUSCH. Upon completion, the UE may return to the previous BWP or the Default BWP. The previous BWP may be the BWP that activated it to operate in the Active-Other-BWP. Fig.21A and Fig. 21C An example is shown in . Fig.21BAn example default BWP is illustrated. If an Active-Anchor BWP triggers the UE to switch to an Active-Other-BWP, then the BWPInactivityTimer for the Active-Anchor BWP is reset and continues to decrement as if the UE was in an Active-Anchor BWP. For the second procedure, control signaling may be monitored on the Active-Other-BWP, similar to that in the Active-Anchor BWP. Similar to the BWPInactivityTimer for the Active-Anchor BWP, the Active-Other-BWP BWPInactivityTimer may be used once the UE enters the Active-Other-BWP. After expiration of the Active-Other-BWP BWPInactivityTimer, the UE returns to the default BWP. Fig.21D An example is shown in FIG. Alternatively, the DCI may trigger the UE to switch to another BWP, such as the default BWP or the Active-Anchor BWP or another Active-Other-BWP. Note that Fig.21A As shown in , the PDCCH provides a command and a grant to switch the BWP from default to active. After processing the grant, the UE returns to the default BWP. Fig.21B With Fig.21A Similar behavior, but the UE starts with an active BWP on the anchor. Fig. 21C , similar to Fig.21B , but returns to the active BWP on the anchor. Fig.21D Similar to Fig. 21C , but returns to the default BWP in the anchor when the BWP timer completes.

[0173] BWP management during channel access failure. NR-U BWP operation may be affected by channel access uncertainty. If the default behavior in NR is followed, the UE can stay in an active BWP even after the gNB loses channel access and decrements the BWPInactivtyTimer. However, the value of BWPInactivtyTimer may be fixed by RRC and cannot be changed based on channel availability. A "valid BWP" may be defined as a BWP that is activated to the UE and for which the gNB or UE has channel access rights. An "invalid BWP" may be defined as a BWP that is activated to the UE but for which the gNB or UE does not have channel access rights.

[0174] If BWPInactivtyTimer is set to a large value at the beginning, the UE can stay on the active BWP long enough until the gNB regains access to the channel. However, during the time when the channel is unavailable, the UE may experience a large power consumption due to its operation on the inactive BWP. Fig.23A An example is shown where the gNB initially has t COT,gNB,1 ms channel access, followed by LBT attempt and t COT,gNB,2 ms channel access. The UE's BWPInactivtyTimer can be set at t COT,gNB,1 The UE is unaware of the loss of channel access and continues to monitor during the LBT duration of the gNB (e.g., it monitors for invalid BWP and decrements its BWPInactivtyTimer during invalid BWP).

[0175] If BWPInactivtyTimer is set to a small value at the beginning, the UE can deactivate the active BWP faster and save power; however, the UE should be triggered to switch back to the active BWP whenever the gNB receives a channel access. Fig. 23B As shown in , the UE's BWPInactivtyTimer is set to t COT,gNB,1 The BWP is activated when the gNB is inactive and expires shortly thereafter. Since its BWP is deactivated, it does not waste much power monitoring during the inactive BWP period, but once the gNB gains channel access, it must receive a BWP activation DCI to switch back to the active BWP. This UE-specific DCI is transmitted on the default BWP. This process can cause significant signaling overhead, especially since the BWPs of multiple UEs may need to be reconfigured each time channel access is regained.

[0176] Figure 23A-23B illustrates an exemplary BWP operation during channel access unavailability in NR, where when COT is unavailable, BWPInactivityTimer is decremented ( Fig.23A ), or the BWP is deactivated due to the expiration of the BWPInactiviryTimer ( Fig. 23B ). The following methods may enable the UE to reduce excessive monitoring on an invalid BWP: 1) the UE suspends the BWPInactiviryTimer during the duration without channel access; or 2) the gNB dynamically indicates the value of the BWPInactivityTimer to manage the duration without channel access.

[0177] The UE may suspend the BWPInactivityTimer during the invalid BWP duration. If the UE knows the channel access time, it may suspend the BWPInactivityTimer during this duration, e.g., maintain the value of the BWPInactivityTimer and not decrement the timer while suspended. When the UE identifies a valid BWP state, the timer may be resumed, e.g., the BWPInactivityTimer starts decrementing again.

[0178] As disclosed, the gNB may indicate information from which the UE may infer a valid BWP through CCI when the UE obtains channel access. When the UE receives the CCI, it may recognize that the BWP is a valid BWP at that time and start or continue monitoring the BWP for grant.

[0179] The gNB may transmit CCI on the active BWP. CCI may be transmitted in broadcast mode in the form of a sequence (such as PSS). CCI may have the same sequence (such as PSS) to keep detection at the UE simple. CCI may be sent periodically so that the UE can detect it with high reliability, such as Fig.24A as shown in .

[0180] Alternatively, CCI may be transmitted on multiple U-SCBWs in non-raster positions so that the UE does not confuse it with the PSS of the SS / PBCH blocks, e.g. Fig. 24B As shown in . Multiple frequency resources ensure that UEs with different BWPs can detect at least one CCI.

[0181] The sequence, period and resources used for CCI can be configured to the UE via RRC signaling. It can be configured in a UE-specific manner per BWP.

[0182] Figure 24A-24B FIG. 1 illustrates an exemplary periodic CCI transmission in an active BWP, indicating that a node has channel access rights (valid BWP), wherein the periodicity has the same frequency resource (eg, Fig.24A ) or periodically have different frequency resources (e.g., Fig. 24B). It is disclosed herein that the UE maintains a timer called ValidBWPWindowTimer. When the UE receives CCI in an active BWP, it knows that the gNB has channel access and is on a valid BWP. It starts a ValidBWPWindowTimer and sets it to a value ValidBWPWindowTimerRRCValue, which can be configured through RRC signaling and decrements over time. The ValidBWPWindowTimerRRCValue is greater than the period of the CCI. Upon receiving CCI, the UE may perform one or more of the following operations: 1) restart the ValidBWPWindowTimer by setting it to the ValidBWPWindowTimerRRCValue; 2) if the BWPInactivityTimer was previously suspended, then unsuspend it and start decrementing on the active BWP; or 3) if the BWPInactivityTimer was not previously suspended, then restart it. The ValidBWPWindowTimer may expire because no new CCI has been received. The UE may then assume that an invalid BWP state has occurred, and it may perform one or more of the following operations: 1) suspend BWPInactivityTimer; 2) deactivate the active BWP; or 3) perform channel access, as described in more detail herein. First, the UE may assume that an invalid BWP state has occurred, and it may suspend BWPInactivityTimer, but monitor CCI. Unlike comprehensive BWP monitoring, because CCI may be relatively narrowband, CCI may be monitored in a low power state, and the UE may adjust its filter to monitor only within the narrowband bandwidth of the CCI. Second, the UE may assume that an invalid BWP state has occurred, and it may deactivate the active BWP and return to the default BWP. Third, the UE may assume that an invalid BWP state has occurred, and it may perform channel access for UL transmissions in the BWP.

[0183] In valid BWP operation, when the UE receives the grant, it may restart the ValidBWPWindowTimer.

[0184] Fig.25 The diagram illustrates an exemplary operation of using ValidBWPWindowTimer to identify valid BWP and invalid BWP states. The gNB may initially obtain a time window of duration t COT,gNB,1ms channel access. The UE operates in the active BWP in the corresponding composite cell. The UE starts BWPInactivityTimer when activating the BWP. The UE receives CCI twice in this COT and each time it starts ValidBWPWindowTimer. ValidBWPWindowTimer continues to decrement beyond t COT,gNB,1 . But the gNB lost channel access and hence the UE does not receive CCI. Therefore, the ValidBWPWindowTimer expires. The UE now realises that an invalid BWP period has started and suspends the BWPInactivityTimer.

[0185] However, the UE may continue to monitor the CCI during the Inactive BWP period, possibly in a low power state. Subsequently, the gNB obtains t COT,gNB,2 ms of access to the carrier. The UE may receive the CCI and may recognize at this time that it is entering a valid BWP state. It cancels the suspension of the BWPInactivityTimer, which begins to decrement. The UE also recognizes this as a valid BWP and begins monitoring the active BWP for authorization. Subsequently, the UE receives authorization, which resets the BWPInactivityTimer and the ValidBWPWindowTimer.

[0186] This approach can be considered to focus on indicating a valid BWP to the UE via CCI. Note that the UE can recognize the expiration of the valid BWP state when the ValidBWPWindowTimer expires; therefore, there can be a time lag between the gNB losing the MCOT and the UE recognizing the expiration of the valid BWP. Similarly, there can be a time lag between channel access being available and the UE recognizing that the invalid BWP has ended.

[0187] Fig.26 An example process is shown in . Here, ValidBWPWindowTimer is set when CCI is received. When ValidBWPWindowTimer expires, the UE suspends BWPInactivityTimer but monitors CCI in a low power state. After receiving CCI, the UE restarts ValidBWPWindowTimer and resumes BWPInactivityTimer.

[0188] refer to Fig.26, at step 271, when an active BWP is activated, BWPInactivityTimer is started. At step 272, the active BWP is monitored and BWPInactivityTimer is decremented. If it is determined at step 273 that BWPInactivityTimer has expired, then at step 274, the BWP is deactivated and returned to the default BWP. If it is determined at step 273 that BWPInactivityTimer has not expired, then at step 275, it is determined whether CCI is detected. Based on the detection of CCI, ValidBWPWindowTimer is started at step 276 and decremented for each time unit. If it is determined at step 277 that ValidBWPWindowTimer has expired, then at step 278, BWPInactivityTimer is frozen and an invalid BWP state is identified. At step 279, CCI is monitored, and if CCI is detected at step 280, then at step 281, BWPInactivityTimer is unfrozen, a valid BWP state is identified, and ValidBWPWindowTimer is started.

[0189] The active BWP is deactivated during the Inactive BWP state. When the UE enters the Invalid BWP state, it may run a timer called invalidBWPTimer. This timer may be set to the RRC configured value "invalidBWPTimerRRCValue" when the UE identifies an Invalid BWP state and the UE may continue to monitor CCI. This timer decrements as long as the UE does not identify a valid BWP state. If the UE detects CCI, it transitions to the Valid BWP state and suspends the invalidBWPTimer. Fig.27A This is illustrated. The arrow pointing near the top of the first default BWP indicates that the ValidBWPWindowTimer starts when a CCI is received.

[0190] If the invalidBWPTimer expires, the UE may switch to a different BWP (such as the default BWP). Fig.27B This operation is shown. This invalidBWPTimer procedure can help ensure that channel access failure of a composite carrier does not force the UE to remain in an invalid BWP state for a long time. Instead, the UE may be able to gain access to a different composite carrier configuration and continue to communicate there. Upon expiration of the invalidBWPTimer, the UE may go to the initial BWP or default BWP.

[0191] Fig.28A process for re-entering a valid BWP state upon receipt of a CCI and deactivating the BWP after expiration of the invalidBWPTimer is shown. At step 291, a determination is made as to whether an invalid BWP is identified. If so, then at step 292, an invalidBWPTimer is started, and at step 293, the invalidBWPTimer is decremented and the CCI is monitored. At step 294, if it is determined that the invalidBWPTimer has expired, then at step 295, the BWP is deactivated. If at step 294, it is determined that the invalidBWPTimer has not expired, then at step 296, a determination is made as to whether a CCI is detected. If a CCI is detected, then at step 297, a valid BWO state is identified, and at step 298, monitoring is performed on the active BWP. This is a summary of the process, but for further consideration of the flow, also review Fig.28 .

[0192] Invalid BWP determination based on COT (channel occupancy time). This document discloses a method for managing BWP using an indication of the expiration of a node's COT. For example, a gNB can indicate its COT to a UE. The COT can be indicated by a UE-specific DCI (such as format 0_0 or format 0_1 ​​or format 1_0 or format 1_1). Alternatively, the CCI can be indicated in multicast mode through the GC-PDCCH using the CCI-RNTI. When the channel access of the gNB ends, the UE can suspend the BWPInactivityTimer or deactivate the BWP. This provides the following advantages: the UE can enter a low power state as soon as the valid BWP state ends; the invalid BWP starts immediately after the COT expires. This is Fig.29 Here, when the UE obtains the cotExpiry time from the gNB, the UE uses the cotExpiryTimer. It sets the cotExpiryTimer and decrements it so that it expires when the gNB loses channel access. This timer can override the ValidBWPWindowTimer, for example, if the ValidBWPWindowTimer has not expired, but the cotExpiryTimer has expired, the UE recognizes the invalid BWP state, suspends the BWPInactivityTimer, and can monitor only the CCI without comprehensive BWP monitoring in a low power state. Fig.25 Unlike in which the UE can still monitor some early part of the invalid BWP until the ValidBWPWindowTimer expires, the UE resumes the BWPInactivityTimer and identifies the valid BWP state when detecting the CCI. Fig.30It shows the process of freezing BWPInactivityTimer when cotExpiryTimer expires.

[0193] refer to Fig.30 , at step 301, when an active BWP is activated, BWPInactivityTimer is started. At step 302, the active BWP is monitored and BWPInactivityTimer is decremented. If it is determined at step 303 that BWPInactivityTimer has expired, then at step 304, the BWP is deactivated and the default BWP is returned. If it is determined at step 303 that BWPInactivityTimer has not expired, then at step 305, it is determined whether cotExpiry is available. Based on cotExpiry being available, cotExpiryTimer is started at step 306 and decremented per time unit. If it is determined at step 277 that cotExpiryTimer has expired, then at step 308, BWPInactivityTimer is frozen and an invalid BWP state is identified. At step 309, CCI is monitored, and if CCI is detected at step 310, then at step 311, BWPInactivityTimer is unfrozen (if frozen), and a valid BWP state is identified.

[0194] UE-based COT freeze BWPInactivityTimer - For UL BWP operation in unpaired spectrum, the UE knows its COT duration t when it gains channel access to the active BWP COT,UE The UE suspends its BWPInactivityTimer after its COT expires so that it does not decrement until the UE gains next channel access. Fig.31 An example is shown, where the UE is at t COT,UE,1 UL BWP channel access is obtained in the UE, followed by LBT and t COT,UE,2 Since the UE knows t COT,UE,1 The expiration time and the COT,UE,2 The channel access start time for channel access, so it can suspend BWPInactivityTimer between channel access opportunities. Since this is an invalid BWP, the UE cannot monitor the active BWP during this period either.

[0195] Fig.32Another example is shown, where the UE may also restart the BWPInactivityTimer after acquiring channel access. During the Inactive BWP duration, the UE may be in a "zero BWP" state, in which the UE may at most perform channel sensing / LBT, but not monitor PDCCH or transmit UL signals.

[0196] The gNB dynamically indicates the value of BWPInactivityTimer. Another scheme for efficient management of BWPInactivityTimer is described herein. The gNB may dynamically indicate the value of BWPInactivityTimer BWPInactivityTimerDCIValue via a UE-specific DCI, such as a grant carrying DCI (format 00, 01, 10, 11) or a GC-PDCCH scrambled with CCI-RNTI. Upon receiving this DCI, the UE may reset the value of BWPInactivityTimer to one of the following values: 1) BWPInactivityTimerDCIValue; or 2) min(BWPInactivityTimerDCIValue, BWPInactivityTimerRRCValue). BWPInactivityTimerDCIValue may be calculated based on the COT of the gNB. After the COT expires, the UE may enter a low power state in an invalid BWP, or the UE may deactivate the active BWP when the COT expires.

[0197] Active BWP management in flexible broadband operation. If flexible broadband operation is supported in NR-U, the active BWP available to the UE in a given channel access opportunity may not be available in the next channel access opportunity because the gNB may not be able to access the same 20 MHz band during two channel access opportunities; therefore, a new active BWP may be obtained depending on the synthesized carrier configuration. This concept is as follows Figures 33A-33B As shown in , the bandwidth and spectrum of the composite carrier can be different in different channel access opportunities (ChAxOp). As shown in the figure, CCI can indicate the composite carrier BW. Fig.33A In ChAxOp1, the gNB can COT,gNB,1 The UE may obtain channel access to the composite channel within t2 in ChAxOp2. During this time, the UE may operate in BWP1. Subsequently, the gNB may COT,gNB,2 Composite carrier access is obtained within 10 seconds and the UE can operate on BWP2. Fig.33B In the case of gNB, the gNB can COT,gNB,1After the gNB’s COT expires, it provides an UL grant to the UE in BWP2. The UE may perform LBT and gain access to BWP2. If the UE does not gain channel access to BWP2 for transmission of PUSCH, then the UE may return to the default BWP or active BWP1.

[0198] The BWP may be different between different channel access opportunities. Therefore, as disclosed, when the COT of the gNB or UE expires, the UE may deactivate the active BWP. Subsequently, the UE may perform the following procedures to determine a new active BWP. In the first procedure, after deactivating BWP1 at the expiration of the COT, the UE may switch to a BWP (such as the default BWP configured for the UE). The UE may monitor this BWP for DCI, which may activate the active BWP2 based on the composite carrier in the next channel access opportunity. The deactivation of the active BWP may be performed using Fig.30 The cotExpiryTimer procedure in Fig.34 The COT itself can be obtained from the CCI transmitted in the active BWP1. In the second process, after deactivating BWP1 when the COT expires, the UE may not have a default BWP. Instead, it can search for CCI in the candidate BWPs. Up to BWP max The candidate BWP (for CCI monitoring) is configured to the UE by RRC on the potential composite carrier. The configuration may include a duration t CCImonitor,i ms to monitor is called BWP i The UE can switch to the i-th candidate BWP and CCImonitor,i Monitor BWP within ms i To obtain CCI. If the UE is at t CCImonitor,i No message received from BWP within ms i Corresponding CCI, then it can switch to BWP i+1 and starts monitoring CCI. If the UE is in the i-th candidate BWP i If it receives CCI in the j If the UE does not receive CCI in any candidate BWP, it may return to monitoring BWP1 and may cycle through the candidate BWPs. i If no CCI is received on the UE, the UE may consider it to be in an invalid BWP state. Fig.34As shown in , arrow 401 from CORESET shows that the PDCCH indicates the expiration time of the COT of the gNB. Therefore, the UE can switch to the default BWP when the COT of the gNB expires. After receiving the PDCCH indicating the new gNB COT in COREEST on the default BWP, in another channel access opportunity, the UE switches to the new BWP according to the BW of the composite carrier. When the COT of the gNB expires, the UE transitions to the default BWP and monitors it for the next CCI. If the next CCI on the default BWP indicates that it must switch to BWP2, the UE switches and monitors BWP2.

[0199] Fig.35 The concept of candidate BWPs for searching CCI is shown. CCI may be transmitted on a BWP so that the UE has enough time to tune to a new BWP before trying to receive CCI.

[0200] Fig.36 The process of finding an active BWP in a channel access opportunity is shown. Here, the UE can activate the BWP in ChAxOp1 by searching for CCI in the candidate BWPs and can activate the active BWP in ChAxOp2.

[0201] refer to Fig.36 , at step 321, deactivate BWP from ChAxOp1. At step 322, i=1 and CCIMonitorTimer1=t CCImonitor i. At step 323, monitor BWP i To get CCI and decrement CCIMonitorTimeri. At step 324, determine whether CCIMonitorTimeri has expired. If yes, then i=i+1, and at step 326 determine whether i>BWPmax. If no to step 326, then at step 327, CCIMonitorTimeri=t CCImonitor i. At step 324, if it is determined that CCIMonitorTimer i If the CCI is detected, then a subsequent determination is made at step 328 whether the CCI is detected. If the CCI is detected, then at step 329 the BWP indicated by the CCI is activated for ChAxOp2. Fig.36 A summary of some of the processes.

[0202] Can be obtained through BWP i The CCI is indicated by the UE-specific DCI on the BWP. Activ e provides authorization to the UE. The UE can switch to BWP Active to process the grant. When the gNB gains channel access to the new composite carrier configuration, multiple UEs may be affected. The gNB may want to configure BWP for multiple UEs on the newly acquired composite carrier; therefore, CCI can be used to trigger BWP switching in multicast or broadcast mode. The BWP activation trigger can move multiple UEs to the new active BWP at once. GC-PDCCH scrambled with CCI-RNTI can be used to indicate the BWP to the UE Active GC-PDCCH carries BWP Active Reference Fig.35 , CCI may be a CORESET (Control Resource Set) which includes a common search space for GC-PDCCH that the UE is configured to monitor. When the UE receives the CCI, it may identify the BWP to be activated.

[0203] Alternatively, the GC-PDCCH may carry only information about the composite carrier (e.g., the composite U-SCBW). The UE may be configured via RRC to switch to the BWP for that composite carrier configuration. k To enable the UE to monitor CCI in low power mode, the CCI can be a sequence-based signal similar to PSS / SSS. In addition, it can be narrowband so that the UE can operate on a smaller bandwidth during the CCI detection phase. The CCI can also indicate the COT of the gNB so that the UE can deactivate the BWP after the COT expires. Active .

[0204] Currently, NR supports the case where the UE has a single active BWP. The subject matter of this article discloses that when the UE has multiple Tx-Rx chains, it can monitor more than one candidate simultaneously using one Tx-Rx chain for each candidate BWP. For such UEs, the gNB can schedule CCI on different candidates simultaneously. This can allow for minimal latency in obtaining CCI. i After receiving the CCI, the UE can switch to the indicated BWP Active And the candidate BWP can be deactivated. NR-U can use this process on a synthesized carrier using an anchor cell. In addition, this document discloses NR-U support carrier synthesis based on channel availability in the absence of an anchor cell. In this case, a process based on searching for CCI in the candidate BWP to obtain the BWP can be applied. In flexible operation without an anchor, depending on channel availability, a cell can potentially occupy up to N*U-SCBW Hz. The node can synthesize adjacent available U-SCBWs into one ChAxOp. The set of frequency resources available in one ChAxOp may be different or non-adjacent to the set of frequency resources available in another ChAxOp, since anchors are not required to be present in every ChAxOp.

[0205] Here is a process related to the deactivation of an active BWP when triggered by the expiration of the COT. The deactivation of an active BWP can be performed in one of the following ways. The timer "cotExpiryTimer" is used to determine when to deactivate the BWP. The timer is set to the value cotExpiry, which can be the remaining duration within the MCOT. The counter is decremented in time units (such as ms) or time slots or codewords. When the counter expires (reaches zero), the BWP is deactivated. Deactivation may occur even if the BWPInactiviryTimer has not expired. Fig.37A The BWP is shown to be deactivated when the gNB acquires the channel. Here, the UE starts BWPInactivityTimer and cotExpiryTimer when activating its BWP. The BWPInactivityTimer can be restarted every time there is a grant. When the cotExpiryTimer expires, the UE deactivates the active BWP even if the BWPInactivityTimer has not expired. Fig.37B 1 shows that BWP is disabled when the UE acquires a channel. Here, cotExpiryTimer is set to t COT,UE .

[0206] Once the UE receives cotExpiry, it may start cotExpiryTimer; the UE may receive this on an active BWP, so there may be a lag in setting cotExpiryTimer relative to starting BWPInactivityTimer. The UE may adjust the cotExpiry value to cotExpiryAdj based on its processing delay before setting cotExpiryTimer. This is done in Fig.38 As shown in Figure 1, where CCI indicates the COT of the gNB from the start of the CORESET carrying the CCI. Fig.38 The arrow shown in provides the time when the CCI indicates the COT expires.

[0207] Fig.39 The process of deactivating a BWP using cotExpiryTimer is shown. Here, the UE may operate in an active BWP until cotExpiryTimer expires or BWPInactivityTimer expires. The value of BWPInactivityTimer is a function of channel availability, such as the remaining duration within the COT, referred to as cotExpiry. For example, BWPInactivityTimer is set according to Equation 1. Here, BWPInactivityTimerRRCValue is the value configured for the timer by RRC.

[0208] Equation 1

[0209] BWPInactivityTimer

[0210] =min(BWPInactivityTimerRRCValue, cotExpiry)

[0211] refer to Fig.39 , at step 331, when an active BWP is activated or an authorization is received, BWPInactiviryTimer is started. At step 332, the UE may operate in the active BWP and decrement BWPInactivityTimer. At step 333, if cotExpiry is available, cotExpiryAdj is calculated at step 334, and cotExpiryTimer is started with the cotExpiryAdj value and cotExpiryTimer is decremented for each time unit. At step 335, it is determined whether cotExpiryTimer or BWPInactivityTimer has expired. At step 336, if expired, the active BWP for the UE is deactivated. This is just Fig.39 Note that, in general, the descriptions of processes in this document are examples and summaries, and these processes may include more information than the summary in this document.

[0212] Fig.40A The concept of deactivating BWP when channel access is obtained by gNB is shown. Here, the UE can deactivate BWP based on the remaining time t of channel access. COT,gNB -t i To update the value of cotExpiry, where t i is to calculate cotExpiry i At t j After receiving the authorization, the UE can use t j cotExpiry j When the BWPInactivityTimer expires, the UE may deactivate the BWP. Fig.40B An example is shown, where cotExpiry is the COT time t of the UE. COT,Uf function. Fig.41The process of deactivating a BWP using BWPInactivityTimer is shown. At step 341, when an active BWP is activated or authorization is received, BWPInactivityTimer is started. Note that cotExpiry = maximum possible value. At step 342, operate in the active BWP and decrement BWPInactivityTimer. At step 343, determine whether cotExpiry is received. If cotExpiry is received at step 343, then set BWPInactivityTimer = min(BWPInactivityTimerRRCValue, cotExpiry) and decrement BWPInactivityTimer per unit time. If BWPInactivityTimer expires at step 345, then deactivate the active BWP for the UE at step 346. If cotExpiry is not received at step 343, or BWPInactivityTimer has not expired at step 345, then go to step 342.

[0213] The value of cotExpiry may be obtained by the UE in the following ways. In the first way, cotExpiry is set based on the COT of the gNB when the gNB obtains channel access. cotExpiry may be provided to the UE via UE-specific DCI (such as UL or DL ​​grant). Alternatively, cotExpiry may be transmitted in a multicast or broadcast manner via a signal such as CCI; the CCI may carry the channel access duration of the gNB based on which the UE calculates cotExpiry. In the second way, cotExpiry may be set based on the COT of the UE when the UE obtains channel access. Depending on the LBT access and priority type, cotExpiry may be set to the MCOT of the UE, or to the duration of the grant received by the UE.

[0214] BWP deactivation based on channel access may be a configurable mode of operation. If configured, the UE may deactivate the active BWP using the procedures described herein. If not configured, the UE may continue to operate in a default manner in NR, for example based on setting the BWPInactivityTimer via RRC signaling / parameters. Configuration of BWP deactivation based on channel access may be done via RRC and may be UE-specific. Each BWP may be configured with a parameter indicating whether the UE may use BWP deactivation based on the channel access duration.

[0215] Alternatively, a bit in the grant given to the UE may indicate whether the UE has to perform BWP deactivation based on the channel access time. If cotExpiry is not available to the UE (e.g. if the gNB does not transmit its channel occupancy duration or the UE does not receive it), then the UE may operate with the default procedure in NR.

[0216] The UE can perform LBT on a bandwidth equal to or less than its accessed BWP so that it does not need to increase the Rx bandwidth for channel sensing. The minimum bandwidth for sensing can be equal to the minimum carrier bandwidth (CBW) supported in NR. For example, in FR1 (frequency range - implying below 7GHz), for UL RACH transmissions in NR-U initial access for FR1, the UE can perform LBT on a band as small as 5MHz.

[0217] like Fig.22A As shown in , if the UE uses block interleaved frequency division multiple access (BIFDMA) transmission on its UL BWP (such as PUCCH or PUSCH), it can perform LBT as described in the following options. In the first option, the UE performs LBT only on the frequency blocks for which it has a grant. In this case, energy detection is performed in the frequency domain (e.g., after a Fast Fourier Transform (FFT) operation at the UE receiver), so only the frequency blocks for UL transmissions granted to the UE are used for energy measurement. If the energy detection (ED) exceeds a threshold, the UE cannot access the channel to transmit on the UL. Fig. 22B In a second option, the UE may perform energy detection (ED) on the contiguous spectrum between the lowest and highest blocks in the grant, e.g., measuring the energy in the time domain after a filter with a bandwidth smaller than its active UL BWP. Fig. 22C . In wideband operation, this may mean that the UE may perform channel access on the U-SCBW band for which PUSCH resources are provided in the grant. In a third option, the UE performs LBT on the entire BWP, e.g., measures the energy in the time domain after a filter with the same bandwidth as its active UL BWP, even if its operating band only constitutes a portion of the BWP, e.g., when the UE's UL grant spans a subset of the U-SCBW in the BWP. If the ED exceeds a threshold, the UE does not access the channel. Fig.22D This example is shown in the figure.

[0218] With reference to the second and third options, the UE may be multiplexed with other UEs and may sense energy from other UEs. Depending on the number of UEs, the multiplexed resources, the thresholds may be different. The gNB may indicate to the UE the resources and thresholds used for channel sensing. This information may be part of the UL grant. In the above options 2 and 3, the UE may sense energy in the multiplexing block in the frequency from other UEs. Depending on the number of multiplexing blocks and UEs, the thresholds may be different. The gNB may indicate to the UE (one or more) channel sensing options and (one or more) related thresholds. This information may be carried on the UL grant DCI as illustrated in Table 2.

[0219] Table 2 - UL Grant DCI / BWP Activation (DCI 0_1) with LBT Field Extension

[0220]

[0221]

[0222] Some of the following examples may be related to FIG. 22 (e.g., how a UE performs LBT on a 20 MHz band with respect to its allocated grant). The following examples illustrate how a UE may perform LBT for PUSCH transmissions in wideband operation. Assume that the gNB obtains access to a set S of T subbands. gNB ={S t}, where t = 0, 1, …, T-1. The gNB can share this COT with the UE for either dynamic PUSCH transmission or configured grant (CG) PUSCH transmission. The active BWP of the UE spans B UE U-SCBWS BWP ={S b}, where b = 0, 1, ..., B UE -1. UE receives the signal across the U-SCBW band S UE ={S j}, where j = 0, 1,…, J-1.

[0223] If the UL grant is outside the gNB’s COT, the UE performs CAT4 LBT to acquire the channel in one of the following ways. In the first way, The UE shall only be in S UE CAT4 LBT is performed on the frequency bands in Fig.44A In the second method, The UE shall grant the S BWP LBT is performed on the frequency band in Fig.44BNote that a BWP may not completely cover the integer G U-SCBWs. In this case, if a node includes at least some BWP resources, it performs LBT on the entire U-SCBW.

[0224] For the case where the COT obtained by the gNB is shared with the UE, the following scenarios are possible and are Figure 45A-Figure 47 In the first scenario, the set S gNB The bandwidth of the UE can cover the BWP of the UE. It can also exceed the active BWP of the UE. In this case, to access the shared COT, the UE performs CAT2 LBT in one of the following ways. In the first way, UE in S gNB LBT is performed on Fig.45A In the second method, The UE includes S in the UE's BWP BWP LBT is performed on the frequency band of Fig.45B In the third method, The UE shall include only S in the UE authorization. UE LBT is performed on the U-SCBW band. Fig.45C Shown in.

[0225] In the second scenario, the set S gNB The bandwidth does not span the entire active BWP of the UE. In this case, in order to access the shared COT, when When the UE’s authorized resources are within the gNB’s COT bandwidth (e.g., the UE’s authorized resources are within the gNB’s COT bandwidth), the UE performs CAT2 LBT in one of the following ways. BWP LBT is performed on all U-SCBWs of the resource. Fig.46A In the second method, the UE is in S gNB LBT is performed on all U-SCBWs in the Fig.46B In the third method, the UE only includes S in the UE authorization. UE LBT is performed on the U-SCBW. Fig.46C Shown in.

[0226] In the third scenario, In the case that, for example, the resources of the UE's grant are not within the subband of the gNB's channel access (this can happen in the case of CG PUSCH, where the resources exceed the bandwidth of the gNB's current COT), the UE can act on the grant in one of the following ways. In the first way, the UE does not transmit the grant. In the second way, the UE gNBCAT2 LBT is performed on the U-SCBW and through the S gNB The PUSCH is transmitted using the granted resources within the node’s range by puncturing or rate matching to ensure that the channel is occupied and not lost to another node. Fig.47 , where the UE can only access the channel on one U-SCBW, while its CG PUSCH resources span two U-SCBWs. Since the gNB can only access one band, the UE transmits on that band after a successful CAT2LBT, but does not transmit on the other U-SCBW band on the gNB without COT.

[0227] Fig.52A 361 for composite carrier enabling gNB-acquired COT sharing with UE 361. At step 371, gNB 360 obtains channel access for a certain duration (COT) on a composite carrier composed of one or more U-SCBW bands. At step 372, gNB 360 transmits CCI to UE 361. At step 373, UE 361 identifies at least one U-SCBW band in the COT of gNB. Subsequently, at step 374, UE 361 receives UL grant within the COT of gNB. UE 361 receives UL grant via S in step 375. BWP or S UE or S gNB CAT2 LBT is performed, and at step 376, if the LBT is successful, the PUSCH is transmitted. Fig.52B The UE process for sharing a COT acquired by a gNB is shown. UE 361 monitors CCI (at step 381) and upon detecting it (at step 382), identifies at least one frequency band in the composite carrier in that COT at step 383. If UE 361 receives an UL grant in that COT (at step 384), it performs CAT2 LBT (at step 385) and transmits PUSCH (at step 386).

[0228] If UE 361 has multiple CGs from which it can automatically select a CG for PUSCH transmission within the COT acquired by the gNB, it can perform the following operations. gNB If UE 361 has resources restricted to S gNBIf there are more than one CG available, UE 361 can select an appropriate CG to transmit PUSCH on the COT acquired by the gNB. UE 361 autonomously selects a CG based on the type of traffic, latency requirements, priority, etc. gNB 360 identifies the autonomously selected CG based on its DMRS.

[0229] If UE 361 receives multiple PUSCH grants in a shared COT, where the PUSCH grants span different numbers of U-SCBWs, such as Fig.48A As shown in , UE 361 uses the total set of PUSCH frequency resources on multiple grants to determine the LBT bandwidth (if it is based on S UE In this example, UE 361 is in S UE,1 Receive the grant for PUSCH1 on the S UE,2 The LBT bandwidth is the union of the PUSCH frequency resources of PUSCH1 and PUSCH2.

[0230] Alternatively, if the U-SCBW of the subsequent PUSCH is not included in the U-SCBW band of the previous PUSCH, the UE 361 may perform separate LBT before each PUSCH. Fig.48B In the example of , UE 361 performs CAT2 LBT before PUSCH1 and between PUSCH1 and PUSCH2. In doing so, UE 361 may puncture either the last symbol of PUSCH1 or the first symbol of PUSCH2.

[0231] exist Fig.48C In this case, the U-SCBW frequency band of PUSCH2 includes the frequency band of PUSCH1 and the additional U-SCBW frequency band. UE,1 Perform CAT2LBT on the S UE,2 CAT2 LBT is performed on the frequency band of PUSCH1 to transmit PUSCH2. Because the gap between PUSCH1 and PUSCH2 is long due to the need for CCA before the additional U-SCBW, it performs LBT on the frequency band of PUSCH1. PUSCH3 is transmitted but included in the frequency band of PUSCH2, so CCA is not required between PUSCH2 and PUSCH3.

[0232] The following procedures may be supported. UE 361 may perform CAT2 LBT on PUSCH2 only when UE 361 has obtained a channel for at least one or more frequency bands included in PUSCH2 (e.g., there is an overlap between PUSCH1 and PUSCH2 frequency resources), such as Fig.48C In this case, UE 361 already has channel access to the frequency band for PUSCH1. If this is not the case, then UE 361 may only perform CAT4 LBT to access the channel for PUSCH2, as shown in FIG. Fig.48D as shown in .

[0233] Thus, UE 361 may determine the entire S in a single step or in more than one step. gNB or a subset thereof. Using this information, UE 361 determines its LBT bandwidth according to configuration rules that may be provided by RRC signaling or by a dynamic indication obtained via one of the following ways. In the first way, through DCI in a common search space or a UE-specific search space. This process is Fig.53A Here, UE 361 may monitor its configured CORESET at step 391. After successfully decoding the DCI (which may be broadcast or multicast or UE-specific) at step 392, UE 361 identifies at step 393 that its gNB 360 is transmitting and that at least the U-SCBW of the CORESET in which the DCI is detected is within the COT of the gNB. In step 397 step-1, UE 361 may identify the CORESET denoted as S UE,Step1 If that DCI or another DCI provides a DL grant to UE 361 within that COT, then UE 361 can infer that the COT bandwidth of the gNB includes at least the U-SCBW that includes those PDSCH resources. Similarly, if that DCI provides an UL grant to UE 361 within that COT, then UE 361 can infer that the COT bandwidth of the gNB includes at least the U-SCBW that includes those PUSCH resources. UE 361 identifies S in this second step-2. UE,Step2 (Step 395). Thus, the DCI behaves like an implicit CCI. At step 396, if the UE 361 has to perform LBT or measurements or process the grant, it uses the information from step-1 (step 397) and step-2 (step 395), e.g., the union S UE,Step1 ∪S UE,Step2 , to determine the BW of the signal to be processed. If the step-2 (step 395) information is not available, then the UE 361 is expected to use the result of step-1 (step 397) to perform its operation. Note that S UE,Step1 ∪SUE,Step2 Can be equal to S UE , S BWP , S gNB .

[0234] Rules for a PUSCH transmission method (such as whether to puncture the PUSCH) may be configured to the UE 361 through RRC signaling.

[0235] In the second method, if Fig.53B As shown in the process of FIG. 401 , the CCI may indicate that at least the current (one or more) U-SCBWs (on which the receiver receives the CCI) are in the COT of the gNB. The CCI may explicitly indicate a subset or all of the U-SCBWs in the COT of the gNB, for example, via a bitmap, at step 403. The CCI itself may be in the form of DCI. Upon receiving the CCI (steps 401, 402), the UE 361 at step 404 has sufficient knowledge of the composite carrier to process its signals of interest. Note that this may not include full knowledge of all composite frequency bands in the wideband carrier.

[0236] In the third method, if Fig.53C As shown in the process in , UE 361 can determine whether a U-SCBW exists in the COT of the gNB by detecting the CCI in the U-SCBW (steps 411 and 412). If multiple U-SCBWs are synthesized in the carrier, then UE 361 can detect a CCI in each synthesized U-SCBW (step 413). The number of U-SCBWs to be monitored is configured to UE 361 via RRC signaling. For example, the CCI can be in the form of DMRS. UE 361 can monitor possible U-SCBWs sequentially to detect (one or more) DMRS. If it detects DMRS, then it identifies the U-SCBW as part of the COT and uses that information to process its signal within that COT (step 414).

[0237] To save power, UE 361 may monitor a narrow BWP (such as the default value for a DCI or CCI). The DCI or CCI may explicitly indicate the LBT bandwidth for that COT through a field, or implicitly (without additional signaling or fields) through a grant. If UE 361 has explicitly received the LBT bandwidth as an S gNB instructions, then it can be used with the overlay S gNB The LBT bandwidth corresponding to the U-SCBW. gNB explicit knowledge of S BWP or S UE The corresponding LBT bandwidth (if authorized).

[0238] The wake-up signal may be used for power saving of the NR-U UE 361. The wake-up signal may indicate whether the UE 361 must wake up to monitor the transmission of the gNB or may remain asleep for a certain duration. The wake-up signal may serve as CCI and may provide information about the S gNB or S gNB The wake-up signal may be transmitted outside of the discontinuous reception (DRX) ON cycle, and the UE 361 may receive the wake-up signal in its default BWP (BWP D ), the default BWP can be limited to a portion of the U-SCBW to keep the processing BW small and thus save power. Fig.49A An example is shown in FIG. 1. After receiving the wake-up signal or CCI, UE 361 switches its active BWP (BWP) in the DRX ON period. A ) on wake up. BWP A The frequency band is determined by the CCI.

[0239] Alternatively, UE 361 may Fig.49B The wake-up signal is monitored during its DRX ON duration as shown in FIG. 1 , which can be performed at its default BWP (BWP D ) or active BWP(BWP A ) occurs on.

[0240] If UE 361 receives a wake-up signal indicating that it is waking up, then it will monitor the PDCCH during its DRX ON duration. If it receives a wake-up signal indicating that it can sleep, then UE 361 will not monitor during the subsequent one or more DRX cycles. If it does not receive a wake-up signal, then considering that the wake-up signal is used as CCI indicating that gNB360 has obtained channel access, it continues to monitor for wake-up. The wake-up signal can be transmitted by gNB 360 as a UE-specific DCI or a group-common DCI. Alternatively, a preamble or RS can be used as a wake-up signal. UE 361 is configured by RRC to monitor the wake-up signal with a certain period.

[0241] The following discloses how to transmit synchronization signals in a wideband carrier. The following method may be a further consideration on how to assign SSBs in a wideband carrier.

[0242] When a node such as gNB 360 composites channels into a wideband composite carrier, it can handle the transmission of SSB or DRS in the following manner. For a cell that defines SSB / DRS for each U-SCBW, one or more raster points in frequency may be predefined. The gNB 360 will transmit the SSB / DRS on one or more raster points within its composite carrier. The gNB 360 may perform CAT2 LBT access in the following manner to transmit high priority SSB / DRS. Since only high priority transmissions may follow CAT2 LBT, but OCB requirements must still be met, channel blocking should be avoided in order to coexist fairly with other nodes. In the first approach, the gNB 360 may perform CAT2 LBT on multiple U-SCBWs at once and transmit SBB / DRS on multiple raster points on the composite band with COT. This Fig.50A In the second approach, the gNB 360 may perform CAT2 LBT on one or more U-SCBW bands, but transmit SBB / DRS on a single raster point in the COT. This may avoid blocking the entire wideband carrier at the same time. If CAT2 LBT is successful on multiple U-SCBW bands, the gNB 360 may select a raster point in one of the following options. In the first approach, the raster points to be used are known a priori for the construction of the composite carrier. For example, the raster point carrying SSB / DRS may be the lowest raster point within that composite carrier. This raster point location may be predefined in the specification, or configured to the UE 361 via RRC signaling, or indicated by the PCell. This is described in detail in the specification. Fig.50B In the second option, the gNB 360 may dynamically select the raster points on which it transmits SSB / DRS.

[0243] In the third approach, the gNB 360 may perform CAT2 LBT on a single U-SCBW only and transmit SSB / DRS along with the signal meeting the OCB requirements for that band. Within a single U-SCBW band, SSB / DRS may be repeated in frequency to meet OCB requirements and provide greater robustness for discovery, synchronization, and measurement. This Fig.50C In a fourth approach, the grating points can be staggered in time across the U-SCBW band. Consider one grating point per U-SCBW. Fig.50D As shown in , gNB 360 obtains CAT2 access to the channel for each U-SCBW band separately. The relative shift of DRS between U-SCBW bands can be predefined or configured to UE 361 through RRC signaling, or indicated via PCell. Using the knowledge of the offset and periodicity of DRS, UE 361 can detect DRS signaling on each U-SCBW band.

[0244] Disclosed below is a method by which UE 361 can use CCI to perform measurement and reporting in wideband operation. Some of the following may be considerations for applying CCI to CSI measurement or reporting.

[0245] If UE 361 has to perform measurements, it should know the bandwidth of the gNB's COT so that it can know with certainty that the corresponding RS (such as CSI-RS, DMRS, SSB) is available. , then the UE can only UE,Step1 to perform the measurement.

[0246] S UE,Step1 The determination of may depend on the capabilities of the UE. In the first step, one UE 361 may detect only one U-SCBW in the COT, while in the first step, another UE 361 may detect more than one U-SCBW in the COT. Thus, the measurement becomes dependent on the capabilities of the UE 361. To support this, the UE 361 may indicate to the gNB 360 that it is in S UE,Step1 361 may report the frequency bands on which measurements were made during the COT. Note that within the COT, the S UE,Step1 Subsequent measurements may be made over a smaller bandwidth, but subsequent measurements occurring after determining other U-SCBWs in the COT may occur over multiple U-SCBWs and therefore over a wider bandwidth. Fig.54 An example of signaling to determine measurement bandwidth and reporting between gNB 360 and UE 361 is shown. At step 421, gNB 360 performs LBT and transmits CCI to UE 361 at step 422. Depending on its capabilities, UE 361 may detect one or more synthesized U-SCBWs in that COT at step 423. UE 361 makes measurements based on the identified synthesized frequency bands at step 424. LBT succeeds at step 425. At step 426, UE 361 reports the measurements and the bandwidth over which the measurements were made to gNB 360.

[0247] Fig.51An exemplary method flow associated with the channelization and bandwidth portions as disclosed herein is illustrated. At step 351, a channel is sensed. At step 352, based on the sensing, it is determined that the channel is available in multiple frequency bands (e.g., 20 MHz for each carrier). At step 353, based on the channel being available in multiple frequency bands, multiple frequency bands are combined into a composite carrier. The composite carrier can be a wideband carrier in which the sum of multiple frequency bands exceeds 20 MHz. At step 354, one or more frequency bands in the composite carrier are indicated using CCI. At step 355, the CCI is sent to a receiver. In addition to other methods disclosed herein, CCI can be sent via a preamble of a Zadoff-Chu sequence, a DCI of a UE-specific PDCCH, an RRC, or a DCI of a group common PDCCH. Synthesis can be limited to carriers with adjacent frequencies.

[0248] Channel, frequency band and carrier refer to spectrum. When we say carrier, it is usually understood as cell. So when we say carrier aggregation, each carrier (up to 20MHz in LTE) is a cell. By assigning multiple cells to a UE, it is provided with aggregation of spectrum. However, conventionally, even if adjacent carriers are provided to the UE, there are guard bands between cells to avoid spectrum leakage from a cell to another cell, because each cell operates independently.

[0249] The disclosed subject matter allows for the creation of a single wideband carrier by synthesizing multiple smaller frequency bands, provided that the node has channel access rights to those frequency bands. It is contemplated that a channel may indicate the frequency band(s) that a node desires to access - this may be narrowband or wideband. It is contemplated that the individual carriers used herein, particularly for composite carrier embodiments, are synthesized frequency bands.

[0250] With respect to LBT, if CAT4 is successful on a first adjacent band (e.g., a 20 MHz band), the transmitter performs CAT2 (e.g., 25 microseconds) on a second band (e.g., a 20 MHz band), and if successful, the first and second bands may be combined into a single carrier. In FR1, the band may correspond to the 20 MHz carrier used for unlicensed operation in WiFi and LTE-U. In the event that the UE determines that its network cannot access any of the multiple 20 MHz bands, it may freeze the bandwidth portion inactivity timer. It is contemplated that Fig.51 The subject matter and its description can be combined with the description associated with other figures in this document.

[0251] Note that conventionally performed carrier aggregation identifies each carrier as a cell and has signaling for each carrier. For example, in FR1, LTE-U uses each 20MHz band as a carrier and can aggregate it into an SCell. It also requires more device processors than the disclosed carrier synthesis disclosed herein. Carrier synthesis as described provides multiple bands or carriers to be identified as a cell for wireless communication between devices. This can result in reduced signaling overhead, higher spectral efficiency by eliminating guard spectrum between adjacent bands, and reduced burden on device processors.

[0252] Table 3 includes abbreviations and definitions for some of the subject matter disclosed herein.

[0253] Table 3 - Abbreviations and definitions

[0254]

[0255]

[0256]

[0257] It should be understood that performing the steps shown herein (such as Figure 9-12 Figure 19 Fig.28 , Fig.30 , Fig.36 , Fig.39 , Fig.41 The entities of the steps in the above example can be logical entities. These steps can be stored in a device, server or computer system (such as Fig.43F or Figure 43G ) in a memory and executed on a processor of a device, server, or computer system. It is contemplated that in the exemplary methods disclosed herein (e.g., Figure 9-12 Figure 19 Fig.28 , Fig.30 , Fig.36 , Fig.39 , Fig.41 You can skip steps, combine steps, or add steps between steps (such as , etc.).

[0258] Fig.42An exemplary display (e.g., a graphical user interface) that can be generated based on the methods and systems for channelization and BWP as discussed herein is illustrated. A display interface 901 (e.g., a touch screen display) can provide text associated with channelization and BWP in box 902, such as whether the WLBT was successful. The progress of any step discussed herein (e.g., a message sent or the success of a step) can be displayed in box 902. In addition, a graphical output 902 can be displayed on the display interface 901. A graphical output 903 can be a topology of devices implementing the methods and systems for channelization and BWP, a graphical output of the progress of any method or system discussed herein, etc.

[0259] The Third Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication network technologies, including radio access, core transport networks, and service capabilities - including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced standards, and New Radio (NR), also referred to as "5G". Development of the 3GPP NR standards is expected to continue and include the definition of next generation radio access technologies (new RATs), which are 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. Flexible radio access is expected to include new, non-backwards compatible radio access in new spectrum below 6 GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide set of 3GPP NR use cases with different requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum, which will provide opportunities for ultra-mobile broadband access for, for example, indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with sub-7 GHz flexible radio access, with cmWave- and mmWave-specific design optimizations.

[0260] 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 rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (eMBB) ultra-reliable low-latency communications (URLLC), massive machine-type communications (mMTC), network operations (e.g., network slicing, routing, migration and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications (which may include vehicle-to-vehicle communications (V2V), vehicle-to-infrastructure communications (V2I), vehicle-to-network communications (V2N), vehicle-to-pedestrian communications (V2P), and any of vehicle communications with other entities). Specific services and applications in these categories include, for example, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, car emergency calls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, home automation, robotics, and aerial drones, among others. All of these use cases and others are contemplated herein.

[0261] Fig.43A An example communication system 100 is illustrated in which methods, systems, and apparatus (e.g., UE or gNB) for channelization and BWP may be used, such as the examples shown in FIGS. 2 to 22 described and claimed herein. The communication system 100 may include a wireless transmit / receive unit (WTRU) 102a, 102b, 102c, 102d, 102e, 102f, or 102g (generally or collectively referred to as a WTRU 102 or multiple WTRUs 102). The communication 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. The network services 113 may include, for example, a V2X server, a V2X function, a ProSe server, a ProSe function, an IoT service, video streaming, or edge computing, etc.

[0262] 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, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. Fig.43A , Fig.43B , Fig.43C , Fig.43D , Fig.43E or Fig.43F102a, 102b, 102c, 102d, 102e, 102f or 102g are depicted as handheld wireless communication devices, but it should be understood that for various use cases expected for 5G wireless communications, each WTRU may include or be implemented in any type of device or apparatus configured to transmit or receive wireless signals, and by way of example only, the device or apparatus includes a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronic product, a wearable device (such as a smart watch or smart clothing), a medical or e-health device, a robot, an industrial equipment, a drone, a vehicle (such as a car, bus, truck, train or airplane), etc.

[0263] The communication system 100 may also include a base station 114a and a base station 114b. Fig.43A In the example of , each base station 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. The base station 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 (e.g., the core network 106 / 107 / 109, the Internet 110, the network service 113, or other networks 112). Similarly, the base station 114b may be any type of device configured to wirelessly interface with at least one of the remote radio heads (RRHs) 118a, 118b, the transmission and reception points (TRPs) 119a, 119b, or the 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, the other networks 112, or the network services 113). The 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.

[0264] The TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRUs 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. The RSUs 120a and 120b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102e or 102f 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. By way of example, the base stations 114a, 114b may be base transceiver stations (BTSs), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, next generation Node Bs (gNodeBs), satellites, site controllers, access points (APs), wireless routers, and the like.

[0265] 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), a relay node, 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, an RNC, a relay node, etc. The base station 114a may be configured to transmit or receive wireless signals within a specific geographic area, 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 specific geographic area, which may be referred to as a cell (not shown) for methods, devices, and systems for channelization and BWP, as disclosed herein. Similarly, the base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, a 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 transceiver for each sector of the cell. In an example, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may therefore utilize multiple transceivers for each sector of the cell.

[0266] The base station 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).

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

[0268] The RRH 118a, 118b, TRP 119a, 119b or RSU 120a, 120b may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f via an air interface 115c / 116c / 117c, 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).

[0269] The WTRUs 102a, 102b, 102c, 102d, 102e, or 102f may communicate with each other, such as sidelink communications, via an air interface 115d / 116d / 117d, 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 / 116d / 117d may be established using any suitable radio access technology (RAT).

[0270] The communication 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, etc. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b, TRPs 119a, 119b and RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) or High Speed ​​Uplink Packet Access (HSUPA).

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

[0272] The base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c and 102g or the RRHs 118a, 118b, TRPs 119a, 119b or RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b may implement a radio technology 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) etc.

[0273] For example, Fig.43A The base station 114c in may be a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area (such as a business place, a house, a vehicle, a train, an antenna, a satellite, a factory, a campus, etc.) for implementing methods, systems, and devices for channelization and BWP as disclosed herein. In an example, the base station 114c and the WTRU 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 WTRU 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 WTRU 102 (e.g., WTRU 102e) may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a microcell or a femtocell. As Fig.43A As shown in FIG, the base station 114c may have a direct connection to the Internet 110. Therefore, the base station 114c may not be required to access the Internet 110 via the core network 106 / 107 / 109.

[0274] The RAN 103 / 104 / 105 or RAN 103b / 104b / 105b may be in communication with a 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).

[0275] Although not in Fig.43A 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 utilize an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) that employs a GSM or NR radio technology.

[0276] 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 a circuit-switched telephone network that provides 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), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet Protocol suite. The networks 112 may include wired or wireless communication 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 the RAN 103b / 104b / 105b or a different RAT.

[0277] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may include multi-mode capabilities, for example, the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks over different wireless links to implement the methods, systems, and devices for channelization and BWP as disclosed herein. For example, Fig.43A The WTRU 102g shown in FIG. 1 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.

[0278] Although in Fig.43A 106 / 107 / 109. It will be appreciated that many of the concepts contained herein are equally applicable to a UE that is a WTRU and a UE that uses a wired connection to connect to a network. For example, concepts applicable to wireless interfaces 115, 116, 117, and 115c / 116c / 117c are equally applicable to wired connections.

[0279] Fig.43B 1 is a system diagram of an example RAN 103 and core network 106 that may implement the methods, systems, and apparatus for channelization and BWP as disclosed herein. As described above, the RAN 103 may employ 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. Fig.43B As shown in FIG. 1 , 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).

[0280] like Fig.43BAs shown in , Node B 140a, 140b can communicate with RNC 142a. In addition, Node B 140c can communicate with RNC 142b. Node B 140a, 140b and 140c can communicate with corresponding RNC 142a and 142b via Iub interface. RNC 142a and 142b can communicate with each other via Iur interface. Each of RNC 142a and 142b can be configured to control the corresponding Node B 140a, 140b and 140c to which it is connected. In addition, each of RNC 142a and 142b can be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security function, data encryption, etc.

[0281] Fig.43B The core network 106 shown in FIG. 1 may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, or a gateway GPRS support node (GGSN) 150. Although each of the aforementioned elements is depicted as part of the core network 106, it will be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.

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

[0283] 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 the WTRUs 102a, 102b, and 102c and IP-enabled devices.

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

[0285] Fig.43C1 is a system diagram of an example RAN 104 and a core network 107 that may implement the methods, systems, and apparatus for channelization and BWP as disclosed herein. As described 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.

[0286] The RAN 104 may include eNode-Bs 160a, 160b, and 160c, although 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, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0287] 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, user scheduling in uplink or downlink, etc. Fig.43C As shown in FIG, eNode-Bs 160a, 160b, and 160c may communicate with each other via an X2 interface.

[0288] Fig.43C The core network 107 shown in FIG. 1 may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the aforementioned elements is depicted as part of the core network 107, it should be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.

[0289] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 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, etc. 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.

[0290] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 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 a user plane during an inter-eNode B handover, 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.

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

[0292] 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 acts 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 owned or operated by other service providers.

[0293] Fig.43D 1 is a system diagram of an example RAN 105 and a core network 109 that may implement the methods, systems, and devices for channelization and BWP as disclosed herein. The RAN 105 may employ 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 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.

[0294] The RAN 105 may include gNode-Bs 180a and 180b. 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 an integrated access and backhaul connection is used, the same air interface may be used between the WTRUs and the gNode-Bs, which may be a core network 109 via one or more gNBs. The gNode-Bs 180a and 180b may implement MIMO, MU-MIMO, or digital beamforming techniques. Thus, for example, the gNode-B 180a 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 other types of base stations, such as an eNode-B. It should also be appreciated that the RAN 105 may employ more than one type of base station. For example, RAN may employ eNode-B and gNode-B.

[0295] 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 WTRU 102c over the air interface 198. The non-3GPP access point 180c may communicate with the WTRU 102c over the air interface 198 using the 802.11 protocol.

[0296] 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, user scheduling in uplink or downlink, etc. Fig.43D As shown in , for example, gNode-Bs 180a and 180b may communicate with each other via an Xn interface.

[0297] Fig.43D The core network 109 shown in the figure may be a 5G core network (5GC). The core network 109 may provide a variety of communication services to customers interconnected by a radio access network. The core network 109 includes multiple entities that perform the functions of the core network. As used herein, the term "core network entity" or "network function" refers to any entity that performs one or more functions of the core network. It should be understood that such a core network entity may be a device or computer system (such as a 5G core network) stored in a device or computer system configured for wireless or network communications. Figure 43G A logical entity implemented in the form of computer-executable instructions (software) stored in a memory of the system 90 shown in FIG. 1 and executed on a processor thereof.

[0298] exist Fig.43D In the example of , the 5G core network 109 may include access and mobility management function (AMF) 172, session management function (SMF) 174, user plane function (UPF) 176a and 176b, user data management function (UDM) 197, authentication server function (AUSF) 190, network exposure function (NEF) 196, policy control function (PCF) 184, non-3GPP interworking function (N3IWF) 199, user data repository (UDR) 178. Although each of the aforementioned elements is depicted as part of the 5G core network 109, it should be recognized that any of these elements may be owned or operated by an entity other than the core network operator. It will also be recognized that the 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.43D The network functions are shown connected directly to each other, however, it should be appreciated that they may communicate via a routing agent such as the Diameter routing agent or a message bus.

[0299] exist Fig.43D In the example of , the connectivity between network functions is achieved via a set of interfaces or reference points. It will be appreciated that a network function can be modeled, described or implemented as a set of services that are called or invoked by other network functions or services. The invocation of a network function service can be achieved via a direct connection between network functions, an exchange of messaging on a message bus, calling a software function, etc.

[0300] 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 for forwarding user plane tunnel configuration information to the RAN 105 via the N2 interface. The AMF 172 may receive user plane tunnel configuration information from the SMF via the N11 interface. The AMF 172 may generally route and forward NAS packets to / from the WTRUs 102a, 102b, and 102c via the N1 interface. The N1 interface is not used in Fig.43D Shown in.

[0301] 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 UPFs 176a and 176b, and generation of downlink data notifications to the AMF 172.

[0302] The UPF 176a and UPF 176b may provide the WTRUs 102a, 102b, and 102c with access to a packet data network (PDN), such as the Internet 110, to facilitate communication 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, the other network 112 may be an Ethernet network 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 an N4 interface. The UPF 176a and UPF 176b may provide access to a packet data network by connecting the packet data network to an N6 interface or by connecting to each other and to other UPFs via an N9 interface. In addition to providing access to the packet data network, UPF 176 may also be responsible for packet routing and forwarding, policy rule enforcement, quality of service handling of user plane traffic, and downlink packet buffering.

[0303] The AMF 172 may also be connected to the N3IWF 199, for example, via an N2 interface. The N3IWF facilitates connectivity between the WTRU 102c and the 5G core network 170, for example, via a 3GPP undefined radio interface technology. The AMF may interact with the N3IWF 199 in the same or similar manner as it interacts with the RAN 105.

[0304] PCF 184 may be connected to SMF 174 via an N7 interface, may be connected to AMF 172 via an N15 interface, and may be connected to application function (AF) 188 via an N5 interface. The N15 and N5 interfaces are not Fig.43D1. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, thereby allowing the control plane nodes to enforce the rules. The PCF 184 may send the policy for the WTRUs 102a, 102b, and 102c to the AMF 172 so that the AMF may deliver the policy to the WTRUs 102a, 102b, and 102c via the N1 interface. The policy may then be enforced or applied at the WTRUs 102a, 102b, and 102c.

[0305] The UDR 178 may act as a repository for authentication credentials and subscription information. The UDR may be connected to network functions so that the network functions may add to, read, and modify data in the repository. For example, the UDR 178 may be connected to the PCF 184 via an N36 interface. Similarly, the UDR 178 may be connected to the NEF 196 via an N37 interface, and the UDR 178 may be connected to the UDM 197 via an N35 interface.

[0306] 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 the UDR 178. For example, the UDM 197 may be connected to the AMF 172 via the N8 interface, and the UDM 197 may be connected to the SMF 174 via the N10 interface. Similarly, the UDM 197 may be connected to the AUSF 190 via the N13 interface. The UDR 178 and the UDM 197 may be tightly integrated.

[0307] The AUSF 190 performs operations related to authentication and is connected to the UDM 178 via the N13 interface and to the AMF 172 via the N12 interface.

[0308] NEF 196 exposes the capabilities and services in the 5G core network 109 to the application function (AF) 188. The exposure can occur on the N33 API interface. NEF can be connected to AF 188 via the N33 interface and it can be connected to other network functions to expose the capabilities and services of the 5G core network 109.

[0309] The application function 188 may interact with the network function in the 5G core network 109. The interaction between the application function 188 and the network function may occur via a direct interface or may occur via the NEF 196. The application function 188 may be considered part of the 5G core network 109 or may be external to the 5G core network 109 and deployed by an enterprise having a business relationship with a mobile network operator.

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

[0311] 3GPP has designed the 5G core network to support network slicing. Network slicing is a great tool that network operators can use to support a diverse set of 5G use cases (e.g., massive IoT, critical communications, V2X, and enhanced mobile broadband) that have very diverse and sometimes extreme requirements. Without using network slicing technology, the network architecture may not be flexible and scalable enough to efficiently support a wide range of use case requirements when each use case has its own specific set of performance, scalability, and availability requirements. In addition, the introduction of new network services should be made more efficient.

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

[0313] 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 the PSTN 108. For example, the core network 109 may include or communicate with a short message service (SMS) service center, which facilitates communication via 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 a server or application function 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 owned or operated by other service providers.

[0314] This article describes and Fig.43A , Fig.43C , Fig.43D or Fig.43E The core network entities shown in the figure are identified by the names given to those entities in certain existing 3GPP specifications, but it will be appreciated that those entities and functions may be identified by other names in the future, and that certain entities or functions may be combined in future specifications published by 3GPP (including future 3GPP NR specifications). Fig.43A , Fig.43B , Fig.43C , Fig.43D or Fig.43E Although specific network entities and functionality are described and illustrated in the specification, it should be understood that the subject matter disclosed and claimed herein may be implemented or realized in any similar communication system, whether currently defined or defined in the future.

[0315] Fig.43E An example communication system 111 is illustrated in which the systems, methods, and apparatus described herein for implementing channelization and BWP may be used. The communication 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 roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein may be applied to any number of WTRUs, base stations gNBs, V2X networks, or other network elements. One or several or all WTRUs A, B, C, D, E, and F may be outside the range of access network coverage 131. WTRUs A, B, and C form a V2X group, where WTRU A is the group leader and WTRUs B and C are group members.

[0316] If WTRUs A, B, C, D, E, and F are within access network coverage 131, they may communicate with each other via gNB 121 over the Uu interface 129. Fig.43E In the example of , WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F may communicate directly to each other via a sidelink interface (e.g., PC5 or NR PC5) such as interface 125a, 125b, or 128 whether they are within or outside of access network coverage 131. For example, in Fig.43E In the example of , WTRU D outside the access network coverage 131 communicates with WTRU F inside the coverage 131.

[0317] WTRUs A, B, C, D, E, and F may communicate with the RSU 123a or 123b via the vehicle-to-network (V2N) 133 or the sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate with the V2X server 124 via the vehicle-to-infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F may communicate with another UE via the vehicle-to-person (V2P) interface 128.

[0318] Fig.43F is an example apparatus or device WTRU 102 (such as a WTRU 102) that may be configured for wireless communication and operation in accordance with the systems, methods, and apparatus for implementing channelization and BWP as described herein. Fig.43A , Fig.43B , Fig.43C , Fig.43D or Fig.43E 102, or a block diagram of a UE disclosed throughout the text (such as UE 361). Fig.43F As shown in , 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 / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 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, and that the base stations 114a and 114b or the nodes that the base stations 114a and 114b may represent (such as, but not limited to, a 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) (e.g., gNB 360), and a proxy node, etc.) may include Fig.43F Some or all of the elements depicted in and may be exemplary implementations of the disclosed methods for channelization and BWP described herein.

[0319] 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 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. Although Fig.43F The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0320] The transmit / receive element 122 of the UE may be configured to transmit data to a base station (eg, Fig.43A The transmit / receive element 122 may be a base station 114a) of a wireless communication network, or may transmit or receive signals to or from another UE via an air interface 115d / 116d / 117d. For example, the transmit / receive element 122 may be an antenna configured to transmit or receive RF signals. The transmit / receive element 122 may be a transmitter / detector configured to transmit or receive IR, UV, or visible light signals, for example. The transmit / receive element 122 may be configured to transmit and receive both RF and optical 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.

[0321] In addition, although the transmit / receive element 122 is Fig.43F Although depicted as a single element in the figure, 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.

[0322] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., 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.

[0323] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, or the display / touchpad / indicator 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a 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, etc. The processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server hosted in a cloud or edge computing platform or in a home computer (not shown). The processor 118 may be configured to control a lighting pattern, image, or color on the display or indicator 128 in response to whether the channelization and BWP are working as expected in some examples described herein, or otherwise indicate the status of the associated components. The control lighting pattern, image, or color on the display or indicator 128 may reflect the diagrams illustrated or discussed herein (e.g., Figure 9-12 , FIG. 19 , etc.) of any method flow or component state. Disclosed herein are messages and processes for channelization and BWP. The messages and processes may be extended to provide an interface / API for a user to request resources via an input source (e.g., speaker / microphone 124, keypad 126, or display / touchpad / indicator 128), and to request, configure, or query information related to channelization and BWP, etc., which may be displayed on display 128.

[0324] The processor 118 may receive power from the power source 134 and may be configured to distribute or control the power to 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, etc.

[0325] 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 from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117, or determine its location based on the timing of receiving signals from two or more base stations in the vicinity. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method.

[0326] The processor 118 may also 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 accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), universal serial bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.

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

[0328] Figure 43G is a block diagram of an exemplary computing system 90 in which Fig.43A , Fig.43C , Fig.43D and Fig.43EOne or more devices of the communication network shown in and channelization and BWP (such as the systems and methods described and claimed herein), such as core network 106 / 107 / 109, PSTN 108, Internet 110, other networks 112, network services 113 or certain nodes or functional entities in RAN103 / 104 / 105. The computing system 90 may include a computer or server and may be primarily controlled by computer-readable instructions, which may be in the form of software, wherever, whenever, or by any means to store or access such software. Such computer-readable instructions may be executed within a processor 91 to enable the computing system 90 to operate. 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 associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables the computing system 90 to operate in a communication 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 apparatus for channelization and BWP disclosed herein, such as the success of WLBT.

[0329] 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 components in computing system 90 and defines a 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 bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.

[0330] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memory includes a circuit system that allows information to be stored and retrieved. ROM 93 generally contains stored data that is not easily modified. The data stored in RAM 82 can be read or changed by a processor 91 or other hardware device. Access to RAM 82 or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address translation function that translates a virtual address into a physical address when an instruction is executed. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Therefore, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes has been set up, it cannot access memory within the virtual address space of another process.

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

[0332] The display 86 controlled by the display controller 96 is used to display the visual output generated by the 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). The display 86 may be implemented with a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch pad. The display controller 96 includes the electronic components required to generate the video signal sent to the display 86.

[0333] In addition, the computing system 90 may include communication circuitry, such as, for example, a wireless or wired network adapter 97, which may be used to connect the computing system 90 to an external communication network or device (such as the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110, the WTRU 102, or Fig.43A , Fig.43B , Fig.43C , Fig.43D or Fig.43E Other networks 112) to enable computing system 90 to communicate with other nodes or functional entities of those networks. Alone or in combination with processor 91, the communication circuit system can be used to perform the transmission and reception steps of certain devices, nodes or functional entities described herein.

[0334] It should be understood that any or all of the devices, systems, methods, and processes described herein may be implemented in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), causes the processor to perform or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein may be implemented in the form of such computer executable instructions executed on a processor of a device or computing system configured for wireless or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any non-transient (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassette, tape, disk storage or other magnetic storage device, or any other tangible or physical medium that can be used to store desired information and can be accessed by a computing system.

[0335] In describing the preferred methods, systems or apparatus of the subject matter of the present disclosure (channelization and BWP) as shown in the figures, specific terminology is employed for the sake of clarity. However, the claimed subject matter is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to achieve a similar purpose.

[0336] The user equipment can share the channel occupation time with the transmitter and transmit data to the transmitter after successful CAT2 channel sensing on a frequency band spanning its data resources. The UE can transmit UL PUSCH within the COT obtained by the gNB because gNB allows UEs to share COT. The UE then performs short LBT (CAT2). If successful, then it can transmit. This claim provides the frequency at which the UE performs LBT. The UE can perform LBT on a frequency band covering UL PUSCH resources.

[0337] The various techniques described herein can be implemented in combination with hardware, firmware, software or in combination thereof when appropriate. Such hardware, firmware and software can reside in the device at each node of the communication network. The device can be operated individually or in combination with each other to implement the method described herein. As used herein, the terms "device", "network device", "node", "equipment", "network node" etc. can be used interchangeably. In addition, unless otherwise provided herein, the use of the word "or" is generally used inclusively.

[0338] This written description uses examples to disclose the present invention, including the best mode, and also enables any person skilled in the art to practice the present invention, including making and using any device or system and performing any combined method. The patentable scope of the present invention is defined by the claims, and may include other examples that occur to a person skilled in the art (e.g., skipping steps, combining steps, or adding steps between the exemplary methods disclosed herein). If such other examples have structural elements that are not different from the literal language of the claims, or if they include equivalent structural elements that are not substantially different from the literal language of the claims, then it is intended that these other examples be included within the scope of the claims. The subject matter described herein for anchor carriers may be applicable to deployments based on non-anchor carriers. Similarly, the subject matter described herein for non-anchor based may be applicable to deployments based on anchor carriers. For example, this concept of indicating 20MHz in a carrier may be applicable to both cases. The method of indicating it (such as the bitmap in FIG. 4) may be applicable to both cases. Again, the subject matter described may be seen in the context of the respective case, but is applicable to both cases.

[0339] Methods, systems, and apparatus as described herein, among other things, may provide means for performing wireless communications. A method, system, computer-readable storage medium, or apparatus having means for: determining that a channel is available based on an indication of a composite carrier indicator (CCI); and based on determining that the channel is available, dynamically increasing bandwidth by adding attachments to an anchor cell; monitoring a first anchor and a second anchor to obtain a composite carrier indicator (CCI); when the CCI is obtained in the first anchor, increasing bandwidth on a first receive chain when a first cell with attachments for a second anchor is required to be received; and not monitoring the second cell on a second receive chain until the first cell grant is completed or the first cell releases attachments for the second anchor. The apparatus may be a base station or a user equipment. A method, system, computer-readable storage medium, or apparatus having means for: sensing a channel; based on the sensing, determining that the channel is available in a plurality of frequency bands; based on determining that the channel is available in a plurality of frequency bands, combining the plurality of frequency bands into a composite carrier; generating a composite carrier indicator (CCI) indicating one or more of the plurality of frequency bands within the composite carrier; transmitting the CCI to a receiver. Each of the plurality of frequency bands may be 20Mhz. The composite carrier may be a wideband carrier. The device may be a base station, a user equipment, or other device. CCI may be obtained or transmitted via a preamble of a Zadoff-Chu sequence, downlink control information, an uplink grant, a downlink grant, or a radio resource control signaling. CCI may be obtained or transmitted via downlink control information of a UE-specific PDCCH or downlink control information of a group common PDCCH. Carriers may be synthesized only when the frequencies are adjacent. The method, system, computer-readable storage medium, or device has means for: determining that a category four listen-before-talk (LBT) is successful on a first carrier in a plurality of frequency bands; performing a category two LBT on a second carrier based on the category four LBT being successful on a first carrier in a plurality of frequency bands and the first carrier being adjacent to a second carrier; and synthesizing the first carrier and the second carrier into a composite carrier based on the category two LBT being successful. The method, system, computer-readable storage medium, or device has means for: determining that a base station has no right to access a first carrier; and suspending a bandwidth portion inactivity timer based on determining that a base station has no right to access a first carrier. A method, system, computer readable storage medium or apparatus having means for obtaining channel access to a predefined anchor frequency band before synthesizing other frequency bands to form a composite carrier. If it cannot channel access the anchor frequency band, then it cannot form a composite carrier with other frequency bands that may be available during that channel access opportunity. A method, system, computer readable storage medium or apparatus having means for obtaining a composite carrier indicator (CCI) from a transmitter; based on the CCI, identifying the bandwidth of the composite carrier; performing measurement, transmission, reception or synchronization based on identifying one or more frequency bands in the composite carrier of the transmitter.The UE may receive knowledge of all or part of the frequency bands of the gNB and perform processes (e.g., transmission, reception, etc.) on those frequency bands. The user equipment may share channel occupancy time with the transmitter and transmit data to the transmitter after successful CAT2 channel sensing on a frequency band spanning its data resources. The user equipment may share channel occupancy time with the transmitter and transmit data to the transmitter after successful CAT2 channel sensing on a frequency band spanning its BWP. The user equipment may share channel occupancy time with the transmitter and transmit data to the transmitter after successful CAT2 channel sensing that does not exceed the composite carrier bandwidth of the transmitter. All combinations in this paragraph (including removal or addition of steps) are contemplated in a manner consistent with other portions of the detailed description.

Claims

1. A wireless transmit / receive unit (WTRU) comprising a processor and a memory, wherein the processor and the memory are configured to: Sensing channel; Based on the sensing, determining that the channel is available; generating a composite carrier indicator (CCI); and Transmits CCI to the receiver.

2. A wireless transmit / receive unit (WTRU) comprising a processor and a memory, the processor and the memory being configured to: receiving a composite carrier indicator (CCI) from a network node; determining one or more frequency bands based on the CCI; determining that a listen-before-talk (LBT) process is successful on the one or more frequency bands; as well as Uplink transmissions are sent via the one or more frequency bands.

3. The WTRU of claim 1 , wherein the CCI is transmitted via downlink control information of a physical downlink control channel (PDCCH).

4. The WTRU of claim 1, wherein the processor and memory are further configured to determine that Category Four (CAT4) Listen Before Talk (LBT) is successful on a frequency band.

5. The WTRU of claim 2, wherein the CCI is conveyed via downlink control information transmitted via a physical downlink control channel (PDCCH).

6. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: Sensing channel; Based on the sensing, determining that the channel is available; Generate a composite carrier indicator (CCI); as well as Transmits CCI to the receiver.

7. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving a composite carrier indicator (CCI) from a network node; determining one or more frequency bands based on the CCI; determining that a listen-before-talk (LBT) process is successful on the one or more frequency bands; as well as Uplink transmissions are sent via the one or more frequency bands.

8. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving a bandwidth part (BWP) from a network node, wherein the BWP includes a grant; Switching to the active other BWP for Physical Downlink Shared Channel (PDSCH) transmission; as well as When the authorization is complete, return to BWP.

9. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving an active anchor bandwidth part (BWP) from a network node, wherein the BWP includes a grant; monitoring said authorization in the active anchor BWP; Switching to the active other BWP for Physical Downlink Shared Channel (PDSCH) transmission; When the authorization is completed, return to the activity anchor BWP.

10. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving an active anchor bandwidth part (BWP) from a network node, wherein the BWP includes a grant; as well as When it is determined that the BWP is less than or equal to the threshold, listen before talk (LBT) is performed.