Devices and equipment for wireless communication

Abstract

The present disclosure relates to network configuration options for coexistence of reduced capability devices with legacy new air interface devices. The present disclosure relates to improved network configuration options that enable reduced capability (Redcap) devices to coexist with legacy devices. A master information block (MIB) cellBarred indication received by a Redcap device in a synchronization system block (SSB) may be ignored by the Redcap device, which may read the system information block 1 (SIB1) to determine whether to connect to a cell defined by the received SSB. If the SIB1 includes a cellBarred indication for a Redcap device, the Redcap device may consider the cell to be barred. The Redcap device may alternatively search for an alternative SSB indicated by the SIB1 to determine whether to connect to a cell defined by the alternative SSB. A network node may broadcast a Redcap-specific SSB and a legacy-specific SSB at the same frequency location in a time division multiplexed manner, where each type of device determines cell access based on the received specific SSB. The network node may transmit an SSB burst specifically for Redcap devices.

Description

Technical Field

[0001] The present application relates to wireless communications, including providing network configuration options for coexistence of reduced capability devices with legacy devices during wireless communications (e.g., during wireless cellular communications such as 5G-NR (NR) communications).

[0002] Related technical description

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices (i.e., user equipment devices or UEs) now also provide access to the Internet, email, text messaging and navigation using the Global Positioning System (GPS), and are capable of operating sophisticated applications that utilize these capabilities. In addition, there are many different wireless communication technologies and wireless communication standards. Some examples of wireless communication standards include GSM, UMTS (WCDMA, TDS-CDMA), LTE, LTE Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE802.11 (WLAN or Wi-Fi), IEEE 802.16 (WiMAX), BLUETOOTH TM The current communications standard that goes beyond the current International Mobile Telecommunications-Advanced (IMT-Advanced) standard is known as the fifth generation mobile network or fifth generation wireless network and is referred to as 3GPP NR (otherwise referred to as 5G-NR or NR-5G, and also simply NR, for 5G New Radio). NR provides higher capacity for a higher density of mobile broadband users while supporting device-to-device, ultra-reliable and massive machine communications, as well as lower latency and lower battery consumption than the LTE standard.

[0004] One aspect of wireless communication systems (including NR cellular wireless communication) involves scheduling communications for devices with different corresponding capabilities. Some devices are classified as "reduced-capability devices" or simply "Redcap devices" with reference to the reduced capabilities of those devices relative to other devices or relative to legacy devices. Within a network, such as within an NR network (or cell), managing wireless communications for both Redcap devices and other higher-capability devices (e.g., legacy devices) remains challenging. Improvements in this area are desired. Summary of the Invention

[0005] In particular, embodiments of methods and procedures are presented herein for network configuration options for coexistence of reduced capability (Redcap) devices with legacy devices, such as in NR networks. Embodiments of a wireless communication system are also presented herein, including wireless communication devices or user equipment devices (UEs) and / or base stations and access points (APs) communicating with each other within the wireless communication system.

[0006] To improve the coexistence of Redcap devices with non-Redcap or legacy devices, the initial cell access procedure performed by a mobile device may be revised. In some embodiments, a device (e.g., a UE) may search for and receive a cell-defining first synchronization signal block (SSB), which may include a first information block (IB) (e.g., a master information block (MIB)) indicating whether the cell defined by the SSB is barred. The UE may consider the cell to be valid and not barred for the UE regardless of what the first IB indicates, and may proceed to read a second IB (e.g., a system information block (SIB1)) included in the first SSB to determine whether to connect to the cell. In response to the second IB including information about the initial bandwidth part (BWP) for Redcap devices, the UE may consider the cell to be valid for the device. Alternatively, in response to the second IB not including information about the initial BWP for Redcap devices, the UE may consider the cell to be barred for the UE. The first IB may still indicate whether the cell is barred for one or more additional devices other than the UE, such as legacy devices. Additionally, in response to the second IB indicating that the cell is barred, the UE may consider the cell to be barred for the UE.

[0007] In some embodiments, in response to a second IB indicating that the cell is barred, the UE may search for and locate a second SSB defined by the cell indicated by the second IB. The UE may receive the second SSB and may determine whether to connect to the second cell defined by the second SSB based on the information included in the second SSB. Alternatively, the UE may determine the location of a third SSB that is not on the global synchronization channel number from the information included in the second IB and define a third cell. The UE may receive the third SSB and may determine whether to connect to the third cell based on the information included in the third SSB.

[0008] In some embodiments, a network node may broadcast a first SSB defining a cell for a first group of devices and may also broadcast a second SSB defining a cell for a second group of devices that is different from and does not overlap with the first group of devices, wherein the first SSB and the second SSB are broadcast at the same frequency location in a time-multiplexed manner. The first SSB and the second SSB may define different respective initial downlink BWPs for the first and second groups of devices. The different respective initial downlink BWPs may overlap. The first group of devices may be Redcap devices, while the second group of devices may be legacy devices.

[0009] In some embodiments, the UE may receive a cell-defining first SSB at a first frequency location, and in response to a first SSB indicating that the cell defined by the first SSB is prohibited for use with the device, the UE may search for a cell-defining second SSB at the first frequency location at a different time.

[0010] In some embodiments, a network node may transmit a first SSB that includes a first information block indicating a set of SSB burst positions corresponding to a plurality of SSB bursts broadcast by the network node. The first information block may further indicate which of the plurality of SSB bursts is intended for a first group of devices (e.g., Redcap devices) and which of the plurality of SSB bursts is intended for a second group of devices (e.g., legacy devices) that is different from and does not overlap with the first group of devices. One or more individual SSB bursts in the plurality of SSB bursts may each include a first number of SSBs used on a first frequency in a cell defined by the first SSB. The first number of SSBs may include a first group of SSBs and a second group of SSBs that do not overlap with each other. The first group of SSBs may include a corresponding first master information block (MIB) intended for the first group of devices, and the second group of SSBs may include a corresponding second MIB intended for the second group of devices. The corresponding first MIB and the corresponding second MIB indicate whether the cell is prohibited for devices belonging to the first group of devices or devices belonging to the second group of devices. The first MIB and the second MIB may indicate different corresponding sets of control resources for the first group of devices and the second group of devices, respectively. In some embodiments, the first number of SSBs may include a corresponding MIB indicating whether the cell is barred and may also include a corresponding second information block indicating the frequency location of an information block defining a unit for devices belonging to the first group of devices but not the second group of devices.

[0011] Note that the techniques described herein can be implemented in and / or used with many different types of devices, including but not limited to base stations, access points, cellular phones, portable media players, tablets, wearable devices, head-mounted displays, VR displays, wearable glasses, XR devices, and various other computing devices.

[0012] This summary is intended to provide a brief overview of some of the subject matter described in this document. Therefore, it should be understood that the above-described features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, accompanying drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 An exemplary (and simplified) wireless communication system according to some embodiments is shown;

[0014] Figure 2 illustrates an exemplary base station in communication with an exemplary wireless user equipment (UE) device in accordance with some embodiments;

[0015] Figure 3 shows an exemplary block diagram of a UE according to some embodiments;

[0016] Figure 4 shows an exemplary block diagram of a base station according to some embodiments;

[0017] Figure 5 shows an exemplary simplified block diagram of an example cellular communication circuit according to some embodiments;

[0018] Figure 6 A simplified diagram illustrating channel bandwidth (CHBW) and bandwidth part (BWP) configurations for initial access of a device (e.g., a wireless communication device or user equipment device (UE)) to a cell (e.g., via a base station) is shown;

[0019] Figure 7 shows a simplified diagram illustrating Synchronous System Block (SSB) transmission using Global Synchronization Channel Number (GSCN) and CHBW and BWP configurations;

[0020] Figure 8 A simplified diagram illustrating potential issues when transmitting SSB and configuring CHBW and BWP for simultaneous operation of reduced capability (Redcap) devices and legacy devices is shown;

[0021] Figure 9shows a table illustrating a proposed solution to ensure successful coexistence of Redcap devices and legacy devices based on cell barring indication according to some embodiments;

[0022] Figure 10 A simplified diagram illustrating SSB transmission when the initial downlink bandwidth portion is greater than 20 MHz and channel CHBW and BWP configurations for initial access of a device to a cell is shown according to some embodiments;

[0023] Figure 11 A simplified diagram illustrating SSB transmission when the initial downlink bandwidth portion is 20 MHz and channel CHBW and BWP configurations for initial access of a device to a cell according to some embodiments is shown;

