Method and apparatus for SS / PBCH block structure

Abstract

The present disclosure relates to a 5G communication system or a 6G communication system for supporting higher data rates beyond a 4G communication system such as LTE. Methods and apparatuses for SS / PBCH block structure(s) are provided. A method performed by a UE in a wireless communication system includes identifying a structure for a SS / PBCH block, the structure including a first number N symb of OFDM symbols in a time domain and a second number N RB of RBs in a frequency domain and identifying, from the N symb OFDM symbols, a third number N 1 of OFDM symbols mapped for a PSS, where N 1 > 1. The method further includes identifying, from the N symb OFDM symbols, a fourth number N 2 of OFDM symbols mapped for a SSS, where N 2 > 1 and receiving the SS / PBCH block based on the structure.

Description

METHOD AND APPARATUS FOR SS / PBCH BLOCK STRUCTURE

[0001] The present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure relates to methods and apparatuses for synchronization signals / physical broadcast channel (SS / PBCH) block structure(s).

[0002] Considering the development of wireless communication from generation to generation, the technologies have been developed mainly for services targeting humans, such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th-generation) communication systems, it is expected that the number of connected devices will exponentially grow. Increasingly, these will be connected to communication networks. Examples of connected things may include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machines, and factory equipment. Mobile devices are expected to evolve in various form-factors, such as augmented reality glasses, virtual reality headsets, and hologram devices. In order to provide various services by connecting hundreds of billions of devices and things in the 6G (6th-generation) era, there have been ongoing efforts to develop improved 6G communication systems. For these reasons, 6G communication systems are referred to as beyond-5G systems.

[0003] 6G communication systems, which are expected to be commercialized around 2030, will have a peak data rate of tera (1,000 giga)-level bps and a radio latency less than 100μsec, and thus will be 50 times as fast as 5G communication systems and have the 1 / 10 radio latency thereof.

[0004] In order to accomplish such a high data rate and an ultra-low latency, it has been considered to implement 6G communication systems in a terahertz band (for example, 95GHz to 3THz bands). It is expected that, due to severer path loss and atmospheric absorption in the terahertz bands than those in mmWave bands introduced in 5G, technologies capable of securing the signal transmission distance (that is, coverage) will become more crucial. It is necessary to develop, as major technologies for securing the coverage, radio frequency (RF) elements, antennas, novel waveforms having a better coverage than orthogonal frequency division multiplexing (OFDM), beamforming and massive multiple input multiple output (MIMO), full dimensional MIMO (FD-MIMO), array antennas, and multiantenna transmission technologies such as large-scale antennas. In addition, there has been ongoing discussion on new technologies for improving the coverage of terahertz-band signals, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS).

[0005] Moreover, in order to improve the spectral efficiency and the overall network performances, the following technologies have been developed for 6G communication systems: a full-duplex technology for enabling an uplink transmission and a downlink transmission to simultaneously use the same frequency resource at the same time; a network technology for utilizing satellites, high-altitude platform stations (HAPS), and the like in an integrated manner; an improved network structure for supporting mobile base stations and the like and enabling network operation optimization and automation and the like; a dynamic spectrum sharing technology via collison avoidance based on a prediction of spectrum usage; an use of artificial intelligence (AI) in wireless communication for improvement of overall network operation by utilizing AI from a designing phase for developing 6G and internalizing end-to-end AI support functions; and a next-generation distributed computing technology for overcoming the limit of UE computing ability through reachable super-high-performance communication and computing resources (such as mobile edge computing (MEC), clouds, and the like) over the network. In addition, through designing new protocols to be used in 6G communication systems, developing mecahnisms for implementing a hardware-based security environment and safe use of data, and developing technologies for maintaining privacy, attempts to strengthen the connectivity between devices, optimize the network, promote softwarization of network entities, and increase the openness of wireless communications are continuing.

[0006] It is expected that research and development of 6G communication systems in hyper-connectivity, including person to machine (P2M) as well as machine to machine (M2M), will allow the next hyper-connected experience. Particularly, it is expected that services such as truly immersive extended reality (XR), high-fidelity mobile hologram, and digital replica could be provided through 6G communication systems. In addition, services such as remote surgery for security and reliability enhancement, industrial automation, and emergency response will be provided through the 6G communication system such that the technologies could be applied in various fields such as industry, medical care, automobiles, and home appliances.

[0007] The present disclosure relates to SS / PBCH block structure(s). /

[0008] In one embodiment, a user equipment (UE) in a wireless communication system is provided. The UE includes a processor configured to identify a structure for a SS / PBCH block, the structure including a first number of orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second number of resource blocks (RBs) in a frequency domain, identify, from the OFDM symbols, a third number of OFDM symbols mapped for a primary synchronization signal (PSS), where , and identify, from the OFDM symbols, a fourth number of OFDM symbols mapped for a secondary synchronization signal (SSS), where . The UE further includes a transceiver operably coupled to the processor. The transceiver is configured to receive the SS / PBCH block based on the structure.

[0009] In one embodiment, a base station (BS) in a wireless communication system is provided. The BS includes a processor configured to determine a structure for a SS / PBCH block, the structure including a first number of OFDM symbols in a time domain and a second number of RBs in a frequency domain, determine, from the OFDM symbols, a third number of OFDM symbols mapped for a PSS, where , and determine, from the OFDM symbols, a fourth number of OFDM symbols mapped for a SSS, where . The BS further includes a transceiver operably coupled to the processor. The transceiver is configured to transmit the SS / PBCH block based on the structure.

[0010] In one embodiment, a method performed by a UE in a wireless communication system is provided. The method includes identifying a structure for a SS / PBCH block, the structure including a first number of OFDM symbols in a time domain and a second number of RBs in a frequency domain and identifying, from the OFDM symbols, a third number of OFDM symbols mapped for a PSS, where . The method further includes identifying, from the OFDM symbols, a fourth number of OFDM symbols mapped for a SSS, where and receiving the SS / PBCH block based on the structure.

[0011] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0012] Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “transmit,” “receive,” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and / or. The phrase “associated with,” as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0013] Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0014] Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases.

[0015] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0016] FIG. 1 illustrates an example wireless network according to embodiments of the present disclosure;

[0017] FIG. 2 illustrates an example BS according to embodiments of the present disclosure;

[0018] FIG. 3 illustrates an example UE according to embodiments of the present disclosure;

[0019] FIG. 4A illustrate an example of a wireless transmit path according to embodiments of the present disclosure;

[0020] FIG. 4B illustrate an example of a wireless receive path according to embodiments of the present disclosure;

[0021] FIG. 5 illustrates an example SS / PBCH block architecture according to embodiments of the present disclosure;

[0022] FIG. 6 illustrates diagrams of example synchronization signal block (SSB) architectures according to embodiments of the present disclosure;

[0023] FIG. 7 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0024] FIG. 8 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0025] FIG. 9 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0026] FIG. 10 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0027] FIG. 11 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0028] FIG. 12 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0029] FIG. 13 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0030] FIG. 14 illustrates a flowchart of an example UE procedure for receiving signal(s) / channel(s) according to embodiments of the present disclosure;

[0031] FIG. 15 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0032] FIG. 16 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0033] FIG. 17 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0034] FIG. 18 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0035] FIG. 19 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0036] FIG. 20 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0037] FIG. 21 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0038] FIG. 22 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0039] FIG. 23 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure;

[0040] FIG. 24 illustrates diagrams of example SSB architectures according to embodiments of the present disclosure; and

[0041] FIG. 25 illustrates a flowchart of an example UE procedure for receiving signal(s) / channel(s) according to embodiments of the present disclosure.

[0042] In one embodiment, a user equipment (UE) in a wireless communication system is provided. The UE comprising: at least one transceiver; at least one processor communicatively coupled to the at least one transceiver; and at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to: identify a structure for a synchronization signals / physical broadcast channel (SS / PBCH) block, the structure including a first number of orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second number of resource blocks (RBs) in a frequency domain; identify, from the OFDM symbols, a third number of OFDM symbols mapped for a primary synchronization signal (PSS), where ; and identify, from the OFDM symbols, a fourth number of OFDM symbols mapped for a secondary synchronization signal (SSS), where ; and receive the SS / PBCH block based on the structure.

[0043] In one embodiment, the OFDM symbols are consecutive and within a slot.

[0044] In one embodiment, the OFDM symbols are first consecutive OFDM symbols within the OFDM symbols.

[0045] In one embodiment, the OFDM symbols are non-consecutive OFDM symbols within the OFDM symbols.

[0046] In one embodiment, =12.

[0047] In one embodiment, a first sequence for the PSS is mapped to center 127 subcarriers within subcarriers of the RBs, in each OFDM symbol within the OFDM symbols; and a second sequence for the SSS is mapped to center 127 subcarriers within subcarriers of the RBs, in each OFDM symbol within the OFDM symbols.

[0048] In one embodiment, remaining - - OFDM symbols within the OFDM symbols are mapped for a PBCH in the SS / PBCH block.

[0049] In one embodiment, a base station (BS) in a wireless communication system is provided. The BS comprising: at least one transceiver; at least one processor communicatively coupled to the at least one transceiver; and at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the BS to: determine a structure for a synchronization signals / physical broadcast channel (SS / PBCH) block, the structure including a first number of orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second number of resource blocks (RBs) in a frequency domain; determine, from the OFDM symbols, a third number of OFDM symbols mapped for a primary synchronization signal (PSS), where ; and determine, from the OFDM symbols, a fourth number of OFDM symbols mapped for a secondary synchronization signal (SSS), where ; and transmit the SS / PBCH block based on the structure.

[0050] In one embodiment, the OFDM symbols are consecutive and within a slot.

[0051] In one embodiment, the OFDM symbols are first consecutive OFDM symbols within the OFDM symbols.

[0052] In one embodiment, the OFDM symbols are non-consecutive OFDM symbols within the OFDM symbols.

[0053] In one embodiment, a first sequence for the PSS is mapped to center 127 subcarriers within subcarriers of the RBs, in each OFDM symbol within the OFDM symbols; and a second sequence for the SSS is mapped to center 127 subcarriers within subcarriers of the RBs, in each OFDM symbol within the OFDM symbols.

[0054] In one embodiment, remaining - - OFDM symbols within the OFDM symbols are mapped for a PBCH in the SS / PBCH block.

[0055] In one embodiment, a method performed by a user equipment (UE) in a wireless communication system, is provided. The method comprising: identifying a structure for a synchronization signals / physical broadcast channel (SS / PBCH) block, the structure including a first number of orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second number of resource blocks (RBs) in a frequency domain; identifying, from the OFDM symbols, a third number of OFDM symbols mapped for a primary synchronization signal (PSS), where ; identifying, from the OFDM symbols, a fourth number of OFDM symbols mapped for a secondary synchronization signal (SSS), where ; and receiving the SS / PBCH block based on the structure.

