CN116746103A - Configuration for narrowband wireless communications - Google Patents

Abstract

Aspects relate to one or more configurations for wireless communication via a Radio Frequency (RF) band. A User Equipment (UE) and a Base Station (BS) may support communication on a first RF band. A first minimum bandwidth size may be defined for the first RF band. The first minimum bandwidth size may be less than a second minimum bandwidth size defined for a second RF band available to the UE. The UE and the BS may each communicate via the first RF band according to a first configuration based on the first minimum bandwidth size.

Description

Configuration for narrowband wireless communications

Cross Reference to Related Applications

The present application claims priority and benefit from non-provisional application No. 17/564,835, entitled "configuration for narrowband wireless communications (CONFIGURATIONS FOR NARROWBAND WIRELESS COMMUNICATION)" filed on 12/29 of 2021. The priority and benefit of provisional application No. 63/143,419, entitled "configuration for narrowband wireless communications (CONFIGURATIONS FOR NARROWBAND WIRELESS COMMUNICATION)" filed on 1 month 29 of 2021, which is assigned to the assignee of the present application and is expressly incorporated herein by reference as if fully set forth below and for all applicable purposes.

Technical Field

The techniques discussed below relate generally to wireless communications and, more particularly, relate to configurations using one or more definitions for narrowband wireless communications.

Background

The next generation wireless communication system (e.g., 5 GS) may include a 5G core network and a 5G Radio Access Network (RAN), such as a New Radio (NR) -RAN. The NR-RAN supports communication via one or more cells. For example, a wireless communication device, such as a User Equipment (UE), may access a first cell, such as a first Base Station (BS) of a gNB, and/or access a second cell of a second base station.

The base station may schedule access to the cell to support access by multiple UEs. For example, the base station may allocate different resources (e.g., time domain and frequency domain resources) for different UEs operating within the cell of the base station. The base station may provide services on one or more Radio Frequency (RF) bands. For example, one cell served by a base station may be on one RF band, while another cell served by the base station may be on another RF band.

Disclosure of Invention

The following presents a simplified summary of one or more aspects of the disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the disclosure, and is intended to neither identify key or critical elements of all aspects of the disclosure nor delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a form as a prelude to the more detailed description that is presented later.

In some examples, a user device may include: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: receiving an indication that the base station supports a first Radio Frequency (RF) band; and communicate with the base station via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band. In some examples, the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user device.

In some examples, a method for wireless communication at a user device may include: receiving an indication that the base station supports a first Radio Frequency (RF) band; and communicate with the base station via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band. In some examples, the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user device.

In some examples, a user device may include: means for receiving an indication that a base station supports a first Radio Frequency (RF) band; and means for communicating with the base station via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band. In some examples, the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user device.

In some examples, an article of manufacture for use by a user device includes a non-transitory computer-readable medium having instructions stored therein, the instructions executable by one or more processors of the user device to: receiving an indication that the base station supports a first Radio Frequency (RF) band; and communicate with the base station via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band. In some examples, the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user device.

In some examples, a base station may include: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: transmitting an indication that the base station supports a first Radio Frequency (RF) band; and communicate with the user device via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band. In some examples, the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user device.

In some examples, a method for wireless communication at a base station may include: transmitting an indication that the base station supports a first Radio Frequency (RF) band; and communicate with the user device via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band. In some examples, the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user device.

In some examples, a base station may include: means for transmitting an indication that the base station supports a first Radio Frequency (RF) band; and means for communicating with a user device via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band. In some examples, the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user device.

In some examples, an article of manufacture for use by a base station includes a non-transitory computer-readable medium having instructions stored therein, the instructions executable by one or more processors of the base station to: transmitting an indication that the base station supports a first Radio Frequency (RF) band; and communicate with the user device via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band. In some examples, the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user device.

These and other aspects of the disclosure will be more fully understood upon reading the following detailed description. Other aspects, features, and examples of the present disclosure will become apparent to those of ordinary skill in the art upon review of the following description of specific exemplary aspects of the disclosure in conjunction with the accompanying drawings. While features of the present disclosure may be discussed with respect to certain examples and figures below, all examples of the present disclosure may include one or more of the advantageous features discussed herein. In other words, while one or more examples may be discussed as having certain advantageous features, one or more of these features may also be used in accordance with various examples of the disclosure discussed herein. In a similar manner, although example aspects may be discussed below as device, system, or method examples, it should be understood that such example aspects may be implemented in a variety of devices, systems, and methods.

Drawings

Fig. 1 is a schematic illustration of a wireless communication system in accordance with some aspects.

Fig. 2 is a conceptual illustration of an example of a radio access network according to some aspects.

Fig. 3 is a diagram illustrating an organization of radio resources in an air interface utilizing Orthogonal Frequency Division Multiplexing (OFDM), in accordance with some aspects.

Fig. 4A is a diagram illustrating an example of a frame structure for a synchronization signal in a wireless communication network, according to some aspects.

Fig. 4B is a diagram illustrating an example of a portion of a frame or subframe structure with various channels and associated messages for use in a wireless communication network, in accordance with some aspects.

Fig. 5 is a signaling diagram of an example of Random Access Channel (RACH) signaling in accordance with some aspects.

Fig. 6 is a conceptual illustration of an example of a narrow radio frequency band according to some aspects.

Fig. 7 is a conceptual illustration of another example of a narrow radio frequency band according to some aspects.

Fig. 8 is a flow chart illustrating an example of a method for narrowband downlink communications by a user equipment, in accordance with some aspects.

Fig. 9 is a flow chart illustrating an example of a method for narrowband uplink communications by a user equipment, in accordance with some aspects.

Fig. 10 is a flow chart illustrating an example of a method for narrowband random access communication by a user equipment, in accordance with some aspects.

Fig. 11 is a flow chart illustrating an example of a method for narrowband downlink communications by a base station, in accordance with some aspects.

Fig. 12 is a flow chart illustrating an example of a method for narrowband uplink communications by a base station, in accordance with some aspects.

Fig. 13 is a flow chart illustrating an example of a method for narrowband random access communication by a base station, in accordance with some aspects.

Fig. 14 is a flow chart illustrating an example of a method for narrowband wireless communications by a user equipment, in accordance with some aspects.

Fig. 15 is a flow chart illustrating an example of a method for narrowband wireless communications by a base station, in accordance with some aspects.

Fig. 16 is a block diagram illustrating an example of a hardware implementation of a user device employing a processing system in accordance with some aspects.

Fig. 17 is a flow diagram illustrating an example method for narrowband wireless communication with a base station, in accordance with some aspects.

Fig. 18 is a flow diagram illustrating another example method for narrowband wireless communication with a base station, in accordance with some aspects.

Fig. 19 is a flow chart illustrating another example method for narrowband wireless communication with a base station, in accordance with some aspects.

Fig. 20 is a block diagram illustrating an example of a hardware implementation of a base station employing a processing system in accordance with some aspects.

Fig. 21 is a flow diagram illustrating an example method for narrowband wireless communication with a user equipment, in accordance with some aspects.

Fig. 22 is a flow diagram illustrating another example method for narrowband wireless communication with a user equipment, in accordance with some aspects.

Fig. 23 is a flow diagram illustrating another example method for narrowband wireless communication with a user equipment, in accordance with some aspects.

Detailed Description

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for providing a thorough understanding of various concepts. It will be apparent, however, to one skilled in the art that the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

While aspects and examples are described in this disclosure by way of illustration of some examples, those skilled in the art will appreciate that additional embodiments and use cases may occur in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and/or uses may be implemented via integrated chip examples and other non-module component based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI-enabled) devices, etc.). While some examples may or may not be specific to use cases or applications, various applicability of the described innovations may occur. Embodiments may range from chip-level or modular components to non-modular, non-chip-level embodiments, and further to aggregate, distributed, or Original Equipment Manufacturer (OEM) devices or systems that include one or more aspects of the described innovations. In some practical arrangements, a device incorporating the described aspects and features may also necessarily include additional components and features to implement and practice the claimed and described examples. For example, the transmission and reception of wireless signals necessarily includes a plurality of components for analog and digital purposes (e.g., hardware components including antennas, radio Frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders/summers, etc.). The innovations described herein are intended to be practiced in a variety of different size, shape, and configuration devices, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and/or UEs), end-user devices, and the like.

The present disclosure relates in some aspects to one or more configurations for wireless communication via a Radio Frequency (RF) band. Conventional wireless communication systems may use a relatively wide RF band (e.g., 5 megahertz (MHz) or more). Further, these wireless communication systems may use a nominal bandwidth portion (BWP) size of 5 MHz.

The present disclosure relates in some aspects to wireless communications over a narrower RF band (e.g., less than 4 MHz). In this case, the base station and the user equipment may use different communication configurations on the narrower RF band than on the wider RF band. For example, communication of uplink signals and/or downlink signals may be based on a smaller minimum BWP size (e.g., 3.6 MHz).

The present disclosure relates in some aspects to base stations and user equipment that disable one or more features when communicating over a narrower RF band. For example, for narrowband communications, the base station and user equipment may disable one or more of particular reference signals, modulation and coding schemes, frequency hopping, random access frequency division multiplexing, random access formats, or combinations thereof.

The various concepts presented throughout this disclosure may be implemented in a wide variety of telecommunication systems, network architectures, and communication standards. Referring now to fig. 1, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as a non-limiting illustrative example. The wireless communication system 100 includes three interaction domains: a core network 102, a Radio Access Network (RAN) 104, and a User Equipment (UE) 106. With the aid of the wireless communication system 100, the ue 106 is capable of performing data communication with an external data network 110, such as, but not limited to, the internet.

RAN 104 may implement any suitable wireless communication technology to provide radio access to UEs 106. As one example, RAN 104 may operate in accordance with a third generation partnership project (3 GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and evolved universal terrestrial radio access network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). The 3GPP refers to this hybrid RAN as the next generation RAN or NG-RAN. In another example, RAN 104 may operate in accordance with both LTE and 5G NR standards. Of course, many other examples may be used within the scope of the present disclosure.

As illustrated, the RAN 104 includes a plurality of base stations 108. Broadly, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be referred to variously by those skilled in the art as a base station transceiver (BTS), a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), an Access Point (AP), a Node B (NB), an eNodeB (eNB), a gndeb (gNB), a Transmission and Reception Point (TRP), or some other suitable terminology. In some examples, a base station may include two or more TRPs that may or may not be co-located (co-located). Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In examples where RAN 104 operates in accordance with both LTE and 5G NR standards, one of base stations 108 may be an LTE base station and the other base station may be a 5G NR base station.

The radio access network 104 is further illustrated as supporting wireless communications for a plurality of mobile devices. A mobile device may be referred to in the 3GPP standards as a User Equipment (UE) 106, but may also be referred to by those skilled in the art as a Mobile Station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an Access Terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. The UE 106 may be a device that provides a user with access to network services. In examples where RAN 104 operates in accordance with both LTE and 5G NR standards, UE 106 may be an evolved universal terrestrial radio access network-new radio dual connectivity (EN-DC) UE capable of simultaneously connecting to both an LTE base station and a NR base station to receive data packets from both the LTE base station and the NR base station.

Within this document, a mobile device need not have the capability to move, and may be stationary. The term "mobile device" or "mobile apparatus" generally refers to an array of various devices and technologies. The UE may include a plurality of hardware structural components sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, and the like, electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile equipment, cellular (cell) phones, smart phones, session Initiation Protocol (SIP) phones, laptops, personal Computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal Digital Assistants (PDAs), and a wide array of embedded systems corresponding to, for example, the internet of things (IoT).

The mobile apparatus may also be an automobile or other transportation vehicle, a remote sensor or actuator, one or more robotic devices, satellite radio, global Positioning System (GPS) device, object tracking device, drone, multi-axis aircraft (multi-copter), quad-axis aircraft (quad-copter), remote control device, consumer and/or wearable device (such as glasses, wearable cameras, virtual reality devices, smart watches, health or fitness trackers), digital audio player (e.g., MP3 player), camera, game console, etc. The mobile device may also be a digital home or smart home device such as a home audio, video and/or multimedia device, appliance, vending machine, smart lighting, home security system, smart meter, etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling power (e.g., smart grid), lighting, water, etc., industrial automation and enterprise devices, logistics controllers, agricultural equipment, etc. Further, the mobile device may provide connected medical or telemedicine support, i.e., tele-healthcare. The telemedicine devices may include telemedicine monitoring devices and telemedicine management devices whose communications may be given preferential treatment or preferential access over other types of information, e.g., in terms of preferential access to communicate critical service data and/or in terms of communicating relevant QoS for the critical service data.

Wireless communication between RAN 104 and UE 106 may be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over an air interface may be referred to as Downlink (DL) transmissions. In some examples, the term downlink may refer to a point-to-multipoint transmission initiated at a base station (e.g., base station 108). Another way to describe the point-to-multipoint transmission scheme may be to use the term broadcast channel multiplexing. The transmission from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as an Uplink (UL) transmission. In some examples, the term uplink may refer to a point-to-point transmission initiated at a UE (e.g., UE 106).

In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. In the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs). That is, for scheduled communications, multiple UEs 106, which may be scheduled entities, may utilize resources allocated by a scheduling entity (e.g., base station 108).

The base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE may act as a scheduling entity that schedules resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE may communicate with other UEs in a peer-to-peer or device-to-device manner and/or in a relay configuration.

As shown in fig. 1, a scheduling entity (e.g., base station 108) may broadcast downlink traffic 112 to one or more scheduled entities (e.g., UEs 106). Broadly, a scheduling entity is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112, and in some examples, uplink traffic 116 and/or uplink control information 118 from one or more scheduled entities to the scheduling entity. On the other hand, the scheduled entity is a node or device that receives downlink control information 114, the downlink control information 114 including, but not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network, such as a scheduling entity.

Further, uplink control information 118, downlink control information 114, downlink traffic 112, and/or uplink traffic 116 may be time-divided into frames, subframes, slots, and/or symbols. As used herein, a symbol may refer to a unit of time in an Orthogonal Frequency Division Multiplexing (OFDM) waveform in which each subcarrier carries one Resource Element (RE). In some examples, a slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 millisecond (ms). Multiple subframes or slots may be grouped together to form a single frame or radio frame. Within this disclosure, frames may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, where each frame is comprised of 10 subframes, e.g., 1ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various temporal divisions of the waveforms may have any suitable duration.

In general, the base station 108 may include a backhaul interface for communicating with a backhaul 120 of a wireless communication system. Backhaul 120 may provide a link between base station 108 and core network 102. Further, in some examples, the backhaul network may provide interconnection between respective base stations 108. Various types of backhaul interfaces may be employed, such as direct physical connections using any suitable delivery network, virtual networks, and the like.

The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5 GC). In other examples, core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

Referring now to fig. 2, by way of example and not limitation, a schematic illustration of a Radio Access Network (RAN) 200 is provided. In some examples, RAN 200 may be the same as RAN 104 described above and illustrated in fig. 1.

The geographic area covered by the RAN 200 may be divided into cellular areas (cells) that may be uniquely identified by User Equipment (UE) based on an identification broadcast from one access point or base station. Fig. 2 illustrates cells 202, 204, 206, and 208, each of which may include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same base station. Radio links within a sector may be identified by a single logical identification belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by groups of antennas, with each antenna being responsible for communication with UEs in a portion of the cell.

Various base station arrangements may be utilized. For example, in fig. 2, two base stations 210 and 212 are shown in cells 202 and 204; the base station 214 is shown controlling a Remote Radio Head (RRH) 216 in the cell 206. In other words, the base station may have an integrated antenna or may be connected to an antenna or RRH through a feeder cable. In the example shown, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells having a large size. In addition, a base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, the cell 208 may be referred to as a small cell (e.g., a micro cell, pico cell, femto cell, home base station, home node B, home eNodeB, etc.) because the base station 218 supports cells having a relatively small size. Cell size determination may be made based on system design and component constraints.

It should be appreciated that RAN 200 may include any number of radio base stations and cells. Furthermore, relay nodes may be deployed to extend the size or coverage area of a given cell. The base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and/or 218 may be the same as the base station/scheduling entities described above and shown in fig. 1.