[0024] Figure 12 shows a simplified diagram illustrating SSB transmission with PDCCH-ConfigSIB1 based redirection and channel CHBW and BWP configurations for initial access of a device to a cell according to some embodiments;

[0025] Figure 13 shows a simplified diagram illustrating SSB transmission with SIB1 based redirection and channel CHBW and BWP configurations for initial access of a device to a cell according to some embodiments; and

[0026] Figure 14 A simplified diagram illustrating time domain multiplexing of Redcap SSB and non-Redcap SSB transmissions according to some embodiments is shown.

[0027] While the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereof are not intended to limit this disclosure to the specific forms disclosed, but on the contrary, are intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0028] Acronyms

[0029] Various acronyms are used throughout this patent application. The definitions of the most prominent acronyms used that may appear throughout this patent application are as follows:

[0030] AF: Application Function

[0031] AMF: Access and mobility management function

[0032] AMR: Adaptive Multi-Rate

[0033] AP: Access Point

[0034] APN: Access Point Name

[0035] APR: Application Processor

[0036] AS: Access layer

[0037] BS: Base Station

[0038] BSR: Buffer Status Report

[0039] BSSID: Basic Service Set Identifier

[0040] CBRS: Citizens Broadband Radio Service

[0041] CBSD: Citizens Broadband Radio Service Device

[0042] CCA: Clear Channel Assessment

[0043] CCE: Control Channel Element

[0044] CMR: Change Mode Request

[0045] CN: Core Network

[0046] CORESET: Control resource set

[0047] CS: cyclic shift

[0048] DL: Downlink (from BS to UE)

[0049] DMRS: Demodulation Reference Signal

[0050] DN: Data Network

[0051] DRB: Data Radio Bearer

[0052] DSDS: Dual SIM Dual Standby

[0053] DYN: Dynamic

[0054] EDCF: Enhanced Distributed Coordination Function eSNPN: Equivalent Standalone Non-Public Network

[0055] FDD: Frequency Division Duplex

[0056] FT: frame type

[0057] GAA: General Authorization Access

[0058] GPRS: General Packet Radio Service

[0059] GSCN: Global Synchronization Channel Number

[0060] GSM: Global System for Mobile Communications

[0061] GTP: GPRS Tunneling Protocol

[0062] HPLMN: Home Public Land Mobile Network IMS: Internet Protocol Multimedia Subsystem IOT: Internet of Things

[0063] IP: Internet Protocol

[0064] KPI: Key Performance Indicator

[0065] LAN: Local Area Network

[0066] LBT: Listen first, speak later

[0067] LCP: Logical Channel Prioritization

[0068] LQM: Link Quality Metric

[0069] LTE: Long Term Evolution

[0070] MCC: Mobile Country Code

[0071] MIB: Master Information Block

[0072] MNO: Mobile Network Operator

[0073] MO: Monitoring time

[0074] NAS: Non-Access Stratum

[0075] NEF: Network Exposure Function

[0076] NF: Network Function

[0077] NG-RAN: Next Generation Radio Access Network

[0078] NID: Network Identifier

[0079] NMF: Network Identifier Management Function

[0080] NPN: Non-Public (Cellular) Network

[0081] NRF: Network Repository Function

[0082] NSI: Network Slicing Instance

[0083] NSSAI: Network Slice Selection Auxiliary Information

[0084] OFDM: Orthogonal Frequency Division Multiplexing

[0085] OOC: Out of coverage

[0086] PBCH: Physical Broadcast Channel

[0087] PCF: Point Coordination Function

[0088] PDB: Packet Delay Budget

[0089] PDCP: Packet Data Convergence Protocol

[0090] PDN: Packet Data Network

[0091] PDU: Protocol Data Unit

[0092] PGW: PDN Gateway

[0093] PLMN: Public Land Mobile Network

[0094] PRACH: Physical Random Access Channel

[0095] PRB: Physical Resource Block

[0096] PRI: Physical Uplink Control Channel (PUCCH) Resource Indicator PSCCH: Physical Sidelink Control Channel

[0097] PSFCH: Physical side link feedback channel

[0098] PSSCH: Physical side link shared channel

[0099] PSD: Power Spectral Density

[0100] PSS: Primary Synchronization Signal

[0101] PT: Payload Type

[0102] PTRS: Phase Tracking Reference Signal

[0103] PUCCH: Physical Uplink Control Channel QBSS: Basic Service Set for Quality of Service Enhancement QFI: Quality of Service Flow Identifier

[0104] QI: Quality Indicator

[0105] QoE: Quality of Experience

[0106] QoS: Quality of Service

[0107] RA: Registration Acceptance

[0108] RAN: Radio Access Network

[0109] RAR: Random Access Response

[0110] RAT: Radio Access Technology

[0111] RF: Radio Frequency

[0112] ROHC: Robust Header Compression

[0113] RR: Registration Request

[0114] RRC: Radio Resource Control

[0115] RSRP: Reference Signal Received Power

[0116] RTP: Real-time Transport Protocol

[0117] RX: Receive

[0118] SAS: Spectrum Allocation Server

[0119] SD: Slice Descriptor

[0120] SDAP: Service Data Adaptation Protocol

[0121] SDU: Service Data Unit

[0122] SI: System Information

[0123] SIB: System Information Block

[0124] SID: System Identification Number

[0125] SIM: Subscriber Identity Module

[0126] SGW: Serving Gateway

[0127] SMF: Session Management Function

[0128] SNPN: Independent Non-Public Network

[0129] SPS: Semi-persistent scheduling

[0130] SSB: Synchronous Signal Block

[0131] SSS: Secondary synchronization signal

[0132] SUPI: Subscription Permanent Identifier

[0133] TBS: Transport Block Size

[0134] TCP: Transmission Control Protocol

[0135] TDD: Time Division Duplex

[0136] TDRA: Time Domain Resource Allocation

[0137] TPC: Transmit Power Control

[0138] TSC: Time Sensitive Communication

[0139] TSCAI: Time-Sensitive Communication Assistance Information

[0140] TX: Transmit

[0141] UAC: Unified Access Control

[0142] UDM: Unified Data Management

[0143] UDR: User Data Repository

[0144] UE: User Equipment

[0145] UI: User input

[0146] UL: Uplink (from UE to BS)

[0147] UMTS: Universal Mobile Telecommunications System

[0148] UPF: User Plane Function

[0149] URLLC: Ultra-Reliable Low Latency Communication

[0150] URM: Universal Resource Management

[0151] URSP: UE routing strategy

[0152] USIM: User Subscriber Identity Module

[0153] Wi-Fi: Wireless local area network based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard

[0154] WLAN RAT

[0155] WLAN: Wireless LAN

[0156] XR: Extended Reality

[0157] the term

[0158] The following is a glossary of terms that will appear in this application:

[0159] Memory medium – Any of various memory devices or storage devices. The term "memory medium" is intended to include installation media such as CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, internal processor memory, etc.; non-volatile memory such as flash memory, magnetic media such as hard drives or optical storage devices; registers, or other similar types of memory elements. Memory media may also include other types of memory or a combination thereof. Furthermore, a memory medium may be located in a first computer system executing a program, or in a different second computer system connected to the first computer system via a network, such as the Internet. In the latter example, the second computer system may provide program instructions to the first computer system for execution. The term "memory medium" may include two or more memory media that may reside in different locations in different computer systems, for example, connected via a network. A memory medium may store program instructions (e.g., represented as a computer program) that are executable by one or more processors.

[0160] Carrier Medium—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic, or digital signals.

[0161] Programmable hardware elements—include various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can range from fine-grained (combinational logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0162] Computer system (or computer)—any of various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, Internet appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined as any device (or combination of devices) that includes at least one processor that executes instructions from a memory medium.