[0056] In one embodiment, a method performed by a base station (BS) in a wireless communication system is provided. The method comprising: determining a structure for a synchronization signals / physical broadcast channel (SS / PBCH) block, the structure including a first number of orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second number of resource blocks (RBs) in a frequency domain; determining, from the OFDM symbols, a third number of OFDM symbols mapped for a primary synchronization signal (PSS), where ; and determining, from the OFDM symbols, a fourth number of OFDM symbols mapped for a secondary synchronization signal (SSS), where ; and transmitting the SS / PBCH block based on the structure.

[0057] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0058] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0059] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0060] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0061] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0062] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0063] As used in embodiments of the disclosure, a “~unit” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit” does not always have a meaning limited to software or hardware. The “~unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit” may be either combined into a smaller number of components and a “~unit,” or divided into additional components and a “~unit.” Moreover, the components and “~units” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit” may include one or more processors.

[0064] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0065] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.

[0066] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0067] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0068] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0069] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0070] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0071] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0072] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0073] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0074] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0075] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0076] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0077] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0078] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0079] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0080] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure.

[0081] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0082] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0083] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0084] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0085] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0086] The drawings or flowcharts described below illustrate exemplary methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0087] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0088] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0089] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project　(3GPP) technical specifications (TS) where appropriate.

[0090] Hereinafter, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a BS controller, or a node on a network.

[0091] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0092] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.

[0093] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a UE, and an uplink (UL) refers to a radio link through which a UE transmits a signal to a BS.

[0094] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0095] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0096] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling.

[0097] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0098] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0099] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.FIGS. 1-25, discussed below, and the various, non-limiting embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0100] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. The 5G / NR communication system is implemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60GHz bands, so as to accomplish higher data rates or in lower frequency bands, such as 6 GHz, to enable robust coverage and mobility support. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G / NR communication systems.

[0101] In addition, in 5G / NR communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancelation and the like.

[0102] The discussion of 5G systems and frequency bands associated therewith is for reference as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems, or the frequency bands associated therewith, and embodiments of the present disclosure may be utilized in connection with any frequency band. For example, aspects of the present disclosure may also be applied to deployment of 5G communication systems, 6G, or even later releases which may use terahertz (THz) bands.

[0103] The following documents and standards descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: [REF 1] 3GPP TS 38.211 v18.0.0, “NR; Physical channels and modulation;” [REF 2] 3GPP TS 38.212 v18.0.0, “NR; Multiplexing and channel coding;” [REF 3] 3GPP TS 38.213 v18.0.0, “NR; Physical layer procedures for control;” [REF 4] 3GPP TS 38.214 v18.0.0, “NR; Physical layer procedures for data;” and [REF 5] 3GPP TS 38.331 v18.0.0, “NR; Radio Resource Control (RRC) protocol specification.”

[0104] FIGS. 1-3 below describe various embodiments implemented in wireless communications systems and with the use of OFDM or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of FIGS. 1-3 are not meant to imply physical or architectural limitations to how different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0105] FIG. 1 illustrates an example wireless network 100 according to embodiments of the present disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 could be used without departing from the scope of this disclosure.

[0106] As shown in FIG. 1, the wireless network 100 includes a gNB 101 (e.g., base station, BS), a gNB 102, and a gNB 103. The gNB 101 communicates with the gNB 102 and the gNB 103. The gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0107] The gNB 102 provides wireless broadband access to the network 130 for a first plurality of user equipments (UEs) within a coverage area 120 of the gNB 102. The first plurality of UEs includes a UE 111, which may be located in a small business; a UE 112, which may be located in an enterprise; a UE 113, which may be a WiFi hotspot; a UE 114, which may be located in a first residence; a UE 115, which may be located in a second residence; and a UE 116, which may be a mobile device, such as a cell phone, a wireless laptop, a wireless PDA, or the like. The gNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of the gNB 103. The second plurality of UEs includes the UE 115 and the UE 116. In some embodiments, one or more of the gNBs 101-103 may communicate with each other and with the UEs 111-116 using 5G / NR, long term evolution (LTE), long term evolution-advanced (LTE-A), WiMAX, WiFi, or other wireless communication techniques.

[0108] Depending on the network type, the term “base station” or “BS” can refer to any component (or collection of components) configured to provide wireless access to a network, such as transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G / NR 3rdgeneration partnership project (3GPP) NR, long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms “BS” and “TRP” are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term “user equipment” or “UE” can refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” “receive point,” or “user device.” For the sake of convenience, the terms “user equipment” and “UE” are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer or vending machine).

[0109] The dotted lines show the approximate extents of the coverage areas 120 and 125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending upon the configuration of the gNBs and variations in the radio environment associated with natural and man-made obstructions.

[0110] As described in more detail below, one or more of the UEs 111-116 include circuitry, programing, or a combination thereof for identifying a SS / PBCH block structure(s). In certain embodiments, one or more of the BSs 101-103 include circuitry, programing, or a combination thereof to support SS / PBCH block structure(s).

[0111] Although FIG. 1 illustrates one example of a wireless network, various changes may be made to FIG. 1. For example, the wireless network 100 could include any number of gNBs and any number of UEs in any suitable arrangement. Also, the gNB 101 could communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each gNB 102-103 could communicate directly with the network 130 and provide UEs with direct wireless broadband access to the network 130. Further, the gNBs 101, 102, and / or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0112] FIG. 2 illustrates an example BS (e.g. gNB 102) according to embodiments of the present disclosure. The embodiment of the gNB 102 illustrated in FIG. 2 is for illustration only, and the gNBs 101 and 103 of FIG. 1 could have the same or similar configuration. However, gNBs come in a wide variety of configurations, and FIG. 2 does not limit the scope of this disclosure to any particular implementation of a gNB.

[0113] As shown in FIG. 2, the gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0114] The transceivers 210a-210n receive, from the antennas 205a-205n, incoming radio frequency (RF) signals, such as signals transmitted by UEs in the wireless network 100. The transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0115] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n up-converts the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0116] The controller / processor 225 can include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 could control the reception of uplink (UL) channel signals and the transmission of downlink (DL) channel signals by the transceivers 210a-210n in accordance with well-known principles. The controller / processor 225 could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller / processor 225 could support beam forming or directional routing operations in which outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. Any of a wide variety of other functions could be supported in the gNB 102 by the controller / processor 225.

[0117] The controller / processor 225 is also capable of executing programs and other processes resident in the memory 230, such as providing for SS / PBCH block structure(s). The controller / processor 225 can move data into or out of the memory 230 as required by an executing process.

[0118] The processor 225 may control general operations of the BS 102 according to embodiments of the disclosure. The processor 225 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 225 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 230, individually, collectively or in any combination thereof. Further, the processor 225 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0119] The processor 225 may be electrically, operatively, or communicatively coupled to the transceiver 210a-210n to control the transceiver 210a-210n.

[0120] The processor 225 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 225 may be included in one chip and the other part of the processor 225 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 210a-210n or the memory 230.

[0121] The processor 225 may perform or control or cause an operation of the BS 102 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 225 may control operations of the BS 102 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 102 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 225 may execute a computer program, codes, or instructions stored in the memory 230, so as to control other components of the BS 102 to enable execution of various operations.

[0122] The controller / processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems over a backhaul connection or over a network. The interface 235 could support communications over any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as one supporting 5G / NR, LTE, or LTE-A), the interface 235 could allow the gNB 102 to communicate with other gNBs over a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 could allow the gNB 102 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or transceiver.

[0123] The memory 230 is coupled to the controller / processor 225. Part of the memory 230 could include a RAM, and another part of the memory 230 could include a Flash memory or other ROM.

[0124] The memory 230 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 230 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0125] The memory 230 may be electrically, operatively, or communicatively coupled to the processor 225 and may be accessed by the processor 225.

[0126] The memory 230 may store a computer program, codes, or instructions executable by the processor 225. According to an embodiment, a computer program, codes, or instructions executable by the processor 225 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 230, the processor 225 may perform various functions according to an embodiment of the disclosure.

[0127] According to an embodiment of the disclosure, operations of the BS 102 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 230 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0128] Although FIG. 2 illustrates one example of gNB 102, various changes may be made to FIG. 2. For example, the gNB 102 could include any number of each component shown in FIG. 2. Also, various components in FIG. 2 could be combined, further subdivided, or omitted and additional components could be added according to particular needs.

[0129] FIG. 3 illustrates an example UE 116 according to embodiments of the present disclosure. The embodiment of the UE 116 illustrated in FIG. 3 is for illustration only, and the UEs 111-115 of FIG. 1 could have the same or similar configuration. However, UEs come in a wide variety of configurations, and FIG. 3 does not limit the scope of this disclosure to any particular implementation of a UE.

[0130] As shown in FIG. 3, the UE　116 includes antenna(s) 305, a transceiver(s) 310, and a microphone 320. The UE　116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0131] The transceiver(s) 310 receives from the antenna(s) 305, an incoming RF signal transmitted by a gNB of the wireless network 100. The transceiver(s) 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in the transceiver(s) 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry sends the processed baseband signal to the speaker 330 (such as for voice data) or is processed by the processor 340 (such as for web browsing data).

[0132] TX processing circuitry in the transceiver(s) 310 and / or processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver(s) 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna(s) 305.

[0133] The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 could control the reception of DL channels or signals and the transmission of UL channels or signals by the transceiver(s) 310 in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0134] The processor 340 is also capable of executing other processes and programs resident in the memory 360. For example, the processor 340 may execute processes for identifying a SS / PBCH block structure(s) and receiving the SS / PBCH base thereon as described in embodiments of the present disclosure. The processor 340 can move data into or out of the memory 360 as required by an executing process. In some embodiments, the processor 340 is configured to execute the applications 362 based on the OS 361 or in response to signals received from gNBs or an operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0135] The processor 340 may control general operations of the UE 116 according to embodiments of the disclosure. The processor 340 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 340 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 360, individually, collectively or in any combination thereof. Further, the processor 340 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0136] The processor 340 may be electrically, operatively, or communicatively coupled to the transceiver 310 to control the transceiver 310.

[0137] The processor 340 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 340 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 340 may be included in one chip and the other part of the processor 340 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 310 or the memory 360.

[0138] The processor 340 may perform or control or cause an operation of the UE 116 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 340 may control operations of the UE 116 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 340 may execute a computer program, codes, or instructions stored in the memory 360, so as to control other components of the UE 116 to enable execution of various operations.

[0139] The processor 340 is also coupled to the input 350, which includes, for example, a touchscreen, keypad, etc., and the display 355. The operator of the UE 116 can use the input 350 to enter data into the UE 116. The display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as from web sites.

[0140] The memory 360 is coupled to the processor 340. Part of the memory 360 could include a random-access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).

[0141] The memory 360 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 360 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0142] The memory 360 may be electrically, operatively, or communicatively coupled to the processor 340 and may be accessed by the processor 340.

