METHOD AND APPARATUS FOR RMSI CORESET CONFIGURATION IN A WIRELESS COMMUNICATION SYSTEM - Patent application

Abstract

A method, an apparatus, and a base station are provided that support higher data rates in a pre-5G or 5G communication system than in a 4G communication system. The method determines a frequency offset including an RB level frequency offset and an RE level frequency offset, the frequency offset being determined based on the lowest RE of an SS / PBCH block and the lowest RE of a CORESET for an RMSI, a first field of 4 bits is used to jointly configure the RB level frequency offset together with a multiplexing pattern of the SS / PBCH block and CORESET, a bandwidth of the CORESET, and a number of symbols for the CORESET for a combination of an SCS of the SS / PBCH block and an SCS of the CORESET, and a second field of 4 bits is used to configure, generate an MIB including the RB level frequency offset and the RE level frequency offset, and transmit the MIB to a UE via a PBCH.

Description

[Technical field]

[0001] The present disclosure relates generally to wireless communication systems, and more particularly to an improved remaining minimum system information (RMSI) control resource set (CORESET) configuration in a wireless communication system. [Background technology]

[0002] 4G(4 th Since the commercialization of the 5G (fifth generation) communication system, efforts have been made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic. For this reason, 5G or pre-5G communication systems are referred to as "Beyond 4G networks" or "post-LTE systems."

[0003] To achieve higher data transmission rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz bands). To reduce radio wave path loss and increase transmission distances, beamforming, massive MIMO, full dimensional MIMO (FD-MIMO), array antennas, analog beam-forming, and large scale antenna technologies are being discussed for 5G communication systems.

[0004] In addition, to improve the system network, the 5G communication system is undergoing technological developments such as improved small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, CoMP (Coordinated Multi-Points), and receiver interference cancellation.

[0005] For the 5G system, advanced coding modulation (ACM) technologies such as FQAM (hybrid frequency shift keying and quadrature amplitude modulation) and SWSC (sliding window superposition coding) and advanced access technologies such as FBMC (filter bank multi carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed.

[0006] In wireless communication networks, network access and radio resource management (RRM) are enabled by physical layer synchronization signals and higher (MAC) layer procedures. In particular, the UE attempts to detect the presence of synchronization signals along with at least one cell identification (ID) for initial access. After the UE is in the network and associated with a serving cell, the UE monitors multiple neighboring cells by detecting their synchronization signals and / or measuring associated cell-specific reference signals (RS). For next generation cellular systems such as 3GPP-NR (3rd Generation Partnership New Radio Access or Interface), an efficient integrated radio resource acquisition or tracking mechanism that works for various use cases such as enhanced mobile broadband (eMBB), ultra reliable low latency (URLLC), and massive machine type communication (mMTC), each of which corresponds to frequency bands with different coverage requirements and different radio losses, is preferred. A seamless and low latency RRM is preferred, which is likely to be designed for different network and radio resource paradigms. Summary of the Invention [Problem to be solved by the invention]

[0007] Embodiments of the present disclosure provide an improved new radio (NR) synchronization signal (SS) burst set design in a wireless communication system. [Means for solving the problem]

[0008] In one embodiment, a user equipment (UE) for control information configuration in a wireless communication system is provided. The UE includes a transceiver configured to receive a master information block (MIB) from a base station (BS) via a physical broadcasting channel (PBCH). The UE further includes a processor operatively connected to the transceiver, the processor configured to determine a frequency offset from the received MIB. The frequency offset is determined based on a lowest RE of a control resource set (CORESET) for a remaining minimum system information (RMSI) and a lowest RE of a SS / synchronization signal / physical broadcast channel (PBCH) block. The frequency offset includes a resource block (RB) level frequency offset and a resource element (RE) level frequency offset. The RB level frequency offset is configured jointly with the multiplexing pattern of the SS / PBCH block and CORESET, the bandwidth (BW) of the CORESET, and the number of symbols for the CORESET, for a combination of the subcarrier spacing (SCS) of the SS / PBCH block and the SCS of the CORESET, using a 4-bit first field. The RE level frequency offset is configured using a 4-bit second field.

[0009] In another embodiment, a base station (BS) for control information configuration in a wireless communication system is provided. The BS includes a processor configured to determine frequency offsets including resource block (RB) level frequency offsets and resource element (RE) level frequency offsets, where the frequency offsets are determined based on the lowest RE of a synchronization signal / physical broadcast channel (SS / PBCH) block and the lowest RE of a control resource set (CORESET) for a remaining minimum system information (RMSI), to jointly configure the RB level frequency offsets together with a multiplexing pattern of the SS / PBCH block and CORESET, a bandwidth (BW) of the CORESET, and a number of symbols for the CORESET using a first field of 4 bits for a combination of a subcarrier spacing (SCS) of the SS / PBCH block and an SCS of the CORESET, and to configure an RE level frequency offset using a second field of 4 bits, and to generate a master information block (MIB) including the configured RB level frequency offsets and the configured RE level frequency offsets. The BS further includes a transceiver operatively connected to the processor, where the transceiver is configured to transmit the MIB to a user equipment (UE) via the PBCH.

[0010] In another embodiment, a base station (BS) method for control information configuration in a wireless communication system is provided, comprising the steps of determining frequency offsets including resource block (RB) level frequency offsets and resource element (RE) level frequency offsets, where the frequency offsets are determined based on the lowest RE of a synchronization signal / physical broadcast channel (SS / PBCH) block and the lowest RE of a control resource set (CORESET) for the remaining minimum system information (RMSI), jointly configuring the RB level frequency offset together with a multiplexing pattern of the SS / PBCH block and CORESET, a bandwidth (BW) of the CORESET, and a number of symbols for the CORESET using a first field of 4 bits for a combination of a subcarrier spacing (SCS) of the SS / PBCH block and an SCS of the CORESET, configuring the RE level frequency offset using a second field of 4 bits, generating a master information block (MIB) including the RB level frequency offset and the RE level frequency offset, and transmitting the MIB to a user equipment (UE) via the PBCH.

[0011] Other technical features may become readily apparent to those skilled in the art from the following drawings, descriptions and claims.

[0012] Before proceeding with the detailed description below, it will be advantageous to provide definitions of certain words and phrases that are used throughout this patent specification. The term "couple" and its derivatives refer to some 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," and their derivatives, include both direct and indirect communication. The terms "include" and "comprise," and their derivatives, are meant to include without limitation. The term "or" is an inclusive term, meaning and / or. The phrase "associated with" and its derivatives means 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, and the like. The term "controller" means a device, system, or part thereof that controls at least one operation. Such a controller may be embodied in hardware or a combination of hardware and software and / or firmware. The functionality associated with a particular controller may be centralized or distributed, either locally or remotely. The phrase "at least one," when used in conjunction with a list of items, means that different combinations of one or more of the listed items may be used.For example, "at least one of A, B, and C" includes any one of the following combinations: A, B, C, A and B, A and C, B and C, and even A, B, and C.

[0013] Additionally, the various functions described below may be embodied or supported by one or more computer programs each formed of 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, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof configured for implementation in suitable computer readable program code. The phrase "computer readable program code" includes computer code varieties including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium that can be accessed by a computer, such as read only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of memory. "Non-transitory" computer readable medium excludes communications links that convey wired, wireless, optical, transitory electrical, or other signals. Non-transitory computer readable medium includes media on which data is permanently stored, as well as media on which data is stored and subsequently overwritten, such as rewritable optical disks or erasable memory devices.

[0014] Definitions for other specific words and phrases are provided throughout this patent specification, and those of skill in the art should understand that in many, if not most, cases such definitions may apply to both the past and future uses of the words and phrases so defined. Effect of the Invention

[0015] Various embodiments of the present disclosure provide a more effective channel measurement scheme. [Brief description of the drawings]

[0016] 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 indicate like parts and in which:

[0017] [Figure 1] FIG. 1 illustrates an exemplary wireless network in accordance with an embodiment of the present disclosure. [Diagram 2] FIG. 2 illustrates an example eNB according to an embodiment of the present disclosure. [Diagram 3] FIG. 2 illustrates an example UE according to an embodiment of the present disclosure. [Figure 4A] FIG. 2 illustrates a high-level diagram of an orthogonal frequency division multiple access transmission path according to an embodiment of the present disclosure. [Figure 4B] FIG. 2 illustrates a high-level diagram of an orthogonal frequency division multiple access receive path in accordance with an embodiment of the present disclosure. [Diagram 5] FIG. 2 illustrates a transmitter block diagram for PDSCH in a subframe according to an embodiment of the present disclosure. [Figure 6] FIG. 2 illustrates a receiver block diagram for PDSCH in a subframe according to an embodiment of the present disclosure. [Figure 7] FIG. 2 illustrates a transmitter block diagram for PUSCH in a subframe according to an embodiment of the present disclosure. [Figure 8] FIG. 2 illustrates a receiver block diagram for PUSCH in a subframe according to an embodiment of the present disclosure. [Figure 9] FIG. 2 illustrates an exemplary multiplexing of two slices according to an embodiment of the present disclosure. [Figure 10] FIG. 2 illustrates an exemplary antenna block according to an embodiment of the present disclosure. [Figure 11] FIG. 1 illustrates an example UE mobility scenario according to an embodiment of the present disclosure. [Figure 12] FIG. 1 illustrates an exemplary beam sweeping operation according to an embodiment of the present disclosure. [Figure 13A] FIG. 2 illustrates an exemplary TDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 13B] FIG. 2 illustrates an example FDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 13C] FIG. 2 illustrates an example hybrid TDM and FDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 14] FIG. 2 illustrates an example configuration of frequency offset for a first case of a TDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 15] FIG. 13 illustrates an example configuration of frequency offset for a second case of a TDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 16] FIG. 13 illustrates an example configuration of frequency offset for a third case of a TDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 17] FIG. 13 illustrates an example configuration of frequency offset for a fourth case of a TDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 18] FIG. 13 illustrates an example configuration of frequency offset for a fifth case of a TDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 19] FIG. 13 illustrates an exemplary configuration of frequency offset for a sixth case of a TDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 20] FIG. 2 illustrates an example configuration of frequency offset for a first case of an FDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 21] FIG. 13 illustrates an example configuration of frequency offset for a second case of FDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 22] FIG. 13 illustrates an example configuration of frequency offset for a third case of FDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 23] FIG. 13 illustrates an example configuration of frequency offset for a fourth case of FDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 24] FIG. 13 illustrates an example configuration of frequency offset for a fifth case of an FDM multiplexing pattern according to an embodiment of the present disclosure. [Diagram 25] FIG. 13 illustrates an example configuration of frequency offset for a sixth case of an FDM multiplexing pattern according to an embodiment of the present disclosure. [Figure 26A] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 15 kHz, 5 MHz, 24 PRB} in accordance with an embodiment of the present disclosure. [Figure 26B] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 30 kHz, 5 MHz, 12 PRB} in accordance with an embodiment of the present disclosure. [Figure 26C] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={30 kHz, 15 kHz, 10 MHz, 48 PRB} in accordance with an embodiment of the present disclosure. [Figure 26D] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={30 kHz, 30 kHz, 10 MHz, 24 PRB} in accordance with an embodiment of the present disclosure. [Figure 26E] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={120 kHz, 60 kHz, 50 MHz, 48 PRB} in accordance with an embodiment of the present disclosure. [Figure 26F] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={120 kHz, 120 kHz, 50 MHz, 24 PRB} in accordance with an embodiment of the present disclosure. [Figure 26G]FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={240 kHz, 120 kHz, 100 MHz, 48 PRB} in accordance with an embodiment of the present disclosure. [Fig. 26H] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={240 kHz, 60 kHz, 100 MHz, 96 PRB} in accordance with an embodiment of the present disclosure. [Figure 27A] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 15 kHz, 10 MHz, 48 PRB} in accordance with an embodiment of the present disclosure. [Figure 27B] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 15 kHz, 20 MHz, 96 PRB} in accordance with an embodiment of the present disclosure. [Figure 27C] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 30 kHz, 10 MHz, 24 PRB} in accordance with an embodiment of the present disclosure. [Figure 27D] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 30 kHz, 20 MHz, 48 PRB} in accordance with an embodiment of the present disclosure. [Figure 27E] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={30 kHz, 15 kHz, 20 MHz, 96 PRB} in accordance with an embodiment of the present disclosure. [Figure 27F] FIG. 13 illustrates an exemplary configuration of ΔF2 in the case where {SS SCS, RMSI SCS, CH BW, CORESET BW}={30 kHz, 30 kHz, 20 MHz, 48 PRB} in accordance with an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] 1 to 27F described below, and the various embodiments used to explain the principles of the present disclosure in this patent specification, are by way of example only and should not be construed as limiting the scope of the present disclosure in any manner. Those skilled in the art will appreciate that the principles of the present disclosure may be embodied in any suitably configured system or device.

[0019] The following documents and standard descriptions are incorporated by reference into this disclosure as if fully set forth herein: 3GPP TS 36.211 v13.2.0, "E-UTRA, Physical channels and modulation;" 3GPP TS 36.212 v13.2.0, "E-UTRA, Multiplexing and Channel coding;" 3GPP TS 36.213 v13.2.0, "E-UTRA, Physical Layer Procedures;" 3GPP TS 36.321 v13.2.0, "E-UTRA, Medium Access Control (MAC) protocol specification;" and 3GPP TS 36.331 v13.2.0, "E-UTRA, Radio Resource Control (RRC) protocol specification."

[0020] In the following, Fig. 1 to Fig. 4B, various embodiments implemented in a wireless communication system using an orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technology will be described. The description in Fig. 1 to Fig. 3 does not imply physical or architectural limitations on the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any appropriately configured communication system.

[0021] 1 is a diagram illustrating an exemplary wireless network according to an embodiment of the present disclosure. The embodiment of the wireless network shown in FIG. 1 is for illustration purposes only. Other embodiments for the wireless network 100 may be used without departing from the scope of the present disclosure.

[0022] 1, the wireless network includes eNB101, eNB102, and eNB103. eNB101 communicates with eNB102 and eNB103. eNB101 also communicates with at least one network 130, such as the Internet, a dedicated Internet Protocol (IP) network, or other data network.

[0023] The eNB 102 provides wireless broadband access to the network 130 for a first plurality of user equipment (UE) within the coverage area 120 of the eNB 102. The first plurality of UEs includes UE 111, which may be located at a small or medium business (SB); UE 112, which may be located at a large enterprise (E); UE 113, which may be located at a WiFi hotspot (HS); UE 114, which may be located at a first residential area (R); UE 115, which may be located at a second residential area (R); and UE 116, which is a mobile device (M) such as a mobile phone, wireless laptop, wireless PDA, etc. The eNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within the coverage area 125 of the eNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of the eNBs 101-103 can communicate with each other and with the UEs 111-116 using 5G, LTE, LTE-A, WiMAX, WiFi, or other wireless communication technology.

[0024] Depending on the network type, the term "base station" or "BS" may refer to a component (or collection of components) configured to provide wireless access to the network, such as a transmission point (TP), a transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wireless-enabled device. A base station may provide wireless access via one or more wireless communication protocols, such as 5G 3GPP new radio interface / access (NR), long term evolution (LTE), LTE-advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent specification to refer to the network infrastructure that provides wireless access to remote terminals. Also, depending on the network type, the term "user equipment" or "UE" may refer to any component such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "terminal," "receiving point," or "user equipment." For convenience, the terms "user equipment" and "UE" are used in this patent specification to refer to remote wireless devices that wirelessly access a BS, whether the UE is a mobile device (e.g., a mobile phone or smartphone) or what is commonly considered a fixed device (e.g., a desktop computer or vending machine).

[0025] The dotted lines indicate the general extents of coverage areas 120 and 125, which are shown as generally circular for purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with an eNB, e.g., coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the eNB and changes in the radio environment associated with natural and man-made obstacles.

[0026] As described in more detail below, one or more of the UEs 111-116 include circuitry, programming, or a combination thereof for efficient NR RMSI CORESET configuration in an improved wireless communication system. In certain embodiments, one or more of the eNBs 101-103 include circuitry, programming, or a combination thereof for NR RMSI CORESET configuration in an improved wireless communication system.

[0027] Although Figure 1 illustrates an example wireless network, various changes may be made to Figure 1. For example, a wireless network may include any number of eNBs and any number of UEs in any suitable arrangement. Additionally, eNB 101 may be in direct communication with any number of UEs to provide the UEs with wireless broadband access to network 130. Similarly, each eNB 102-103 may be in direct communication with network 130 to provide the UEs with direct wireless broadband access to network 130. Additionally, eNBs 101, 102, and / or 103 may provide access to other or additional external networks, such as an external telephone network or other types of data networks.

[0028] Figure 2 illustrates an example eNB 102 according to an embodiment of the present disclosure. The embodiment of eNB 102 illustrated in Figure 2 is for illustrative purposes only, and eNBs 101 and 103 of Figure 1 may have the same or similar configurations. However, eNBs may come in a variety of different configurations, and Figure 2 does not limit the scope of the present disclosure to any particular implementation for an eNB.

[0029] 2, the eNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. The eNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0030] The RF transceivers 210a-210n receive incoming RF signals from the antennas 205a-205n, such as signals to be transmitted by UEs in the network 100. The RF transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are transmitted to RX processing circuitry 220, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The RX processing circuitry 220 transmits the processed baseband signals to the controller / processor 225 for further processing.

[0031] TX processing circuitry 215 receives analog or digital data (e.g., voice data, web data, email, or interactive video game data) from controller / processor 225. TX processing circuitry 215 encodes, multiplexes, and / or digitizes outgoing baseband data and generates processed baseband or IF signals. RF transceivers 210a-210n receive the outgoing processed baseband or IF signals from TX processing circuitry 215 and upconvert the baseband or IF signals to RF signals that are transmitted via antennas 205a-205n.

[0032] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the eNB 102. For example, the controller / processor 225 may control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers 210a-210n, the RX processing circuitry 220, and the TX processing circuitry 215 in accordance with well-known principles. The controller / processor 225 may also support additional functionality, such as improved wireless communication capabilities. For example, the controller / processor 225 may support beamforming or directional routing operations in which outgoing signals from multiple antennas 205a-205n are weighted differently to effectively steer in a desired direction. Any of a variety of other functions may be supported in the eNB 102 by the controller / processor 225.

[0033] Controller / processor 225 may also execute programs and other processes, such as the OS, that reside in memory 230. Controller / processor 225 may move data into or out of memory 230 as required by the executing processes.

[0034] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 enables the eNB 102 to communicate with other devices or systems over a backhaul connection or over a network. The interface 235 can support communication over any suitable wired or wireless connection(s). For example, if the eNB 102 is embodied as part of a cellular communication system (e.g., supporting 5G, LTE, or LTE-A), the interface 235 can enable the eNB 102 to communicate with other eNBs over a wired or wireless backhaul connection. If the eNB 102 is embodied as an access point, the interface 235 can enable the eNB 102 to transmit over a wired or wireless local area network or to a larger network (e.g., the Internet) over a wired or wireless connection. The interface 235 includes any suitable structure supporting communication over a wired or wireless connection, e.g., an Ethernet or RF transceiver.

[0035] The memory 230 is coupled to the controller / processor 225. A portion of the memory 230 may include RAM, and another portion of the memory 230 may include flash memory or other ROM.

[0036] Although FIG. 2 illustrates one example of an eNB 102, various changes may be made to FIG. 2. For example, the eNB 102 may include any number of each of the components illustrated in FIG. 2. As one particular example, an access point may include multiple interfaces 235, and the controller / processor 225 may support a routing function for routing data between different network addresses. As another particular example, although illustrated as including a single instance of the TX processing circuitry 215 and a single instance of the RX processing circuitry 220, the eNB 102 may include multiple instances of each (e.g., one per RF transceiver). Additionally, the various components of FIG. 2 may be combined, further subdivided, or omitted, and additional components may be added as needed.

[0037] Figure 3 illustrates an example UE 116, according to an embodiment of the present disclosure. The embodiment of the UE 116 illustrated in Figure 3 is for illustrative purposes only, and the UEs 111-115 of Figure 1 may have the same or similar configurations. However, UEs may come in a variety of different configurations, and Figure 3 does not limit the scope of the present disclosure to any particular implementation for a UE.

[0038] 3, the UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a TX processing circuit 315, a microphone 320, and a receive (RX) processing circuit 325. The UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, a touch screen 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0039] The RF transceiver 310 receives an input RF signal from an antenna 305 to be transmitted by an eNB of the network 100. The RF transceiver 310 downconverts the input RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is transmitted to RX processing circuitry 325 which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry 325 transmits the processed baseband signal to a speaker 330 (e.g., voice data) or to a processor 340 for further processing (e.g., web browsing data).

[0040] TX processing circuitry 315 receives analog or digital voice data from microphone 320 or other outgoing baseband data (e.g., web data, email, or interactive video game data) from processor 340. TX processing circuitry 315 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 310 receives the outgoing processed baseband or IF signal from TX processing circuitry 315 and upconverts the baseband or IF signal to an RF signal that is transmitted via antenna 305.

[0041] The processor 340 may include one or more processors or other processing devices and may control the overall operation of the UE 116 by executing an OS 361 stored in memory 360. For example, the processor 340 may control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver 310, the RX processing circuitry 325, and the TX processing circuitry 315 in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0042] The processor 340 may also execute other processes and programs resident in the memory 360. The processor 340 may move data into or out of the memory 360 as required by the executing processes. In some embodiments, the processor 340 is configured to execute applications 362 based on an OS 361 or upon signals received from an eNB or an operator. The processor 340 is also coupled to an I / O interface 345 that 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 a communication path between the processor 340 and its peripherals.

[0043] Processor 340 is also coupled to a touch screen 350 and a display 355. An operator of UE 116 can input data into UE 116 using touch screen 350. Display 355 can be, for example, a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics from a website.

[0044] Memory 360 is coupled to processor 340. A portion of memory 360 may include random access memory (RAM), and another portion of memory 360 may include flash memory or other read-only memory (ROM).

[0045] Although Figure 3 illustrates an example of a UE 116, various changes may be made to Figure 3. For example, various components of Figure 3 may be combined, further subdivided, or omitted, and additional components may be added as needed. As one particular example, the processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, while Figure 3 illustrates a UE 116 configured as a mobile phone or smartphone, the UE may be configured to operate as other types of mobile or fixed devices.

[0046] FIG. 4A is a high-level diagram of a transmit path circuit. For example, the transmit path circuit may be used for orthogonal frequency division multiple access (OFDMA) communication. FIG. 4B is a high-level diagram of a receive path circuit. For example, the receive path circuit may be used for orthogonal frequency division multiple access (OFDMA) communication. In FIG. 4A and FIG. 4B, in the case of downlink communication, the transmit path circuit may be embodied in a base station (eNB) 102 or a relay station, and the receive path circuit may be embodied in a user equipment (e.g., user equipment 116 of FIG. 1). In another example, in the case of uplink communication, the receive path circuit 450 may be embodied in a base station (e.g., eNB 102 of FIG. 1) or a relay station, and the transmit path circuit may be embodied in a user equipment (e.g., user equipment 116 of FIG. 1).

[0047] The transmit path circuitry 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 circuitry 450 includes a down-converter (DC) 455, a remove cyclic prefix block 460, a serial-to-parallel (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.

[0048] At least some of the components in Figures 4A (400) and 4B (450) may be implemented in software, while other components may be implemented in configurable hardware or a mixture of software and configurable hardware. In particular, it is noted that the FFT and IFFT blocks described in this disclosure may be implemented as configurable software algorithms, where the value of size N may be changed depending on the implementation.

[0049] In addition, although the present disclosure relates to embodiments implementing a fast Fourier transform and an inverse fast Fourier transform, this is merely by way of example and should not be construed as limiting the scope of the present disclosure. In other embodiments of the present disclosure, it can be understood that the fast Fourier transform function and the inverse fast Fourier transform function can be easily replaced by a discrete Fourier transform (DFT) function and an inverse discrete Fourier transform (IDFT) function, respectively. It can be understood that in the case of the DFT and IDFT functions, the value of the variable N can be any integer (e.g., 1, 2, 3, 4, etc.), and in the case of the FFT and IFFT functions, the value of the variable N can be any integer that is a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).

[0050] In the transmit path circuitry 400, the channel coding and modulation block 405 receives a set of information bits and applies coding (e.g., LDPC coding) and modulates (e.g., Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) the input bits to generate a sequence of frequency-domain modulation symbols. The serial-to-parallel block 410 converts (i.e., demultiplexes) the serially modulated symbols to parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used at the BS 102 and the UE 116. The Size N IFFT block 415 then performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. The parallel-to-serial block 420 then converts (i.e., multiplexes) the parallel time-domain output symbols from the Size N IFFT block 415 to generate a serial time-domain signal. The add cyclic prefix block 425 then inserts a cyclic prefix into the time-domain signal. Finally, an up-converter 430 modulates (i.e., up-converts) the output of the add cyclic prefix block 425 to an RF frequency for transmission over a wireless channel. The signal may also be baseband filtered before converting to an RF frequency.

[0051] The transmitted RF signal reaches the UE 116 after passing through a wireless channel, and the reverse operation to that at the eNB 102 is performed. 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 a parallel time-domain signal. The size N FFT block 470 then performs an FFT algorithm to generate N parallel frequency-domain signals. The parallel-to-serial block 475 converts the parallel frequency-domain signals to a sequence of modulated data symbols. The channel decode and demodulation block 480 performs demodulation on the modulated symbols and then decoding to recover the original input data stream.

[0052] The eNBs 101-103 may implement a similar transmit path for downlink transmissions to the user equipment 111-116, respectively, and may also implement a similar receive path for uplink reception from the user equipment 111-116. Similarly, the user equipment 111-116 may implement a transmit path corresponding to the architecture for uplink transmissions to the eNBs 101-103, respectively, and may also implement a receive path corresponding to the architecture for downlink reception from the eNBs 101-103.

[0053] Use cases for 5G communication systems were identified and explained. These use cases can be broadly categorized into three groups. As one example, enhanced mobile broadband (eMBB) is determined to have high bits / sec requirements with looser latency and reliability requirements. As another example, ultra-reliable and low latency (URLL) is determined to have looser bits / sec requirements. As yet another example, massive machine type communication (mMTC) is determined to have a large number of devices in the vicinity of km. 2It is determined that the number of devices that can be deployed can reach hundreds of thousands to millions per second, but the reliability / throughput / latency requirements can be more moderate. Such a scenario can also include power efficiency requirements in that battery drain should be minimized as much as possible.

[0054] A communication system includes a downlink (DL) that conveys signals from a transmission point, such as a base station (BS) or NodeB, to a user equipment (UE), and an uplink (UL) that conveys signals from the UE to a receiving point, such as a NodeB. The UE, also commonly referred to as a terminal or mobile station, can be fixed or mobile and can be a cellular phone, a personal computing device, or an automated device. The eNodeB, which is generally a fixed station, can also be referred to as an access point or other equivalent term. In the case of an LTE system, the NodeB is sometimes referred to as an eNodeB.

[0055] In a communication system such as an LTE system, DL signals may include data signals conveying information content, control signals conveying DL control information (DCI), and reference signals (RS), also known as pilot signals. An eNodeB transmits data information via a physical DL shared channel (PDSCH). An eNodeB transmits DCI via a physical DL control channel (PDCCH) or an enhanced PDCCH (EPDCCH).