Fig. 2 also includes an Unmanned Aerial Vehicle (UAV) 220, which may be an unmanned aerial vehicle or a four-axis aircraft. UAV 220 may be configured to act as a base station, or more specifically as a mobile base station. That is, in some examples, the cells may not necessarily be stationary, and the geographic area of the cells may move according to the location of a mobile base station, such as UAV 220.

Within RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Further, each base station 210, 212, 214, and 218 may be configured to provide an access point to the core network 102 (see fig. 1) for all UEs in the respective cell. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 over RRH 216; and UE 234 may communicate with base station 218. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and/or 242 may be the same as the UEs/scheduled entities described above and illustrated in fig. 1. In some examples, UAV 220 (e.g., a four-axis vehicle) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

In another aspect of the RAN 200, side-uplink signals may be used between UEs without having to rely on scheduling or control information from the base station. The side-link communications may be used, for example, in a device-to-device (D2D) network, a peer-to-peer (P2P) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, and/or other suitable side-link networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using side-uplink signals 237 without relaying the communication through the base station. In some examples, UEs 238, 240, and 242 may each act as a scheduling entity or transmitting-side uplink device and/or a scheduled entity or receiving-side uplink device to schedule resources therebetween and communicate-side uplink signals 237 independent of scheduling or control information from the base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of a base station (e.g., base station 212) may also communicate sidelink signal 227 on a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources for side-link communications to UEs 226 and 228.

In the RAN 200, the ability of a UE to communicate independent of its location while moving is referred to as mobility. The various physical channels between the UE and the radio access network are typically established, maintained and released under control of an access and mobility management function (AMF, not shown, which is part of the core network 102 in fig. 1) which may include a Security Context Management Function (SCMF) that manages security contexts for control plane and user plane functionality, and a security anchor function (SEAF) that performs authentication.

RAN 200 may utilize DL-based mobility or UL-based mobility to effect mobility and handover (i.e., transfer the connection of the UE from one radio channel to another). In a network configured for DL-based mobility, a UE may monitor various parameters of signals from its serving cell and various parameters of neighboring cells during a call with a scheduling entity or at any other time. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another cell, or if the signal quality from the neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may make a handover or handoff from the serving cell to the neighboring (target) cell. For example, UE 224 (illustrated as a vehicle, although any suitable form of UE may be used) may move from a geographic region corresponding to its serving cell (e.g., cell 202) to a geographic region corresponding to a neighboring cell (e.g., cell 206). When the signal strength or quality from the neighboring cell exceeds the signal strength or quality of the serving cell for a given amount of time, UE 224 may send a report message to its serving base station (e.g., base station 210) indicating this condition. In response, UE 224 may receive the handover command and the UE may experience a handover to cell 206.

In a network configured for UL-based mobility, UL reference signals from each UE may be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214/216 may broadcast a unified synchronization signal (e.g., unified Primary Synchronization Signal (PSS), unified Secondary Synchronization Signal (SSS), and unified Physical Broadcast Channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signal, derive carrier frequencies and slot timing from the synchronization signal, and transmit uplink pilot or reference signals in response to the derived timing. Uplink pilot signals transmitted by a UE (e.g., UE 224) may be received simultaneously by two or more cells (e.g., base stations 210 and 214/216) within RAN 200. Each cell may measure the strength of the pilot signal and the radio access network (e.g., one or more of base stations 210 and 214/216 and/or a central node within the core network) may determine a serving cell for UE 224. As UE 224 moves through RAN 200, the network may continue to monitor the uplink pilot signals transmitted by UE 224. When the signal strength or quality of the pilot signal measured by the neighbor cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may handover the UE 224 from the serving cell to the neighbor cell with or without informing the UE 224.

Although the synchronization signals transmitted by the base stations 210, 212, and 214/216 may be uniform, the synchronization signals may not identify a particular cell, but may identify areas of multiple cells operating at the same frequency and/or having the same timing. The use of zones in a 5G network or other next generation communication network enables an uplink-based mobility framework and improves the efficiency of both the UE and the network, as the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

In various embodiments, the air interface in RAN 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides the exclusive use of a portion of spectrum by means of a mobile network operator purchasing a license from a government regulatory body. Unlicensed spectrum provides shared use of a portion of spectrum without the need for government-granted permissions. Access is generally available to any operator or device, although some technical rules still generally need to be complied with to access the unlicensed spectrum. The shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple Radio Access Technologies (RATs). For example, a licensed holder that licensed a portion of a spectrum may provide Licensed Shared Access (LSA) to share the spectrum with other parties (e.g., having appropriate licensee-determined conditions to gain access).

Electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be appreciated that although a portion of FR1 is greater than 6GHz, FR1 is commonly (interchangeably) referred to in various documents and articles as the "Sub-6 GHz (Sub-6 GHz)" frequency band. Similar naming problems sometimes occur for FR2, FR2 is often (interchangeably) referred to in the literature and articles as the "millimeter wave" frequency band, although it is different from the Extremely High Frequency (EHF) frequency band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" frequency band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band of these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics and may therefore effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating bands have been identified as frequency range names FR4-a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above, unless specifically stated otherwise, it should be understood that if the term "sub-6 GHz" or the like is used herein, it may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that the term "millimeter wave" or the like (if used herein) may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4-a or FR4-1 and/or FR5, or may be within the EHF band.

In some examples, a particular frequency value (e.g., 5MHz bandwidth, 3.6MHz bandwidth, etc.) or range of values (e.g., 410MHz-7.125 GHz) may be specified (e.g., by a wireless communication standard or regulatory agency). In some examples, the actual operating frequency of a wireless communication device (e.g., a UE or a base station) may be slightly different than the specified nominal value or values. For example, a wireless communication device configured to use a 5MHz bandwidth may transmit signals over a bandwidth slightly greater than or slightly less than 5 MHz. As used herein, references to a particular frequency value or range of values should be understood to include small variations (e.g., +/-5%) of the nominal frequency or range of frequencies.

The air interface in RAN 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices. For example, using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP), the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to base station 210 and DL transmissions from base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification also provides support for discrete fourier transform spread OFDM (DFT-s-OFDM) with CP, also known as single carrier FDMA (SC-FDMA). However, it is within the scope of the present disclosure that multiplexing and multiple access are not limited to the above schemes, and may be provided using Time Division Multiple Access (TDMA), code Division Multiple Access (CDMA), frequency Division Multiple Access (FDMA), sparse Code Multiple Access (SCMA), resource Spread Multiple Access (RSMA), or other suitable multiple access schemes. Further, multiplexed DL transmissions from base station 210 to UEs 222 and 224 may be provided utilizing Time Division Multiplexing (TDM), code Division Multiplexing (CDM), frequency Division Multiplexing (FDM), orthogonal Frequency Division Multiplexing (OFDM), sparse Code Multiplexing (SCM), or other suitable multiplexing schemes.

The air interface in RAN 200 may also utilize one or more duplexing algorithms. Duplex is a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full duplex means that two endpoints can communicate with each other at the same time. Half duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex simulations are often implemented for wireless links that utilize Time Division Duplexing (TDD). In TDD, time division multiplexing is used to separate transmissions in different directions on a given channel from each other. That is, at some times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in the other direction, where the direction may change very rapidly, e.g., several times per slot. In wireless links, full duplex channels typically rely on physical isolation of the transmitter and receiver, as well as appropriate interference cancellation techniques. Full duplex emulation is often implemented for wireless links using Frequency Division Duplexing (FDD) or Space Division Duplexing (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated from each other using Space Division Multiplexing (SDM). In other examples, full duplex communications may be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full duplex communication may be referred to as sub-band full duplex (SBFD), cross-division duplex (xDD), or flexible duplex.

Various aspects of the disclosure will be described with reference to OFDM waveforms, an example of which is schematically illustrated in fig. 3. Those of ordinary skill in the art will appreciate that the various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles may also be applied to SC-FDMA waveforms.

Referring now to fig. 3, an expanded view of an example subframe 302 is illustrated showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the Physical (PHY) layer transmission structure for any particular application may vary from the examples described herein depending on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and the frequencies are in units of subcarriers of the carrier in the vertical direction.

The resource grid 304 may be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding number of resource grids 304 may be used for communication. The resource grid 304 is partitioned into a plurality of Resource Elements (REs) 306. REs (which are 1 subcarrier x 1 symbol) are the smallest discrete part of the time-frequency grid and contain a single complex value representing data or signals from a physical channel. Each RE may represent one or more bits of information, depending on the modulation utilized in a particular embodiment. In some examples, a block of REs may be referred to as a Physical Resource Block (PRB) or more simply as a Resource Block (RB) 308 that contains any suitable number of contiguous subcarriers in the frequency domain. In one example, the RB may include 12 subcarriers, the number of which is independent of the parameter set (numerology) used. In some examples, an RB may include any suitable number of consecutive OFDM symbols in the time domain, depending on the parameter set. Within this disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to a single communication direction (transmission or reception of a given device).

The set of contiguous or non-contiguous resource blocks may be referred to herein as a Resource Block Group (RBG), a subband, or a bandwidth portion (BWP). The set of subbands or BWP may span the entire bandwidth. Scheduling a scheduled entity (e.g., UE) for downlink, uplink, or side-uplink transmission generally involves scheduling one or more resource elements 306 within one or more subbands or bandwidth portions (BWP). Thus, the UE typically uses only a subset of the resource grid 304. In some examples, an RB may be the smallest resource unit that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate of the UE. The RBs may be scheduled by a scheduling entity, such as a base station (e.g., a gNB, eNB, etc.), or may be self-scheduled by a UE implementing D2D side uplink communications.

In this illustration, RB 308 is shown to occupy less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given embodiment, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Further, in this illustration, RB 308 is shown to occupy less than the entire duration of subframe 302, although this is just one possible example.

Each 1ms subframe 302 may be comprised of one or more adjacent slots. In the example shown in fig. 3, one subframe 302 includes four slots 310 as an illustrative example. In some examples, a slot may be defined according to a specified number of OFDM symbols having a given Cyclic Prefix (CP) length. For example, a slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include minislots with shorter durations (e.g., one to three OFDM symbols), sometimes referred to as shortened Transmission Time Intervals (TTIs). In some cases, these minislots or shortened Transmission Time Intervals (TTIs) may be transmitted occupying resources scheduled for ongoing slot transmissions for the same or different UEs. Any number of resource blocks may be used within a subframe or slot.

An expanded view of one of the time slots 310 shows the time slot 310 including a control region 312 and a data region 314. In general, control region 312 may carry control channels, while data region 314 may carry data channels. Of course, a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. The structure shown in fig. 3 is only an example, and a different slot structure may be used, and may include one or more of each of a control region and a data region.

Although not shown in fig. 3, individual REs 306 within RBs 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, and the like. Other REs 306 within an RB 308 may also carry pilot or reference signals. These pilot or reference signals may be provided to a receiving device to perform channel estimation for the corresponding channel, which may enable coherent demodulation/detection of the control and/or data channel within RB 308.

In some examples, the time slots 310 may be used for broadcast, multicast, or unicast communications. For example, broadcast, multicast, or multicast communication may refer to a point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to another device. Here, broadcast communications are delivered to all devices, while multicast or multicast communications are delivered to a plurality of intended receiving devices. Unicast communication may refer to point-to-point transmission from one device to a single other device.

In an example of cellular communication over a cellular carrier via a Uu interface, for DL transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within a control region 312) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (e.g., physical Downlink Control Channels (PDCCHs)). The PDCCH carries Downlink Control Information (DCI) including, but not limited to, power control commands (e.g., one or more open loop power control parameters and/or one or more closed loop power control parameters), scheduling information, grants, and/or allocation of REs for DL and UL transmissions. The PDCCH may also carry hybrid automatic repeat request (HARQ) feedback transmissions, such as Acknowledgements (ACKs) or Negative Acknowledgements (NACKs). HARQ is a well-known technique to those of ordinary skill in the art, wherein the integrity of a packet transmission may be checked at the receiving side to ensure accuracy, for example, using any suitable integrity checking mechanism, such as a checksum or Cyclic Redundancy Check (CRC). If the integrity of the transmission is acknowledged, an ACK may be sent, and if not, a NACK may be sent. In response to the NACK, the transmitting device may transmit a HARQ retransmission, which may implement chase combining, incremental redundancy, and the like.

The base station may also allocate one or more REs 306 (e.g., in a control region 312 or a data region 314) to carry other DL signals, such as demodulation reference signals (DMRS); phase tracking reference signal (PT-RS); channel State Information (CSI) reference signals (CSI-RS); a Synchronization Signal Block (SSB). SSBs may be broadcast at regular intervals based on periodicity (e.g., 5, 10, 20, 30, 80, or 130 ms). SSBs include a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a physical broadcast control channel (PBCH). The UE may implement radio frame, subframe, slot, and symbol synchronization in the time domain, identify the center of channel (system) bandwidth in the frequency domain, and identify the Physical Cell Identity (PCI) of the cell using PSS and SSS.

The PBCH in the SSB may further include a Master Information Block (MIB) including various system information and parameters for decoding the System Information Block (SIB). The SIB may be, for example, systemiformationtype 1 (SIB 1) which may include various additional (remaining) system information. The MIB and SIB1 together provide minimum System Information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of PDCCH control resource set (CORESET) (e.g., PDCCH CORESET 0), cell prohibit indicator, cell reselection indicator, grid (ras) offset, and search space for SIB 1. Examples of Remaining Minimum System Information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also transmit Other System Information (OSI).

In some examples, an antenna port used to transmit SSB or other signals may be referred to as quasi co-location (QCL) if the spatial parameters of a transmission on one antenna port may be inferred from the spatial parameters of another transmission on a different antenna port. A receiving device (e.g., UE) can perform channel estimation for demodulating data or control information received from a first set of antenna ports based on reference signals received from a second set of antenna ports quasi co-located with the first set of antenna ports. Thus, a quasi co-located (QCL) relationship between antenna ports may increase the chance that the UE can successfully decode downlink transmissions from the base station. In some cases, the base station may send an indication to the UE of which antenna port is QCL so that the UE can identify additional reference signals for channel estimation.

In some examples, a base station may configure a Transmission Configuration Indication (TCI) state set to indicate to a UE one or more QCL relationships between antenna ports for transmitting downlink signals to the UE. Each TCI state may be associated with a set of reference signals (e.g., SSBs or CSI-RS of different types), and the TCI state may indicate a QCL relationship between an antenna port used to transmit the set of reference signals and an antenna port used to transmit data or control information to the UE. In this way, when the UE receives an indication of a particular TCI state from the base station (e.g., in DCI), the UE may determine that the antenna port for transmitting the reference signal associated with the TCI state is quasi co-located with the antenna port for transmitting data and control information to the UE. The UE may perform channel estimation for demodulating data or control information received from the base station using a reference signal associated with the TCI state.

In UL transmissions, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to carry UL Control Information (UCI) including one or more UL control channels (e.g., physical Uplink Control Channel (PUCCH)) to the scheduling entity. UCI may include various packet types and categories including pilot, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of the uplink reference signal may include a Sounding Reference Signal (SRS) and an uplink DMRS. In some examples, UCI may include a Scheduling Request (SR), i.e., a request to schedule uplink transmissions for a scheduling entity. Here, in response to the SR transmitted on the UCI, the scheduling entity may transmit Downlink Control Information (DCI) capable of scheduling resources for uplink packet transmission. UCI may also include HARQ feedback, channel State Feedback (CSF) (such as CSI reports), or any other suitable UCI.

In addition to control information, one or more REs 306 may be allocated for data traffic (e.g., within a data region 314). Such data traffic may be carried on one or more traffic channels, such as a Physical Downlink Shared Channel (PDSCH) for DL transmissions; or for UL transmissions, a Physical Uplink Shared Channel (PUSCH). In some examples, one or more REs 306 within the data region 314 may be configured to carry other signals, such as one or more SIBs and DMRSs.

In an example of sidelink communication over a sidelink carrier via a proximity services (ProSe) PC5 interface, the control region 312 of the slot 310 may comprise a Physical Sidelink Control Channel (PSCCH) comprising Sidelink Control Information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a transmitting (Tx) V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., a receiving (Rx) V2X device or some other Rx UE). The data region 314 of the slot 310 may include a physical side uplink shared channel (PSSCH) that includes side uplink data traffic transmitted by an initiating (transmitting) side uplink device within resources reserved by the transmitting side uplink device over side uplink carriers via SCI. Other information may also be sent through the various REs 306 within the time slot 310. For example, HARQ feedback information may be transmitted from a receiving side downlink device to a transmitting side downlink device in a physical side uplink feedback channel (PSFCH) within a time slot 310. Further, one or more reference signals, such as sidelink SSB, sidelink CSI-RS, sidelink SRS, and/or sidelink Positioning Reference Signals (PRS), may be transmitted within the slot 310.