[0143] The memory 360 may store a computer program, codes, or instructions executable by the processor 340. According to an embodiment, a computer program, codes, or instructions executable by the processor 340 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 360, the processor 340 may perform various functions according to an embodiment of the disclosure.

[0144] According to an embodiment of the disclosure, operations of the UE 116 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 360 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0145] Although FIG. 3 illustrates one example of UE 116, various changes may be made to FIG. 3. For example, various components in FIG. 3 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, the transceiver(s) 310 may include any number of transceivers and signal processing chains and may be connected to any number of antennas. Also, while FIG. 3 illustrates the UE 116 configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices.

[0146] FIG. 4A and FIG. 4B illustrate an example of wireless transmit and receive paths 400 and 450, respectively, according to embodiments of the present disclosure. For example, a transmit path 400 may be described as being implemented in a gNB (such as gNB 102), while a receive path 450 may be described as being implemented in a UE (such as UE 116). However, it will be understood that the receive path 450 can be implemented in a gNB and that the transmit path 400 can be implemented in a UE. In some embodiments, the transmit path 400 and / or receive path 450 is configured to transmit or receive a SS / PBCH block according to a SS / PBCH block structure(s) as described in embodiments of the present disclosure.

[0147] As illustrated in FIG. 4A, the transmit path 400 includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a size N Inverse Fast Fourier Transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an up-converter (UC) 430. The receive path 450 includes a down-converter (DC) 455, a remove cyclic prefix block 460, a S-to-P block 465, a size N Fast Fourier Transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

[0148] In the transmit path 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as a low-density parity check (LDPC) coding), and modulates the input bits (such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. The serial-to-parallel block 410 converts (such as de-multiplexes) the serial modulated symbols to parallel data in order to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB 102 and the UE 116. The size N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate time-domain output signals. The parallel-to-serial block 420 converts (such as multiplexes) the parallel time-domain output symbols from the size N IFFT block 415 in order to generate a serial time-domain signal. The add cyclic prefix block 425 inserts a cyclic prefix to the time-domain signal. The up-converter 430 modulates (such as up-converts) the output of the add cyclic prefix block 425 to a RF frequency for transmission via a wireless channel. The signal may also be filtered at a baseband before conversion to the RF frequency.

[0149] As illustrated in FIG. 4B, the down-converter 455 down-converts the received signal to a baseband frequency, and the remove cyclic prefix block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. The serial-to-parallel block 465 converts the time-domain baseband signal to parallel time-domain signals. The size N FFT block 470 performs an FFT algorithm to generate N parallel frequency-domain signals. The (P-to-S) block 475 converts the parallel frequency-domain signals to a sequence of modulated data symbols. The channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0150] Each of the gNBs 101-103 may implement a transmit path 400 that is analogous to transmitting in the downlink to UEs 111-116 and may implement a receive path 450 that is analogous to receiving in the uplink from UEs 111-116. Similarly, each of UEs 111-116 may implement a transmit path 400 for transmitting in the uplink to gNBs 101-103 and may implement a receive path 450 for receiving in the downlink from gNBs 101-103.

[0151] Each of the components in FIGS. 4A and 4B can be implemented using only hardware or using a combination of hardware and software / firmware. As a particular example, at least some of the components in FIGS. 4A and 4B may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For instance, the FFT block 470 and the IFFT block 415 may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation.

[0152] Furthermore, although described as using FFT and IFFT, this is by way of illustration only and should not be construed to limit the scope of this disclosure. Other types of transforms, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be appreciated that the value of the variable N may be any integer number (such as 1, 2, 3, 4, or the like) for DFT and IDFT functions, while the value of the variable N may be any integer number that is a power of two (such as 1, 2, 4, 8, 16, or the like) for FFT and IFFT functions.

[0153] Although FIGS. 4A and 4B illustrate examples of wireless transmit and receive paths 400 and 450, respectively, various changes may be made to FIGS. 4A and 4B. For example, various components in FIGS. 4A and 4B can be combined, further subdivided, or omitted and additional components can be added according to particular needs. Also, FIGS. 4A and 4B are meant to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architectures can be used to support wireless communications in a wireless network.

[0154] FIG. 5 illustrates an example SS / PBCH block architecture 500 according to embodiments of the present disclosure. For example, SS / PBCH block architecture 500 can be utilized by any of the UEs 111-116 of FIG.1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0155] In NR Rel-15, each SS / PBCH block compromises of four consecutive OFDM symbols, wherein the center 12 resource blocks (RBs) of the first symbol are mapped for PSS, the second and forth symbols are mapped for PBCH, and the third symbol is mapped for both SSS and PBCH. An illustration of the SS / PBCH block composition is shown in FIG. 5. The same SS / PBCH composition is applied to supported carrier frequency ranges in NR, which spans from 0.41 GHz to 7.125 GHz as Frequency Range 1 (FR1), and spans from 24.25 to 52.6 GHz as Frequency Range 2 (FR2). In every RB mapped for PBCH, 3 out of the 12 resource elements (REs) are mapped for the demodulation reference signal (DM-RS) of PBCH, wherein the 3 REs are uniformly distributed in the RB and the starting location of the first RE is based on cell identity (ID).

[0156] Embodiments of the present disclosure recognize that, for new generation of wireless communication to save the energy of a base station, the one shot detection performance for SS / PBCH block can be enhanced and the time and frequency domain structure for SS / PBCH block can be enhanced accordingly.

[0157] This disclosure provides for a SS / PBCH block structure. In various embodiments, the following aspects are included in the disclosure:

[0158] ● SSB Structure with 14 symbols

[0159] ● SSB Structure with 13 symbols

[0160] ● SSB Structure with 12 symbols

[0161] ● SSB Structure with 11 symbols

[0162] ● Example UE procedure

[0163] In one embodiment, one slot can include at least one SSB including at least synchronization signal(s). The SSB can also be multiplexed with a physical broadcast channel (PBCH).

[0164] For one example, a SSB can include OFDM symbols in the time domain. The OFDM symbols of the SSB can be indexed from 0 to -1. For one instance, the OFDM symbols can be consecutive in the time domain. For another instance, the OFDM symbols can be consecutive downlink OFDM symbols in the time domain.

[0165] ● Within the OFDM symbols of the SSB, number of the OFDM symbols are mapped for a first type of signal(s) / channel(s), and the set of indexes of the number of the OFDM symbols can be denoted as .

[0166] ● Within the OFDM symbols of the SSB, number of the OFDM symbols are mapped for a second type of signal(s) / channel(s), and the set of indexes of the number of the OFDM symbols can be denoted as .

[0167] ● Within the OFDM symbols of the SSB, number of the OFDM symbols are mapped for a third type of signal(s) / channel(s), and the set of indexes of the number of the OFDM symbols can be denoted as .

[0168] In one example, the OFDM symbol for the first type of signal(s) / channel(s) can at least include a primary synchronization signal (PSS).

[0169] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for PSS is mapped to the center 127 subcarriers within the subcarriers (e.g., mapped to subcarrier # to # ), with the remaining subcarriers as empty.

[0170] ● For another sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for PSS is mapped to the center 127 subcarriers within the center 12 RBs within the RBs (e.g., mapped to subcarrier # to # ), with the remaining RBs mapped for PBCH.

[0171] In one example, the OFDM symbol for the second type of signal(s) / channel(s) can at least include a SSS.

[0172] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for SSS is mapped to the center 127 subcarriers within the subcarriers (e.g., mapped to subcarrier # to # ), with the remaining subcarriers as empty.

[0173] ● For another sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for SSS is mapped to the center 127 subcarriers within the center 12 RBs within the RBs (e.g., mapped to subcarrier # to # ), with the remaining RBs mapped for PBCH.

[0174] In one example, the OFDM symbol for the third type of signal(s) / channel(s) can at least include a PBCH, e.g., including a demodulation reference signal (DM-RS) of the PBCH, if supported.

[0175] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers).

[0176] For one example, can be pre-determined, e.g., as 11, or as 12, or as 18, or as 20, or as 22, or as 24. For one further evaluation, at least for the UE performing an initial cell search procedure.

[0177] For one example, can be configured by the base station, e.g., using higher layer parameter.

[0178] For one example, can be indicated by the base station, e.g., using control information.

[0179] For one example, can be pre-determined, e.g., according to one example of this disclosure. For one further evaluation, at least for the UE performing an initial cell search procedure.

[0180] For one example, can be configured by the base station, e.g., using higher layer parameter.

[0181] For one example, can be indicated by the base station, e.g., using control information.

[0182] For one example, the SSB structure can be pre-determined, e.g., according to one example of this disclosure. For instance, the SSB structure can be determined based on at least one of , or , or , or , or .

[0183] For one example, the SSB structure can be configured by the base station. For one instance, at least one of , or , or , or , or can be provided by a higher layer parameter. For one instance, at least one of the example SSB structure in the disclosure can be configured by the base station.

[0184] For one example, the SSB structure can be indicated by the base station. For one instance, at least one of , or , or , or , or can be indicated by control information. For one instance, at least one of the example SSB structure in the disclosure can be indicated by control information.

[0185] FIG. 6 illustrates diagrams of example SSB architectures 600 according to embodiments of the present disclosure. For example, SSB architectures 600 can be received by any of the UEs 111-116 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0186] FIG. 7 illustrates diagrams of example SSB architectures 700 according to embodiments of the present disclosure. For example, SSB architectures 700 can be received by any of the UEs 111-116 of FIG. 1, such as the UE 111. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0187] In one sub-embodiment, = 14.

[0188] For a first example (e.g., 601 in FIG. 6) of this sub-embodiment, = 3, = {0, 1, 2}, = 3, = {5, 8, 11}, = 8, = {3, 4, 6, 7, 9, 10, 12, 13}.

[0189] For a second example (e.g., 602 in FIG. 6) of this sub-embodiment, = 3, = {0, 1, 2}, = 3, = {3, 4, 5}, = 8, = {6, 7, 8, 9, 10, 11, 12, 13}.

[0190] For a third example (e.g., 603 in FIG. 6) of this sub-embodiment, = 2, = {0, 2}, = 2, = {1,3}, = 10, = {4, 5, 6, 7, 8, 9, 10, 11, 12, 13}.

[0191] For a fourth example (e.g., 604 in FIG. 6) of this sub-embodiment, =2, = {0, 1}, = 2, = {2, 3}, = 10, = {4, 5, 6, 7, 8, 9, 10, 11, 12, 13}.

[0192] For a fifth example (e.g., 605 in FIG. 6) of this sub-embodiment, = 2, = {6, 7}, = 2, = {0, 1}, = 10, = {2, 3, 4, 5, 8, 9, 10, 11, 12, 13}.

[0193] For a sixth example (e.g., 606 in FIG. 6) of this sub-embodiment, = 3, = {0, 1, 2}, = 2, = {3, 4}, = 9, = {5, 6, 7, 8, 9, 10, 11, 12, 13}.

[0194] For a seventh example (e.g., 607 in FIG. 6) of this sub-embodiment, = 3, = {0, 2, 4}, = 2, = {1, 3}, = 9, = {5, 6, 7, 8, 9, 10, 11, 12, 13}.

[0195] For a eighth example (e.g., 608 in FIG. 6) of this sub-embodiment, = 3, = {0, 1, 2}, = 2, = {7, 8}, = 9, = {3, 4, 5, 6, 9, 10, 11, 12, 13}.

[0196] For a ninth example (e.g., 701 in FIG. 7) of this sub-embodiment, = 3, = {1, 2, 3}, = 3, = {6, 9, 12}, = 8, = {0, 4, 5, 7, 8, 10, 11, 13}.

[0197] For a tenth example (e.g., 702 in FIG. 7) of this sub-embodiment, = 3, = {1, 2, 3}, = 3, = {4, 5, 6}, = 8, = {0, 7, 8, 9, 10, 11, 12, 13}.

[0198] For an eleventh example (e.g., 703 in FIG. 7) of this sub-embodiment, = 2, = {1, 3}, = 2, = {2, 4}, = 10, = {0, 5, 6, 7, 8, 9, 10, 11, 12, 13}.

[0199] For a twelfth example (e.g., 704 in FIG. 7) of this sub-embodiment, =2, = {1, 2}, = 2, = {3, 4}, = 10, = {0, 5, 6, 7, 8, 9, 10, 11, 12, 13}.

[0200] For a thirteenth example (e.g., 705 in FIG. 7) of this sub-embodiment, = 2, = {7, 8}, = 2, = {1, 2}, = 10, = {0, 3, 4, 5, 6, 9, 10, 11, 12, 13}.

[0201] For a fourteenth example (e.g., 706 in FIG. 7) of this sub-embodiment, = 3, = {1, 2, 3}, = 2, = {4, 5}, = 9, = {0, 6, 7, 8, 9, 10, 11, 12, 13}.

[0202] For a fifteenth example (e.g., 707 in FIG. 7) of this sub-embodiment, = 3, = {1, 3, 5}, = 2, = {2, 4}, = 9, = {0, 6, 7, 8, 9, 10, 11, 12, 13}.

[0203] For a sixteenth example (e.g., 708 in FIG. 7) of this sub-embodiment, = 3, = {1, 2, 3}, = 2, = {8, 9}, = 9, = {0, 4, 5, 6, 7, 10, 11, 12, 13}.

[0204] In one further evaluation for the examples of this sub-embodiment, the SSB with 14 OFDM symbols can be mapped from a first OFDM symbol in a slot, e.g., #0 of the SSB is aligned with #0 of a slot. For one instance, the mapping can be applicable for all slots including the SSB.

[0205] FIG. 8 illustrates diagrams of example SSB architectures 800 according to embodiments of the present disclosure. For example, SSB architectures 800 can be received by any of the UEs 111-116 of FIG. 1, such as the UE 112. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0206] FIG. 9 illustrates diagrams of example SSB architectures 900 according to embodiments of the present disclosure. For example, SSB architectures 900 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 113. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0207] In one sub-embodiment, = 13.

