Physical broadcast channel enhancement for lightweight new radio

Abstract

Methods, systems, and apparatus for wireless communications are described. A user equipment (UE) can distinguish synchronization signal blocks (SSBs) intended for different UE categories. For example, a base station can send different SSBs in a physical broadcast channel with different configurations or parameters to indicate different UE categories, where the UE can monitor and receive SSBs for its UE category. The UE can operate according to a UE category associated with a lower bandwidth (e.g., a lightweight version of New Radio (NR)) and can identify SSBs associated with the UE category to connect with the base station. The UE can identify the SSB associated with the UE category based on a subcarrier level offset value implicitly or explicitly indicated to the UE. In addition, the base station can send fields to indicate different parameters for subsequent communications sent according to the UE category.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 983,522, filed on February 28, 2020 by LEI et al., entitled “PHYSICAL BROADCAST CHANNEL ENHANCEMENT FOR NEW RADIO LIGHT COMMUNICATIONS,” and U.S. Patent Application No. 17 / 180,375, filed on February 19, 2021 by LEI et al., entitled “PHYSICAL BROADCAST CHANNEL ENHANCEMENT FOR NEW RADIO LIGHT COMMUNICATIONS,” each of which has been assigned to the assignee of this patent application. Technical Field

[0003] The following relates generally to wireless communications and, more particularly, to physical broadcast channel (PBCH) enhancements. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems or LTE-A Pro systems, and fifth generation (5G) systems that may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA) or discrete Fourier transform extended orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node supporting communication of multiple communication devices simultaneously, which may be referred to as user equipment (UE) in addition. Summary of the invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatus for physical broadcast channel enhancements (PBCH) that support lightweight new radio (NR) communications. In general, the described techniques provide for distinguishing synchronization signal blocks (SSBs) intended for different categories of user equipment (UE). For example, a base station may send different SSBs in a PBCH with different configurations or parameters to indicate different UE categories, where the UE may monitor and receive SSBs for its UE category. As described herein, a UE may operate in accordance with a UE category associated with a lower bandwidth (e.g., lightweight NR (NR Light)) and may identify SSBs associated with the UE category to establish or modify a connection with a base station. In some cases, a UE may identify a subcarrier level offset value (kS) that is implicitly or explicitly indicated to the UE (e.g., via the PBCH). SSB ) to identify the SSB associated with the UE category. In addition, the base station can send fields in the PBCH to indicate different parameters (e.g., related to repetition or frequency hopping) for subsequent communications sent according to the UE category. The UE can also determine the multiplexing pattern of communications sent according to the UE category (e.g., SSB, control resource set (CORESET), system information block (SIB), etc.) based on the different subcarrier spacing (SCS) and bandwidth being used by the base station.

[0006] A method of wireless communication is described. The method may include: receiving a SSB at a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determining, based on the indication, that the UE belongs to the UE category supported by the SSB; and establishing or modifying a connection between the UE and a base station using the SSB based on the determination.

[0007] An apparatus for a method of wireless communication is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive a SSB at a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determine, based on the indication, that the UE belongs to a UE category supported by the SSB; and establish or modify a connection between the UE and a base station using the SSB based on the determination.

[0008] Another apparatus for a method of wireless communication is described. The apparatus may include components for: receiving a SSB at a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determining, based on the indication, that the UE belongs to the UE category supported by the SSB; and establishing or modifying a connection between the UE and a base station using the SSB based on the determination.

[0009] A non-transitory computer-readable medium storing code for a method of wireless communication is described. The code may include instructions executable by a processor to: receive a SSB at a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determine, based on the indication, that the UE belongs to the UE category supported by the SSB; and establish or modify a connection between the UE and a base station using the SSB based on the determination.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving an SSB may include operations, features, components, or instructions for receiving an indication of a subcarrier offset between the SSB and a carrier resource block grid, wherein establishing or modifying a connection between a UE and a base station may be based on the subcarrier offset.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the UE category supported by the SSB can be based on a range within which the subcarrier offset falls.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the subcarrier offset may be based on a combination of a first set of one or more bits in a first field of the SSB and a second set of one or more bits in a second field of the SSB.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a valid range of subcarrier offsets based on a UE category supported by an SSB, wherein establishing or modifying a connection between a UE and a base station may also be based on subcarrier offsets in the SSB that fall within a valid range.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the SSB may include operations, features, components, or instructions for receiving one or more bits that explicitly indicate a UE category supported by the SSB.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving repetition information of a broadcast channel from a base station, wherein the repetition information may be based on a UE category supported by the SSB.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the repetition information may include operations, features, components, or instructions for an indication of support for intra-slot repetition on a broadcast channel, an indication of support for inter-slot repetition on a broadcast channel, or a combination thereof.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the repetition information includes an indication of a number of transmission repetitions configured for the broadcast channel.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, frequency hopping information is received in one or more of: a master information block (MIB), a physical layer payload of a broadcast channel, a demodulation reference signal (DMRS) scrambling identifier of a broadcast channel, or any combination thereof.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the repetition information is received in one or more of: a MIB, a physical layer payload of a broadcast channel, a DMRS scrambling identifier of a broadcast channel, or any combination thereof.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving frequency hopping information for a broadcast channel from a base station, wherein the frequency hopping information may be based on a UE category supported by SSB.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the frequency hopping information may include operations, features, components, or instructions for an indication of support for intra-slot frequency hopping on a broadcast channel, an indication of support for inter-slot frequency hopping on a broadcast channel, or a combination thereof.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a multiplexing pattern of SSBs, a CORESET of broadcast control information, and SIBs based on a UE category supported by the SSBs.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining a multiplexing pattern based on a UE category supported by an SSB may include operations, features, components, or instructions for mapping the multiplexing pattern to a combination of a UE bandwidth, an SCS associated with the SSB, and an SCS of broadcast control information of a CORESET.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, establishing or modifying a connection may include: receiving system information in an SSB and performing one or more operations, features, components, or instructions of a radio resource control (RRC) connection establishment procedure, an RRC connection reconfiguration procedure, or an RRC release procedure based at least in part on the system information.

[0025] A method of wireless communication at a base station is described. The method may include: sending a SSB to a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determining that the UE belongs to the UE category supported by the SSB; and establishing or modifying a connection between the UE and the base station using the SSB based on the determination.

[0026] An apparatus for a method of wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: send a SSB to a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determine that the UE belongs to a UE category supported by the SSB; and establish or modify a connection between the UE and the base station using the SSB based on the determination.

[0027] Another apparatus for a method of wireless communication at a base station is described. The apparatus may include components for: sending a SSB to a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determining that the UE belongs to the UE category supported by the SSB; and establishing or modifying a connection between the UE and the base station using the SSB based on the determination.

[0028] A non-transitory computer-readable medium storing code for a method of wireless communication at a base station is described. The code may include instructions executable by a processor to: send a SSB to a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determine that the UE belongs to a UE category supported by the SSB; and establish or modify a connection between the UE and the base station using the SSB based on the determination.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an SSB may include operations, features, components, or instructions for sending an indication of a subcarrier offset between the SSB and a carrier resource block grid, wherein establishing or modifying a connection between a UE and a base station may be based on the subcarrier offset.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the UE category supported by the SSB can be based on a range within which the subcarrier offset falls.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the subcarrier offset may be based on a combination of a first set of one or more bits in a first field of the SSB and a second set of one or more bits in a second field of the SSB.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a valid range of subcarrier offsets based on a UE category supported by an SSB, wherein establishing or modifying a connection between a UE and a base station may also be based on subcarrier offsets in the SSB that fall within a valid range.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the SSB may include operations, features, components, or instructions for sending one or more bits that explicitly indicate a UE category supported by the SSB.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending repetition information of a broadcast channel to a UE, wherein the repetition information may be based on a UE category supported by SSB.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the repetition information may include operations, features, components, or instructions for an indication of support for intra-slot repetition on a broadcast channel, an indication of support for inter-slot repetition on a broadcast channel, or a combination thereof.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the repetition information includes an indication of a number of transmission repetitions configured for the broadcast channel.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the repetition information is received in one or more of: a MIB, a physical layer payload of a broadcast channel, a DMRS scrambling identifier of a broadcast channel, or any combination thereof.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending frequency hopping information of a broadcast channel to a UE, wherein the frequency hopping information may be based on a UE category supported by SSB.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the frequency hopping information may include operations, features, components, or instructions for an indication of support for intra-slot frequency hopping on a broadcast channel, an indication of support for inter-slot frequency hopping on a broadcast channel, or a combination thereof.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the frequency hopping information is received in one or more of: a MIB, a physical layer payload of a broadcast channel, a DMRS scrambling identifier of a broadcast channel, or any combination thereof.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a multiplexing pattern of SSBs, a CORESET of broadcast control information, and SIBs based on a UE category supported by the SSBs.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining a multiplexing pattern based on a UE category supported by an SSB may include operations, features, components, or instructions for mapping the multiplexing pattern to a combination of a UE bandwidth, an SCS associated with the SSB, and an SCS of broadcast control information of a CORESET.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining that a UE belongs to a UE category may include operations, features, components, or instructions for receiving capability information indicating the UE category from the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 and Figure 2 An example of a wireless communication system supporting physical broadcast channel (PBCH) enhancements for lightweight new radio (NR) communications in accordance with aspects of the present disclosure is illustrated.

[0045] Figure 3A and Figure 3B An example of resource and synchronization block configuration for PBCH enhancement supporting lightweight NR communications according to aspects of the present disclosure is illustrated.

[0046] Figure 4 An example of a flow chart for PBCH enhancement supporting lightweight NR communications in accordance with aspects of the present disclosure is illustrated.

[0047] Figure 5A and Figure 5B An example of offset values ​​and a flow chart for PBCH enhancement supporting lightweight NR communications according to aspects of the present disclosure is illustrated.

[0048] Figure 6 Examples of offset values ​​for PBCH enhancement supporting lightweight NR communications in accordance with aspects of the present disclosure are illustrated.

[0049] Figure 7 An example of an information field decision tree for PBCH enhancements supporting lightweight NR communications in accordance with aspects of the present disclosure is illustrated.

[0050] Fig. 8A and Figure 8B An example of a PBCH enhanced time division multiplexing (TDM) pattern supporting lightweight NR communications according to aspects of the present disclosure is illustrated.

[0051] Fig. 9 An example of a PBCH enhanced frequency division multiplexing (FDM) pattern supporting lightweight NR communications according to various aspects of the present disclosure is illustrated.

[0052] Fig. 10A and Fig. 10B An example of a hybrid multiplexing pattern for PBCH enhancement supporting lightweight NR communications according to aspects of the present disclosure is illustrated.

[0053] Fig.11 An example of a process flow for PBCH enhancement supporting lightweight NR communications in accordance with aspects of the present disclosure is illustrated.

[0054] Fig.12 and Fig.13 A block diagram of a device supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is shown.

[0055] Fig.14 A block diagram of a communication manager supporting PBCH enhancements for lightweight NR communications in accordance with aspects of the present disclosure is shown.

[0056] Fig.15 A schematic diagram of a system including devices supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is shown.

[0057] Fig.16 and Fig.17 A block diagram of a device supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is shown.

[0058] Fig.18 A block diagram of a communication manager supporting PBCH enhancements for lightweight NR communications in accordance with aspects of the present disclosure is shown.

[0059] Fig.19 A schematic diagram of a system including devices supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is shown.

[0060] Figure 20 to Figure 26 A flow chart illustrating a method for PBCH enhancement to support lightweight NR communications according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0061] In some wireless communication systems, communications for lightweight new radio (NR) devices may be defined. Lightweight NR (e.g., NR-Lite) devices may include wearable UEs, industrial wireless sensor networks (IWSNs), surveillance cameras, low-end smartphones, loose Internet of Things (IoT) devices, and the like. In addition, for lightweight NR communications, enhanced coverage recovery, relaxed timelines (e.g., 10-30 milliseconds (ms) latency), and reduced user equipment (UE) bandwidth (e.g., 1 to 2 megahertz (MHz)) may be defined that are different from other communication systems for NR (e.g., lightweight NR may operate according to different communication standards such as ultra-reliable low latency communications (URLLC), enhanced mobile broadband (eMBB) communications, enhanced machine type communications (eMTC), long term evolution (LTE), and the like). In some cases, lightweight NR communications may enable different wireless communications to support a single wireless communication system (e.g., NR network) for different levels of devices. In some cases, a user equipment UE may monitor and receive a physical broadcast channel (PBCH) from a base station to receive configuration information, synchronization information, and additional information for establishing or modifying a connection with a base station. However, techniques for indicating support for Light NR and indicating different parameters for Light NR communications may be inefficient or non-existent (e.g., such as PBCH transmissions and information included in the PBCH and the PBCH's synchronization signal blocks (SSBs)).

[0062] As described herein, a process for PBCH enhancement for a lightweight NR UE is presented while also maintaining the same SSB transmission chain for other types of communications (e.g., NR SSBs). In some cases, a base station may transmit an SSB for lightweight NR communications, and a lightweight NR UE may recognize that the SSB is for lightweight NR communications and may establish (e.g., or modify) a connection with the base station based on recognizing the SSB and using relevant information in the SSB. For example, the SSB may include a value (e.g., k) representing a subcarrier level offset between the SSB and a carrier resource block (CRB) grid. SSB value), where the value of the subcarrier level offset indicates that the SSB is used for lightweight NR communication based on being outside the valid range of the different frequency band. That is, the first frequency range (e.g., FR1) can have a valid k in a first range (e.g., from 0 to 23 ([0,23])). SSB values, and a second frequency range (eg, FR2) may have valid k in a second range (eg, from 0 to 11 ([0,11])). SSB value, so that if k in SSB SSB If the value of k is outside these ranges for the corresponding frequency range, the UE may recognize that the SSB includes configuration information to be used for lightweight NR communication.SSB The value can be k for cell definition SSB SSB values ​​outside the value range (e.g., such that if the UE identifies k in the value range SSB If the value is k, the UE can determine that the SSB is for lightweight NR), or it can be an explicitly indicated value (for example, a specific k in the SSB used to indicate lightweight NR communication). SSB value).