[0163] User Equipment (UE) (or "UE device") - any of various types of computer system devices that perform wireless communications. Also known as wireless communication devices, many of which may be mobile and / or portable. Examples of UE devices include mobile phones or smartphones (e.g., iPhones). TM, based on Android TM phones) and tablets such as iPads TM 、Samsung Galaxy TM etc., gaming devices (e.g., Sony PlayStation TM , Microsoft XBox TM etc.), portable gaming devices (e.g., Nintendo DS TM PlayStation Portable TM 、Gameboy Advance TM iPod TM ), laptops, wearable devices (e.g., Apple Watch TM , Google Glass TM ), PDAs, wearable glasses, head-mounted displays, XR devices, portable internet devices, music players, data storage devices or other handheld devices, unmanned aerial vehicles (e.g., drones) and drone controllers, etc. Various other types of devices that include Wi-Fi communication capabilities or both cellular and Wi-Fi communication capabilities and / or other wireless communication capabilities (e.g., via short-range radio access technologies (SRAT) such as BLUETOOTH TM Generally speaking, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device and / or telecommunication device (or combination of devices) capable of wireless communication and which may also be portable / mobile.

[0164] Wireless device (or wireless communication device)—any of various types of computer system devices that perform wireless communication using WLAN communication, SRAT communication, Wi-Fi communication, etc. As used herein, the term "wireless device" can refer to a UE device as defined above or a fixed device such as a fixed wireless client or a wireless base station. For example, a wireless device can be a wireless station of any type of 802.11 system, such as an access point (AP) or a client station (UE), or a wireless station of any type of cellular communication system that communicates according to a cellular radio access technology (e.g., 5G NR, LTE, CDMA, GSM), such as, for example, a base station or a cellular phone.

[0165] Communication Device—Any of various types of computer systems or devices that perform communication, either wired or wireless. A communication device can be portable (or mobile), or stationary or fixed in place. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0166] Base Station (BS)—The term “base station” has the full breadth of its ordinary meaning and includes at least a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0167] Processor—refers to any element (e.g., circuitry) or combination of elements capable of performing functions in a device (e.g., in a user equipment device or in a cellular network device). Processors may include, for example, general-purpose processors and associated memory, portions or circuitry of individual processor cores, entire processor cores or processing circuit cores, processing circuit arrays or processor arrays, circuits such as ASICs (Application Specific Integrated Circuits), programmable hardware elements such as field programmable gate arrays (FPGAs), and any combination of the foregoing.

[0168] Channel - the medium used to transmit information from a sender (transmitter) to a receiver. It should be noted that since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" as used in the present invention may be considered to be used in a manner that is consistent with the standard of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel may be 22 MHz wide, while a Bluetooth channel may be 1 MHz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0169] Band (or frequency band)—The term "band" has its full meaning and includes at least a section of spectrum (e.g., radio frequency spectrum) where channels are used or set aside for the same purpose. Furthermore, "band" is used to refer to any interval in the frequency domain bounded by lower and upper frequencies. The term can refer to a radio frequency band or some other interval of spectrum. A radio communication signal can occupy a frequency range over which the signal is carried (or within which the signal is carried). This frequency range is also referred to as the bandwidth of the signal. Thus, bandwidth refers to the difference between the upper and lower frequencies in a continuous frequency band. A frequency band can represent a communication channel or it can be subdivided into multiple communication channels. The allocation of radio frequency ranges for different uses is a primary function of radio spectrum allocation. For example, in 5G NR, operating bands are categorized into two groups. More specifically, according to 3GPP Release 15, frequency bands are specified for different frequency ranges (FRs), and these bands are defined as FR1 and FR2, with FR1 covering the range of 410 MHz to 7125 MHz and FR2 covering the range of 24,250 MHz to 52,600 MHz.

[0170] Wi-Fi—The term "Wi-Fi" has the full scope of its ordinary meaning and includes at least wireless communication networks, or RATs, that are served by wireless LAN (WLAN) access points and provide connectivity to the Internet through those access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi." Wi-Fi (WLAN) networks are distinct from cellular networks.

[0171] Automatic—refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without requiring user input to directly specify or execute the action or operation. Thus, the term "automatic" is in contrast to manual execution or specification of an action by a user, where the user provides input to directly execute the action. An automatic process may be initiated by input provided by a user, but the subsequent actions performed "automatically" are not specified by the user, i.e., they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting checkboxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user's actions. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills it out without requiring any user input to specify the answers to the fields. As indicated above, a user may invoke automatic filling of a form without participating in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields, but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0172] About—refers to a value that is close to being correct or exact. For example, about can refer to a value that is within 1% to 10% of the exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may depend on the application. For example, in some embodiments, "about" may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the desires or requirements of a particular application.

[0173] Concurrency—refers to parallel execution or implementation, where tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism," where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0174] Station (STA)—The term "station" herein refers to any device capable of communicating wirelessly (e.g., using the 802.11 protocol). A station can be a laptop, desktop PC, PDA, access point, or Wi-Fi phone, or any other type of device similar to a UE. A STA can be fixed, mobile, portable, or wearable. Generally speaking, in wireless networking terminology, a station (STA) broadly encompasses any device capable of wireless communication, and the terms station (STA), wireless client (UE), and node (BS) are often used interchangeably.

[0175] Configured to—Various components may be described as being “configured to” perform one or more tasks. In such contexts, “configured to” is a broad statement that generally means “having the structure” to perform one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, “configured to” can be a broad statement that generally means “having the circuitry” to perform one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently turned on. Generally, the circuitry that forms the structure corresponding to “configured to” may include hardware circuitry.

[0176] Transmission Scheduling—refers to the scheduling of transmissions (such as wireless transmissions). In some implementations of cellular radio communications, signal transmissions and data transmissions may be organized according to designated time units of a specific duration during which the transmission occurs. As used herein, the term "time slot" has the full range of its ordinary meaning and refers to at least the smallest (or shortest) scheduled time unit in wireless communications. For example, in 3GPP LTE, transmissions are divided into radio frames, each of which has an equal (time) duration (e.g., 10 ms). Radio frames in 3GPP LTE can be further divided into a specified number (e.g., ten) of subframes, each of which has an equal duration, with subframes designated as the smallest (shortest) scheduled unit, or a designated time unit for transmission. Thus, in the 3GPP LTE example, a "subframe" can be considered an example of a "time slot" as defined above. Similarly, the smallest (or shortest) scheduled time unit for 5G NR (or simply NR) transmissions is called a "time slot." The smallest (or shortest) scheduled time unit may also be named differently in different communication protocols.

[0177] Resources—The term "resource" has the full scope of its ordinary meaning and may refer to both frequency and time resources used during wireless communications. As used herein, a resource element (RE) refers to a specific quantity or number of resources. For example, in the context of time resources, a resource element may be a time period of a specific length. In the context of frequency resources, a resource element may be a specific frequency bandwidth or a specific amount of frequency bandwidth centered on a specific frequency. As a specific example, a resource element may refer to a unit of resources having one symbol (in reference to a time resource, e.g., a time period of a specific length) per one subcarrier (in reference to a frequency resource, e.g., a specific frequency bandwidth, which may be centered on a specific frequency). A resource element group (REG) has the full scope of its ordinary meaning and refers to at least a specified number of contiguous resource elements. In some implementations, a resource element group may not include resource elements reserved for reference signals. A control channel element (CCE) refers to a group of a specified number of contiguous REGs. A resource block (RB) refers to a specified number of resource elements consisting of a specified number of subcarriers per a specified number of symbols. Each RB may include a specified number of subcarriers. A resource block group (RBG) refers to a unit that includes multiple RBs. The number of RBs in one RBG may vary according to the system bandwidth.

[0178] Bandwidth Part (BWP) - A Bandwidth Part (BWP) is a set of contiguous physical resource blocks selected from a contiguous subset of common resource blocks for a given parameter set on a given carrier. For the downlink, a UE can be configured with up to a specified number of carrier BWPs (e.g., four BWPs per some specifications), with one BWP active per carrier at a given time (per some specifications). For the uplink, a UE can similarly be configured with up to a number (e.g., four) of carrier BWPs, with one BWP active per carrier at a given time (per some specifications). If a UE is configured with a supplemental uplink, the UE can additionally be configured with up to a specified number (e.g., four) of carrier BWPs in the supplemental uplink, with one carrier BWP active at a given time (per some specifications).

[0179] Multi-cell arrangement - A master node is defined as a node (radio access node) that provides a control plane connection to the core network in the case of multi-radio dual connectivity (MR-DC). The master node can be, for example, a master eNB (3GPP LTE) or a master gNB (3GPP NR). A secondary node is defined as a radio access node that does not have a control plane connection to the core network and provides additional resources to the UE in the case of MR-DC. A master cell group (MCG) is defined as a set of serving cells associated with a master node, including a primary cell (PCell) and optionally one or more secondary cells (SCells). A secondary cell group (SCG) is defined as a set of serving cells associated with a secondary node, including a special cell, i.e., the primary cell (PSCell) of the SCG, and optionally one or more SCells. The UE can typically apply radio link monitoring to the PCell. If the UE is configured with an SCG, the UE can also apply radio link monitoring to the PSCell. Radio link monitoring is typically applied to the active BWP, and the UE does not need to monitor the inactive BWP. The PCell is used to initiate initial access, and the UE can communicate with the PCell and SCell via carrier aggregation (CA). The currently modified capability means that the UE can receive and / or transmit to and / or from multiple cells.The UE is initially connected to a PCell, and once the UE is in the connected state, one or more SCells may be configured for the UE.