[0208] For a first example (e.g., 801 in FIG. 8 ) of this sub-embodiment, = 3, = {0, 1, 2}, = 3, = {5, 8, 11}, = 7, = {3, 4, 6, 7, 9, 10, 12}.

[0209] For a second example (e.g., 802 in FIG. 8 ) of this sub-embodiment, = 3, = {0, 1, 2}, = 3, = {3, 4, 5}, = 7, = {6, 7, 8, 9, 10, 11, 12}.

[0210] For a third example (e.g., 803 in FIG. 8) of this sub-embodiment, = 2, = {0, 2}, = 2, = {1,3}, = 9, = {4, 5, 6, 7, 8, 9, 10, 11, 12}.

[0211] For a fourth example (e.g., 804 in FIG. 8) of this sub-embodiment, =2, = {0, 1}, = 2, = {2, 3}, = 9, = {4, 5, 6, 7, 8, 9, 10, 11, 12}.

[0212] For a fifth example (e.g., 805 in FIG. 8) of this sub-embodiment, = 2, = {6, 7}, = 2, = {0, 1}, = 9, = {2, 3, 4, 5, 8, 9, 10, 11, 12}.

[0213] For a sixth example (e.g., 806 in FIG. 8) of this sub-embodiment, = 3, = {0, 1, 2}, = 2, = {3, 4}, = 8, = {5, 6, 7, 8, 9, 10, 11, 12}.

[0214] For a seventh example (e.g., 807 in FIG. 8) of this sub-embodiment, = 3, = {0, 2, 4}, = 2, = {1, 3}, = 8, = {5, 6, 7, 8, 9, 10, 11, 12}.

[0215] For a eighth example (e.g., 808 in FIG. 8) of this sub-embodiment, = 3, = {0, 1, 2}, = 2, = {7, 8}, = 8, = {3, 4, 5, 6, 9, 10, 11, 12}.

[0216] For a ninth example (e.g., 901 in FIG. 9) of this sub-embodiment, = 3, = {1, 2, 3}, = 3, = {6, 9, 12}, = 7, = {0, 4, 5, 7, 8, 10, 11}.

[0217] For a tenth example (e.g., 902 in FIG. 9) of this sub-embodiment, = 3, = {1, 2, 3}, = 3, = {4, 5, 6}, = 7, = {0, 7, 8, 9, 10, 11, 12}.

[0218] For a eleventh example (e.g., 903 in FIG. 9) of this sub-embodiment, = 2, = {1, 3}, = 2, = {2, 4}, = 9, = {0, 5, 6, 7, 8, 9, 10, 11, 12}.

[0219] For a twelfth example (e.g., 904 in FIG. 9) of this sub-embodiment, =2, = {1, 2}, = 2, = {3, 4}, = 9, = {0, 5, 6, 7, 8, 9, 10, 11, 12}.

[0220] For a thirteenth example (e.g., 905 in FIG. 9) of this sub-embodiment, = 2, = {7, 8}, = 2, = {1, 2}, = 9, = {0, 3, 4, 5, 6, 9, 10, 11, 12}.

[0221] For a fourteenth example (e.g., 906 in FIG. 9) of this sub-embodiment, = 3, = {1, 2, 3}, = 2, = {4, 5}, = 8, = {0, 6, 7, 8, 9, 10, 11, 12}.

[0222] For a fifteenth example (e.g., 907 in FIG. 9) of this sub-embodiment, = 3, = {1, 3, 5}, = 2, = {2, 4}, = 8, = {0, 6, 7, 8, 9, 10, 11, 12}.

[0223] For a sixteenth example (e.g., 908 in FIG. 9) of this sub-embodiment, = 3, = {1, 2, 3}, = 2, = {8, 9}, = 8, = {0, 4, 5, 6, 7, 10, 11, 12}.

[0224] In one further evaluation for the examples of this sub-embodiment, the SSB with 13 OFDM symbols can be mapped from a first OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #0 of a slot. The remaining one symbol of this slot can be mapped for a CORESET and / or a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0225] In one further evaluation for the examples of this sub-embodiment, the SSB with 13 OFDM symbols can be mapped from a second OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #1 of a slot. The remaining one symbol of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0226] In one further evaluation for the examples of this sub-embodiment, the OFDM symbol that is used as a first OFDM symbol of the SSB with 13 OFDM symbols configured by the base station. For instance, the candidate value can be from {0, 1}. The remaining one symbol of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0227] FIG. 10 illustrates diagrams of example SSB architectures 1000 according to embodiments of the present disclosure. For example, SSB architectures 1000 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 114. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0228] FIG. 11 illustrates diagrams of example SSB architectures 1100 according to embodiments of the present disclosure. For example, SSB architectures 1100 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 115. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0229] In one sub-embodiment, = 12.

[0230] For a first example (e.g., 1001 in FIG. 10) of this sub-embodiment, = 3, = {0, 1, 2}, = 3, = {5, 8, 11}, = 6, = {3, 4, 6, 7, 9, 10}.

[0231] For a second example (e.g., 1002 in FIG. 10 ) of this sub-embodiment, = 3, = {0, 1, 2}, = 3, = {3, 4, 5}, = 6, = {6, 7, 8, 9, 10, 11}.

[0232] For a third example (e.g., 1003 in FIG. 10) of this sub-embodiment, = 2, = {0, 2}, = 2, = {1,3}, = 8, = {4, 5, 6, 7, 8, 9, 10, 11}.

[0233] For a fourth example (e.g., 1004 in FIG. 10) of this sub-embodiment, =2, = {0, 1}, = 2, = {2, 3}, = 8, = {4, 5, 6, 7, 8, 9, 10, 11}.

[0234] For a fifth example (e.g., 1005 in FIG. 10) of this sub-embodiment, = 2, = {6, 7}, = 2, = {0, 1}, = 8, = {2, 3, 4, 5, 8, 9, 10, 11}.

[0235] For a sixth example (e.g., 1006 in FIG. 10) of this sub-embodiment, = 3, = {0, 1, 2}, = 2, = {3, 4}, = 7, = {5, 6, 7, 8, 9, 10, 11}.

[0236] For a seventh example (e.g., 1007 in FIG. 10) of this sub-embodiment, = 3, = {0, 2, 4}, = 2, = {1, 3}, = 7, = {5, 6, 7, 8, 9, 10, 11}.

[0237] For a eighth example (e.g., 1008 in FIG. 10) of this sub-embodiment, = 3, = {0, 1, 2}, = 2, = {7, 8}, = 7, = {3, 4, 5, 6, 9, 10, 11}.

[0238] For a ninth example (e.g., 1101 in FIG. 11) of this sub-embodiment, = 3, = {1, 2, 3}, = 3, = {6, 9, 11}, = 6, = {0, 4, 5, 7, 8, 10}.

[0239] For a tenth example (e.g., 1102 in FIG. 11) of this sub-embodiment, = 3, = {1, 2, 3}, = 3, = {4, 5, 6}, = 6, = {0, 7, 8, 9, 10, 11}.

[0240] For a eleventh example (e.g., 1103 in FIG. 11) of this sub-embodiment, = 2, = {1, 3}, = 2, = {2, 4}, = 8, = {0, 5, 6, 7, 8, 9, 10, 11}.

[0241] For a twelfth example (e.g., 1104 in FIG. 11) of this sub-embodiment, =2, = {1, 2}, = 2, = {3, 4}, = 8, = {0, 5, 6, 7, 8, 9, 10, 11}.

[0242] For a thirteenth example (e.g., 1105 in FIG. 11) of this sub-embodiment, = 2, = {7, 8}, = 2, = {1, 2}, = 8, = {0, 3, 4, 5, 6, 9, 10, 11}.