[0063] In addition, the base station can add different information elements or fields in the PBCH to indicate different parameters of the lightweight NR communication. For example, the base station can add fields to the PBCH to indicate intra-slot or inter-slot repetition, intra-slot or inter-slot frequency hopping, or both for broadcasting physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), demodulation reference signal (DMRS), etc. In some cases, the new field can indicate whether inter-slot or intra-slot repetition or frequency hopping is enabled, whether the repetition level (e.g., the value of the repetition) is enabled, or both. These new fields can be mapped to unused, reserved, or reused parts of the PBCH, the master information block (MIB) transport block (TB), the physical payload of the PBCH, the DMRS scrambling identifier (ID) of the PBCH, etc. In addition, the base station can indicate the multiplexing pattern of the lightweight NR communication based on the SSB (e.g., time division multiplexing (TDM) pattern, frequency division multiplexing (FDM) pattern, hybrid pattern, etc.). For example, the UE can determine the multiplexing pattern of lightweight NR communication based on the UE's bandwidth (e.g., configured by the base station), the subcarrier spacing (SCS) of the SSB, and the SCS of the downlink message from the base station (PBCH, Type0-PDCCH, etc.).

[0064] Various aspects of the present disclosure are initially described in the context of a wireless communication system. In addition, various aspects of the present disclosure are illustrated by additional wireless communication systems, resource blocks (RBs) and SSB configurations, flow charts, offset values, information field decision trees, TDM patterns, FDM patterns, hybrid multiplexing patterns, and process flows. Various aspects of the present disclosure are further illustrated and described in conjunction with apparatus diagrams, system diagrams, and flow charts involving PBCH enhancement for lightweight NR communications.

[0065] Figure 1An example of a wireless communication system 100 that supports PBCH enhancement for lightweight NR communication according to various aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be an LTE network, an LTE Advanced (LTE-A) network, an LTE-A Pro network, or an NR network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof, etc.

[0066] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be devices of different forms or capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support communication of signals according to one or more radio access technologies.

[0067] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be fixed or mobile, or fixed or mobile at different times. The UEs 115 may be devices of different forms or with different capabilities. Figure 1 Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), such as Figure 1 shown.

[0068] Base stations 105 may communicate with core network 130, or with each other, or both. For example, base stations 105 may interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base stations 105 may communicate with each other via backhaul links 120 (e.g., via X2, Xn, or other interfaces) directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130), or both. In some examples, backhaul links 120 may be or include one or more wireless links.

[0069] One or more of the base stations 105 described herein may include or may be referred to by a person of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a giga-NodeB (any of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology.

[0070] In other examples, UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal or a client. UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an IoT device, an Internet of Everything (IoE) device or a machine type communication (MTC) device and other examples, which may be implemented in various objects, such as appliances, vehicles, meters and other examples.

[0071] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network devices including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0072] UE 115 and base station 105 can communicate with each other wirelessly via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio spectrum resources with a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio spectrum band (e.g., bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel can carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating operations for carriers, user data, or other signaling. The wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers according to the carrier aggregation configuration. Carrier aggregation can be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0073] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel raster for discovery by a UE 115. A carrier may operate in a standalone mode, where initial acquisition and connection may be performed by a UE 115 via a carrier, or a carrier may operate in a non-standalone mode, where a connection is anchored using a different carrier (e.g., of the same or different radio access technology).

[0074] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0075] A carrier may be associated with a particular bandwidth of a radio spectrum, and in some examples, a carrier bandwidth may be referred to as a "system bandwidth" of a carrier or wireless communication system 100. For example, a carrier bandwidth may be one of a plurality of determined bandwidths of a carrier for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). A device of the wireless communication system 100 (e.g., a base station 105, a UE 115, or both) may have a hardware configuration that supports communications on a particular carrier bandwidth, or may be configured to support communications on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or a UE 115 that supports simultaneous communications via carriers associated with a plurality of carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0076] The signal waveform transmitted on the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are anti-correlated. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 may be. Wireless communication resources may refer to a combination of radio spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity of communications with UE 115.

[0077] One or more parameter sets for a carrier may be supported, where the parameter set may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be restricted to the one or more active BWPs.

[0078] The time interval of the base station 105 or the UE 115 may be expressed as a multiple of a basic time unit. For example, the basic time unit may be T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specific duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0079] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple symbol periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple mini-time slots containing one or more symbols. In addition to the cyclic prefix, each symbol period may contain one or more (e.g., N f ) sampling period. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0080] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0081] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a TDM technique, an FDM technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by the number of symbol periods and may extend across the system bandwidth of a carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search for a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with the coding information for a control information format having a given payload size. A search space set may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0082] Each base station 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots or other types of cells, or various combinations thereof). The term "cell" can refer to a logical communication entity used to communicate with the base station 105 (e.g., via a carrier), and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish neighboring cells. In some examples, a cell can also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the base station 105, these cells can range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell can be or include a building, a subset of a building, or an external space between or overlapping geographic coverage areas 110, and the like.

[0083] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. A small cell may be associated with a base station 105 of lower power than a macro cell, and the small cell may operate in the same or different (e.g., authorized, unauthorized) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 that has an association with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A base station 105 may support one or more cells, and may also support communications on one or more cells using one or more component carriers.

[0084] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0085] In some examples, base stations 105 may be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0086] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automatic communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to the application or humans interacting with it. Some UEs 115 may be designed to collect information or implement automatic behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0087] Some UEs 115 may be configured to employ a reduced power consumption operating mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception, but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating on a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or RBs) within a carrier, within a guard band of a carrier, or outside a carrier.

[0088] The wireless communication system 100 can be configured to support ultra-reliable communication or low-delay communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support URLLC or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-delay or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication, and can be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include service prioritization, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-delay, mission-critical, and ultra-reliable low-delay are used interchangeably herein.

[0089] In some examples, UE 115 may also be able to communicate directly with other UE 115 via a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within a geographic coverage area 110 of a base station 105. Other UEs 115 in this group may be outside the geographic coverage area 110 of the base station 105, or may otherwise not be able to receive transmissions from the base station 105. In some examples, a group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.

[0090] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in a V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with a network using vehicle-to-network (V2N) communication via one or more network nodes (e.g., base station 105), or both.

[0091] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connection, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnections to an external network. The control plane entity may manage non-access stratum (NAS) functions associated with the core network 130 for UE 115 served by the base station 105, such as mobility, authentication, and bearer management. User IP packets may be delivered through a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator's IP service 150. The network operator IP service 150 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0092] Some of the network devices, such as the base station 105, may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with the UE 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transmission entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs), or merged into a single network device (e.g., base station 105).

[0093] The wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, however, the waves may be sufficient to penetrate structures for macro cells to provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0094] The wireless communication system 100 can utilize both licensed and unlicensed radio spectrum bands. For example, the wireless communication system 100 can employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio spectrum band, devices such as base stations 105 and UEs 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in licensed bands. Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

[0095] The base station 105 or UE 115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographic locations. The base station 105 may have an antenna array with multiple rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals sent via the antenna ports.

[0096] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to form or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other direction).

[0097] The base station 105 or the UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communications with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the base station 105 in different directions. For example, the base station 105 may send signals according to different sets of beamforming weights associated with different transmit directions. Transmissions in different beam directions may be used to identify (e.g., by a transmitting device such as the base station 105, or by a receiving device such as the UE 115) a beam direction for later transmission or reception by the base station 105.

[0098] The wireless communication system 100 can be a packet-based network operated according to a layered protocol stack. In the user plane, the communication at the bearer or packet data convergence protocol (PDCP) layer can be based on IP. The radio link control (RLC) layer can perform packet segmentation and reorganization to communicate on a logical channel. The medium access control (MAC) layer can perform priority processing and multiplex the logical channel into a transport channel. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration, and maintenance of an RRC connection (which supports radio bearers for user plane data) between UE 115 and base station 105 or core network 130. At the physical layer, a transport channel can be mapped to a physical channel.

[0099] UE 115 and base station 105 can support retransmission of data to increase the possibility of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data through communication link 125. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC) and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support the same time slot HARQ feedback, wherein the device can provide HARQ feedback for data received in the previous symbol in the time slot in a specific time slot. In other cases, the device can provide HARQ feedback in a subsequent time slot or according to some other time intervals.

[0100] A UE 115 attempting to access a wireless network may perform an initial cell search by detecting a primary synchronization signal (PSS) from a base station 105. The PSS may enable synchronization of time slot timing and may indicate a physical layer identification value. The UE 115 may then receive a secondary synchronization signal (SSS). The SSS may enable radio frame synchronization and may provide a cell identification value, which may be combined with a physical layer identification value to identify a cell. The SSS may also enable detection of duplex mode and cyclic prefix length. Some systems (such as TDD systems) may send SSS but not PSS. Both PSS and SSS may be located in the center 62 and 72 subcarriers of a carrier, respectively. In some cases, the base station 105 may use multiple beams to send synchronization signals (e.g., PSS, SSS, etc.) in a beam scanning manner through a cell coverage area 110. In some cases, PSS, SSS, broadcast information (e.g., PBCH) or a combination thereof may be sent within different synchronization signal (SS) blocks (e.g., SSB) on corresponding directional beams, wherein one or more SS blocks may be included within an SS burst.

[0101] After receiving the PSS and SSS, the UE 115 may receive the MIB, which may be sent in the PBCH. The MIB may include system bandwidth information, SFN, and physical HARQ indicator channel (PHICH) configuration. After decoding the MIB, the UE 115 may receive one or more SIBs. For example, the first SIB (SIB1) may include cell access parameters and scheduling information for other SIBs. Decoding SIB1 may enable the UE 115 to receive the second SIB (SIB2). SIB2 may include RRC configuration information related to random access channel (RACH) procedures, paging, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, sounding reference signal (SRS), and cell barring.

[0102] After completing the initial cell synchronization, the UE 115 can decode the MIB, SIB1 and SIB2 before accessing the network. The MIB can be sent on the PBCH and can utilize the first 4 OFDMA symbols of the second time slot of the first subframe of each radio frame. The MIB can use the middle 6 RBs (72 subcarriers) in the frequency domain. The MIB can carry information for the initial access of the UE, including the downlink channel bandwidth in terms of RBs, PHICH configuration (duration and resource allocation), and SFN. The new MIB can be broadcast once every fourth radio frame (SFN mod 4=0) and rebroadcast once every frame (10ms). Each repetition can be scrambled with a different scrambling code.

[0103] After reading the MIB (new version or copy), the UE 115 can try different phases of the scrambling code until the UE 115 obtains a successful CRC check. The phase of the scrambling code (0, 1, 2, or 3) can enable the UE 115 to identify which of the four repetitions has been received. Therefore, the UE 115 can determine the current SFN by reading the SFN in the decoded transmission and adding the scrambling code phase. After receiving the MIB, the UE can receive one or more SIBs. Different SIBs can be defined according to the type of system information transmitted. The new SIB1 can be sent in the fifth subframe of every eighth frame (SFN mod 8=0) and rebroadcast every other frame (20 milliseconds). SIB1 may include access information (including cell identification information) and may indicate whether the UE 115 can camp on the cell. SIB1 may also include cell selection information, such as cell selection parameters. In addition, SIB1 may include scheduling information for other SIBs. SIB2 can be dynamically scheduled based on the information in SIB1 and includes access information and parameters related to common and shared channels. The periodicity of SIB2 may be set to 8, 16, 32, 64, 128, 256 or 512 radio frames.