These physical channels are typically multiplexed and mapped to transport channels for processing at the Medium Access Control (MAC) layer. The transport channel carries blocks of information called Transport Blocks (TBs). The Transport Block Size (TBS), which may correspond to a plurality of information bits, may be a controlled parameter based on the Modulation and Coding Scheme (MCS) and the number of RBs in a given transmission.

The channels or carriers described above with reference to fig. 1-3 are not necessarily all channels or carriers that may be used between the scheduling entity and the scheduled entity, and one of ordinary skill in the art will recognize that other channels or carriers may be used in addition to the illustrated channels or carriers, such as other traffic, control, and feedback channels.

Fig. 4A illustrates an example 400 of various downlink channels within a subframe of a frame including channels for initial access and synchronization. As shown in fig. 4A, a Physical Downlink Control Channel (PDCCH) 402 is transmitted in at least two symbols (e.g., symbol 0 and symbol 1) and may carry DCI within at least one Control Channel Element (CCE), where each CCE includes nine RE groups (REGs) and each RE group (REG) includes four consecutive REs in an OFDM symbol. Further, fig. 4A illustrates an exemplary Synchronization Signal Block (SSB) 404 that may be periodically transmitted by a base station or a gNB. SSB 404 carries synchronization signals PSS 406 and SSS 408 and broadcast channel (PBCH) 410. In this example, SSB 404 contains one PSS symbol (shown in symbol 2), one SSS symbol (shown in symbol 4) and two PBCH symbols (shown in symbols 3 and 5). The PSS and SSS combination may be used to identify the physical cell identity. The UE uses PSS to determine subframe/symbol timing and physical layer identity. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine a Physical Cell Identifier (PCI). Further, based on the PCI, the UE may determine the location of the aforementioned DMRS. Physical broadcast channels PBCH and PSS and SSS logical packets carrying a Master Information Block (MIB) to form a synchronization signal; i.e., SSB 404. The MIB provides the number of RBs and a System Frame Number (SFN) in the system bandwidth.

Fig. 4B is a diagram illustrating various broadcast information 450 related to initial cell access, according to some examples. The broadcast information 450 may be transmitted by a RAN node (e.g., a base station, such as an eNB or a gNB) on resources (e.g., time-frequency resources) allocated for transmission of the broadcast information 450 in a cell. Broadcast information 450 includes SSB 404 shown in fig. 4A. Note that the PBCH in SSB 404 includes MIB carrying various System Information (SI) including, for example, a cell prohibit indication, a subcarrier spacing, a system frame number, and scheduling information for CORESET0 452. For example, the PBCH in SSB 404 may include scheduling information indicating the time-frequency resources allocated for CORESET0 452. In some examples, CORESET0 452 may be transmitted within the first four symbols of a slot (e.g., within a control region). In addition, CORESET0 452 carries PDCCH with DCI containing scheduling information for scheduling SIB1 454. SIB1 454 is carried within a Physical Downlink Shared Channel (PDSCH) within the data region of the slot. Further, SIB1 454 may be referred to as RMSI and include a set of radio resource parameters that provide network identification and configuration, for example. For example, the set of radio resource parameters may include a bandwidth (e.g., a number of BWP) over which the UE may communicate with the base station.

Fig. 4B also shows that RMSI of SIB1 message 454 may also include a bit field 468 (e.g., indicating availability of narrowband wireless communication and/or its configuration). The time/frequency location of the bit field 468 is merely exemplary to illustrate some time and frequency resources that the bit field 468 utilizes the SIB1 message 454.

The MIB in the PBCH may include System Information (SI) and parameters for decoding SIBs (e.g., SIB 1). Examples of SI transmitted in MIB may include, but are not limited to, subcarrier spacing, system frame number, configuration of PDCCH control resource set (CORESET) (e.g., PDCCH CORESET 0), and search space for SIB 1. Examples of SI transmitted in SIB1 may include, but are not limited to, random access search space, downlink configuration information, and uplink configuration information. MIB and SIB1 together provide the minimum SI for initial access.

The initial access procedure of the UE using the above information is briefly discussed below. As discussed above, a Base Station (BS) may transmit synchronization signals (e.g., including PSS and SSS) in a network to enable a UE to synchronize with the BS, and SI (e.g., including MIB, RMSI, and OSI) to facilitate initial network access. The BS may transmit PSS, SSS, and/or MIB over the PBCH via SSB, and may broadcast RMSI and/or OSI over the PDSCH.

A UE attempting to access a RAN (e.g., RAN 200 of fig. 2) may perform an initial cell search by detecting PSS from a BS of the RAN (e.g., PSS of a cell of the BS). The PSS may enable the UE to synchronize with the periodic timing of the BS and may indicate the physical layer identification value assigned to the cell. The UE may also receive SSS from the BS that enables the UE to synchronize with the cell on a radio frame level. The SSS may also provide a cell identification value that the UE may combine with the physical layer identification value to identify the cell.

After receiving the PSS and SSS, the UE may receive SI from the BS. The system information may take the form of MIB and SIB as discussed above. The system information may include information that the UE can use to access the network, such as Downlink (DL) channel configuration information, uplink (UL) channel configuration information, access category information, and cell barring information, among others. The MIB may include SI for initial network access and scheduling information for RMSI and/or OSI. After decoding the MIB, the UE may receive RMSI and/or OSI.

SI includes information that enables the UE to determine how to make an initial access to the RAN. In some examples, SIB2 includes random access configuration information (e.g., RACH configuration) that indicates resources used by the UE for communication with the RAN during initial access. The random access configuration information may indicate resources allocated by the RAN for a Random Access Channel (RACH) procedure, for example. For example, the RACH configuration may indicate resources allocated by the network for the UE to transmit a Physical Random Access Channel (PRACH) preamble and receive a random access response. In some examples, the RACH configuration identifies a Monitor Occasion (MO) that specifies a set of symbols (e.g., in a PRACH slot) scheduled by the base station for the PRACH procedure. The RACH configuration may also indicate the size of a random access response window during which the UE will monitor for a response to the PRACH preamble. In some examples, the RACH configuration may also specify that the random access response window starts a number of subframes after the PRACH preamble ends. After obtaining MIB, RMSI and/or OSI, the UE may thus perform a random access procedure for initial access to the RAN.

Fig. 5 is a signaling diagram 500 illustrating an example of signaling for a contention-based RACH procedure in a wireless communication system including a Base Station (BS) 502 and a User Equipment (UE) 504. In some examples, base station 502 may correspond to any base station or scheduling entity shown in any of fig. 1, 2, and 20. In some examples, the UE 504 may correspond to any UE or scheduled entity shown in any of fig. 1, 2, and 16.

At #506 of fig. 5, the UE 504 sends message 1 (Msg 1) of the RACH procedure to the BS 502. In some examples, msg1 is a PRACH preamble. RACH Msg1 may be referred to as PRACH. As described above, the UE 504 may transmit the PRACH preamble on the resources specified by the RACH configuration included in SIB 2.

At #508, the BS 502 responds to the PRACH preamble with message 2 (Msg 2) of the RACH procedure. Msg2 may be informally referred to as a Random Access Response (RAR). In some examples of #508, BS 502 transmits DCI on a PDCCH, where the DCI schedules a PDSCH (e.g., the DCI specifies resources for PDSCH transmission). Then, the BS 502 transmits a PDSCH including RAR data, such as, for example, UL grant for the UE to transmit message 3 (Msg 3) of the RACH procedure.

In some examples, the UE monitors RACH Msg2 on resources specified by the RACH configuration during a RAR window specified by the RACH configuration. For example, the UE may decode DCI carried on PDCCH and then decode RAR carried on PDSCH.

At #510, upon receiving all RAR information, the UE 504 sends Msg3 of the RACH procedure. In some examples, RACH Msg3 is a Radio Resource Control (RRC) connection request message.

At #512, BS 502 responds with message 4 (Msg 4) of the RACH procedure. In some examples, RACH Msg4 is an RRC connection setup message.

At #514, the UE 504 responds with message 5 (Msg 5) of the RACH procedure. In some examples, RACH Msg5 is an RRC connection complete message. In some examples, if the UE 504 successfully decodes RACH Msg4, the transmission of RACH Msg5 may involve transmitting PUCCH including HARQ-ACK for PDSCH data of RACH Msg 4. In some examples, PUCCH hopping (frequency hopping) may be used for such transmission of RACH Msg 5.

In some examples, prior to dedicated PUCCH resource configuration, the PUCCH resource set may be configured by PUCCH-resource com mon, where the PUCCH resource set includes 16 resources, each resource corresponding to a PUCCH format, a first symbol, a duration, a PRB offset for PUCCH transmissionAnd cyclically shifting the index set. PRB offset->And UL BWP size may be used to determine a frequency hopping pattern (pattern). For example, the UE may determine the PRB index of the PUCCH transmission in the first hop as +. >And determining the PRB index of the PUCCH transmission in the second hop as + ->Wherein N is _CS Is the total number of initial cyclic shift indices in the initial cyclic shift index set. In some examples, the nominal UL BWP size is 5MHz, where

As shown in #516, the BS 502 and the UE 504 eventually establish a connection and enter an active phase of operation where data may be exchanged. For example, as discussed herein, the BS may schedule the UE for UL communication and/or DL communication.

Global system for mobile communications (GSM) for railways (GSM-R) supports over 100,000 kilometers of railroad track in europe. However, the ending plan for GSM-R support is approximately 2030. Future Railroad Mobile Communication Systems (FRMCSs) are being developed for migrating from 2G GSM-R to 5G NR and have more forward compatibility to future 6G systems. In some aspects, this may involve reallocating GSM bands for FRMCS. For example, as shown in fig. 6, the GSM 900MHz FDD band 600 has been used in rural areas. The 900MHz FDD band 600 includes two 5.6MHz GSM-R bands 602 and 604. For FRMCS, two 3.6MHz bands (not shown) based on 5G NR can be used within the two 5.6MHz bands while supporting coexistence with GSM-R.

Similarly, in the united states, the 900MHz band 700 shown in fig. 7 is currently configured as illustrated at the top 702 of fig. 7. This band may be re-used in two 3MHz FDD bands (not shown) for 5G NR based broadband services such as public mesh private networks.

In some examples, the CSI-RS is configured with 4n RBs. In this case, the UE may expectIf Bandwidth (BW) =5 MHz, then in some examples the number of RBs for CSI-RS is 24 RBs.

In some examples, if bwp=10 MHz, flexible tracking references are based on UE capabilitiesThe signal (TRS) BW may be configured to be 5MHz or 10MHz. Here, the bandwidth of the CSI-RS resource as given by the higher layer parameter freqBand configured by CSI-RS-resource mapping is X resource blocks, where X.gtoreq.28 Resources (RBs) if the UE indicates trs-AddBW-Set1 for the trs-AdditionalBandwidth capability and X.gtoreq.32 Resources (RBs) if the UE indicates trs-AddBW-Set2 for the additionalBandwidth capability. If the UE is configured with a UE including X<The bandwidth of the CSI-RS resource given by the higher layer parameter freqBand configured by the CSI-RS-resource mapping is 52 andminimum value in each resource block, or equal to +. >And resource blocks.

Thus, in the above example, the minimum BW for CSI-RS/TRS is 5MHz even for UEs supporting flexible TRS BW. This is greater than the 3.6MHz BW or 3.0MHz BW of the narrow RF communication bands proposed in fig. 6 and 7, respectively.

The present disclosure relates in some aspects to CSI-RS and TRS configurations for UEs supporting narrowband NR. These UEs may be referred to herein as narrowband NR UEs.

In a first example (1-Alt 1), the nominal BWP is configured to be 5MHz (as in a wideband system), but also provides support for flexible CSI-RS/TRS BW within a narrowband of less than 5MHz. For example, to support NR railway (NR-R) CSI-RSs of 16 RBs or 20 RBs, the CSI-RSs may be modified to be configured withIn addition, the TRS may be modified with x=16 RBs or 20 RBs based on UE capabilities for flexible TRS.

In a second example (1-Alt 1 a), the nominal BWP is configured to be 5MHz (as in a wideband system), but the TRS is disabled for narrowband NR. In this case, since SSB and TRS may have the same BW, TRS may be omitted. In this case, the UE may assume that the QCL relationship (e.g., relativity) of PDSCH DMRS is SSB-based rather than TRS-based. Further, at an initial stage, the use of high MCS values (e.g., requiring TRS) may be limited.

In a third example (1-Alt 2), a new UE capability is defined that supports DL BWP with a size of 3.6MHz (or some other BWP size). In this case, the CSI-RS/TRS BW will be mapped to a flexible DL BWP size.

The legacy PUCCH configuration may use frequency hopping within UL BWP. If UL BWP is configured to 5MHz, UL PUCCH hopping would be out of the range of 3.6 MHz.

The present disclosure relates in some aspects to PUCCH configuration for narrowband NR UEs.

In a first example (2-Alt 1), the nominal BWP is configured to be 5MHz (as in a broadband system), but a different hopping pattern is used for UEs with a limited BW (e.g. 3.6 MHz).

In a second example (2-Alt 1 a), the nominal BWP is configured to be 5MHz (as in a wideband system), but PUCCH hopping is not used for UEs with limited BW (e.g. 3.6 MHz).

In a third example (2-Alt 2), a new UE capability is defined that supports UL BWP with a size of 3.6MHz (or some other BWP size).

The present disclosure relates in some aspects to random access configuration for narrowband NR UEs. Legacy random access is on an initial UL BWP with a minimum bandwidth (minBW) of 5 MHz.

In a first example (3-Alt 1), the nominal BWP is configured to be 5MHz (as in a broadband system), but there is an added limitation on the Random Access (RA) configuration. For RACH Msg1 frequency position: msg1-FrequencyStart: 0..274 redefines RB offset at the lowest position of PRACH occasion within narrowband NR. For msg1-FDM 1,2,4,8, FDM is disabled (e.g., only set 1 is used).

Furthermore, only some RACH Msg1 PRACH format configurations may be supported. For example, a long PRACH with 1.08MHz may be used: format 0/1/2; but format 3 with 4.32mhz >3.6mhz may not be supported. A short PRACH with 2.16MHz may fit into 3.6MHz and thus may be supported.

For RACH Msg4 feedback, PUCCH hopping may be disabled for HARQ-ACK feedback in PUCCH-ConfigCommon.

In a second example (3-Alt 2), a new UE capability is defined that supports an initial UL BWP with a size of 3.6MHz (or some other BWP size).

In view of the above, in some examples, the nominal minimum BWP size is 5MHz, while the BW of the UE and the gNB is less than 5MHz (e.g., 3MHz or 3.6 MHz). In these examples, the smaller BWP (e.g., 3.6 MHz) may not be well defined or configured.

Alternatively, in some examples, a smaller BWP (e.g., 3.6 MHz) may be explicitly defined or configured. Thus, in these examples, both BWP and BW of the UE and the gNB may be less than 5MHz.