[0243] For a fourteenth example (e.g., 1106 in FIG. 11) of this sub-embodiment, = 3, = {1, 2, 3}, = 2, = {4, 5}, = 7, = {0, 6, 7, 8, 9, 10, 11}.

[0244] For a fifteenth example (e.g., 1107 in FIG. 11) of this sub-embodiment, = 3, = {1, 3, 5}, = 2, = {2, 4}, = 7, = {0, 6, 7, 8, 9, 10, 11}.

[0245] For a sixteenth example (e.g., 1108 in FIG. 11) of this sub-embodiment, = 3, = {1, 2, 3}, = 2, = {8, 9}, = 7, = {0, 4, 5, 6, 7, 10, 11}.

[0246] In one further evaluation for the examples of this sub-embodiment, the SSB with 12 OFDM symbols can be mapped from a first OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #0 of a slot. The remaining two symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0247] In one further evaluation for the examples of this sub-embodiment, the SSB with 12 OFDM symbols can be mapped from a second OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #1 of a slot. The remaining two symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0248] In one further evaluation for the examples of this sub-embodiment, the SSB with 12 OFDM symbols can be mapped from a second OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #2 of a slot. The remaining two symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0249] In one further evaluation for the examples of this sub-embodiment, the OFDM symbol that is used as a first OFDM symbol of the SSB with 12 OFDM symbols configured by the base station. For instance, the candidate value can be from {0, 1, 2} or its subset. The remaining two symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0250] FIG. 12 illustrates diagrams of example SSB architectures 1200 according to embodiments of the present disclosure. For example, SSB architectures 1200 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 116. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0251] FIG. 13 illustrates diagrams of example SSB architectures 1300 according to embodiments of the present disclosure. For example, SSB architectures 1300 can be utilized by the UE 116 of FIG. 3. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0252] In one sub-embodiment, = 11.

[0253] For a first example (e.g., 1201 in FIG. 12) of this sub-embodiment, = 3, = {0, 1, 2}, = 3, = {5, 8, 10}, = 5, = {3, 4, 6, 7, 9}.

[0254] For a second example (e.g., 1202 in FIG. 12 ) of this sub-embodiment, = 3, = {0, 1, 2}, = 3, = {3, 4, 5}, = 5, = {6, 7, 8, 9, 10}.

[0255] For a third example (e.g., 1203 in FIG. 12) of this sub-embodiment, = 2, = {0, 2}, = 2, = {1,3}, = 7, = {4, 5, 6, 7, 8, 9, 10}.

[0256] For a fourth example (e.g., 1204 in FIG. 12) of this sub-embodiment, =2, = {0, 1}, = 2, = {2, 3}, = 7, = {4, 5, 6, 7, 8, 9, 10}.

[0257] For a fifth example (e.g., 1205 in FIG. 12) of this sub-embodiment, = 2, = {6, 7}, = 2, = {0, 1}, = 7, = {2, 3, 4, 5, 8, 9, 10}.

[0258] For a sixth example (e.g., 1206 in FIG. 12) of this sub-embodiment, = 3, = {0, 1, 2}, = 2, = {3, 4}, = 6, = {5, 6, 7, 8, 9, 10}.

[0259] For a seventh example (e.g., 1207 in FIG. 12) of this sub-embodiment, = 3, = {0, 2, 4}, = 2, = {1, 3}, = 6, = {5, 6, 7, 8, 9, 10}.

[0260] For a eighth example (e.g., 1208 in FIG. 12) of this sub-embodiment, = 3, = {0, 1, 2}, = 2, = {7, 8}, = 6, = {3, 4, 5, 6, 9, 10}.

[0261] For a ninth example (e.g., 1301 in FIG. 13) of this sub-embodiment, = 3, = {1, 2, 3}, = 3, = {5, 8, 10}, = 5, = {0, 4, 6, 7, 9}.

[0262] For a tenth example (e.g., 1302 in FIG. 13) of this sub-embodiment, = 3, = {1, 2, 3}, = 3, = {4, 5, 6}, = 5, = {0, 7, 8, 9, 10}.

[0263] For a eleventh example (e.g., 1303 in FIG. 13) of this sub-embodiment, = 2, = {1, 3}, = 2, = {2, 4}, = 7, = {0, 5, 6, 7, 8, 9, 10}.

[0264] For a twelfth example (e.g., 1304 in FIG. 13) of this sub-embodiment, =2, = {1, 2}, = 2, = {3, 4}, = 7, = {0, 5, 6, 7, 8, 9, 10}.

[0265] For a thirteenth example (e.g., 1305 in FIG. 13) of this sub-embodiment, = 2, = {7, 8}, = 2, = {1, 2}, = 7, = {0, 3, 4, 5, 6, 9, 10}.

[0266] For a fourteenth example (e.g., 1306 in FIG. 13) of this sub-embodiment, = 3, = {1, 2, 3}, = 2, = {4, 5}, = 6, = {0, 6, 7, 8, 9, 10}.

[0267] For a fifteenth example (e.g., 1307 in FIG. 13) of this sub-embodiment, = 3, = {1, 3, 5}, = 2, = {2, 4}, = 6, = {0, 6, 7, 8, 9, 10}.

[0268] For a sixteenth example (e.g., 1308 in FIG. 13) of this sub-embodiment, = 3, = {1, 2, 3}, = 2, = {8, 9}, = 6, = {0, 4, 5, 6, 7, 10}.

[0269] In one further evaluation for the examples of this sub-embodiment, the SSB with 11 OFDM symbols can be mapped from a first OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #0 of a slot. The remaining three symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0270] In one further evaluation for the examples of this sub-embodiment, the SSB with 11 OFDM symbols can be mapped from a second OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #1 of a slot. The remaining three symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0271] In one further evaluation for the examples of this sub-embodiment, the SSB with 11 OFDM symbols can be mapped from a second OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #2 of a slot. The remaining three symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0272] In one further evaluation for the examples of this sub-embodiment, the SSB with 11 OFDM symbols can be mapped from a second OFDM symbol within a slot, e.g., #0 of the SSB is aligned with #3 of a slot. The remaining three symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0273] In one further evaluation for the examples of this sub-embodiment, the OFDM symbol that is used as a first OFDM symbol of the SSB with 11 OFDM symbols configured by the base station. For instance, the candidate value can be from {0, 1, 2, 3} or its subset. The remaining two symbols of this slot can be mapped for a CORESET and / or a HARQ-ACK feedback. For one instance, the mapping can be applicable for all slots including the SSB.

[0274] FIG. 14 illustrates a flowchart of an example UE procedure 1400 for receiving signal(s) / channel(s) according to embodiments of the present disclosure. For example, procedure 1400 can be performed by any of the UEs 111-116 of FIG.1 and a corresponding or analogous process may be performed by the any of the BSs 101-103 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0275] In one embodiment, an example UE procedure for receiving a SSB is shown in FIG. 14. The procedure begins in 1401, a UE determines a number of RBs for a SSB. In 1402, the UE determines a number of OFDM symbols for the SSB. In 1403, the UE determines a first number and corresponding locations of OFDM symbols for a first type of signal(s) / channel(s) included in the SSB. For example, the type of signal(s) / channel(s) may be PSS, SSS, or PBCH. In 1404, the UE determines a second number and corresponding locations of OFDM symbols for a second type of signal(s) / channel(s) included in the SSB. For example, the type of signal(s) / channel(s) may be PSS, SSS, or PBCH. In 1405, the UE determines a third number and corresponding locations of OFDM symbols for a third type of signal(s) / channel(s) included in the SSB. For example, the type of signal(s) / channel(s) may be PSS, SSS, or PBCH. In 1406, the UE receives the first, second, and third type of signal(s) / channel(s) included in the SSB.

[0276] This disclosure provides for a SS / PBCH block structure with large bandwidth, wherein signal(s) and / or channel(s) within the SS / PBCH block can be frequency division multiplexed (FDMed). In various embodiments, the following aspects are included in the disclosure:

[0277] ● SSB Structure with Short PSS / SSS

[0278] ● SSB Structure with Long PSS / SSS

[0279] ● SSB Structure with Long PSS and Short SSS

[0280] ● SSB Structure with Short PSS and Long SSS

[0281] ● Example UE procedure

[0282] In one embodiment, one slot can include at least one SSB. For one further evaluation, the SSB can also be multiplexed with PBCH.

[0283] For one example, a SSB can include RBs in the frequency domain. The RBs of the SSB can be indexed from 0 to -1 .

[0284] For another example, a SSB can include OFDM symbols in the time domain. The OFDM symbols of the SSB can be indexed from 0 to -1.

[0285] The following notations are used for this embodiment:

[0286] ● : a number of RBs in the frequency domain of a SSB, i.e., the bandwidth of the OFDM symbol(s) of a SSB.

[0287] ● : a number of OFDM symbols in the time domain of a SSB.

[0288] ● : a number of a first type of signal(s) / channel(s) within the SSB.

[0289] ● : a number of a second type of signal(s) / channel(s) within the SSB.

[0290] ● : a number of a third type of signal(s) / channel(s) within the SSB.

[0291] ● : the set of indexes of a first type of signal(s) / channel(s) within the SSB. An index of a first type of signal(s) / channel(s) has two dimensions (e.g., denoted as ), including a time domain index (e.g., ) denoting the OFDM symbol where the first type of signal(s) / channel(s) is mapped to, and a frequency domain index (e.g., ) denoting the lowest RB index where the first type of signal(s) / channel(s) is mapped from.

[0292] ● : the set of indexes of a second type of signal(s) / channel(s) within the SSB. An index of a first type of signal(s) / channel(s) has two dimensions (e.g., denoted as ), including a time domain index (e.g., ) denoting the OFDM symbol where the first type of signal(s) / channel(s) is mapped to, and a frequency domain index (e.g., ) denoting the lowest RB index where the first type of signal(s) / channel(s) is mapped from.

[0293] ● : the set of indexes of a third type of signal(s) / channel(s) within the SSB. An index of a first type of signal(s) / channel(s) has two dimensions (e.g., denoted as ), including a time domain index (e.g., ) denoting the OFDM symbol where the first type of signal(s) / channel(s) is mapped to, and a frequency domain index (e.g., ) denoting the lowest RB index where the first type of signal(s) / channel(s) is mapped from.

[0294] ● : a number of RBs in the frequency domain wherein a primary synchronization signal (PSS) is mapped.

[0295] ● : a number of RBs in the frequency domain wherein a secondary synchronization signal (SSS) is mapped.

[0296] In one example, the OFDM symbol for the first type of signal(s) / channel(s) can at least include a primary synchronization signal (PSS).

[0297] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for PSS is mapped to the center 127 subcarriers within the subcarriers, with the remaining subcarriers as empty.

[0298] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for PSS is mapped to the center 127 subcarriers within the center 12 RBs within the RBs, with the remaining RBs mapped for another signal or channel in the SSB, e.g., SSS or PBCH.

