Patent ID: 12207208

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

FIG.1depicts an embodiment of a wireless communication system100for transmitting and/or receiving a synchronization signal block. In one embodiment, the wireless communication system100includes remote units102and network units104. Even though a specific number of remote units102and network units104are depicted inFIG.1, one of skill in the art will recognize that any number of remote units102and network units104may be included in the wireless communication system100.

In one embodiment, the remote units102may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), IoT devices, or the like. In some embodiments, the remote units102include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units102may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units102may communicate directly with one or more of the network units104via UL communication signals. In various embodiments, the remote units102may communicate directly with one or more other remote units102.

The network units104may be distributed over a geographic region. In certain embodiments, a network unit104may also be referred to as an access point, an access terminal, a base, a base unit, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a network device, an infrastructure device, or by any other terminology used in the art. The network units104are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art. In some embodiments, a network unit104may include one or more of the following network components an eNB, a gNB, an AMF, a DB, an MME, a PCF, a UDR, a UPF, a serving gateway, and/or a UDM.

In one implementation, the wireless communication system100is compliant with the LTE of the 3GPP protocol, wherein the network unit104transmits using an OFDM modulation scheme on the DL and the remote units102transmit on the UL using a SC-FDMA scheme or an OFDM scheme. More generally, however, the wireless communication system100may implement some other open or proprietary communication protocol, for example, WiMAX, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

The network units104may serve a number of remote units102within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units104transmit DL communication signals to serve the remote units102in the time, frequency, and/or spatial domain.

In certain embodiments, a remote unit102may receive a synchronization signal block. In various embodiments, the remote unit102may detect a primary synchronization signal and a broadcast channel of the synchronization signal block. In some embodiments, receiving the synchronization signal block includes receiving at least one synchronization signal block of multiple synchronization signal blocks within a time window and the broadcast channel includes multiple sub-bands. Accordingly, a remote unit102may be used for receiving a synchronization signal block.

In various embodiments, a network unit104may determine a synchronization signal block including a primary synchronization signal and a broadcast channel. In various embodiments, the network unit104may transmit the synchronization signal block. In certain embodiments, transmitting the synchronization signal block includes transmitting multiple synchronization signal blocks within a time window and the broadcast channel includes multiple sub-bands. Accordingly, a network unit104may be used for transmitting a synchronization signal block.

FIG.2depicts one embodiment of an apparatus200that may be used for receiving a synchronization signal block. The apparatus200includes one embodiment of the remote unit102. Furthermore, the remote unit102may include a processor202, a memory204, an input device206, a display208, a transmitter210, and a receiver212. In some embodiments, the input device206and the display208are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit102may not include any input device206and/or display208. In various embodiments, the remote unit102may include one or more of the processor202, the memory204, the transmitter210, and the receiver212, and may not include the input device206and/or the display208.

The processor202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor202may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor202executes instructions stored in the memory204to perform the methods and routines described herein. In certain embodiments, the processor202may detect a primary synchronization signal and a broadcast channel of the synchronization signal block. In some embodiments, the broadcast channel includes at least one sub-band, and the at least one sub-band carries a self-decodable unit. The processor202is communicatively coupled to the memory204, the input device206, the display208, the transmitter210, and the receiver212.

The memory204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory204includes volatile computer storage media. For example, the memory204may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory204includes non-volatile computer storage media. For example, the memory204may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory204includes both volatile and non-volatile computer storage media. In some embodiments, the memory204stores data relating to synchronization signal blocks. In some embodiments, the memory204also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit102.

The input device206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device206may be integrated with the display208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device206includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device206includes two or more different devices, such as a keyboard and a touch panel.

The display208, in one embodiment, may include any known electronically controllable display or display device. The display208may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display208includes an electronic display capable of outputting visual data to a user. For example, the display208may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display208may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display208may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

In certain embodiments, the display208includes one or more speakers for producing sound. For example, the display208may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display208includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display208may be integrated with the input device206. For example, the input device206and display208may form a touchscreen or similar touch-sensitive display. In other embodiments, the display208may be located near the input device206.