[0180] Core Network (CN) - The core network (or backbone) is defined as the part of the 3GPP system that is independent of the UE's connectivity technology (e.g., radio access technology, RAT). A UE can connect to the core network via a radio access network, RAN, which can be RAT-specific. A CN can typically be part of a computer network that interconnects networks, providing a path for information to be exchanged between different local area networks (LANs) or subnetworks. A CN can also connect different networks together in the same building, in different buildings in a campus environment, or over a wide area. Typically, a CN has a larger capacity than the networks it connects to.

[0181] Ultra-Reliable Low-Latency Communication (URLLC)—URLLC refers to the use of networks for mission-critical (or essential) applications that require uninterrupted and robust data exchange.

[0182] Time-Sensitive Communication (TSC)—TSC has stricter requirements in terms of latency and reliability than URLLC, and absolute time synchronization and on-time delivery of packets for deterministic and synchronous real-time applications may sometimes be required. The success of TSC depends on the efficient scheduling of TSC traffic flows.

[0183] Extended Reality (XR)—XR is an umbrella term encompassing virtual reality (VR), augmented reality (AR), and mixed reality (MR), and represents one of the most important media applications being considered for establishing the way people interact with media.

[0184] Service Data Unit (SDU)—An SDU is a data unit that has been passed down from an Open Systems Interconnection layer or sublayer to a lower layer. The SDU has not yet been encapsulated into a Protocol Data Unit (PDU) by the lower layer.

[0185] Service Data Adaptation Protocol (SDAP) - SDAP is responsible for QoS flow handling across the air (e.g., NR air) interface. Specifically, SDAP maps specific QoS flows to corresponding data radio bearers (DRBs) that have been established with the appropriate QoS level. In NR sidelink communications, the SDAP sublayer maps PC5 (i.e., sidelink, SL) quality of service (QoS) flows to SL data radio bearers (SL-DRBs).

[0186] NR channel hierarchy - In order to group the data to be sent over the NR radio access network, the data is organized in a specific way. Since there are many different functions associated with the data transmitted over the radio communication link, they need to be clearly labeled and have a defined location and format. Therefore, several different forms of data channels are defined and used. Higher-layer channels are mapped to or contained in other channels until the physical layer is reached. The physical channel contains all the data from the higher-layer channels. This provides a logical and manageable data flow from the higher layers of the protocol stack down to the physical layer. In mobile communication systems, such as NR communication systems, three main types of data channels are used.

[0187] Logical Channel (LCH) - Logical channels can belong to one of the following two groups: control channels and traffic channels. Control channels are used to transmit data from the control plane, while traffic channels are used to transmit user plane data.

[0188] Transport Channel (TCH)—A transport channel represents a multiplex of logical data to be transmitted by the physical layer and its channels over the radio interface.

[0189] Physical Channel (PCH)—The physical channel is closest to the actual transmission of data over the radio access network / NR radio frequency signal and is used to carry data over the radio interface. Higher-layer channels are typically mapped to the physical channel to provide specific services. The physical channel carries the payload data or details of specific data transmission characteristics, such as modulation, reference signal multiplexing, transmit power, RF resources, etc.

[0190] Network Exposure Function (NEF) - NEF is a function in the 3GPP core network architecture that provides a way to securely expose capabilities and events. NEF stores the received information as structured data and exposes it to other network functions.

[0191] Point Coordination Function (PCF)—PCF is a medium access control (MAC) technology used to coordinate communications within a communication network.

[0192] User Plane Function (UPF)—UPF is one of the Network Functions (NFs) of the 5G / NR core network and is responsible for packet routing and forwarding, packet inspection, QoS processing, and external PDU sessions for interconnecting data networks (DNs) in the NR architecture.

[0193] Medium Access Control (MAC) Control Element (MAC CE) - In at least LTE and NR communications, there are several communication paths at the MAC layer, where a specific MAC structure carries special control information. The specific MAC structure that carries this control information is called a "MAC CE." The MAC CE operates between the UE (MAC) and the base station (MAC) for fast signaling communication exchange without involving upper layers. The MAC CE is sent as part of the MAC PDU. For NR uplink communications, the MAC CE is typically placed at the end of the MAC PDU. For NR downlink communications, the MAC CE is typically placed at the beginning of the MAC PDU.

[0194] Camping on a cell (or network) - At least in LTE and NR communications, a device or UE that searches for a suitable cell of a selected mobile network, selects that cell to provide available services, and monitors its control channels is said to be a UE "camped on a cell". The UE registers its presence in the registration area of ​​the selected cell through a location registration procedure (if necessary). If the UE finds a more suitable cell, it can reselect to the more suitable cell and camp on it. If the new cell is in a different registration area, a location registration is performed. A UE can camp on a cell in idle mode, which means that the UE may not be actively communicating with other UEs, but may monitor certain control channels and may periodically check for paging messages or other communications on the cell, thereby remaining (camped) on the cell. A UE camped on a cell can receive system information from the mobile network. A UE camped on a cell can initiate a call (when registered on the cell) by initially accessing the network on the control channel of the cell on which it is camped. If the mobile network receives a call for a registered UE, the network will access the registration area of ​​the cell where the UE is camped and can send a "paging" message for the UE on the control channels of all cells in the registration area. The UE can receive the paging message because it is tuned to the control channel of the cell where the UE is camped, and the UE can respond on this control channel. Camping on a cell also means that the UE can receive cell broadcast messages.

[0195] Barred cell (or network) - At least in LTE and NR communications, a cell (or network) is said to be barred when the UE is not allowed to camp / remain on that cell. According to 3GPP TS 25.304, a "barred cell" is a "cell on which the UE is not allowed to camp." The UE is not allowed to camp on a barred cell, not even for emergency calls. If the cell on which the UE is currently camped is barred, cell reselection is triggered.

[0196] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to." Representing a component as being configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112, sixth paragraph, to interpret such component.

[0197] Figure 1 and Figure 2 —Exemplary Communication System

[0198] Figure 1 An exemplary (and simplified) wireless communication system according to some embodiments is shown. Note that Figure 1 The system is only one example of a possible system, and embodiments may be implemented in any of a variety of systems as desired.

[0199] As shown, the exemplary wireless communication system includes base stations 102A through 102N, also collectively referred to as a plurality of base stations 102 or base stations 102. Figure 1 As shown, base station 102A communicates with one or more user devices 106A to 106N via a transmission medium. Each user device may be referred to herein as a "user equipment" (UE) or a UE device. Thus, user devices 106A to 106N are referred to as UEs or UE devices, and are also collectively referred to as multiple UEs 106 or UEs 106.

[0200] Base station 102 may be a base transceiver station (BTS) or cell site and may include hardware that enables wireless communications with UEs 106A through 106N. Base station 102A may also be configured to communicate with a network 100, such as a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet, a neutral host, or various CBRS (Citizens Broadband Radio Service) deployments, among other possibilities. Thus, base station 102A may facilitate communications between user devices 106 and / or between user devices 106 and network 100. Specifically, cellular base station 102A may provide UEs 106 with various communication capabilities, such as voice, short message service (SMS), and / or data services. The communication area (or coverage area) of base station 106 may be referred to as a "cell." Note that a "cell" may also refer to a logical designation for a given wireless communication coverage area at a given frequency. In general, any individual cellular wireless coverage area may be referred to as a "cell." In such a case, a base station may be located at a particular intersection of three cells. In this uniform topology, a base station may serve three 120 degree beam width areas called cells. Also, for carrier aggregation, small cells, relays, etc. may all represent cells. Thus, particularly in carrier aggregation, there may be primary cells and secondary cells that may serve at least partially overlapping coverage areas but on different respective frequencies. For example, a base station may serve any number of cells, and the cells served by a base station may or may not be collocated (e.g., remote radio heads). Also as used herein, with respect to a UE, a base station may sometimes be considered to represent a network in view of the UE's uplink and downlink communications. Thus, a UE communicating with one or more base stations in a network may also be interpreted as a UE communicating with the network, and may also be considered to be at least a portion of a UE communicating on or through a network.