[0299] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for PSS is mapped to the upper and / or lower 127 subcarriers within the subcarriers, with the remaining subcarriers as empty.

[0300] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for PSS is mapped to the upper and / or lower 127 subcarriers within the subcarriers, with the remaining RBs mapped for another signal or channel in the SSB, e.g., SSS or PBCH.

[0301] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for PSS is mapped to the center 255 subcarriers within the subcarriers, with the remaining subcarriers as empty.

[0302] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for PSS is mapped to the center 255 subcarriers within the subcarriers, with the remaining RBs mapped for another signal or channel in the SSB, e.g., SSS or PBCH.

[0303] In one example, the OFDM symbol for the second type of signal(s) / channel(s) can at least include a SSS.

[0304] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for SSS is mapped to the center 127 subcarriers within the subcarriers, with the remaining subcarriers as empty.

[0305] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for SSS is mapped to the center 127 subcarriers within the center 12 RBs within the RBs, with the remaining RBs mapped for another signal or channel in the SSB, e.g., PSS or PBCH.

[0306] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for SSS is mapped to the upper and / or lower 127 subcarriers within the subcarriers, with the remaining subcarriers as empty.

[0307] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for SSS is mapped to the upper and / or lower 127 subcarriers within the subcarriers, with the remaining RBs mapped for another signal or channel in the SSB, e.g., PSS or PBCH.

[0308] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for SSS is mapped to the center 255 subcarriers within the subcarriers, with the remaining subcarriers as empty.

[0309] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers), and a sequence for SSS is mapped to the center 255 subcarriers within the subcarriers, with the remaining RBs mapped for another signal or channel in the SSB, e.g., PSS or PBCH.

[0310] In one example, the OFDM symbol for the third type of signal(s) / channel(s) can at least include a PBCH) e.g., including a demodulation reference signal (DM-RS) of the PBCH, if supported.

[0311] ● For one sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers).

[0312] ● For yet another sub-example, the bandwidth of the OFDM symbol can be RBs (e.g., subcarriers).

[0313] For one example, can be pre-determined, e.g., as 12, or as 18, or as 20, or as 24.

[0314] For one example, can be configured by the base station, e.g., using higher layer parameter.

[0315] For one example, can be indicated by the base station, e.g., using control information.

[0316] For one example, can be pre-determined, e.g., as 14, or as 13, or as 12, or as 11, or as 10, or as 9, or as 8, or as 7, or as 6, or as 5.

[0317] For one example, can be configured by the base station, e.g., using higher layer parameter.

[0318] For one example, can be indicated by the base station, e.g., using control information.

[0319] For one example, can be predefined based on the bandwidth of a SSB, e.g., can be predefined as 12 RBs (e.g., when is 12 and / or 24 RBs).

[0320] For one example, can be predefined as 24 RBs (e.g., when is 24 RBs).

[0321] For one example, can be predefined as 6 RBs.

[0322] For one example, can be predefined based on the bandwidth of a SSB, e.g., can be predefined as 12 RBs (e.g., when is 12 and / or 24 RBs).

[0323] For one example, can be predefined as 24 RBs (e.g., when is 24 RBs).

[0324] For one example, can be predefined as 6 RBs.

[0325] For one example, the SSB structure can be pre-determined, e.g., according to one example of this disclosure. For instance, the SSB structure can be determined based on at least one of , or , or , or , or , or , or .

[0326] For one example, the SSB structure can be configured by the base station. For one instance, at least one of , or , or , or , or , or , or can be provided by a higher layer parameter. For another instance, at least one of the example SSB structure in the disclosure can be configured by the base station.

[0327] For one example, the SSB structure can be indicated by the base station. For one instance, at least one of , or , or , or , or , or , or can be indicated by control information. For another instance, at least one of the example SSB structure in the disclosure can be indicated by control information.

[0328] FIG. 15 illustrates diagrams of example SSB architectures 1500 according to embodiments of the present disclosure. For example, SSB architectures 1500 can be utilized by any of the UEs 111-116 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0329] FIG. 16 illustrates diagrams of example SSB architectures 1600 according to embodiments of the present disclosure. For example, SSB architectures 1600 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 111. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0330] FIG. 17 illustrates diagrams of example SSB architectures 1700 according to embodiments of the present disclosure. For example, SSB architectures 1700 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 112. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0331] FIG. 18 illustrates diagrams of example SSB architectures 1800 according to embodiments of the present disclosure. For example, SSB architectures 1800 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 113. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0332] In one sub-embodiment, . For one example, =12, and / or =12. For another example, =11, and / or =11.

[0333] For a first example (e.g., 1501 in FIG. 15) of this sub-embodiment, = 2, = {(0, 0), (1, )}, = 2, = {(5, 0), (8, 0)}, = 14, = {(0, ), (1, 0), (2, 0), (3, 0), (4, 0), (5, ), (6, 0), ……, ( , 0)}.