The transmitter210is used to provide UL communication signals to the network unit104and the receiver212is used to receive DL communication signals from the network unit104. In one embodiment, the receiver212may receive a synchronization signal block. In some embodiments, the receiver212receiving the synchronization signal block includes the receiver212receiving at least one synchronization signal block of multiple synchronization signal blocks within a time window and the broadcast channel includes multiple sub-bands. In some embodiments, the primary synchronization signal, at least one secondary synchronization signal, and the broadcast channel are transmitted in one slot. In certain embodiments, the method includes determining slot and frame timing information from the synchronization signal block. In various embodiments, the time window including the multiple synchronization signal blocks occurs periodically. In some embodiments, the time window includes 5 ms or 10 ms. Although only one transmitter210and one receiver212are illustrated, the remote unit102may have any suitable number of transmitters210and receivers212. The transmitter210and the receiver212may be any suitable type of transmitters and receivers. In one embodiment, the transmitter210and the receiver212may be part of a transceiver.

FIG.3depicts one embodiment of an apparatus300that may be used for transmitting a synchronization signal block. The apparatus300includes one embodiment of the network unit104. Furthermore, the network unit104may include a processor302, a memory304, an input device306, a display308, a transmitter310, and a receiver312. As may be appreciated, the processor302, the memory304, the input device306, the display308, the transmitter310, and the receiver312may be substantially similar to the processor202, the memory204, the input device206, the display208, the transmitter210, and the receiver212of the remote unit102, respectively.

In various embodiments, the processor302may determine a synchronization signal block including a primary synchronization signal and a broadcast channel. In certain embodiments, the transmitter310may transmit the synchronization signal block. In some embodiments, the transmitter310transmitting the synchronization signal block includes the transmitter310transmitting multiple synchronization signal blocks within a time window and the broadcast channel includes multiple sub-bands. In some embodiments, the primary synchronization signal, at least one secondary synchronization signal, and the broadcast channel are transmitted in one slot. In certain embodiments, slot and frame timing information are determined from the synchronization signal block. In various embodiments, the time window including the multiple synchronization signal blocks occurs periodically. In some embodiments, the time window includes 5 ms or 10 ms. In various embodiments, the broadcast channel includes at least one sub-band, and the at least one sub-band carries a self-decodable unit. Although only one transmitter310and one receiver312are illustrated, the network unit104may have any suitable number of transmitters310and receivers312. The transmitter310and the receiver312may be any suitable type of transmitters and receivers. In one embodiment, the transmitter310and the receiver312may be part of a transceiver.

In certain embodiments, a minimum channel bandwidth of various networks (e.g., 5G RAT) may be larger than a minimum channel bandwidth of other networks (e.g., LTE, 1.4 MHz). In various embodiments, a transmission bandwidth of SS and/or PBCH of certain networks (e.g., 5G RAT) may be wider than a transmission bandwidth of other networks (e.g., LTE PSS and/or SSS, 1.08 MHz including guard subcarriers). In some embodiments, remote units102may operate in a network with a limited bandwidth (e.g., a receiver bandwidth of 1.4 MHz) and/or with a wideband bandwidth (e.g., a receiver bandwidth larger than 1.4 MHz), and a common PBCH for operation with the limited bandwidth and the wideband bandwidth is beneficial for efficient radio resource utilization.

In some embodiments, when PSS and/or SSS are transmitted with narrow beams, many SS blocks (each of which carries beamformed PSS and/or SSS) may be transmitted in order to cover multiple spatial directions. In one embodiment, an idle mode remote unit102may assume that an SS burst set including one or more SS blocks (e.g., up to two hundred SS blocks) is transmitted with 80 ms periodicity, and the remote unit102may detect one (or multiple) SS block transmitted with suitable transmit beams for the remote unit102. In such embodiments, two hundred vertical and/or azimuth narrow beams may be considered to cover one sector; however, it may be difficult to predetermine locations of two hundred SS blocks, considering dynamic UL and/or DL operation in TDD. In various embodiments, an actual number of SS blocks may vary depending on a network implementation. In some embodiments, if a network entity employs wide beams for PSS and/or SSS transmission, the network entity may transmit a smaller number of SS blocks than two hundred SS blocks. In such embodiments, some flexibility to locate SS blocks may be available without resulting in too much signaling overhead for indicating the SS block location. In various embodiments, PBCH may be transmitted within SS blocks.