[0056] The eNodeB transmits acknowledgement information in response to a data transport block (TB) transmission from the UE on a physical hybrid ARQ indicator channel (PHICH). The eNodeB transmits one or more of a number of RS types, including a UE-common RS (CRS), a channel state information RS (CSI-RS), or a demodulation RS (DMRS). The CRS is transmitted over the DL system bandwidth (BW) and may be used by the UE to obtain a channel estimate to demodulate data or control information or to make measurements. To reduce CRS overhead, the eNodeB may transmit the CSI-RS with a smaller density in the time and / or frequency domain than the CRS. The DMRS may be transmitted only in the BW of the respective PDSCH or EPDCCH, and the UE may use the DMRS to demodulate data or control information in the PDRSCH or EPDCCH, respectively. The transmission time interval for the DL channel is called a subframe and may have a duration of, for example, 1 millisecond.

[0057] DL signals also include the transmission of logical channels carrying system control information. The BCCH is mapped to a transport channel called broadcast channel (BCH) when carrying master information blocks (MIBs) or DL ​​shared channel (DL-SCH) when carrying system information blocks (SIBs). Most of the system information is contained in different SIBs transmitted using the DL-SCH. The presence of system information on the DL-SCH in a subframe can be indicated by the transmission of a corresponding PDCCH carrying a codeword with a cyclic redundancy check (CRC) scrambled with the system information RNTI (SI-RNTI). Alternatively, scheduling information for SIB transmissions can be provided in the previous SIB and scheduling information for the first SIB (SIB-1) can be provided by the MIB.

[0058] DL resource allocation is done in subframe units and Physical Resource Block (PRB) groups. The transmission BW includes frequency resource units called resource blocks (RBs). Each RB is

number

number

[0059] The UL signals may include data signals carrying data information, control signals carrying UL control information (UCI), and UL RSs. The UL RSs include DMRS and SRS (Sounding RS). The UE transmits the DMRS only in the BW of the respective PUSCH or PUCCH. The eNodeB can demodulate the data signal or UCI signal using the DMRS. The UE transmits the SRS to provide the eNodeB with UL CSI. The UE transmits the data information or UCI via the respective physical UL shared channel (PUSCH) or physical UL control channel (PUCCH). If the UE needs to transmit data information and UCI in the same UL subframe, the UE can multiplex both in the PUSCH. The UCI includes Hybrid Automatic Repeat request acknowledgement (HARQ-ACK) information indicating correct (ACK) or incorrect (NACK) detection of a data TB on the PDSCH or the absence of a PDCCH detection (DTX), a scheduling request (SR) indicating whether the UE has data in its buffer, a rank indicator (RI) and channel state information (CSI) that allows the eNodeB to perform link adaptation for PDSCH transmission to the UE. The HARQ-ACK information is sent by the UE in response to detection of a PDCCH / EPDCCH indicating the release of a semi-permanently scheduled PDSCH.

[0060] The UL subframe includes two slots. Each slot is used to transmit data information, UCI, DMRS, or SRS.

number

number

number

[0061] 5 illustrates a transmitter block diagram (500) for a PDSCH in a subframe according to an embodiment of the present disclosure. The embodiment of the transmitter block diagram (500) shown in FIG. 5 is for illustration purposes only. FIG. 5 does not limit the scope of the present disclosure to any particular implementation of the transmitter block diagram (500).

[0062] As shown in Fig. 5, information bits 510 are encoded by an encoder 520, such as a turbo encoder, and modulated by a modulator 530, for example, using Quadrature Phase Shift Keying (QPSK) modulation. A serial-to-parallel (S / P) converter 540 generates M modulation symbols that are subsequently provided to a mapper 550 to be mapped to REs selected by a transmit BW selection unit 555 for the assigned PDSCH transmit BW, and a unit 560 applies an Inverse Fast Fourier Transform (IFFT), after which the output is serialized by a parallel-to-serial (P / S) converter 570 to generate a time domain signal, filtering is applied by a filter 580, and the signal is transmitted (590 in Fig. 5). Additional functions such as data scrambling, cyclic prefix insertion, time windowing, interleaving, etc. are well known in the art and are not shown for simplicity.

[0063] FIG. 6 illustrates a receiver block diagram (600) for PDSCH in a subframe according to an embodiment of the present disclosure. The embodiment of diagram 600 shown in FIG. 6 is for illustration purposes only. FIG. 6 does not limit the scope of the present disclosure to any particular implementation of diagram 600.

[0064] As shown in Fig. 6, a received signal 610 is filtered by a filter 620, an RE 630 for an assigned receive BW is selected by a BW selector 635, a unit 640 applies a fast Fourier transform (FFT), and the output is serialized by a parallel-to-serial converter 650. Then, a demodulator 660 coherently demodulates the data symbols by applying a channel estimate obtained from a DMRS or CRS (not shown), and a decoder 670, such as a turbo decoder, decodes the demodulated data to provide an estimate of the information data bits 680. Additional functions such as time windowing, cyclic prefix removal, descrambling, channel estimation, and de-interleaving are not shown for simplicity.

[0065] 7 illustrates a transmitter block diagram (700) for a PUSCH in a subframe according to an embodiment of the present disclosure. The embodiment of the block diagram (700) shown in FIG. 7 is for illustration purposes only. FIG. 7 does not limit the scope of the present disclosure to any particular implementation of the block diagram (700).

[0066] As shown in Fig. 7, information data bits 710 are encoded by an encoder 720, such as a turbo encoder, and modulated by a modulator 730. A discrete Fourier transform (DFT) unit 740 applies a DFT to the modulated data bits, a RE 750 corresponding to the assigned PUSCH transmission BW is selected by a transmission BW selection unit 755, an IFFT is applied by a unit 760, and after cyclic prefix insertion (not shown), filtering is applied by a filter 770, and the signal is transmitted (780 in Fig. 7).

[0067] 8 illustrates a receiver block diagram (800) for a PUSCH in a subframe according to an embodiment of the present disclosure. The embodiment of the block diagram (800) shown in FIG. 8 is for illustration purposes only. FIG. 8 does not limit the scope of the present disclosure to any particular implementation of the block diagram (800).

[0068] As shown in Fig. 8, a received signal 810 is filtered by a filter 820. Then, after the cyclic prefix is ​​removed (not shown), a unit 830 applies an FFT, a RE 840 corresponding to the assigned PUSCH receive BW is selected by a receive BW selector 845, a unit 850 applies an inverse DFT (IDFT), a demodulator 860 coherently demodulates the data symbols by applying a channel estimate obtained from a DMRS (not shown), and a decoder 870, such as a turbo decoder, decodes the demodulated data to provide estimates of information data bits 880.

[0069] In the next generation cellular system, various use cases are envisaged beyond the capabilities of the LTE system. Systems capable of operating below 6 GHz (sub-6 GHz) and above 6 GHz (e.g. mmWave regime), called 5G or fifth generation cellular systems, are one such requirement. 74 5G use cases have been identified and described in 3GPP TR 22.891. These use cases can be broadly categorized into three different groups. The first group is called 'eMBB (enhanced mobile broadband)', which targets high data rate services with more relaxed latency and reliability requirements. The second group is called "URLL (ultra reliable and low latency)", which targets applications with more relaxed data rate requirements but with less tolerance for latency. The third group is called "mMTC (massive MTC)", which targets km services with more relaxed requirements for reliability, data rate and latency. 2 The goal is to connect as many as a million low power devices per second.

[0070] In order for 5G networks to support various services with different Quality of Service (QoS), one method called network slicing has been identified in the LTE specification. A flexible and self-contained frame or subframe design is utilized to efficiently utilize PHY resources to multiplex various slices (with different resource allocation schemes, neural networks and scheduling strategies) on the DL-SCH.

[0071] 9 is a diagram illustrating an example multiplexing of two slices 900 according to an embodiment of the present disclosure. The embodiment of multiplexing of two slices 900 shown in FIG. 9 is for illustration purposes only. FIG. 9 does not limit the scope of the present disclosure to any particular implementation of multiplexing of two slices 900.

[0072] Two exemplary instances of multiplexing two slices in a common subframe or frame are shown in FIG. 9. In such exemplary embodiments, a slice can be composed of one or two transmission instances, where one transmission instance includes a control (CTRL) component (e.g., 920a, 960a, 960b, 920b, or 960c) and a data component (e.g., 930a, 970a, 970b, 930b, or 970c). In embodiment 910, the two slices are multiplexed in the frequency domain, whereas in embodiment 950, the two slices are multiplexed in the time domain. Such two slices can be transmitted to different neuroradio sets.

[0073] The LTE specification supports up to 32 CSI-RS antenna ports, which allows an eNB to be equipped with a number of antenna elements (such as 64 or 128), where multiple antenna elements are mapped onto one CSI-RS port. For next generation cellular systems such as 5G, the maximum number of CSI-RS ports can remain the same or can be increased.

[0074] 10 is a diagram illustrating an exemplary antenna block 1000 according to an embodiment of the present disclosure. The embodiment of the antenna block 1000 shown in FIG. 10 is for illustration purposes only. FIG. 10 does not limit the scope of the present disclosure to any particular implementation of the antenna block 1000.

[0075] For mmWave bands, the number of antenna elements may be larger for a given form factor, but the number of CSI-RS ports corresponding to the number of digitally precoded ports tends to be limited by hardware constraints (such as the possibility of installing a large number of ADCs / DACs at mmWave frequencies) as shown in Figure 10. In this case, one CSI-RS port is mapped to many antenna elements that can be controlled by a bank of analog phase shifters. One CSI-RS port can then correspond to one subarray that generates a narrow analog beam by analog beamforming. Such an analog beam can be configured to sweep over a wider range of angles by varying the phase shifter bank over symbols or subframes. The number of subarrays (which is the same as the number of RF chains) is the number of CSI-RS ports N. CSI-PORT The digital beamforming unit is N CSI-PORT Linear combining is performed across analog beams to further increase the precoding gain: analog beams are wideband (and therefore not frequency selective), but digital precoding can be varied across frequency subbands or resource blocks.

[0076] In 3GPP LTE communication systems, network access and radio resource management (RRM) are enabled by physical layer synchronization signals and higher (MAC) layer procedures. In particular, the UE attempts to detect the presence of synchronization signals along with at least one cell ID for initial access. Once the UE is in the network and associated with any serving cell, the UE monitors several neighboring cells by detecting / attempting to detect their synchronization signals and measuring associated cell-specific RS (e.g., measuring their RSRP). For next generation cellular systems such as 3GPP NR (new radio access or interface), an efficient and unified radio resource acquisition or tracking mechanism that applies to various use cases (e.g., eMBB, URLLC, mMTC, each of which corresponds to different coverage requirements) and frequency bands (with different radio losses) is preferred. A seamless and low latency RRM is preferred, which is likely to be designed for different network and radio resource paradigms. Such a goal poses at least the following challenges in designing an access, radio resource and mobility management framework:

[0077] First, NR may support more diverse network topologies, so the concept of a cell may be redefined or replaced by other radio resource entities. For example, in a synchronous network, a cell may be associated with multiple transport-receive points (TRPs), similar to the coordinated multipoint transmission (COMP) scenario in the LTE specification. In this case, seamless mobility is a desirable feature.

[0078] Second, when large antenna arrays and beamforming are used, it may be a natural approach to define radio resources in terms of beams (which may also be referred to differently, e.g., as spatial domain filters). Given that multiple beamforming architectures may be used, an access, radio resource and mobility management framework that accommodates a variety of beamforming architectures (or alternatively, is independent of the beamforming architecture) is preferred.

[0079] 11 is a diagram illustrating an example UE mobility scenario 1100 according to an embodiment of the present disclosure. The embodiment of the UE mobility scenario 1100 illustrated in FIG. 11 is for illustrative purposes only. FIG. 11 does not limit the scope of the present disclosure to any particular realization of the UE mobility scenario 1100.

[0080] For example, this framework may be applied regardless of whether a beam is formed for a single CSI-RS port (e.g., multiple analog ports connected to a single digital port and applied to multiple widely separated digital signals) or whether a beam is formed by multiple CSI-RS ports. This framework may also be applied with or without the use of beam sweeping (as shown in FIG. 11).

[0081] Third, different frequency bands and use cases will have different coverage limitations. For example, mmWave bands will have large signal losses. Therefore, some form of coverage enhancement scheme will be required. Some candidates include beam sweeping (shown in Figure 10), repetition, diversity and / or multiple TRP transmission. For mMTC, where the transmission bandwidth is small, time domain repetition will be required to ensure sufficient coverage.

[0082] UE-centric access using two levels of radio resource entities is illustrated in FIG. 11. These two levels can also be referred to as "cell" and "beam". These two terms are exemplary and are used for illustrative purposes. Other terms such as radio resource (RR) 1 and 2 can also be used. Also, the term "beam" as a radio resource unit should be differentiated from, for example, the analog beam in FIG. 10 where beam sweeping is used.

[0083] As shown in FIG. 11, the first RR level (referred to as "cell") applies when a UE enters the network and engages in an initial access procedure. At 1110, a UE 1111 is connected to a cell 1112 after performing an initial access procedure that includes detecting the presence of a synchronization signal. The synchronization signal may be used to detect a cell identification (cell ID) associated with a serving cell as well as general timing and frequency acquisition. At this first level, the UE observes cell boundaries since different cells may be associated with different cell IDs. In FIG. 11, a cell is associated with one TRP (in general, a cell may be associated with multiple TRPs). Since the cell ID is a MAC layer entity, the initial access involves not only physical layer procedure(s) (e.g., cell search with synchronization signal acquisition) but also MAC layer procedure(s).

[0084] The second RR level (referred to as "beam") applies when a UE is already attached to a cell and in the network. At this second level, the UE 1111 can move within the network without observing cell boundaries, as shown in embodiment 1150. That is, UE mobility is handled at the beam level rather than the cell level, where one cell may be associated with N beams (N may be 1 or > 1). However, unlike cells, beams are physical layer entities. Therefore, UE mobility management is handled only at the physical layer. An example of a UE mobility scenario based on the second level (RR) is given in embodiment 1150 of FIG. 11.

[0085] After the UE 1111 is associated with the serving cell 1112, the UE 1111 is associated with the beam 1151. This is accomplished by acquiring a beam or radio resource (RR) acquisition signal from which the UE can acquire a beam identity or identification. An example of a beam or RR acquisition signal is a measurement reference signal (RS). Upon acquiring a beam (or RR) acquisition signal, the UE 1111 can report the status to the network or associated TRP. An example of such a report includes a measured beam power (or measured RS power) or one or more recommended "beam identities (IDs)" or "RR-IDs" set. Based on this report, the network or associated TRP can assign a beam (as a radio resource) to the UE 1111 for data and control transmission. When the UE 1111 moves to another cell, the boundary between the previous cell and the next cell is not observed or visible to the UE 1111. Instead of a cell handover, the UE 1111 switches from the beam 1151 to the beam 1152. Such seamless mobility is made possible by reporting from the UE 711 to the network or associated TRP - in particular, when the UE 1111 reports a set of M>1 preferred beam identities by acquiring and measuring M beam (or RR) acquisition signals.

[0086] 12 is a diagram illustrating an example beam sweeping operation 1200 according to an embodiment of the present disclosure. The embodiment of the beam sweeping operation 1200 shown in FIG. 12 is for illustration purposes only. FIG. 12 does not limit the scope of the present disclosure to any particular implementation of the beam sweeping operation 1200.

[0087] As shown in Figure 12, the initial access procedure 1210 described above and the mobility or radio resource management 1220 described above are described from the perspective of the UE. The initial access procedure 1210 includes cell ID acquisition from DL synchronization signal(s) 1211 as well as retrieval of broadcast information (with system information required by the UE to establish DL and UL connections) and then UL synchronization (which may include a random access procedure). Once the UE has completed 1211 and 1212, the UE is connected to the network and associated with any cell. After the initial access procedure is completed, the UE (possibly mobile) will be in the RRM state described at 1220. This state includes an acquisition step 1221 where the UE may attempt to periodically (repeatedly) acquire a "beam" or RR ID from a "beam" or RR acquisition signal (e.g., measurement RS).

[0088] The UE may be configured with a list of beams / RR IDs to monitor. Such a list of “beams” / RR IDs may be updated or reconfigured by the TRP / network. Such configuration may be signaled via higher layer (e.g., RRC) signaling or dedicated L1 or L2 control channels. Based on this list, the UE may monitor and measure signals associated with each of such beams / RR IDs. Such signals may correspond to measurement RS resources similar to CSI-RS resources in LTE systems. In this case, the UE may be configured with a set of K>1 CSI-RS resources to monitor. Several options may be possible for the measurement report 1222. First, the UE may measure each of the K CSI-RS resources, calculate the corresponding RS power (similar to RSRP or RSRQ in LTE systems), and report this RS power to the TRP (or network). Second, the UE may measure each of the K CSI-RS resources, calculate the associated CSI (which may include CQI and potentially other CSI parameters, e.g., RI and PMI), and report this CSI to the TRP (or network). Based on the report from the UE, the UE is assigned M≧1 “beams” or RRs via higher layer (RRC) signaling or L1 / L2 control signaling 1223. The UE is then connected to these M “beams” / RRs.

[0089] For certain scenarios, such as asynchronous networks, the UE can fall back to cell ID-based or cell-level mobility management similar to 3GPP LTE systems. Therefore, only one of the two levels of radio resource entities (cells) can be applied. When a two-level ("cell" and "beam") radio resource entity or management is used, the synchronization signal(s) can be designed mainly for initial access to the network. For mmWave systems, where analog beam sweeping (as shown in FIG. 12) or repetition can be used to enhance the coverage of common signals (e.g., synchronization signal(s) and broadcast channels), the synchronization signals can be repeated over time (e.g., across OFDM symbols or slots or subframes). However, such repetition factors do not necessarily correlate with the number of "beams" (defined as radio resource units and distinct from analog beams used for beam sweeping) supported per cell or TRP. Thus, beam identification (ID) is not obtained or detected from the synchronization signal(s). Instead, the beam ID is carried by the beam (RR) acquisition signal, such as the measurement RS. Similarly, the beam (RR) acquisition signal does not carry the cell ID (and therefore the cell ID is not detected from the beam or RR acquisition signal).

[0090] Therefore, taking into consideration the above new challenges in initial access procedures and RRM for new radio access technologies (NR), a primary broadcast channel needs to be designed to carry synchronization signals (with associated UE procedures) and broadcast information (e.g., Master Information Block or MIB).

[0091] For LTE NR, the synchronization signal and PBCH block (NR-SS / PBCH block) is designed for eMBB purposes and for licensed bands only. Each NR-SS / PBCH block negotiates one symbol for the NR-PSS, one symbol for the NR-SSS that is multiplexed in the frequency domain with a portion of the NR-PBCH, and two symbols for the remaining NR-PBCH, where the four symbols are contiguously mapped and time division multiplexed.

[0092] NR-SS / PBCH is a unified design that includes NR-PSS and NR-SSS sequence designs for all supported carrier frequency ranges of NR. The transmission bandwidth of NR-PSS and NR-SSS (e.g., 12 PRB) is smaller than that of NR-PBCH (e.g., 20 PRB), and the total transmission bandwidth of the NR-SS / PBCH block is the same as that of NR-PBCH (e.g., 20 PRB). In NR initial cell selection, the UE assumes a default NR-SS / PBCH burst set periodicity of 20 ms, and to detect non-independent NR cells, the network provides the UE with one NR-SS / PBCH burst set periodicity information per frequency carrier, and, if possible, provides information for deriving measurement timing / duration.

[0093] In the case of NR unlicensed spectrum (including shared spectrum), due to the uncertainty of channel access, the transmission of NR-SS / PBCH blocks may be canceled or delayed depending on the results of clear channel assessment (CCA) in listen-before-talk (LBT). In the case of V2X sidelink synchronization or URLLC systems, the synchronization delay requirements are much more restrictive than LTE NR, so more accurate synchronization performance is required in one-shot detection to avoid more combinations of NR-SS / PBCH blocks and reduce synchronization latency. In the case of MTC or IoT systems, the operating SNR region is much lower than LTE NR, so better one-shot detection performance is required to avoid weak coverage issues.

[0094] In at least one of the aforementioned systems, performance (e.g., detection accuracy and synchronization latency) may be degraded if the synchronization signals for these systems are kept the same as for LTE NR. Thus, NR-SS / PBCH block enhancements and / or modifications for at least one of the aforementioned systems are necessary (other systems may use the same or different enhancement schemes as discussed in this disclosure). For example, the enhancements and / or modifications may be targeted to increase channel access opportunities, for example, for unlicensed spectrum. Also, for example, the enhancements and / or modifications may be targeted to improve one-shot detection accuracy of cell search and / or broadcasting, for example, for unlicensed / V2X / URLLC / MTC / IoT systems.

[0095] The main design consideration is whether to adopt a unified enhanced NR-SS / PBCH block design (e.g., configuration and / or mapping and / or multiplexing of the enhanced NR-SS / PBCH block) for different application scenarios (which may include different carrier frequency ranges, independent or non-independent, etc.).

[0096] In one embodiment, the design of the configuration / mapping / multiplexing in the enhanced NR-SS / PBCH block can be unified for all carrier frequency ranges (e.g., 5 GHz, 6 GHz, and 60 GHz unlicensed spectrum use the same design) and for all independent and non-independent scenarios. The unified design helps to minimize detector complexity. Note that the unified design of the enhanced NR-SS / PBCH block does not preclude other possible designs for the transmission period and / or LBT of the enhanced NR-SS / PBCH block. For example, the same configuration / mapping / multiplexing in the enhanced NR-SS / PBCH block may be used, but different transmission period and / or LBT procedures (if applicable) may be used for different carrier frequency ranges and / or independent and non-independent scenarios.

[0097] In other embodiments, the configuration / mapping / multiplexing design for the enhanced NR-SS / PBCH block is unified for all carrier frequency ranges (e.g., 5 GHz, 6 GHz, and 60 GHz unlicensed spectrum use the same design), but is different for standalone and non-standalone scenarios. For example, a unified configuration / mapping / multiplexing design for the enhanced NR-SS / PBCH block is used for standalone scenarios and all carrier frequency ranges, and another unified configuration / mapping / multiplexing design for the enhanced NR-SS / PBCH block is used for non-standalone scenarios and all carrier frequency ranges. It is noted that the unified design for the enhanced NR-SS / PBCH block does not preclude other possible transmission periodicity and / or LBT procedure (if applicable) designs for the enhanced NR-SS / PBCH block.

[0098] In yet another embodiment, the configuration / mapping / multiplexing in the enhanced NR-SS / PBCH block is unified for the standalone and non-standalone scenarios, but is different for different carrier frequency ranges (e.g., 5 GHz, 6 GHz, and 60 GHz unlicensed spectrum use different designs from each other). It is noted that the unified design of the enhanced NR-SS / PBCH block does not preclude the design of other possible transmission periodicities and / or LBT procedures (if applicable) for the enhanced NR-SS / PBCH block. For example, the same configuration / mapping / multiplexing in the enhanced NR-SS / PBCH block may be used for standalone and non-standalone scenarios, but different transmission periodicities and / or LBT procedures (if applicable).

[0099] In yet other embodiments, the configuration / mapping / multiplexing in the enhanced NR-SS / PBCH block is specific to each carrier frequency range (e.g., 5 GHz, 6 GHz, and 60 GHz unlicensed spectrum use different designs) and standalone / non-standalone scenarios.

[0100] Another important design consideration is the default period of the enhanced NR-SS / PBCH block (or equivalently, the default period of the enhanced NR-SS / PBCH burst set) from the detector's perspective. For enhanced NR-SS / PBCH blocks transmitted within a Discovery RS (DRS) Measurement Timing Configuration (DMTC), the default period of the enhanced NR-SS / PBCH block (or equivalently, the default period of the enhanced NR-SS / PBCH burst set) may be considered to be the default period of the DMTC, although the actual transmission of the enhanced NR-SS / PBCH block may not be strictly periodic.

[0101] In one embodiment, to enhance channel access opportunities (e.g., for NR unlicensed spectrum), the default period of the enhanced NR-SS / PBCH block (or equivalently, the default period of the enhanced NR-SS / PBCH burst set or the default period of the DMTC) may be reduced compared to the NR licensed spectrum. For example, the default period may be reduced to 10 ms or 5 ms.

[0102] In other embodiments, the default periodicity of the enhanced NR-SS / PBCH block (or equivalently, the default periodicity of the enhanced NR-SS / PBCH burst set or the default periodicity of the DMTC) may be kept the same as LTE NR (e.g., 20 ms). For example, the duration of the LBT procedure for the enhanced NR-SS / PBCH block may be minimized to improve channel access opportunities for NR unlicensed spectrum.

[0103] The next design consideration is repeated and / or additional and / or enhanced transmission of NR-PSS / SSS / PBCH (referred to as NR-ePSS / eSSS / ePBCH) within an enhanced NR-SS / PBCH block to improve one-shot synchronization / broadcasting performance (note that the signal / channel design of NR-ePSS / eSSS / ePBCH may be the same as NR-PSS / SSS / PBCH or the same as NR-PSS / SSS / PBCH for a particular scenario).

[0104] In one embodiment, the enhanced NR-SS / PBCH block consists of only NR-ePSS / eSSS / ePBCH.

[0105] In one example, the NR-ePSS / eSSS / ePBCH are time division multiplexed (wherein portions of the NR-eSSS and NR-ePBCH may be frequency division multiplexed in the same symbol), e.g., the NR-PSS / SSS / PBCH is replaced by the NR-ePSS / eSSS / ePBCH, but multiplexed and mapped in a manner similar to the LTE NR-SS / PBCH block.

[0106] In other examples, the NR-ePSS / eSSS / ePBCH are multiplexed and / or mapped differently than the LTE NR-SS / PBCH blocks, e.g., frequency division multiplexed with NR-ePSS / eSSS / ePBCH, or a mixture of time and frequency division multiplexing.

[0107] In another embodiment, the enhanced NR-SS / PBCH block is composed of at least one of the NR-PSS / SSS / PBCH and at least one of these enhanced NR-ePSS / eSSS / ePBCH.

[0108] In other embodiments, the NR-ePSS / eSSS / ePBCH is time division multiplexed with the NR-PSS / SSS / PBCH (note that there may be symbols in an enhanced NR-SS / PBCH block that includes FDMed NR-SSS / NR-PBCH and / or FDMed NR-eSSS / NR-ePBCH).

[0109] In one example, when both NR-ePSS and NR-PSS are supported in an enhanced NR-SS / PBCH block, for example, symbols mapped corresponding to NR-ePSS and NR-PSS are TDMed to be continuous, to facilitate implementation of NR-PSS / NR-ePSS joint detection in the time domain.

[0110] In another example, when more than one NR-ePSS is supported in an enhanced NR-SS / PBCH block, the symbols mapped to the NR-ePSS are TDM'd to be contiguous, e.g., to facilitate implementing NR-ePSS joint detection in the time domain.

[0111] In yet another example, when both NR-eSSS and NR-SSS are supported in an enhanced NR-SS / PBCH block, the symbols mapped corresponding to NR-eSSS and NR-SSS are TDM'd to be non-contiguous, for example, the symbol(s) between NR-eSSS and NR-SSS may be mapped to NR-PBCH / NR-ePBCH.

[0112] In yet another example, when more than one NR-eSSS is supported in an enhanced NR-SS / PBCH block, the symbols mapped to the NR-eSSS may be TDM'd to be non-contiguous, e.g., the symbol(s) between the NR-eSSS may be mapped to the NR-PBCH / NR-ePBCH.

[0113] In one embodiment, the NR-ePSS / eSSS / ePBCH is frequency division multiplexed with the LTE NR-PSS / SSS / PBCH.

[0114] In other embodiments, the NR-ePSS / eSSS / ePBCH is multiplexed with the LTE NR-PSS / SSS / PBCH in a mixed time division multiplexed and frequency division multiplexed manner.