In the case of narrowband spectrum with 16 RBs or 20 RBs,may be based on the actual narrowband size instead of having +.>A nominal UL BWP size of 5MHz (e.g., as discussed above at #514 of fig. 5). If the PUCCH resource set of index #15 is configured, the PRB offset is typically based on the UL BWP size +.1-1 as specified in Table 9.2.1 of TS 38.213V15.12.0 (2020-12) >In case of narrowband spectrum with 16 RBs or 20 RBs, in case of PUCCH resource set with indicated index #15, PRB offset +.>May be six (6), which is different from the PRB offset of four (4) with the indicated index # 14. In some examples, PRB offset +_ in case of PUCCH resource set with indicated index #15>Is fixed to six (6), or PRB offset +.>Based on the nominal UL BWP size of 24 RBs instead of the actual narrowband size. Alternatively, the UE does not expect the pucch-ResourceCommon to indicate index #15.

Fig. 8 is a flow chart illustrating an example method 800 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 800 for wireless communication may be performed by the UE 1600 shown in fig. 16. In some examples, the method 800 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 802, the UE transmits capability information indicating support for narrowband wireless communications. For example, the UE may send a UE capability message including an indication that the UE supports the 3MHz band and/or the 3.6MHz band. In some examples, the UE may send the capability information before or after receiving a message (e.g., via SIB or some other signaling) that the base station supports narrowband communications (e.g., a frequency band less than 5 MHz). The base station may also indicate whether it supports broadband communications (e.g., a frequency band of 5MHz or greater). In some examples, the capability circuitry 1642 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610 may provide components to transmit capability information.

At block 804, the UE determines a configuration for the narrowband wireless communication. In some examples, the UE may receive the configuration from the base station. In some examples, the UE may use a predefined configuration (e.g., a narrowband configuration defined by a wireless communication standard). In some examples, the UE may identify the configuration specified for a particular RF band. In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16 may provide components to determine a configuration.

At optional block 806, the UE may monitor the CSI-RS using a minimum BWP size (e.g., a minimum BWP size of 5MHz or less) specified by the configuration for narrowband wireless communication (determined at block 804). In some examples, the configuration circuitry 1643 and communication and processing circuitry 1641 and transceiver 1610 shown and described above in connection with fig. 16 may provide components to monitor CSI-RS.

At optional block 808, if the configuration (determined at block 804) indicates that a TRS is not to be transmitted for the narrowband wireless communication, the UE may disable monitoring the TRS. In some examples, the configuration circuit 1643 shown and described above in connection with fig. 16 may provide components to disable the monitoring TRS.

At optional block 810, the UE may monitor the TRS using a minimum BWP size (e.g., a minimum BWP size of 5MHz or less) specified by the configuration for narrowband wireless communication (determined at block 804). In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610, may provide components to monitor the TRS.

At optional block 812, if the configuration (determined at block 804) indicates that a TRS is not to be sent for the narrowband wireless communication, the UE may determine a QCL relationship for PDSCH DMRS based on the SSB instead of the TRS. In some examples, the configuration circuit 1643 shown and described above in connection with fig. 16 may provide components to determine QCL relationships.

At optional block 814, the UE may refrain from using the higher order MCS if the configuration (determined at block 804) indicates that certain higher order MCSs are not to be used for the narrowband wireless communication (e.g., because TRSs are not to be transmitted). In some examples, the configuration circuitry 1643 and communication and processing circuitry 1641 and transceiver 1610 shown and described above in connection with fig. 16 may provide components to avoid using higher order MCSs.

Fig. 9 is a flow chart illustrating an example method 900 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 900 for wireless communication may be performed by the UE 1600 shown in fig. 16. In some examples, method 900 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 902, the UE transmits capability information indicating support for narrowband wireless communications. For example, the UE may send a UE capability message that includes an indication that the UE supports the 3MHz band and/or the 3.6MHz band. In some examples, the capability circuitry 1642 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610, may provide components to send capability information.

At block 904, the UE determines a configuration for the narrowband wireless communication. In some examples, the UE may receive the configuration from the base station. In some examples, the UE may use a predefined configuration (e.g., a narrowband configuration defined by a wireless communication standard). In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16 may provide components to determine a configuration.

At block 906, the UE receives DCI including scheduling information for PUCCH transmission. For example, a UE may receive DCI from a base station, wherein the DCI indicates resources used by the UE for the PUCCH transmission. In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610, may provide components to receive DCI.

At optional block 908, if the configuration (determined at block 904) specifies that frequency hopping is not to be used for PUCCH transmission for narrowband wireless communication, the UE may disable frequency hopping for the PUCCH transmission. In some examples, the configuration circuit 1643 shown and described above in connection with fig. 16 may provide components to disable frequency hopping.

At optional block 910, the UE may use the hopping pattern specified by the configuration (determined at block 904) for the PUCCH transmission. For example, the base station may specify one hopping pattern for narrowband wireless communication and another hopping pattern for wideband wireless communication. In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610, may provide components to use a frequency hopping pattern.

Fig. 10 is a flow chart illustrating an example method 1000 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1000 for wireless communication may be performed by the UE 1600 shown in fig. 16. In some examples, the method 1000 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1002, the UE transmits capability information indicating support for narrowband wireless communications. For example, the UE may send a UE capability message to the base station, wherein the capability message includes an indication that the UE supports the 3MHz band and/or the 3.6MHz band. In some examples, the capability circuitry 1642 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610 may provide components to transmit capability information.

At block 1004, the UE determines a configuration for the narrowband wireless communication. In some examples, the UE may receive the configuration from the base station. In some examples, the UE may use a predefined configuration (e.g., a narrowband configuration defined by a wireless communication standard). In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16 may provide components to determine a configuration.

At optional block 1006, if the configuration (determined at block 1004) specifies that FDM is not used for random access for narrowband wireless communications, the UE may disable FDM for random access. In some examples, the configuration circuit 1643 shown and described above in connection with fig. 16 may provide components to disable FDM.

At optional block 1008, the UE may use the RB offset of the lowest PRACH occasion specified by the configuration (determined at block 1004) for random access. For example, the base station may assign one RB offset for narrowband wireless communications and another RB offset for wideband wireless communications. In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610, may provide means to use RB offset for the lowest PRACH occasion.

At optional block 1010, the UE may select the PRACH format configuration specified by the configuration (determined at block 1004) for the random access. For example, the UE may avoid using any PRACH format configuration supported by narrowband wireless communications that is not specified by the configuration. In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16 may provide means to select a PRACH format configuration.

At optional block 1012, if this is specified by the configuration (determined at block 1004), the UE may disable PUCCH hopping for HARQ-ACK feedback. In some examples, the configuration circuit 1643 shown and described above in connection with fig. 16 may provide means to disable PUCCH frequency hopping.

Fig. 11 is a flow chart illustrating an example method 1100 for wireless communication according to some aspects of the disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1100 for wireless communication may be performed by the BS 2000 shown in fig. 20. In some examples, the method 1100 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1102, the base station receives capability information indicating that the UE supports narrowband wireless communications. For example, the base station may receive a UE capability message from the UE that includes an indication that the UE supports the 3MHz band and/or the 3.6MHz band. In some examples, the base station may receive this capability information before or after sending a message (e.g., via SIB or some other signaling) that the base station supports narrowband communication (e.g., a frequency band less than 5 MHz). The base station may also indicate whether it supports broadband communications (e.g., a frequency band of 5MHz or greater). In some examples, the capability circuitry 2042 shown and described above in connection with fig. 20, along with the communication and processing circuitry 2041 and transceiver 2010, may provide components to receive capability information.

At block 1104, the base station determines a configuration for the narrowband wireless communication (e.g., a narrowband configuration defined by a wireless communication standard). In some examples, the base station may identify the configuration specified for a particular RF band. In some examples, the base station may send the configuration to the UE. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide components to determine a configuration.

At optional block 1106, the base station may transmit the CSI-RS using a minimum BWP size (e.g., a minimum BWP size of 5MHz or less) specified by the configuration for narrowband wireless communication (determined at block 1104). In some examples, configuration circuitry 2043, as shown and described above in connection with fig. 20, along with communication and processing circuitry 2041 and transceiver 2010, may provide components to transmit CSI-RS.

At optional block 1108, if the configuration (determined at block 1104) indicates that the TRS is not to be transmitted for narrowband wireless communications, the base station may disable transmission of the TRS. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide components to disable transmission of the TRS.

At optional block 1110, the base station may transmit the TRS using a minimum BWP size (e.g., a minimum BWP size of 5MHz or less) specified by the configuration for narrowband wireless communication (determined at block 1104). In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20, along with the communication and processing circuit 2041 and the transceiver 2010, may provide components to transmit a TRS.

At optional block 1112, if the configuration (determined at block 1104) indicates that a TRS is not to be sent for the narrowband wireless communication, the base station may determine a QCL relationship for PDSCH DMRS based on the SSB and not the TRS. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide components to determine QCL relationships.

At optional block 1114, if the configuration (determined at block 1104) indicates that certain higher order MCSs are not to be used for the narrowband wireless communication (e.g., because TRSs are not being transmitted), the base station may refrain from using higher order MCSs. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20, along with the communication and processing circuit 2041 and transceiver 2010, may provide components to avoid using higher order MCSs.

Fig. 12 is a flow chart illustrating an example method 1200 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1200 for wireless communication may be performed by the BS 2000 shown in fig. 20. In some examples, the method 1200 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1202, the base station receives capability information indicating that the UE supports narrowband wireless communication. For example, the base station may receive a UE capability message from the UE that includes an indication that the UE supports the 3MHz band and/or the 3.6MHz band. In some examples, the capability circuitry 2042 shown and described above in connection with fig. 20, along with the communication and processing circuitry 2041 and the transceiver 2010, may provide components to receive capability information.

At block 1204, the base station determines a configuration for the narrowband wireless communication (e.g., a narrowband configuration defined by a wireless communication standard). In some examples, the base station may send the configuration to the UE. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide components to determine a configuration.

At block 1206, the base station transmits DCI including scheduling information for PUCCH transmission. For example, the base station may send DCI to the UE, where the DCI indicates resources to be used by the UE for the PUCCH transmission. In some examples, the configuration circuitry 2043 and the communication and processing circuitry 2041 and transceiver 2010 shown and described above in connection with fig. 20 may provide components to transmit DCI.

At optional block 1208, if the configuration (determined at block 1204) specifies that frequency hopping is not to be used for PUCCH transmission for narrowband wireless communication, the base station may receive the PUCCH transmission without frequency hopping. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20, along with the communication and processing circuit 2041 and the transceiver 2010, may provide components to receive PUCCH transmissions.

At optional block 1210, the base station may use the hopping pattern specified by the configuration (determined at block 1204) for receiving the PUCCH transmission. For example, one hopping pattern may be assigned for narrowband wireless communications and another hopping pattern may be assigned for wideband wireless communications. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20, along with the communication and processing circuit 2041 and the transceiver 2010, may provide components to use a frequency hopping pattern.

Fig. 13 is a flow chart illustrating an example method 1300 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1300 for wireless communication may be performed by the BS 2000 shown in fig. 20. In some examples, the method 1300 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1302, the base station receives capability information indicating that the UE supports narrowband wireless communications. For example, the base station may receive a UE capability message from the UE that includes an indication that the UE supports the 3MHz band and/or the 3.6MHz band. In some examples, the capability circuitry 2042 shown and described above in connection with fig. 20, along with the communication and processing circuitry 2041 and the transceiver 2010, may provide components to receive capability information.

At block 1304, the base station determines a configuration for the narrowband wireless communication (e.g., a narrowband configuration defined by a wireless communication standard). In some examples, the base station may send the configuration to the UE. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide components to determine a configuration.

At optional block 1306, if the configuration (determined at block 1304) specifies that FDM is not to be used for random access for narrowband wireless communications, the base station monitors random access signaling without FDM. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20, along with the communication and processing circuit 2041 and transceiver 2010, may provide components to monitor random access signaling.

At optional block 1308, the base station may monitor random access signaling for random access using the RB offset of the lowest PRACH occasion specified by the configuration (determined at block 1304). For example, one RB offset may be designated for narrowband wireless communications and another RB offset may be designated for wideband wireless communications. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20, along with the communication and processing circuit 2041 and transceiver 2010, may provide components to monitor random access signaling.

At optional block 1310, the base station may monitor the PRACH format configuration specified by the configuration (determined at block 1304) for the random access. For example, the base station may exclude any unsupported PRACH format configuration. In some examples, the configuration circuitry 2043 shown and described above in connection with fig. 20, along with the communication and processing circuitry 2041 and transceiver 2010, may provide components to monitor PRACH format configurations.

At optional block 1312, if this is specified by the configuration (determined at block 1304), the base station may monitor HARQ-ACK feedback on PUCCH without frequency hopping. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20, along with the communication and processing circuit 2041 and transceiver 2010, may provide components to monitor HARQ-ACK feedback.

Fig. 14 is a flow chart illustrating an example method 1400 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1400 for wireless communication may be performed by the UE 1600 shown in fig. 16. In some examples, the method 1400 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1402, the UE transmits capability information indicating support for narrowband wireless communications. For example, the UE may send a UE capability message that includes an indication that the UE supports the 3MHz band and/or the 3.6MHz band. In some examples, the capability circuitry 1642 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610 may provide components to transmit capability information.

At block 1404, the UE determines at least one configuration for the narrowband wireless communication. In this case, the at least one configuration is based on a smaller nominal BWP size (e.g., 3GHz or 3.6 GHz) than the nominal BWP size (e.g., 5 GHz) defined for broadband communications. Thus, the BWP size for downlink and uplink signaling is adjusted according to the smaller nominal BWP size. In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16 may provide components to determine at least one configuration.

At block 1406, the UE communicates with the base station using the at least one configuration (e.g., using flexible uplink and downlink bandwidths). In some examples, the configuration circuitry 1643 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610 may provide components to communicate with a base station.

Fig. 15 is a flow chart illustrating an example method 1500 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1500 for wireless communication may be performed by the BS 2000 shown in fig. 20. In some examples, the method 1500 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1502, the base station receives capability information indicating that the UE supports narrowband wireless communications. For example, the base station may receive a UE capability message from the UE that includes an indication that the UE supports the 3MHz band and/or the 3.6MHz band. In some examples, the capability circuitry 2042 shown and described above in connection with fig. 20, along with the communication and processing circuitry 2041 and transceiver 2010, may provide components to receive capability information.

At block 1504, the base station determines at least one configuration for the narrowband wireless communication. In this case, the at least one configuration is based on a smaller nominal BWP size (e.g., 3GHz or 3.6 GHz) than the nominal BWP size defined for broadband communications (e.g., 5 GHz). Thus, the BWP size for downlink and uplink signaling is adjusted according to the smaller nominal BWP size. In some examples, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide components to determine at least one configuration.

At block 1506, the base station communicates with the UE using the at least one configuration (e.g., using flexible uplink and downlink bandwidths). In some examples, the configuration circuitry 2043 shown and described above in connection with fig. 20, along with the communication and processing circuitry 2041 and transceiver 2010, may provide components to communicate with a UE.

Fig. 16 is a block diagram illustrating an example of a hardware implementation of a UE 1600 employing a processing system 1614. For example, UE 1600 may be a device configured to communicate wirelessly with a base station, as discussed in any one or more of fig. 1-15. In some embodiments, UE 1600 may correspond to any UE or scheduled entity shown in any of fig. 1, 2, and 5.

According to various aspects of the disclosure, the processing system 1614 may be utilized to implement an element or any portion of an element or any combination of elements. The processing system 1614 may include one or more processors 1604. Examples of processor 1604 include a microprocessor, a microcontroller, a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a state machine, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, UE 1600 may be configured to perform any one or more of the functions described herein. That is, the processor 1604 used in the UE 1600 may be used to implement any one or more of the processes and procedures described herein.

In some cases, the processor 1604 may be implemented via a baseband or modem chip, while in other embodiments the processor 1604 may include multiple devices different from the baseband or modem chip (e.g., in such scenarios that may cooperate to implement the examples discussed herein). As described above, various hardware configurations and components external to the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders/summers, and the like.

In this example, the processing system 1614 may be implemented with a bus architecture, represented generally by the bus 1602. The bus 1602 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1614 and the overall design constraints. The bus 1602 communicatively couples various circuitry including one or more processors (indicated generally by the processor 1604), memory 1605, and computer-readable media (indicated generally by the computer-readable medium 1606). The bus 1602 may also link various other circuits known in the art, such as timing sources, peripherals, voltage regulators, and power management circuits, and therefore, will not be described any further. Bus interface 1608 provides an interface between bus 1602 and transceiver 1610, and between bus 1602 and interface 1630. The transceiver 1610 provides a communication interface or means for communicating with various other apparatus over a wireless transmission medium. In some examples, the UE may include two or more transceivers 1610 (e.g., for communicating via one or more RF bands). Interface 1630 provides a communication interface or means for communicating with various other apparatus and devices, e.g., other apparatus housed within the same device as the UE or other external device, via an internal bus such as an ethernet cable or an external transmission medium. Depending on the nature of the device, interface 1630 may include a user interface (e.g., keyboard, display, speaker, microphone, joystick). Of course, such a user interface is optional and may be omitted in some examples, such as an IoT device.

The processor 1604 is responsible for managing the bus 1602 and general processing, including the execution of software stored on the computer-readable medium 1606. When executed by the processor 1604, the software causes the processing system 1614 to perform the various functions described infra for any particular apparatus. The computer-readable medium 1606 and memory 1605 may also be used for storing data that is manipulated by the processor 1604 when executing software. For example, memory 1605 may store configuration information 1615 (e.g., configuration information specified by a standard and/or received from a base station) that is used by processor 1604 in cooperation with transceiver 1610 for narrowband wireless communication.

The one or more processors 1604 in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on the computer readable medium 1606.

The computer-readable medium 1606 may be a non-transitory computer-readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact Disk (CD) or Digital Versatile Disk (DVD)), smart cards, flash memory devices (e.g., card, stick, or key drive), random Access Memory (RAM), read Only Memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically Erasable PROM (EEPROM), registers, removable disk, and any other suitable media for storing software and/or instructions that can be accessed and read by a computer. The computer readable medium 1606 may reside in the processing system 1614, external to the processing system 1614, or distributed across multiple entities including the processing system 1614. The computer readable medium 1606 may be embodied in a computer program product. As an example, the computer program product may include a computer readable medium in a packaging material. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and overall design constraints imposed on the overall system.