[0201] The base station 102 and the user equipment 106 can be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunication standards, such as GSM, UMTS (WCDMA), LTE, LTE-Advanced (LTE-A), LAA / LTE-U, 5G-NR (abbreviated as NR), 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, WiMAX, and the like. It should be noted that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB." Similarly, if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB." Depending on a given application or specific considerations, for convenience, some of the different RATs may be functionally grouped according to overall defining characteristics. For example, all cellular RATs may be collectively considered to represent a first (form / type) RAT, while Wi-Fi communications may be considered to represent a second RAT. In other cases, each cellular RAT may be individually considered a different RAT. For example, when distinguishing between cellular and Wi-Fi communications, "first RAT" may collectively refer to all cellular RATs under consideration, while "second RAT" may refer to Wi-Fi. Similarly, different forms of Wi-Fi communications (e.g., over 2.4 GHz versus over 5 GHz) may be considered to correspond to different RATs, where applicable. Furthermore, cellular communications performed according to a given RAT (e.g., LTE or NR) may be distinguished from one another based on the spectrum over which those communications occur. For example, LTE or NR communications may be performed on a primary licensed spectrum as well as on a secondary spectrum, such as unlicensed spectrum and / or spectrum allocated to private networks. In general, the use of various terms and expressions will always be clearly indicated in relation to and within the context of the various applications / implementations under consideration.

[0202] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices 106 and / or between user devices 106 and network 100. Specifically, cellular base station 102A may provide UE 106 with various telecommunications capabilities, such as voice, short message service (SMS), and / or data services. UE 106 may be capable of communicating using multiple wireless communication standards. For example, UE 106 may be configured to communicate using any or all of 3GPP cellular communication standards (such as LTE or NR) and / or 3GPP2 cellular communication standards (such as a cellular communication standard in the CDMA2000 family of cellular communication standards). Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as one or more cell networks that can provide continuous or nearly continuous overlapping service to UE 106 and similar devices over a wide geographic area via one or more cellular communication standards.

[0203] Thus, although base station 102A may function as Figure 1 106N, each of the UEs 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (potentially provided by base stations 102B through 102N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be capable of facilitating communications between user devices 106 and / or between user devices 106 and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any other variety of granularities of service area size. For example, in Figure 1 The base stations 102A-102B shown in FIG may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

[0204] In some embodiments, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB." In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transmit and receive points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0205] UE 106 may also or alternatively be configured to use WLAN, BLUETOOTHTM 、BLUETOOTH TM Low-Energy, one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible. In addition, the UE 106 can also communicate with the network 100 through one or more base stations or through other devices, stations, or any appliances not explicitly shown but considered to be part of the network 100. Therefore, the UE 106 communicating with the network can be interpreted as the UE 106 communicating with one or more network nodes considered to be part of the network, and can interact with the UE 106 to communicate with the UE 106, and in some cases affect at least some communication parameters and / or the use of communication resources of the UE 106.

[0206] For example, Figure 1 As shown in FIG, at least some of the UEs (e.g., UE 106D and 106E) may represent vehicles communicating with each other and with base station 102, for example, via cellular communications such as 3GPP LTE and / or 5G-NR communications. Additionally, UE 106F may represent a pedestrian communicating and / or interacting in a similar manner with the vehicles represented by UEs 106D and 106E. For example, in the context of vehicle-to-everything (V2X) communications (such as those specified by certain versions of 3GPP standards), the disclosed Figure 1 Various embodiments of vehicles communicating in a network illustrated in FIG.

[0207] Figure 2 An exemplary user equipment 106 (e.g., one of UEs 106A through 106N) is shown in communication with a base station 122 and an access point 112 according to some embodiments. The UE 106 may be a user equipment having cellular communication capabilities and non-cellular communication capabilities (e.g., BLUETOOTH TM, Wi-Fi, etc.), such as a mobile phone, a handheld device, a computer or a tablet computer, or almost any type of wireless device. UE 106 may include a processor configured to execute program instructions stored in a memory. UE 106 may execute any of the method embodiments described in the present invention by executing such stored instructions. Alternatively or in addition, UE 106 may include a programmable hardware element, such as an FPGA (field programmable gate array) configured to execute any of the method embodiments described herein or any part of any of the method embodiments described herein. UE 106 may be configured to communicate using any of a plurality of wireless communication protocols. For example, UE 106 may be configured to communicate using two or more of CDMA 2000, LTE, LTE-A, NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0208] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols according to one or more RAT standards, such as those previously described above. In some embodiments, UE 106 may share one or more portions of a receive chain and / or transmit chain between multiple wireless communication standards. The shared radio components may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Alternatively, UE 106 may include an independent transmit chain and / or receive chain (e.g., including independent antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another alternative, UE 106 may include one or more radio components or radio circuits shared between multiple wireless communication protocols, as well as one or more radio components used uniquely by a single wireless communication protocol. For example, UE 106 may include radio circuits for communicating using any of LTE or DMA2000 1xRTT or NR, and radio circuits for communicating using Wi-Fi and BLUETOOTH. TM Independent radio components for each of the communications. Other configurations are also possible.

[0209] Figure 3 —Block diagram of an exemplary UE

[0210] Figure 3A block diagram of an exemplary UE 106 according to some embodiments is shown. As shown, the UE 106 may include a system on a chip (SOC) 300, which may include various elements / components for various purposes. For example, as shown, the SOC 300 may include a processor 302 that can execute program instructions for the UE 106, and a display circuit 304 that can perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 and / or other circuits or devices (such as display circuit 304, radio circuit 330, connector I / F 320 and / or display 360). The MMU 340 may be configured to receive addresses from the processor 302 and convert those addresses to locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of one or more processors 302.

[0211] As shown, the SOC 300 can be coupled to various other circuits of the UE 106. For example, the UE 106 can include various types of memory (e.g., including NAND flash memory 310), a connector interface 320 (e.g., for coupling to a computer system), a display 360, and wireless communication circuitry (e.g., for LTE, LTE-A, NR, CDMA2000, BLUETOOTH, etc.). TM , Wi-Fi, GPS, etc.). The UE device 106 may include at least one antenna (e.g., 335a), and may include multiple antennas (e.g., as shown by antennas 335a and 335b), for performing wireless communications with base stations and / or other devices. Antennas 335a and 335b are shown by way of example, and the UE device 106 may include fewer or more antennas. In general, one or more antennas are collectively referred to as antennas 335. For example, the UE device 106 may use antennas 335 to perform wireless communications with the radio circuit 330. As described above, in some embodiments, the UE may be configured to perform wireless communications using multiple wireless communication standards.

[0212] The processor 302 of the UE device 106 can be configured to implement part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, the processor 302 can be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). In addition, the processor 302 can be coupled to a processor such as Figure 3The other components shown and / or may interoperate with other components to enable communication through the UE 106 according to various embodiments disclosed herein. Specifically, the processor 302 may be coupled to Figure 3 The other components shown in and / or interoperable with these components to facilitate UE 106 to communicate in a manner that attempts to optimize RAT selection. Processor 302 can also implement various other applications and / or end-user applications running on UE 106.

[0213] In some embodiments, the radio circuitry 330 may include separate controllers dedicated to controlling communications for various corresponding RATs and / or RAT standards. Figure 3 As shown, the radio circuit 330 may include a Wi-Fi controller 356, a cellular controller (eg, LTE and / or NR controller) 352, and a BLUETOOTH controller. TM Controller 354, and according to at least some embodiments, one or more or all of these controllers may be implemented as respective integrated circuits (ICs or chips) that communicate with each other and with SOC 300 (e.g., with processor 302). For example, Wi-Fi controller 356 may communicate with cellular controller 352 via a cell-ISM link or WCI interface, and / or BLUETOOTH TM The controller 354 may communicate with the cellular controller 352 via a cell-ISM link, etc. Although three separate controllers are shown within the radio circuit 330, other embodiments may have fewer or more similar controllers for various different RATs and / or RAT standards implemented in the UE device 106. For example, in Figure 5 At least one exemplary block diagram illustrating some embodiments of the cellular controller 352 is shown in FIG. 1 and will be further described below.

[0214] Figure 4 —Block diagram of an exemplary base station

[0215] Figure 4 1 shows a block diagram of an exemplary base station 102 according to some embodiments. Note that Figure 4 The base station 102 is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuit or device that may be configured to receive addresses from the processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0216] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide access to the telephone network as described above. Figure 1 and Figure 2 The network port 470 may be configured to couple to a plurality of devices such as the UE device 106 to a telephone network as described herein. The network port 470 (or an additional network port) may additionally or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to a plurality of devices such as the UE device 106. In some cases, the network port 470 may be coupled to the telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other UE devices served by the cellular service provider).