[0115] In other embodiments, the enhanced NR-SS / PBCH block consists of only LTE NR-PSS / SSS / PBCH, for example, an enhanced NR-SS / PBCH block in an unlicensed spectrum consists of only NR-PSS and NR-SSS for a particular application scenario (e.g., a non-independent scenario).

[0116] In another embodiment, the NR-PSS / SSS / PBCH within an enhanced NR-SS / PBCH block are time division multiplexed.

[0117] It is noted that, in combination with the previous design considerations, the above embodiments can be applied to different application scenarios, for example, an enhanced NR-SS / PBCH block consisting of only LTE NR-PSS / SSS / PBCH is used for a non-standalone scenario, and an NR-SS / PBCH block consisting of LTE NR-PSS / SSS / PBCH and these enhanced NR-ePSS / eSSS / ePBCH is used for a stand-alone scenario.

[0118] Another design consideration for the enhanced NR-SS / PBCH block is the mapping scheme affected by possible LBT and / or possible additional transmission of enhanced NR-PSS / SSS / PBCH and / or transmission of control channels and / or being reserved as empty (e.g., reserved due to AGC issues or for CORESET). For an LTE NR-SS / PBCH block, the NR-PSS / SSS / PBCH is mapped to four consecutive symbols. For an enhanced NR-SS / PBCH block, with the possible introduction of enhanced NR-PSS / SSS / PBCH, one enhanced NR-SS / PBCH block can occupy more symbols compared to an LTE NR-SS / PBCH block. Additionally, depending on potential LBT between transmission of adjacent enhanced NR-SS / PBCH blocks (e.g., when considering unlicensed spectrum usage scenarios) and reserving possible locations for CORESET or control signals, the mapping of enhanced NR-SS / PBCH to slots may differ from LTE NR-SS / PBCH blocks (e.g., mapped to non-consecutive symbols or in a different order compared to LTE NR-SS / PBCH blocks).

[0119] In one embodiment, it is advantageous to design an enhanced NR-SS / PBCH block that is composed of consecutive symbols, e.g., when considering unlicensed spectrum usage scenarios, no LBT is required within the enhanced NR-SS / PBCH block.

[0120] In another embodiment, when considering the coexistence issue of spare and multiple neuroradio for CORESET or control channel, the enhanced NR-SS / PBCH block may be composed of non-contiguous symbols. In one example, when considering an unlicensed spectrum usage scenario, the gap between symbol groups in the enhanced NR-SS / PBCH block is shorter than the maximum gap without LBT (e.g., 16us for 5GHz, 8us for 60GHz), which makes the gaps in the enhanced NR-SS / PBCH block unnecessary for LBT. In another example, when considering an unlicensed spectrum usage scenario, the gap between symbol groups in the enhanced NR-SS / PBCH block is shorter than the maximum gap without LBT (e.g., 16us for 5GHz, 8us for 60GHz), which makes the gaps in the enhanced NR-SS / PBCH block unnecessary for LBT.

[0121] In other embodiments, possible gaps within an enhanced NR-SS / PBCH block may not have the same design for different enhanced NR-SS / PBCH blocks, for example, gap locations within an enhanced NR-SS / PBCH block may be different for different enhanced NR-SS / PBCH blocks even if the components of the enhanced NR-SS / PBCH block (e.g., signals / channels within the enhanced NR-SS / PBCH block) are the same.

[0122] In general, an enhanced NR-SS / PBCH block may consist of 0-1 symbols mapped to NR-PSS, 0-1 symbols mapped to NR-SSS (within each symbol the enhanced NR-SS / PBCH block may be FDM'd with NR-PBCH or NR-ePBCH), 0-2 symbols mapped to NR-ePSS, 0-2 symbols mapped to NR-eSSS (within each symbol the enhanced NR-SS / PBCH block may be FDM'd with NR-PBCH or NR-ePBCH), 0-2 symbols fully mapped to NR-PBCH (including the DMRS of the enhanced NR-SS / PBCH block) or 0-8 symbols fully mapped to NR-ePBCH (including the DMRS of the enhanced NR-SS / PBCH block), and 0-G symbols (G is an integer) for the gap.

[0123] The specific number of symbols for each signal / channel / gap may be determined from the application scenario (e.g., utilization scenario including at least one of unlicensed spectrum / V2X sidelink / URLLC / MTC / IoT, and / or carrier frequency range, and / or independent / non-independent). Examples of enhanced NR-SS / PBCH block configurations / mapping / multiplexing are illustrated in Figures 13 to 19, which correspond to enhanced NR-SS / PBCH blocks having 2 to 8 symbols (symbols not counting gaps), respectively, and more examples for enhanced NR-SS / PBCH block configurations / mapping / multiplexing are illustrated in Figure 20, which corresponds to an enhanced NR-SS / PBCH block having 14 symbols (i.e., slots including potential spare empty symbols), where the above design considerations have been taken into account.

[0124] In one embodiment, all signals and / or channels of an enhanced NR-SS / PBCH block are transmitted using the same antenna port. Note that Figures 13-20 may not be an exhaustive list of all supported designs covered by this disclosure.

[0125] Note that if a wider BW can be supported for the enhanced NR-SS / PBCH block, the BW of each signal / channel in the figures is expanded accordingly. For example, if the BW of the enhanced NR-SS / PBCH block is 40 PRBs, the BW of 20 PRBs in the figures can be replaced with 40 PRBs or 12 PRBs can be replaced with 24 PRBs without any change in the time domain multiplexing pattern.

[0126] Note that if a smaller BW is supported for the enhanced NR-SS / PBCH block, the BW of each signal / channel in the drawing is reduced to the center PRBs corresponding to the supported BW of the enhanced NR-SS / PBCH block. For example, if the BW of the enhanced NR-SS / PBCH block is 12 PRBs, then all signals / channels in the drawing are reduced to the center 12 PRBs, resulting in no NR-PBCH or NR-ePBCH that is FDMed with NR-SSS or NR-eSSS in the drawing.

[0127] The symbols or some of the symbols mapped to the NR-PBCH / NR-ePBCH in the drawings may also include DMRS for the NR-PBCH / NR-ePBCH, where in one embodiment, the REs for the DMRS may be FDMed with the REs for the NR-PBCH / NR-ePBCH, or in another embodiment, may be TDMed with the REs for the NR-PBCH / NR-ePBCH.

[0128] A control resource set (CORESET) should be configured for receiving common control channels such as remaining minimum system information (RMSI), other system information (OSI), etc. One CORESET configuration may be provided at least for RMSI scheduling via a physical broadcast channel (PBCH), e.g., a master information block (MIB).

[0129] A CORESET may be characterized by slot timing, OFDM symbol number and frequency resource in each slot. Such CORESET characteristics may be indicated or pre-configured for each CORESET. In the case of RMSI / OSI scheduling, the CORESET characteristics may be provided in the PBCH. Among these CORESET characteristics configured by the PBCH, the OFDM symbol number and frequency resource may be commonly applied to all common channels (e.g., system information blocks (SIBx), etc.), but the slot timing may be specifically determined for different SIBx.

[0130] The present disclosure considers configuration of frequency / time resources for RMSIs and CORESETs (which can potentially be configured with slot timing and / or orthogonal frequency division multiplexing (OFDM) symbol numbers), including physical downlink control channel (PDCCH) scheduling RMSIs, which may also be reused for SIBs if possible.

[0131] Note that in this disclosure, the notation x:y:(x+(n-1)*y) refers to the length-n vector (x, x+y, x+2y, ..., x+(n-2)y, x+(n-1)y).

[0132] At least the following components of the present disclosure, associated with RMSIs including PDCCH scheduling RMSIs and frequency / time resources for the CORESET (abbreviated as "RMSI resources" in the remainder of this specification), are considered to be directly or indirectly configured with bits in the NR-PBCH MIB:

[0133] Configuration components et al.

[0134] The first component for configuring the RMSI resource may be a parameter of the RMSI resource.

[0135] In one embodiment, the RMSI resource parameter can be configured by a separate bit in the MIB.

[0136] In other embodiments, the RMSI resource paradigm can be configured in other configurations to reduce payload size. For example, if the configuration of all RMSI CORESET configurations is captured in the example table shown in this disclosure, the effective payload size of the RMSI paradigm may be less than 1 bit by limiting the combination of SS / PBCH block paradigm and RMSI resource.

[0137] A second component for configuring the RMSI resource may be a multiplexing pattern of the RMSI resource.

[0138] Figure 13A illustrates an exemplary TDM multiplexing pattern 1300 according to an embodiment of the present disclosure. The embodiment of the TDM multiplexing pattern 1300 illustrated in Figure 13A is for illustrative purposes only. Figure 13A does not limit the scope of the present disclosure to any particular implementation.

[0139] In one embodiment of the multiplexing pattern, the SS / PBCH blocks and RMSI resources are TDMed, where the center of the SS / PBCH block BW and the center of the RMSI resource BW may or may not be aligned, and the SS / PBCH block BW may or may not be the same as the RMSI resource BW. An example is shown in FIG. 13A.

[0140] 13B is a diagram illustrating an example FDM multiplexing pattern 1320 according to an embodiment of the present disclosure. The embodiment of the FDM multiplexing pattern 1320 shown in FIG. 13B is for illustration purposes only. FIG. 13B does not limit the scope of the present disclosure to any particular implementation.

[0141] In another embodiment of the multiplexing pattern, the SS / PBCH blocks and RMSI resources are FDMed, where the symbols for the SS / PBCH blocks and the symbols for the RMSI resources may or may not be the same, and the SS / PBCH block BW may or may not be the same as the RMSI resource BW. An example is shown in Figure 13B.

[0142] In one example, the timing offset in FIG. 13B can be 0, which causes the PDSCHs of CORESET and RMSI to be FDM'd with the SS / PBCH block.

[0143] In another example, the timing offset in FIG. 13B may be greater than 0, whereby the CORESET is TDM and FDMed with the SS / PBCH block and the PDSCH of the RMSI is FDMed with the SS / PBCH block.

[0144] Regardless of whether the first symbol for the SS / PBCH block and the first symbol for the RMSI resource are the same or not, the frequency offset indication scheme may be the same, for example, the frequency offset indication scheme for the above two examples of this embodiment may be the same.

[0145] 13C is a diagram illustrating an example hybrid TDM and FDM multiplexing pattern 1340 according to an embodiment of the present disclosure. The embodiment of the hybrid TDM and FDM multiplexing pattern 1340 shown in FIG. 13C is for illustration purposes only. FIG. 13C does not limit the scope of the present disclosure to any particular implementation.

[0146] In other embodiments, the SS / PBCH blocks and RMSI resources are simultaneously TDM and FDMed (eg, hybrid TDM and FDMed), an example of which is shown in FIG.

[0147] In one example of this embodiment, the RMSI CORESET can be purely TDMed with the SS / PBCH block, even if the RMSI resource is hybrid TDM and FDMed with the SS / PBCH block. In this case, the timing and frequency offset configuration can refer to the TDM case.

[0148] In another example of the above embodiment, multiple RMSI resource blocks (e.g., two blocks on each side of the SS / PBCH block) are purely FDMed with the SS / PBCH block. In this case, the timing and frequency offset configurations can refer to the FDM case with some appropriate modifications.

[0149] A third component for configuring the RMSI resource may be the bandwidth of the CORESET including the PDCCH scheduling RMSI (e.g., RMSI CORESET BW), which may be expressed in terms of the subcarrier spacing of the RMSI in terms of the number of physical resource blocks (PRBs).

[0150] In one embodiment, when the frequency / time resources for the CORESET form a rectangle in the RE grid (e.g., in the pure TDM and FDM cases as in Figs. 13A and 13B), the number of PRBs for the CORESET can be configured in terms of the PRBs together with the CORESET BW in terms of the OFDM symbols. Note that for a given total number of PRBs for the RMSI CORESET, the CORESET BW can be determined based on the neural network of the RMSI CORESET. In one subembodiment of this embodiment, the effective BW of the RMSI CORESET is 24 PRBs or more in terms of the neural network of the SS / PBCH block.

[0151] In one example, if the total number of PRBs for CORESET is 12 PRBs, this can be configured using one OFDM symbol with 12 PRB CORESET BW or two OFDM symbols with 6 PRB CORESET BW.

[0152] In another example, if the total number of PRBs for CORESET is 24 PRBs, this can be configured using one OFDM symbol with 24 PRB CORESET BW or two OFDM symbols with 12 PRB CORESET BW.

[0153] In yet another example, if the total number of PRBs for a CORESET is 48 PRBs, this can be configured using one OFDM symbol with a PRB CORESET BW of 48, or two OFDM symbols with a PRB CORESET BW of 24, or three symbols with a PRB CORESET BW of 16.

[0154] In yet another example, if the total number of PRBs for a CORESET is 72 PRBs, this can be configured using 3 OFDM symbols with a PRB CORESET BW of 24.

[0155] In yet another example, if the total number of PRBs for a CORESET is 96 PRBs, this can be configured using one OFDM symbol with a PRB CORESET BW of 96, or two OFDM symbols with a PRB CORESET BW of 48, or three symbols with a PRB CORESET BW of 32.

[0156] In yet another example, if the total number of PRBs for the CORESET is 144 PRBs, this can be configured using 3 OFDM symbols with a PRB CORESET BW of 48.

[0157] In other embodiments, the number of PRBs for a CORESET may be configured as a single number that is the total number of PRBs (e.g., N_CORESET_PRB = 12 or 24 or 48 or 96 PRBs) and may be additionally configured with other components to define the RE mapping pattern.

[0158] For example, the total number of PRBs for CORESET may be configured by N_CORESET_PRBPRB, and may additionally be configured with a hybrid TDM and FDM pattern (eg, similar to FIG. 13C) to define RE mapping.

[0159] A fourth component for configuring the RMSI resource may be timing information for monitoring the RMSI resource.

[0160] In one embodiment of this component, one configuration can be a timing offset between the SS / PBCH block and the RMSI resource, which can be configured by the number of OFDM symbols (e.g., in terms of SS / PBCH block neuroradiology or RMSI CORESET neuroradiology), or by the number of slots (e.g., in terms of SS / PBCH block neuroradiology or RMSI CORESET neuroradiology), or by time (e.g., in terms of ms), which indicates the difference between the starting position of the SS / PBCH block and the RMSI resource (or CORESET position). Note that such a timing offset configuration can be the same or different in the TDM / FDM / hybrid case.

[0161] For example, in the TDM case, the timing offset may be several ms or more.

[0162] In another example, in the FDM case, the timing offset may be 0 or less by up to a few OFDM symbols.

[0163] In yet another example, in the hybrid case, the timing offset may be small as in the FDM case.

[0164] In other embodiments of such components, other configurations may be the periodicity of monitoring the RMSI resource in the time domain.

[0165] A fifth component for configuring the RMSI resource may be a frequency offset between the SS / PBCH block and the RMSI resource (eg, the RMSI CORESET).

[0166] The definition of the frequency offset configuration may be the same or different in the multiplexing cases, including the TDM / FDM / hybrid case. For example, one of the following embodiments is commonly used for the TDM / FDM / hybrid case. In another embodiment, one of the following embodiments is used to define the frequency offset for the TDM case, and one of the following embodiments is used for the FDM / hybrid case. Also, knowing the SS / PBCH block BW and the RMSI resource BW, the following frequency offset definitions can be corresponding (one can be subtracted from the other).

[0167] In one embodiment, the frequency offset can be defined by the difference between the center of the SS / PBCH block BW and the center of the RMSI resource BW, which can be in terms of number of PRBs or REs or Hz. In some cases (e.g., SS / PBCH block BW=20 PRBs and RMSI resource BW is an even number), this definition is the same as the center PRB grid offset between the SS / PBCH block BW and the RMSI resource BW.

[0168] In other embodiments, the frequency offset can be defined by the difference between the lowest / highest RE / PRB grid of the SS / PBCH block and the lowest / highest RE / PRB grid of the RMSI resource, which can be in terms of number of PRBs or REs or Hz.

[0169] ΔF (from the perspective of RMSI CORESET neuroradiology) is defined as ΔF = F_ref + ΔF', where F_ref indicates the frequency offset reference (from the perspective of RMSI CORESET neuroradiology) and may be defined as a constant / predefined value in the specification, or may be indicated / configured by other configuration, or may be known from other information, and ΔF' (from the perspective of RMSI CORESET neuroradiology) is the part that needs to be indicated / configured for the frequency offset reference.

[0170] The range that needs to be configured for the frequency offset ΔF (e.g., defined as the vector ΔF_Range) is actually determined by the range for ΔF' (e.g., defined as the vector ΔF'_Range), and since the frequency offset reference is known, the relationship between the ranges is given by ΔF_Range = F_ref + ΔF'_Range.

[0171] The configuration of the frequency offset can depend on the relationship between the neuroradio and BW of the SS / PBCH block and the RMSI CORESET as well as different multiplexing schemes. The following embodiments for different multiplexing patterns are considered in this disclosure. Note that in one example, multiple embodiments from the TDM and FDM subcases can be supported simultaneously.

[0172] In TDM subcase 1, the minimum channel BW is equal to or greater than the RMSI CORESET BW. For this subcase, multiple embodiments are considered in terms of the relative positions of possible SS blocks, the RMSI CORESET and the minimum channel bandwidth, which additionally determines the frequency offset criteria and the frequency offset range (i.e., ΔF′_Range) that needs to be configured.

[0173] 14 is a diagram illustrating an example configuration of a frequency offset 1400 for a first case of a TDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the frequency offset 1400 configuration shown in FIG. 14 is for illustration purposes only. FIG. 14 does not limit the scope of the present disclosure to any particular implementation.