In certain embodiments, PBCH may be transmitted in 6 RBs of 1.08 MHz bandwidth, and one self-decodable unit of channel bits may be transmitted on 4 consecutive OFDM symbols. In some embodiments, such as dynamic TDD operation and/or URLLC services in 5G RAT, longer transmission duration may not be used for physical channels which are transmitted on predefined and/or known locations (e.g., PBCH), because it may restrict UL and/or DL switching flexibility.

In various embodiments, PSS and/or SSS may be transmitted once per a 5 ms periodicity, and, therefore, it may be difficult to efficiently locate multiple SS blocks (e.g., up to two hundred SS blocks) within a periodically transmitted SS burst set.

In some embodiments, for energy-efficient network operation, a network may minimize an “always-on” signal in the network. In various embodiments, a NE may set a periodicity of SS blocks including one or more synchronization signals and PBCH to a larger value. In such embodiments, a remote unit102may detect a cell network quickly even with an NE's sparse transmission of SS blocks in time. In certain embodiments, for RRC idle mode remote units102, the remote units102may detect and/or measure a cell network based on one or more SS blocks that each include one or more SS and PBCH.

In some embodiments, a transmission BW for PSS and/or SSS may be determined to provide good one-shot detection probability at −6 dB received baseband SNR with less than 1% false alarm rate. In such embodiments, for a given SNR per sub-carrier and a given subcarrier spacing, a larger transmission BW (and a larger number of subcarriers and a longer PSS and/or SSS sequence) for PSS and/or SSS may provide better detection performance, as it may provide a larger processing gain. In some embodiments, length-63 PSS sequences may achieve a 1% missed detection rate at 3 dB SNR, while length-251 Zadoff-Chu (“ZC”) sequence based PSS may have a −4.5 dB SNR for a 1% missed detection rate. In one embodiment, with subcarrier mapping of PSS and 15 KHz subcarrier spacing, the transmission BW for PSS may be set to 8.64 MHz (e.g., 48 RBs assuming 12 subcarriers in one RB), which is 8 times wider than certain SS bandwidths (e.g., 1.08 MHz, 6 RB). In such embodiments, assuming a same transmission BW for both PSS and SSS, certain SSS sequences may be approximately 8 times longer than other SSS, which may be beneficial for improving one-shot detection performance. In certain embodiments, applying a same set of PSS and/or SSS sequences as used in certain above embodiments to a frequency range above 6 GHz, the transmission BW for PSS and/or SSS may be 69.12 MHz with 120 KHz subcarrier spacing in the frequency range above 6 GHz.

FIG.4illustrates one embodiment of wideband PBCH400carried by four symbols. Specifically, a first transmission402(e.g., PBCH transmission) and a second transmission404(e.g., PBCH transmission) are illustrated. The first transmission402may be transmitted in a first time interval406that is part of an SS burst set periodicity408. In some embodiments, the first time interval406may be approximately 20 ms; while in other embodiments, the first time interval406may have a different time interval. In various embodiments, the SS burst set periodicity408may be approximately 80 ms; while in other embodiments, the SS burst set periodicity408may have a different time interval. In certain embodiments, the first transmission402may include a first symbol RV0410, a second symbol RV1412, a third symbol RV2414, and a fourth symbol RV3416. In some embodiments, the first symbol RV0410, the second symbol RV1412, the third symbol RV2414, and the fourth symbol RV3416may each have a bandwidth418. In various embodiments, the bandwidth418may be 12 RBs; while, in other embodiments, the bandwidth418may have a different number of RBs. In certain embodiments, the first symbol RV0410and the second symbol RV1412(e.g., a first sub-band) are located at a central frequency portion of the first transmission402, and the third symbol RV2414and the forth symbol RV3416(e.g., a second sub-band) are located on both sides of the central frequency portion. In such embodiments, the first sub-band and the second sub-band may be substantially the same size; while, in other embodiments, the first sub-band and the second sub-band may be different in size. In some embodiments, only the first sub-band may be received and/or decoded by a remote unit102; while, in other embodiments, both the first sub-band and the second sub-band may be received and/or decoded by a remote unit102. In various embodiments, the first sub-band and the second sub-band are both self-decodable units.