[0104] After the UE 115 decodes SIB2, the UE 115 may send a RACH preamble to the base station 105. For example, the UE 115 or the base station 105 may randomly select a RACH preamble from a set of 64 predetermined sequences. This may enable the base station 105 to distinguish between multiple UEs 115 attempting to access the system at the same time. The base station 105 may respond with a random access response that provides an uplink resource grant, a timing advance, and a temporary cell-radio network temporary identifier (C-RNTI). The UE 115 may then send an RRC connection request together with a temporary mobile subscriber identity (TMSI) (e.g., if the UE 115 has previously been connected to the same wireless network) or a random identifier. The RRC connection request may also indicate the reason why the UE 115 is connecting to the network (e.g., emergency, signaling, data exchange, etc.). The base station 105 may respond to the connection request with a contention resolution message addressed to the UE 115, wherein the contention resolution message may provide a new C-RNTI. If the UE 115 receives a contention resolution message with a correct identity, the UE 115 can proceed with the RRC setup. If the UE 115 does not receive a contention resolution message (e.g., if there is a collision with another UE 115), the UE 115 can repeat the RACH process by sending a new RACH preamble. This message exchange between the UE 115 and the base station 105 for random access can be referred to as a four-step RACH process.

[0105] In some cases, minimum system information (MSI) can be mapped to three parts of the PBCH. For example, the MSI can include a set of bits (e.g., 35 bits) that a wireless device (e.g., UE 115) can use to connect to the base station 105 that sends the PBCH. The three parts of the PBCH can include the MIB, the physical layer (PHY) payload, and the DMRS scrambling ID. For the MIB, a first subset of the bit set (e.g., 24 of the 35 bits) can be mapped to different parts of the MIB (e.g., systemFrameNumber, subCarrierSpacingCommon, ssb-SubcarrierOffset, dmrs-TypeA-Position, pdcch-ConfigSIB1, cellBarred, intraFreReselection, spare, etc.). For the PHY payload, a second subset of the set of bits (e.g., eight (8) bits out of 35 bits) may be mapped to different portions of the PHY payload (e.g., four (4) least significant bits (LSBs) of the SFN, a half-frame index, a most significant bit (MSB) of a subcarrier offset, an MSB of an SSB block index, etc.). For the DMRS scrambling ID, a third subset of the set of bits (e.g., 3 bits out of 35 bits) may be mapped to a portion of the DMRS scrambling ID (e.g., an LSB of an SSB index).

[0106] Table 1 below may indicate different numbers of reserved bits currently allocated to different parts of the PBCH based on respective use cases. The use cases may include communications in frequency range 1 (FR1), frequency range 2 (FR2), unlicensed bands for NR communications (e.g., NR unlicensed (NR-U) bands, such as bands below 6 GHz (sub6)), etc.

[0107] Table 1 - Reserved bits in PBCH

[0108]

[0109] As shown, different bits in different parts of the PBCH (eg, MIB, PHY payload / payload, etc.) may be reserved, which may be used for other potential signaling in the PBCH.

[0110] In some wireless communication systems, different types of UEs 115 (e.g., advanced smartphones for eMBB communications, other vertical types of UEs 115 for URLLC, V2X, etc.) may have different rules and operating parameters. However, wireless communication systems may benefit from the scalability of NR and can be deployed in a more efficient and cost-effective manner. For example, peak throughput, latency requirements, reliability requirements, or a combination thereof may be relaxed, and efficiency (e.g., power consumption, system overhead, etc.) and cost improvements may be expected. Therefore, different types of communications may be defined for other UEs 115 that were not previously covered. These other UEs 115 may use lightweight NR communications (e.g., UE capabilities / classifications) and may be referred to as lightweight NR UEs 115 with higher coverage recovery, relaxed timelines (e.g., 5 to 10 milliseconds of latency), and reduced UE bandwidth. For example, lightweight NR UEs 115 may include wearable devices (e.g., smart watches), IWSNs, surveillance cameras, low-end smartphones, etc.

[0111] In addition, for some wireless communication systems, the minimum channel bandwidth (e.g., on a single component carrier) may be related to the frequency band (e.g., FR1 or FR2) and the SCS of the SS or PBCH (e.g., SSB) and type 0 PDCCH (e.g., SCS SSB and SCS PDCCH ). For example, for FR1, 15 / 30kHz SCS SSB The minimum channel bandwidth may be given by 5 / 10 MHz, respectively. In order to accommodate the reduced capabilities of the lightweight NR UE 115, new system information elements / blocks may be configured to support coverage recovery, relaxed timelines, and reduced UE bandwidth associated with the lightweight NR UE 115. In addition, some of the information elements belonging to the MIB and SIB may no longer be useful or valid for lightweight NR (for example, system information (SI) of previous wireless communications designed for previous NR systems may be simplified, deleted, or reused to reduce the signaling overhead of lightweight NR). For the coexistence of lightweight NR UE 115 and other UEs 115, the same or similar PSS and SSS designs may be used with the same bandwidth and transmit chain of the PBCH for any UE 115 to monitor and receive.

[0112] As described herein, the wireless communication system 100 can support the PBCH enhancement strategy for the lightweight NR UE 115 without changing the transmission chain of the SSB in the PBCH. For example, the subcarrier level offset value (e.g., k SSB) or reserved bits of the PBCH to support PBCH type differentiation (e.g., whether different transmissions in the PBCH are intended for lightweight NR communication or other types of communication, such as eMBB, URLLC, etc.). In addition, reserved or unused bits in the PBCH may be reused (e.g., in the MIB, in the PHY payload of the PBCH, or in both) to carry information elements for different UE capabilities as part of lightweight NR communication, and different adaptive multiplexing patterns may be specified for the lightweight NR UE 115 for SSBs (e.g., SS or PBCH), for a type0-PDCCH common search space (CSS) set (e.g., CORESET0), for SIB1 in the PBCH, or a combination thereof.

[0113] Figure 2 An example of a wireless communication system 200 supporting PBCH enhancement for lightweight NR communication according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. The wireless communication system 200 can include a base station 105-a and a UE 115-a, which can be examples of corresponding base stations 105 and UE 115, respectively, such as in conjunction with Figure 1 In some cases, base station 105-a and UE 115-a may communicate using resources (eg, time and frequency resources) of carrier 205.

[0114] As described herein, a UE 115-a may be a lightweight NR device (e.g., a UE category) that uses lower bandwidth than other UEs 115 (e.g., with relaxed timelines or delays and enhanced coverage recovery). The UE category may be based on one or more types of communications supported by the UE 115-a, such as lightweight NR communications. Thus, when compared to other UEs 115 (e.g., standard UEs 115), the lightweight NR device may operate according to different system parameters of the PBCH 210 (e.g., broadcast or otherwise transmitted on resources of the carrier 205) to synchronize and connect to the NR network (e.g., via the base station 105-a). However, there may not be a separate SSB defined for lightweight NR communications, and there may not be a way for the UE 115-a (e.g., and other lightweight NR devices) to distinguish between SSBs intended for lightweight NR devices and SSBs intended for UEs 115 with wider bandwidths.

[0115] In some wireless communication systems, k SSB It can represent the subcarrier level offset between SSB and CRB grid, where k of SSB is defined by the cell. SSBThe valid range of is [0,23] for FR1 and [0,11] for FR2. If UE 115 detects a first SSB and determines k of the first SSB SSB If the value of k is outside the valid range of the cell-defined SSB, the UE 115 may assume that no CORESET (e.g., CORESET0) is configured for the first SSB. Additionally or alternatively, k may be SSB The different mapping procedures of NR-lite may be used for NR-lite devices without affecting the behavior of other UEs 115 that are not operating according to or using NR-lite communications. In some cases, NR-lite devices (e.g., UE 115-a) may use SSBs configured for other wireless communication systems for reference signal measurements, and other UEs 115 (e.g., eMBB UEs 115, URLLC UEs 115, etc.) may use SSBs configured for NR-lite for reference signal measurements.

[0116] As described herein, base station 105-a and UE 115-a may use k SSB The different mapping processes of the PBCH 210 are used to identify whether the SSB 215 sent in the PBCH 210 is intended for lightweight NR communication. For example, the base station 105-a may SSB (For example, k SSB,NR-light ) is mapped to the k value of the cell definition SSB used in other wireless communication systems SSB The range of values ​​does not overlap (e.g., implicitly indicated). Additionally or alternatively, the base station 105-a can indicate the PBCH type distinction based on reserved bits in the MIB or PHY payload of the PBCH 210. That is, the base station 105-a can explicitly indicate whether the SSB 215 is intended for lightweight NR communication based on using reserved bits in different parts of the PBCH 210.

[0117] In addition, to indicate different UE capabilities for lightweight NR communications, the base station 105-a may send one or more configuration parameters 220 to the UE 115-a (e.g., in the PBCH 210). For example, the base station 105-a may add information elements and fields to the PBCH 210 to support coverage enhancement for broadcasting different downlink messages (e.g., PDCCH, PDSCH, DMRS, etc.) to the UE 115-a. In some cases, the base station 105-a may add fields to the PBCH 210 to indicate support for intra-slot or inter-slot repetition, intra-slot or inter-slot frequency hopping for broadcasting different downlink messages. The added fields may be mapped to a subset of unused, reserved, or reused information bits carried by the PBCH 210 (e.g., including a MIB TB, a PHY payload of the PBCH 210, a DMRS scrambling ID of the PBCH 210, or a combination thereof).

[0118] In some cases, UE 115-a may also perform a multiplexing pattern determination 225 to determine the multiplexing pattern (e.g., PBCH 210, SSB 215, CSS set in PBCH 210, SIB1 in PBCH 210, or a combination thereof) that base station 105-a is using to send downlink messages to UE 115a. For example, the multiplexing pattern used by base station 105-a may depend on the bandwidth and SCS configured by base station 105-a. Some wireless communication systems may support different multiplexing patterns based on frequency range (e.g., FR1 supports TDM pattern, FR2 supports TDM, FDM, and hybrid patterns for multiplexing of SSB, CSS set, SIB, or a combination thereof). Depending on the bandwidth, SCS, and frequency band of UE 115-a (e.g., a lightweight NR device or UE 115), the multiplexing pattern may be used to determine the multiplexing pattern of UE 115-a. SSB (e.g., SCS for SSB 215) and SCS Type0-PDCCH (e.g., SCS for Type0-PDCCH or CORESET), different multiplexing patterns (e.g., TDM, FDM, a mixture of TDM and FDM, or a combination thereof) may be configured for lightweight NR communications (e.g., in both FR1 and FR2). To accommodate different multiplexing patterns and repetition-based transmissions for broadcasting downlink messages for lightweight NR communications, a lookup table may be defined and used for the default configuration of CORESET0 and Type0-PDCCH monitoring occasions, where the lookup table may be based on bandwidth, SCS, and the like. SSB and SCS Type0-PDCCH parameterized by the combination of

[0119] Subsequently, based on identifying that the SSB 215 is intended for lightweight NR communication, using the configuration parameters 220 and the multiplexing pattern determination 225, the UE 115-a and the base station 105-a may perform a connection establishment 230 to begin lightweight NR communication. For example, the connection establishment 230 may include a RACH procedure for establishing an RRC connection between the UE 115-a and the base station 105-a. Additionally or alternatively, the connection establishment 230 may include a re-establishment procedure or the like to modify a currently established connection between the UE 115-a and the base station 105-a based on the lightweight NR communication.

[0120] Figure 3A and Figure 3B Examples of RB configuration 300 and SSB configuration 301 for PBCH enhancement supporting lightweight NR communication according to various aspects of the present disclosure are respectively illustrated. In some examples, RB configuration 300 and SSB configuration 301 can implement aspects of wireless communication system 100 and wireless communication system 200. In some cases, UE 115 can use RB configuration 300 and SSB configuration 301 to identify control and synchronization information for connecting to base station 105.

[0121] The RB configuration 300 may include a CRB grid 305 that includes N physical RBs (PRBs) 310 in increasing frequency, ranging from PRB 310-a to the Nth PRB 310-n. The CRB grid 305 may be located at a reference position in the frequency domain such that the base station 105 transmits the CRB grid 305 (e.g., in the PBCH) at the same reference position at any given time. In addition, the RB configuration 300 may include one or more global synchronization channel numbers (GSCNs) 315 ranging from a first GSCN 315-a to a Kth GSCN 315-k. In some cases, each GSCN 315 may correspond to a candidate frequency domain location for the center of an SSB. Due to the different SCSs used by the CRB grid 305 and the SSBs (e.g., indicated by the GSCN 315) and the synchronization (SYNC) raster definition (e.g., the frequency location of the SSBs that can be used by the UE 115 for system acquisition), the PRB index of the SSB may not necessarily align with the PRB index of the CRB grid 305.

[0122] SSB configuration 301 may include one or more SSBs 320 (e.g., as shown, ranging from SSB 320-a to SSB 320-f) that are positioned according to GSCN 315 as described with reference to RB configuration 300. The frequency domain location of SSB 320 relative to CRB grid 305 may be determined by (e.g., the number of PRBs 310 and the number of SSBs 320) and k SSB The sum of the subcarriers is expressed as kSSB Indicated in the PBCH from base station 105. As described above Figure 2 As pointed out in SSB The subcarrier level offset value between the SSB 320 and the CRB grid 305 may be indicated. Since the CRB grid 305 is transmitted at the same reference position, the position of the SSB 320 may be indicated via the offset from the same reference position, enabling the UE 115 to monitor and receive the appropriate SSB 320 from the base station 105.