[0174] In a first embodiment of TDM subcase 1 (e.g., TDM-embodiment 1.1), the frequency location of the RMSI CORESET can be arbitrary within the minimum channel BW (as shown in FIG. 14, where 1402, 1403, 1404, 1405 and 1406 are all examples for the relative locations of the RMSI resources considered in this subembodiment. In this embodiment, the frequency offset reference can be determined to F_ref=0 (i.e., ΔF=ΔF′), and the frequency offset range for ΔF′ can be determined to ΔF′_Range at PRB=(minimum channel BW at PRB−SS / PBCH block BW at PRB)*R_SCS, where the minimum channel BW is defined in SS / PBCH block neuroradio, ΔF′_Range is defined in RMSI CORESET neuroradio, and R_SCS=SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of the SS / PBCH block and the RMSI CORESET.

[0175] In a second embodiment of TDM subcase 1 (e.g., TDM-embodiment 1.2), the frequency locations of the RMSI CORESET may be restricted within a subset of the minimum channel BW (possible frequency locations are subsets of TDM embodiment 1.1). For example, the frequency locations of the RMSI CORESET can be configured such that the SS / PBCH block BW is a subset of the RMSI CORESET BW at the PRB level (note that this configuration already guarantees that the entire RMSI resource can be obtained within the minimum channel BW for the particular configuration).

[0176] 15 is a diagram illustrating an example configuration of frequency offset 1500 for a second case of a TDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 1500 shown in FIG. 15 is for illustration purposes only. FIG. 15 does not limit the scope of the present disclosure to any particular implementation.

[0177] As shown in Fig. 15, 1502, 1503 and 1504 are all examples for the relative positions of RMSI resources considered in this subembodiment. In this embodiment, the frequency offset reference can be determined as F_ref = 0 (i.e., ΔF = ΔF'), and the frequency offset range for ΔF' can be determined as ΔF'_Range at PRB = max (0, (RMSI CORESET BW at PRB - SS / PBCH block BW at PRB * R_SCS)), where ΔF'_Range is defined in the RMSI CORESET neuroradio and R_SCS = SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of SS / PBCH block and RMSI CORESET. If the RMSI CORESET BW is smaller than or equal to the SS / PBCH block BW, ΔF'_Range at PRB is 0 (meaning that no PRB level indication is required).

[0178] 16 is a diagram illustrating an example configuration of frequency offset 1600 for a third case of a TDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 1600 shown in FIG. 16 is for illustration purposes only. FIG. 16 does not limit the scope of the present disclosure to any particular implementation.

[0179] In a third embodiment of TDM subcase 1 (e.g., TDM-embodiment 1.3), the frequency location of the RMSI CORESET is restricted within the minimum channel BW (possible frequency locations are a subset of TDM-embodiment 1.1). For example, the frequency location of the RMSI CORESET can be configured such that the BW portion of the SS / PBCH block BW that exceeds the RMSI CORESET BW does not exceed one PRB from the RMSI CORESET neural radio point of view (this one PRB is used for the floating synchronization function to indicate the possible offset between the SS / PBCH block PRB boundary and the RMSI CORESET PRB boundary). It should be noted that this configuration already ensures that the entire RMSI resource can be obtained within the minimum channel BW in the particular configuration.

[0180] As shown in Fig. 16, 1602, 1603 and 1604 are examples of relative positions of RMSI resources considered in this subembodiment, where floating synchronization can be applied simultaneously to SS / PBCH blocks. In this embodiment, the frequency offset reference can be determined as F_ref=0 (i.e., ΔF=ΔF'), and the frequency offset range for ΔF' can be determined as ΔF'_Range in PRB=max(1,(RMSI CORESET in PRB+1 BW-SS / PBCH block in PRB BW*R_SCS)), where ΔF'_Range is defined in the RMSI CORESET neuroradio and R_SCS=SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of the SS / PBCH block and the RMSI CORESET. If the RMSI CORESET BW is smaller than or equal to the SS / PBCH block BW, ΔF′_Range in the PRB is 1 (meaning that no PRB level indication is needed within one PRB, only RE level indication is needed).

[0181] In TDM subcase 2, the minimum channel BW is smaller than the RMSI CORESET BW. For this subcase, multiple embodiments are considered in terms of the relative positions of possible SS blocks, the RMSI CORESET and the minimum channel bandwidth, which additionally determines the frequency offset criteria and the frequency offset range (i.e., ΔF′_Range) that needs to be configured.

[0182] 17 is a diagram illustrating an example configuration of frequency offset 1700 for a fourth case of a TDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 1700 shown in FIG. 17 is for illustration purposes only. FIG. 17 does not limit the scope of the present disclosure to any particular implementation.

[0183] In a first embodiment of TDM subcase 2 (e.g., TDM embodiment 2.1), the frequency location of the SS / PBCH block may be arbitrary within the RMSI CORESET BW. As shown in FIG. 17, 1701, 1702, ..., 1704 are all examples for the relative location of the SS / PBCH block considered in this embodiment. In this embodiment, the frequency offset reference may be determined as F_ref = 0 (i.e., ΔF = ΔF'), and the frequency offset range for ΔF' may be determined as ΔF'_Range at PRB = RMSI CORESET BW at PRB - SS / PBCH block BW at PRB * R_SCS, where ΔF'_Range is defined in the RMSI CORESET neural network, and R_SCS = SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing value of the SS / PBCH block and the RMSI CORESET.

[0184] In a second embodiment of TDM subcase 2 (e.g., TDM-embodiment 2.2), the frequency location of the SS / PBCH block may be restricted within a portion of the RMSI CORESET BW (possible frequency locations are a subset of TDM-embodiment 2.1). For example, the frequency location of the RMSI CORESET may be configured such that the SS / PBCH block BW is a subset of a portion of the RMSI CORESET BW at the PRB level, where the portion of the RMSI CORESET BW may be referred to as a "restricted BW" and may be a value predefined in the specification to reduce overhead. In one example, the restricted BW may be 24 PRBs from the SS / PBCH block neural network perspective, which indicates a minimum value for the BW that allows the entire RMSI CORESET BW to be within the minimum UE BW.

[0185] 18 is a diagram illustrating an example configuration of frequency offset 1800 for a fifth case of a TDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 1800 shown in FIG. 18 is for illustration purposes only. FIG. 18 does not limit the scope of the present disclosure to any particular implementation.

[0186] In another example, the constrained BW can be the same as the minimum channel BW, and the entire RMSI CORESET BW can also be within the minimum UE BW. As shown in Fig. 18, 1801, 1802, 1803 and 1804 are all examples for the relative positions of SS / PBCH blocks considered in this embodiment. In this embodiment, the frequency offset reference indicates the center offset of the constrained BW relative to the RMSI CORESET BW, which is determined by the frequency position of the predefined constrained BW, and is a value predefined in the specification, for example, F_ref=ΔCORESET_BW_Offset (defined in the RMSI CORESET neuroradio).

[0187] In one example, the limited BW may be limited to the center of the RMSI CORESET BW (i.e., the centers of the RMSI CORESET BW and the limited BW are aligned) such that F_ref=ΔCORESET_BW_Offset=0. In another example, the limited BW may be limited starting from one end such that F_ref=ΔCORESET_BW_Offset=CORESET BW / 2-Limited BW / 2 or F_ref=ΔCORESET_BW_Offset=-CORESET BW / 2+Limited BW / 2 depending on which end it starts from. In this embodiment, the total frequency offset range for ΔF' can be determined as ΔF'_Range at PRB = limited BW at PRB - SS / PBCH block BW at PRB * R_SCS, where the limited BW and ΔF'_Range are defined in the RMSI CORESET neuroradiography, and R_SCS = SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of the SS / PBCH block and the RMSI CORESET.

[0188] In a third embodiment of TDM subcase 2 (e.g., TDM-embodiment 2.3), the frequency location of the SS / PBCH block is restricted within a portion of the RMSI CORESET BW (possible frequency locations are a subset of TDM-embodiment 2.1), and a potential additional offset is indicated by up to one PRB from the RMSI CORESET neuroradiographic point of view (this one PRB is used for the floating synchronization function to indicate the possible offset between the SS / PBCH block PRB boundary and the RMSI CORESET PRB boundary).

[0189] For example, the frequency location of the RMSI CORESET may be configured such that the SS / PBCH block BW is a subset of a portion of the RMSI CORESET BW, excluding a potential additional offset of up to 1 PRB larger from the RMSI CORESET neural radio perspective, where the portion of the RMSI CORESET BW may denote a "limited BW" and may be a value predefined in the specification to reduce overhead.

[0190] 19 is a diagram illustrating an example configuration of frequency offset 1900 for a sixth case of a TDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 1900 shown in FIG. 19 is for illustration purposes only. FIG. 19 does not limit the scope of the present disclosure to any particular implementation.

[0191] In one example, the restricted BW can be 24 PRBs from the SS / PBCH block neural network perspective, which refers to the minimum value for the BW that allows the entire RMSI CORESET BW to be within the minimum UE BW. In another example, the restricted BW can be the same as the minimum channel BW, and the entire RMSI CORESET BW can be within the minimum UE BW. As shown in Figure 19, 1901, 1902, 1903, and 1904 are all examples of relative positions of SS / PBCH blocks considered in this embodiment.

[0192] In this embodiment, the frequency offset reference indicates the center offset of the restricted BW relative to the RMSI CORESET BW, which is determined by the frequency location of the predefined restricted BW, and is a value predefined in the specification, for example, F_ref=ΔCORESET_BW_Offset (defined in the RMSI CORESET neuroradio).

[0193] In one example, the limited BW may be limited to the center of the RMSI CORESET BW (i.e., the centers of the RMSI CORESET BW and the limited BW are aligned) such that F_ref=ΔCORESET_BW_Offset=0. In another example, the limited BW may be limited starting from one end such that F_ref=ΔCORESET_BW_Offset=CORESET BW / 2-Limited BW / 2 or F_ref=ΔCORESET_BW_Offset=-CORESET BW / 2+Limited BW / 2 depending on which end it starts from. In this embodiment, the total frequency offset range for ΔF' can be determined as ΔF'_Range at PRB = limited BW at PRB + 1-SS / PBCH block BW at PRB * R_SCS, where the limited BW and ΔF'_Range are defined in the RMSI CORESET neuroradiography, and R_SCS = SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of the SS / PBCH block and the RMSI CORESET.

[0194] In FDM subcase 1, a single RMSI resource block is FDMed with the SS / PBCH block and can be on either side of the SS / PBCH block in the frequency domain. For this subcase, multiple embodiments are considered in terms of possible relative SS block positions, RMSI CORESET and minimum channel bandwidth, which additionally determine the frequency offset criteria and the frequency offset range (i.e., ΔF′_Range) that needs to be configured.

[0195] In a first embodiment of FDM subcase 1 (e.g., FDM-embodiment 1.1), the frequency location of the SS / PBCH blocks can be arbitrary within the minimum channel BW, and the RMSI CORESET blocks are multiplexed outside the minimum channel BW with a potentially predefined constant gap ΔGap (defined in the RMSI CORESET neuroradio).

[0196] 20 is a diagram illustrating an example configuration of frequency offset 2000 for a first case of FDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 2000 shown in FIG. 20 is for illustration purposes only. FIG. 20 does not limit the scope of the present disclosure to any particular implementation.

[0197] As shown in Figure 20, 2001, 2002, 2003 and 2004 are all examples for the relative positions of SS / PBCH blocks considered in this embodiment. In one example, the gap is 0 PRB. In another example, the gap is determined to be within 1 PRB and aligned with the RE level offset value to allow floating synchronization (e.g., if the RE level offset is defined as -6:1:5 or -6:1:6, then ΔGap=6RE; if the RE level offset is defined as 0:1:11 or 0:1:12, then ΔGap=0RE; if the RE level offset is defined as -11:1:0, then ΔGap=11RE; if the RE level offset is defined as -12:1:0, then ΔGap=12RE).

[0198] In this embodiment, the frequency offset reference can be determined as the midpoint offset between the RMSI CORESET BW and the minimum channel BW such that F_ref=RMSI CORESET BW / 2+ΔGap+minimum channel BW / 2, and the frequency offset range for ΔF′ can be determined as ΔF′_Range in PRB=(minimum channel BW in PRB−SS / PBCH block BW in PRB)*R_SCS, where the minimum channel BW is defined in the SS / PBCH block neuroradio, ΔF′_Range is defined in the RMSI CORESET neuroradio, and R_SCS=SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of the SS / PBCH block and the RMSI CORESET.

[0199] In one possible variation of this embodiment, the multiplexing pattern of RMSI resources with SS / PBCH blocks can be on either side of the SS / PBCH blocks, and therefore the frequency offset reference can be RMSI CORESET BW / 2+ΔGap+Min Channel BW / 2 or -(RMSI CORESET BW / 2+ΔGap'+Min Channel BW*R_SCS / 2), where ΔGap' is a predefined constant gap. One consideration is that ΔGap'+ΔGap=12RE to allow floating synchronization (e.g., if ΔGap=6RE is selected to be aligned with RE level offset defined as -6:1:5, then with RE level offset defined as -5:1:6 to be aligned with this setting, ΔGap'=6RE).

[0200] In another example, if ΔGap=6RE is selected to be aligned with a RE level offset defined as -6:1:6, then ΔGap′=6RE will result in a RE level offset defined as -6:1:6 to be aligned with this setting. In another example, if ΔGap=0RE is selected to be aligned with a RE level offset defined as 0:1:11, then ΔGap′=12RE will result in a RE level offset defined as -11:1:0 to be aligned with this setting. In another example, if ΔGap=0RE is selected to be aligned with a RE level offset defined as 0:1:12, then ΔGap′=12RE will result in a RE level offset defined as -12:1:0 to be aligned with this setting. In yet another example, if ΔGap=12RE is selected to be aligned with a RE level offset defined as -12:1:0, then ΔGap′=0RE will result in a RE level offset defined as 0:1:12 to be aligned with this setting. This variant doubles the number of configurations compared to restricting RMSI resources on a particular side of an SS / PBCH block predefined in the specification.

[0201] In a second embodiment of FDM subcase 1 (e.g., FDM embodiment 1.2), the frequency location of the SS / PBCH blocks can be within the minimum channel BW and the RMSI CORESET blocks can be (partially) multiplexed within the minimum channel BW with a potentially predefined constant gap ΔGap (defined in the RMSI CORESET neuroradio) in the frequency domain.

[0202] 21 is a diagram illustrating an example configuration of frequency offset 2100 for a second case of FDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 2100 shown in FIG. 21 is for illustration only. FIG. 21 does not limit the scope of the present disclosure to any particular implementation.

[0203] As shown in FIG. 21, 2101, 2102 and 2103 are all examples for the relative positions of SS / PBCH blocks considered in this embodiment. In one example, the gap is 0 PRB. In another example, the gap is determined to be within 1 PRB and aligned with the RE level offset value to allow floating synchronization (e.g., if the RE level offset is defined as -6:1:5 or -6:1:6, then ΔGap=6RE; if the RE level offset is defined as 0:1:11 or 0:1:12, then ΔGap=0RE; if the RE level offset is defined as -11:1:0, then ΔGap=11RE; if the RE level offset is defined as -12:1:0, then ΔGap=12RE). In addition to the RE reserved to allow floating synchronization, another possible gap component could be 1 PRB to allow FDM for mixed neuroradiation scenarios. In this embodiment, the frequency offset reference can be determined as F_ref=RMSI CORESET BW / 2+ΔGap+SS / PBCH block BW*R_SCS / 2, and the frequency offset range for ΔF′ can be determined as ΔF′_Range=0 at the PRB (which means the relative position is fixed at the PRB level), where ΔF′_Range is defined in the RMSI CORESET neural network, and R_SCS=SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of the SS / PBCH block and the RMSI CORESET.

[0204] In one possible variation of this embodiment, the multiplexing pattern of RMSI resources with SS / PBCH blocks can be on either side of the SS / PBCH blocks, and thus the frequency offset reference can be RMSI CORESET BW / 2+ΔGap+SS / PBCH block BW*R_SCS / 2 or −(RMSI CORESET BW / 2+ΔGap′+SS / PBCH block BW*R_SCS / 2), where ΔGap′ is a predefined constant gap. In one consideration, ΔGap′+ΔGap=11RE to allow for floating synchronization (e.g., if ΔGap=6RE is selected to be aligned with a RE level offset defined as −6:1:5, then with a RE level offset defined as −5:1:6, then ΔGap′=6RE is aligned with this setting. In another example, if ΔGap=6RE is selected to be aligned with a RE level offset defined as −6:1:6, then with a RE level offset defined as −6:1:6, then ΔGap′=6RE is aligned with this setting).

[0205] In another example, if ΔGap=0RE is selected to be aligned with an RE level offset defined as 0:1:11, then ΔGap′=12RE with an RE level offset defined as −11:1:0 to be aligned with this configuration. In another example, if ΔGap=0RE is selected to be aligned with an RE level offset defined as 0:1:12, then ΔGap′=12RE with an RE level offset defined as −12:1:0 to be aligned with this configuration. In yet another example, if ΔGap=12RE is selected to be aligned with an RE level offset defined as −12:1:0, then ΔGap′=0RE with an RE level offset defined as 0:1:12 to be aligned with this configuration. This variant doubles the number of configurations compared to restricting RMSI resources on a particular side of an SS / PBCH block predefined in the specification.

[0206] In a third embodiment of FDM subcase 1 (e.g., FDM-embodiment 1.3), the frequency location of the SS / PBCH block may be within the minimum channel BW, and the RMSI CORESET block may be (partially) multiplexed within the minimum channel BW with a potentially predefined constant gap ΔGap (defined in the RMSI CORESET neuroradio), where the SS / PBCH block has a potential additional offset that may be displayed up to one PRB larger from the RMSI CORESET neuroradio perspective (this one PRB is used for the floating synchronization function to indicate the possible offset between the SS / PBCH block PRB boundary and the RMSI CORESET PRB boundary).

[0207] 22 is a diagram illustrating an example configuration of frequency offset 2200 for a third case of FDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 2200 shown in FIG. 22 is for illustration purposes only. FIG. 22 does not limit the scope of the present disclosure to any particular implementation.

[0208] As shown in FIG. 22, 2201, 2202 and 2203 are all examples for the relative positions of SS / PBCH blocks considered in this embodiment. In one example, the gap is 0 PRB. In another example, the gap is determined to be within 1 PRB and aligned with the RE level offset value to allow floating synchronization (e.g., if the RE level offset is defined as -6:1:5 or -6:1:6, then ΔGap=6RE; if the RE level offset is defined as 0:1:11 or 0:1:12, then ΔGap=0RE; if the RE level offset is defined as -11:1:0, then ΔGap=11RE; if the RE level offset is defined as -12:1:0, then ΔGap=12RE). In this embodiment, the frequency offset reference can be determined as F_ref=RMSI CORESET BW / 2+ΔGap+SS / PBCH block BW*R_SCS / 2, and the frequency offset range for ΔF' can be determined as ΔF'_Range=1 in the PRB, where ΔF'_Range is defined in the RMSI CORESET neuroradio and R_SCS=SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of the SS / PBCH block and the RMSI CORESET.

[0209] In one possible variation of this embodiment, the multiplexing pattern of RMSI resources with SS / PBCH blocks can be on either side of the SS / PBCH blocks, and thus the frequency offset reference can be RMSI CORESET BW / 2+ΔGap+SS / PBCH block BW*R_SCS / 2 or −(RMSI CORESET BW / 2+ΔGap′+SS / PBCH block BW*R_SCS / 2), where ΔGap′ is a predefined constant gap. In one consideration, ΔGap′+ΔGap=11RE to allow for floating synchronization (e.g., if ΔGap=6RE is selected to be aligned with a RE level offset defined as −6:1:5, then with a RE level offset defined as −5:1:6, then ΔGap′=6RE is aligned with this setting. In another example, if ΔGap=6RE is selected to be aligned with a RE level offset defined as −6:1:6, then with a RE level offset defined as −6:1:6, then ΔGap′=6RE is aligned with this setting).

[0210] In another example, if ΔGap=0RE is selected to be aligned with an RE level offset defined as 0:1:11, then ΔGap′=12RE with an RE level offset defined as −11:1:0 to be aligned with this configuration. In another example, if ΔGap=0RE is selected to be aligned with an RE level offset defined as 0:1:12, then ΔGap′=12RE with an RE level offset defined as −12:1:0 to be aligned with this configuration. In yet another example, if ΔGap=12RE is selected to be aligned with an RE level offset defined as −12:1:0, then ΔGap′=0RE with an RE level offset defined as 0:1:12 to be aligned with this configuration. In this variant, the number of configurations is doubled compared to restricting RMSI resources on a particular side of an SS / PBCH block predefined in the specification.

[0211] In FDM subcase 2, multiple RMSI resource blocks (e.g., two) are FDMed with the SS / PBCH block and can be located in both the SS / PBCH block in the frequency domain. For this subcase, multiple embodiments are considered in terms of possible relative positions of SS blocks, RMSI CORESET and minimum channel bandwidth, which additionally determine the frequency offset criteria and the frequency offset range (i.e., ΔF′_Range) that needs to be configured.

[0212] In a first embodiment of FDM subcase 2 (e.g., FDM-embodiment 2.1), the frequency location of the SS / PBCH block can be arbitrary within the minimum channel BW, and multiple RMSI CORESET blocks (e.g., two blocks on each side of the SS / PBCH block) are multiplexed outside the minimum channel BW with potentially predefined constant gaps ΔGap1 and ΔGap2 (both defined in the RMSI CORESET neural network) in the frequency domain.

[0213] 23 is a diagram illustrating an example configuration of frequency offset 2300 for a fourth case of FDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 2300 shown in FIG. 23 is for illustration purposes only. FIG. 23 does not limit the scope of the present disclosure to any particular implementation.

[0214] As shown in Figure 23, 2301, 2302, 2303 and 2304 are all examples for the relative positions of SS / PBCH blocks considered in this embodiment. In this embodiment, the total RMSI CORESET BW is defined as the sum of the BWs of two blocks (e.g., RMSI CORESET BW = RMSI CORESET BW1 + RMSI CORESET BW2) to be consistent with the previous definition.

[0215] In this embodiment, the frequency center of the RMSI CORESET BW may refer to the center of the entire frequency range including RMSI CORESET BW1, RMSI CORESET BW2, ΔGap1, ΔGap2, and the minimum channel BW. In one consideration, the RMSI CORESET BW1 and RMSI CORESET BW2 are fixed and have the same value to reduce overhead in the specification.

[0216] Among other considerations, the gaps ΔGap1 and ΔGap2 are determined to be ΔGap1+ΔGap2=12RE and are aligned with the RE level offset values ​​to allow floating synchronization (e.g., if the RE level offset is defined as -6:1:5 or -6:1:6, then ΔGap1=6RE and ΔGap2=6RE; if the RE level offset is defined as 0:1:11 or 0:1:12, then ΔGap1=0RE and ΔGap2=12RE; if the RE level offset is defined as -11:1:0, then ΔGap1=11RE and ΔGap2=1RE; if the RE level offset is defined as -12:1:0, then ΔGap1=12RE and ΔGap2=0RE).

[0217] In this embodiment, the frequency offset reference can be determined as F_ref=(ΔGap1-ΔGap2) / 2+(RMSI CORESET BW1-RMSI CORESET BW2) / 2, and the frequency offset range for ΔF' can be determined as ΔF'_Range in PRB=(minimum channel BW in PRB-SS / PBCH block BW in PRB)*R_SCS, where the minimum channel BW is defined in the SS / PBCH block neuroradio, ΔF'_Range is defined in the RMSI CORESET neuroradio, and R_SCS=SCS_SS / SCS_CORESET is the ratio between the subcarrier spacing values ​​of the SS / PBCH block and the RMSI CORESET.

[0218] In a second embodiment of FDM subcase 2 (e.g., FDM-embodiment 2.2), the frequency location of the SS / PBCH block can be within the minimum channel BW, and multiple RMSI CORESET blocks (e.g., two blocks on each side of the SS / PBCH block) can be (partially) multiplexed within the minimum channel BW with potentially predefined constant gaps ΔGap1 and ΔGap2 (both defined in the RMSI CORESET neural network) in the frequency domain.

[0219] 24 is a diagram illustrating an example configuration of frequency offset 2400 for a fifth case of FDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 2400 shown in FIG. 24 is for illustration purposes only. FIG. 24 does not limit the scope of the present disclosure to any particular implementation.

[0220] As shown in Fig. 24, 2401, 2402 and 2403 are all examples for the relative positions of SS / PBCH blocks considered in this embodiment. In this embodiment, the total RMSI CORESET BW is defined as the sum of the BWs of two blocks (e.g., RMSI CORESET BW = RMSI CORESET BW1 + RMSI CORESET BW2) to be consistent with the previous definition. In this embodiment, the frequency center of the RMSI CORESET BW may refer to the center of the entire frequency range including RMSI CORESET BW1, RMSI CORESET BW2, ΔGap1, ΔGap2 and SS / PBCH block BW.

[0221] In one consideration, RMSI CORESET BW1 and RMSI CORESET BW2 are fixed and have the same value to reduce overhead in the specification. In another consideration, the gaps ΔGap1 and ΔGap2 are determined to be ΔGap1+ΔGap2=12RE and are aligned with the RE level offset value to allow floating synchronization (for example, if the RE level offset is defined as -6:1:5 or -6:1:6, then ΔGap1=6RE and ΔGap2=6RE; if the RE level offset is defined as 0:1:11 or 0:1:12, then ΔGap1=0RE and ΔGap2=12RE; if the RE level offset is defined as -11:1:0, then ΔGap1=11RE and ΔGap2=1RE; if the RE level offset is defined as -12:1:0, then ΔGap1=12RE and ΔGap2=0RE). In this embodiment, the frequency offset reference can be determined as F_ref=(ΔGap1-ΔGap2) / 2+(RMSI CORESET BW1-RMSI CORESET BW2) / 2, and the frequency offset range for ΔF' can be determined as ΔF'_Range=0 at the PRB (which means that the relative position is fixed from the PRB level), where ΔF'_Range is defined in the RMSI CORESET neuroradio.

[0222] In a third embodiment of FDM subcase 2 (e.g., FDM-embodiment 2.3), the frequency location of the SS / PBCH block can be within the minimum channel BW, and multiple RMSI CORESET blocks (e.g., two blocks on each side of the SS / PBCH block) can be (partially) multiplexed within the minimum channel BW with potentially predefined constant gaps ΔGap1 and ΔGap2 (both defined in the RMSI CORESET neuroradio) in the frequency domain, where the SS / PBCH block has a potential additional offset represented by up to one PRB from the RMSI CORESET neuroradio perspective (this one PRB is used for the function of floating synchronization to indicate the possible offset between the SS / PBCH block PRB boundary and the RMSI CORESET PRB boundary).

[0223] 25 is a diagram illustrating an example configuration of frequency offset 2500 for a sixth case of FDM multiplexing pattern according to an embodiment of the present disclosure. The embodiment of the configuration of frequency offset 2500 shown in FIG. 25 is for illustration purposes only. FIG. 25 does not limit the scope of the present disclosure to any particular implementation.

[0224] As shown in Fig. 25, 2501, 2502 and 2503 are all examples for the relative positions of SS / PBCH blocks considered in this embodiment. In this embodiment, the total RMSI CORESET BW is defined as the sum of the BWs of two blocks (e.g., RMSI CORESET BW = RMSI CORESET BW1 + RMSI CORESET BW2) to be consistent with the previous definition. In this embodiment, the frequency center of the RMSI CORESET BW may refer to the center of the entire frequency range including RMSI CORESET BW1, RMSI CORESET BW2, ΔGap1, ΔGap2 and the SS / PBCH block BW.

[0225] In one consideration, RMSI CORESET BW1 and RMSI CORESET BW2 are fixed and have the same value to reduce overhead in the specification. In another consideration, the gaps ΔGap1 and ΔGap2 are determined to be ΔGap1+ΔGap2=12RE and are aligned with the RE level offset value to allow floating synchronization (for example, if the RE level offset is defined as -6:1:5 or -6:1:6, then ΔGap1=6RE and ΔGap2=6RE; if the RE level offset is defined as 0:1:11 or 0:1:12, then ΔGap1=0RE and ΔGap2=12RE; if the RE level offset is defined as -11:1:0, then ΔGap1=11RE and ΔGap2=1RE; if the RE level offset is defined as -12:1:0, then ΔGap1=12RE and ΔGap2=0RE). In this embodiment, the frequency offset reference can be determined as F_ref=(ΔGap1-ΔGap2) / 2+(RMSI CORESET BW1-RMSI CORESET BW2) / 2, and the frequency offset range for ΔF' can be determined as ΔF'_Range=1 in the PRB, where ΔF'_Range is defined in the RMSI CORESET neuroradio.

[0226] Construction method and principle.

[0227] The method for configuring at least one of said components may be according to the following embodiments.

[0228] In one embodiment, each of the components may be represented by a bit, for example, for component i (1≦i≦5), N_Component_i bits are used to configure that configuration, and the total number of bits in the MIB for the RMSI CORESET configuration is given by N_Component_1+N_Component_2+N_Component_3+N_Component_4+N_Component_5.

[0229] In another embodiment, the combination of components can be represented by an example table, where each RMSI CORESET configuration is represented by a row or column in the table, containing information of all components.

[0230] In other embodiments, a hybrid configuration method using both bits and tables may be used for RMSI CORESET configuration, for example some components or some parameters of the components may be represented by individual bits and the remaining components or some combinations of the components may be represented by a table or multiple tables.

[0231] In the table or partial table approach to represent the RMSI CORESET configuration, the main motivation is to conserve the total number of bits in the MIB. For example, the number of bits to represent the frequency offset can be significantly different for different TDM and FDM implementations, in which case using a uniform number of bits for the configuration may not be efficient. The following principles are considered when trying to limit the number of component combinations.

[0232] In principle, the number of bits used for individual components can be minimized unless the components can be completely separated or the individual components incur an increase in the total number of bits.

[0233] Another principle is that the supported combinations of SS / PBCH blocks and RMSI CORESETs of neural networks can be restricted so that a smaller number of configurations are required. One or more of the following example combinations are considered:

[0234] In one example, the combination of SCS_SS=240 kHz and SCS_CORESET=60 kHz may not be supported for all scenarios.

[0235] In another example, the combination of SCS_SS=240 kHz and SCS_CORESET=60 kHz cannot be supported, at least for the TDM case.

[0236] In another example, the combination of SCS_SS=240 kHz and SCS_CORESET=60 kHz cannot be supported, at least for the FDM case.

[0237] In yet another example, for the FDM case, only the combination SCS_SS=SCS_CORESET may be supported.

[0238] In yet another principle, the RMSI CORESET BW may have certain limitations related to the RMSI CORESET neuroradiology if possible. One or more combinations of the following examples are considered:

[0239] In one example, the RMSI CORESET BW can be at least 24 PRBs in terms of the SS / PBCH block neural network, and can be up to 48 PRBs in terms of the SS / PBCH block neural network.

[0240] In another example, the RMSI CORESET BW can be at least 24 PRBs in terms of the SS / PBCH block neural network, at least for the TDM case, and can be up to 48 PRBs in terms of the SS / PBCH block neural network.

[0241] In yet another example, the RMSI CORESET BW can be at least 12 PRBs from an SS / PBCH block neural network perspective, at least for the FDM case, and can be up to 24 PRBs from an SS / PBCH block neural network perspective.

[0242] In yet another example, the RMSI CORESET BW may be only 24 PRBs from an SS / PBCH block neural network perspective, at least for the FDM case.

[0243] In yet another principle, the number of symbols for the RMSI CORESET may have specific limitations associated with the RMSI CORESET neuroradio and / or SS / PBCH neuroradio and / or RMSI CORESET BW, if possible. Combinations of one or more of the following examples are contemplated:

[0244] In one example, if the RMSI CORESET BW is 24 PRBs from the RMSI CORESET neuroradiographic point of view, the number of symbols for the RMSI CORESET can be 1 or 2.

[0245] In another example, if the RMSI CORESET BW is 48 PRBs from the RMSI CORESET neuroradiographic point of view, the number of symbols for the RMSI CORESET can be 1 or 2.

[0246] In yet another example, if the RMSI CORESET BW is 96 PRBs from the RMSI CORESET neuroradiographic point of view, the number of symbols for the RMSI CORESET may be 1.

[0247] In yet another example, the number of symbols for the RMSI CORESET can be the same as the R_SCS, where R_SCS is the ratio between the SS / PBCH SCS and the RMSI CORESET SCS (which occupies some blank symbols before the SS block in the slot to which the SS / PBCH block is mapped).

[0248] In yet another example, the number of symbols for the RMSI CORESET can be equal to 2*R_SCS, where R_SCS is the ratio between the SS / PBCH SCS and the RMSI CORESET SCS (which occupies some blank symbols before the SS block in the slot to which the SS / PBCH block is mapped).

[0249] In yet another principle, when determining the frequency offset, the relative positions of the SS / PBCH blocks, the RMSI CORESET and the minimum channel BW can be constrained to minimize the number of configurations required. One or more combinations of the following examples are considered:

[0250] In one example, for TDM subcase 1, TDM embodiment 1.2 or TDM embodiment 1.3 can be considered to reduce the number of configurations compared to TDM embodiment 1.1.

[0251] In another example, for TDM subcase 2, TDM embodiment 2.2 or TDM embodiment 2.3 can be considered to reduce the number of configurations compared to TDM embodiment 2.1.

[0252] In yet another example, for the FDM case, FDM embodiment 1.2 or FDM embodiment 1.3 may be considered to reduce the number of configurations compared to FDM embodiment 1.1.

[0253] In yet another example, for the FDM case, FDM embodiment 2.2 or FDM embodiment 2.3 may be considered to reduce the number of configurations compared to FDM embodiment 2.1.

[0254] Other principles for using tables or partially using tables to represent the RMSI CORESET configuration are contemplated in this disclosure.

[0255] In another principle, a configuration table for RMSI CORESET may be defined per band, or per band group using the same SS / PBCH neuroradio, or per SS / PBCH neuroradio. Note that the maximum number of configurations for different SS / PBCH neuroradioradio (if the maximum number of configurations is different) determines the number of bits required to represent the table. In another embodiment, a common table of RMSI CORESET configurations may be defined for all bands and all SS / PBCH neuroradioradio, but there may be some configuration waste due to the different number of configurations for different bands or different SS / PBCH neuroradioradio (e.g., the number of common configurations may be larger than any individual table for each SS / PBCH neuroradio).

[0256] In yet another principle, the configuration table for the RMSI CORESET can include one or more entries from the FDM case (e.g., can be from one or more subcases) as well as one or more entries from the TDM case (e.g., can be from one or more subcases). For each case, configurations can be correspondingly determined (e.g., configuration groups for each multiplexing case), and the number of total configurations in the table is the sum of all configurations from all groups, depending on which specific multiplexing cases are supported.

[0257] In yet another principle, some or all of the components considered in this disclosure may be jointly coded using a table or multiple tables, and each of the remaining components (if there are any) may have at least one separate field (which may be multiple fields to consider additional sub-components within the component) coded independently. The components jointly coded in the table may include at least one of the following: multiplexing pattern (which may not be explicitly indicated if it may be clearly indicated in combination with other components), RMSI CORESET neuroradio, RMSI CORESET BW, RMSI CORESET symbol number, PRB level frequency offset (only in dual field configuration scheme), RE level frequency offset, frequency offset, and timing offset.

[0258] The dependency (which remains even if the components are not jointly coded in the table) is that after knowing the multiplexing pattern (or timing offset) and the RMSI CORESET neural network, the configuration for the RMSI CORESET BW and the number of RMSI CORESET symbols can be determined, and all of this except for the timing offset and the number of RMSI CORESET symbols determines the configuration of the frequency offset (PRB level frequency offset and RE level frequency offset).

[0259] In yet another principle, when using a table approach or a partial table approach where the configuration does not fully use all the codewords of some tables, one of the redundant / reserved codewords can be used to not indicate the RMSI and CORESET of one of the redundant / reserved codewords associated with the SS / PBCH block, and no separate bits in the MIB are required to indicate this information.

[0260] For example, when using dual field frequency offset indication and the number of configurations for RE level offset ΔF1 is 12, one of four reserved codewords (e.g., 1111) may be used to not indicate the RMSI and CORESET of one of four reserved codewords associated with an SS / PBCH block. In another example, when using dual field frequency offset indication and the number of configurations for RE level offset ΔF1 is 24, one of eight reserved codewords (e.g., 11111) may be used to not indicate the RMSI and CORESET of one of eight codewords associated with an SS / PBCH block.

[0261] In another example, when using a dual field frequency offset representation and the configuration number for the PRB level offset ΔF2 is less than 2^x2 (where x2 is the number of bits to represent ΔF2), an unused / reserved codeword (e.g., every one of the codewords of length x2) may be used to indicate the RMSI and CORESET of one of the unused / reserved codewords associated with the SS / PBCH block.

[0262] In yet another example, when using a single-field frequency offset representation and the number of configurations for the RE level offset ΔF is less than 2^x (where x is the number of bits to represent ΔF), one of the unused / reserved codewords (e.g., every one of the codewords of length x) may be used to not indicate the RMSI and CORESET of one of the unused / reserved codewords associated with the SS / PBCH block.

[0263] In yet another example, when using joint coding of CORESET BW and number of symbols, and the number of configurations is less than 2^y, where y is the total number of bits for this representation (e.g., y=1 or 2), one of the unused / reserved codewords (e.g., every one of the codewords of length y) may be used to not indicate the RMSI and CORESET of one of the unused / reserved codewords associated with the SS / PBCH block.

[0264] Configuration approaches and examples.

[0265] The following configuration scheme examples according to the above method principles can be considered to represent frequency offsets, which can be used in any of the above TDM / FDM embodiments. In one embodiment, all bands (e.g., for both <6 and >6 GHz) use the same configuration scheme. In other embodiments, a configuration scheme can be selected per band.

[0266] In a first scheme (e.g., scheme 1), the frequency offset can be configured by two parts / fields (dual-field configuration scheme): the first configuration is the RE level offset between the SS / PBCH block and the RMSI CORESET PRB grid (e.g., the RE offset defined in floating synchronization), and the second configuration is the PRB level offset between the SS / PBCH block and the RMSI resource.

[0267] In a first approach of the first scheme (e.g., scheme 1a), the RE offset ΔF1 and the PRB offset ΔF2 are thereby measured and expressed in SS / PBCH RE and PRB granularity (i.e., whereby the possible values ​​of ΔF1 and ΔF2 are in units of SS / PBCH RE and PRB).

[0268] Then, the total number of possible values ​​for ΔF1 at RE and ΔF2 at PRB, i.e., N_ΔF1 and N_ΔF2, can be determined as N_ΔF1=N_RE_PRB / R_SCS (asymmetric RE position), N_ΔF2=ΔF′_Range at PRB / R_SCS+1 for TDM case and N_ΔF2=ΔF′_Range at PRB / R_SCS (where R_SCS=SCS_SS / SCS_CORESET) for FDM case, and the possible values ​​of ΔF1 and ΔF2 are (1) ΔF1 with asymmetric RE position: -(N_ΔF1-2) / 2, -(N_ΔF1-4) / 2, …, (N_ΔF1-2) / 2, N_ΔF1 / 2 or -N_ΔF1 / 2, -(N_ΔF1-2) / 2, ..., (N_ΔF1-2) / 2 or 0,1, ..., N_ΔF1-1 or -(N_ΔF1-1), ..., -1, 0 (or also denoted as -(N_ΔF1-2) / 2:1:N_ΔF1 / 2 or -N_ΔF1 / 2:1:(N_ΔF1-2) / 2 or 0:1:N_ΔF1-1 or -(N_ΔF1-1):1:0); (2) ΔF1 with symmetric RE position: -(N_ΔF1-1) / 2, -(N_ΔF1-3) / 2, ..., (N_ΔF1-3) / 2, (N_ΔF1-1) / 2 (or also denoted as -(N_ΔF1-1) / 2:1:(N_ΔF1-1) / 2). Note that in such symmetric RE position configurations, one of the RE position configurations is not required; or (3) ΔF2:-(N_ΔF2-1) / 2, -(N_ΔF2-3) / 2, ..., (N_ΔF2-3) / 2, (N_ΔF2-1) / 2 (also denoted as -(N_ΔF2-1) / 2:1:(N_ΔF2-1) / 2). If N_ΔF2=0 or 1, then the possible values ​​of ΔF2 are 0 (indicating that it is a fixed value and does not need to be configured).

[0269] The final frequency offset ΔF can be determined by the TDM / FDM embodiment taking into account the frequency offset reference in the offset as in Table 1, where ΔF=ΔF′+F_ref and ΔF′=ΔF1+ΔF2*N_RE_PRB (N_RE_PRB=12 regardless of the neuroradiography). Table 1 illustrates ΔF determination for different multiplexing cases using scheme 1a.

[0270] [Table 1-1] [Table 1-2]

[0271] In a second approach of the first scheme (e.g., scheme 1b), the RE offset ΔF1 and the PRB offset ΔF2 are thereby measured and expressed in RMSI CORESET RE and PRB granularity (i.e., the possible values ​​of ΔF1 and ΔF2 are thereby in units of RMSI CORESET RE and PRB). Then, the total number of possible values ​​of ΔF1 at RE and ΔF2 at PRB, i.e., N_ΔF1 and N_ΔF2, can be correspondingly determined as follows: for TDM case, N_ΔF1=N_RE_PRB (asymmetric RE position); or N_ΔF1=N_RE_PRB+1 (symmetric RE position); and N_ΔF2=ΔF′_Range at PRB+1; for FDM case, N_ΔF2=ΔF′_Range at PRB.

[0272] Possible values ​​of ΔF1 and ΔF2 are: (1) ΔF1 with asymmetric RE position: -(N_ΔF1-2) / 2, -(N_ΔF1-4) / 2, …,(N_ΔF1-2) / 2,N_ΔF1 / 2 or -N_ΔF1 / 2, -(N_ΔF1-2) / 2, …,(N_ΔF1-2) / 2 or 0,1, …,N_ΔF1-1 or -(N_ΔF1-1), …,-1,0 (or -(N_ΔF1-2) / 2:1:N_ΔF1 / 2 or -N_ΔF1 / 2:1:(N_ΔF1-2) / 2 or 0:1:N_ΔF1-1 or -(N_ΔF1-1):1:0); (2) ΔF1 with symmetric RE position: -(N_ΔF1-1) / 2, -(N_ΔF1-3) / 2, ..., (N_ΔF1-3) / 2, (N_ΔF1-1) / 2 (or also denoted as -(N_ΔF1-1) / 2:1:(N_ΔF1-1) / 2). Note that in such symmetric RE location configurations, one of the RE location configurations is not mandatory; or (3) ΔF2:-(N_ΔF2-1) / 2, -(N_ΔF2-3) / 2, ..., (N_ΔF2-3) / 2, (N_ΔF2-1) / 2 (or also denoted as -(N_ΔF2-1) / 2:1:(N_ΔF2-1) / 2). If N_ΔF2=0 or 1, the possible values ​​of ΔF2 are 0 (indicating a fixed value and no need to configure).

[0273] The final frequency offset ΔF can be determined by the TDM / FDM embodiment taking into account the frequency offset reference in the offset as in Table 2, where ΔF=ΔF′+F_ref and ΔF′=ΔF1+ΔF2*N_RE_PRB (N_RE_PRB=12 regardless of the neuroradiography). Table 2 illustrates ΔF determination for different multiplexing cases using Scheme 1b.

[0274] [Table 2-1] [Table 2-2]

[0275] In a third approach (e.g., scheme 1c) of the first scheme, the RE offset ΔF1 / PRB offset ΔF2 is measured and expressed at a smaller granularity between the SS / PBCH block RE / PRB and the RMSI CORESET RE / PRB. Then, the total number of possible values ​​for ΔF1 at RE and ΔF2 at PRB, i.e., N_ΔF1 and N_ΔF2, can be determined as N_ΔF1=N_RE_PRB / min(R_SCS,1) (asymmetric RE position); or N_ΔF1=N_RE_PRB / min(R_SCS,1)+1 (symmetric RE position); N_ΔF2=ΔF′_Range / min(R_SCS,1)+1 at PRB for the TDM case; and N_ΔF2=ΔF′_Range / min(R_SCS,1) at PRB for the FDM case (R_SCS=SCS_SS / SCS_CORESET).

[0276] Possible values ​​of ΔF1 and ΔF2 are: (1) ΔF1 with asymmetric RE position: -(N_ΔF1-2) / 2, -(N_ΔF1-4) / 2, …,(N_ΔF1-2) / 2,N_ΔF1 / 2 or -N_ΔF1 / 2, -(N_ΔF1-2) / 2, …,(N_ΔF1-2) / 2 or 0,1, …,N_ΔF1-1 or -(N_ΔF1-1), …,-1,0 (or -(N_ΔF1-2) / 2:1:N_ΔF1 / 2 or -N_ΔF1 / 2:1:(N_ΔF1-2) / 2 or 0:1:N_ΔF1-1 or -(N_ΔF1-1):1:0); (2) ΔF1 with symmetric RE position: -(N_ΔF1-1) / 2, -(N_ΔF1-3) / 2, ..., (N_ΔF1-3) / 2, (N_ΔF1-1) / 2 (or also denoted as -(N_ΔF1-1) / 2:1:(N_ΔF1-1) / 2). Note that in such symmetric RE location configurations, one of the RE location configurations is not mandatory; or (3) ΔF2:-(N_ΔF2-1) / 2, -(N_ΔF2-3) / 2, ..., (N_ΔF2-3) / 2, (N_ΔF2-1) / 2 (or also denoted as -(N_ΔF2-1) / 2:1:(N_ΔF2-1) / 2). If N_ΔF2=0 or 1, the possible values ​​of ΔF2 are 0 (indicating a fixed value and no need to configure).

[0277] The final frequency offset ΔF can be determined by the TDM / FDM embodiment taking into account the frequency offset reference in the offset, where ΔF=ΔF′+F_ref and ΔF′=ΔF1+ΔF2*N_RE_PRB (N_RE_PRB=12 regardless of the neuroradiography).

[0278] In a fourth approach of the first scheme (eg, scheme 1d), the RE offset ΔF1 and the PRB offset ΔF2 are correspondingly expressed in RMSI CORESET RE and PRB (ie, the units of ΔF1 and ΔF2 are RMSI CORESET RE and PRB).

[0279] In a first example of granularity of ΔF2, the granularity of ΔF2 is the same as the SS / PBCH PRB (eg, if the RMSI CORESET SCS is smaller than the SS / PBCH SCS, there is no need to indicate a granularity smaller than the SS / PBCH PRB). Then, the total number of possible values ​​for ΔF2 at the PRB, i.e., N_ΔF2, can be determined as N_ΔF2=ΔF'_Range at PRB / R_SCS+1 for the TDM case, and N_ΔF2=ΔF'_Range at PRB / R_SCS for the FDM case, where R_SCS=SCS_SS / SCS_CORESET (the ratio between SS / PBCH SCS and CORESET SCS), and the possible values ​​of ΔF2 can be determined as -(N_ΔF2-1)*R_SCS / 2, -(N_ΔF2-3)*R_SCS / 2, ..., (N_ΔF2-3)*R_SCS / 2, (N_ΔF2-1)*R_SCS / 2 (or also denoted as -(N_ΔF2-1)*R_SCS / 2:R_SCS:(N_ΔF2-1)*R_SCS / 2). If N_ΔF2=0 or ≦1, then the possible value of ΔF2 is 0 (indicating that it is a fixed value and does not need to be configured).

[0280] In a second example of the granularity of ΔF2, the granularity of ΔF2 is equal to the maximum value of SS / PBCH PRB and RMSI CORESET PRB. Then, the total number of possible values ​​for ΔF2 in PRB, i.e., N_ΔF2, can be determined as N_ΔF2=ΔF′_Range / max(1,R_SCS)+1 in PRB for the TDM case, and N_ΔF2=ΔF′_Range / max(1,R_SCS) in PRB for the FDM case, where R_SCS=SCS_SS / SCS_CORESET (the ratio between SS / PBCH SCS and CORESET SCS), and the possible values ​​of ΔF2 are -(N_ΔF2-1)*max(1,R_SCS) / 2, -(N_ΔF2-3)*max(1,R_SCS) / 2, ...,(N_ΔF2-3)*max(1,R_SCS) / 2,(N_ΔF2-1)*max(1,R_SCS) / 2 (also denoted as -(N_ΔF2-1)*max(1,R_SCS) / 2:max(1,R_SCS):(N_ΔF2-1)*max(1,R_SCS) / 2). If N_ΔF2=0 or ≦1, the possible values ​​of ΔF2 are 0 (indicating a fixed value and no need to configure).

[0281] In a third example of the granularity of ΔF2, the granularity of ΔF2 is the same as the RMSI CORESET PRB (eg, if the RMSI CORESET SCS is greater than the SS / PBCH SCS, there is no need to indicate a granularity smaller than the RMSI CORESET PRB). Then, the total number of possible values ​​for ΔF2 at the PRB, i.e., N_ΔF2, can be determined as N_ΔF2=ΔF′_Range at the PRB+1 for the TDM case, and N_ΔF2=ΔF′_Range at the PRB for the FDM case, where R_SCS=SCS_SS / SCS_CORESET (the ratio between SS / PBCH SCS and CORESET SCS), and the possible values ​​of ΔF2 can be determined as −(N_ΔF2-1) / 2, −(N_ΔF2-3) / 2, …, (N_ΔF2-3) / 2, (N_ΔF2-1) / 2 (or also denoted as −(N_ΔF2-1) / 2:1:(N_ΔF2-1) / 2). If N_ΔF2=0 or 1, the possible values ​​of ΔF2 are 0 (indicating a fixed value and no need to configure).

[0282] In a fourth example of the granularity of ΔF2, the granularity of ΔF2 is the same as the minimum value of SS / PBCH PRB and RMSI CORESET PRB. Then, the total number of possible values ​​for ΔF2 in PRB, i.e., N_ΔF2, can be determined as N_ΔF2=ΔF′_Range / min(1,R_SCS)+1 in PRB for the TDM case, and N_ΔF2=ΔF′_Range / min(1,R_SCS) in PRB for the FDM case, where R_SCS=SCS_SS / SCS_CORESET (the ratio between SS / PBCH SCS and CORESET SCS), and the possible values ​​of ΔF2 are -(N_ΔF2-1)*min(1,R_SCS) / 2, -(N_ΔF2-3)*min(1,R_SCS) / 2,...,(N_ΔF2-3)*min(1,R_SCS) / 2,(N_ΔF2-1)*min(1,R_SCS) / 2 (also denoted as -(N_ΔF2-1)*min(1,R_SCS) / 2:min(1,R_SCS):(N_ΔF2-1)*min(1,R_SCS) / 2). If N_ΔF2=0 or ≦1, the possible values ​​of ΔF2 are 0 (indicating a fixed value and no need to configure).

[0283] In a fifth example of granularity of ΔF2, the granularity of ΔF2 is the same as one or more RMSI CORESET PRBs (e.g., if CORESET SCS is larger than SS / PBCH, there is no need to indicate a smaller granularity than RMSI CORESET PRB since it is already indicated by ΔF1 for the RE offset), where the granularity Δf2 (which can be considered as the “RMSI raster”) is determined by the relationship between the minimum CH BW and the RMSI CORESET BW for TDM subcase 1 (e.g., if the RMSI CORESET BW is within the minimum channel BW, then Δf2=RMSI CORESET BW+PRB_CH_Raster of PRBs at RMSI neuroradio) and by the relationship between the carrier BW and the RMSI CORESET BW for TDM subcase 2 (e.g., if the RMSI CORESET BW is larger than the minimum channel BW, then Δf2=Carrier BW at RMSI neuroradioradio-RMSI CORESET BW+PRB_CH_Raster). BW+PRB_CH_Raster), with Δf2=1 for the FDM case (the ΔF2 value is not important since no PRB level display is required), where PRB_CH_Raster is determined by the relationship between the CORESET SCS, SS SCS and channel raster, and can be determined as PRB_CH_Raster=min(CH Raster / SCS_CORESET,1), which means that if SCS_CORESET>CH raster, no display below half PRB is required. A summary of examples for determining PRB_CH_Raster is shown in Table 3. Table 3 shows an example of determining PRB_CH_Raster.

[0284] [Table 3]

[0285] In this example, Δf2 represents the maximum frequency offset that allows the same SS / PBCH block and RMSI CORESET multiplexing pattern to be used. The total number of possible values ​​of ΔF2 in the PRB, i.e., N_ΔF2, can be determined as N_ΔF2=[display range / ΔF2] for the TDM case and as N_ΔF2=1 for the FDM case, where R_SCS=SCS_SS / SCS_CORESET (the ratio between SS / PBCH SCS and CORESET SCS), and the display range corresponds to the SS raster (e.g., =minimum CH BW-SS / PBCH block BW (for some bands)) in terms of the RMSI CORESET neural radius (the number of relative SS / PBCH block positions within the minimum CH BW) for the TDM case. The possible values ​​of ΔF2 can be determined as -(ΔF'_Range at PRB) / 2:Δf2:(ΔF'_Range at PRB) / 2 if N_ΔF2>3, the possible values ​​of ΔF2 (when expressed as a central offset) can be determined as -(ΔF'_Range at PRB) / 2 and +(ΔF'_Range at PRB) / 2 if N_ΔF2=2, or -(ΔF'_Range at PRB) / 2+1 and +(ΔF'_Range at PRB) / 2-1 if N_ΔF2=2, and the possible values ​​of ΔF2 (when expressed as a central offset) can be determined as 0 if N_ΔF2=1 (indicating a fixed value and no need to configure). ΔF'_Range is determined in the previous TDM and FDM embodiments.

[0286] The selection of possible values ​​for ΔF2 assumes that the frequency range for the SS / PBCH block is a subset of the frequency range for the RMSI CORESET, such that only the difference in their BWs needs to be indicated.

[0287] In one possible variation to this example, if there is no configuration for ΔF2=0 (when expressed as a central offset), other configurations for ΔF2=0 can be introduced. The purpose of introducing the possible value 0 is for better measurement.

[0288] In another possible variation on this example, in the FDM case, even if N_ΔF2=1, there may still be two possible values ​​for that criterion, such as multiplexing the lower edge of the SS block with a potential gap to the upper edge.

[0289] FIG 26A is a diagram illustrating an example configuration of ΔF2 (2610) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 15 kHz, 5 MHz, 24 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2610) shown in FIG 26A is for illustration purposes only. FIG 26A does not limit the scope of the present disclosure to any particular implementation.

[0290] An example of such an approach (Scheme 1d) with a fifth example of ΔF2 granularity for TDM subcase-1 is illustrated in Figure 26A and a summary of this example is shown in Table 4. Table 4 shows an example of ΔF2 configuration for TDM subcase-1.

[0291] [Table 4]

[0292] In the first example as in Fig. 26A, a TDM scenario with SCS_SS = 15kHz and SCS_CORESET = 15kHz and channel raster = 15kHz or 100kHz is considered (assuming that the minimum CH BW is 5MHz (25PRB in SS and RMSI neuroradio). In this case, if the RMSI CORESET BW is 24PRB, then the display range = 5PRB and Δf2 = 2PRB, so that N_ΔF2 = 3, i.e. three configurations are sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, the possible values ​​can be -2, 0, 2PRB (center offset) or 4, 2, 0PRB (edge ​​offset) from the RMSI CORESET neuroradio perspective.

[0293] As shown in FIG. 26A, 26a01 and 26a02 use the same configuration #0 (ΔF2=-2PRB for center offset or ΔF2=4PRB for edge offset), 26a03 and 26a04 use the same configuration #1 (ΔF2=0PRB for center offset or ΔF2=2PRB for edge offset), and 26a05 and 26a06 use the same configuration #2 (ΔF2=2PRB for center offset or ΔF2=0PRB for edge offset).

[0294] FIG. 26B is a diagram illustrating an example configuration of ΔF2 (2620) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 30 kHz, 5 MHz, 12 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2620) shown in FIG. 26B is for illustration only. FIG. 26B does not limit the scope of the present disclosure to any particular implementation.

[0295] In a second example as in FIG. 26B, a scenario with SCS_SS=15kHz and SCS_CORESET=30kHz and channel raster=15kHz or 100kHz is considered (assuming that the minimum CH BW is 5MHz (25PRB in SS neuroradio and 11PRB in RMSI neuroradio). In this case, the RMSI CORESET BW as 12PRB cannot be supported unless the channel utilization of 5MHz BW with 30kHz SCS is more than 12PRB. For example, in FIG. 26B, there is no configuration available to fit CORESET within the minimum CH BW.

[0296] FIG. 26C is a diagram illustrating an example configuration of ΔF2 (2630) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={30 kHz, 15 kHz, 10 MHz, 48 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2630) shown in FIG. 26C is for illustration only. FIG. 26C does not limit the scope of the present disclosure to any particular implementation.

[0297] In a third example as in FIG. 26C, a scenario with SCS_SS=30kHz and SCS_CORESET=15kHz and channel raster=15kHz or 100kHz is considered (assuming that the minimum CH BW is 10MHz (24PRB for SS neuroradio and 52PRB for RMSI neuroradio)). In this case, if the RMSI CORESET BW is 48PRB, then the display range=8PRB and Δf2=5PRB, so N_ΔF2=2, i.e. two configurations are sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, possible values ​​could be -2, 2PRB (center offset) or 6, 2PRB (edge ​​offset) from the RMSI CORESET neuroradio perspective.

[0298] As shown in Figure 26C, 26c01 to 26c05 use the same configuration #0 (ΔF2 = -2PRB for center offset or ΔF2 = 6PRB for edge offset), and 26c06 to 26c09 use the same configuration #1 (ΔF2 = 2PRB for center offset or ΔF2 = 2PRB for edge offset). In this case, if the channel utilization alignment is not shown in Figure 26C (e.g., not center aligned), the two configurations can still be used and the value of each configuration can be changed accordingly, where the difference in value is the same as the offset between the PRBs of the channel utilization in the mixed neuroradio.

[0299] FIG. 26D illustrates an example configuration of ΔF2 (2640) for the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={30 kHz, 30 kHz, 10 MHz, 24 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2640) shown in FIG. 26D is for illustration only. FIG. 26D does not limit the scope of the present disclosure to any particular implementation.

[0300] In a fourth example as in Figure 26D, a scenario with SCS_SS = 30kHz and SCS_CORESET = 30kHz and channel raster = 15kHz or 100kHz is considered (assuming that the minimum CH BW is 10MHz (24PRB in SS and RMSI neuroradio). In this case, if the RMSI CORESET BW is 24PRB, the display range = 4PRB and Δf2 = 1PRB, so N_ΔF2 = 5, i.e. 5 configurations are sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, and the possible values ​​can be -2, -1, 0, 1, 2PRB (center offset) or 4, 3, 2, 1, 0PRB (edge ​​offset) from the RMSI CORESET neuroradio perspective.

[0301] As shown in FIG. 26D, each of 26d01, 26d03, 26d05, 26d07 and 26d09 uses individual configurations #0 to #4 accordingly, where each configuration corresponds to ΔF2 as -2, -1, 0, 1, 2 PRB in the case of center offset, or ΔF2 as 4, 3, 2, 1, 0 PRB in the case of edge offset, and other cases (e.g., 26d02, 26d04, 26d06 and 26d08) do not require a separate configuration because the RE level offset representation ΔF1, whose offset is not an integer multiple of the RMSI PRB but is combined with the existing configuration of ΔF2, can cover this case.

[0302] FIG. 26E is a diagram illustrating an example configuration of ΔF2 (2650) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={120 kHz, 60 kHz, 50 MHz, 48 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2650) shown in FIG. 26E is for illustration only. FIG. 26E does not limit the scope of the present disclosure to any particular implementation.

[0303] In the fifth example as in FIG. 26E, a scenario of SCS_SS=120kHz and SCS_CORESET=60kHz and channel raster=60kHz is considered (assuming that the minimum CH BW is 50MHz (32PRB for SS neuroradio and 66PRB for RMSI neuroradio)). In this case, if the RMSI CORESET BW is 48PRB, then the display range=24PRB and Δf2=19PRB, so that N_ΔF2=2, i.e. two configurations are sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, possible values ​​could be -4, 4PRB (center offset) or 8, 0PRB (edge ​​offset) from the RMSI CORESET neuroradio perspective.

[0304] As shown in FIG. 26E, 26e01 to 26e03 use the same configuration #0 (ΔF2=-4PRB for center offset or ΔF2=8PRB for edge offset), and 26e04 to 26e06 use the same configuration #1 (ΔF2=4PRB for center offset or ΔF2=8PRB for edge offset). Note that in some cases (e.g., 26e03 and 26e04), one of the two configurations can be used. Also, if we add a third configuration, ΔF2=0 for center offset or ΔF2=4 for edge offset, 26e03 and 26e04 can use this configuration.

[0305] FIG. 26F is a diagram illustrating an example configuration of ΔF2 (2660) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={120 kHz, 120 kHz, 50 MHz, 24 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2660) shown in FIG. 26F is for illustration only. FIG. 26F does not limit the scope of the present disclosure to any particular implementation.

[0306] In the sixth example as in Figure 26F, a scenario of SCS_SS = 120kHz and SCS_CORESET = 120kHz and channel raster = 60kHz is considered (assuming that the minimum CH BW is 50MHz (32PRB in SS and RMSI neuroradio). In this case, if the RMSI CORESET BW is 24PRB, then the display range = 12PRB and Δf2 = 9PRB, so that N_ΔF2 = 2, i.e. two configurations are sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, possible values ​​could be -2, 2PRB (center offset) or 4, 0PRB (edge ​​offset) from the RMSI CORESET neuroradio perspective.

[0307] As shown in FIG. 26F, 26f01 to 26f03 use the same configuration #0 (ΔF2=-2PRB for center offset or ΔF2=4PRB for edge offset), and 26f04 to 26f06 use the same configuration #1 (ΔF2=2PRB for center offset or ΔF2=0PRB for edge offset). In some cases (e.g., 26f03 and 26f04), one of the configurations can be used. Also, adding a third configuration, ΔF2=0 for center offset or ΔF2=2 for edge offset, allows 26f03 to 26f04 to use this configuration.

[0308] FIG. 26G illustrates an example configuration of ΔF2 (2670) for the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={240 kHz, 120 kHz, 100 MHz, 48 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2670) shown in FIG. 26G is for illustration only. FIG. 26G does not limit the scope of the present disclosure to any particular implementation.

[0309] In the seventh example as in FIG. 26G, a scenario of SCS_SS=240kHz and SCS_CORESET=120kHz and channel raster=60kHz is considered (assuming that the minimum CH BW is 100MHz (32PRB for SS neuroradio and 66PRB for RMSI neuroradio)). In this case, if the RMSI CORESET BW is 48PRB, then the display range=24PRB and Δf2=19PRB, which is sufficient to configure N_ΔF2=2, i.e., two configurations of PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, and possible values ​​can be -4, 4PRB (center offset) or 8, 0PRB (edge ​​offset) from the RMSI CORESET neuroradio perspective.

[0310] As shown in FIG. 26G, 26g01-26g03 use the same configuration #0 (ΔF2=-4PRB for center offset or ΔF2=8PRB for edge offset), and 26g04-26g06 use the same configuration #1 (ΔF2=4PRB for center offset or ΔF2=0PRB for edge offset). In some cases (e.g., 26g03 and 26g04), one of the configurations can be used. Also note that adding a third configuration, ΔF2=0 for center offset or ΔF2=4 for edge offset, allows 26g03-26g04 to use this configuration.

[0311] FIG. 26H illustrates an example configuration of ΔF2 (2680) for the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={240 kHz, 60 kHz, 100 MHz, 96 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2680) shown in FIG. 26H is for illustration purposes only. FIG. 26H does not limit the scope of the present disclosure to any particular implementation.

[0312] In the eighth example as in FIG. 26H, a scenario of SCS_SS=240kHz and SCS_CORESET=60kHz and channel raster=60kHz is considered (assuming that the minimum CH BW is 100MHz (32PRB for SS neuroradio and 132PRB for RMSI neuroradio). In this case, if the RMSI CORESET BW is 96PRB, then the display range=48PRB and Δf2=37PRB, which is sufficient to configure N_ΔF2=2, i.e., two configurations of PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, and possible values ​​can be -8,8PRB (center offset) or 16,0PRB (edge ​​offset) from the RMSI CORESET neuroradio perspective.

[0313] As shown in Figure 26H, 26h01 to 26h03 use the same configuration #0 (ΔF2=-4PRB for center offset or ΔF2=8PRB for edge offset), and 26h04 to 26h06 use the same configuration #1 (ΔF2=4PRB for center offset or ΔF2=0PRB for edge offset). In some cases (e.g., 26h03 and 26h04), one of the configurations can be used. Also, adding a third configuration, ΔF2=0 for center offset or ΔF2=8 for edge offset, allows 26h03 to 26h04 to use this configuration.

[0314] FIG. 27A is a diagram illustrating an example configuration of ΔF2 (2700) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 15 kHz, 10 MHz, 48 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2700) shown in FIG. 27A is for illustration purposes only. FIG. 27A does not limit the scope of the present disclosure to any particular implementation.

[0315] An example of such an approach (Scheme 1d) with a fifth example of ΔF2 granularity for TDM subcase-2 is illustrated in Figure 27A and a summary of this example is shown in Table 5. Table 5 shows an example of ΔF2 configuration for TDM subcase-2.

[0316] [Table 5]

[0317] In the first example as in Fig. 27A, a TDM scenario with SCS_SS=15kHz and SCS_CORESET=15kHz and channel raster=15kHz or 100kHz is considered. The carrier BW is 10MHz and 52PRB in SS and RMSI neuroradio. In this case, if the RMSI CORESET BW is 48PRB and the limited BW can be selected as the central 24PRB of the RMSI CORESET BW, then the display range=5PRB and Δf2=5PRB, so that N_ΔF2=2, i.e. two configurations are sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, the possible values ​​can be -2, 2PRB (center offset) or 12, 16PRB (edge ​​offset) from the RMSI CORESET neuroradio point of view.

[0318] As shown in FIG. 27A, 27a01, 27a02 and 275a03 use the same configuration #0 (ΔF2=-2PRB for center offset or ΔF2=16PRB for edge offset), and 27a04, 27a05 and 27a06 use the same configuration #1 (ΔF2=2PRB for center offset or ΔF2=12PRB for edge offset).

[0319] FIG. 27B is a diagram illustrating an example configuration of ΔF2 (2710) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 15 kHz, 20 MHz, 96 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2710) shown in FIG. 27B is for illustration purposes only. FIG. 27B does not limit the scope of the present disclosure to any particular implementation.

[0320] In the second example as in Fig. 27B, a TDM scenario with SCS_SS=15kHz and SCS_CORESET=15kHz and channel raster=15kHz or 100kHz is considered. The carrier BW is 20MHz and 106PRB in SS and RMSI neuroradio. In this case, if the RMSI CORESET BW is 96PRB and the limited BW can be selected as the central 24PRB of the RMSI CORESET BW, then with the display range=5PRB, Δf2=11PRB, so that N_ΔF2=1, i.e. one configuration is enough to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, and the possible values ​​can be 0PRB (center offset) or 38PRB (edge ​​offset) from the RMSI CORESET neuroradio viewpoint.

[0321] As shown in FIG. 27B, 27b01 to 27b06 all use the same configuration #0 (ΔF2=0 PRB for center offset or ΔF2=38 PRB for edge offset).

[0322] FIG. 27C is a diagram illustrating an example configuration of ΔF2 (2720) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 30 kHz, 10 MHz, 24 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2720) shown in FIG. 27C is for illustration purposes only. FIG. 27C does not limit the scope of the present disclosure to any particular implementation.

[0323] In a third example as in Fig. 27C, a TDM scenario with SCS_SS=15kHz and SCS_CORESET=30kHz and channel raster=15kHz or 100kHz is considered. The carrier BW is 10MHz, 52PRB for SS neuroradio and 24PRB for RMSI neuroradio. In this case, if the RMSI CORESET BW is 24PRB and the limited BW can be selected as the central 12PRB of the RMSI CORESET BW, then the display range=2.5PRB and Δf2=1PRB, so that N_ΔF2=3, i.e. three configurations are sufficient to configure the PRB level frequency offset between the SS block and the center / edge of the RMSI CORESET, and the possible values ​​can be -1, 0, 1PRB (center offset) or 6, 7, 8PRB (edge ​​offset) from the RMSI CORESET neuroradio viewpoint.

[0324] As shown in FIG. 27C, 27c01 uses configuration #0 (ΔF2=-1PRB for center offset or ΔF2=8PRB for edge offset), 27c03 uses configuration #1 (ΔF2=0PRB for center offset or ΔF2=7PRB for edge offset), 27c05 uses configuration #2 (ΔF2=1PRB for center offset or ΔF2=6PRB for edge offset), and the rest do not require configurations since the PRBs are not aligned (RE level display combination with other existing configurations can cover such cases).

[0325] FIG. 27D is a diagram illustrating an example configuration of ΔF2 (2730) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={15 kHz, 30 kHz, 20 MHz, 48 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2730) shown in FIG. 27D is for illustration only. FIG. 27D does not limit the scope of the present disclosure to any particular implementation.

[0326] In the fourth example as in Fig. 27D, a TDM scenario with SCS_SS=15kHz and SCS_CORESET=30kHz and channel raster=15kHz or 100kHz is considered. The carrier BW is 20MHz, 106PRB for SS neuroradio and 50PRB for RMSI neuroradio (rounding down one PRB with even PRB for mixed neuroradio). In this case, if the RMSI CORESET BW is 48PRB and the limited BW can be selected as the center 12PRB of the RMSI CORESET BW, then the display range = 2.5PRB and Δf2 = 3PRB, so that N_ΔF2 = 2, i.e. two configurations are sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, the possible values ​​can be -1, 1PRB (center offset) or 18, 20PRB (edge ​​offset) from the RMSI CORESET neuroradio point of view.

[0327] As shown in FIG. 27D, 27d01, 27d02 and 27d03 use the same configuration #0 (ΔF2=-1PRB for center offset or ΔF2=20PRB for edge offset), while 27d04, 27d05 and 27d06 use the same configuration #1 (ΔF2=1PRB for center offset or ΔF2=18PRB for edge offset).

[0328] FIG. 27E illustrates an example configuration of ΔF2 (2740) for the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={30 kHz, 15 kHz, 20 MHz, 96 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2740) shown in FIG. 27E is for illustration only. FIG. 27E does not limit the scope of the present disclosure to any particular implementation.

[0329] In the fifth example as in Fig. 27E, a TDM scenario with SCS_SS = 30kHz and SCS_CORESET = 15kHz and channel raster = 15kHz or 100kHz is considered. The carrier BW is 20MHz, with 50PRBs in the SS neuroradio (one PRB is truncated by an even number of PRBs in the mixed neuroradio) and 106PRBs in the RMSI neuroradio. In this case, if the RMSI CORESET BW is 96PRBs and the limited BW can be selected as the central 48PRBs of the RMSI CORESET BW, then the display range = 9PRBs, and Δf2 = 11PRBs, so that N_ΔF2 = 1, i.e. one configuration is sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, and the possible values ​​can be 0PRBs (center offset) or 28PRBs (edge ​​offset) from the RMSI CORESET neuroradio perspective.

[0330] As shown in FIG. 27E, all use the same configuration #0 (ΔF2=0 PRB for center offset or ΔF2=28 PRB for edge offset).

[0331] FIG. 27F is a diagram illustrating an example configuration of ΔF2 (2750) in the case of {SS SCS, RMSI SCS, CH BW, CORESET BW}={30 kHz, 30 kHz, 20 MHz, 48 PRB} according to an embodiment of the present disclosure. The embodiment of the configuration of ΔF2 (2750) shown in FIG. 27F is for illustration only. FIG. 27F does not limit the scope of the present disclosure to any particular implementation.

[0332] In the sixth example as in Fig. 27F, a TDM scenario with SCS_SS=30kHz and SCS_CORESET=30kHz and channel raster=15kHz or 100kHz is considered. The carrier BW is 20MHz and 50PRB in SS and RMSI neuroradio. In this case, if the RMSI CORESET BW is 48PRB and the limited BW can be selected as the central 24PRB of the RMSI CORESET BW, then the display range=9PRB and Δf2=3PRB, so that N_ΔF2=3, i.e. three configurations are sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, and the possible values ​​can be -2, 0, 2PRB (center offset) or 12, 14, 16PRB (edge ​​offset) from the RMSI CORESET neuroradio viewpoint.

[0333] As shown in FIG. 27F, 27f01 to 27f03 use the same configuration #0 (ΔF2=-2PRB for center offset or ΔF2=16PRB for edge offset), 27f04 to 27f06 use the same configuration #1 (ΔF2=0PRB for center offset or ΔF2=14PRB for edge offset), and 27f07 to 27f09 use the same configuration #1 (ΔF2=2PRB for center offset or ΔF2=12PRB for edge offset).

[0334] For the >6GHz case (e.g., SS SCS is 240kHz or 120kHz), since the channel utilization is quite high, the display range is much smaller than Δf2, so a single configuration is sufficient to configure the PRB level frequency offset between the center / edge of the SS block and the RMSI CORESET, and possible values ​​can be 0PRB (center offset) from the RMSI CORESET neural radio perspective, or CORESET_BW / 2-SS_BW / 2*R_SCS PRB (edge ​​offset).

[0335] When TDM subcases 1 and 2 are merged together, one joint table can be given similar to Table 6, where a=R_SCS=SCS_SS / SCS_CORESET. Note that the relationship between edge offset and center offset is given by edge offset=center offset+CORESET_BW / 2-SS block BW / 2*R_SCS. Table 6 shows an example of ΔF2 configuration for the TDM case.

[0336] [Table 6]

[0337] For such an approach (e.g., scheme 1d) with a fifth example of granularity of ΔF2 for the FDM case, two configurations are sufficient to indicate the PRB level frequency offset ΔF2, i.e., CORESET is multiplexed at the top of the SS block or multiplexed at the bottom of the SS block, all of which have potentially smaller gaps to allow for floating synchronization and / or mixed neural radio of SS and RMSI. For example, the edge offset can be SS block BW*R_SCS-1 or CORESET BW when ΔF1 is not 0 (i.e., the PRB grid is not aligned) and the SS and RMSI neuroradiographies are the same; or SS block BW*R_SCS or CORESET BW when ΔF1 is 0 (i.e., the PRB grid is aligned) and the SS and RMSI neuroradiographies are the same; or SS block BW*R_SCS-2 or CORESET BW+1 when ΔF1 is not 0 (i.e., the PRB grid is not aligned) and the SS and RMSI neuroradiographies are different from each other; or SS block BW*R_SCS-1 or CORESET BW+1 when ΔF1 is 0 (i.e., the PRB grid is aligned) and the SS and RMSI neuroradiographies are different from each other.

[0338] In one embodiment for this approach (Scheme 1d), for each combination of SS SCS and RMSI CORESET SCS, the multiplexing pattern of the SS / PBCH block and RMSI CORESET, the RMSI CORESET BW, the number of symbols for CORESET, and the PRB level offset are jointly coded in a table using X bits in the DL NR-PBCH, where X may be, for example, 4.

[0339] An example of this embodiment is shown in Tables 7A to 7H, in which "Pattern 1" refers to a multiplexing pattern in which the SS / PBCH block and the RMSI CORESET occur at different time instances and the SS / PBCH block TX BW and the initial active DL BWP including the RMSI CORESET overlap (TDM case (including subcases 1 and 2) in the above embodiment); "Pattern 2" refers to a multiplexing pattern in which the SS / PBCH block and the RMSI CORESET occur at different time instances and the SS / PBCH block TX BW and the initial active DL BWP including the RMSI CORESET do not overlap (FDM subcase 1 with SS block and RMSI CORESET starting from different symbols (timing offset is greater than 0)); "Pattern 3" refers to a multiplexing pattern in which the SS / PBCH block and the RMSI CORESET occur at the same time instance and the SS / PBCH block TX BW and the initial active DL BWP including the RMSI CORESET do not overlap (SS block and RMSI CORESET starting from the same symbol (timing offset is 0) FDM subcase 1) with CORESET refers to the multiplexing pattern.

[0340] Table 7A provides a joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of symbols in CORESET, and PRB level offset using 4 bits in MIB when SCS of SS is 15 kHz and SCS of CORESET is 15 kHz. This configuration table can be used at least for carriers with 15 kHz SS SCS and minimum channel BW of 5 MHz. For carriers with minimum channel BW larger than 5 MHz, Table 7A can be reused for these carriers as well, if the synchronization raster can be kept the same or smaller than the carrier with minimum channel BW of 5 MHz.

[0341] For example, for bands where the minimum CH BW is 10 MHz but the SS raster step size is still within the 900 kHz+ channel raster, Table 7A can be applied to these bands as well; for bands where the minimum CH BW is 20 MHz but the SS raster step size is still within the 900 kHz+ channel raster, Table 7A can be applied to these bands as well. Table 7A illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 15 kHz}.

[0342] [Table 7A]

[0343] Table 7B provides a joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of symbols of CORESET, and PRB level offset using 4 bits in MIB when SCS of SS is 15 kHz and SCS of CORESET is 30 kHz. This configuration table can be used at least for carriers with 15 kHz SS SCS and minimum channel BW of 5 MHz. For carriers with minimum channel BW larger than 5 MHz, Table 7B can be reused for these carriers as well if the synchronization raster can be kept the same or smaller than the carrier with minimum channel BW of 5 MHz. For example, for bands with minimum CH BW of 10 MHz but SS raster step size still within 900 kHz+ channel raster, Table 7B can be applied to these bands as well; for bands with minimum CH BW of 20 MHz but SS raster step size still within 900 kHz+ channel raster, Table 7B can be applied to these bands as well. Table 7B illustrates an example of an RMSI CORESET configuration for bands with at least a minimum CH BW of 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 30 kHz}.

[0344] [Table 7B]

[0345] Table 7C provides a joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of symbols in CORESET, and PRB level offset using 4 bits in MIB when SCS of SS is 30 kHz and SCS of CORESET is 15 kHz. This configuration table can be used at least for carriers with 30 kHz SS SCS and 10 MHz minimum channel BW. For carriers with 5 MHz minimum channel BW, Table 7C can be reused for these carriers if one network can operate at 10 MHz. For carriers with minimum channel BW larger than 10 MHz, Table 7C can be reused for these carriers if the synchronization raster can be kept the same or smaller than the carrier with minimum channel BW of 10 MHz. Table 7C illustrates the RMSI CORESET configuration at least for bands with minimum CH BW of 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={30 kHz, 15 kHz}.

[0346] [Table 7C]

[0347] Table 7D provides a joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of symbols in CORESET, and PRB level offset using 4 bits in MIB when SCS of SS is 30 kHz and SCS of CORESET is 30 kHz. This configuration table can be used at least for carriers with 30 kHz SS SCS and 10 MHz minimum channel BW. For carriers with 5 MHz minimum channel BW, Table 7D can be reused for these carriers if one network can operate at 10 MHz. For carriers with minimum channel BW larger than 10 MHz, Table 7D can be reused for these carriers if the synchronization raster can be kept the same or smaller than the carrier with minimum channel BW of 10 MHz. Table 7D illustrates the RMSI CORESET configuration at least for bands with minimum CH BW of 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={30 kHz, 30 kHz}.

[0348] [Table 7D]

[0349] Table 7E provides a joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of symbols in CORESET, and PRB level offset using 4 bits in MIB when SCS of SS is 120kHz and SCS of CORESET is 60kHz. This configuration table can be used at least for carriers with 120kHz SS SCS and minimum channel BW of 50MHz. For carriers with minimum channel BW larger than 50MHz, Table 7E can be reused for these carriers as well if the synchronization raster can be kept the same or smaller than the carrier with minimum channel BW of 50MHz. Table 7E illustrates the RMSI CORESET configuration at least for bands with minimum CH BW of 50MHz when {SS SCS, RMSI SCS}={120kHz,60kHz}.

[0350] [Table 7E]

[0351] Table 7F provides a joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of symbols in CORESET, and PRB level offset using 4 bits in MIB when SCS of SS is 120kHz and SCS of CORESET is 120kHz. This configuration table can be used at least for carriers with 120kHz SS SCS and minimum channel BW of 50MHz. For carriers with minimum channel BW larger than 50MHz, Table 7F can be reused for these carriers as well if the synchronization raster can be kept the same or smaller than the carrier with minimum channel BW of 50MHz. Table 7F illustrates the RMSI CORESET configuration at least for bands with minimum CH BW of 50MHz when {SS SCS, RMSI SCS}={120kHz, 120kHz}.

[0352] [Table 7F]

[0353] Table 7G provides a joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of symbols in CORESET, and PRB level offset using 4 bits in MIB when SCS of SS is 240 kHz and SCS of CORESET is 60 kHz. This configuration table can be used at least for carriers with 240 kHz SS SCS and 100 MHz minimum channel BW. For carriers with 50 MHz minimum channel BW, Table 7G can be reused for these carriers if one network can operate at 100 MHz. For carriers with minimum channel BW larger than 100 MHz, Table 7G can be reused for these carriers if the synchronization raster can be kept the same or smaller than the carrier with minimum channel BW of 100 MHz. Table 7G illustrates the RMSI CORESET configuration at least for bands with minimum CH BW of 50 MHz when {SS SCS, RMSI SCS}={240 kHz, 60 kHz}.

[0354] [Table 7G]

[0355] Table 7H provides a joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of symbols in CORESET, and PRB level offset using 4 bits in MIB when SCS of SS is 240kHz and SCS of CORESET is 120kHz. This configuration table can be used at least for carriers with 240kHz SS SCS and 100MHz minimum channel BW. For carriers with 50MHz minimum channel BW, Table 7H can be reused for these carriers if one network can operate at 100MHz. For carriers with minimum channel BW larger than 100MHz, Table 7H can be reused for these carriers if the synchronization raster can be kept the same or smaller than the carrier with minimum channel BW of 100MHz. Table 7H illustrates the RMSI CORESET configuration at least for bands with minimum CH BW of 50MHz when {SS SCS, RMSI SCS}={240kHz, 120kHz}.

[0356] [Table 7H]

[0357] In a first example of ΔF1 granularity, the granularity of ΔF1 is the same as the RMSI CORESET SCS (e.g., there is no indication of finer granularity if the channel raster is smaller than the RMSI CORESET SCS). In this case, the network selects a subset from the channel raster such that no indication of finer granularity is necessary, and the UE assumes that the SS / PBCH block PRB grid is aligned with the RMSI RE grid such that the PRB grid offset between the SS / PBCH block and the RMSI is an integer multiple of the RMSI subcarrier spacing.

[0358] Then, the total number of possible values ​​for ΔF1 at RE, i.e., N_ΔF1, can be determined as N_ΔF1=N_ΔF1=N_RE_PRB (asymmetric RE position); or N_ΔF1=N_RE_PRB+1 (symmetric RE position), where N_RE_PRB=12, and R_SCS=SCS_SS / SCS_CORESET (ratio between SS / PBCH SCS and CORESET SCS), and the possible values ​​of ΔF1 are: (1) ΔF1 with asymmetric RE position: -(N_ΔF1-2) / 2, -(N_ΔF1-4) / 2, ..., (N_ΔF1-2) / 2, N_ΔF1 / 2 or -N_ΔF1 / 2, (2) ΔF1 with symmetric RE position: -(N_ΔF1-1) / 2, -(N_ΔF1-3) / 2, ..., (N_ΔF1-3) / 2, (N_ΔF1-1) / 2 (or -(N_ΔF1-1) / 2:1:(N_ΔF1-1) / 2). Note that in such symmetric RE location configurations, one of the RE location configurations is not mandatory.

[0359] In a second example of the granularity of ΔF1, if the granularity of ΔF1 is defined as SCS-based (e.g., 15 kHz for <6 GHz and 60 kHz for >6 GHz), it is the same as the channel raster. Then, the total number of possible values ​​for ΔF1 at the RE, i.e., N_ΔF1, can be determined as N_ΔF1=N_RE_PRB*R_SCS′ (asymmetric RE position); or N_ΔF1=N_RE_PRB*R_SCS′+1 (symmetric RE position); where N_RE_PRB=12, and R_SCS′=SCS_CORESET / 15 kHz for <6 GHz and R_SCS′=SCS_CORESET / 60 kHz for >6 GHz (e.g., CORESET if the channel raster is SCS-based). Ratio between SCS and channel raster), or possible values ​​of ΔF1 are (1) ΔF1 with asymmetric RE position: -(N_ΔF1-2) / 2 / R_SCS′, -(N_ΔF1-4) / 2 / R_SCS′, …, (N_ΔF1-2) / 2 / R_SCS′, N_ΔF1 / 2 / R_SCS′ or -N_ΔF1 / 2 / R_SCS′, -( N_ΔF1-2) / 2 / R_SCS′,…,(N_ΔF1-2) / 2 / R_SCS′ or 0,1 / R_SCS′,…,(N_ΔF1-1) / R_SCS′ or -(N_ΔF1-1) / R_SCS′,…,-1 / R_SCS′,0(or -(N_ΔF1-2) / 2 / R_SCS′:1 / R_SCS′:N_ΔF1 / 2 / (N_ΔF1-1) / R_SCS′ or -N_ΔF1 / 2 / R_SCS′:1 / R_SCS′:(N_ΔF1-2) / 2 / R_SCS′ or 0:1 / R_SCS′:(N_ΔF1-1) / R_SCS′ or -(N_ΔF1-1) / R_SCS′:1 / R_SCS′:0); (2) ΔF1 with symmetric RE position: -(N_ΔF1-1) / 2 / R_SCS′, -(N_ΔF1-3) / 2 / R_SCS′, ..., (N_ΔF1-3) / 2 / R_SCS′, (N_ΔF1-1) / 2 / R_SCS′ (or -(N_ΔF1-1) / 2 / R_SCS′:1 / R_SCS′:(N_ΔF1-1) / 2 / R_SCS′). Note that in such symmetric RE location configurations, one of the RE location configurations is not mandatory.