UE 1600 may be configured to perform any one or more of the operations described herein (e.g., as described above in connection with fig. 1-15 and as described below in connection with fig. 17-19). In some aspects of the disclosure, the processor 1604 used in the UE 1600 may include circuitry configured for various functions.

The processor 1604 may include a communication and processing circuit 1641. Communication and processing circuitry 1641 may be configured to communicate with a base station, such as a gNB. The communications and processing circuitry 1641 can include one or more hardware components that provide a physical structure that performs various processes related to wireless communications (e.g., signal reception and/or signal transmission) as described herein. The communications and processing circuitry 1641 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and/or processing signals for transmission) as described herein. In some examples, the communication and processing circuitry 1641 may include two or more transmit/receive chains, each configured to process signals of a different RAT (or RAN) type. The communication and processing circuitry 1641 may also be configured to execute communication and processing software 1651 included on the computer-readable medium 1606 to implement one or more functions described herein.

In some examples, communication and processing circuitry 1641 may be configured to receive and process downlink signals via transceiver 1610 and an antenna array. For example, communication and processing circuitry 1641 may be configured to receive respective reference signals (e.g., SSBs or CSI-RSs) from a base station via antenna array 1620.

In some examples, the communication and processing circuitry 1641 may be further configured to generate and transmit uplink signals via the transceiver 1610. For example, the communication and processing circuitry 1641 may be configured to transmit respective reference signals (e.g., SRS or DMRS) to a base station via the antenna array 1620.

The communication and processing circuit 1641 may also be configured to generate and transmit uplink signals to the base station. The uplink signal may include, for example, PUCCH, PUSCH, SRS, DMRS or PRACH. In some examples, the signaling may take the form of MAC-CE carried in PUSCH, UCI in PUCCH or PUSCH, a random access message, or an RRC message. The communication and processing circuitry 1641 may also be configured to generate and transmit (e.g., via UCI in PUCCH) a scheduling request to a base station to receive an uplink grant for carrying PUSCH including the MAC-CE of the request.

In some examples (e.g., where UE 1600 supports both narrowband and wideband communications), communications and processing circuitry 1641 may be configured to receive and process downlink beamformed signals at millimeter-wave frequencies or sub-6 GHz frequencies via transceiver 1610 and antenna array 1620. For example, the communication and processing circuitry 1641 may be configured to receive beamformed signals on each of a plurality of downlink beams from a base station via at least one antenna panel of the antenna array 1620.

In some examples, communication and processing circuitry 1641 may be further configured to generate and transmit uplink beamformed signals at millimeter wave frequencies or sub-6 GHz frequencies via transceiver 1610 and antenna array 1620. For example, the communication and processing circuitry 1641 may be configured to transmit the beamformed signals to the base station on each of the plurality of uplink beams via at least one antenna panel of the antenna array 1620.

In some embodiments in which communication involves receiving information, communication and processing circuitry 1641 may obtain information from components of UE 1600 (e.g., from transceiver 1610 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuit 1641 may output information to another component of processor 1604, memory 1605, or bus interface 1608. In some examples, communication and processing circuitry 1641 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1641 may receive information via one or more channels. In some examples, the communication and processing circuitry 1641 may include functionality for a received component. In some examples, the communication and processing circuitry 1641 may include functionality for decoding components.

In some implementations in which communication involves issuing (e.g., sending) information, communication and processing circuitry 1641 may obtain information (e.g., from processor 1604, memory 1605, or another component of bus interface 1608), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1641 may output information to transceiver 1610 (e.g., which transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1641 may send out one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1641 may send out information via one or more channels. In some examples, communication and processing circuitry 1641 may include functionality for issuing components (e.g., components for transmitting). In some examples, the communication and processing circuitry 1641 may include functionality for the encoded components.

In some examples, the communication and processing circuitry 1641 may include functionality for communicating with a base station via a first RF band according to a first configuration. For example, communication and processing circuitry 1641 may cooperate with transceiver 1610 to send information to and/or receive information from the gNB via a narrowband uplink channel using one or more parameters or aspects specified by the first configuration (e.g., BWP size, etc., as discussed herein).

The processor 1604 may include a capability circuit 1642 configured to perform the capability-related operations as discussed herein (e.g., one or more of the operations described in connection with fig. 6-15). The capability circuitry 1642 may be configured to execute capability software 1652 included on the computer-readable medium 1606 to implement one or more functions described herein.

In some examples, the capability circuitry 1642 may include functionality for receiving a component of the base station that supports a particular RF band. For example, the capability circuitry 1642, along with the communication and processing circuitry 1641 and transceiver 1610, may receive SIBs or some other type of message indicating that the gNB supports narrowband communication.

In some examples, the capability circuitry 1642 may include functionality to determine that UE 1600 supports a minimum BWP size for narrowband wireless communications. For example, the capability circuitry 1642 may identify the UE as a multi-band UE supporting narrowband communications (e.g., less than 5MHz in bandwidth) and/or wideband communications (e.g., 5MHz or higher in bandwidth), or as a reduced capability UE (e.g., a UE supporting only narrowband communications).

In some examples, the capability circuitry 1642 may include functionality for identifying components of an RF band supported by the base station. For example, the capability circuitry 1642, along with the communication and processing circuitry 1641 and transceiver 1610 may monitor information (e.g., SIBs) sent by the gNB for indications of the RF bands that the gNB uses to communicate with the UE. Thus, the capability circuitry 1642 may include functionality for receiving a component of the base station that supports a particular RF band.

The processor 1604 may include configuration circuitry 1643 configured to perform configuration-related operations as discussed herein (e.g., one or more of the operations described in connection with fig. 6-15). The configuration circuitry 1643 may be configured to execute configuration software 1653 included on the computer-readable medium 1606 to implement one or more functions described herein.

In some examples, the configuration circuitry 1643 may include functionality for selecting components of the configuration. For example, the configuration circuitry 1643 may obtain configuration information defined for narrowband communications (e.g., as specified by a wireless communication standard and/or as received from a gNB) that specifies certain parameters and/or actions to be taken (or not taken) for downlink communications (e.g., CSI-RS and/or TRS), uplink communications (e.g., PUCCH), random access, or a combination thereof, for example.

In some examples, the configuration circuitry 1643 may include functionality for identifying BWP-sized components. For example, the configuration circuitry 1643 may obtain configuration information defined for narrowband communications (e.g., as specified by a wireless communication standard and/or as received from a gNB) that specifies a minimum BWP size to be used for narrowband communications.

Fig. 17 is a flow chart illustrating an example method 1700 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1700 for wireless communication may be performed by the UE 1600 shown in fig. 16. In some examples, the method 1700 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1702, a user device may receive an indication that a base station supports a first Radio Frequency (RF) band. For example, the capability circuitry 1642 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610 may provide means to receive an indication that a base station supports a first Radio Frequency (RF) band.

At block 1704, the user device may communicate with the base station via a first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band that is less than a second minimum bandwidth size defined for a second RF band available to the user device. For example, the configuration circuitry 1643 and communication and processing circuitry 1641 and transceiver 1610 shown and described above in connection with fig. 16 may provide components to communicate with a base station via a first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band.

In some examples, the first minimum bandwidth size is a first minimum bandwidth portion size and the second minimum bandwidth size is a second minimum bandwidth portion size. In some examples, the second minimum bandwidth portion size is 5 megahertz (MHz) and the first minimum bandwidth portion size is 3MHz or 3.6MHz.

In some examples, the first radio frequency band is at least one of a future railway mobile communication system band or a broadband service band. In some examples, the first radio frequency band is a 900 megahertz (MHz) band.

In some examples, the first configuration may include a minimum number of Resource Blocks (RBs) for a channel state information-reference signal (CSI-RS). In some examples, communicating with the base station via the first RF band according to the first configuration may include: the CSI-RS is received via at least the minimum number of RBs.

In some examples, the first configuration may include a minimum number of Resource Blocks (RBs) for Tracking Reference Signals (TRSs). In some examples, communicating with the base station via the first RF band according to the first configuration may include: the TRS is received via at least the minimum number of RBs.

In some examples, the first configuration specifies that transmission of Tracking Reference Signals (TRSs) is disabled. In some examples, the user equipment may determine a quasi co-location (QCL) relationship for a Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS) based on a Synchronization Signal Block (SSB) instead of the TRS.

In some examples, the first configuration specifies that use of at least one specified Modulation and Coding Scheme (MCS) value is limited. In some examples, communicating with the base station via the first RF band according to the first configuration may include: when communicating with the base station via the first RF band, the use of the at least one specified modulation and coding scheme value is relinquished (abstain).

In some examples, the first configuration may include a first hopping pattern defined for the first RF band for uplink signal transmission (e.g., PUCCH transmission, PUSCH transmission, etc.), and the first hopping pattern is different from a second hopping pattern defined for the second RF band. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the first hopping pattern is used for transmission on an uplink channel (e.g., PUCCH, PUSCH, etc.).

In some examples, the first configuration may include a first Physical Uplink Control Channel (PUCCH) hopping pattern defined for the first RF band, and the first PUCCH hopping pattern is different from a second PUCCH hopping pattern defined for the second RF band. In some examples, communicating with the base station via the first RF band according to the first configuration may include: and transmitting on the PUCCH using the first PUCCH hopping pattern.

In some examples, the first configuration specifies that frequency hopping for uplink signal transmissions (e.g., PUCCH transmissions, PUSCH transmissions, etc.) is disabled. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when transmitting on an uplink channel (e.g., for transmission on an uplink channel) (e.g., PUCCH, PUSCH, etc.).

In some examples, the first configuration specifies that Physical Uplink Control Channel (PUCCH) hopping is disabled. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when transmitting on the PUCCH.

In some examples, the first configuration may include a first Resource Block (RB) offset of a Physical Random Access Channel (PRACH) occasion defined within the first RF band, and the first RB offset is different from a second RB offset of a PRACH occasion defined within the second RF band. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the first RB offset is used for transmission on the PRACH.

In some examples, the first configuration specifies disabling Frequency Division Multiplexing (FDM) for Physical Random Access Channel (PRACH) resource allocation. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of frequency division multiplexed (FDMed) resources is abandoned when transmitted on the PRACH.

In some examples, the first configuration specifies that at least one specified Physical Random Access Channel (PRACH) format is disabled. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of the at least one specified PRACH format is abandoned when transmitted on the PRACH.

In some examples, the first configuration specifies disabling Physical Uplink Control Channel (PUCCH) hopping for hybrid automatic repeat request (HARQ) feedback. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when the HARQ feedback is transmitted.

In some examples, the user device may send a capability message indicating that the user device supports communications on the first RF band.

Fig. 18 is a flow chart illustrating an example method 1800 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1800 for wireless communication may be performed by the UE 1600 shown in fig. 16. In some examples, the method 1800 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1802, the user equipment may determine that the user equipment supports a first minimum bandwidth size defined for a first Radio Frequency (RF) band, wherein the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the UE. For example, the capability circuitry 1642 shown and described above in connection with fig. 16 may provide means to determine that the user device supports a first minimum bandwidth size defined for a first Radio Frequency (RF) band.

In some examples, the first minimum bandwidth size is a first minimum bandwidth portion size and the second minimum bandwidth size is a second minimum bandwidth portion size. In some examples, the second minimum bandwidth portion size is 5 megahertz (MHz) and the first minimum bandwidth portion size is 3MHz or 3.6MHz.

In some examples, the first radio frequency band is at least one of a future railway mobile communication system band or a broadband service band. In some examples, the first radio frequency band is a 900 megahertz (MHz) band.

At block 1804, the user device may select a first configuration based on the first minimum bandwidth size. For example, the configuration circuit 1643 shown and described above in connection with fig. 16 may provide components to select the first configuration based on the first minimum bandwidth size.

At block 1806, the user device may communicate with a base station via the first RF band according to the first configuration. For example, the communication and processing circuitry 1641 and transceiver 1610 shown and described above in connection with fig. 16 may provide means to communicate with a base station via the first RF band according to the first configuration.

In some examples, the first configuration may include a minimum number of Resource Blocks (RBs) for a channel state information-reference signal (CSI-RS). In some examples, communicating with the base station via the first RF band according to the first configuration may include: the CSI-RS is received via at least the minimum number of RBs.

In some examples, the first configuration may include a minimum number of Resource Blocks (RBs) for Tracking Reference Signals (TRSs). In some examples, communicating with the base station via the first RF band according to the first configuration may include: the TRS is received via at least the minimum number of RBs.

In some examples, the first configuration specifies that transmission of Tracking Reference Signals (TRSs) is disabled. In some examples, a user equipment may determine a quasi co-location (QCL) relationship for a Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS) based on a Synchronization Signal Block (SSB) instead of the TRS.

In some examples, the first configuration specifies that use of at least one specified Modulation and Coding Scheme (MCS) value is limited. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of the at least one specified modulation and coding scheme value is relinquished when communicating with the base station via the first RF band.

In some examples, the first configuration may include a first hopping pattern defined for the first RF band for uplink signal transmission (e.g., PUCCH transmission, PUSCH transmission, etc.), and the first hopping pattern is different from a second hopping pattern defined for the second RF band. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the first hopping pattern is used for transmission on an uplink channel (e.g., PUCCH, PUSCH, etc.).

In some examples, the first configuration may include a first Physical Uplink Control Channel (PUCCH) hopping pattern defined for the first RF band, and the first PUCCH hopping pattern is different from a second PUCCH hopping pattern defined for the second RF band. In some examples, communicating with the base station via the first RF band according to the first configuration may include: and transmitting on the PUCCH by using the first PUCCH hopping pattern.

In some examples, the first configuration specifies that frequency hopping for uplink signal transmissions (e.g., PUCCH transmissions, PUSCH transmissions, etc.) is disabled. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when transmitting on an uplink channel (e.g., PUCCH, PUSCH, etc.).

In some examples, the first configuration specifies that Physical Uplink Control Channel (PUCCH) hopping is disabled. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when transmitting on the PUCCH.

In some examples, the first configuration may include a first Resource Block (RB) offset of a Physical Random Access Channel (PRACH) occasion defined within the first RF band, and the first RB offset is different from a second RB offset of a PRACH occasion defined within the second RF band. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the first RB offset is used for transmission on the PRACH.

In some examples, the first configuration specifies disabling Frequency Division Multiplexing (FDM) for Physical Random Access Channel (PRACH) resource allocation. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of frequency division multiplexed resources is abandoned when transmitted on the PRACH.

In some examples, the first configuration specifies that at least one specified Physical Random Access Channel (PRACH) format is disabled. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of the at least one specified PRACH format is abandoned when transmitted on the PRACH.

In some examples, the first configuration specifies disabling Physical Uplink Control Channel (PUCCH) hopping for hybrid automatic repeat request (HARQ) feedback. In some examples, communicating with the base station via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when the HARQ feedback is transmitted.

In some examples, the user device may send a capability message indicating that the user device supports communications on the first RF band.