[0123] SSB subcarrier offset (k SSB ) may enable the UE 115 to perform a process for monitoring the Type0-PDCCH CSS set. In addition, not all SSBs 320 sent by the base station 105 may be cell-defined SSBs (CD-SSBs). For example, SSB 320-b may be a non-cell-defined SSB without CORESET0, while SSB 320-e may be a cell-defined SSB with CORESET0. The UE 115 may select a corresponding SSB 320 based on the k of the corresponding SSB 320. SSB Whether to define SSB k in the cell SSB The valid range of values ​​is used to identify whether SSB 320 is a cell-defined SSB (e.g., as shown in FIG. Figure 2 Thus, as described herein, UE 115 may be configured to receive a k signal based on SSB 320. SSB The value is used to identify whether the SSB 320 is a cell-defined SSB for communication of a different UE category or type (such as lightweight NR).

[0124] Figure 4 An example of a flowchart 400 for PBCH enhancements to support lightweight NR communications in accordance with aspects of the present disclosure is illustrated. In some examples, flowchart 400 can implement aspects of wireless communication system 100 and wireless communication system 200. Flowchart 400 may include a UE process for distinguishing CD-SSBs from non-CD-SSBs. For example, UE 115 may receive one or more SSBs in a PBCH from base station 105, and may determine whether each SSB is a CD-SSB (e.g., to be used for cell acquisition and synchronization to communicate with base station 105) or a non-CD-SSB (e.g., which may be used for reference signal measurements and reporting by UE 115).

[0125] At 405, UE 115 may check the k for SSB indicated in the PBCH. SSB At 410, UE 115 may determine k SSB Is the value within the k defined for CD-SSB? SSBFor example, UE 115 may check k SSB Whether the value satisfies the inequality 0≤k SSB ≤k max,CD-SS , where k max,CD-SS is k defined for CD-SSB SSB The maximum value of the valid range of values.

[0126] At 415, if UE 115 SSB Values ​​(e.g., k SSB Value greater than K max,CD-S ) determines that the SSB is a non-CD-SSB, the UE 115 may search the SYNC raster for the SSB closest to the last checked SSB (e.g., as combined with Figure 3B Subsequently, after finding the closest SSB, UE 115 may then perform k again. SSB The value is checked and the inequality is satisfied to determine whether the closest SSB is a CD-SSB or a non-CD-SSB.

[0127] Additionally or alternatively, at 420, if UE 115 determines based on k falling within the inequality SSB If the value determines that the SSB is a CD-SSB, the UE 115 can extract configuration information (e.g., indicated by the SSB) from the MIB in the PBCH (e.g., pdcch-ConfigSIB1 indication). Subsequently, at 425, the UE 115 can monitor the CSS (e.g., Type 0 CSS set) for downlink control information (DCI) (e.g., scheduling DCI of SIB1) from the base station 105 to obtain further information for establishing or modifying a connection with the base station 105, to receive downlink information from the base station 105, or both.

[0128] Figure 5A and Figure 5B An example of an offset value 500 and a flowchart 501 for PBCH enhancement supporting lightweight NR communication according to various aspects of the present disclosure are respectively illustrated. In some examples, the offset value 500 and the flowchart 501 can implement various aspects of the wireless communication system 100 and the wireless communication system 200.

[0129] As described herein, the base station 105 may configure the offset value 500 for different UE categories or types of communications (such as light NR, eMBB communications, URLLC, etc.). For example, the base station 105 may configure the k value of the light NR SSB Values ​​(such as k SSB,NR-light value) is mapped to the k of CD-SSB used for other types of communication (e.g., eMBB communication, URLLC, etc.) SSBThe ranges of values ​​do not overlap. As shown, k SSB Range 505-a may be configured for CD-SSB of a first type of communication and a set of UE categories (eg, eMBB devices, URLLC devices, etc.). SSB Range 505-b may be configured for CD-SSB for a second type of communication and a set of UE categories (e.g., lightweight NR devices), and k SSB Range 505 - c may be configured for non-CD-SSB for both communication types and UE categories.

[0130] Therefore, for a device operating in the first type of communication and UE category set, k SSB Scope 505-b and k SSB Range 505-c may correspond to non-CD-SSB for a first type of communication and a set of UE categories. Similarly, for devices operating in a second type of communication and a set of UE categories, k SSB Scope 505-a and k SSB Range 505 - c may correspond to non-CD-SSBs for the second type of communication and UE category set. Non-CD-SSBs may be used by the corresponding device for measurements (eg, reference signal measurements and reporting).

[0131] Each k SSB Range 505 may include a maximum value. SSB Range 505-a may include k SSB The value 510-a gives the maximum value (e.g., ). In addition, k SSB Range 505-b may include k SSB The value 510-b gives the maximum value based on k SSB Value 510-a defined (e.g., Where Δ is configured for NR Lite or second type of communication). In some cases, k SSB Range 505-b may include K max The maximum value given.

[0132] k SSB The bit width configuration of the field may have one or more alternatives. For example, the bit width configuration may reuse k SSB The existing design of k value (e.g., for communication systems such as eMBB communication, URLLC, or both). Additionally or alternatively, by adding reserved or unused bits of PBCH, it is possible to use a k value with a larger bit width. SSB The extended field is used to construct the bit width configuration.

[0133] Based on the offset value 500, the UE 115 may be able to SSB Range 505 to distinguish SSBs. For example, UE 115 may use flow chart 501 to determine whether an SSB is a CD-SSB or a non-CD-SSB for a communication type or UE category of which UE 115 is a part.

[0134] If the UE 115 operates in accordance with the first type of communication or the first set of UE categories as described herein, the UE 115 may determine whether the SSB corresponds to k SSB k in range 505-a SSB At 515, the UE 115 may check the k value of the SSB indicated in the PBCH. SSB At 520, UE 115 may then determine k for the SSB. SSB Is the value within the CD-SSB range for the first type of communication or the first UE category set (e.g., k SSB Range 505-a).

[0135] At 525, if UE 115 falls within k SSB Outside range 505-a (e.g., within k SSB Range 505-b or k SSB k in range 505-c) SSB If the SSB is determined to be a non-CD-SSB for a first type of communication or a first UE category set, the UE 115 may search for an SSB on the SYNC raster that is closest to the last checked SSB (e.g., as combined with Figure 3B and Figure 4 Subsequently, after finding the closest SSB, UE 115 may perform k again. SSB The value check and inequality satisfaction determination are performed to determine whether the closest SSB is a CD-SSB or a non-CD-SSB for the first type of communication or the first UE category set.

[0136] Additionally or alternatively, at 530, if UE 115 receives a request based on falling into k SSB k in range 505-a SSBIf the value determines that the SSB is a CD-SSB for a first type of communication or a first UE category set, the UE 115 can extract configuration information (e.g., indicated by the SSB) from the MIB in the PBCH (e.g., pdcch-ConfigSIB1 indication). Subsequently, at 535, the UE 115 can monitor the CSS (e.g., Type0 CSS set) for downlink control information (DCI) (e.g., scheduling DCI of SIB1) from the base station 105 to obtain further information for establishing or modifying a connection with the base station 105, to receive downlink information from the base station 105, or both.

[0137] If the UE 115 operates according to the second type of communication or second UE category as described herein (e.g., lightweight NR communication), the UE 115 may perform similar steps in flowchart 501. However, when determining the k of the SSB SSB Is the value 510 in k for the second type of communication or the second UE category? SSB When the UE 115 is within the range 505 to identify whether the SSB is a CD-SSB or a non-CD-SSB, the UE 115 may check k SSB is in k SSB Range 505-b (e.g., CD-SSB) or k SSB Outside range 505-b (e.g., within k SSB Range 505-a or k SSB range 505-c, indicating non-CD-SSB). Subsequently, UE 115 may perform corresponding operations of flowchart 501 based on the determination of CD-SSB and non-CD-SSB.

[0138] Figure 6 An example of an offset value 600 for PBCH enhancement supporting lightweight NR communication according to aspects of the present disclosure is illustrated. In some examples, the offset value 600 can implement aspects of the wireless communication system 100 and the wireless communication system 200. As described herein, the base station 105 can configure the offset value 600 for different UE categories or types of communication (such as lightweight NR, eMBB communication, URLLC, etc.). In some examples, the base station 105 can configure different k values ​​for different types of communication or UE categories in an overlapping manner. SSB Value and range.

[0139] The offset value 600 may be based on the provision of a reserved bit in the MIB or the PHY payload of the PBCH to distinguish between PBCH types. For example, the base station 105 may set the k for the second type of communication or the second UE category (e.g., lightweight NR) to SSB The value is mapped to k for a first type of communication or a first set of UE categories (eg, eMBB communication, URLLC, etc.).SSB In some cases, the base station 105 may use reserved or unused bits of the PBCH to indicate whether the PBCH is for a second type of communication or a second UE category (eg, NR Lite).

[0140] UEs 115 operating according to the first type of communication or the first set of UE categories may bypass the range from 0 to k. SSB 610-a (for example, ranging from 0≤K max ≤k SSB , where K nax and k SSB K is configured based on the first type of communication or the first UE category set max Additionally or alternatively, the UE 115 operating according to the second type of communication or the second UE category may process the reserved bit to indicate the PBCH type for the second type of communication or the second UE category. The UE 115 operating according to the second type of communication or the second UE category may process the reserved bit in k SSB Value 605-b (which ranges from 0 to K max 610-b (for example, in the range of 0≤k SS ≤K max , where k SSB and K max This type of indication can be considered as a k for different types of communications or UE categories by the base station 105. SSB An explicit indication of the values ​​may enable the base station 105 to use the same set of overlapping values ​​for each type of communication or UE category.

[0141] Figure 7 An example of an information field decision tree 700 for PBCH enhancement supporting lightweight NR communication according to aspects of the present disclosure is illustrated. In some examples, the information field decision tree 700 can implement aspects of the wireless communication system 100 and the wireless communication system 200. Figure 2 As described, when establishing or modifying communications between the base station 105 and the UE 115, the base station 105 may indicate different UE capabilities for lightweight NR communications via one or more configuration parameters.

[0142] For example, the base station 105 can add information elements and fields to the PBCH to support coverage enhancement for broadcasting different downlink messages (e.g., PDCCH, PDSCH, DMRS, etc.) to the UE 115. In some wireless communication systems, the CORESET0 resource configuration and the Type0-PDCCH CSS set configuration can be given by the information element "pdcch-ConfigSIB1". However, this information element may not support PDCCH repetition and frequency hopping. In addition, the default PDSCH time domain resource allocation (TDRA) table can be used to broadcast PDSCH, such as SIB and random access response (RAR) messages, which may limit the support of PDCCH, PDSCH or DMRS repetition due to K0=0 of the TDRA table (e.g., no delay between repetitions).

[0143] To alleviate these issues, the base station 105 may add fields, information elements, or both to the PBCH to support intra-slot or inter-slot repetition and intra-slot or inter-slot frequency hopping for broadcasting PDCCH, PDSCH, DMRS, or a combination thereof. For example, the base station 105 may add a style repetition field (e.g., via one (1) bit) to indicate whether intra-slot repetition of the PDCCH or PDSCH is enabled (e.g., "0") or inter-slot repetition of the PDCCH or PDSCH is enabled (e.g., "1"). Additionally or alternatively, the base station 105 may add a level repetition field (e.g., one (1) or two (2) bits) to indicate mapping to a repetition level (2, 4, 8, etc.) for coverage enhancement.

[0144] The base station 105 may map these added fields to a subset of unused, reserved, or reused information bits carried by the PBCH, including the MIB TB, the PHY payload of the PBCH, the DMRS scrambling ID of the PBCH, or a combination thereof. For example, two reserved bits in the PHY payload of FR1 may be used for the added fields; repeated bits of the half-frame indication in the PHY payload or the DMRS scrambling ID may be used for the added fields; reused fields or bits in the MIB of the PBCH as a result of the bit width reduction of "SFN", "dmrs-TypeA-Position", "pdcch-ConfigSIB1", or a combination thereof may be used for the added fields; or, idle bits in the MIB may be used for the added fields.

[0145] The information field decision tree 700 may illustrate which unused, reserved, or reused information bits carried by the PBCH are to be used to carry the added fields. For example, at 705, the base station 105 may identify an MSI that is common to both the UE capabilities of a first type of communication or a first UE category (e.g., eMBB communication or URLLC) and a second type of communication or a second UE category (e.g., lightweight NR communication). In addition, at 710, the base station 105 may identify system information unique to the UE capabilities of the first type of communication or the first UE category (e.g., legacy system information for legacy UE capabilities). At 715, the base station 105 may identify system information unique to the second type of communication or the second UE category (e.g., new system information for new UE capabilities).

[0146] At 720, based on identifying the common MSI for both types of communications or UE categories, the base station 105 may keep the corresponding field in the PBCH unchanged for sending the common MSI. At 725, based on identifying the system information unique to the first type of communications or the first UE category, the base station 105 may delete or reuse the corresponding field in the PBCH to free up bits for carrying the added field. At 730, based on identifying the system information unique to the second type of communications or the second UE category, the base station 105 may reuse the field in the PBCH or the reserved bits to carry the added field.

[0147] Subsequently, at 735, the base station 105 may determine a PBCH for carrying the added field for the second type of communication or UE capabilities of the second UE category. For example, based on the reused, reserved, or unchanged fields identified in 720 and 730, the base station 105 may send a PBCH carrying the added field (e.g., repeated within or between slots, frequency hopped within or between slots, or both, for broadcasting PDCCH, PDSCH, or DMRS).

[0148] Fig. 8A and Figure 8B Examples of TDM patterns 800 and 801 for PBCH enhancements supporting lightweight NR communications according to aspects of the present disclosure are illustrated. In some examples, TDM patterns 800 and 801 can implement aspects of wireless communication systems 100 and 200. As shown in FIG. Figure 2 As described, UE 115 may determine a multiplexing pattern, and base station 105 may use the multiplexing pattern to send a downlink message (e.g., PBCH, SSB, CSS set in PBCH, SIB1 in PBCH, or a combination thereof) to UE 115 as part of a lightweight NR communication (e.g., a second type of communication or a second UE category as described herein). For example, UE 115 may determine a multiplexing pattern based on the bandwidth, SCS, and / orSSB (e.g., SCS for SSB) and SCS Type0-PDCCH The multiplexing pattern of the downlink message is determined by the SCS (eg, for Type0-PDCCH or CORESET) (eg, configured by the base station 105 for the UE 115). The TDM patterns 800 and 801 may represent examples of multiplexing patterns determined by the UE 115.

[0149] TDM patterns 800 and 801 may support same or cross-slot scheduling (e.g., K0 ≥ 0). For TDM pattern 800, base station 105 may initially transmit PSS and SSS 805 and PBCH 810. Subsequently, base station 105 may transmit one or more PDCCH CSS sets 815 after the PSS and SSS 805 and PBCH 810 transmission. PDCCH CSS set 815 may indicate where UE 115 will monitor and receive SIB1 820 from base station 105.

[0150] Additionally or alternatively, for TDM pattern 801, the base station 105 can send a PDCCH CSS set 815 prior to the transmission of the PSS and SSS 805 and the PBCH 810, wherein the PDCCH CSS set includes an indication of the SIB1 820 transmission that occurs after the transmission of the PSS and SSS 805 and the PBCH 810. Based on TDM patterns 800 and 801, the base station 105 can send different downlink messages across time without overlapping the downlink messages in frequency. The UE 115 can determine which TDM pattern or another type of multiplexing pattern to use based on a lookup table that is based on bandwidth, SCS, and the like. SSB and SCS Type0-PDCCH The combination of parameters is as follows: Figure 2 As described.

[0151] Fig. 9 An example of an FDM pattern 900 for PBCH enhancement supporting lightweight NR communication according to aspects of the present disclosure is illustrated. In some examples, the FDM pattern 900 can implement aspects of the wireless communication system 100 and the wireless communication system 200. As shown in FIG. Figure 2 As described, UE 115 may determine a multiplexing pattern, and base station 105 may use the multiplexing pattern to send a downlink message (e.g., PBCH, SSB, CSS set in PBCH, SIB1 in PBCH, or a combination thereof) to UE 115 as part of a lightweight NR communication (e.g., a second type of communication or a second UE category as described herein). For example, UE 115 may determine a multiplexing pattern based on the bandwidth, SCS, and / or the UE 115's bandwidth. SSB (e.g., SCS for SSB) and SCS Type0-PDCCHThe multiplexing pattern of the downlink message is determined by the SCS (eg, for Type0-PDCCH or CORESET) (eg, configured by the base station 105 for the UE 115). The FDM pattern 900 may represent an example of a multiplexing pattern determined by the UE 115.

[0152] The FDM pattern 900 may support same or cross-slot scheduling (e.g., K0 ≥ 0). For the FDM pattern 900, the base station 105 may send PSS and SSS 905 and PBCH 910 that overlap in time with one or more PDCCH CSS sets 915 (e.g., sent at the same time but on different frequencies). The PDCCH CSS set 915 may then indicate where the UE 115 will monitor and receive SIB1 920 from the base station 105 after the PDCCH CSS set 915. Based on the FDM pattern 900, the base station 105 may send different downlink messages at the same time across different frequencies. The UE 115 may determine to use the FDM pattern or another type of multiplexing pattern based on a lookup table that is based on bandwidth, SCS, and the like. SSB and SCS Type0-PDCCH The combination of parameters is as follows: Figure 2 As described.

[0153] Fig. 10A and Fig. 10B Examples of hybrid multiplexing patterns 1000 and 1001 for PBCH enhancement supporting lightweight NR communication according to aspects of the present disclosure are illustrated. In some examples, hybrid multiplexing patterns 1000 and 1001 can implement aspects of wireless communication systems 100 and 200. As shown in reference Figure 2 As described, UE 115 may determine a multiplexing pattern, and base station 105 may use the multiplexing pattern to send a downlink message (e.g., PBCH, SSB, CSS set in PBCH, SIB1 in PBCH, or a combination thereof) to UE 115 as part of a lightweight NR communication (e.g., a second type of communication or a second UE category as described herein). For example, UE 115 may determine a multiplexing pattern based on the bandwidth, SCS, and / or the UE 115's bandwidth. SSB (e.g., SCS for SSB) and SCS Type0-PDCCH The multiplexing pattern of the downlink message is determined by the base station 105 (eg, SCS for Type0-PDCCH or CORESET) (eg, configured by the base station 105 for the UE 115). The hybrid multiplexing patterns 1000 and 1001 may represent examples of multiplexing patterns determined by the UE 115.

[0154] Hybrid multiplexing patterns 1000 and 1001 can support the same or cross-slot scheduling (e.g., K0≥0). In addition, hybrid multiplexing patterns 1000 and 1001 can implement aspects of both TDM patterns and FDM patterns. For hybrid multiplexing pattern 1000, base station 105 can send PSS and SSS 1005 and PBCH 1010 that overlap in time with one or more PDCCH CSS sets 1015-a. Subsequently, base station 105 can also send one or more PDCCH CSS sets 1015-b after transmission of PSS and SSS 1005, PBCH 1010, and PDCCH CSS set 1015-a. PDCCH CSS set 1015-a and PDCCH CSS set 1015-b can indicate where UE 115 is to monitor and receive SIB1 1020 from base station 105. In some cases, SIB1 1020 may be sent or received after the second PDCCH CSS set 1015 - b is transmitted.

[0155] Additionally or alternatively, for hybrid multiplexing pattern 1001, base station 105 may transmit PSS and SSS 1005 and PBCH 1010 that overlap in time with one or more PDCCH CSS sets 1015-a, and may transmit one or more PDCCH CSS sets 1015-b after the transmission of PSS and SSS 1005, PBCH 1010, and PDCCH CSS set 1015-a. However, PDCCH CSS set 1015 may indicate that SIB1 1020 transmission occurs at the same time as PDCCH CSS set 1015-b transmission. Therefore, based on hybrid multiplexing patterns 1000 and 1001, base station 105 may transmit different downlink messages across time without overlapping the downlink messages in frequency, or may transmit different downlink messages at the same time across different frequencies. UE 115 may determine which hybrid pattern or another type of multiplexing pattern to use based on a lookup table that is based on bandwidth, SCS, and frequency. SSB and SCS Type0-PDCCH The combination of parameters is as follows: Figure 2 As described.

[0156] Fig.11 An example of a process flow 1100 for supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is illustrated. In some examples, the process flow 1100 can implement aspects of the wireless communication system 100 and the wireless communication system 200. The process flow 1100 can include a base station 105-b and a UE 115-b, which can be respectively as described in reference Figure 1 to Figure 1 0 describes an example of a corresponding base station 105 and a UE 115.

[0157] In the following description of process flow 1100, operations between UE 115-b and base station 105-b may be sent in an order different from the exemplary order shown, or operations performed by UE 115-b and base station 105-b may be performed in a different order or at a different time. One or more operations may also be excluded from process flow 1100, or other operations may be added to process flow 1100. It should be understood that although UE 115-b and base station 105-b are shown as performing multiple operations of process flow 1100, any wireless device may perform the operations shown.

[0158] At 1105, UE 115-b may receive an SSB that includes an indication of a UE category (e.g., lightweight NR communications) supported by the SSB, where the UE category is based on a UE bandwidth. In some examples, the UE bandwidth may be a channel bandwidth supported by UE 115-b.

[0159] At 1110, UE 115-b may receive an indication of a subcarrier offset between the SSB and CRB grids (e.g., k SSB In some cases, UE 115-b may receive one or more bits that explicitly indicate the UE categories supported by SSB (e.g., as shown in FIG. Figure 6 described).

[0160] Additionally or alternatively, the indication of the UE category supported by the SSB may be based on a range within which the subcarrier offset falls (e.g., as described with reference to FIG. 5 ). In some cases, the indication of the subcarrier offset may be based on a combination of a first set of one or more bits in a first field of the SSB and a second set of one or more bits in a second field of the SSB. Thus, UE 115-b may determine a valid range of subcarrier offsets based on the UE category supported by the SSB, wherein a connection between UE 115-b and base station 105-b is established or modified based on a subcarrier offset in the SSB that falls within the valid range.

[0161] At 1115, UE 115-b may receive repeated information (e.g., as described in reference to FIG. 1 ) of a broadcast channel (e.g., PBCH) from base station 105-b. Figure 7The repetition information may include an indication of support for intra-slot repetition on the broadcast channel, an indication of support for inter-slot repetition on the broadcast channel, or a combination thereof. Additionally or alternatively, the repetition information may include an indication of a number of transmission repetitions configured for the broadcast channel. In some cases, the repetition information may be received in a MIB, a PHY payload of the broadcast channel, a DMRS scrambling identifier of the broadcast channel, or any combination thereof.

[0162] Additionally or alternatively, UE 115-b may receive frequency hopping information of a broadcast channel (e.g., PBCH) from base station 105b (e.g., as described in reference Figure 7 The method of claim 1 , wherein the frequency hopping information is based on a UE category supported by the SSB. In some cases, the frequency hopping information may include an indication of support for intra-slot frequency hopping on the broadcast channel, an indication of support for inter-slot frequency hopping on the broadcast channel, or a combination thereof. Additionally, the frequency hopping information may be received in a MIB, a PHY payload of a broadcast channel, a DMRS scrambling identifier of a broadcast channel, or any combination thereof.

[0163] At 1120, UE 115-b may determine, based on the indication, that UE 115-b belongs to a UE category supported by SSB. In some examples, UE 115-b may send capability information indicating the UE category to base station 105-b.

[0164] At 1125, UE 115-b may determine a multiplexing pattern for the SSB based on the UE category supported by the SSB (e.g., as described above with reference to FIGS. 8 to 10 ), the CORESET for broadcast control information, and the SIB (e.g., SIB1). In some cases, UE 115-b may map the multiplexing pattern to the UE bandwidth, the SCS associated with the SSB (e.g., SCS SSB), and the SCS for broadcast control information of the CORESET (e.g., SCS Type0-PDCCH ) combination.

[0165] At 1130, based on the determination that UE 115-b belongs to a category of UEs supported by SSB, UE 115-b and base station 105-b may establish or modify a connection between each other using SSB.

[0166] Fig.12A block diagram 1200 of a device 1205 supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is illustrated. The device 1205 may be an example of aspects of the UE 115 as described herein. The device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0167] The receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to PBCH enhancements for lightweight NR communications, or a combination thereof). The information may be delivered to other components of the device 1205. The receiver 1210 may be a reference Fig.15 Examples of various aspects of the transceiver 1520 are described. The receiver 1210 may utilize a single antenna or a collection of antennas.

[0168] The communication manager 1215 may: receive an SSB at a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determine, based on the indication, that the UE belongs to a UE category supported by the SSB; and establish or modify a connection between the UE and a base station using the SSB based on the determination. The communication manager 1215 may be an example of aspects of the communication manager 1510 described herein.

[0169] The communication manager 1215 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1215 or its subcomponents may be performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device designed to perform the functions described in the present disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0170] The communication manager 1215 or its subcomponents can be physically located in a variety of locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, the communication manager 1215 or its subcomponents can be independent and distinct components according to various aspects of the present disclosure. In some examples, according to various aspects of the present disclosure, the communication manager 1215 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0171] Transmitter 1220 can transmit signals generated by other components of device 1205. In some examples, transmitter 1220 can be co-located with receiver 1210 in a transceiver module. For example, transmitter 1220 can be a reference Fig.15 Examples of various aspects of the transceiver 1520 are described. The transmitter 1220 may utilize a single antenna or a collection of antennas.

[0172] Fig.13 A block diagram 1300 of a device 1305 supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is illustrated. The device 1305 may be an example of aspects of the device 1205 or UE 115 as described herein. The device 1305 may include a receiver 1310, a communication manager 1315, and a transmitter 1335. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0173] The receiver 1310 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to PBCH enhancements for lightweight NR communications, or a combination thereof). The information may be delivered to other components of the device 1305. The receiver 1310 may be a reference Fig.15 Examples of various aspects of the transceiver 1520 are described. The receiver 1310 may utilize a single antenna or a collection of antennas.

[0174] The communication manager 1315 may be an example of aspects of the communication manager 1215 as described herein. The communication manager 1315 may include an SSB receiver 1320, a UE category determination component 1325, and a connection component 1330. The communication manager 1315 may be an example of aspects of the communication manager 1510 described herein.

[0175] The SSB receiver 1320 can receive an SSB at the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The UE category determination component 1325 can determine, based on the indication, that the UE belongs to a UE category supported by the SSB. The connection component 1330 can establish or modify a connection between the UE and a base station based on the determination to use the SSB. The transmitter 1335 can transmit signals generated by other components of the device 1305. In some examples, the transmitter 1335 can be co-located with the receiver 1310 in a transceiver module. For example, the transmitter 1335 can be a reference Fig.15 Examples of various aspects of the transceiver 1520 are described. The transmitter 1335 can utilize a single antenna or a collection of antennas.

[0176] Fig.14A block diagram 1400 of a communication manager 1405 supporting PBCH enhancement for lightweight NR communication in accordance with aspects of the present disclosure is illustrated. The communication manager 1405 may be an example of aspects of the communication manager 1215, the communication manager 1315, or the communication manager 1510 described herein. The communication manager 1405 may include an SSB receiver 1410, a UE category determination component 1415, a connection component 1420, a subcarrier offset component 1425, a repetition capability component 1430, a frequency hopping capability component 1435, and a multiplexing determination component 1440. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0177] The SSB receiver 1410 may receive an SSB at a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth. The UE category determination component 1415 may determine, based on the indication, that the UE belongs to a UE category supported by the SSB. In some examples, the UE category determination component 1415 may receive one or more bits that explicitly indicate a UE category supported by the SSB.

[0178] The connection component 1420 can establish or modify a connection between the UE and the base station based on determining to use the SSB. The subcarrier offset component 1425 can receive an indication of a subcarrier offset between the SSB and the CRB grid, wherein establishing or modifying the connection between the UE and the base station is based on the subcarrier offset. In some examples, the subcarrier offset component 1425 can determine a valid range of the subcarrier offset based on a UE category supported by the SSB, wherein establishing or modifying the connection between the UE and the base station is further based on a subcarrier offset in the SSB that falls within the valid range.

[0179] In some cases, the indication of the UE category supported by the SSB is based on a range that the subcarrier offset falls within. In some cases, the indication of the subcarrier offset is based on a combination of a first set of one or more bits in a first field of the SSB and a second set of one or more bits in a second field of the SSB.

[0180] The repetition capability component 1430 can receive repetition information for a broadcast channel from a base station, wherein the repetition information is based on a UE category supported by the SSB. The repetition information can include an indication of support for intra-slot repetition on the broadcast channel, an indication of support for inter-slot repetition on the broadcast channel, or a combination thereof. In some cases, the repetition information includes an indication of the number of transmission repetitions configured for the broadcast channel. In some cases, the repetition information is received in one or more of the MIB, the physical layer payload of the broadcast channel, the DMRS scrambling identifier of the broadcast channel, or any combination thereof.

[0181] The frequency hopping capability component 1435 can receive frequency hopping information for a broadcast channel from a base station, wherein the frequency hopping information is based on a UE category supported by the SSB. In some cases, the frequency hopping information can include an indication of support for intra-slot frequency hopping on the broadcast channel, an indication of support for inter-slot frequency hopping on the broadcast channel, or a combination thereof. In some cases, the frequency hopping information is received in one or more of a MIB, a physical layer payload of a broadcast channel, a DMRS scrambling identifier of a broadcast channel, or any combination thereof.

[0182] The multiplexing determination component 1440 can determine a multiplexing pattern for the SSB, a control resource set for broadcast control information, and a system information block based on the UE category supported by the SSB. In some examples, the multiplexing determination component 1440 can map the multiplexing pattern to a combination of the UE bandwidth, the subcarrier spacing associated with the SSB, and the subcarrier spacing of the broadcast control information of the control resource set. In some examples, the base station can receive capability information indicating the UE category from the UE.

[0183] Fig.15 A schematic diagram of a system 1500 including a device 1505 for PBCH enhancement supporting lightweight NR communications according to aspects of the present disclosure is shown. The device 1505 may be an example of or include components of a device 1205, a device 1305, or a UE 115 as described herein. The device 1505 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 1510, an I / O controller 1515, a transceiver 1520, an antenna 1525, a memory 1530, and a processor 1540. These components may be in electronic communication via one or more buses (e.g., a bus 1545).

[0184] The communication manager 1510 may: receive an SSB at a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determine based on the indication that the UE belongs to the UE category supported by the SSB; and establish or modify a connection between the UE and a base station based on the determination to use the SSB.

[0185] I / O controller 1515 can manage input and output signals for device 1505. I / O controller 1515 can also manage peripheral devices that are not integrated into device 1505. In some cases, I / O controller 1515 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1515 can utilize a computer such as a Or other known operating systems. In other cases, I / O controller 1515 can represent or interact with a modem, keyboard, mouse, touch screen or similar device. In some cases, I / O controller 1515 can be implemented as a part of a processor. In some cases, a user can interact with device 1505 via I / O controller 1515 or via hardware components controlled by I / O controller 1515.

[0186] The transceiver 1520 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1520 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1520 can also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0187] In some cases, a wireless device may include a single antenna 1525. However, in some cases, the device may have more than one antenna 1525, which may be capable of sending or receiving multiple wireless transmissions simultaneously.