In certain embodiments, the second transmission404may include the first symbol RV0410, the second symbol RV1412, the third symbol RV2414, and the fourth symbol RV3416. In some embodiments, the first symbol RV0410, the second symbol RV1412, the third symbol RV2414, and the fourth symbol RV3416may each have the bandwidth418. In certain embodiments, the third symbol RV2414and the forth symbol RV3416(e.g., a first sub-band) are located at a central frequency portion of the second transmission404, and the first symbol RV0410and the second symbol RV1412(e.g., a second sub-band) are located on both sides of the central frequency portion. In such embodiments, the first sub-band and the second sub-band may be substantially the same size; while, in other embodiments, the first sub-band and the second sub-band may be different in size. In some embodiments, only the first sub-band may be received and/or decoded by a remote unit102; while, in other embodiments, both the first sub-band and the second sub-band may be received and/or decoded by a remote unit102. In various embodiments, the first sub-band and the second sub-band are both self-decodable units. As may be appreciated, a remote unit102receiving the first sub-band of the first transmission402and the first sub-band of the second transmission404may receive the first symbol RV0410, the second symbol RV1412, the third symbol RV2414, and the fourth symbol RV3416. Furthermore, a remote unit102receiving the first and second sub-bands of the first transmission402and the first and second sub-bands of the second transmission404may receive the first symbol RV0410, the second symbol RV1412, the third symbol RV2414, and the fourth symbol RV3416, wherein each symbol is received twice in different time and frequency resources.

FIG.5illustrates one embodiment of wideband PBCH500carried by two symbols. Specifically, a first transmission502(e.g., PBCH transmission) and a second transmission504(e.g., PBCH transmission) are illustrated. The first transmission502may be transmitted in a first time interval506that is part of an SS burst set periodicity508. In some embodiments, the first time interval506may be approximately 20 ms; while in other embodiments, the first time interval506may have a different time interval. In various embodiments, the SS burst set periodicity508may be approximately 80 ms; while in other embodiments, the SS burst set periodicity508may have a different time interval. In certain embodiments, the first transmission502may include a first symbol RV0510and a second symbol RV1512. In various embodiments, the second transmission504may include a third symbol RV2514and a fourth symbol RV3516. In some embodiments, the first symbol RV0510, the second symbol RV1512, the third symbol RV2514, and the fourth symbol RV3516may each have a bandwidth518. In various embodiments, the bandwidth518may be 24 RBs; while, in other embodiments, the bandwidth518may have a different number of RBs. In certain embodiments, the first symbol RV0510(e.g., a first sub-band) is located at a central frequency portion of the first transmission502, and the second symbol RV1512(e.g., a second sub-band) is located on both sides of the central frequency portion. In such embodiments, the first sub-band and the second sub-band may be substantially the same size; while, in other embodiments, the first sub-band and the second sub-band may be different in size. In some embodiments, only the first sub-band may be received and/or decoded by a remote unit102; while, in other embodiments, both the first sub-band and the second sub-band may be received and/or decoded by a remote unit102. In various embodiments, the first sub-band and the second sub-band are both self-decodable units.