Fig. 19 is a flow chart illustrating an example method 1900 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, method 1900 for wireless communication may be performed by UE 1600 shown in fig. 16. In some examples, method 1900 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 1902, a user device may identify a first Radio Frequency (RF) band supported by a base station. For example, the capability circuitry 1642 shown and described above in connection with fig. 16, along with the communication and processing circuitry 1641 and transceiver 1610, may provide means to identify a first Radio Frequency (RF) band supported by a base station.

At block 1904, the user equipment may identify a first minimum bandwidth portion (BWP) size defined for the first RF band, wherein the first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available to the UE, wherein the second RF band is wider than the first RF band. For example, the configuration circuit 1643 shown and described above in connection with fig. 16 may provide means to identify a first minimum bandwidth portion (BWP) size defined for the first RF band.

At block 1906, the user equipment may communicate with the base station via the first RF band according to the first minimum BWP size. For example, the communication and processing circuitry 1641 and transceiver 1610 shown and described above in connection with fig. 16 may provide means to communicate with the base station via the first RF band according to the first minimum BWP size.

In some examples, the first minimum BWP size is a minimum uplink BWP size. In some examples, communicating with the base station via the first RF band according to a first minimum BWP size may include: information is transmitted to the base station using at least the minimum uplink BWP size.

In some examples, the first minimum BWP size is a minimum downlink BWP size. In some examples, communicating with the base station via the first RF band according to a first minimum BWP size may include: information is received from the base station using at least the minimum downlink BWP size.

In some examples, a user equipment includes: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: a first minimum bandwidth size defined for a first Radio Frequency (RF) band is determined to be supported by the user equipment. The first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. The processor and the memory may be further configured to: selecting a first configuration based on the first minimum bandwidth size; and communicating with the base station via the first RF band according to the first configuration.

In some examples, a method for wireless communication at a user device may include: a first minimum bandwidth size defined for a first Radio Frequency (RF) band is determined to be supported by the user equipment. The first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. The method may further comprise: selecting a first configuration based on the first minimum bandwidth size; and communicating with the base station via the first RF band according to the first configuration.

In some examples, a user device may include: means for determining that the user equipment supports a first minimum bandwidth size defined for a first Radio Frequency (RF) band. The first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. The user equipment may further include: means for selecting a first configuration based on the first minimum bandwidth size; and means for communicating with the base station via the first RF band according to the first configuration.

In some examples, an article of manufacture for use by a user device may include a computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of the user device to: a first minimum bandwidth size defined for a first Radio Frequency (RF) band is determined to be supported by the user equipment. The first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. The computer-readable medium may also have instructions stored therein that are executable by one or more processors of the user device to: selecting a first configuration based on the first minimum bandwidth size; and communicating with the base station via the first RF band according to the first configuration.

In some examples, a user equipment includes: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: identifying a first Radio Frequency (RF) band supported by the base station; and identifying a first minimum bandwidth portion (BWP) size defined for the first RF band. The first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available for the user equipment. The second RF band is wider than the first RF band. The processor and the memory may be configured to: communicate with the base station via the first RF band according to the first minimum BWP size.

In some examples, a method for wireless communication at a user device may include: identifying a first Radio Frequency (RF) band supported by the base station; and identifying a first minimum bandwidth portion (BWP) size defined for the first RF band. The first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available for the user equipment. The second RF band is wider than the first RF band. The method may further comprise: communicate with the base station via the first RF band according to the first minimum BWP size.

In some examples, a user device may include means for: identifying a first Radio Frequency (RF) band supported by the base station; and identifying a first minimum bandwidth portion (BWP) size defined for the first RF band. The first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available for the user equipment. The second RF band is wider than the first RF band. The user equipment may further comprise means for: communicate with the base station via the first RF band according to the first minimum BWP size.

In some examples, an article of manufacture for use by a user device may include a computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of the user device to: identifying a first Radio Frequency (RF) band supported by the base station; and identifying a first minimum bandwidth portion (BWP) size defined for the first RF band. The first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available for the user equipment. The second RF band is wider than the first RF band. The computer-readable medium may also have instructions stored therein that are executable by one or more processors of the user device to: communicate with the base station via the first RF band according to the first minimum BWP size.

In one configuration, UE 1600 includes: means for receiving an indication that a base station supports a first Radio Frequency (RF) band; and means for communicating with the base station via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size being smaller than a second minimum bandwidth size defined for a second RF band available to the user equipment. In one aspect, the foregoing components may be a processor 1604, shown in fig. 16, configured to perform the functions recited by the foregoing components (e.g., as discussed above). In another aspect, the aforementioned means may be circuitry or any apparatus configured to perform the functions recited by the aforementioned means.

Of course, in the above examples, the circuitry included in the processor 1604 is provided as an example only, and other means for performing the described functions may be included within aspects of the disclosure, including but not limited to instructions stored in the computer-readable medium 1606, or any other suitable device or means described in any one or more of fig. 1, 2, 5, and 16 and utilizing, for example, the methods and/or algorithms described herein with respect to fig. 17-19.

Fig. 20 is a conceptual diagram illustrating an example of a hardware implementation of a Base Station (BS) 2000 employing a processing system 2014. In some implementations, BS 2000 may correspond to any BS (e.g., a gNB) or scheduling entity shown in any of fig. 1, 2, and 5.

According to various aspects of the disclosure, the processing system 2014 may be utilized to implement elements or any portions of elements or any combination of elements. The processing system may include one or more processors 2004. The processing system 2014 may be substantially identical to the processing system 1614 illustrated in fig. 16, including a bus interface 2008, a bus 2002, a memory 2005, a processor 2004, and a computer readable medium 2006. The memory 2005 may store configuration information 2015 (e.g., configuration information specified by a standard) that is used by the processor 2004 in cooperation with the transceiver 2010 for narrowband wireless communications. Further, BS 2000 may include an interface 2030 (e.g., a network interface) that provides means for communicating with at least one other device within the core network and with at least one radio access network.

BS 2000 may be configured to perform any one or more of the operations described herein (e.g., as described above in connection with fig. 1-15 and below in connection with fig. 21-23). In some aspects of the present disclosure, the processor 2004 used in the BS 2000 may include circuitry configured for various functions.

The processor 2004 may be configured to generate, schedule, and modify resource allocations or grants of time-frequency resources (e.g., a set of one or more resource elements). For example, processor 2004 may schedule time-frequency resources within a plurality of Time Division Duplex (TDD) and/or Frequency Division Duplex (FDD) subframes, slots, and/or minislots to carry user data traffic and/or control information to and/or from a plurality of UEs.

The processor 2004 may be configured to schedule resources (e.g., on a plurality of downlink beams for downlink beam scanning) for transmission of downlink reference signals (e.g., SSBs or CSI-RSs). The processor 2004 may also be configured to schedule resources (e.g., on multiple uplink beams for uplink beam scanning) for uplink transmissions of uplink reference signals (e.g., SRS). The processor 2004 may also be configured to schedule resources that the UE may use to transmit uplink signals. For example, the resources may be scheduled for PUCCH, PUSCH, PRACH occasion or transmission of RRC messages. In some examples, the processor 2004 may be configured to schedule PUSCH resources in response to receiving a scheduling request from a UE.

In some aspects of the disclosure, the processor 2004 may include communication and processing circuitry 2041. The communication and processing circuitry 2044 may be configured to communicate with a UE. The communication and processing circuitry 2041 may include one or more hardware components that provide a physical structure that performs various processing related to communication (e.g., signal reception and/or signal transmission) as described herein. The communication and processing circuitry 2041 may also include one or more hardware components that provide a physical structure that performs various processing related to signal processing (e.g., processing received signals and/or processing signals for transmission) as described herein. The communication and processing circuitry 2041 may also be configured to execute communication and processing software 2051, which is included on the computer readable medium 2006, to implement one or more of the functions described herein.

The communication and processing circuitry 2041 may also be configured to receive uplink signals from the UE. The uplink signal may include, for example, PUCCH, PUSCH, SRS, DMRS or PRACH. In some examples, the uplink signal may take the form of a MAC-CE carried in PUSCH, UCI in PUCCH or PUSCH, a random access message, or an RRC message. The communication and processing circuitry 2041 may also be configured to receive a scheduling request for uplink grant of PUSCH from the UE (e.g., via UCI in PUCCH).

In some examples (e.g., where BS 2000 supports both narrowband and wideband communications), communications and processing circuitry 2041 may also be configured to generate and transmit downlink beamformed signals at millimeter wave frequencies or sub-6 GHz frequencies via transceiver 2010 and antenna array 2020. For example, the communication and processing circuitry 2041 may be configured to transmit respective downlink reference signals (e.g., SSBs or CSI-RSs) to the UE on each of the plurality of downlink beams via at least one first antenna panel of the antenna array 2020.

Communication and processing circuitry 2041 may also be configured to receive uplink signals via transceiver 2010 and antenna array 2020 on one or more uplink receive beams at millimeter wave frequencies or sub-6 GHz frequencies. For example, the communication and processing circuitry 2041 may be configured to receive uplink signals on one or more uplink receive beams via at least one first antenna panel of the antenna array 2020.

In some embodiments in which communication involves receiving information, the communication and processing circuitry 2041 may obtain the information from components of the BS 2000 (e.g., from the transceiver 2010 that receives the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuit 2041 may output information to another component of the processor 2004, the memory 2005, or the bus interface 2008. In some examples, the communication and processing circuitry 2041 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry 2041 may receive information via one or more channels. In some examples, the communication and processing circuitry 2041 may include functionality for a receiving component. In some examples, the communication and processing circuitry 2041 may include functionality for decoding.

In some implementations in which communication involves issuing (e.g., sending) information, the communication and processing circuitry 2041 may obtain the information (e.g., from the processor 2004, the memory 2005, or another component of the bus interface 2008), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 2041 may output information to the transceiver 2010 (e.g., which transmits the information via radio frequency signaling or some other type of signaling appropriate for the applicable communication medium). In some examples, the communication and processing circuitry 2041 may emit one or more of signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry 2041 may send out information via one or more channels. In some examples, the communication and processing circuitry 2041 may include functionality for issuing components (e.g., components for transmitting). In some examples, the communication and processing circuitry 2041 may include functionality for encoding components.

In some examples, the communication and processing circuitry 2041 may include functionality for communicating with a user device via a first RF band according to a first configuration. For example, the communication and processing circuitry 2041 may cooperate with the transceiver 2010 to transmit information to the UE via a narrowband downlink channel and/or receive information from the UE via a narrowband uplink channel using one or more parameters or aspects specified by the first configuration (e.g., BWP size, etc., as discussed herein).

The processor 2004 may include a capability circuit 2042 configured to perform capability-related operations as discussed herein (e.g., one or more of the operations described in connection with fig. 6-15). The capability circuitry 2042 may be configured to execute capability software 2052, which is included on the computer readable medium 2006, to implement one or more of the functions described herein.

In some examples, the capability circuitry 2042 may include functionality for transmitting an indication that the base station 2000 supports a particular RF band. For example, the capability circuitry 2042, along with the communication and processing circuitry 2041 and transceiver 2010, may broadcast SIBs or some other type of message that indicates that the base station 2000 supports narrowband communications.

In some examples, the capability circuitry 2042 may include functionality to determine that the UE supports a minimum BWP size for narrowband wireless communications. For example, the capability circuitry 2042, along with the communication and processing circuitry 2041 and transceiver 2010, may receive a capability message from the UE indicating that the UE is a multi-band UE supporting narrowband communications (e.g., less than 5MHz bandwidth) and/or wideband communications (e.g., 5MHz or higher bandwidth), or indicating that the UE is a reduced capability UE (e.g., a UE supporting only narrowband communications).

In some examples, the capability circuitry 2042 may include functionality for determining that the UE supports an RF band. For example, the capability circuitry 2042, along with the communication and processing circuitry 2041 and transceiver 2010, may receive a capability message from a UE indicating that the UE is a multi-band UE supporting narrowband communications (e.g., less than 5MHz in bandwidth) and/or wideband communications (e.g., 5MHz or higher in bandwidth), or indicating that the UE is a reduced capability UE (e.g., a UE supporting only narrowband communications).

The processor 2004 may include a configuration circuit 2043 configured to perform configuration-related operations as discussed herein (e.g., one or more of the operations described in connection with fig. 6-15). The configuration circuit 2043 may be configured to execute configuration software 2053, which is included on the computer readable medium 2006, to implement one or more of the functions described herein.

In some examples, the configuration circuit 2043 may include functionality for selecting components of the configuration. For example, the configuration circuitry 2043 may obtain configuration information from the memory 2005 that defines for narrowband communications (e.g., as specified by a wireless communication standard and/or as received from the gNB) that specifies certain parameters and/or actions to be taken (or not taken) for downlink communications (e.g., CSI-RS and/or TRS), uplink communications (e.g., PUCCH), random access, or a combination thereof, for example.

In some examples, the configuration circuit 2043 may include functionality for identifying BWP-sized components. For example, the configuration circuit 2043 shown and described above in connection with fig. 20 may obtain configuration information defined for narrowband communication (e.g., as specified by the wireless communication standard) from the memory 2005, the configuration information specifying a minimum BWP size to be used for narrowband communication.

Fig. 21 is a flow chart illustrating an example method 2100 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 2100 for wireless communication may be performed by the BS 2000 shown in fig. 20. In some examples, the method 2100 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 2102, the base station may transmit an indication that the base station supports a first Radio Frequency (RF) band. For example, the capability circuitry 2042 shown and described above in connection with fig. 20, along with the communication and processing circuitry 2041 and transceiver 2010, may provide means for transmitting an indication that the base station supports a first Radio Frequency (RF) band.

At block 2104, the base station may communicate with a user device via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size being less than a second minimum bandwidth size defined for a second RF band available to the user device. For example, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide components to communicate with a user device via the first RF band in accordance with a first configuration based on a first minimum bandwidth size defined for the first RF band.

In some examples, the first minimum bandwidth size is a first minimum bandwidth portion size and the second minimum bandwidth size is a second minimum bandwidth portion size. In some examples, the second minimum bandwidth portion size is 5 megahertz (MHz) and the first minimum bandwidth portion size is 3MHz or 3.6MHz.

In some examples, the first radio frequency band is at least one of a future railway mobile communication system band or a broadband service band. In some examples, the first radio frequency band is a 900 megahertz (MHz) band.

In some examples, the base station may determine that the user equipment supports the first minimum bandwidth portion size. In some examples, determining that the user equipment supports the first minimum bandwidth portion size may include: a capability message is received from the user equipment indicating that the user equipment supports communication on the first RF band.

In some examples, the first configuration may include a minimum number of Resource Blocks (RBs) for a channel state information-reference signal (CSI-RS). In some examples, communicating with the user device via the first RF band according to the first configuration may include: the CSI-RS is transmitted via at least the minimum number of RBs.

In some examples, the first configuration may include a minimum number of Resource Blocks (RBs) for Tracking Reference Signals (TRSs). In some examples, communicating with the user device via the first RF band according to the first configuration may include: the TRS is transmitted via at least the minimum number of RBs.

In some examples, the first configuration specifies that transmission of Tracking Reference Signals (TRSs) is disabled. In some examples, the method may further comprise: a quasi co-location (QCL) relationship for a Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS) is determined based on a Synchronization Signal Block (SSB) instead of the TRS.

In some examples, the first configuration specifies that use of at least one specified Modulation and Coding Scheme (MCS) value is limited. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of the at least one specified modulation and coding scheme value is abandoned when transmitted to the user equipment via the first RF band.

In some examples, the first configuration may include a first hopping pattern defined for the first RF band for uplink signal transmission (e.g., PUCCH transmission, PUSCH transmission, etc.), and the first hopping pattern is different from a second hopping pattern defined for the second RF band. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the first hopping pattern is used for reception on an uplink channel (e.g., PUCCH, PUSCH, etc.).

In some examples, the first configuration may include a first Physical Uplink Control Channel (PUCCH) hopping pattern defined for the first RF band, and the first PUCCH hopping pattern is different from a second PUCCH hopping pattern defined for the second RF band. In some examples, communicating with the user device via the first RF band according to the first configuration may include: and receiving on the PUCCH using the first PUCCH hopping pattern.

In some examples, the first configuration specifies that frequency hopping for uplink signal transmissions (e.g., PUCCH transmissions, PUSCH transmissions, etc.) is disabled. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when received on an uplink channel (e.g., PUCCH, PUSCH, etc.).