[0188] Memory 1530 may include random access memory (RAM) and read-only memory (ROM). Memory 1530 may store computer-readable, computer-executable code 1535 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1530 may additionally contain a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0189] Processor 1540 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1540 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause device 1505 to perform various functions (e.g., functions or tasks to support PBCH enhancements for lightweight NR communications).

[0190] The code 1535 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1535 may be stored in a non-transitory computer-readable medium such as a system memory or other type of memory. In some cases, the code 1535 may not be directly executed by the processor 1540, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0191] Fig.16 A block diagram 1600 of a device 1605 supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is shown. The device 1605 may be an example of aspects of the base station 105 as described herein. The device 1605 may include a receiver 1610, a communication manager 1615, and a transmitter 1620. The device 1605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0192] The receiver 1610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to PBCH enhancements for lightweight NR communications, or a combination thereof). The information may be delivered to other components of the device 1605. The receiver 1610 may be a reference Fig.19 Examples of various aspects of the transceiver 1920 are described. The receiver 1610 may utilize a single antenna or a collection of antennas.

[0193] The communication manager 1615 may: send an SSB to the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth; determine that the UE belongs to the UE category supported by the SSB; and establish or modify a connection between the UE and a base station using the SSB based on the determination. The communication manager 1615 may be an example of aspects of the communication manager 1910 described herein.