[0360] For a given frequency range, one consideration for the two examples of granularity of ΔF1 is to select between these two examples, e.g., if >6GHz, the first example is used, if <6GHz, the second example is used.

[0361] In the fourth approach of the first scheme (e.g. scheme 1d), the final frequency offset ΔF can be determined by ΔF=ΔF1+ΔF2*N_RE_PRB (N_RE_PRB=12 regardless of the neuroradio) considering the frequency offset criteria within the same offset as in Table 8. Table 8 illustrates ΔF determination for different multiplexing cases using scheme 1d.

[0362] [Table 8-1] [Table 8-2]

[0363] In a second scheme (e.g., scheme 2), the frequency offset can be configured by a single configuration that captures the RE offset between the SS / PBCH block and the RMSI resource PRB grid (e.g., single field configuration scheme, where there is no need to separately indicate the RE offset in the PRB due to floating synchronization). Note that an advantage from this embodiment (e.g., single field configuration compared to dual field configuration) is the reduction in the number of potential configurations (or bits).

[0364] In a first approach of the second scheme (eg, scheme 2a), the RE offset ΔF′ is measured and expressed in terms of the granularity of the SS / PBCH SCS (ie, the units and intervals of possible values ​​of ΔF′ are the SS / PBCH SCS). Then, the total number of possible values ​​of ΔF′, i.e., N_ΔF′, can be determined as N_ΔF′=ΔF′_Range at PRB*N_RE_PRB / R_SCS (asymmetric RE position) for TDM and FDM cases; or N_ΔF′=ΔF′_Range at PRB*N_RE_PRB / R_SCS+1 (symmetric RE position) for TDM and FDM cases, where N_RE_PRB=12 is the number of REs in PRB in frequency domain independent of neuroradiology, R_SCS=SCS_SS / SCS_CORESET, and the possible values ​​of ΔF′ are (1) ΔF′ with asymmetric RE position: -(N_ΔF′-2) / 2, -(N_ΔF′-4) / 2, …, (N_ΔF′-2) / 2, N_ΔF′ / 2 or -N_ΔF′ / 2, (2) ΔF′ with symmetric RE position: -(N_ΔF′-1) / 2, -(N_ΔF′-3) / 2, ..., (N_ΔF′-3) / 2, (N_ΔF′-1) / 2 (or -(N_ΔF′-1) / 2:1:(N_ΔF′-1) / 2). Note that in such symmetric RE location configurations, one of the RE location configurations is not mandatory.