In some examples, the first configuration specifies that Physical Uplink Control Channel (PUCCH) hopping is disabled. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when received on the PUCCH.

In some examples, the first configuration may include a first Resource Block (RB) offset of a Physical Random Access Channel (PRACH) occasion defined within a first RF band, and the first RB offset is different from a second RB offset of a PRACH occasion defined within the second RF band. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the first RB offset is used for reception on the PRACH.

In some examples, the first configuration specifies disabling Frequency Division Multiplexing (FDM) for Physical Random Access Channel (PRACH) resource allocation. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of frequency division multiplexed resources is abandoned when received on the PRACH.

In some examples, the first configuration specifies that at least one specified Physical Random Access Channel (PRACH) format is disabled.

In some examples, the first configuration specifies disabling Physical Uplink Control Channel (PUCCH) hopping for hybrid automatic repeat request (HARQ) feedback. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when receiving HARQ feedback.

Fig. 22 is a flowchart illustrating an example method 2200 for wireless communication in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 2200 for wireless communication may be performed by the BS 2000 shown in fig. 20. In some examples, the method 2200 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 2202, the base station may determine that the user equipment supports a first minimum bandwidth size defined for a first Radio Frequency (RF) band, wherein the first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. For example, the capability circuitry 2042 shown and described above in connection with fig. 20 may provide means to determine that the user device supports a first minimum bandwidth size defined for a first Radio Frequency (RF) band.

In some examples, the first minimum bandwidth size is a first minimum bandwidth portion size and the second minimum bandwidth size is a second minimum bandwidth portion size. In some examples, the second minimum bandwidth portion size is 5 megahertz (MHz) and the first minimum bandwidth portion size is 3MHz or 3.6MHz.

In some examples, the first radio frequency band is at least one of a future railway mobile communication system band or a broadband service band. In some examples, the first radio frequency band is a 900 megahertz (MHz) band.

In some examples, determining that the user equipment supports the first minimum bandwidth portion size may include: a capability message is received from the user equipment indicating that the user equipment supports communication on the first RF band.

At block 2204, the base station may select a first configuration based on the first minimum bandwidth size. For example, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide components to select a first configuration based on the first minimum bandwidth size.

At block 2206, the base station may communicate with the user equipment via a first RF band according to the first configuration. For example, the communication and processing circuitry 2041 and transceiver 2010 shown and described above in connection with fig. 20 may provide components to communicate with the user equipment via the first RF band in accordance with the first configuration.

In some examples, the first configuration may include a minimum number of Resource Blocks (RBs) for a channel state information-reference signal (CSI-RS). In some examples, communicating with the user device via the first RF band according to the first configuration may include: the CSI-RS is transmitted via at least the minimum number of RBs.

In some examples, the first configuration may include a minimum number of Resource Blocks (RBs) for Tracking Reference Signals (TRSs). In some examples, communicating with the user device via the first RF band according to the first configuration may include: the TRS is transmitted via at least the minimum number of RBs.

In some examples, the first configuration specifies that transmission of Tracking Reference Signals (TRSs) is disabled. In some examples, the method may further comprise: a quasi co-location (QCL) relationship for a Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS) is determined based on a Synchronization Signal Block (SSB) instead of the TRS.

In some examples, the first configuration specifies that use of at least one specified Modulation and Coding Scheme (MCS) value is limited. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of the at least one specified modulation and coding scheme value is abandoned when transmitted to the user equipment via the first RF band.

In some examples, the first configuration may include a first hopping pattern defined for the first RF band for uplink signal transmission (e.g., PUCCH transmission, PUSCH transmission, etc.), and the first hopping pattern is different from a second hopping pattern defined for the second RF band. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the first hopping pattern is used for reception on an uplink channel (e.g., PUCCH, PUSCH, etc.).

In some examples, the first configuration may include a first Physical Uplink Control Channel (PUCCH) hopping pattern defined for the first RF band, and the first PUCCH hopping pattern is different from a second PUCCH hopping pattern defined for the second RF band. In some examples, communicating with the user device via the first RF band according to the first configuration may include: and receiving on the PUCCH using the first PUCCH hopping pattern.

In some examples, the first configuration specifies that frequency hopping for uplink signal transmissions (e.g., PUCCH transmissions, PUSCH transmissions, etc.) is disabled. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when received on an uplink channel (e.g., PUCCH, PUSCH, etc.).

In some examples, the first configuration specifies that Physical Uplink Control Channel (PUCCH) hopping is disabled. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when received on the PUCCH.

In some examples, the first configuration may include a first Resource Block (RB) offset of a Physical Random Access Channel (PRACH) occasion defined within a first RF band, and the first RB offset is different from a second RB offset of a PRACH occasion defined within the second RF band. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the first RB offset is used for reception on the PRACH.

In some examples, the first configuration specifies disabling Frequency Division Multiplexing (FDM) for Physical Random Access Channel (PRACH) resource allocation. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of frequency division multiplexed resources is abandoned when received on the PRACH.

In some examples, the first configuration specifies that at least one specified Physical Random Access Channel (PRACH) format is disabled.

In some examples, the first configuration specifies disabling Physical Uplink Control Channel (PUCCH) hopping for hybrid automatic repeat request (HARQ) feedback. In some examples, communicating with the user device via the first RF band according to the first configuration may include: the use of frequency hopping is abandoned when receiving HARQ feedback.

Fig. 23 is a flow chart illustrating an example method 2300 for wireless communication, according to some aspects of the disclosure. As described herein, some or all of the illustrated features may be omitted from certain embodiments within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 2300 for wireless communication may be performed by the BS 2000 shown in fig. 20. In some examples, method 2300 for wireless communication may be performed by any suitable means or component for performing the functions or algorithms described below.

At block 2302, the base station may determine that the user equipment supports a first Radio Frequency (RF) band. For example, the capability circuitry 2042 shown and described above in connection with fig. 20, along with the communication and processing circuitry 2041 and transceiver 2010, may provide components to determine that the user equipment supports a first Radio Frequency (RF) band.

At block 2304, the base station may identify a first minimum bandwidth portion (BWP) size defined for the first RF band, wherein the first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available to the user equipment, wherein the second RF band is wider than the first RF band. For example, the configuration circuit 2043 shown and described above in connection with fig. 20 may provide means to identify a first minimum bandwidth portion (BWP) size defined for the first RF band.

At block 2306, the base station may communicate with the user equipment via the first RF band according to the first minimum BWP size. For example, the communication and processing circuitry 2041 and transceiver 2010 shown and described above in connection with fig. 20 may provide components to communicate with the user equipment via the first RF band in accordance with the first minimum BWP size.

In some examples, the first minimum BWP size is a minimum uplink BWP size. In some examples, communicating with the user equipment via the first RF band according to the first minimum BWP size may include: information is received from the user equipment using at least the minimum uplink BWP size.

In some examples, the first minimum BWP size is a minimum downlink BWP size. In some examples, communicating with the user equipment via the first RF band according to the first minimum BWP size may include: information is transmitted to the user equipment using at least the minimum downlink BWP size.

In some examples, a base station may include: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: a first minimum bandwidth size that is defined for a first Radio Frequency (RF) band is determined to be supported by a user equipment. The first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. The processor and the memory may be configured to: selecting a first configuration based on the first minimum bandwidth size; and communicating with the user equipment via the first RF band according to the first configuration.

In some examples, a method for wireless communication at a base station may include: a first minimum bandwidth size defined for a first Radio Frequency (RF) band is determined to be supported by the user equipment. The first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. The method may further comprise: selecting a first configuration based on the first minimum bandwidth size; and communicating with the user equipment via the first RF band according to the first configuration.

In some examples, a base station may include: means for determining that a user equipment supports a first minimum bandwidth size defined for a first Radio Frequency (RF) band. The first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. The base station may further include: means for selecting a first configuration based on the first minimum bandwidth size; and means for communicating with the user equipment via the first RF band according to the first configuration.

In some examples, an article of manufacture for use by a base station may include a computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of the base station to: a first minimum bandwidth size that is defined for a first Radio Frequency (RF) band is determined to be supported by a user equipment. The first minimum bandwidth size is less than a second minimum bandwidth size defined for a second RF band available to the user equipment. The computer-readable medium may also have instructions stored therein that are executable by one or more processors of the base station to: selecting a first configuration based on the first minimum bandwidth size; and communicating with the user equipment via the first RF band according to the first configuration.

In some examples, a base station may include: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to: determining that a user equipment supports a first Radio Frequency (RF) band; and identifying a first minimum bandwidth portion (BWP) size defined for the first RF band. The first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available for the user equipment. The second RF band is wider than the first RF band. The processor and the memory may be further configured to: communication with the user equipment via the first RF band is performed according to the first minimum BWP size.

In some examples, a method for wireless communication at a base station may include: determining that a user equipment supports a first Radio Frequency (RF) band; and identifying a first minimum bandwidth portion (BWP) size defined for the first RF band. The first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available for the user equipment. The second RF band is wider than the first RF band. The method may further comprise: communication with the user equipment via the first RF band is performed according to the first minimum BWP size.

In some examples, a base station may include means for: determining that a user equipment supports a first Radio Frequency (RF) band; and identifying a first minimum bandwidth portion (BWP) size defined for the first RF band. The first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available for the user equipment. The second RF band is wider than the first RF band. The base station may further comprise means for: communication with the user equipment via the first RF band is performed according to the first minimum BWP size.

In some examples, an article of manufacture for use by a base station may include a computer-readable medium having instructions stored therein, the instructions being executable by one or more processors of the base station to: determining that a user equipment supports a first Radio Frequency (RF) band; and identifying a first minimum bandwidth portion (BWP) size defined for the first RF band. The first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available for the user equipment. The second RF band is wider than the first RF band. The computer-readable medium may also have instructions stored therein that are executable by one or more processors of the base station to: communication with the user equipment via the first RF band is performed according to the first minimum BWP size.

In one configuration, the base station 2000 includes: means for transmitting an indication that the base station supports a first Radio Frequency (RF) band; and means for communicating with the user equipment via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size being smaller than a second minimum bandwidth size defined for a second RF band available to the user equipment. In one aspect, the foregoing components may be the processor 2004 shown in fig. 20 configured to perform the functions recited by the foregoing components (e.g., as discussed above). In another aspect, the aforementioned means may be circuitry or any apparatus configured to perform the functions recited by the aforementioned means.

Of course, in the above examples, the circuitry included in the processor 2004 is provided as an example only, and other means for performing the described functions may be included in aspects of the disclosure, including but not limited to instructions stored in the computer-readable medium 2006, or any other suitable device or means described in any one or more of fig. 1, 2, 5, and 20 and utilizing, for example, the methods and/or algorithms described herein with respect to fig. 21-23.

The methods shown in fig. 17-19 and 21-23 may include additional aspects, such as any single aspect or any combination of aspects of one or more other processes described below and/or in conjunction with other processes described elsewhere herein. The following provides an overview of several aspects of the disclosure.

Aspect 1: a method for wireless communication at a user device, the method comprising: receiving an indication that the base station supports a first Radio Frequency (RF) band; and communicating with a base station via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size being smaller than a second minimum bandwidth size defined for a second RF band available to the user equipment.

Aspect 2: the method according to aspect 1, wherein: the first minimum bandwidth size is a first minimum bandwidth portion size; and the second minimum bandwidth size is a second minimum bandwidth portion size.

Aspect 3: the method according to aspect 2, wherein: the second minimum bandwidth portion size is 5 megahertz (MHz); and the first minimum bandwidth portion size is 3MHz or 3.6MHz.

Aspect 4: the method according to any one of aspects 1 to 3, wherein the first configuration comprises a minimum number of Resource Blocks (RBs) for a channel state information-reference signal (CSI-RS).

Aspect 5: the method according to aspect 4, wherein communicating with the base station via the first RF band according to the first configuration comprises: the CSI-RS is received via at least the minimum number of RBs.

Aspect 6: the method according to any one of aspects 1 to 5, wherein the first configuration comprises a minimum number of Resource Blocks (RBs) for tracking a reference signal (TRS).

Aspect 7: the method of aspect 6, wherein communicating with the base station via the first RF band according to the first configuration comprises: the TRS is received via at least the minimum number of RBs.

Aspect 8: the method according to any one of aspects 1 to 5, wherein the first configuration specifies that transmission of Tracking Reference Signals (TRSs) is disabled.

Aspect 9: the method according to aspect 8, further comprising: a quasi co-location (QCL) relationship for a Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS) is determined based on a Synchronization Signal Block (SSB) instead of the TRS.

Aspect 10: the method according to any one of aspects 1 to 9, wherein the first configuration specifies that use of at least one specified Modulation and Coding Scheme (MCS) value is limited.

Aspect 11: the method of aspect 10, wherein communicating with the base station via the first RF band according to the first configuration comprises: the use of the at least one specified modulation and coding scheme value is relinquished when communicating with the base station via the first RF band.

Aspect 12: the method according to any one of aspects 1 to 11, wherein: the first configuration includes a first frequency hopping pattern for uplink signal transmission defined for the first RF band; and the first frequency hopping pattern is different from a second frequency hopping pattern defined for the second RF band.

Aspect 13: the method of aspect 12, wherein communicating with the base station via the first RF band according to the first configuration comprises: and transmitting on an uplink channel using the first hopping pattern.

Aspect 14: the method according to any one of aspects 1 to 11, wherein the first configuration specifies that frequency hopping for uplink signal transmission is disabled.

Aspect 15: the method of aspect 14, wherein communicating with the base station via the first RF band according to the first configuration comprises: the use of frequency hopping is abandoned when transmitting on the uplink channel.

Aspect 16: the method according to any one of aspects 1 to 15, wherein: the first configuration includes a first Resource Block (RB) offset of a first Physical Random Access Channel (PRACH) occasion defined within the first RF band; and the first RB offset is different from a second RB offset of a second PRACH occasion defined within the second RF band.

Aspect 17: the method of aspect 16, wherein communicating with the base station via the first RF band according to the first configuration comprises: the first RB offset is used for transmission on the PRACH.

Aspect 18: the method according to any one of aspects 1 to 17, wherein the first configuration specifies disabling Frequency Division Multiplexing (FDM) for Physical Random Access Channel (PRACH) resource allocation.

Aspect 19: the method of aspect 18, wherein communicating with the base station via the first RF band according to the first configuration comprises: the use of frequency division multiplexed resources is abandoned when transmitted on the PRACH.

Aspect 20: the method according to any one of aspects 1 to 19, wherein the first configuration specifies that at least one specified Physical Random Access Channel (PRACH) format is disabled.

Aspect 21: the method of aspect 20, wherein communicating with the base station via the first RF band according to the first configuration comprises: the use of the at least one specified PRACH format is abandoned when transmitted on the PRACH.

Aspect 22: the method according to any one of aspects 1 to 21, wherein the first configuration specifies disabling Physical Uplink Control Channel (PUCCH) hopping for hybrid automatic repeat request (HARQ) feedback.

Aspect 23: the method of aspect 22, wherein communicating with the base station via the first RF band according to the first configuration comprises: the use of frequency hopping is abandoned when the HARQ feedback is transmitted.

Aspect 24: the method according to any one of aspects 1 to 23, further comprising: a capability message is sent indicating that the user equipment supports communication on the first RF band.

Aspect 25: the method according to any one of aspects 1 to 24, wherein the first radio frequency band is at least one of a future railway mobile communication system band or a broadband service band.

Aspect 26: the method of any one of aspects 1 to 25, wherein the first radio frequency band is a 900 megahertz (MHz) band.

Aspect 27: a User Equipment (UE), comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 1 through 26.

Aspect 28: an apparatus configured for wireless communication, comprising at least one means for performing any of aspects 1-26.

Aspect 29: a non-transitory computer-readable medium storing computer-executable code comprising code for causing an apparatus to perform any one of aspects 1 to 26.

Aspect 51: a method for wireless communication at a base station, the method comprising: transmitting an indication that the base station supports a first Radio Frequency (RF) band; and communicating with a user device via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size being smaller than a second minimum bandwidth size defined for a second RF band available to the user device.

Aspect 52: the method according to aspect 51, wherein: the first minimum bandwidth size is a first minimum bandwidth portion size; and the second minimum bandwidth size is a second minimum bandwidth portion size.