[0194] The communication manager 1615 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1615 or its subcomponents may be performed by a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device designed to perform the functions described in the present disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0195] The communication manager 1615 or its subcomponents can be physically located in a variety of locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, the communication manager 1615 or its subcomponents can be independent and distinct components according to various aspects of the present disclosure. In some examples, according to various aspects of the present disclosure, the communication manager 1615 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0196] Transmitter 1620 can transmit signals generated by other components of device 1605. In some examples, transmitter 1620 can be co-located with receiver 1610 in a transceiver module. For example, transmitter 1620 can be a reference Fig.19 Examples of various aspects of the transceiver 1920 are described. The transmitter 1620 may utilize a single antenna or a collection of antennas.

[0197] Fig.17 A block diagram 1700 of a device 1705 supporting PBCH enhancement for lightweight NR communications according to aspects of the present disclosure is shown. The device 1705 may be an example of aspects of the device 1605 or base station 105 as described herein. The device 1705 may include a receiver 1710, a communication manager 1715, and a transmitter 1735. The device 1705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0198] The receiver 1710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to PBCH enhancements for lightweight NR communications, or a combination thereof). The information may be delivered to other components of the device 1705. The receiver 1710 may be a reference Fig.19 Examples of various aspects of the transceiver 1920 are described. The receiver 1710 may utilize a single antenna or a collection of antennas.

[0199] The communication manager 1715 may be an example of aspects of the communication manager 1615 as described herein. The communication manager 1715 may include an SSB transmitter 1720, a UE classification component 1725, and a connection establishment / modification component 1730. The communication manager 1715 may be an example of aspects of the communication manager 1910 described herein.

[0200] SSB transmitter 1720 can send an SSB to the UE, the SSB including an indication of a UE category supported by the SSB, where the UE category is based on the UE bandwidth. UE category component 1725 can determine that the UE belongs to a UE category supported by the SSB. Connection establishment or modification component 1730 can establish or modify a connection between the UE and a base station based on the determination to use the SSB. Transmitter 1735 can transmit signals generated by other components of device 1705. In some examples, transmitter 1735 can be co-located with receiver 1710 in a transceiver module. For example, transmitter 1735 can be a reference Fig.19 Examples of various aspects of the transceiver 1920 are described. The transmitter 1735 can utilize a single antenna or a collection of antennas.

[0201] Fig.18 A block diagram 1800 of a communication manager 1805 supporting PBCH enhancement for lightweight NR communications in accordance with aspects of the present disclosure is shown. The communication manager 1805 may be an example of aspects of the communication manager 1615, the communication manager 1715, or the communication manager 1910 described herein. The communication manager 1805 may include an SSB transmitter 1810, a UE category component 1815, a connection establishment / modification component 1820, a subcarrier offset indicator 1825, a repetition capability transmitter 1830, a frequency hopping capability transmitter 1835, and a multiplexing pattern determination component 1840. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0202] The SSB transmitter 1810 may send an SSB to the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The UE category component 1815 may determine that the UE belongs to a UE category supported by the SSB. In some examples, the UE category component 1815 may send one or more bits that explicitly indicate the UE category supported by the SSB.

[0203] The connection establishing or modifying component 1820 can establish or modify the connection between the UE and the base station based on the determination to use the SSB.

[0204] The subcarrier offset indicator 1825 may send an indication of a subcarrier offset between an SSB and a CRB grid, wherein establishing or modifying a connection between a UE and a base station is based on the subcarrier offset. In some examples, the subcarrier offset indicator 1825 may determine a valid range of the subcarrier offset based on a UE category supported by the SSB, wherein establishing or modifying a connection between the UE and the base station is further based on a subcarrier offset in the SSB that falls within the valid range. In some cases, the indication of the UE category supported by the SSB is based on the range within which the subcarrier offset falls. In some cases, the indication of the subcarrier offset is based on a combination of a first set of one or more bits in a first field of the SSB and a second set of one or more bits in a second field of the SSB.

[0205] The repetition capability transmitter 1830 may send repetition information for receiving a broadcast channel to the UE, wherein the repetition information is based on the UE category supported by the SSB. In some cases, the repetition information includes an indication of support for intra-slot repetition on the broadcast channel, an indication of support for inter-slot repetition on the broadcast channel, or a combination thereof. In some cases, the repetition information includes an indication of the number of transmission repetitions configured for the broadcast channel. In some cases, the repetition information is received in one or more of the MIB, the physical layer payload of the broadcast channel, the DMRS scrambling identifier of the broadcast channel, or any combination thereof.

[0206] The frequency hopping capability transmitter 1835 may send frequency hopping information for a broadcast channel to the UE, wherein the frequency hopping information is based on the UE category supported by the SSB. In some cases, the frequency hopping information may include an indication of support for intra-slot frequency hopping on the broadcast channel, an indication of support for inter-slot frequency hopping on the broadcast channel, or a combination thereof. In some cases, the frequency hopping information is received in one or more of the MIB, the physical layer payload of the broadcast channel, the DMRS scrambling identifier of the broadcast channel, or any combination thereof.

[0207] The multiplexing pattern determining component 1840 can determine the multiplexing pattern of the SSB, the control resource set for broadcast control information, and the system information block based on the UE category supported by the SSB. In some examples, the multiplexing pattern determining component 1840 can map the multiplexing pattern to a combination of the UE bandwidth, the subcarrier spacing associated with the SSB, and the subcarrier spacing of the control resource set for broadcast control information.

[0208] Fig.19A schematic diagram of a system 1900 including a device 1905 for PBCH enhancement supporting lightweight NR communications according to various aspects of the present disclosure is shown. The device 1905 may be an example of or include components of a device 1605, a device 1705, or a base station 105 as described herein. The device 1905 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 1910, a network communication manager 1915, a transceiver 1920, an antenna 1925, a memory 1930, a processor 1940, and an inter-station communication manager 1945. These components may be in electronic communication via one or more buses (e.g., a bus 1950).

[0209] The communication manager 1910 may: send an SSB to a UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on a UE bandwidth; determine that the UE belongs to a UE category supported by the SSB; and establish or modify a connection between the UE and a base station based on the determination using the SSB.