[0365] In a second approach of the second scheme (eg, scheme 2b), the RE offset ΔF′ is measured and expressed in terms of the granularity of the RMSI CORESET SCS (ie, the possible values ​​of ΔF′ are in units of the RMSI CORESET SCS). Then, the total number of possible values ​​of ΔF′, i.e., N_ΔF′, can be determined as N_ΔF′=ΔF′_Range at PRB*N_RE_PRB (asymmetric RE position) for TDM and FDM cases; or N_ΔF′=ΔF′_Range at PRB*N_RE_PRB+1 (symmetric RE position) for TDM and FDM cases, where N_RE_PRB=12 is the number of REs in the PRB in the frequency domain independent of neuroradiology, and the possible values ​​of ΔF′ are: (1) ΔF′ with asymmetric RE position: -(N_ΔF′-2) / 2, -(N_ΔF′-4) / 2, ..., (N_ΔF′-2) / 2, N_ΔF′ / 2 or -N_ΔF′ / 2, (2) ΔF′ with symmetric RE position: -(N_ΔF′-1) / 2, -(N_ΔF′-3) / 2, ..., (N_ΔF′-3) / 2, (N_ΔF′-1) / 2 (or -(N_ΔF′-1) / 2:1:(N_ΔF′-1) / 2). Note that in such symmetric RE location configurations, one of the RE location configurations is not required.

[0366] In a third approach to the second scheme (e.g., scheme 2c), the RE offset ΔF′ is measured and expressed in terms of the smaller granularity between the SS / PBCH SCS and the RMSI CORESET SCS (i.e., the units and intervals of possible values ​​of ΔF′ are the smaller between the SS / PBCH SCS and the RMSI CORESET SCS). Then, the total number of possible values ​​of ΔF′, i.e., N_ΔF′, can be determined as N_ΔF′=ΔF′_Range at PRB*N_RE_PRB / min(R_SCS,1) (asymmetric RE position) for TDM and FDM cases; or N_ΔF′=ΔF′_Range at PRB*N_RE_PRB / min(R_SCS,1)+1 (symmetric RE position) for TDM and FDM cases, where N_RE_PRB=12 is the number of REs in the PRB in the frequency domain independent of neuroradiology, and the possible values ​​of ΔF′ are (1) ΔF′ with asymmetric RE position: -(N_ΔF′-2) / 2, -(N_ΔF′-4) / 2, ..., (N_ΔF′-2) / 2, N_ΔF′ / 2 or -N_ΔF′ / 2, (2) ΔF′ with symmetric RE position: -(N_ΔF′-1) / 2, -(N_ΔF′-3) / 2, ..., (N_ΔF′-3) / 2, (N_ΔF′-1) / 2 (or -(N_ΔF′-1) / 2:1:(N_ΔF′-1) / 2). Note that in such symmetric RE location configurations, one of the RE location configurations is not mandatory.

[0367] In a fourth approach of the second scheme (e.g., scheme 2d), the RE offset ΔF′ is configured by ΔF′=N_RE_PRB*ΔF2+ΔF1, where the RE offset ΔF1 and the PRB offset ΔF2 are defined in the same manner as in scheme 1d. The final frequency offset ΔF can be determined by the TDM / FDM embodiment taking into account the frequency offset reference in the offset, i.e., ΔF=ΔF′+F_ref.

[0368] In a third scheme (e.g., scheme 3), the frequency offset can be configured by a single configuration that captures the frequency offset between the SS / PBCH block and the RMSI resource, where the offset is measured in terms of the magnitude of the channel raster, regardless of whether floating synchronization is supported or not. For example, the N_ΔF′ possible configurations in the MIB are used to indicate a frequency offset and the value of N_ΔF′ can be determined as N_ΔF′=ΔF′_Range in PRB*N_RE_PRB*SCS_CORESET / CH_Raster, where N_RE_PRB=12 is the number of REs in the PRB in the frequency domain regardless of neuroradiation, SCS_CORESET is the subcarrier spacing of the RMSI CORESET, CH_Raster is the channel raster size in Hz, and the possible values ​​of ΔF′ can be determined as -(N_ΔF′-1) / 2, -(N_ΔF′-3) / 2, ..., (N_ΔF′-3) / 2, (N_ΔF′-1) / 2 (or also denoted as -(N_ΔF′-1) / 2:1:(N_ΔF′-1) / 2).