[0217] The base station 102 may include at least one antenna 434a, and may include multiple antennas (e.g., as shown by antennas 434a and 434b), for wireless communication with mobile devices and / or other devices. Antennas 434a and 434b are shown by way of example, and the UE device 102 may include fewer or more antennas. In general, one or more antennas, including antenna 434a and / or antenna 434b, may be collectively referred to as antenna 434 or multiple antennas 434. Antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with the UE device 106 via radio circuitry 430. Antenna 434 communicates with radio component 430 via communication chain 432. Communication chain 432 may be a receive chain, a transmit chain, or both. Radio circuitry 430 may be designed to communicate via various wireless telecommunications standards, including but not limited to LTE, LTE-A, 5G-NR (NR), WCDMA, CDMA2000, and the like. The one or more processors 404 of the base station 102 can be configured to implement part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) for causing the base station 102 to communicate with a UE device as disclosed herein. Alternatively, the processor 404 can be configured as one or more programmable hardware elements such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit) or a combination thereof. In the case of certain RATs (e.g., Wi-Fi), the base station 102 can be designed as an access point (AP), in which case the network port 470 can be implemented to provide access to a wide area network and / or one or more local area networks, for example, it can include at least one Ethernet port, and the radio component 430 can be designed to communicate according to the Wi-Fi standard. The base station 102 can operate according to various methods as disclosed herein for communicating with mobile devices.

[0218] Figure 5—Exemplary Cellular Communications Circuit

[0219] Figure 5 1 shows an exemplary simplified block diagram of an exemplary cellular controller 352 according to some embodiments. Note that Figure 5 The block diagram of the cellular communication circuitry is only one example of possible cellular communication circuitry; other circuitry, such as circuitry that includes or is coupled to sufficient antennas for different RATs to perform uplink activities using separate antennas, or circuitry that includes or is coupled to fewer antennas, e.g., circuitry that can be shared between multiple RATs, is also possible. According to some embodiments, the cellular communication circuitry 352 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and / or a combination of devices, among other devices.

[0220] The cellular communication circuitry 352 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335a-b and 336 as shown. In some embodiments, the cellular communication circuitry 352 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, Figure 5 As shown, the cellular communication circuitry 352 may include a first modem 510 and a second modem 520. The first modem 510 may be configured to communicate according to a first RAT (e.g., such as LTE or LTE-A), and the second modem 520 may be configured to communicate according to a second RAT (e.g., such as 5G NR).

[0221] As shown, the first modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may communicate with a downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0222] Similarly, the second modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with an RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, the receive circuitry 542 may communicate with a downlink (DL) front end 560, which may include circuitry for receiving radio signals via the antenna 335b.

[0223] In some embodiments, the switch 570 can couple the transmit circuitry 534 to an uplink (UL) front end 572. Furthermore, the switch 570 can couple the transmit circuitry 544 to the UL front end 572. The UL front end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 352 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572), the switch 570 can be switched to a first state that allows the first modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 352 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572), the switch 570 can be switched to a second state that allows the second modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572).

[0224] As described herein, the first modem 510 and / or the second modem 520 may include hardware and software components for implementing any of the various features and techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processors 512, 522 may be configured to implement a portion or all of the features described herein. Alternatively (or in addition), the processors 512, 522 may be configured as programmable hardware elements, such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 540, 542, 544, 550, 570, 572, 335, and 336, the processors 512, 522 may be configured to implement a portion or all of the features described herein.

[0225] Furthermore, as described herein, processors 512, 522 may include one or more components. Thus, processors 512, 522 may include one or more integrated circuits (ICs) configured to perform the functions of processors 512, 522. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processors 512, 522.

[0226] In some embodiments, the cellular communication circuitry 352 may include only one transmit / receive chain. For example, the cellular communication circuitry 352 may not include the modem 520, the RF front end 540, the DL front end 560, and / or the antenna 335b. As another example, the cellular communication circuitry 352 may not include the modem 510, the RF front end 530, the DL front end 550, and / or the antenna 335a. In some embodiments, the cellular communication circuitry 352 may also not include the switch 570, and the RF front end 530 or the RF front end 540 may communicate with the UL front end 572, for example, directly.

[0227] Reduced Capacity (Redcap) Devices

[0228] Support for reduced-capability NR devices (e.g., devices with low-end capabilities for certain features and parameters) has gained importance, at least in part, in the context of industrial wireless sensors, video surveillance, and wearable devices. One goal has become to reduce the UE bandwidth from 100 MHz or more specified in the 3GPP standards (Rel-15 / 16) for "normal" NR devices (also known as legacy devices) to 20 MHz for reduced-capability (referred to as "Redcap") devices. Therefore, support has been established for UEs with reduced maximum bandwidth (BW), identifying a maximum bandwidth of 20 MHz during and after initial access. The possibility of optional support for wider bandwidths of up to 40 MHz or even 100 MHz and any associated conditions is also considered.

[0229] Release 17 of the 3GPP specification defines various aspects of wireless communications conducted by Redcap devices. One aspect includes specifying an access control mechanism that allows an operator to restrict access to specific (e.g., selected) cells by Redcap devices (Redcap UEs) when desired. This includes providing at least one system information indication of whether the Redcap UE can camp on that cell / frequency, and it is expected that this indication is specific to the number of receive (Rx) branches of the UE. As described above, Redcap devices are characterized by a reduced maximum UE bandwidth, wherein the maximum bandwidth of a FR1 Redcap UE is defined as 20 MHz during and after initial access, and the maximum bandwidth of a FR2 Redcap UE is defined as 100 MHz during and after initial access. Redcap devices are also characterized by a reduced minimum number of receive branches. For frequency bands where a legacy NR UE is required to be equipped with a minimum of two (2) Rx antenna ports, the minimum number of Rx branches supported for a Redcap UE according to the 3GPP specification is one (1). The 3GPP specification also supports two (2) Rx branches for Redcap UEs in these frequency bands. For bands where legacy NR UEs (except 2-Rx vehicular UEs) are required to be equipped with a minimum of four (4) Rx antenna ports, the minimum number of Rx branches supported by the 3GPP specification for Redcap UEs is one (1). The 3GPP specification also supports two (2) Rx branches for Redcap UEs in these bands. Therefore, a mechanism is desired by which the base station (e.g., gNB) is made aware of the number of Rx branches of the UE.

[0230] Cell operation for initial access

[0231] Figure 6

[0232] Figure 6 A simplified diagram illustrating channel bandwidth (CHBW) and bandwidth part (BWP) configurations for initial access of a device (e.g., a wireless communication device or user equipment device (UE)) to a cell (e.g., via a base station) is shown. Figure 6 As shown, from the perspective of a base station (e.g., gNB), the CHBW is broadcast by the base station in the System Information Block (SIB) and is defined per subcarrier spacing (SCS). When using the initial BWP, the UE applies this CHBW as part of its initial access to the cell. From the perspective of the UE, the cell definition SSB 602 includes a key reference signal that indicates (or provides) the identity of the cell. More specifically, it is the SIB1 identity indicated by the MIB that is part of the SSB burst (Physical Broadcast Channel PBCH part of the MIB). The base station (e.g., gNB) can transmit more SSBs (e.g., Figure 6), but those SSBs are not considered cell-defining SSBs.

[0233] During cell search, the UE searches for or monitors SSBs. To simplify the UE's cell search procedure, SSBs are located on (or transmitted according to) a "global synchronization raster channel," providing the UE with a frequency range for initial search. This is also known as the Global Synchronization Channel Number (GSCN). The GSCN can be considered an integer fraction of the available spectrum or overall available frequency bandwidth, such that SSBs intended to serve as cell-defining SSBs are located only on the GSCN.

[0234] Figure 7