[0210] The network communications manager 1915 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1915 may manage data communications transmissions for client devices such as one or more UEs 115.

[0211] The transceiver 1920 may communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1920 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1920 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0212] In some cases, a wireless device may include a single antenna 1925. However, in some cases, the device may have more than one antenna 1925, which may be capable of sending or receiving multiple wireless transmissions simultaneously.

[0213] Memory 1930 may include RAM, ROM, or a combination thereof. Memory 1930 may store computer readable code 1935 including instructions that, when executed by a processor (e.g., processor 1940), cause the device to perform various functions described herein. In some cases, memory 1930 may additionally include BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0214] Processor 1940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1940. Processor 1940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1930) to cause device 1905 to perform various functions (e.g., functions or tasks to support PBCH enhancements for lightweight NR communications).

[0215] The inter-site communication manager 1945 may manage communications with other base stations 105 and may include a controller or scheduler to control communications with the UE 115 in cooperation with the other base stations 105. For example, the inter-site communication manager 1945 may coordinate the scheduling of transmissions to the UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-site communication manager 1945 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between base stations 105.

[0216] The code 1935 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1935 may be stored in a non-transitory computer-readable medium such as a system memory or other type of memory. In some cases, the code 1935 may not be directly executed by the processor 1940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0217] Fig. 20 A flow chart illustrating a method 2000 for PBCH enhancement to support lightweight NR communications according to aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a UE 115 or a component thereof as described herein. Figures 12 to 15 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0218] At 2005, the UE may receive an SSB at the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The operations of 2005 may be performed according to the methods described herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Figures 12 to 15 The described SSB receiver is implemented.

[0219] At 2010, the UE may determine, based on the indication, that the UE belongs to a UE category supported by SSB. The operations of 2010 may be performed according to the methods described herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Figures 12 to 15 The described UE category determination component performs.

[0220] At 2015, the UE may establish or modify a connection between the UE and the base station based on the determination to use the SSB. The operations of 2015 may be performed according to the methods described herein. In some examples, various aspects of the operations of 2015 may be performed as described in reference to Figures 12 to 15 The described connected components are implemented.

[0221] Fig.21 A flow chart illustrating a method 2100 for PBCH enhancement for supporting lightweight NR communications according to aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a UE 115 or a component thereof as described herein. Figures 12 to 15 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0222] At 2105, the UE may receive an SSB at the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The operations of 2105 may be performed according to the methods described herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Figures 12 to 15 The described SSB receiver is implemented.

[0223] At 2110, the UE may receive an indication of a subcarrier offset between an SSB and a CRB grid. The operations of 2110 may be performed according to the methods described herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Figures 12 to 15 The subcarrier offset component described is performed.

[0224] At 2115, the UE may determine, based on the indication, that the UE belongs to a category of UEs supported by SSB. The operations of 2115 may be performed according to the methods described herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Figures 12 to 15 The described UE category determination component performs.

[0225] At 2120, the UE may establish or modify a connection between the UE and the base station using the SSB based on the determination and the subcarrier offset. The operations of 2120 may be performed according to the methods described herein. In some examples, aspects of the operations of 2120 may be performed as described in reference to Figures 12 to 15 The described connected components are implemented.

[0226] Fig. 22 A flow chart illustrating a method 2200 for PBCH enhancement to support lightweight NR communications according to aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 2200 may be implemented by a UE 115 or a component thereof as described herein. Figures 12 to 15 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0227] At 2205, the UE may receive an SSB at the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The operations of 2205 may be performed according to the methods described herein. In some examples, aspects of the operations of 2205 may be performed as described in reference to Figures 12 to 15 The described SSB receiver is implemented.

[0228] At 2210, the UE may determine, based on the indication, that the UE belongs to a category of UEs supported by SSB. The operations of 2210 may be performed according to the methods described herein. In some examples, aspects of the operations of 2210 may be performed as described in reference to Figures 12 to 15 The described UE category determination component performs.

[0229] At 2215, the UE may receive repetition information of a broadcast channel from the base station, wherein the repetition information is based on a UE category supported by the SSB. The operations of 2215 may be performed according to the methods described herein. In some examples, aspects of the operations of 2215 may be performed as described in reference to Figures 12 to 15 The described repetitive competency components are performed.

[0230] At 2220, the UE may establish or modify a connection between the UE and the base station based on the determination to use the SSB. The operations of 2220 may be performed according to the methods described herein. In some examples, aspects of the operations of 2220 may be performed as described in reference to Figures 12 to 15 The described connected components are implemented.

[0231] Fig.23A flow chart illustrating a method 2300 for PBCH enhancement to support lightweight NR communications according to aspects of the present disclosure is shown. The operations of the method 2300 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 2300 may be implemented by a UE 115 or a component thereof as described herein. Figures 12 to 15 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0232] At 2305, the UE may receive an SSB at the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The operations of 2305 may be performed according to the methods described herein. In some examples, aspects of the operations of 2305 may be performed as described in reference to Figures 12 to 15 The described SSB receiver is implemented.

[0233] At 2310, the UE may determine, based on the indication, that the UE belongs to a category of UEs supported by SSB. The operations of 2310 may be performed according to the methods described herein. In some examples, aspects of the operations of 2310 may be performed as described in reference to Figures 12 to 15 The described UE category determination component performs.

[0234] At 2315, the UE may receive frequency hopping information for a broadcast channel from the base station, wherein the frequency hopping information is based on a UE category supported by the SSB. The operations of 2315 may be performed according to the methods described herein. In some examples, aspects of the operations of 2315 may be performed as described in reference to Figures 12 to 15 The described frequency hopping capability components are implemented.

[0235] At 2320, the UE may establish or modify a connection between the UE and the base station based on the determination to use the SSB. The operations of 2320 may be performed according to the methods described herein. In some examples, aspects of the operations of 2320 may be performed as described in reference to Figures 12 to 15 The described connected components are implemented.

[0236] Fig.24 A flow chart illustrating a method 2400 for PBCH enhancement to support lightweight NR communications according to aspects of the present disclosure is shown. The operations of the method 2400 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 2400 may be implemented by a UE 115 or a component thereof as described herein. Figures 12 to 15 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0237] At 2405, the UE may receive an SSB at the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The operations of 2405 may be performed according to the methods described herein. In some examples, aspects of the operations of 2405 may be performed as described in reference to Figures 12 to 15 The described SSB receiver is implemented.

[0238] At 2410, the UE may determine, based on the indication, that the UE belongs to a category of UEs supported by SSB. The operations of 2410 may be performed according to the methods described herein. In some examples, aspects of the operations of 2410 may be performed as described in reference to Figures 12 to 15 The described UE category determination component performs.

[0239] At 2415, the UE may determine a multiplexing pattern for the SSB, a control resource set for broadcast control information, and a system information block based on the UE category supported by the SSB. The operations of 2415 may be performed according to the methods described herein. In some examples, aspects of the operations of 2415 may be performed as described in reference to Figures 12 to 15 The described multiplexing determines the component execution.

[0240] At 2420, the UE may establish or modify a connection between the UE and the base station based on the determination to use the SSB. The operations of 2420 may be performed according to the methods described herein. In some examples, aspects of the operations of 2420 may be performed as described in reference to Figures 12 to 15 The described connected components are implemented.

[0241] Fig.25 A flow chart illustrating a method 2500 for PBCH enhancement for supporting lightweight NR communications according to aspects of the present disclosure is shown. The operations of the method 2500 may be implemented by a base station 105 or a component thereof as described herein. For example, the operations of the method 2500 may be implemented by a base station 105 or a component thereof as described herein. Figures 16 to 19 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0242] At 2505, the base station may send an SSB to the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The operations of 2505 may be performed according to the methods described herein. In some examples, aspects of the operations of 2505 may be performed as described in reference to Figures 16 to 19 The described SSB transmitter implementation.

[0243] At 2510, the base station may determine that the UE belongs to a UE category supported by SSB. The operations of 2510 may be performed according to the methods described herein. In some examples, aspects of the operations of 2510 may be performed as described in reference to Figures 16 to 19 The described UE category components perform.

[0244] At 2515, the base station may establish or modify a connection between the UE and the base station based on determining to use SSB. The operations of 2515 may be performed according to the methods described herein. In some examples, aspects of the operations of 2515 may be performed as described in reference to Figures 16 to 19 The described connection establishment / modification component performs.

[0245] Fig.26 A flow chart illustrating a method 2600 for PBCH enhancement to support lightweight NR communications according to aspects of the present disclosure is shown. The operations of the method 2600 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 2600 may be implemented by a base station 105 or components thereof as described herein. Figures 16 to 19 In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0246] At 2605, the base station may send an SSB to the UE, the SSB including an indication of a UE category supported by the SSB, wherein the UE category is based on the UE bandwidth. The operations of 2605 may be performed according to the methods described herein. In some examples, aspects of the operations of 2605 may be performed as described in reference to Figures 16 to 19 The described SSB transmitter implementation.

[0247] At 2610, the base station may send an indication of a subcarrier offset between the SSB and CRB grids. The operations of 2610 may be performed according to the methods described herein. In some examples, aspects of the operations of 2610 may be performed as described in reference to Figures 16 to 19 The described subcarrier offset indicator is implemented.

[0248] At 2615, the base station may determine that the UE belongs to a UE category supported by SSB. The operations of 2615 may be performed according to the methods described herein. In some examples, aspects of the operations of 2615 may be performed as described in reference to Figures 16 to 19 The described UE category components perform.

[0249] At 2620, the UE may establish or modify a connection between the UE and the base station using the SSB based on the determination and the subcarrier offset. The operations of 2620 may be performed according to the methods described herein. In some examples, aspects of the operations of 2620 may be performed as described in reference to Figures 16 to 19 The described connection establishment / modification component performs.

[0250] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more of the methods may be combined.

[0251] The following provides an overview of various aspects of the present disclosure:

[0252] Aspect 1: A method of wireless communication, comprising: receiving a synchronization signal block at a UE, the synchronization signal block including an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on the UE bandwidth; determining at least in part based on the indication that the UE belongs to the UE category supported by the synchronization signal block; and establishing or modifying a connection between the UE and a base station based at least in part on determining to use the synchronization signal block.

[0253] Aspect 2: A method according to Aspect 1, wherein receiving a synchronization signal block includes: receiving an indication of a subcarrier offset between the synchronization signal block and a carrier resource block grid, wherein establishing or modifying a connection between the UE and the base station is at least partially based on the subcarrier offset.

[0254] Aspect 3: A method according to aspect 2, wherein the indication of the UE category supported by the synchronization signal block is based at least in part on the range within which the subcarrier offset falls.

[0255] Aspect 4: A method according to any one of Aspects 2 to 3, wherein the indication of the subcarrier offset is at least partially based on a combination of a first set of one or more bits in a first field of a synchronization signal block and a second set of one or more bits in a second field of the synchronization signal block.

[0256] Aspect 5: The method according to Aspect 4 further includes: determining a valid range of subcarrier offsets based at least in part on a UE category supported by a synchronization signal block, wherein establishing or modifying a connection between a UE and a base station is also based at least in part on a subcarrier offset in the synchronization signal block that falls within the valid range.

[0257] Aspect 6: A method according to any one of Aspects 1 to 5, wherein receiving a synchronization signal block includes: receiving one or more bits that explicitly indicate a UE category supported by the synchronization signal block.

[0258] Aspect 7: The method according to any one of Aspects 1 to 6 further includes: receiving repetition information of the broadcast channel from the base station, wherein the repetition information is at least partially based on the UE category supported by the synchronization signal block.

[0259] Aspect 8: The method according to aspect 7, wherein the repetition information includes one or more of the following: an indication of support for intra-slot repetition on the broadcast channel, an indication of support for inter-slot repetition on the broadcast channel, or a combination thereof.

[0260] Aspect 9: The method according to any one of aspects 7 to 8, wherein the repetition information includes an indication of a number of transmission repetitions configured for the broadcast channel.

[0261] Aspect 10: A method according to any one of Aspects 7 to 9, wherein the repetition information is received in one or more of the following: a master information block, a physical layer payload of a broadcast channel, a demodulation reference signal scrambling identifier of a broadcast channel, or any combination thereof.

[0262] Aspect 11: The method according to any one of aspects 1 to 10 further includes: receiving frequency hopping information of a broadcast channel from a base station, wherein the frequency hopping information is at least partially based on a UE category supported by a synchronization signal block.

[0263] Aspect 12: The method according to aspect 11, wherein the frequency hopping information includes one or more of the following: an indication of support for intra-time slot frequency hopping on the broadcast channel, an indication of support for inter-time slot frequency hopping on the broadcast channel, or a combination thereof.

[0264] Aspect 13: A method according to any one of Aspects 11 to 12, wherein the frequency hopping information is received in one or more of the following: a master information block, a physical layer payload of a broadcast channel, a demodulation reference signal scrambling identifier of a broadcast channel, or any combination thereof.