[0369] In a fourth scheme (e.g., scheme 4), the frequency offset can be configured by a single configuration that captures the frequency offset between the SS / PBCH block and the RMSI resource, where the offset is measured in terms of the synchronization raster size, regardless of whether floating synchronization is supported. For example, the N_ΔF′ possible configurations in the MIB are used to indicate the frequency offset, and the value of N_ΔF′ can be determined as N_ΔF′=ΔF′_Range in PRB*N_RE_PRB*SCS_CORESET / SS_Raster, where N_RE_PRB=12 is the number of REs in the PRB in the frequency domain regardless of the neuroradiography, SCS_CORESET is the subcarrier spacing of the RMSI CORESET, SS_Raster is the synchronization raster size in Hz, and the possible values ​​of ΔF′ are -(N_ΔF′-1) / 2, -(N_ΔF′-3) / 2, ..., (N_ΔF′-3) / 2, (N_ΔF′-1) / 2 (or can be expressed as -(N_ΔF′-1) / 2:1:(N_ΔF′-1) / 2).

[0370] In a fifth scheme (e.g. scheme 5), the frequency offset can be configured in two parts (dual field configuration): the first configuration is the RE offset between the SS / PBCH block and the RMSI CORESET PRB grid (e.g. RE offset defined for floating synchronization), and the second configuration is the PRB offset between the SS / PBCH block and the RMSI resource. For example, a possible configuration of the MIB with the whole N_ΔF1·N_ΔF2 is used to indicate the frequency offset, where the N_ΔF1 configuration is used to indicate the RE offset compared to the PRB grid (e.g. floating synchronization), and the N_ΔF2 configuration is used to indicate the PRB offset between the SS / PBCH block and the RMSI resource (e.g. this offset is denoted as ΔF2 from the PRB point of view). If the N_ΔF1 configuration is expressed in x bits, then x1=[log2(N_ΔF1)], and if the N_ΔF2 configuration is expressed in x2 bits, then x2=[log2(N_ΔF2)]. Overall, the number of bits required, when expressed in bits, is given by x = x1 + x2. The difference between Scheme 5 and Scheme 1 is that the representation granularity with floating synchronization can be sparser, which corresponds to potential changes in the channel raster values.

[0371] In one example of this approach, the PRB offset ΔF2 is measured and expressed in RMSI CORESET PRB granularity, the RE offset ΔF1 is measured and expressed in RMSI CORESET RE granularity of N_RE_ΔF1 (N_RE_ΔF1 can be 1 or 2 or 3 or 4 or 6 or 12), and N_RE_ΔF1 The total number of possible values ​​of ΔF1 at RE and ΔF2 at PRB, i.e., N_ΔF1 and N_ΔF2, can be determined as N_ΔF1=N_RE_PRB / N_RE_ΔF1 (asymmetric RE position) for TDM case; or N_ΔF1=N_RE_PRB / N_RE_ΔF1+1 (symmetric RE position); and N_ΔF2=ΔF_Range+1 at PRB; and N_ΔF2=ΔF_Range at PRB for TDM case; and the possible values ​​of ΔF1 and ΔF2 are (1) ΔF1 with asymmetric RE position: -(N_ΔF1-2) / 2, -(N_ΔF1-4) / 2, ..., (N_ΔF1-2) / 2, N_ΔF1 / 2 or -N_ΔF1 / 2, -(N_ΔF1-2) / 2, ..., (N_ΔF1-2) / 2 or 0,1, ..., N_ΔF1-1 or -(N_ΔF1-1), ..., -1, 0 (or also denoted as -(N_ΔF1-2) / 2:1:N_ΔF1 / 2 or -N_ΔF1 / 2:1:(N_ΔF1-2) / 2 or 0:1:N_ΔF1-1 or -(N_ΔF1-1):1:0); ΔF1 with symmetric RE position: -(N_ΔF1-1) / 2, -(N_ΔF1-3) / 2, ..., (N_ΔF1-3) / 2, (N_ΔF1-1) / 2 (or also denoted as -(N_ΔF1-1) / 2:1:(N_ΔF1-1) / 2); or ΔF2: -(N_ΔF2-1) / 2, -(N_ΔF2-3) / 2,...,(N_ΔF2-3) / 2,(N_ΔF2-1) / 2 (or denoted as -(N_ΔF2-1) / 2:1:(N_ΔF2-1) / 2). If N_ΔF2=0 or 1, then the possible values ​​of ΔF2 are 0 (indicating a fixed value and no need to configure).

[0372] Scheme 5 is the same as Scheme 1 when N_RE_ΔF1 = 1. Also, a special case of this scheme is when N_RE_ΔF1 = 12 (which can refer to a scenario where the channel raster is defined at the PRB level), where N_ΔF1 = 1, which means that there is no need to indicate floating synchronization (SS / PBCH block PRB and RMSI CORESET PRB are automatically aligned) and only the PRB offset needs to be indicated.

[0373] In a sixth scheme (e.g. scheme 6), the frequency offset can be configured by a single configuration that captures the frequency offset between the SS / PBCH block and the RMSI resource at the PRB level, where the offset is measured in terms of the RMSI CORESET neuroradiography or the SS / PBCH block neuroradiography. The RMSI resource and the SS / PBCH block PRB grids are assumed to be aligned or have a subset relationship (if these neuroradiography are not the same, the PRB grid with the larger subcarrier spacing is a subset of the PRB grid with the smaller subcarrier spacing), which eliminates the need for floating synchronization in the MIB. The PRB grid offset between the RMSI and other data outside the initial active BW measured at the RE level can be displayed in the RMSI / OSI. The determination of the PRB level offset can refer to ΔF2 in scheme 1.

[0374] An example of an additional configuration using method 1d.

[0375] More examples for Scheme 1d using joint configuration of SS / PBCH block and RMSI CORESET multiplexing pattern, RMSI CORESET BW, number of CORESET symbols and PRB level offset are provided below, where different combinations of SS SCS and CORESET SCS are considered. In such examples, the display range may be smaller than the theoretical upper limit, such as minimum CH BW-SS / PBCH block BW+CH raster, which is the same as the SS raster of the corresponding carrier.

[0376] In the first example, in the NR band, when the minimum CH BW=10 MHz, the SS SCS is determined to be 15 kHz. For this band, if the SS raster is defined at 4320 kHz (24 PRBs with SS SCS), the CORESET configuration may differ from the table above since the frequency offset indication may be different when using a different SS raster. A summary of the frequency offset (PRB level) configuration for this example is shown in Table 9. Table 9 shows an example of ΔF2 configuration for the TDM case.

[0377] [Table 9]

[0378] In such an example for SCS_CORESET=15kHz, if the carrier BW is 10MHz (52PRB in SS and RMSI neuroradio) and the RMSI CORESET BW is 24PRB, then the display range can be the same as the SS raster (e.g., 24PRB in SS SCS) and Δf2=29PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 2PRB from the RMSI CORESET neuroradio perspective.

[0379] In such an example for SCS_CORESET=15kHz, if the carrier BW is 10MHz (52PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 48PRB, the display range can be the same as the SS raster (e.g., 24PRB for SS SCS), and Δf2=5PRB, so N_ΔF2=5, i.e., 5 configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 4, 9, 14, 19, 24PRB from the RMSI CORESET neuroradio perspective (other sets of offset value choices are possible, but in this case the interval should be 5PRB. For example, possible values ​​for this offset can be X, X+5, X+10, X+15, X+20, where X can be 0 or 1 or 2 or 3 or 4 or 5 or 6 or 7).

[0380] In such an example for SCS_CORESET=15kHz, if the carrier BW is 20MHz (106 PRB for SS and RMSI neuroradio) (exceeding the minimum CH BW in this case) and the RMSI CORESET BW is 96 PRB, then the display range can be the same as the SS raster (e.g., 24 PRB for SS SCS) and Δf2=11 PRB, thereby providing N_ΔF2=3, i.e., three configurations sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 27, 38, and 49 PRB from the RMSI CORESET neuroradio perspective.

[0381] In such an example for SCS_CORESET=30kHz, if the carrier BW is 10MHz (52PRBs for SS neuroradio and 24PRBs for RMSI neuroradio) and the RMSI CORESET BW is 24PRBs, then the display range can be the same as the SS raster (e.g., 24PRBs for SS SCS and 12PRBs for RMSI neuroradio), and Δf2=1PRB, thereby giving N_ΔF2=12, i.e., 12 configurations sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 1,...,12PRBs from the RMSI CORESET neuroradio perspective.

[0382] In such an example for SCS_CORESET=30kHz, if the carrier BW is 20MHz (exceeding the minimum CH BW in this case) (106PRB for SS neuroradio and 51PRB for RMSI neuroradio) and the RMSI CORESET BW is 24PRB, the display range can be the same as the SS raster (e.g., 24PRB for SS SCS and 12PRB for RMSI neuroradio), Δf2=28PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value can be 7PRB from the RMSI CORESET neuroradio perspective. The channel utilization in this case for the RMSI can be only 50PRB due to the filter design, Δf2=27PRB, so that one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value can be 7PRB from the RMSI CORESET neuroradio perspective.

[0383] In such an example for SCS_CORESET=30kHz, if the carrier BW is 20MHz (exceeding the minimum CH BW) (106PRB for SS neuroradio and 51PRB for RMSI neuroradio) and the RMSI CORESET BW is 48PRB, then the display range can be the same as the SS raster (e.g., 24PRB for SS SCS and 12PRB for RMSI neuroradio), and Δf2=4PRB, thereby providing N_ΔF2=3, i.e., three configurations sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 15, 19, and 23PRB from the RMSI CORESET neuroradio perspective. The channel utilization in this case for RMSI is only 50 PRB due to the filter design, and Δf2=3 PRB, so N_ΔF2=4, i.e., four configurations are sufficient, and the possible values ​​can be X, X+3, X+6, X+9 PRB from the RMSI CORESET neuroradiologic point of view, where X can be 14 or 15.

[0384] An example of a CORESET configuration (frequency PRB offset combined with different symbol number selections for CORESET) for a band with 10 MHz minimum CH BW and 15 kHz SS SCS can be summarized as in Table 10, where Table 10A is for {SS SCS, RMSI SCS}={15 kHz, 15 kHz}, Table 10B is for {SS SCS, RMSI SCS}={15 kHz, 30 kHz} when the 30 kHz channel utilization is 51 PRB, and Table 10C is for {SS SCS, RMSI SCS}={15 kHz, 30 kHz} when the 30 kHz channel utilization is 50 PRB.

[0385] If all CORESET configuration tables for min CH BW=5 MHz and min CH BW=10 MHz are supported, in one approach there is no indication of the configuration table and the UE must blindly detect whether the SS rasters are aligned or too close for the UE to distinguish in the initial cell search. If all CORESET configuration tables for min CH BW=5 MHz and min CH BW=10 MHz are supported, in another approach one bit is used in the PBCH to indicate the number of bands / configuration table / carrier frequency range. In one example, the bit used for the indication can be a reserved bit in the PBCH and only applicable to <3 GHz. In another example, the bit used for the indication can be a field in the PBCH used in the original half frame indication, where the half frame indication in the PBCH is only for >3 GHz and the same field is used to indicate the number of bands / configuration table / carrier frequency range. Table 10A illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 15 kHz}.

[0386] [Table 10A]

[0387] Table 10B illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 30 kHz}.

[0388] [Table 10B]

[0389] Table 10C illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 30 kHz}.

[0390] [Table 10C]

[0391] In a second example, in the NR band, when the minimum CH BW=10 MHz, the SS SCS is determined to be 15 kHz. For this band, the SS raster can be defined at 3600 kHz (20 PRBs for the SS SCS), and the CORESET configuration may differ from the table above because the frequency offset indication may be different when using a different SS raster. A summary of the frequency offset (PRB level) configuration for this example is shown in Table 11. Table 11 shows an example of ΔF2 configuration for the TDM case.

[0392] [Table 11]

[0393] In such an example for SCS_CORESET=15kHz, if the carrier BW is 10MHz (52PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 24PRB, then the display range can be the same as the SS raster (e.g., 20PRB for SS SCS) and Δf2=29PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 2PRB from the RMSI CORESET neuroradio perspective.

[0394] In such an example for SCS_CORESET=15kHz, if the carrier BW is 10MHz (52PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 48PRB, the display range can be the same as the SS raster (e.g., 20PRB for SS SCS), and Δf2=5PRB, so N_ΔF2=4, i.e., four configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 7, 12, 17, 22PRB from the RMSI CORESET neuroradio perspective (other sets of offset value choices are possible, but in this case the interval should be 5PRB. For example, possible values ​​for this offset can be X, X+5, X+10, X+15, where X can be 0 or 1 or 2 or 3 or 4 or 5 or 6 or 7).

[0395] In such an example for SCS_CORESET=15kHz, if the carrier BW is 20MHz (106 PRB in SS and RMSI neuroradio) (exceeding the minimum CH BW in this case) and the RMSI CORESET BW is 96 PRB, then the display range can be the same as the SS raster (e.g., 20 PRB in SS SCS) and Δf2=11 PRB, thereby resulting in N_ΔF2=2, i.e., sufficient to configure a PRB level frequency offset between the edges of the SS block and RMSI CORESET in two configurations, with possible values ​​being 0, 76 PRB from the RMSI CORESET neuroradio perspective.

[0396] In such an example for SCS_CORESET=30kHz, if the carrier BW is 10MHz (52PRBs for SS neuroradio and 24PRBs for RMSI neuroradio) and the RMSI CORESET BW is 24PRBs, then the display range can be the same as the SS raster (e.g., 20PRBs for SS SCS and 10PRBs for RMSI neuroradio), and Δf2=1PRB, so that N_ΔF2=10, i.e., 10 configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and possible values ​​can be 2,...,11PRBs from the RMSI CORESET neuroradio perspective.

[0397] In such an example for SCS_CORESET=30kHz, if the carrier BW is 20MHz (exceeding the minimum CH BW) (106PRB for SS neuroradio and 51PRB for RMSI neuroradio) and the RMSI CORESET BW is 48PRB, then the display range can be the same as the SS raster (e.g., 20PRB for SS SCS and 10PRB for RMSI neuroradio), and Δf2=4PRB, thereby providing N_ΔF2=3, i.e., three configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 15, 19, and 23PRB from the RMSI CORESET neuroradio perspective. If the channel utilization in this case for RMSI is only 50 PRB due to the filter design, then Δf2=3 PRB, so N_ΔF2=4, i.e., four configurations are sufficient, and the possible values ​​can be X, X+3, X+6, X+9 PRB from the RMSI CORESET neuroradiologic point of view, where X can be 14 or 15.

[0398] An example of a CORESET configuration (frequency PRB offset combined with different symbol number selections for CORESET) for a band with 10 MHz minimum CH BW and 15 kHz SS SCS can be summarized similarly to Table 12, where Table 12A is for {SS SCS, RMSI SCS}={15 kHz, 15 kHz}, Table 12B is for {SS SCS, RMSI SCS}={15 kHz, 30 kHz} when the 30 kHz channel utilization is 51 PRB, and Table 12C is for {SS SCS, RMSI SCS}={15 kHz, 30 kHz} when the 30 kHz channel utilization is 50 PRB.

[0399] If the CORESET configuration tables for min CH BW=5 MHz and min CH BW=10 MHz are all supported, then in one approach there is no indication of the configuration tables and the UE needs to blindly detect whether the SS rasters are aligned or too close together for the UE to distinguish in the initial cell search.

[0400] In another approach, if the CORESET configuration tables for min CH BW=5 MHz and min CH BW=10 MHz are all supported, one bit is used in the PBCH to indicate the number of bands / configuration table / carrier frequency range. In one example, the bit used for indication can be a reserved bit in the PBCH and can only apply to <3 GHz. In another example, the bit used for indication can be a field in the PBCH used in the original half-frame indication, where the half-frame indication in the PBCH is only for >3 GHz, and the same field is used to indicate the number of bands / configuration table / carrier frequency range. Table 12A illustrates an example of an RMSI CORESET configuration for bands with at least a min CH BW of 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 15 kHz}.

[0401] [Table 12A]

[0402] Table 12B illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 30 kHz}.

[0403] [Table 12B]

[0404] Table 12C illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 30 kHz}.

[0405] [Table 12C]

[0406] In the third example, in the NR band, when the minimum CH BW=40 MHz, the SS SCS is determined to be 30 kHz. For this band, if the SS raster is defined below 30240 kHz (84 PRBs for the SS SCS), the CORESET configuration may differ from the table above, since the frequency offset indication may be different when using a different SS raster. A summary of the frequency offset (PRB level) configuration methods is shown in Table 13.

[0407] In this discussion, if the maximum TX BW is 40 MHz and the minimum UE BW is defined as 20 MHz, configurations for 192 PRB of RMSI CORESET BW with 15 kHz RMSI SCS and 96 PRB of RMSI CORESET BW with 30 kHz RMSI SCS are not supported. Table 13 shows an example of ΔF2 configuration for the TDM case.

[0408] [Table 13]

[0409] In such an example for SCS_CORESET=15kHz, if the carrier BW is 40MHz (106PRB for SS neuroradio and 216PRB for RMSI neuroradio) and the RMSI CORESET BW is 48PRB, then the display range can be the same as the SS raster (e.g., 84PRB for SS SCS and 168PRB for RMSI SCS), and Δf2=169PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure a PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 4PRB from the RMSI CORESET neuroradio perspective.

[0410] In such an example for SCS_CORESET=15kHz, if the carrier BW is 40MHz (106PRB for SS neuroradio and 216PRB for RMSI neuroradio) and the RMSI CORESET BW is 96PRB, the display range can be the same as the SS raster (e.g., 84PRB for SS SCS and 168PRB for RMSI SCS), and Δf2=121PRB, which is sufficient to configure N_ΔF2=2, i.e., a PRB level frequency offset between the edges of the SS block and the RMSI CORESET in two configurations, with possible values ​​being 0, 56PRB from the RMSI CORESET neuroradio perspective.

[0411] In such an example for SCS_CORESET=15kHz, if the carrier BW is 40MHz (106PRB for SS neuroradio and 216PRB for RMSI neuroradio) and the RMSI CORESET BW is 192PRB, the display range can be the same as the SS raster (e.g., 84PRB for SS SCS and 168PRB for RMSI SCS), and Δf2=25PRB, thereby providing N_ΔF2=7, i.e., seven configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and the possible values ​​can be X, X+25, X+50, X+75, X+100, X+125, X+150PRB from the RMSI CORESET neuroradio perspective, where X can be 0, 1 or 2.

[0412] In such an example for SCS_CORESET=30kHz, if the carrier BW is 40MHz (106PRB in SS and RMSI neuroradio) and the RMSI CORESET BW is 24PRB, then the display range can be the same as the SS raster (e.g., 84PRB in SS SCS) and Δf2=83PRB, which is sufficient to configure N_ΔF2=2, i.e., the PRB level frequency offset between the edges of the SS block and RMSI CORESET in two configurations, with possible values ​​being 0, 4PRB from the RMSI CORESET neuroradio perspective.