In certain embodiments, the second transmission504may include the third symbol RV2514and the fourth symbol RV3516. In some embodiments, the third symbol RV2514(e.g., a first sub-band) is located at a central frequency portion of the second transmission504, and the fourth symbol RV3516(e.g., a second sub-band) is located on both sides of the central frequency portion. In such embodiments, the first sub-band and the second sub-band may be substantially the same size; while, in other embodiments, the first sub-band and the second sub-band may be different in size. In some embodiments, only the first sub-band may be received and/or decoded by a remote unit102; while, in other embodiments, both the first sub-band and the second sub-band may be received and/or decoded by a remote unit102. In various embodiments, the first sub-band and the second sub-band are both self-decodable units. As may be appreciated, a remote unit102receiving the first sub-band of the first transmission502and the first sub-band of the second transmission504may receive the first symbol RV0510and the third symbol RV2514. Furthermore, a remote unit102receiving the first and second sub-bands of the first transmission502and the first and second sub-bands of the second transmission504may receive the first symbol RV0510, the second symbol RV1512, the third symbol RV2514, and the fourth symbol RV3516.

In some embodiments, similar to PSS and/or SSS, PBCH may be transmitted with predefined subcarrier spacing and a predefined transmission BW, and the PBCH transmission BW may be the same as the SS transmission BW. In various embodiments, wideband PBCH transmission may be on 2 OFDM symbols per PBCH TTI (e.g.,FIG.5), for example, 48 RB PBCH BW, equivalently, 8.64 MHz PBCH BW for a frequency range below 6 GHz and 69.12 MHz PBCH BW for a frequency range above 6 GHz, may achieve similar coding rate as LTE PBCH (e.g., 6 RB PBCH BW, 4 OFDM symbols per frame, 4 frame TTI). If two PBCH OFDM symbols are transmitted on different frames as shown inFIG.5, time diversity may be achieved. Furthermore, wideband transmission may exploit frequency diversity, and short PBCH transmission duration may enable flexible UL and/or DL TDD operation even when PBCH is transmitted in a predefined time instance.

In one embodiment, PBCH may be transmitted at predefined time (e.g. frame, slot, subframe, and/or OFDM symbols) and frequency radio resources. In some embodiments, once a remote unit102detects an SS block and acquires symbol, slot, and/or frame timing information from the detected SS block, the remote unit102may locate and/or receive PBCH based on the acquired timing information. In such embodiments, this may enable PBCH transmission sparser than SS in time. In certain embodiments, a payload in PBCH may include slot and/or frame timing related information (e.g., symbol index and/or slot index). In such embodiments, a remote unit102may acquire symbol timing information from the detected SS block and decode PBCH based on the acquired symbol timing in order to obtain slot and/or frame timing information.

In one embodiment, wideband PBCH includes two sub-bands with the same or different sizes, and one or more self-decodable segmentation units of coded and/or rate-matched PBCH channels bits transmitted on each sub-band. For example,FIG.4illustrates 4 symbol PBCH andFIG.5illustrates 2 symbol PBCH. In some embodiments, a few subcarriers between two sub-bands are reserved as guard subcarriers. In various embodiments, for a remote unit102operated with a smaller bandwidth (e.g., 24 RBs), narrow bandwidth (e.g., 24 RBs), and/or being bandlimited (e.g., 24 RBs), the remote unit102may receive only the center sub-band of wideband PBCH, and may perform decoding of redundancy versions (“RVs”) transmitted on the center sub-band. In certain embodiments, such as with 2 symbol PBCH illustrated inFIG.5, a narrowband remote unit102may combine RV0510and RV2514channel bits for PBCH decoding. In such embodiments, a narrowband operation may occur for remote units102with limited bandwidth capability and/or remote units102in a power saving mode. In some embodiments, such as for power saving remote units102, a remote unit102operating bandwidth may be reduced to 5 MHz after the remote unit102performs an initial access with a 10 MHz bandwidth. In another embodiment, mapping of rate-matched PBCH channel coded bits to REs of a sub-band, mapping of a portion of PBCH channel coded bits to REs of a sub-band, and/or mapping of one or more rate-matched PBCH channel coded bits to a portion of REs of a sub-band (located approximately symmetric around a synchronization raster location—which may correspond to a central frequency portion of a PBCH transmission on a carrier) may be invariant to a PBCH transmission bandwidth. In certain embodiments, a few subcarriers around a sub-band may be reserved as guard subcarriers. In such embodiments, this may enable narrow bandwidth capable remote units102, bandlimited capable remote units102, and/or remote units102operating with a narrow bandwidth to receive PBCH in a narrow bandwidth and/or combine received PBCH REs on multiple PBCH symbols without different PBCH RE mapping for multiple PBCH transmission bandwidths.