[0265] Aspect 14: The method according to any one of Aspects 1 to 13 also includes: determining a multiplexing pattern of a synchronization signal block, a control resource set for broadcast control information, and a system information block based at least in part on a UE category supported by the synchronization signal block.

[0266] Aspect 15: A method according to Aspect 14, wherein determining the multiplexing pattern based at least in part on the UE category supported by the synchronization signal block includes mapping the multiplexing pattern to a combination of the UE bandwidth, the subcarrier spacing associated with the synchronization signal block, and the subcarrier spacing of the broadcast control information of the control resource set.

[0267] Aspect 16: A method according to any one of Aspects 1 to 15, wherein establishing or modifying a connection includes: receiving system information in a synchronization information block; and performing one or more of the following based at least in part on the system information: a radio resource control (RRC) connection establishment process, an RRC connection reconfiguration process, or an RRC release process.

[0268] Aspect 17: A method of wireless communication at a base station, comprising: sending a synchronization signal block to a UE, the synchronization signal block including an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on the UE bandwidth; determining that the UE belongs to the UE category supported by the synchronization signal block; and establishing or modifying a connection between the UE and the base station based at least in part on determining to use the synchronization signal block.

[0269] Aspect 18: A method according to Aspect 17, wherein sending a synchronization signal block includes: sending an indication of a subcarrier offset between the synchronization signal block and a carrier resource block grid, wherein establishing or modifying a connection between the UE and the base station is at least partially based on the subcarrier offset.

[0270] Aspect 19: The method according to any one of aspects 17 and 18, wherein determining that the UE belongs to a UE category comprises: receiving UE capability information indicating the UE category from the UE.

[0271] Aspect 20: A method according to any one of Aspects 17 to 18, wherein sending a synchronization signal block includes: sending one or more bits that explicitly indicate the UE category supported by the synchronization signal block.

[0272] Aspect 21: The method according to any one of Aspects 17 to 20 further includes: sending repetition information of the broadcast channel to the UE, wherein the repetition information is at least partially based on the UE category supported by the synchronization signal block.

[0273] Aspect 22: The method according to any one of Aspects 17 to 21 further includes: sending frequency hopping information of the broadcast channel to the UE, wherein the frequency hopping information is at least partially based on the UE category supported by the synchronization signal block.

[0274] Aspect 23: An apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 1 to 15.

[0275] Aspect 24: An apparatus comprising at least one component for performing the method according to any one of aspects 1 to 15.

[0276] Aspect 25: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method of any one of Aspects 1 to 15.

[0277] Aspect 26: An apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 17 to 22.

[0278] Aspect 27: An apparatus comprising at least one component for performing the method according to any one of aspects 17 to 22.

[0279] Aspect 28: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method of any one of Aspects 17 to 22.

[0280] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems are described for purposes of illustration, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0281] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0282] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0283] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent through a computer-readable medium as one or more instructions or codes. Other examples and implementations are also within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented in software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features implementing the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0284] Computer readable medium includes two kinds of non-temporary computer storage medium and communication medium, and communication medium includes any medium that is convenient to transfer computer program from one place to another place.Non-temporary storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-temporary computer readable medium can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-temporary medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, etc., then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave, etc. are all included in the definition of computer readable medium. Disk and disc, as used herein, include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0285] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0286] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the similar components. If only the first reference label is used in the specification, the description applies to any of the similar components having the same first reference label without regard to the second reference label or other subsequent reference labels.

[0287] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." The detailed description includes specific details intended to provide an understanding of the described technology. However, these technologies may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0288] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A wireless communication device, comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, at a user equipment (UE), a synchronization signal block, the synchronization signal block comprising an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on a UE bandwidth, wherein the UE belongs to the UE category supported by the synchronization signal block; determining a multiplexing pattern for the synchronization signal block based at least in part on the UE category supported by the synchronization signal block as indicated by the indication; and A connection between the UE and a network device is established or modified using the synchronization signal block based at least in part on the UE belonging to the UE category supported by the synchronization signal block.

2. The device according to claim 1, wherein: The instructions for receiving the synchronization signal block are executable by the processor to cause the apparatus to: An indication of a subcarrier offset between the synchronization signal block and a grid of carrier resource blocks is received, wherein establishing or modifying the connection between the UE and the network device is based at least in part on the subcarrier offset.

3. The device according to claim 2, wherein: The indication of the UE category supported by the synchronization signal block is based at least in part on a range within which the subcarrier offset falls.

4. The device according to claim 2, wherein: The indication of the subcarrier offset is based at least in part on a combination of a first set of one or more bits in a first field of the synchronization signal block and a second set of one or more bits in a second field of the synchronization signal block.

5. The device according to claim 4, wherein: When the indication of the subcarrier offset is based at least in part on the combination of the first set of one or more bits in the first field of the synchronization signal block and the second set of one or more bits in the second field of the synchronization signal block, the instructions are further executable by the processor to cause the apparatus to: A valid range of the subcarrier offset is determined at least in part based on the UE category supported by the synchronization signal block, wherein establishing or modifying the connection between the UE and the network device is also at least in part based on the subcarrier offset in the synchronization signal block falling within the valid range.

6. The device according to claim 1, wherein: The instructions for receiving the synchronization signal block are executable by the processor to cause the apparatus to: One or more bits are received that explicitly indicate the UE category supported by the synchronization signal block.

7. The device according to claim 1, wherein: The instructions are further executable by the processor to cause the apparatus to: Repetition information of a broadcast channel is received from a network device, wherein the repetition information is based at least in part on the UE category supported by the synchronization signal block.

8. The device according to claim 7, wherein: The repetition information includes one or more of: an indication of support for intra-slot repetition on the broadcast channel, an indication of support for inter-slot repetition on the broadcast channel.

9. The device according to claim 7, wherein: The repetition information includes an indication of a number of transmission repetitions configured for the broadcast channel.

10. The device according to claim 7, wherein: The repetition information is received in one or more of: a master information block, a physical layer payload of the broadcast channel, a demodulation reference signal scrambling identifier of the broadcast channel.

11. The device according to claim 1, wherein: The instructions are further executable by the processor to cause the apparatus to: Frequency hopping information for a broadcast channel is received from a network device, wherein the frequency hopping information is based at least in part on the UE category supported by the synchronization signal block.

12. The device according to claim 11, wherein The frequency hopping information includes one or more of: an indication of support for intra-slot frequency hopping on the broadcast channel, an indication of support for inter-slot frequency hopping on the broadcast channel.

13. The device according to claim 11, wherein: The frequency hopping information is received in one or more of: a master information block, a physical layer payload of the broadcast channel, a demodulation reference signal scrambling identifier of the broadcast channel.

14. The device according to claim 1, wherein: The instructions are further executable by the processor to cause the apparatus to: A control resource set and a system information block for broadcasting control information are determined based at least in part on the UE category supported by the synchronization signal block.

15. The device according to claim 14, wherein: The instructions for determining the multiplexing pattern of the synchronization signal block based at least in part on the UE category supported by the synchronization signal block are executable by the processor to cause the apparatus to: The multiplexing pattern is mapped to a combination of the UE bandwidth, the subcarrier spacing associated with the synchronization signal block, and the subcarrier spacing of the broadcast control information of the control resource set.

16. The device according to claim 1, wherein The instructions are further executable by the processor to cause the apparatus to: receiving system information in the synchronization signal block; and Based at least in part on the system information, one or more of: a radio resource control, RRC, connection establishment procedure, an RRC connection reconfiguration procedure, or an RRC release procedure is performed.

17. A wireless communication device, comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: sending a synchronization signal block to a user equipment (UE), the synchronization signal block comprising an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on a UE bandwidth, wherein the UE belongs to the UE category supported by the synchronization signal block, and multiplexing the synchronization signal block based at least in part on the UE category supported by the synchronization signal block; as well as The synchronization signal block is used to establish or modify a connection between the UE and a network device.

18. The device according to claim 17, wherein: The instructions for sending the synchronization signal block are executable by the processor to cause the apparatus to: An indication of a subcarrier offset between the synchronization signal block and a carrier resource block grid is sent.

19. The device according to claim 17, wherein: The instructions for sending the synchronization signal block are executable by the processor to cause the apparatus to: One or more bits are sent that explicitly indicate the UE category supported by the synchronization signal block.

20. The device according to claim 17, wherein: The instructions are further executable by the processor to cause the apparatus to: Repetition information of a broadcast channel is sent to the UE, wherein the repetition information is based at least in part on the UE category supported by the synchronization signal block.

21. The device according to claim 17, wherein: The instructions are further executable by the processor to cause the apparatus to: Frequency hopping information for a broadcast channel is transmitted to the UE, wherein the frequency hopping information is based at least in part on the UE category supported by the synchronization signal block.

22. The device according to claim 17, wherein: The instructions for determining that the UE belongs to the UE category are further executable by the processor to cause the apparatus to: Capability information indicating the UE category is received from the UE.

23. A method of wireless communication, comprising: receiving, at a user equipment (UE), a synchronization signal block, the synchronization signal block comprising an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on a UE bandwidth, wherein the UE belongs to the UE category supported by the synchronization signal block; determining a multiplexing pattern for the synchronization signal block based at least in part on the UE category supported by the synchronization signal block as indicated by the indication; and A connection between the UE and a network device is established or modified using the synchronization signal block based at least in part on the UE belonging to the UE category supported by the synchronization signal block.

24. The method according to claim 23, wherein: Receiving the synchronization signal block includes: An indication of a subcarrier offset between the synchronization signal block and a grid of carrier resource blocks is received, wherein establishing or modifying the connection between the UE and the network device is based at least in part on the subcarrier offset.

25. The method according to claim 23, wherein: The receiving the synchronization signal block comprises: One or more bits are received that explicitly indicate the UE category supported by the synchronization signal block.

26. The method of claim 23, further comprising: Repetition information of a broadcast channel is received from a network device, wherein the repetition information is based at least in part on the UE category supported by the synchronization signal block.

27. The method of claim 23, further comprising: Frequency hopping information for a broadcast channel is received from a network device, wherein the frequency hopping information is based at least in part on the UE category supported by the synchronization signal block.

28. A method of wireless communication at a network device, comprising: sending a synchronization signal block to a user equipment (UE), the synchronization signal block comprising an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on a UE bandwidth, wherein the UE belongs to the UE category supported by the synchronization signal block, and multiplexing the synchronization signal block based at least in part on the UE category supported by the synchronization signal block; and A connection between the UE and the network device is established or modified using the synchronization signal block.

29. The method according to claim 28, wherein: Sending the synchronization signal block includes: An indication of a subcarrier offset between the synchronization signal block and a carrier resource block grid is sent.

30. The method of claim 28, wherein: The sending the synchronization signal block comprises: One or more bits are sent that explicitly indicate the UE category supported by the synchronization signal block.

31. The method of claim 28, further comprising: Repetition information of a broadcast channel is sent to the UE, wherein the repetition information is based at least in part on the UE category supported by the synchronization signal block.

32. The method of claim 28, further comprising: Frequency hopping information for a broadcast channel is transmitted to the UE, wherein the frequency hopping information is based at least in part on the UE category supported by the synchronization signal block.

33. A wireless communication device, comprising: means for receiving, at a user equipment (UE), a synchronization signal block, the synchronization signal block comprising an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on a UE bandwidth, wherein the UE belongs to the UE category supported by the synchronization signal block; means for determining a multiplexing pattern of the synchronization signal block based at least in part on the UE category supported by the synchronization signal block as indicated by the indication; and Means for establishing or modifying a connection between the UE and a network device using the synchronization signal block based at least in part on the UE belonging to the UE category supported by the synchronization signal block.

34. An apparatus for wireless communication at a network device, comprising: means for sending a synchronization signal block to a user equipment, UE, the synchronization signal block comprising an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on a UE bandwidth, wherein the UE belongs to the UE category supported by the synchronization signal block; means for multiplexing the synchronization signal blocks based at least in part on the UE categories supported by the synchronization signal blocks; and means for establishing or modifying a connection between the UE and the network device using the synchronization signal block.

35. A non-transitory computer readable medium storing program instructions that, when executed by a processor, perform a method of wireless communication comprising: receiving, at a user equipment (UE), a synchronization signal block, the synchronization signal block comprising an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on a UE bandwidth, wherein the UE belongs to the UE category supported by the synchronization signal block; determining a multiplexing pattern for the synchronization signal block based at least in part on the UE category supported by the synchronization signal block as indicated by the indication; and A connection between the UE and a network device is established or modified using the synchronization signal block based at least in part on the UE belonging to the UE category supported by the synchronization signal block.

36. A non-transitory computer readable medium storing program instructions that, when executed by a processor, perform a method of wireless communication at a network device, comprising: sending a synchronization signal block to a user equipment (UE), the synchronization signal block comprising an indication of a UE category supported by the synchronization signal block, wherein the UE category is based at least in part on a UE bandwidth, wherein the UE belongs to the UE category supported by the synchronization signal block, and multiplexing the synchronization signal block based at least in part on the UE category supported by the synchronization signal block; and A connection between the UE and the network device is established or modified using the synchronization signal block.

Images