[0235] Figure 7 A simplified diagram showing SSB transmission using GSCN and CHBW and BWP configurations is shown. SSB can also be transmitted over GSCN (e.g. Figure 7 However, these SSBs are not intended to be detected by the UE during cell search. Figure 7 As shown in the figure, SSB2, SSB1 and SSB3 are all located on the GSCN. The network (or cell, for example via the base station / gNB) is free to configure such SSBs without any restrictions on the network as to where the SSBs can be located in the spectrum. Some SSBs may have a MIB that does not point to the location of SIB1. When this happens, the base station (gNB) can (optionally) provide the location of the SSB where a valid SIB1 in the associated MIB can be found. Such information is present in the PDCCH-Config-SIB1 information element (IE) in the MIB. The base station may also choose not to provide such a reference. In general, SIB1 carries information related to evaluating whether a UE is allowed to access a cell and also defines the scheduling of other system information. SIB1 also provides radio resource configuration information common to all UEs, as well as (cell) barring information required for unified access control.

[0236] The SSB includes reference signals and the PBCH which includes the MIB. The MIB provides the following information elements of interest (ie) among others:

[0237] When the SSB is a cell-defined SSB, PDCCH-ConfigSIB1—Indicates the time / frequency resources that carry the physical channels (PDCCH and PDSCH) containing SIB1. Otherwise, for example, when the SSB is not a cell-defined SSB, this IE in the MIB (optional) indicates the location of the cell-defined SSB that can carry valid SIB1.

[0238] • cellBarred - informs the UE whether the UE is allowed to camp on this cell (ie, on the cell that transmits the SSB containing the MIB).

[0239] intraFreqReselection—informs the UE whether there are other cells (also transmitting SSB) in the same frequency band.

[0240] The interpretation of PDCCH-ConfigSIB1 is specified in Tables 13-1 to 13-15 of the 3GPP TS 38.213 specification. Redcap UEs expect the initial BWP configuration for the Redcap UE to be no larger than the BW supported by the Redcap UE, for example, no larger than 20 MHz. The Redcap UE also expects to find a cell-defined SSB that includes reference signals that the UE interprets as reference signals of the serving cell. Finally, the cell-defined SSB is also expected to carry SIB1 information for the Redcap UE.

[0241] Coexistence issues between Redcap devices and traditional devices

[0242] In some cases, a Redcap UE may have to perform downlink communications on an initial downlink (DL) bandwidth part (BWP) shared with other UEs, where the initial DL BWP has a higher bandwidth than the BW supported by the Redcap UE relative to the other UEs. However, when an existing base station (e.g., a base station of a cell, such as a gNB) is intended to support Redcap devices and the base station operates on a cell with a channel bandwidth (CHBW) that is larger than the BW supported by the Redcap devices (e.g., larger than 20 MHz), and the initial DL BWP is also larger than the BW supported by Redcap (e.g., larger than 20 MHz), then the base station cannot use the existing configuration currently outlined in the existing 3GPP standards. In addition, if the base station creates another initial DL BWP that is only for Redcap devices, then legacy devices can also start camping on the cell relying on the existing configuration.

[0243] Figure 8

[0244] The above problems are Figure 8 , which shows a simplified diagram of SSB transmission and CHBW and BWP configuration (as related to the current 3GPP standard) when the initial DL BWP is larger than the specified BWP size supported by the Redcap device (e.g., larger than 20MHz). Figure 8As shown, when the initial DL BWP has a bandwidth greater than that supported by the Redcap UE (e.g., for FR1 Redcap devices, the bandwidth is greater than 20 MHz), the Redcap device cannot use the initial DL BWP as the initial DL BWP for the Redcap device. On the other hand, the base station creating an SSB 802 for only Redcap devices may also be interpreted by legacy devices as another cell-defined SSB, and legacy devices may also start camping on the corresponding cell, even though they may not be intended to camp on the cell (e.g., if the cell has been indicated as prohibited for legacy UEs).

[0245] Successful coexistence of Redcap devices and traditional equipment

[0246] To address at least some of the issues outlined above, a process may be implemented to enable Redcap devices and non-Redcap devices (eg, legacy devices) to coexist without either set of devices accessing or detecting (attempting to access and / or detect) unexpected information.

[0247] Figure 9

[0248] Figure 9 A table illustrating the proposed procedure for ensuring successful coexistence of Redcap devices and legacy devices based on cellBarred indication is shown.

[0249] According to the first option, when the cellBarred IE is detected to be set to true (e.g., set to disabled) in a given SSB, the Redcap UE may ignore the true cellBarred indication. The Redcap UE may not consider the cell to be barred and ignore the IE. This may apply to all Redcap UEs. In other words, unless the SSB is specific to Redcap UEs, when the IE is set to true (e.g., set to disabled), the Redcap UE may simply ignore the indication provided by the cellBarred IE. Figure 9 As indicated in , when cellBarred in the MIB is set to true, Redcap UEs may still consider the cell valid (not barred) and continue to read SIB1. Non-Redcap (e.g., legacy) UEs may skip the cell (considering it barred based on the true indication) and not read SIB1. When cellBarred in the MIB is set to false (FALSE) (not barred), both Redcap UEs and legacy UEs (non-Redcap UEs) may continue to read SIB1.

[0250] According to the second option, which is based in some aspects on the first option, when the network (or cell) actually intends to bar Redcap UEs, then Redcap-UE specific barring can be provided in SIB1. In other words, a new IE, in particular the cellBarred IE, can be introduced and included in SIB1 to provide cell barring information for Redcap UEs in SIB1. Figure 9 As indicated in , when cellBarred in SIB1 is set to true (barred), Redcap UE can read this IE and consider that the cell is barred. When cellBarred in SIB1 is set to false (not barred), Redcap UE can consider that the cell is not barred.

[0251] According to a third option, a new cell barring information element (new cellBarred IE) may be included in SIB1 for Redcap UEs only and may be ignored by non-Redcap UEs or legacy UEs. Figure 9 As indicated in

[15] , regardless of whether the cellBarred IE in SIB1 is set to true or false, legacy UEs completely ignore this IE when reading SIB1. Specifically, when cellBarred in the MIB is set to true, legacy / non-Redcap UEs do not even read SIB1. When cellBarred in the MIB is set to false, legacy / non-Redcap UEs continue to read SIB1 but simply ignore the cellBarred IE in SIB1.

[0252] Figure 10

[0253] Figure 10 Shown are diagrams showing the basis for some embodiments of the present invention. Figure 9 A simplified diagram of a first proposed SSB transmission option and channel bandwidth (CHBW) and bandwidth part (BWP) configuration for a device (e.g., a wireless communication device or UE) making initial access to a cell (e.g., via a base station) is presented. Figure 10 As indicated in the example, the initial DL BWP is greater than 20 MHz. A Redcap UE can camp on a cell only if the SIB1 of the SSB includes Redcap configuration information and / or explicitly sets the new cellBarred IE in SIB1 to false. If the cellBarred IE in SIB1 is missing, the Redcap UE may consider the cell to be one that does not support Redcap devices and may therefore assume that the cell is barred for Redcap devices.

[0254] Figure 11

[0255] Figure 11 A simplified diagram illustrating a second proposed SSB transmission according to the previously presented options and channel bandwidth (CHBW) and bandwidth part (BWP) configuration for initial access of a device (e.g., a wireless communication device or UE) to a cell (e.g., via a base station) is shown. Figure 11 As shown, in this example, the initial DL BWP has a BW of 20 MHz, or more generally, the DL BWP has a BW supported by the Redcap device. In this case, the presence of an initial BWP configuration explicitly for Redcap UEs can be used as an indicator that the cell supports Redcap devices, rather than the Redcap UE using an explicit cellBarred IE to determine whether the cell is barred for Redcap UEs. In other words, the UE can interpret the detection of the initial BWP for Redcap UEs in SIB1 as an indication that the cell allows Redcap devices / UEs. On the other hand, the absence of the initial BWP for Redcap UEs in SIB1 can be interpreted by the UE as the cell being barred for Redcap devices / UEs.

[0256] Figure 12

[0257] Figure 12 A simplified diagram is shown illustrating a third proposed SSB transmission based on previously presented options and a channel bandwidth (CHBW) and bandwidth part (BWP) configuration for initial access of a device (e.g., a wireless communication device or UE) to a cell (e.g., via a base station) in accordance with some embodiments. Figure 12 It shows how to help Redcap UE identify / determine where Redcap supporting cells are located in the spectrum / band. Figure 12 As shown in FIG, when a cell is barred in the MIB and SIB1 explicitly states that a Redcap UE is barred, the Redcap UE can still read the PDCCH-ConfigSIB1 of the barred cell to determine the location of the next SSB including assistance information for the Redcap UE. Figure 12 As indicated, when SIB1 in SSB1 does not include the initial BWP configuration for the Redcap device, the Redcap UE does not use the initial DL BWP corresponding to SSB1. However, even if the cell is barred, the Redcap UE can still read PDCCH-ConfigSIB1, and PDCCH-ConfigSIB1 can indicate to the Redcap UE where SSB 1202 is located, where SSB 1202 includes assistance information for the Redcap UE.

[0258] Figure 13

[0259] Figure 13 A simplified diagram illustrating a fourth proposed SSB transmission and channel bandwidth (CHBW) and bandwidth part (BWP) configuration for initial access (e.g., via a base station) of a device (e.g., a wireless communication device or UE) to a cell (e.g., via a base station) in accordance with some embodiments based on the previously presented options is shown. When Redcap-specific SSBs are placed on a non-GSCN raster, Redcap UEs may not be able to find these SSBs during cell retrieval. To assist Redcap UEs with identifying / determining where in the spectrum / band Redcap-supported cells are located, the network may provide explicit information in SIB1 for cells that support Redcap devices / UEs, but not include the initial BWP for legacy devices. The information may include the location of the next non-GSCN location of the SSB with information to assist Redcap devices. Thus, the network may place Redcap-specific SSBs at non-GSCN locations. As Figure 13 As shown, when the network defines a separate initial DL BWP for Redcap devices / UEs, the initial DL BWP corresponding to SSB1 is not used by Redcap UEs as their initial BWP. Figure 13 When the SSB 1302 shown in FIG1 is in a non-GSNC location (in the frequency domain), the network may include information in SIB1 of SSB1 that indicates to the Redcap UE where the SSB 1302 is located. The Redcap UE is then redirected to SSB 1302 as the cell-defining SSB for the Redcap device based on the information included in SIB1 of SSB1.

[0260] Figure 14

[0261] In some embodiments, SSB for Redcap and non-Redcap devices / UEs may be time domain multiplexed, e.g. Figure 14 As shown. Figure 14 As shown, the network can broadcast Redcap specific cell definition SSBs and legacy cell definition SSBs at the same frequency location, but in a time division multiplexed manner. When detecting that cellBarred is set to true, the Redcap UE can search for SSBs at the same frequency location, but at different times, to check whether the network has broadcast another SSB for the Redcap device / UE. These SSBs can point to different (possibly overlapping) initial DL BWPs intended for legacy UEs and Redcap UEs, respectively.

[0262] Using SSB-PositionsInBurst

[0263] In some embodiments, the network, cell or base station may use a dedicated IE, SSB-PositionsInBurst in SIB1 to provide information about the set of SSB burst positions that the network is broadcasting. It can be assumed that each burst is broadcast with a different beam, up to a specified number, such as 64 possible beams. The network may reserve some of these SSB burst positions for Redcap devices / UEs and other SSB burst positions for non-Redcap devices / UEs. Additional SSB positions / locations (in the frequency domain) that are intended for Redcap UEs only may be provided to (or may be allocated to) Redcap UEs. When a Redcap UE reads SIB1 and this additional configuration information is present in SIB1, the Redcap UE is able to determine / locate the SSB bursts intended for Redcap operation.

[0264] For example, if a first number X of SSBs are used in one SSB burst on the same frequency in a cell, the following options may be implemented:

[0265] Option 1: A second number Y of SSBs (from the number X of SSBs) may include MIB A for legacy UEs, and a third number Z of SSBs (from the number X of SSBs) may include MIB A for redcap UEs. MIB A and MIB B may each clearly indicate which type of UE is barred (e.g., a new bit may be added to the MIB to distinguish between redcap devices / UEs and legacy devices / UEs). MIB A and MIB B may each include different corresponding PDCCH-ConfigSIB1 values ​​to direct different UEs to different CORESETs of SIB1.

[0266] Option 2: A second number Y of SSBs (from the number X of SSBs) may include MIB A for legacy UEs, and a third number Z of SSBs (from the number X of SSBs) may include MIB A for Redcap UEs. MIB A and MIB B may each include their respective corresponding bar settings (e.g., different cellBarred settings), but Redcap UEs may continue to read SIB1 regardless of the value of the bar setting. MIB A and MIB B may each include different corresponding PDCCH-

[0267] ConfigSIB1 value to read different UEs to different CORESETs of SIBs. The network, cell or base station can indicate in SIB1 whether the current SIB1 is for Redcap UEs or legacy UEs, and can further indicate (in the SSB-PositionsInBurst IE) which SSBs are for Redcap UEs and which SSBs are for legacy UEs.

[0268] • Option 3: The SSB includes the same MIB for all types of UEs, and if legacy UEs and Redcap UEs are not prohibited in the MIB, the network, cell or base station may additionally indicate where the SIB1 for Redcap UEs is located in SIB1.

[0269] The options listed above may be implemented, for example, by modifying and / or revising the relevant code portions provided in 3GPP TS 38.331 v.16.5.0, section 6.2.2, page 298, and section 6.3.2, pages 628-629.

[0270] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0271] Embodiments of the present invention may be implemented in any of a variety of forms. For example, in some embodiments, the present invention may be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. In other embodiments, the present invention may be implemented using one or more custom-designed hardware devices such as ASICs. In other embodiments, the present invention may be implemented using one or more programmable hardware elements such as FPGAs.