In various embodiments, in order to decouple PSS and/or SSS periodicity and beamforming from PBCH periodicity and beamforming, PBCH DMRS may be transmitted together with PBCH data instead of using PSS and/or SSS as DMRS for PBCH. In one embodiment, while one transmit beam is used for one PSS and/or SSS instance and 48 PSS and/or SSS instances exist within an SS period of 80 ms, 48 transmit beams may be used on one wideband PBCH symbol via beam cycling and 4 PBCH symbols may exist within 80 ms TTI. In some embodiments, such as for the 4 symbol wideband PBCH ofFIG.4, DMRS of PBCH may be multiplexed with PBCH data in the frequency domain as shown inFIG.6.

Specifically,FIG.6illustrates one embodiment of DMRS multiplexing600.FIG.6illustrates two adjacent OFDM symbols602spanning a bandwidth604(e.g., 1 RB) over a time period606(e.g., two OFDM symbol duration). With the bandwidth, certain of the OFDM symbols602are used to carry DMRS. In particular, OFDM sub carriers608are used to carry DMRS. Because the DMRS may be transmitted on the same subcarriers of 2 consecutive OFDM symbols602, a remote unit102may perform frequency-domain frequency offset estimation and/or compensation by comparing phase rotation of the DMRS on the same DMRS subcarriers of two OFDM symbols602.

FIG.7illustrates one embodiment of transmissions700in a slot702over a bandwidth704. Specifically, the slot702may include PBCH706, PSS708, SSS710, C-PDCCH712, and data714. In certain embodiments, the PBCH706, the PSS708, the SSS710(e.g., including one or more SSS), and the C-PDCCH712may be part of one SS block. In the illustrated embodiment, the PBCH706is transmitted over a sub-bandwidth716(e.g., 12 RBs). Moreover, the PSS708and the SSS710occupy some REs from a first control resource set718, a second control resource set720, and a third control resource set722.

In one embodiment, a remote unit102may assume that a NE transmits SS blocks within an SS block transmission window. In such an embodiment, the SS block transmission window may include one or more slots within an SS burst set period. Furthermore, in certain embodiments, an SS block including the PSS708, the SSS710(e.g., one or more SSS, a tertiary synchronization channel “TSCH,” etc.), and the PBCH706may be transmitted in a DL control region of the slot702within an SS block transmission window. In various embodiments, a maximum of one SS block may be transmitted in a given slot. In some embodiments, a definition of an SS block transmission window may facilitate limiting signaling overhead for indicating an SS block location. However, in certain embodiments, a network may locate an SS block in any slot within a SS block transmission window depending on scheduling needs for UL and/or DL traffic. In various embodiments, even when a network serves UL dominated traffic, the network may still transmit SS blocks within a time window by exploiting a DL control region that may be configured in every slot.

In one embodiment, the DL control region is located in a front part of the slot702, and the PBCH706, the PSS708, the SSS710, and the C-PDCCH712are time-domain multiplexed as shown inFIG.7. In another embodiment, the DL control region is located in a back part of the slot702(e.g., where the data714is shown inFIG.7), and the PBCH706, the PSS708, the SSS710, and the C-PDCCH712are time-domain multiplexed in the back part of the slot702. In certain embodiments, the PBCH706may include one or two PBCH symbols. In various embodiments, the PBCH706may proceed the PSS708in the DL control region as illustrated; however, in other embodiments, the PBCH706may follow the SSS710in the DL control region or may be located between the PSS708and the SSS710.