[0413] In such an example for SCS_CORESET=30kHz, if the carrier BW is 40MHz (106PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 48PRB, then the display range can be the same as the SS raster (e.g., 84PRB for SS SCS) and Δf2=59PRB, thereby sufficient to configure N_ΔF2=2, i.e., the PRB level frequency offset between the edges of the SS block and RMSI CORESET in two configurations, with possible values ​​being 0, 28PRB from the RMSI CORESET neuroradio perspective.

[0414] In such an example for SCS_CORESET=30kHz, if the carrier BW is 40MHz (106 PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 96 PRB, then the display range can be the same as the SS raster (e.g., 84 PRB for SS SCS) and Δf2=11 PRB, so N_ΔF2=8, i.e., 8 configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and possible values ​​can be 0, 11, 22, 33, 43, 54, 65, 76 PRB from the RMSI CORESET neuroradio perspective.

[0415] An example of CORESET configuration (frequency PRB offset combined with different symbol number selection for CORESET) for a band with 40 MHz minimum CH BW and 30 kHz SS SCS can be summarized as Table 14A and Table 14B, where the tables are determined for different combinations of {SCS_SS, SCS_RMSI}, e.g., Table 14A for {SS SCS, RMSI SCS}={30 kHz, 15 kHz} and Table 14B for {SS SCS, RMSI SCS}={30 kHz, 30 kHz}. Note that the minimum UE BW is assumed to be 20 MHz for this band (e.g., configurations for 192 PRB of RMSI CORESET BW with 15 kHz RMSI SCS and 96 PRB of RMSI CORESET BW with 30 kHz RMSI SCS are not supported). Note also that this table can be used for other bands as well, provided that the synchronization raster is the same or smaller than for the band with 40 MHz minimum CH BW. Table 14A illustrates an example RMSI CORESET configuration for bands with at least a 40 MHz minimum CH BW, where {SS SCS, RMSI SCS}={30 kHz, 15 kHz}.

[0416] [Table 14A]

[0417] Table 14B illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 40 MHz when {SS SCS, RMSI SCS}={30 kHz, 30 kHz}.

[0418] [Table 14B]

[0419] In the fourth example, in the NR band, when the minimum CH BW=40 MHz, the SS SCS is determined to be 30 kHz. For this band, if the SS raster is defined at 23040 kHz (64 PRBs for the SS SCS), the CORESET configuration may differ from the table above because the frequency offset indication may be different when using a different SS raster. A summary of the frequency offset (PRB level) configuration method is shown in Table 15.

[0420] In this discussion, if the maximum TX BW is defined as 40 MHz and the minimum UE BW is defined as 20 MHz, then configurations for 192 PRB of RMSI CORESET BW with 15 kHz RMSI SCS and 96 PRB of RMSI CORESET BW with 30 kHz RMSI SCS are not supported. Table 15 shows an example of ΔF2 configuration for the TDM case.

[0421] [Table 15]

[0422] In such an example for SCS_CORESET=15kHz, if the carrier BW is 40MHz (106PRB for SS neuroradio and 216PRB for RMSI neuroradio) and the RMSI CORESET BW is 48PRB, then the display range can be the same as the SS raster (e.g., 64PRB for SS SCS and 128PRB for RMSI SCS), and Δf2=169PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure a PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 4PRB from the RMSI CORESET neuroradio perspective.

[0423] In such an example for SCS_CORESET=15kHz, if the carrier BW is 40MHz (106PRB for SS neuroradio and 216PRB for RMSI neuroradio) and the RMSI CORESET BW is 96PRB, then the display range can be the same as the SS raster (e.g., 64PRB for SS SCS and 128PRB for RMSI SCS), and Δf2=121PRB, which is sufficient to configure N_ΔF2=2, i.e., a PRB level frequency offset between the edges of the SS block and the RMSI CORESET in two configurations, with possible values ​​being 0, 56PRB from the RMSI CORESET neuroradio perspective.

[0424] In such an example for SCS_CORESET=15kHz, if the carrier BW is 40MHz (106 PRB for SS neuroradio and 216 PRB for RMSI neuroradio) and the RMSI CORESET BW is 192 PRB, the display range can be the same as the SS raster (e.g., 64 PRB for SS SCS and 128 PRB for RMSI SCS), and Δf2=25 PRB, so that N_ΔF2=7, i.e., seven configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and the possible values ​​can be X, X+25, X+50, X+75, X+100, X+125 PRB from the RMSI CORESET neuroradio perspective, where X can be 14 or 15.

[0425] In such an example for SCS_CORESET=30kHz, if the carrier BW is 40MHz (106 PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 24 PRB, then the display range can be the same as the SS raster (e.g., 64 PRB for SS SCS) and Δf2=83 PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 2 PRB from the RMSI CORESET neuroradio perspective.

[0426] In such an example for SCS_CORESET=30kHz, if the carrier BW is 40MHz (106 PRB in SS and RMSI neuroradio) and the RMSI CORESET BW is 48 PRB, then the display range can be the same as the SS raster (e.g., 64 PRB in SS SCS) and Δf2=59 PRB, thereby providing N_ΔF2=2, i.e., two configurations sufficient to configure a PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 0, 28 PRB from the RMSI CORESET neuroradio perspective.

[0427] In such an example for SCS_CORESET=30kHz, if the carrier BW is 40MHz (106 PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 96 PRB, then the display range can be the same as the SS raster (e.g., 64 PRB for SS SCS) and Δf2=11 PRB, so N_ΔF2=6, i.e., 6 configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and the possible values ​​can be X+11, X+22, X+33, X+44, X+55, X+66 PRB from the RMSI CORESET neuroradio perspective, where X can be 0 or -1.

[0428] An example of CORESET configuration (frequency PRB offset combined with different symbol number selection for CORESET) for a band with 40 MHz minimum CH BW and 30 kHz SS SCS can be summarized as Table 16A and Table 16B, where the two tables are determined for different combinations of {SCS_SS, SCS_RMSI}, e.g., Table 16A for {SS SCS, RMSI SCS}={30 kHz, 15 kHz} and Table 16B for {SS SCS, RMSI SCS}={30 kHz, 30 kHz}. Note that the minimum UE BW is assumed to be 20 MHz for this band (e.g., configurations for 192 PRB of RMSI CORESET BW with 15 kHz RMSI SCS and 96 PRB of RMSI CORESET BW with 30 kHz RMSI SCS are not supported). Note that this table can also be used for other bands if the synchronization raster is the same or smaller than for the band with 40 MHz minimum CH BW. Table 16A illustrates an example RMSI CORESET configuration for bands with at least a 40 MHz minimum CH BW, where {SS SCS, RMSI SCS}={30 kHz, 15 kHz}.

[0429] [Table 16A]

[0430] Table 16B illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 40 MHz when {SS SCS, RMSI SCS}={30 kHz, 30 kHz}.

[0431] [Table 16B]

[0432] In the fifth example, in the NR band, when the minimum CH BW=20 MHz, the SS SCS is determined to be 30 kHz. If the SS raster is defined as 10080 kHz (28 PRBs with SS SCS) for this band, the CORESET configuration may differ from the above table because the frequency offset indication may be different when using a different SS raster. A summary of the frequency offset (PRB level) configuration method is shown in Table 17. Table 17 shows an example of ΔF2 configuration for the TDM case.

[0433] [Table 17]

[0434] In such an example for SCS_CORESET=15kHz, if the carrier BW is 20MHz (51PRBs for SS neuroradio and 106PRBs for RMSI neuroradio) and the RMSI CORESET BW is 48PRBs, then the display range can be the same as the SS raster (e.g., 28PRBs for SS SCS and 56PRBs for RMSI SCS), and Δf2=59PRBs, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 4PRBs from the RMSI CORESET neuroradio perspective.

[0435] In such an example for SCS_CORESET=15kHz, if the carrier BW is 20MHz (51 PRB for SS neuroradio and 106 PRB for RMSI neuroradio) and the RMSI CORESET BW is 96 PRB, the display range can be the same as the SS raster (e.g., 28 PRB for SS SCS and 56 PRB for RMSI SCS), and Δf2=11 PRB, so that N_ΔF2=6, i.e., 6 configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and the possible values ​​can be X, X+11, X+22, X+33, X+44, X+55 PRB from the RMSI CORESET neuroradio perspective, where X can be 0 or 1.

[0436] In such an example for SCS_CORESET=30kHz, if the carrier BW is 20MHz (51 PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 24 PRB, then the display range can be the same as the SS raster (e.g., 28 PRB for SS SCS and RMSI SCS), and Δf2=28 PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 2 PRB from the RMSI CORESET neuroradio perspective.

[0437] In such an example for SCS_CORESET=30kHz, if the carrier BW is 20MHz (51 PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 48 PRB, then the display range can be the same as the SS raster (e.g., 28 PRB for SS SCS and RMSI SCS), and Δf2=4 PRB, so N_ΔF2=7, i.e., seven configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 2, 6, 10, 14, 18, 22, 26 PRB from the RMSI CORESET neuroradio perspective.

[0438] An example of CORESET configuration (frequency PRB offset combined with different symbol number selection for CORESET) for a band with 20 MHz minimum CH BW and 30 kHz SS SCS can be summarized as Table 18A and Table 18B, where the two tables are determined for different combinations of {SCS_SS, SCS_RMSI}, for example, Table 18A is for {SS SCS, RMSI SCS}={30 kHz, 15 kHz}, and Table 18B is for {SS SCS, RMSI SCS}={30 kHz, 30 kHz}. As an example, X=1 in Table 18A. As another example, X=3 in Table 18B. Table 18A illustrates an RMSI CORESET configuration for a band with at least a minimum CH BW of 20 MHz when {SS SCS, RMSI SCS}={30 kHz, 15 kHz}.

[0439] [Table 18A]

[0440] Table 18B illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 20 MHz when {SS SCS, RMSI SCS}={30 kHz, 30 kHz}.

[0441] [Table 18B]

[0442] In the sixth example, in the NR band, when the minimum CH BW=20 MHz, the SS SCS is determined to be 30 kHz. If the SS raster is defined as 8640 kHz (64 PRBs with SS SCS) for this band, the CORESET configuration may differ from the above table because the frequency offset indication may be different when using a different SS raster. A summary of the frequency offset (PRB level) configuration method is shown in Table 19. Table 19 shows an example of ΔF2 configuration for the TDM case.

[0443] [Table 19]

[0444] In such an example for SCS_CORESET=15kHz, if the carrier BW is 20MHz (51 PRB for SS neuroradio and 106 PRB for RMSI neuroradio) and the RMSI CORESET BW is 48 PRB, then the display range can be the same as the SS raster (e.g., 24 PRB for SS SCS and 48 PRB for RMSI SCS), and Δf2=59 PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 4 PRB from the RMSI CORESET neuroradio perspective.

[0445] In such an example for SCS_CORESET=15kHz, if the carrier BW is 20MHz (51 PRB for SS neuroradio and 106 PRB for RMSI neuroradio) and the RMSI CORESET BW is 96 PRB, the display range can be the same as the SS raster (e.g., 24 PRB for SS SCS and 48 PRB for RMSI SCS), and Δf2=11 PRB, so that N_ΔF2=5, i.e., five configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, with possible values ​​being 6, 17, 28, 39, 50 PRB from the RMSI CORESET neuroradio perspective.

[0446] In such an example for SCS_CORESET=30kHz, if the carrier BW is 20MHz (51 PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 24 PRB, then the display range can be the same as the SS raster (e.g., 24 PRB for SS SCS and RMSI SCS), and Δf2=28 PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 2 PRB from the RMSI CORESET neuroradio perspective.

[0447] In such an example for SCS_CORESET=30kHz, if the carrier BW is 20MHz (51PRB for SS and RMSI neuroradio) and the RMSI CORESET BW is 48PRB, then the display range can be the same as the SS raster (e.g., 24PRB for SS SCS and RMSI SCS), and Δf2=4PRB, so that N_ΔF2=6, i.e., six configurations are sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and possible values ​​can be 4, 8, 12, 16, 20, 24PRB from the RMSI CORESET neuroradio perspective.

[0448] An example of a CORESET configuration (frequency PRB offset combined with different symbol number selection for CORESET) for a band with 20 MHz minimum CH BW and 30 kHz SS SCS can be summarized as Table 20A and Table 20B, where the two tables are determined for different combinations of {SCS_SS, SCS_RMSI}, Table 20A is for {SS SCS, RMSI SCS}={30 kHz, 15 kHz}, and Table 20B is for {SS SCS, RMSI SCS}={30 kHz, 30 kHz}. As an example, X=1 in Table 20A. As another example, X=3 in Table 20B. Table 20A illustrates an RMSI CORESET configuration for a band with at least a minimum CH BW of 20 MHz when {SS SCS, RMSI SCS}={30 kHz, 15 kHz}.

[0449] [Table 20A]

[0450] Table 20B illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 20 MHz when {SS SCS, RMSI SCS}={30 kHz, 30 kHz}.

[0451] [Table 20B]

[0452] In the seventh example, in the NR band, when the minimum CH BW=100 MHz, the SS SCS is determined to be 120 kHz. If the SS raster is defined as 51840 kHz (36 PRBs with SS SCS) for this band, the CORESET configuration may differ from the above table because the frequency offset indication may be different when using a different SS raster. A summary of the frequency offset (PRB level) configuration method for Pattern 1 is shown in Table 21. Table 21 shows an example of ΔF2 configuration for the TDM case.

[0453] [Table 21]

[0454] In such an example for SCS_CORESET=60 kHz and multiplexing pattern 1, if the carrier BW is 100 MHz (66 PRB in SS neuroradio and 132 PRB in RMSI neuroradio) and the RMSI CORESET BW is 48 PRB, the display range can be the same as the SS raster (e.g., 36 PRB in SS SCS and 72 PRB in RMSI SCS), and Δf2=85 PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 4 PRB from the RMSI CORESET neuroradio perspective.

[0455] In such an example for SCS_CORESET=60 kHz and multiplexing pattern 1, if the carrier BW is 100 MHz (66 PRB in SS neuroradio and 132 PRB in RMSI neuroradio) and the RMSI CORESET BW is 96 PRB, the display range can be the same as the SS raster (e.g., 36 PRB in SS SCS and 72 PRB in RMSI SCS), and Δf2=37 PRB, which is sufficient to configure N_ΔF2=2, i.e., a PRB level frequency offset between the edges of the SS block and the RMSI CORESET in two configurations, with possible values ​​being 10, 46 PRB from the RMSI CORESET neuroradio perspective.

[0456] In such an example for SCS_CORESET=120 kHz and multiplexing pattern 1, if the carrier BW is 100 MHz (66 PRB in SS and RMSI neuroradio) and the RMSI CORESET BW is 24 PRB, then the display range can be the same as the SS raster (e.g., 36 PRB in SS and RMSI SCS), and Δf2=43 PRB, so that N_ΔF2=1, i.e., one configuration is sufficient to configure the PRB level frequency offset between the edges of the SS block and the RMSI CORESET, and a possible value could be 2 PRB from the RMSI CORESET neuroradio perspective.

[0457] In such an example for SCS_CORESET=120 kHz and multiplexing pattern 1, if the carrier BW is 100 MHz (66 PRB in SS and RMSI neuroradio) and the RMSI CORESET BW is 48 PRB, the display range can be the same as the SS raster (e.g., 36 PRB in SS and RMSI SCS), and Δf2=19 PRB, which is sufficient to configure N_ΔF2=2, i.e., a PRB level frequency offset between the edges of the SS block and the RMSI CORESET in two configurations, with possible values ​​being 5, 23 PRB from the RMSI CORESET neuroradio perspective.

[0458] In such an example for multiplexing patterns 2 and 3, two configurations (eg, the top or bottom of the SS block) are sufficient, and the PRB offset value depends on the value of ΔF1 and whether the SCS of the SS and RMSI are the same or not.

[0459] An example of a CORESET configuration (frequency PRB offset combined with different symbol number selections for CORESET) for a band with 100 MHz minimum CH BW and 120 kHz SS SCS can be summarized as Tables 22A and 22B, where the two tables are determined for different combinations of {SCS_SS, SCS_RMSI}, where Table 22A is for {SS SCS, RMSI SCS}={120 kHz, 60 kHz} and Table 22B is for {SS SCS, RMSI SCS}={120 kHz, 120 kHz}. Table 22A illustrates an RMSI CORESET configuration for a band with at least a minimum CH BW of 100 MHz when {SS SCS, RMSI SCS}={120 kHz, 60 kHz}.

[0460] [Table 22A]

[0461] Table 22B illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 100 MHz when {SS SCS, RMSI SCS}={120 kHz, 120 kHz}.

[0462] [Table 22B]

[0463] Configuration table merge

[0464] If multiple CORESET configuration tables may be supported for overlapping bands with different minimum CH BWs, then in one approach, the multiple configuration tables may be merged into one table to support all bands.

[0465] Tables 23A to 23E are examples of merging Tables 7A and 12A for {SS SCS, RMSI SCS}={15 kHz, 15 kHz} to simultaneously support bands with a minimum CH BW of 5 MHz or 10 MHz, where Table 7A is used exclusively for bands with a 5 MHz minimum CH BW and Table 12A is used exclusively for bands with a 10 MHz minimum CH BW. Table 23A illustrates the RMSI CORESET configuration for bands with a minimum CH BW of at least 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 15 kHz}.

[0466] [Table 23A]

[0467] Table 23B illustrates an example of an RMSI CORESET configuration for bands with at least a minimum CH BW of 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 15 kHz}.

[0468] [Table 23B]

[0469] Table 23C illustrates an example of a RMSI CORESET configuration for bands with at least a minimum CH BW of 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 15 kHz}.

[0470] [Table 23C]

[0471] Table 23D illustrates an example of an RMSI CORESET configuration for bands with at least a minimum CH BW of 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 15 kHz}.

[0472] [Table 23D]

[0473] Table 23E illustrates an example RMSI CORESET configuration for bands with at least a minimum CH BW of 5 MHz or 10 MHz when {SS SCS, RMSI SCS}={15 kHz, 15 kHz}.

[0474] [Table 23E]

[0475] Table 24A is an example of merging Tables 14A and 20A for {SS SCS, RMSI SCS}={30 kHz, 15 kHz} to simultaneously support bands with a minimum CH BW of 40 MHz or 20 MHz when Table 14A is used exclusively for bands with a 40 MHz minimum CH BW and Table 20A is used exclusively for bands with a 20 MHz minimum CH BW. Table 24A illustrates an example RMSI CORESET configuration for bands with a minimum CH BW of at least 20 MHz or 40 MHz when {SS SCS, RMSI SCS}={30 kHz, 15 kHz}.

[0476] [Table 24A]

[0477] Table 24B is an example of merging Tables 14B and 20B for {SS SCS, RMSI SCS}={30 kHz, 30 kHz} to simultaneously support bands with minimum CH BW of 40 MHz or 20 MHz, when Table 14B is used exclusively for bands with 40 MHz minimum CH BW and Table 20B is used exclusively for bands with 20 MHz minimum CH BW. As an example, X=1 in Table 24A. As another example, X=3 in Table 24B. Table 24B illustrates an example RMSI CORESET configuration for bands with minimum CH BW of at least 20 MHz or 40 MHz, when {SS SCS, RMSI SCS}={30 kHz, 30 kHz}.

[0478] [Table 24B]

[0479] Configuration enhancements for measurement purposes.

[0480] In one embodiment, if it is not included in the table and a reserved configuration is available in the table, for all combinations of CORESET BW and multiple CORESET symbols, a center-aligned configuration of SS block and RMSI CORESET BW may be added to multiplexing pattern 1. The purpose of adding center-aligned SS block and RMSI CORESET BW is for better measurement using the signal of the SS block (e.g., SSS), and this configuration is not mandatory (e.g., the total number of configurations may exceed the theoretical minimum number of configurations).

[0481] In one example, using one of the reserved configurations, ΔF2=14 for “CORESET BW”=24 PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=1, 2 or 3 can be added to Table 7B.

[0482] In one example, using three of the reserved configurations, ΔF2=19 for “CORESET BW”=48PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=1, 2 or 3 can be added to Table 7B.

[0483] In another example, using three of the reserved configurations, ΔF2=4 for “CORESET BW”=48PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=1, 2 or 3 can be added to Table 7C.

[0484] In yet another example, using three of the reserved configurations, ΔF2=4 for “CORESET BW”=48PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=1, 2 and 3 can be added to Table 7E.

[0485] In yet another example, using one of the reserved configurations, ΔF2=2 for “CORESET BW”=24PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=2 can be added to Table 7F.

[0486] In yet another example, using two of the reserved configurations, ΔF2=8 for “CORESET BW”=96PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=1 and 2 can be added to Table 7G.

[0487] In yet another example, using two of the reserved configurations, ΔF2=4 for “CORESET BW”=48PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=1 and 2 can be added to Table 7H.

[0488] In yet another example, using three of the reserved configurations, ΔF2=28 for “CORESET BW”=96PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=1, 2 and 3 can be added to Table 14A.

[0489] In yet another example, using two of the reserved configurations, ΔF2=2 for “CORESET BW”=24PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=2 and 3 can be added to Table 14B.

[0490] In yet another example, using three of the reserved configurations, ΔF2=14 for “CORESET BW”=48PRB combined with “Multiplexing Pattern”=Pattern 1 and “Number of Symbols in CORESET”=1, 2 and 3 can be added to Table 14C.

[0491] Although the present disclosure has been described in exemplary embodiments, various changes and modifications may be suggested to those skilled in the art, and the present disclosure is intended to include such changes and modifications that fall within the scope of the appended claims.

[0492] Nothing in the description herein should be construed as indicating any particular element, step or function as an essential element for inclusion in the claims. The scope of patented subject matter is defined solely by the claims. [Explanation of symbols]

[0493] 130 Internet 210a Transmitter / Receiver 210b Transmitter / Receiver 210n Transmitter / Receiver 215 TX processing circuit 220 RX processing circuit 225 Controller / Processor 230 Memory 235 Backhaul / Network IF 310 RF Transmitter / Receiver 315 TX processing circuit 320 Microphone 325 RX processing circuit 330 Speaker 340 Processor 350 Touchscreen 355 Display 360 Memory 361 Operating Systems 362 Applications et al. 405 Channel Coding and Modulation 415 Size N IFFT 425 Additive Cyclic Prefix 460 Remove Cyclic Prefix 470 Size N FFT 480 Channel Decoding and Demodulation 510 Information Bits et al. 520 Encoder 530 Modulator 550 RE MAPPING 555 Transmission BW control 580 Filters 590 Send 610 Received 620 Filter 630 RE Demapping 635 Receive BW Control 660 Demodulator 670 Decoder 680 Information Bits et al. 710 Databit et al. 720 Encoder 730 Modulator 750 RE MAPPING 755 Transmission BW control 770 Filter 780 Send 810 Received 820 Filter 840 RE Demapping 845 Receive BW control 860 Demodulator 870 Decoder 880 Databit et al. 930a Data frame / subframe for slice 1 930b Data frame / subframe for slice 1 970a Data frame / subframe for slice 2 970b Data frame / subframe for slice 2 970c Data frame / subframe for slice 2

Claims

1. A method for a user equipment (UE) in a wireless communication system, comprising: receiving a synchronization signal / physical broadcast channel (SS / PBCH) block for a master information block (MIB) from a base station (BS); and receiving a remaining minimum system information (RMSI) based on the MIB from a base station (BS); The MIB includes configuration information; The value of the configuration information indicates one of at least one different candidate configurations including information on a multiplexing pattern of the SS / PBCH block and a CORESET, the number of resource blocks (RBs) of the CORESET, the number of symbols of the CORESET, and information on an RB level frequency offset between an RB associated with the SS / PBCH block and an RB associated with the CORESET according to a table; The tables are defined to be different from each other based on a subcarrier spacing (SCS) of the SS / PBCH block and an SCS of the CORESET.

2. The multiplexing pattern of the SS / PBCH block and the CORESET is a first multiplexing pattern, in which the SS / PBCH block and the CORESET occur at different time instances such that a bandwidth of the SS / PBCH block overlaps a bandwidth of the CORESET; a second multiplexing pattern in which the SS / PBCH block and the CORESET occur at different time instances such that the bandwidth of the SS / PBCH block does not overlap with the bandwidth of the CORESET; or 2. The method of claim 1, further comprising at least one of a third multiplexing pattern in which time instances of the SS / PBCH block and time instances of the CORESET occur at the same time instances overlapping, such that a bandwidth of the SS / PBCH block does not overlap a bandwidth of the CORESET.

3. For the first multiplexing pattern, When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0, 2, or 4RB; When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 12 or 16RB; When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=96RB, the RB level frequency offset configuration is determined to be 38RB; When SCSSS=15 kHz, SCSCORESET=30 kHz, and BWCORESET=24 RB, the RB level frequency offset configuration is determined to be one of 6, 7, or 8 RB; When SCSSS=15 kHz, SCSCORESET=30 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 18 or 20 RB; When SCSSS=30 kHz, SCSCORESET=15 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 2 or 6 RB; When SCSSS=30 kHz, SCSCORESET=15 kHz, and BWCORESET=96 RB, the RB level frequency offset configuration is determined to be 28 RB; When SCSSS=30kHz, SCSCORESET=30kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0, 1, 2, 3, or 4RB; When SCSSS=30kHz, SCSCORESET=30kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 12, 14, or 16RB; When SCSSS=120kHz, SCSCORESET=60kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 0 or 8RB; When SCSSS=120kHz, SCSCORESET=60kHz, and BWCORESET=96RB, the RB level frequency offset configuration is determined to be 28RB; When SCSSS=120kHz, SCSCORESET=120kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0 or 4RB, respectively; When SCSSS=120kHz, SCSCORESET=120kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be 14RB; When SCSSS=240 kHz, SCSCORESET=60 kHz, and BWCORESET=96 RB, the RB level frequency offset configuration is determined to be one of 0 or 16 RB; and 3. The method of claim 2, wherein when SCSSS=240 kHz, SCSCORESET=120 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 0 or 8 RB.

4. 2. The method of claim 1, wherein the MIB includes offset information including a resource element (RE) offset between subcarriers associated with the SS / PBCH block and subcarriers associated with a resource block grid.

5. A method for a base station (BS) in a wireless communication system, comprising: transmitting a synchronization signal / physical broadcast channel (SS / PBCH) block for a master information block (MIB) to a user equipment (UE); and transmitting remaining minimum system information (RMSI) based on the MIB to a user equipment (UE); The MIB includes configuration information; The value of the configuration information indicates one of at least one different candidate configurations including information on a multiplexing pattern of the SS / PBCH block and a CORESET, the number of resource blocks (RBs) of the CORESET, the number of symbols of the CORESET, and information on an RB level frequency offset between an RB associated with the SS / PBCH block and an RB associated with the CORESET according to a table; The tables are defined to be different from each other based on a subcarrier spacing (SCS) of the SS / PBCH block and an SCS of the CORESET.

6. The multiplexing pattern of the SS / PBCH block and the CORESET is a first multiplexing pattern, in which the SS / PBCH block and the CORESET occur at different time instances such that a bandwidth of the SS / PBCH block overlaps a bandwidth of the CORESET; a second multiplexing pattern in which the SS / PBCH block and the CORESET occur at different time instances such that the bandwidth of the SS / PBCH block does not overlap with the bandwidth of the CORESET; or 6. The method of claim 5, further comprising at least one of a third multiplexing pattern in which time instances of the SS / PBCH block and time instances of the CORESET occur at the same overlapping time instances such that a bandwidth of the SS / PBCH block does not overlap a bandwidth of the CORESET.

7. For the first multiplexing pattern, When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0, 2, or 4RB; When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 12 or 16RB; When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=96RB, the RB level frequency offset configuration is determined to be 38RB; When SCSSS=15 kHz, SCSCORESET=30 kHz, and BWCORESET=24 RB, the RB level frequency offset configuration is determined to be one of 6, 7, or 8 RB; When SCSSS=15 kHz, SCSCORESET=30 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 18 or 20 RB; When SCSSS=30 kHz, SCSCORESET=15 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 2 or 6 RB; When SCSSS=30 kHz, SCSCORESET=15 kHz, and BWCORESET=96 RB, the RB level frequency offset configuration is determined to be 28 RB; When SCSSS=30kHz, SCSCORESET=30kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0, 1, 2, 3, or 4RB; When SCSSS=30kHz, SCSCORESET=30kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 12, 14, or 16RB; When SCSSS=120kHz, SCSCORESET=60kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 0 or 8RB; When SCSSS=120kHz, SCSCORESET=60kHz, and BWCORESET=96RB, the RB level frequency offset configuration is determined to be 28RB; When SCSSS=120kHz, SCSCORESET=120kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0 or 4RB, respectively; When SCSSS=120kHz, SCSCORESET=120kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be 14RB; When SCSSS=240 kHz, SCSCORESET=60 kHz, and BWCORESET=96 RB, the RB level frequency offset configuration is determined to be one of 0 or 16 RB; and 7. The method of claim 6, wherein when SCSSS=240 kHz, SCSCORESET=120 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 0 or 8 RB.

8. 6. The method of claim 5, wherein the MIB includes offset information including a resource element (RE) offset between subcarriers associated with the SS / PBCH block and subcarriers associated with a resource block grid.

9. In a user equipment (UE) in a wireless communication system, At least one transceiver; and at least one processor; The at least one processor Receive a synchronization signal / physical broadcast channel (SS / PBCH) block for a master information block (MIB) from a base station (BS); receiving remaining minimum system information (RMSI) based on the MIB from a base station (BS); The MIB includes configuration information; The value of the configuration information indicates one of at least one different candidate configurations including information on a multiplexing pattern of the SS / PBCH block and a CORESET, the number of resource blocks (RBs) of the CORESET, the number of symbols of the CORESET, and information on an RB level frequency offset between an RB associated with the SS / PBCH block and an RB associated with the CORESET according to a table; The tables are defined differently based on the subcarrier spacing (SCS) of the SS / PBCH blocks and the SCS of the CORESET, user equipment (UE).

10. The multiplexing pattern of the SS / PBCH block and the CORESET is a first multiplexing pattern, in which the SS / PBCH block and the CORESET occur at different time instances such that a bandwidth of the SS / PBCH block overlaps a bandwidth of the CORESET; a second multiplexing pattern in which the SS / PBCH block and the CORESET occur at different time instances such that the bandwidth of the SS / PBCH block does not overlap with the bandwidth of the CORESET; or 10. The user equipment (UE) of claim 9, further comprising at least one of a third multiplexing pattern, wherein time instances of the SS / PBCH block and time instances of the CORESET occur at the same time instances overlapping, such that a bandwidth of the SS / PBCH block does not overlap a bandwidth of the CORESET.

11. For the first multiplexing pattern, When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0, 2, or 4RB; When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 12 or 16RB; When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=96RB, the RB level frequency offset configuration is determined to be 38RB; When SCSSS=15 kHz, SCSCORESET=30 kHz, and BWCORESET=24 RB, the RB level frequency offset configuration is determined to be one of 6, 7, or 8 RB; When SCSSS=15 kHz, SCSCORESET=30 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 18 or 20 RB; When SCSSS=30 kHz, SCSCORESET=15 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 2 or 6 RB; When SCSSS=30 kHz, SCSCORESET=15 kHz, and BWCORESET=96 RB, the RB level frequency offset configuration is determined to be 28 RB; When SCSSS=30kHz, SCSCORESET=30kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0, 1, 2, 3, or 4RB; When SCSSS=30kHz, SCSCORESET=30kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 12, 14, or 16RB; When SCSSS=120kHz, SCSCORESET=60kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 0 or 8RB; When SCSSS=120kHz, SCSCORESET=60kHz, and BWCORESET=96RB, the RB level frequency offset configuration is determined to be 28RB; When SCSSS=120kHz, SCSCORESET=120kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0 or 4RB, respectively; When SCSSS=120kHz, SCSCORESET=120kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be 14RB; When SCSSS=240 kHz, SCSCORESET=60 kHz, and BWCORESET=96 RB, the RB level frequency offset configuration is determined to be one of 0 or 16 RB; and The user equipment (UE) of claim 10, wherein when SCSSS=240 kHz, SCSCORESET=120 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 0 or 8 RB.

12. 10. The user equipment (UE) of claim 9, wherein the MIB includes offset information including a resource element (RE) offset between subcarriers associated with the SS / PBCH block and subcarriers associated with a resource block grid.

13. In a base station (BS) in a wireless communication system, At least one transceiver; and at least one processor; The at least one processor Transmitting a synchronization signal / physical broadcast channel (SS / PBCH) block for a master information block (MIB) to a user equipment (UE); Sending remaining minimum system information (RMSI) based on the MIB to a user equipment (UE); The MIB includes configuration information; The value of the configuration information indicates one of at least one different candidate configurations including information on a multiplexing pattern of the SS / PBCH block and a CORESET, the number of resource blocks (RBs) of the CORESET, the number of symbols of the CORESET, and information on an RB level frequency offset between an RB associated with the SS / PBCH block and an RB associated with the CORESET according to a table; The tables are defined to be different from each other based on the subcarrier spacing (SCS) of the SS / PBCH block and the SCS of the CORESET, Base Station (BS).

14. The multiplexing pattern of the SS / PBCH block and the CORESET is a first multiplexing pattern, in which the SS / PBCH block and the CORESET occur at different time instances such that a bandwidth of the SS / PBCH block overlaps a bandwidth of the CORESET; a second multiplexing pattern in which the SS / PBCH block and the CORESET occur at different time instances such that the bandwidth of the SS / PBCH block does not overlap with the bandwidth of the CORESET; or 14. The base station (BS) of claim 13, further comprising at least one of a third multiplexing pattern in which time instances of the SS / PBCH block and time instances of the CORESET occur at the same time instances overlapping, such that a bandwidth of the SS / PBCH block does not overlap a bandwidth of the CORESET.

15. For the first multiplexing pattern, When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0, 2, or 4RB; When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 12 or 16RB; When SCSSS=15kHz, SCSCORESET=15kHz, and BWCORESET=96RB, the RB level frequency offset configuration is determined to be 38RB; When SCSSS=15 kHz, SCSCORESET=30 kHz, and BWCORESET=24 RB, the RB level frequency offset configuration is determined to be one of 6, 7, or 8 RB; When SCSSS=15 kHz, SCSCORESET=30 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 18 or 20 RB; When SCSSS=30 kHz, SCSCORESET=15 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 2 or 6 RB; When SCSSS=30 kHz, SCSCORESET=15 kHz, and BWCORESET=96 RB, the RB level frequency offset configuration is determined to be 28 RB; When SCSSS=30kHz, SCSCORESET=30kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0, 1, 2, 3, or 4RB; When SCSSS=30kHz, SCSCORESET=30kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 12, 14, or 16RB; When SCSSS=120kHz, SCSCORESET=60kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be one of 0 or 8RB; When SCSSS=120kHz, SCSCORESET=60kHz, and BWCORESET=96RB, the RB level frequency offset configuration is determined to be 28RB; When SCSSS=120kHz, SCSCORESET=120kHz, and BWCORESET=24RB, the RB level frequency offset configuration is determined to be one of 0 or 4RB, respectively; When SCSSS=120kHz, SCSCORESET=120kHz, and BWCORESET=48RB, the RB level frequency offset configuration is determined to be 14RB; When SCSSS=240 kHz, SCSCORESET=60 kHz, and BWCORESET=96 RB, the RB level frequency offset configuration is determined to be one of 0 or 16 RB; and The base station (BS) of claim 14, wherein when SCSSS=240 kHz, SCSCORESET=120 kHz, and BWCORESET=48 RB, the RB level frequency offset configuration is determined to be one of 0 or 8 RB.

16. The base station (BS) of claim 13, wherein the MIB includes offset information including a resource element (RE) offset between subcarriers associated with the SS / PBCH block and subcarriers associated with a resource block grid.

Images