[0272] In some embodiments, a non-transitory computer-readable storage medium (e.g., a non-transitory memory element) can be configured such that it stores program instructions and / or data, wherein the program instructions, if executed by a computer system, cause the computer system to perform a method, such as any of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any method embodiments described herein, or any combination of such subsets.

[0273] In some embodiments, a device (e.g., a UE) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0274] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A device for wireless communication, the device comprising: A processor configured to: causing a device to receive a cell-defining first synchronization signal block (SSB), wherein the first SSB includes a first information block (IB) indicating whether a cell defined by the SSB is barred; reading a second IB associated with the first IB and, in response to the second IB indicating that the cell is barred, determining that the cell is barred for the device; enabling the device to locate and receive a cell defining a second SSB; as well as Determine whether to connect to a second cell defined by the second SSB based on information included in the second SSB. The apparatus of claim 1 , wherein the device is a reduced-capacity device.

3. The apparatus of claim 2, wherein the processor is further configured to: Responsive to the second IB including information regarding the initial bandwidth portion for reduced capability devices and the second IB not indicating that the cell is barred, it is determined that the cell is valid for the device. 4 . The apparatus of claim 1 , wherein the first IB indicates whether the cell is barred for one or more additional devices other than the device. The apparatus of claim 4 , wherein the one or more additional devices are not reduced-capability devices.

6. The apparatus of claim 1 , wherein the processor is further configured to: The device is enabled to locate and receive the cell-defined second SSB based on the indication provided by the second IB.

7. The apparatus of claim 1 , wherein the processor is further configured to: The position of the second SSB is determined from information included in the second IB, wherein the position of the second SSB is not on a global synchronization channel number.

8. A device for wireless communication, comprising: radio circuitry configured to enable wireless communication of the device; and a processor configured to interoperate with the radio circuitry to: receiving a cell-defining first synchronization signal block (SSB), wherein the first SSB includes a first information block (IB) indicating whether the cell defined by the SSB is barred; reading a second IB associated with the first IB and, in response to the second IB indicating that the cell is barred, determining that the cell is barred for the device; The positioning and receiving cell defines the second SSB; as well as Determine whether to connect to a second cell defined by the second SSB based on information included in the second SSB.

9. The device of claim 8, wherein the device is a reduced capability device.

10. The apparatus of claim 9, wherein the processor is configured to further interoperate with the radio circuitry to: Responsive to the second IB including information regarding the initial bandwidth portion for reduced capability devices and the second IB not indicating that the cell is barred, it is determined that the cell is valid for the device.

11. The apparatus of claim 8, wherein the first IB indicates whether the cell is barred for one or more additional devices other than the device.

12. The device of claim 11, wherein the one or more additional devices are not reduced capability devices.

13. The apparatus of claim 8, wherein the processor is configured to further interoperate with the radio circuitry to: Based on the indication provided by the second IB, the cell locating and receiving the cell defines a second SSB.

14. The apparatus of claim 8, wherein the processor is configured to further interoperate with the radio circuitry to: The position of the second SSB is determined from information included in the second IB, wherein the position of the second SSB is not on a global synchronization channel number.

15. A non-transitory memory element storing instructions executable by a processor to: causing a device to receive a cell-defining first synchronization signal block (SSB), wherein the first SSB includes a first information block (IB) indicating whether a cell defined by the SSB is barred; reading a second IB associated with the first IB and, in response to the second IB indicating that the cell is barred, determining that the cell is barred for the device; enabling the device to locate and receive a cell defining a second SSB; as well as Determine whether to connect to a second cell defined by the second SSB based on information included in the second SSB.

16. The non-transitory memory element of claim 15, wherein the device is a reduced capability device; and wherein the instructions are further executable by the processor to: Responsive to the second IB including information regarding the initial bandwidth portion for reduced capability devices and the second IB not indicating that the cell is barred, it is determined that the cell is valid for the device. 17 . The non-transitory memory element of claim 15 , wherein the first IB indicates whether the cell is prohibited for one or more additional devices other than the device, wherein the one or more additional devices are not reduced-capability devices.

Images