FIG.8illustrates one embodiment of SS block transmissions800. The SS block transmissions800include a first group of SS blocks802and a second group of SS blocks803. The first group of SS blocks802and the second group of SS blocks803each include one type of SS block (designated by A and including PSS and one or more SSS) and another type of SS block (designated by B and including PSS, one or more SSS, and PBCH). The first group of SS blocks802are transmitted over a transmission time804(e.g., 20 ms). Moreover, the first group of SS blocks802and the second group of SS blocks803are both transmitted within an SS block transmission window806(e.g., 40 ms). Furthermore, an SS burst set periodicity808(e.g., default of 80 ms) is illustrated.

In some embodiments, a maximum of two hundred SS blocks may be transmitted within the SS burst set periodicity808. In certain embodiments, if a network is deployed in a frequency range above 6 GHz with a default subcarrier spacing of 120 KHz, slot duration may be 0.125 ms and 80 slots may be available per radio frame of 10 ms duration. In such embodiments, three hundred sixty slots may be available for transmission of potentially up to two hundred SS blocks. In various embodiments, the PBCH of 80 ms TTI is transmitted on one SS block of the first group of SS blocks802and one SS block of the second group of SS blocks803within the 80 ms SS burst set periodicity808. In such embodiments, the first and second SS blocks802and803carrying PBCH are transmitted on slot 0 of radio frames nffulfilling nfmod 8=0 and nfmod 8=2. Because in such embodiments the PBCH TTI is 80 ms, a payload of PBCH may carry 7 bits indicating a system frame number (“SFN”) in which the SFN varies from 0 to 1023. In certain embodiments, a remote unit102may first determine a radio frame index within the 80 ms PBCH TTI by decoding a portion of a detected SS block. The portion of the detected SS block may include 2 bits indicating a radio frame index (e.g., with 4 possibilities) within the 40 ms SS block transmission window806, 7 bits indicating a slot index (e.g., with 80 possibilities) within a radio frame, and cyclic redundancy check (“CRC”) bits. In such embodiments, the remote unit102may detect PSS and/or SSS, decode a portion of the SS block, identify slot and/or frame timing information from the decoded portion of the SS block, and decode the PBCH from the SS block.

In some embodiments, an NE may indicate whether a slot of an SS block transmission window806carries an SS block or not, via C-PDCCH, so that a remote unit102monitoring a DL control region of the slot may properly identify available control channel elements and/or REs available for PDSCH if the SS block is mapped to a portion of the PDCCH and/or PDSCH region. In certain embodiments, in response to a remote unit102monitoring a slot within the SS block transmission window806, the remote unit102may first receive and decode C-PDCCH, and then determine whether an SS block is transmitted in a DL control region of the slot (or anywhere in the slot). In various embodiments, control channel elements of a slot may be determined excluding resource elements used for PSS and/or SSS transmission. In one embodiment in which PSS and/or SSS transmission is mapped to a portion of a PDSCH region, REs available for PDSCH may be determined excluding PDSCH resource elements used for PSS and/or SSS transmission. In some embodiments, C-PDCCH may be transmitted in a first DL OFDM symbol of a slot, and one example of C-PDCCH transmission is shown inFIG.7. In various embodiments, a network configures a larger DL control region for slots corresponding to the SS block transmission window806, to avoid a potential control channel resource deficiency and/or a control channel blocking issue.

FIG.9is a schematic flow chart diagram illustrating one embodiment of a method900for receiving a synchronization signal block. In some embodiments, the method900is performed by an apparatus, such as the remote unit102. In certain embodiments, the method900may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method900may include receiving902a synchronization signal block. In various embodiments, the method900includes detecting904a primary synchronization signal and a broadcast channel of the synchronization signal block. In some embodiments, receiving the synchronization signal block includes906receiving at least one synchronization signal block of multiple synchronization signal blocks within a time window and the broadcast channel includes multiple sub-bands.