Aspect 53: the method according to aspect 52, wherein: the second minimum bandwidth portion size is 5 megahertz (MHz); and the first minimum bandwidth portion size is 3MHz or 3.6MHz.

Aspect 54: the method according to any one of aspects 51 to 53, wherein the first configuration comprises a minimum number of Resource Blocks (RBs) for a channel state information-reference signal (CSI-RS).

Aspect 55: the method of aspect 54, wherein communicating with the user equipment via the first RF band according to the first configuration comprises: the CSI-RS is transmitted via at least the minimum number of RBs.

Aspect 56: the method according to any of aspects 51 to 55, wherein the first configuration comprises a minimum number of Resource Blocks (RBs) for tracking a reference signal (TRS).

Aspect 57: the method of aspect 56, wherein communicating with the user equipment via the first RF band according to the first configuration comprises: the TRS is transmitted via at least the minimum number of RBs.

Aspect 58: the method according to any one of aspects 51 to 55, wherein the first configuration specifies that transmission of Tracking Reference Signals (TRSs) is disabled.

Aspect 59: the method according to aspect 58, further comprising: a quasi co-location (QCL) relationship for a Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS) is determined based on a Synchronization Signal Block (SSB) instead of the TRS.

Aspect 60: the method according to any one of aspects 51 to 59, wherein the first configuration specifies that use of at least one specified Modulation and Coding Scheme (MCS) value is limited.

Aspect 61: the method of aspect 60, wherein communicating with the user equipment via the first RF band according to the first configuration comprises: the use of the at least one specified modulation and coding scheme value is abandoned when transmitted to the user equipment via the first RF band.

Aspect 62: the method according to any one of aspects 51 to 61, wherein: the first configuration includes a first frequency hopping pattern for uplink signal transmission defined for the first RF band; and the first frequency hopping pattern is different from a second frequency hopping pattern defined for the second RF band.

Aspect 63: the method of aspect 62, wherein communicating with the user equipment via the first RF band according to the first configuration comprises: the first hopping pattern is used for reception on an uplink channel.

Aspect 64: the method according to any one of aspects 51 to 61, wherein the first configuration specifies that frequency hopping for uplink signal transmission is disabled.

Aspect 65: the method of aspect 64, wherein communicating with the user equipment via the first RF band according to the first configuration comprises: the use of frequency hopping is abandoned when received on the uplink channel.

Aspect 66: the method of any one of aspects 51 to 65, wherein the first configuration comprises a first Resource Block (RB) offset of a first Physical Random Access Channel (PRACH) occasion defined within a first RF band; and the first RB offset is different from a second RB offset of a second PRACH occasion defined within the second RF band.

Aspect 67: the method of aspect 66, wherein communicating with the user equipment via the first RF band according to the first configuration comprises: the first RB offset is used for reception on the PRACH.

Aspect 68: the method according to any one of aspects 51 to 67, wherein the first configuration specifies disabling Frequency Division Multiplexing (FDM) for Physical Random Access Channel (PRACH) resource allocation.

Aspect 69: the method of aspect 68, wherein communicating with the user equipment via the first RF band according to the first configuration comprises: the use of frequency division multiplexed resources is abandoned when received on the PRACH.

Aspect 70: the method according to any one of aspects 51 to 69, wherein the first configuration specifies that at least one specified Physical Random Access Channel (PRACH) format is disabled.

Aspect 71: the method according to any one of aspects 51 to 70, wherein the first configuration specifies disabling Physical Uplink Control Channel (PUCCH) hopping for hybrid automatic repeat request (HARQ) feedback.

Aspect 72: the method of aspect 71, wherein communicating with the user equipment via the first RF band according to the first configuration comprises: the use of frequency hopping is abandoned when receiving HARQ feedback.

Aspect 73: the method according to any one of aspects 51 to 72, further comprising: a capability message is received from the user equipment indicating that the user equipment supports communication on the first RF band.

Aspect 74: the method according to any one of aspects 51 to 73, wherein the first radio frequency band is a future railway mobile communication system band or a broadband service band.

Aspect 75: the method of any of aspects 51 to 74, wherein the first radio frequency band is a 900 megahertz (MHz) band.

Aspect 76: a Base Station (BS), comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any of aspects 51 to 75.

Aspect 77: an apparatus configured for wireless communication, comprising at least one means for performing any of aspects 51 to 75.

Aspect 78: a non-transitory computer-readable medium storing computer-executable code, comprising code for causing an apparatus to perform any one of aspects 51 to 75.

Aspect 101: a method for wireless communication at a user device, the method comprising: identifying a first Radio Frequency (RF) band supported by the base station; identifying a first minimum bandwidth portion (BWP) size defined for the first RF band, wherein the first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available to the user equipment, wherein the second RF band is wider than the first RF band; and communicating with the base station via the first RF band according to the first minimum BWP size.

Aspect 102: the method according to aspect 101, wherein the first minimum BWP size is a minimum uplink BWP size.

Aspect 103: the method according to aspect 102, wherein communicating with the base station via the first RF band according to a first minimum BWP size comprises: information is transmitted to the base station using at least the minimum uplink BWP size.

Aspect 104: the method according to any one of aspects 101 to 103, wherein the first minimum BWP size is a minimum downlink BWP size.

Aspect 105: the method according to aspect 104, wherein communicating with the base station via the first RF band according to a first minimum BWP size comprises: information is received from the base station using at least the minimum downlink BWP size.

Aspect 106: a User Equipment (UE), comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any of aspects 101-105.

Aspect 107: an apparatus configured for wireless communication, comprising at least one means for performing any of aspects 101-105.

Aspect 108: a non-transitory computer-readable medium storing computer-executable code comprising code for causing an apparatus to perform any one of aspects 101 to 105.

Aspect 113: a method for wireless communication at a base station, the method comprising: determining that a user equipment supports a first Radio Frequency (RF) band; identifying a first minimum bandwidth portion (BWP) size defined for the first RF band, wherein the first minimum BWP size is smaller than a second minimum BWP size defined for a second RF band available to the user equipment, wherein the second RF band is wider than the first RF band; and communicating with the user equipment via the first RF band according to the first minimum BWP size.

Aspect 114: the method according to aspect 113, wherein the first minimum BWP size is a minimum uplink BWP size.

Aspect 115: the method of aspect 114, wherein communicating with the user equipment via the first RF band according to the first minimum BWP size comprises: information is received from the user equipment using at least the minimum uplink BWP size.

Aspect 116: the method according to any one of aspects 113-115, wherein the first minimum BWP size is a minimum downlink BWP size.

Aspect 117: the method of aspect 116, wherein communicating with the user equipment via the first RF band according to the first minimum BWP size comprises: information is transmitted to the user equipment using at least the minimum downlink BWP size.

Aspect 118: a Base Station (BS), comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any of aspects 113-117.

Aspect 119: an apparatus configured for wireless communication, comprising at least one means for performing any of aspects 113-117.

Aspect 120: a non-transitory computer-readable medium storing computer-executable code comprising code for causing an apparatus to perform any one of aspects 113 to 117.

Several aspects of a wireless communication network have been presented with reference to example embodiments. As will be readily appreciated by those skilled in the art, the various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

As an example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), evolved Packet System (EPS), universal Mobile Telecommunications System (UMTS), and/or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by third generation partnership project 2 (3 GPP 2), such as CDMA2000 and/or evolution data optimized (EV-DO). Other examples may be implemented within a system employing Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, ultra Wideband (UWB), bluetooth, and/or other suitable systems. The actual telecommunications standards, network architectures, and/or communication standards employed will depend on the particular application and the overall design constraints imposed on the system.

Within this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration. Any embodiment or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. The term "coupled" is used herein to refer to either direct or indirect coupling between two objects. For example, if object a physically contacts object B and object B contacts object C, then objects a and C may be considered to be coupled to each other even though they are not directly physically in contact with each other. For example, a first object may be coupled to a second object even though the first object is never in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to encompass both hardware implementations of electrical devices and conductors which, when connected and configured, are capable of carrying out the functions described in the present disclosure, without limitation of the type of electronic circuitry, and software implementations of information and instructions which, when executed by a processor, are capable of carrying out the functions described in the present disclosure.

One or more of the components, steps, features, and/or functions illustrated in fig. 1-23 may be rearranged and/or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from the novel features disclosed herein. The apparatus, devices, and/or components shown in fig. 1, 2, 5, 16, and 20 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be implemented efficiently in software and/or embedded in hardware.

It should be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of example processes. Based on design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented, unless specifically recited therein.

As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Further, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so forth. Further, "determining" may include parsing, selecting, choosing, establishing, and the like.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" (unless specifically so stated), but rather "one or more". The term "some" means one or more unless specifically stated otherwise. The phrase referring to "at least one" in a list of options refers to any combination of those options, including a single member. As an example, "at least one of: a. b, or c "is intended to encompass: a, a; b; c, performing operation; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element should be construed as a admission that the element is explicitly recited in the specification of the american society of motion 35, volume 112 (f) unless the element is explicitly recited in the section for … …, or in the case of the method claim, the phrase "step for … …".

Claims (30)

1. A user equipment, comprising:

a transceiver;

a memory; and

a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to:

receiving, via the transceiver, an indication that the base station supports a first Radio Frequency (RF) band; and

communicating, via the transceiver, with the base station via the first RF band according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size being smaller than a second minimum bandwidth size defined for a second RF band available to the user equipment.

2. The user equipment of claim 1, wherein:

the first minimum bandwidth size is a first minimum bandwidth portion size; and

the second minimum bandwidth size is a second minimum bandwidth portion size.

3. The user equipment of claim 2, wherein:

the second minimum bandwidth portion size is 5 megahertz (MHz); and

the first minimum bandwidth portion size is 3MHz or 3.6MHz.

4. The user equipment of claim 1, wherein:

the first configuration includes a minimum number of Resource Blocks (RBs) for a channel state information-reference signal (CSI-RS); and

The processor and the memory are further configured to: the CSI-RS is received via at least the minimum number of RBs.

5. The user equipment of claim 1, wherein:

the first configuration includes a minimum number of Resource Blocks (RBs) for tracking a reference signal (TRS); and

the processor and the memory are further configured to: the TRS is received via at least the minimum number of RBs.

6. The user equipment of claim 1, wherein:

the first configuration specifies that transmission of a Tracking Reference Signal (TRS) is disabled; and

the processor and the memory are further configured to: a quasi co-location (QCL) relationship for a Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS) is determined based on a Synchronization Signal Block (SSB) instead of the TRS.

7. The user equipment of claim 1, wherein:

the first configuration specifies that use of at least one specified modulation and coding scheme value is limited; and

the processor and the memory are further configured to: the use of the at least one specified modulation and coding scheme value is relinquished when communicating with the base station via the first RF band.

8. The user equipment of claim 1, wherein:

The first configuration includes a first frequency hopping pattern for uplink signal transmission defined for the first RF band;

the first frequency hopping pattern is different from a second frequency hopping pattern defined for the second RF band; and

the processor and the memory are further configured to: and transmitting on an uplink channel using the first frequency hopping pattern.

9. The user equipment of claim 1, wherein:

the first configuration specifies that frequency hopping for uplink signal transmission is disabled; and

the processor and the memory are further configured to: the use of frequency hopping is abandoned when transmitting on the uplink channel.

10. The user equipment of claim 1, wherein:

the first configuration includes a first Resource Block (RB) offset of a first Physical Random Access Channel (PRACH) occasion defined within the first RF band;

the first RB offset is different from a second RB offset of a second PRACH occasion defined within the second RF band; and

the processor and the memory are further configured to: and transmitting on the PRACH by using the first RB offset.

11. The user equipment of claim 1, wherein:

the first configuration specifies disabling Frequency Division Multiplexing (FDM) for Physical Random Access Channel (PRACH) resource allocation; and

The processor and the memory are further configured to: the use of frequency division multiplexed resources is abandoned when transmitting on the PRACH.

12. The user equipment of claim 1, wherein:

the first configuration specifying that at least one specified Physical Random Access Channel (PRACH) format is disabled; and

the processor and the memory are further configured to: the use of the at least one specified PRACH format is abandoned when transmitting on the PRACH.

13. The user equipment of claim 1, wherein:

the first configuration specifies disabling Physical Uplink Control Channel (PUCCH) hopping for hybrid automatic repeat request (HARQ) feedback; and

the processor and the memory are further configured to: the use of frequency hopping is abandoned when the HARQ feedback is transmitted.

14. The user equipment of claim 1, wherein the processor and the memory are further configured to:

a capability message is sent indicating that the user equipment supports communication on the first RF band.

15. The user equipment of claim 1, wherein the first radio frequency band is a future railway mobile communication system band or a broadband service band.

16. The user equipment of claim 1, wherein the first radio frequency band is a 900 megahertz (MHz) band.

17. A method for wireless communication at a user device, the method comprising:

receiving an indication that the base station supports a first Radio Frequency (RF) band; and

according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size is smaller than a second minimum bandwidth size defined for a second RF band available to the user equipment, communicating with the base station via the first RF band.

18. A base station, comprising:

a transceiver;

a memory; and

a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to:

transmitting, via the transceiver, an indication that the base station supports a first Radio Frequency (RF) band; and

communication with a user device via the first RF band is performed via the transceiver according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size being smaller than a second minimum bandwidth size defined for a second RF band available to the user device.

19. The base station of claim 18, wherein:

the first configuration includes a minimum number of Resource Blocks (RBs) for a channel state information-reference signal (CSI-RS); and

The processor and the memory are further configured to: the CSI-RS is transmitted via at least the minimum number of RBs.

20. The base station of claim 18, wherein:

the first configuration includes a minimum number of Resource Blocks (RBs) for tracking a reference signal (TRS); and

the processor and the memory are further configured to: the TRS is transmitted via at least the minimum number of RBs.

21. The base station of claim 18, wherein:

the first configuration specifies that transmission of a Tracking Reference Signal (TRS) is disabled; and

the processor and the memory are further configured to: a quasi co-location (QCL) relationship for a Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS) is determined based on a Synchronization Signal Block (SSB) instead of the TRS.

22. The base station of claim 18, wherein:

the first configuration specifies that use of at least one specified modulation and coding scheme value is limited; and

the processor and the memory are further configured to: the use of the at least one specified modulation and coding scheme value is abandoned when transmitted to the user equipment via the first RF band.

23. The base station of claim 18, wherein:

The first configuration includes a first frequency hopping pattern for uplink signal transmission defined for the first RF band;

the first frequency hopping pattern is different from a second frequency hopping pattern defined for the second RF band; and

the processor and the memory are further configured to: and receiving on an uplink channel using the first frequency hopping pattern.

24. The base station of claim 18, wherein:

the first configuration specifies that frequency hopping for uplink signal transmission is disabled; and

the processor and the memory are further configured to: the use of frequency hopping is abandoned when receiving on the uplink channel.

25. The base station of claim 18, wherein:

the first configuration includes a first Resource Block (RB) offset of a first Physical Random Access Channel (PRACH) occasion defined within a first RF band;

the first RB offset is different from a second RB offset of a second PRACH occasion defined within the second RF band; and

the processor and the memory are further configured to: and receiving on the PRACH by using the first RB offset.

26. The base station of claim 18, wherein:

the first configuration specifies disabling Frequency Division Multiplexing (FDM) for Physical Random Access Channel (PRACH) resource allocation; and

The processor and the memory are further configured to: the use of frequency division multiplexed resources is abandoned when receiving on the PRACH.

27. The base station of claim 18, wherein the first configuration specifies that at least one specified Physical Random Access Channel (PRACH) format is disabled.

28. The base station of claim 18, wherein:

the first configuration specifies disabling Physical Uplink Control Channel (PUCCH) hopping for hybrid automatic repeat request (HARQ) feedback; and

the processor and the memory are further configured to: the use of frequency hopping is abandoned when receiving HARQ feedback.

29. The base station of claim 18, wherein the processor and the memory are further configured to:

a capability message is received from the user equipment indicating that the user equipment supports communication on the first RF band.

30. A method for wireless communication at a base station, the method comprising:

transmitting an indication that the base station supports a first Radio Frequency (RF) band; and

according to a first configuration based on a first minimum bandwidth size defined for the first RF band, the first minimum bandwidth size is smaller than a second minimum bandwidth size defined for a second RF band available to the user device, communication is performed with the user device via the first RF band.