[0334] For a second example (e.g., 1502 in FIG. 15) of this sub-embodiment, = 2, = {(0, 0), (1, )}, = 2, = {(0, ), (1, 0)}, = 12, = {(2, 0), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0335] For a third example (e.g., 1503 in FIG. 15) of this sub-embodiment, = 2, = {(0, 0), (1, 0)}, = 2, = {(0, ), (1, )}, = 12, = {(2, 0), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0336] For a fourth example (e.g., 1504 in FIG. 15) of this sub-embodiment, =2, = {(0, 0), (2, 0)}, = 2, = {(1, ), (3, )}, = 14, = {(0, ), (1, 0), (2, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0337] For a fifth example (e.g., 1505 in FIG. 15) of this sub-embodiment, = 2, = {(1, ), (2, )}, = 2, = {(0, 0), (0, )}, = 15, = {(1, 0), (1, ), (2, 0), (2, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0338] For a sixth example (e.g., 1506 in FIG. 15) of this sub-embodiment, = 3, = {(0, 0), (0, ), (2, )}, = 2, = {(1, ), (3, )}, =16 , = {(1, 0), (1, ), (2, 0), (2, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0339] For a seventh example (e.g., 1507 in FIG. 15) of this sub-embodiment, = 2, = {(0, 0), (2, )}, = 2, = {(1, ), (3, )}, =16 , = {(0, ), (1, 0), (1, ), (2, 0), (2, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0340] For a eighth example (e.g., 1508 in FIG. 15) of this sub-embodiment, = 2, = {(0, ), (2, )}, = 2, = {(1, 0), (1, )}, = 15, = {(0, 0), (0, ), (2, 0), (2, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0).

[0341] For a ninth example (e.g., 1601 in FIG. 16) of this sub-embodiment, = 2, = {(1, ), (2, )}, = 2, = {(0, 0), (0, )}, =15 , = {(1, 0), (1, ), (2, 0), (2, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0342] For a tenth example (e.g., 1602 in FIG. 16) of this sub-embodiment, = 3, = {(0, ), (1, ), (2, 0)}, = 2, = {(0, 0), (2, ), }, = 13 , = {(1, 0), (1, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0343] For a eleventh example (e.g., 1603 in FIG. 16) of this sub-embodiment, = 3, = {(0, ), (2, ), (3, 0)}, = 2, = {(0, 0), (1, )}, = 15, = {(1, 0), (1, ), (2, 0), (2, ), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0344] For a twelfth example (e.g., 1604 in FIG. 16) of this sub-embodiment, =2, = {(0, 0), (0, )}, = 2, = {(1, 0), (1, )}, = 12, = {(2, 0), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0345] For a thirteenth example (e.g., 1605 in FIG. 16) of this sub-embodiment, = 3, = {(1, 0), (2, 0), (2, )}, = 3, = {(0, 0), (0, ), (1, )}, =11 , = {(3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0346] For a fourteenth example (e.g., 1606 in FIG. 16) of this sub-embodiment, = 3, = {(0, 0), (0, ), (1, )}, = 3, = {(1, 0), (2, 0), (2, )}, =11 , = {(3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0).

[0347] For a fifteenth example (e.g., 1701 in FIG. 17) of this sub-embodiment, = 2, = {(1, 0), (2, )}, = 2, = {(5, 0), (8, 0)}, = 14, = {(0, 0), (1, ), (2, 0), (3, 0), (4, 0), (5, ), (6, 0), ……, ( , 0)}.

[0348] For a sixteenth example (e.g., 1702 in FIG. 17) of this sub-embodiment, = 2, = {(1, 0), (2, )}, = 2, = {(1, ), (2, 0)}, = 12, = {(0, 0), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0349] For a seventeenth example (e.g., 1703 in FIG. 17) of this sub-embodiment, = 2, = {(1, 0), (2, 0)}, = 2, = {(1, ), (2, )}, = 12, = {(0, 0), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0350] For a eighteenth example (e.g., 1704 in FIG. 17) of this sub-embodiment, =2, = {(1, 0), (3, 0)}, = 2, = {(2, ), (4, )}, = 14, = {(0, 0), (1, ), (2, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0351] For a nineteenth example (e.g., 1705 in FIG. 17) of this sub-embodiment, = 2, = {(2, ), (3, )}, = 2, = {(1, 0), (1, )}, = 15, = {(0, 0), (2, 0), (2, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0352] For a twentieth example (e.g., 1706 in FIG. 17) of this sub-embodiment, = 3, = {(1, 0), (1, ), (3, )}, = 2, = {(2, ), (4, )}, =16 , = {(0, 0), (2, 0), (2, ), (3, 0), (3, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0353] For a twenty-first example (e.g., 1707 in FIG. 17) of this sub-embodiment, = 2, = {(1, 0), (3, )}, = 2, = {(2, ), (4, )}, =16 , = {(0, 0), (1, ), (2, 0), (2, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0354] For a twenty-second example (e.g., 1708 in FIG. 17) of this sub-embodiment, = 2, = {(1, ), (3, )}, = 2, = {(2, 0), (2, )}, = 15, = {(0, 0), (1, 0), (1, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0355] For a twenty-third example (e.g., 1801 in FIG. 18) of this sub-embodiment, = 2, = {(2, ), (3, )}, = 2, = {(1, 0), (1, )}, =15 , = {(0, 0), (2, 0), (2, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0356] For a twenty-fourth example (e.g., 1802 in FIG. 18) of this sub-embodiment, = 3, = {(1, ), (2, ), (3, 0)}, = 2, = {(1, 0), (3, ), }, = 13 , = {(0, 0), (2, 0), (2, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0357] For a twenty-fifth example (e.g., 1803 in FIG. 18) of this sub-embodiment, = 3, = {(1, ), (3, ), (4, 0)}, = 2, = {(1, 0), (2, )}, = 15, = {(0, 0), (2, 0), (2, ), (3, 0), (3, ), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0358] For a twenty-sixth example (e.g., 1804 in FIG. 18) of this sub-embodiment, =2, = {(1, 0), (1, )}, = 2, = {(2, 0), (2, )}, = 12, = {(0, 0), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0359] For a twenty-seventh example (e.g., 1805 in FIG. 18) of this sub-embodiment, = 3, = {(2, 0), (3, 0), (3, )}, = 3, = {(1, 0), (1, ), (2, )}, =11 , = {(0, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0360] For a twenty-eighth example (e.g., 1806 in FIG. 18) of this sub-embodiment, = 3, = {(1, 0), (1, ), (2, )}, = 3, = {(2, 0), (3, 0), (3, )}, =11 , = {(0, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0361] In one further evaluation for the examples of this sub-embodiment, the SSB with 14 OFDM symbols can be mapped from a first OFDM symbol in a slot, e.g., #0 of the SSB is aligned with #0 of a slot.

[0362] FIG. 19 illustrates diagrams of example SSB architectures 1900 according to embodiments of the present disclosure. For example, SSB architectures 1900 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 114. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0363] FIG. 20 illustrates diagrams of example SSB architectures 2000 according to embodiments of the present disclosure. For example, SSB architectures 2000 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 115. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0364] In one sub-embodiment, = . For one example, =24 and / or =24.

[0365] For a first example (e.g., 1901 in FIG. 19) of this sub-embodiment, = 3, = {(0, 0), (1, 0), (2, 0)}, = 3, = {(5, 0), (8, 0), (11, 0)}, = 8, = {(3, 0), (4, 0), (6, 0), ……, ( , 0)}.

[0366] For a second example (e.g., 1902 in FIG. 19) of this sub-embodiment, = 3, = {(0, 0), (1, 0), (2, 0)}, = 3, = {(3, 0), (4, 0), (5, 0)}, = 8, = {(6, 0), ……, ( , 0)}.

[0367] For a third example (e.g., 1903 in FIG. 19) of this sub-embodiment, = 2, = {(0, 0), (2, 0)}, = 2, = {(1, 0), (3, 0)}, = 10, = {(4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0368] For a fourth example (e.g., 1904 in FIG. 19) of this sub-embodiment, =2, = {(0, 0), (1, 0)}, = 2, = {(2, 0), (3, 0)}, = 10, = {(4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0369] For a fifth example (e.g., 1905 in FIG. 19) of this sub-embodiment, = 2, = {(6, 0), (7, 0)}, = 2, = {(0, 0), (1, 0)}, = 10, = {(2, 0), (3, 0), (4, 0), (5, 0), (8, 0), ……, ( , 0)}.

[0370] For a sixth example (e.g., 1906 in FIG. 19) of this sub-embodiment, = 3, = {(0, 0), (1, 0), (2, 0)}, = 2, = {(3, 0), (4, 0)}, = 9, = {(5, 0), (6, 0), ……, ( , 0)}.

[0371] For a seventh example (e.g., 1907 in FIG. 19) of this sub-embodiment, = 3, = {(0, 0), (2, 0), (4, 0)}, = 2, = {(1, 0), (3, 0)}, = 9, = {(5, 0), (6, 0), ……, ( , 0)}.

[0372] For a eighth example (e.g., 1908 in FIG. 19) of this sub-embodiment, = 3, = {(0, 0), (1, 0), (2, 0)}, = 2, = {(7, 0), (8, 0)}, = 9, = {(3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0373] For a ninth example (e.g., 2001 in FIG. 20) of this sub-embodiment, = 3, = {(1, 0), (2, 0), (3, 0)}, = 3, = {(6, 0), (9, 0), (12, 0)}, = 8, = {(0, 0), (4, 0), (5, 0), (7, 0), ……, ( , 0)}.

[0374] For a tenth example (e.g., 2002 in FIG. 20) of this sub-embodiment, = 3, = {(1, 0), (2, 0), (3, 0)}, = 3, =(4, 0), (5, 0), (6, 0)}, = 8, = {(0, 0), (7, 0), ……, ( , 0)}.

[0375] For a eleventh example (e.g., 2003 in FIG. 20) of this sub-embodiment, = 2, = {(1, 0), (3, 0)}, = 2, = {(2, 0), (4, 0)}, = 10, = {(0, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0376] For a twelfth example (e.g., 2004 in FIG. 20) of this sub-embodiment, =2, = {(1, 0), (2, 0)}, = 2, = {(3, 0), (4, 0)}, = 10, = {(0, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0377] For a thirteenth example (e.g., 2005 in FIG. 20) of this sub-embodiment, = 2, = {(7, 0), (8, 0)}, = 2, = {(1, 0), (2, 0)}, = 10, = {(0, 0), (3, 0), (4, 0), (5, 0), (6, 0), (9, 0), ……, ( , 0)}.

[0378] For a fourteenth example (e.g., 2006 in FIG. 20) of this sub-embodiment, = 3, = {(1, 0), (2, 0), (3, 0)}, = 2, = {(4, 0), (5, 0)}, = 9, = {(0, 0), (6, 0), ……, ( , 0)}.

[0379] For a fifteenth example (e.g., 2007 in FIG. 20) of this sub-embodiment, = 3, = {(1, 0), (3, 0), (5, 0)}, = 2, = {(2, 0), (4, 0)}, = 9, = {(0, 0), (6, 0), ……, ( , 0)}.

[0380] For a sixteenth example (e.g., 2008 in FIG. 20) of this sub-embodiment, = 3, = {(1, 0), (2, 0), (3, 0)}, = 2, = {(8, 0), (9, 0)}, = 9, = {(0, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0381] In one further evaluation for the examples of this sub-embodiment, the SSB with 14 OFDM symbols can be mapped from a first OFDM symbol in a slot, e.g., #0 of the SSB is aligned with #0 of a slot.

[0382] FIG. 21 illustrates diagrams of example SSB architectures 2100 according to embodiments of the present disclosure. For example, SSB architectures 2100 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 116. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0383] FIG. 22 illustrates diagrams of example SSB architectures 2200 according to embodiments of the present disclosure. For example, SSB architectures 2200 can be utilized by the UE 116 of FIG. 3. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0384] In one sub-embodiment, = . For one example, =24 and / or =12 or 11.

[0385] For a first example (e.g., 2101 in FIG. 21) of this sub-embodiment, = 1, = {(0, 0)}, = 2, = {(1, ), (2, )}, = 15, = {(1, 0), (1, ), (2, 0), (2, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0386] For a second example (e.g., 2102 in FIG. 21) of this sub-embodiment, = 2, = {(0, 0), (1, 0)}, = 2, = {(2, ), (3, )}, = 14, = {(2, 0), (2, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0387] For a third example (e.g., 2103 in FIG. 21) of this sub-embodiment, = 2, = {(0, 0), (2, 0)}, = 2, = {(1, ), (3, )}, = 14, ={(1, 0), (1, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0388] For a fourth example (e.g., 2104 in FIG. 21) of this sub-embodiment, =1, = {(1, 0)}, = 2, = {(0, ), (2, )}, = 15, = {(0, 0), (0, ), (2, 0), (2, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0389] For a fifth example (e.g., 2105 in FIG. 21) of this sub-embodiment, = 2, = {(1, 0), (2, 0)}, = 2, = {(0, ), (3, )}, = 14, = {(0, 0), (0, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0390] For a sixth example (e.g., 2106 in FIG. 21) of this sub-embodiment, = 2, = {(0, 0), (1, 0)}, = 3, = {(2, ), (3, ), (4, )}, = 15, = {(2, 0), (2, ), (3, 0), (3, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0391] For a seventh example (e.g., 2107 in FIG. 21) of this sub-embodiment, = 2, = {(0, 0), (2, 0)}, = 3, = {(1, ), (3, ), (4, )}, = 15, = {(1, 0), (1, ), (3, 0), (3, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0392] For a eighth example (e.g., 2108 in FIG. 21) of this sub-embodiment, = 2, = {(1, 0), (3, 0)}, = 3, = {(0, ), (2, ), (4, )}, = 15 , = {(0, 0), (0, ), (2, 0), (2, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0393] For a ninth example (e.g., 2201 in FIG. 22) of this sub-embodiment, = 1, = {(1, 0)}, = 2, = {(2, ), (3, )}, = 15, = {(0, 0), (2, 0), (2, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0394] For a tenth example (e.g., 2202 in FIG. 22) of this sub-embodiment, = 2, = {(1, 0), (2, 0)}, = 2, = {(3, ), (4, )}, = 14, = {(0, 0), (3, 0), (3, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0395] For a eleventh example (e.g., 2203 in FIG. 22) of this sub-embodiment, = 2, = {(1, 0), (3, 0)}, = 2, = {(2, ), (4, )}, = 14, ={(0, 0), (2, 0), (2, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0396] For a twelfth example (e.g., 2204 in FIG. 22) of this sub-embodiment, =1, = {(2, 0)}, = 2, = {(1, ), (3, )}, = 15, = {(0, 0), (1, 0), (1, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0397] For a thirteenth example (e.g., 2205 in FIG. 22) of this sub-embodiment, = 2, = {(2, 0), (3, 0)}, = 2, = {(1, ), (4, )}, = 14, = {(0, 0), (1, 0), (1, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0398] For a fourteenth example (e.g., 2206 in FIG. 22) of this sub-embodiment, = 2, = {(1, 0), (2, 0)}, = 3, = {(3, ), (4, ), (5, ), }, = 15, = {(0, 0), (3, 0), (3, ), (4, 0), (4, ), (5, 0), (5, ), (6, 0), ……, ( , 0)}.

[0399] For a fifteenth example (e.g., 2207 in FIG. 22) of this sub-embodiment, = 2, = {(1, 0), (3, 0)}, = 3, = {(2, ), (4, ), (5, )}, = 15, = {(0, 0), (2, 0), (2, ), (4, 0), (4, ), (5, 0), (5, ), (6, 0), ……, ( , 0)}.

[0400] For a sixteenth example (e.g., 2208 in FIG. 22) of this sub-embodiment, = 2, = {(2, 0), (4, 0)}, = 3, = {(1, ), (3, ), (5, )}, = 15 , = {(0, 0), (1, 0), (1, ), (3, 0), (3, ), (5, 0), (5, ), (6, 0), ……, ( , 0)}.

[0401] In one further evaluation for the examples of this sub-embodiment, the SSB with 14 OFDM symbols can be mapped from a first OFDM symbol in a slot, e.g., #0 of the SSB is aligned with #0 of a slot.

[0402] FIG. 23 illustrates diagrams of example SSB architectures 2300 according to embodiments of the present disclosure. For example, SSB architectures 2300 can be utilized by any of the UEs 111-116 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0403] FIG. 24 illustrates diagrams of example SSB architectures 2400 according to embodiments of the present disclosure. For example, SSB architectures 2400 can be utilized by any of the UEs 111-116 of FIG. 1, such as the UE 111. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0404] In one sub-embodiment, = . For one example, =12 or 11 and / or =24.

[0405] For a first example (e.g., 2301 in FIG. 23) of this sub-embodiment, = 2, = {(0, ), (1, )}, = 1, = {(2, 0)}, = 15, = {(0, 0), (0, ), (1, 0), (1, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0406] For a second example (e.g., 2302 in FIG. 23) of this sub-embodiment, = 2, = {(0, ), (1, )}, = 2, = {(2, 0), (3, 0)}, = 14, = {(0, 0), (0, ), (1, 0), (1, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0407] For a third example (e.g., 2303 in FIG. 23) of this sub-embodiment, = 2, = {(0, ), (2, )}, = 2, = {(1, 0), (3, 0)}, = 14, ={(0, 0), (0, ), (2, 0), (2, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0408] For a fourth example (e.g., 2304 in FIG. 23) of this sub-embodiment, =2, = {(0, ), (2, )}, = 1, = {(1, 0)}, = 15, = {(0, 0), (0, ), (2, 0), (2, ), (3, 0), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0409] For a fifth example (e.g., 2305 in FIG. 23) of this sub-embodiment, = 2, = {(0, ), (3, )}, = 2, = {(1, 0), (2, 0)}, = 14, = {(0, 0), (0, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0410] For a sixth example (e.g., 2306 in FIG. 23) of this sub-embodiment, = 3, = {(0, ), (1, ), (2, )}, = 2, = {(3, 0), (4, 0)}, = 15, = {(0, 0), (0, ), (1, 0), (1, ), (2, 0), (2, ), (5, 0), (6, 0), ……, ( , 0)}.

[0411] For a seventh example (e.g., 2307 in FIG. 23) of this sub-embodiment, = 3, = {(1, ), (3, ), (4, )}, = 2, = {(0, 0), (2, 0)}, = 15, = {(1, 0), (1, ), (3, 0), (3, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0412] For a eighth example (e.g., 2308 in FIG. 23) of this sub-embodiment, = 3, = {(0, ), (2, ), (4, )}, = 2, = {(1, 0), (3, 0)}, = 15 , = {(0, 0), (0, ), (2, 0), (2, ), (4, 0), (4, ), (5, 0), (6, 0), ……, ( , 0)}.

[0413] For a ninth example (e.g., 2401 in FIG. 24) of this sub-embodiment, = 2, = {(1, ), (2, )}, = 1, = {(3, 0)}, = 15, = {(0, 0), (1, 0), (1, ), (2, 0), (2, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0414] For a tenth example (e.g., 2402 in FIG. 24) of this sub-embodiment, = 2, = {(1, ), (2, )}, = 2, = {(3, 0), (4, 0)}, = 14, = {(0, 0), (1, 0), (1, ), (2, 0), (2, ), (5, 0), (6, 0), ……, ( , 0)}.

[0415] For a eleventh example (e.g., 2403 in FIG. 24) of this sub-embodiment, = 2, = {(1, ), (3, )}, = 2, = {(2, 0), (4, 0)}, = 14, ={(0, 0), (1, 0), (1, ), (3, 0), (3, ), (5, 0), (6, 0), ……, ( , 0)}.

[0416] For a twelfth example (e.g., 2404 in FIG. 24) of this sub-embodiment, =2, = {(1, ), (3, )}, = 1, = {(2, 0)}, = 15, = {(0, 0), (1, 0), (1, ), (3, 0), (3, ), (4, 0), (5, 0), (6, 0), ……, ( , 0)}.

[0417] For a thirteenth example (e.g., 2405 in FIG. 24) of this sub-embodiment, = 2, = {(1, ), (4, )}, = 2, = {(2, 0), (3, 0)}, = 14, = {(0, 0), (1, 0), (1, ), (4, 0), (4, ), (4, 0), (6, 0), ……, ( , 0)}.

[0418] For a fourteenth example (e.g., 2406 in FIG. 24) of this sub-embodiment, = 3, = {(1, ), (2, ), (3, )}, = 2, = {(4, 0), (5, 0)}, = 15, = {(0, 0), (1, 0), (1, ), (2, 0), (2, ), (3, 0), (3, ), (6, 0), ……, ( , 0)}.

[0419] For a fifteenth example (e.g., 2407 in FIG. 24) of this sub-embodiment, = 3, = {(2, ), (4, ), (5, )}, = 2, = {(1, 0), (3, 0)}, = 15, = {(0, 0), (2, 0), (2, ), (4, 0), (4, ), (5, 0), (5, ), (6, 0), ……, ( , 0)}.

[0420] For a sixteenth example (e.g., 2408 in FIG. 24) of this sub-embodiment, = 3, = {(1, ), (3, ), (5, )}, = 2, = {(2, 0), (4, 0)}, = 15 , = {(0, 0), (1, 0), (1, ), (3, 0), (3, ), (5, 0), (5, ), (6, 0), ……, ( , 0)}.

[0421] In one further evaluation for the examples of this sub-embodiment, the SSB with 14 OFDM symbols can be mapped from a first OFDM symbol in a slot, e.g., #0 of the SSB is aligned with #0 of a slot.

[0422] FIG. 25 illustrates a flowchart of an example UE procedure 2500 for receiving signal(s) / channel(s) according to embodiments of the present disclosure. For example, procedure 2500 can be performed by the UE 116 of FIG. 3 and a corresponding or analogous process may be performed by the BS 102 of FIG. 2. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0423] In one embodiment, an example UE procedure for receiving a SSB is shown in FIG. 25. The procedure 2500 begins in 2501, a UE determines a number of RBs for a SSB. In 2502, the UE determines a number of OFDM symbols for the SSB. In 2503, the UE determines a first number and corresponding locations of OFDM symbols for a first type of signal(s) / channel(s) included in the SSB. For example, the type of signal(s) / channel(s) may be PSS, SSS, or PBCH. In 2504, the UE determines a second number and corresponding locations of OFDM symbols for a second type of signal(s) / channel(s) included in the SSB. For example, the type of signal(s) / channel(s) may be PSS, SSS, or PBCH. In 2505, the UE determines a third number and corresponding locations of OFDM symbols for a third type of signal(s) / channel(s) included in the SSB. For example, the type of signal(s) / channel(s) may be PSS, SSS, or PBCH. In 2506, the UE receives the first, second, and third type of signal(s) / channel(s) included in the SSB.

[0424] In addition, computer-readable storage media may be provided in the form of non-transitory storage media. The 'non-transitory storage medium' is a tangible device and only means that it does not contain a signal (e.g., electromagnetic waves). This term does not distinguish a case in which data is stored semi-permanently in a storage medium from a case in which data is temporarily stored. For example, the non-transitory recording medium may include a buffer in which data is temporarily stored.Any of the above variation embodiments can be utilized independently or in combination with at least one other variation embodiment. The above flowchart(s) illustrate example methods that can be implemented in accordance with the principles of the present disclosure and various changes could be made to the methods illustrated in the flowcharts herein. For example, while shown as a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

[0425] Although the figures illustrate different examples of user equipment, various changes may be made to the figures. For example, the user equipment can include any number of each component in any suitable arrangement. In general, the figures do not limit the scope of the present disclosure to any particular configuration(s). Moreover, while figures illustrate operational environments in which various user equipment features disclosed in this patent document can be used, these features can be used in any other suitable system.

[0426] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the descriptions in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. The scope of patented subject matter is defined by the claims.

[0427] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

Claims

1.A user equipment (UE) in a wireless communication system, the UE comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:identify a structure for a synchronization signals / physical broadcast channel (SS / PBCH) block, the structure including a first numberof orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second numberof resource blocks (RBs) in a frequency domain;identify, from theOFDM symbols, a third numberof OFDM symbols mapped for a primary synchronization signal (PSS), where; andidentify, from theOFDM symbols, a fourth numberof OFDM symbols mapped for a secondary synchronization signal (SSS), where; andreceive the SS / PBCH block based on the structure.2.The UE of claim 1, wherein the OFDM symbols are consecutive and within a slot.3.The UE of claim 1, wherein the OFDM symbols are first consecutive OFDM symbols within the OFDM symbols.4.The UE of claim 1, wherein the OFDM symbols are non-consecutive OFDM symbols within the OFDM symbols.5.The UE of claim 1, wherein = 12.6.The UE of claim 1, wherein:a first sequence for the PSS is mapped to center 127 subcarriers withinsubcarriers of theRBs, in each OFDM symbol within theOFDM symbols; anda second sequence for the SSS is mapped to center 127 subcarriers withinsubcarriers of theRBs, in each OFDM symbol within theOFDM symbols.7.The UE of claim 1, wherein remaining - - OFDM symbols within the OFDM symbols are mapped for a PBCH in the SS / PBCH block.8.A base station (BS) in a wireless communication system, the BS comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the BS to:determine a structure for a synchronization signals / physical broadcast channel (SS / PBCH) block, the structure including a first numberof orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second numberof resource blocks (RBs) in a frequency domain;determine, from theOFDM symbols, a third numberof OFDM symbols mapped for a primary synchronization signal (PSS), where; anddetermine, from theOFDM symbols, a fourth numberof OFDM symbols mapped for a secondary synchronization signal (SSS), where; andtransmit the SS / PBCH block based on the structure.9.The BS of claim 8, wherein the OFDM symbols are consecutive and within a slot.10.The BS of claim 8, wherein the OFDM symbols are first consecutive OFDM symbols within the OFDM symbols.11.The BS of claim 8, wherein the OFDM symbols are non-consecutive OFDM symbols within the OFDM symbols.12.The BS of claim 8, wherein:a first sequence for the PSS is mapped to center 127 subcarriers withinsubcarriers of theRBs, in each OFDM symbol within theOFDM symbols; anda second sequence for the SSS is mapped to center 127 subcarriers withinsubcarriers of theRBs, in each OFDM symbol within theOFDM symbols.13.The BS of claim 8, wherein remaining - - OFDM symbols within the OFDM symbols are mapped for a PBCH in the SS / PBCH block.14.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:identifying a structure for a synchronization signals / physical broadcast channel (SS / PBCH) block, the structure including a first numberof orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second numberof resource blocks (RBs) in a frequency domain;identifying, from theOFDM symbols, a third numberof OFDM symbols mapped for a primary synchronization signal (PSS), where;identifying, from theOFDM symbols, a fourth numberof OFDM symbols mapped for a secondary synchronization signal (SSS), where; andreceiving the SS / PBCH block based on the structure.15.A method performed by a base station (BS) in a wireless communication system, the method comprising:determining a structure for a synchronization signals / physical broadcast channel (SS / PBCH) block, the structure including a first numberof orthogonal frequency-division multiplexing (OFDM) symbols in a time domain and a second numberof resource blocks (RBs) in a frequency domain;determining, from theOFDM symbols, a third numberof OFDM symbols mapped for a primary synchronization signal (PSS), where; anddetermining, from theOFDM symbols, a fourth numberof OFDM symbols mapped for a secondary synchronization signal (SSS), where; andtransmitting the SS / PBCH block based on the structure.

Images