In certain embodiments, at least one sub-band of the multiple sub-bands carries a self-decodable unit. In one embodiment, the method900includes detecting at least one secondary synchronization signal of the synchronization signal block. In a further embodiment, each sub-band of the multiple sub-bands carries at least one self-decodable unit. In certain embodiments, a first sub-band of the multiple sub-bands is a same size as a second sub-band of the multiple sub-bands. In various embodiments, a first sub-band of the multiple sub-bands is a different size than a second sub-band of the multiple sub-bands. In some embodiments, a first sub-band of the multiple sub-bands is located at a central portion of the broadcast channel, and a second sub-band of the multiple sub-bands is located on both sides of the central portion. In certain embodiments, the method900includes receiving only the first sub-band and decoding channel bits transmitted on the first sub-band.

In various embodiments, the at least one self-decodable unit includes coded and rate-matched channel bits. In some embodiments, the primary synchronization signal, at least one secondary synchronization signal, and the broadcast channel are transmitted in one slot. In certain embodiments, the method900includes determining slot and frame timing information from the synchronization signal block. In various embodiments, the time window including the multiple synchronization signal blocks occurs periodically. In some embodiments, the time window includes 5 ms or 10 ms. In certain embodiments, the broadcast channel carries a system frame number. In various embodiments, the broadcast channel carries slot and frame timing related information.

In some embodiments, the method900includes: receiving a common control channel in a first slot; determining whether a synchronization signal block is transmitted in a downlink region of the first slot based on the common control channel; and identifying available downlink resource elements for a physical downlink shared channel or a physical downlink control channel in the downlink region of the first slot. In certain embodiments, the first slot is within a synchronization signal block transmission window, and the synchronization signal block transmission window includes at least one slot for transmitting synchronization signal blocks. In various embodiments, a size of a downlink control region of the first slot is different from a size of a downlink control region of a second slot, and the second slot is not within the synchronization signal block transmission window.

FIG.10is a schematic flow chart diagram illustrating one embodiment of a method1000for transmitting a synchronization signal block. In some embodiments, the method1000is performed by an apparatus, such as the network unit104. In certain embodiments, the method1000may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method1000may include determining1002a synchronization signal block including a primary synchronization signal and a broadcast channel. In various embodiments, the method1000includes transmitting1004the synchronization signal block. In certain embodiments, transmitting the synchronization signal block includes1006transmitting multiple synchronization signal blocks within a time window and the broadcast channel includes multiple sub-bands.

In certain embodiments, at least one sub-band of the multiple sub-bands carries a self-decodable unit. In one embodiment, the method1000includes determining at least one secondary synchronization signal of the synchronization signal block. In a further embodiment, each sub-band of the multiple sub-bands carries at least one self-decodable unit. In certain embodiments, a first sub-band of the multiple sub-bands is a same size as a second sub-band of the multiple sub-bands. In various embodiments, a first sub-band of the multiple sub-bands is a different size than a second sub-band of the multiple sub-bands. In some embodiments, a first sub-band of the multiple sub-bands is located at a central portion of the broadcast channel, and a second sub-band of the multiple sub-bands is located on both sides of the central portion.

In various embodiments, the at least one self-decodable unit includes coded and rate-matched channel bits. In some embodiments, the primary synchronization signal, at least one secondary synchronization signal, and the broadcast channel are transmitted in one slot. In certain embodiments, slot and frame timing information are determined from the synchronization signal block. In various embodiments, the time window including the multiple synchronization signal blocks occurs periodically. In some embodiments, the time window includes 5 ms or 10 ms. In certain embodiments, the broadcast channel carries a system frame number. In various embodiments, the broadcast channel carries slot and frame timing related information.

In some embodiments, the method1000includes transmitting a common control channel in a first slot. In certain embodiments, the first slot is within a synchronization signal block transmission window, and the synchronization signal block transmission window includes at least one slot for transmitting synchronization signal blocks. In various embodiments, a size of a downlink control region of the first slot is different from a size of a downlink control region of a second slot, and the second slot is not within the synchronization signal block transmission window.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.