Method and apparatus for PBCH payload in higher frequency range

Abstract

The present disclosure relates to a communication method and system for integrating a fifth generation (5G) communication system and an Internet of Things (IoT) technology, wherein the fifth generation (5G) communication system supports a higher data rate than a fourth generation (4G) system. The present disclosure can be applied to intelligent services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, health care, digital education, smart retail, safety and security services. An apparatus and method for sending or receiving synchronization signals and physical broadcast channels (SS / PBCH) blocks in a wireless communication system. A method for operating a user equipment (UE) includes receiving an SS / PBCH block, decoding the content of the PBCH in the SS / PBCH block, and determining whether the wireless communication system is operated using a shared spectrum channel access based on the content of the PBCH. The method also includes determining the content of the PBCH in a first manner based on determining that the wireless communication system is operated using a shared spectrum channel access, or determining the content of the PBCH in a second manner based on determining that the wireless communication system is not operated using a shared spectrum channel access.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems, and more particularly, to physical broadcast channel (PBCH) payload design in a higher frequency range in wireless communication systems. Background Art

[0002] In order to meet the increased demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60GHz bands) in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-points (CoMP), receiving-end interference elimination, etc. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coded modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, as a human-centered connected network in which humans generate and consume information, is now developing toward the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of IoT technology and big data processing technology through connection with cloud servers, has emerged. Since technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" have been required for IoT implementation, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently. Such an IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RANs) as an application of the above-mentioned big data processing technologies can also be considered as an example of the convergence between 5G technologies and IoT technologies. Summary of the invention

[0005] Technical issues

[0006] The present disclosure relates to wireless communication systems, and more particularly, to PBCH payload design in a higher frequency range in wireless communication systems.

[0007] Problem Solution

[0008] In one embodiment, a user equipment (UE) in a wireless communication system is provided. The UE includes a transceiver configured to receive a synchronization signal and physical broadcast channel (SS / PBCH) block, and a processor operably connected to the transceiver. The processor is configured to decode the content of a PBCH in the SS / PBCH block; based on the content of the PBCH, determine whether the wireless communication system is operating with shared spectrum channel access; if the wireless communication system is operating with shared spectrum channel access, determine the content of the PBCH in a first manner; and if the wireless communication system is not operating with shared spectrum channel access, determine the content of the PBCH in a second manner.

[0009] In another embodiment, a base station (BS) in a wireless communication system is provided. The BS includes a processor configured to determine whether the wireless communication system operates using shared spectrum channel access; if the wireless communication system operates using shared spectrum channel access, configure the content of a physical broadcast channel (PBCH) according to a first method; if the wireless communication system does not operate using shared spectrum channel access, configure the content of the PBCH according to a second method; and encode the content of the configured PBCH in a synchronization signal and physical broadcast channel (SS / PBCH) block. The BS also includes a transceiver operably connected to the processor. The transceiver is configured to send the SS / PBCH block via a downlink channel.

[0010] In yet another embodiment, a method of a UE in a wireless communication system is provided. The method includes receiving an SS / PBCH block, decoding content of a PBCH in the SS / PBCH block, and determining whether the wireless communication system is operating with shared spectrum channel access based on the content of the PBCH. The method also includes determining the content of the PBCH in a first manner based on determining that the wireless communication system is operating with shared spectrum channel access, or determining the content of the PBCH in a second manner based on determining that the wireless communication system is not operating with shared spectrum channel access.

[0011] Other technical features will be apparent to those skilled in the art from the following drawings, description and claims.

[0012] Before starting the following inventive mode, it may be advantageous to set forth the definitions of certain words and phrases used in this patent document. The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives include direct and indirect communication. The terms "include" and "comprise" and their derivatives mean unlimited inclusion. The term "or" is inclusive, meaning and / or. The phrase "associated" and its derivatives refer to include, be included, interconnect with, include, be included, be connected to or connected with, be coupled to or coupled with, be communicable, cooperate with, interlace, juxtapose, approach, be combined with or combined with, have, have attributes, have a relationship or have a relationship with, etc. The term "controller" refers to any device, system or part thereof that controls at least one operation. Such a controller can be implemented with hardware or a combination of hardware and software and / or firmware. The functions associated with any particular controller can be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items may be used, and only one of the items in the list may be required. For example, "at least one of A, B, and C" includes any combination of: A, B, C, A and B, A and C, B and C, and A, B, and C.

[0013] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a part thereof suitable for implementation with a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or any other type of memory. "Non-transient" computer-readable media do not include wired, wireless, optical or other communication links that propagate transient electrical signals or other signals. Non-transient computer-readable media include media that can permanently store data and media that can store data and rewrite it later, such as rewritable optical discs or erasable storage devices.

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

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

[0016] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0017] Figure 2 An example gNB according to an embodiment of the present disclosure is shown;

[0018] Figure 3 An example UE according to an embodiment of the present disclosure is shown;

[0019] Figure 4 and Figure 5 Example wireless transmit and receive paths according to the present disclosure are shown;

[0020] Figure 6 illustrates example overlapping frequency bands with and without shared spectrum channel access according to embodiments of the present disclosure;

[0021] Figure 7 A flowchart of a method for indicating whether to utilize a shared spectrum channel access operation according to an embodiment of the present disclosure is shown;

[0022] Figure 8 shows an example multiplexing pattern between SSB and CORESET#0 according to an embodiment of the present disclosure;

[0023] Fig. 9 shows an example second type of channelization and synchronization grid according to an embodiment of the present disclosure;

[0024] Fig.10 An example CORESET#0BW of Mode 1 according to an embodiment of the present disclosure is shown;

[0025] Fig.11 An example mode 2 according to an embodiment of the present disclosure is shown;

[0026] Fig.12 An example CORESET#0BW of Mode 2 or Mode 3 according to an embodiment of the present disclosure is shown;

[0027] Fig.13 shows an example mode 3 according to an embodiment of the present disclosure;

[0028] Fig.14 An example carrier aggregation for achieving large bandwidth according to an embodiment of the present disclosure is shown;

[0029] Fig.15 An example set of narrow carriers using carrier aggregation to construct a wideband according to an embodiment of the present disclosure is shown;

[0030] Fig.16 shows an example synchronization grid design for unlicensed and licensed operation according to an embodiment of the present disclosure;

[0031] Fig.17A shows an example cross-carrier indication of CORESET#0 according to an embodiment of the present disclosure;

[0032] Fig. 17B Another example cross-carrier indication of CORESET#0 according to an embodiment of the present disclosure is shown; and

[0033] Fig.18 A flow chart of a method for determining the content of a PBCH according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0034] Discussed below Figures 1 to 18 The various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary and should not be interpreted in any way to limit the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0035] The following documents are incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 v15.7.0, “NR; Physical channels and modulation”; 3GPP TS 38.212 v15.7.0, “NR; Multiplexing and Channel coding”; 3GPP TS 38.213 v15.7.0, “NR; Physical Layer Procedures for Control”; 3GPP TS 38.214 v15.7.0, “NR; Physical Layer Procedures for Data”; and 3GPP TS 38.331 v15.7.0, “NR; Radio Resource Control (RRC) protocol specification”.

[0036] The following Figure 1-3 Various embodiments are described that may be implemented using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques in a wireless communication system. Figure 1-3 The description is not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0037] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown. Figure 1 The embodiment of the wireless network shown is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

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

[0039] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UE) within coverage area 120 of gNB 102. The first plurality of UEs include UE 111, which may be located in a small enterprise; UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M) such as a cellular phone, a wireless laptop, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of gNB 103. The second plurality of UEs include UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, LTE, LTE-A, WiMAX, WiFi, or other wireless communication technologies.

[0040] Depending on the network type, the term "base station" or "BS" may refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femto cell, a WiFi access point (AP), or other wireless-enabled devices. A base station may provide wireless access according to one or more wireless communication protocols (e.g., 5G / NR 3GPP NR, Long Term Evolution (LTE), Advanced LTE (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 document to refer to network infrastructure components that provide wireless access to remote terminals. In addition, depending on the network type, the term "user equipment" or "UE" may refer to any component, such as a "mobile station", "user station", "remote terminal", "wireless terminal", "reception point", or "user device". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).

[0041] The dashed lines illustrate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with gNBs, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and changes in the radio environment associated with natural and man-made obstacles.

[0042] As described in more detail below, one or more of UEs 111-116 include circuits, procedures, or a combination thereof for beam management and coverage enhancement for semi-persistent and configuration grant transmissions. In certain embodiments, one or more of gNBs 101-103 include circuits, procedures, or a combination thereof for beam management and coverage enhancement for semi-persistent and configuration grant transmissions.

[0043] although Figure 1 An example of a wireless network is shown, but Figure 1 Various changes may be made. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. In addition, gNB 101 may communicate directly with any number of UEs and provide wireless broadband access to network 130 to these UEs. Similarly, each gNB 102-103 may communicate directly with network 130 and provide direct wireless broadband access to network 130 to the UEs. In addition, gNBs 101, 102, and / or 103 may provide access to other or additional external networks, such as an external telephone network or other type of data network.

[0044] Figure 2 An example gNB 102 is shown according to an embodiment of the present disclosure. Figure 2 The embodiment of gNB 102 shown is for illustration only, and Figure 1 gNBs 101 and 103 may have the same or similar configurations. However, gNBs have a variety of configurations, and Figure 2 There is no intent to limit the scope of this disclosure to any particular implementation of a gNB.

[0045] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. gNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0046] The RF transceivers 210a-210n receive incoming RF signals from the antennas 205a-205n, such as signals transmitted by UEs in the network 100. The RF transceivers 210a-210n downconvert the incoming RF signals to produce IF or baseband signals. The IF or baseband signals are sent to the RX processing circuit 220, which generates processed baseband signals by filtering, decoding and / or digitizing the baseband or IF signals. The RX processing circuit 220 sends the processed baseband signals to the controller / processor 225 for further processing.

[0047] The TX processing circuit 215 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 225. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the sent baseband data to generate a processed baseband or IF signal. The RF transceivers 210a-210n receive the sent processed baseband or IF signals from the TX processing circuit 215, and up-convert the baseband or IF signals into RF signals, which are sent via the antennas 205a-205n.

[0048] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the reception of forward channel signals and the transmission of reverse channel signals via 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 higher-level wireless communication functionality. For example, the controller / processor 225 may support beamforming or directional routing operations, in which outgoing signals from / incoming signals to the multiple antennas 205a-205n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller / processor 225 may support any of a variety of other functions in the gNB 102.

[0049] The controller / processor 225 is also capable of executing programs and other processes, such as an OS, that reside in the memory 230. The controller / processor 225 may move data into or out of the memory 230 as required by the executing process.

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

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

[0052] although Figure 2 An example of a gNB 102 is shown, but the Figure 2 For example, gNB 102 may include any number of Figure 2 As a specific example, the access point may include multiple interfaces 235, and the controller / processor 225 may support routing functions to route data between different network addresses. As another specific example, although shown as including a single instance of TX processing circuitry 215 and a single instance of RX processing circuitry 220, the gNB 102 may include multiple instances of each processing circuit (such as one for each RF transceiver). In addition, Figure 2 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0053] Figure 3 An example UE 116 is shown in accordance with an embodiment of the present disclosure. Figure 3 The embodiment of UE 116 shown is for illustration only, and Figure 1 UEs 111-115 may have the same or similar configurations. However, UEs have a variety of configurations, and Figure 3 The scope of the present disclosure is not limited to any particular implementation of a UE.

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

[0055] RF transceiver 310 receives incoming RF signals from antenna 305 transmitted by a gNB of network 100. RF transceiver 310 downconverts the incoming RF signals to produce an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 325 sends the processed baseband signal to speaker 330 (e.g., for voice data) or processor 340 for further processing (such as for web browsing data).

[0056] The TX processing circuit 315 receives analog or digital voice data from the microphone 320, or receives other sent baseband data (such as network data, email or interactive video game data) from the processor 340. The TX processing circuit 315 encodes, multiplexes and / or digitizes the sent baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the sent processed baseband or IF signal from the TX processing circuit 315, and up-converts the baseband or IF signal into an RF signal, which is sent via the antenna 305.

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

[0058] The processor 340 is also capable of executing other processes and programs resident in the memory 360, such as processes for beam management. The processor 340 can move data into or out of the memory 360 as needed for the executed process. In some embodiments, the processor 340 is configured to execute the application 362 based on the OS 361 or in response to a signal received from the gNB or operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0059] Processor 340 is also coupled to touch screen 350 and display 355. An operator of UE 116 may input data into UE 116 using touch screen 350. Display 355 may be a liquid crystal display, light emitting diode display, or other display capable of presenting text and / or at least limited graphics (such as from a website).

[0060] 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).

[0061] although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3 The various components in the embodiment may be combined, further subdivided, or omitted, and additional components may be added as required. As a specific example, 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). In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE may be configured to operate as other types of mobile or stationary devices.

[0062] In order to meet the increased demand for wireless data traffic since the deployment of 4G communication systems, and to realize various vertical applications, efforts have been made to develop and deploy improved 5G / NR or pre-5G / NR communication systems. Therefore, 5G / NR or pre-5G / NR communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G / NR communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 28GHz or 60GHz bands) to achieve higher data rates, or in lower frequency bands (e.g., 6GHz) to achieve robust coverage and mobility support. The examples disclosed herein can also be applied to 5G communication systems, 6G, or even later versions of deployment that can use terahertz (THz) bands. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G / NR communication systems.

[0063] In addition, in the 5G / NR communication system, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference cancellation, etc.

[0064] The communication system includes a downlink (DL) and an uplink (UL), where the downlink refers to transmission from a base station or one or more transmission points to a UE, and the uplink refers to transmission from a UE to a base station or one or more reception points.

[0065] The time unit for DL ​​signaling or UL signaling on a cell is called a time slot and may include one or more symbols. A symbol may also be used as an additional time unit. A frequency (or bandwidth (BW)) unit is called a resource block (RB). An RB includes multiple subcarriers (SC). For example, a time slot may have a duration of 0.5 milliseconds or 1 millisecond, include 14 symbols, and an RB may include 12 SCs with an inter-SC spacing of 15KHz or 30KHz, etc.

[0066] DL signals include data signals that convey information content, control signals that convey DL control information (DCI), and reference signals (RS) also known as pilot signals. The gNB sends data information or DCI through the corresponding physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). PDSCH or PDCCH can be transmitted on a variable number of time slot symbols including one time slot symbol. For simplicity, the DCI format that schedules PDSCH reception of the UE is called DL DCI format, and the DCI format that schedules physical uplink shared channel (PUSCH) transmission from the UE is called UL DCI format.

[0067] The gNB transmits one or more of multiple types of RS including Channel State Information RS (CSI-RS) and Demodulation RS (DMRS). CSI-RS is primarily intended for UEs to perform measurements and provide Channel State Information (CSI) to the gNB. For channel measurements, non-zero power CSI-RS (NZP CSI-RS) resources are used. For Interference Measurement Report (IMR), CSI Interference Measurement (CSI-IM) resources associated with a Zero Power CSI-RS (ZP CSI-RS) configuration are used. The CSI process includes both NZP CSI-RS and CSI-IM resources.

[0068] The UE can determine the CSI-RS transmission parameters through DL control signaling or higher layer signaling (such as radio resource control (RRC) signaling) from the gNB. The transmission instance of CSI-RS can be indicated by DL control signaling or configured by higher layer signaling. DMRS is only transmitted in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0069] Figure 4 and Figure 5 Example wireless transmit and receive paths according to the present disclosure are shown. In the following description, the transmit path 400 may be described as being implemented in a gNB (e.g., gNB 102) and the receive path 500 may be described as being implemented in a UE (e.g., UE 116). However, it is understood that the receive path 500 may be implemented in a gNB and the transmit path 400 may be implemented in a UE. In some embodiments, the receive path 500 is configured to support codebook design and structure for a system with a 2D antenna array as described in embodiments of the present disclosure.

[0070] like Figure 4The transmit path 400 shown includes a channel coding and modulation block 405, a serial to parallel (S-to-P) block 410, an inverse fast Fourier transform (IFFT) block of size N 415, a parallel to serial (P-to-S) block 420, an add cyclic prefix block 425, and an upconverter (UC) 430. Figure 5 The receive path 500 shown includes a downconverter (DC) 555, a cyclic prefix removal block 560, a serial to parallel (S-to-P) block 565, a size-N fast Fourier transform (FFT) block 570, a parallel to serial (P-to-S) block 575, and a channel decoding and demodulation block 580.

[0071] As shown in diagram 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., low-density parity check (LDPC) coding), and modulates the input bits (e.g., with quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a frequency-domain modulation symbol sequence.

[0072] The serial to parallel block 410 converts (e.g., demultiplexes) the serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB 102 and the UE 116. The size-N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate a time domain output signal. The parallel to serial block 420 converts (e.g., 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 inserts a cyclic prefix into the time domain signal. The up-converter 430 modulates (e.g., up-converts) the output of the add cyclic prefix block 425 to an RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.

[0073] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and an operation opposite to that at gNB 102 is performed at UE 116.

[0074] like Figure 5 As shown, the down converter 555 down-converts the received signal to the baseband frequency, and the cyclic prefix removal block 560 removes the cyclic prefix to generate a serial time domain baseband signal. The serial to parallel block 565 converts the time domain baseband signal into a parallel time domain signal. The size N FFT block 570 performs an FFT algorithm to generate N parallel frequency domain signals. The parallel to serial block 575 converts the parallel frequency domain signals into a sequence of modulated data symbols. The channel decoding and demodulation block 580 demodulates and decodes the modulation symbols to recover the original input data stream.

[0075] Each of gNBs 101-103 may implement the following Figure 4 The transmission path 400 shown is similar to the transmission to UE 111-116 in the downlink and can be implemented as follows Figure 5 Receive path 500 is shown, which is similar to receiving from UE 111-116 in the uplink. Similarly, each of UE 111-116 can implement transmit path 400 for transmitting to gNB 101-103 in the uplink, and can implement receive path 500 for receiving from gNB 101-103 in the downlink.

[0076] Figure 4 and Figure 5 Each of the components in may be implemented using hardware only or a combination of hardware and software / firmware. As a specific example, Figure 4 and Figure 5 At least some of the components in the can be implemented with software, while other components can be implemented by configurable hardware or a mixture of software and configurable hardware. For example, FFT block 570 and IFFT block 515 can be implemented as configurable software algorithms, wherein the value of size N can be modified according to the implementation.

[0077] In addition, although described as using FFT and IFFT, this is exemplary only and should not be construed as limiting the scope of the present disclosure. Other types of transforms may be used, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions. It will be appreciated that for DFT and IDFT functions, the value of variable N may be any integer (e.g., 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N may be any integer that is a power of 2 (e.g., 1, 2, 4, 8, 16, etc.).

[0078] although Figure 4 and Figure 5 An example of a wireless transmit and receive path is shown, but the Figure 4 and Figure 5 Make various changes. For example, Figure 4 and Figure 5 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. Figure 4 and Figure 5 It is intended to illustrate examples of the types of transmit and receive paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communications in a wireless network.

[0079] The present disclosure focuses on the PBCH payload design for higher frequency ranges in order to support a potentially larger number of candidate synchronization signal / physical broadcast channel (SS / PBCH) blocks. The interleaving of the PBCH payload, the scrambling of the PBCH payload, and the related required changes of the demodulation reference signal (DM-RS) sequence of the PBCH are also specified in the present disclosure.

[0080] The present disclosure includes the following components and examples: an indication of using bits generated from the physical layer, including examples of adding PHY bits, reinterpreting PHY bits, and reconstructing a master information block (MIB) and PHY bits; an indication of quasi-co-location (QCL) parameters in a PBCH payload; an indication of operations in a PBCH payload that utilize or do not utilize shared spectrum channel access; and an indication of k_SSB; an indication of the fourth least significant bit (LSB) of the system frame number (SFN) in the MIB of the PBCH payload; corresponding changes to PBCH payload interleaving; corresponding changes to PBCH payload scrambling; and corresponding changes to the DM-RS sequence of the PBCH payload.

[0081] In NR Rel-15 and Rel-16, the PBCH payload consists of 24 bits from higher layers and 8 bits from the physical layer, where the 24 bits from the higher layers include 23 bits of MIB (as summarized in Table 1) and one MIB extension bit. The 8 bits from the physical layer are Know denoted by , refers to the timing information within 16 radio frames, as summarized in Table 2.

[0082] Table 1. MIB of NR Rel-15 and Rel-16

[0083] Fields value Number of bits systemFrameNumber BIT STRING(SIZE(6)) 6 subCarrierSpacingCommon ENUMERATED{scs15or60,scs30or120} 1 ssb-SubcarrierOffset INTEGER(0..15) 4 dmrs-TypeA-Position ENUMERATED{pos2,pos3} 1 pdcch-ConfigSIBI PDCCH-ConfigSIB1 8 cellBarred ENUMERATED{barred,notBarred} 1 intraFreqReselection ENUMERATED{allowed,notAllowed} 1 spare BIT STRING(SIZE(1)) 1

[0084] Table 2. Physical layer parameters in PBCH payload for NR Rel-15 and Rel-16

[0085]

[0086] For new carrier frequency ranges between 52.6 GHz and 71 GHz, new parameter sets with at least larger subcarrier spacing may be supported to accommodate larger phase noise and larger carrier bandwidth. When new parameter sets (e.g., including new subcarrier spacing) are supported in NR, the timing indication and corresponding PBCH payload design may need to be enhanced to support such new parameter sets. The present disclosure details a PBCH payload for a higher frequency range, wherein the higher frequency range includes at least a carrier frequency range between 52.6 GHz and 71 GHz, and may be applicable to licensed (e.g., not operating with shared spectrum channel access) and unlicensed bands (e.g., operating with shared spectrum channel access) in that frequency range.

[0087] Although the following exemplary description and embodiments assume OFDM or OFDMA, the present disclosure may be extended to other OFDM-based transmission waveforms or multiple access schemes, such as filtered OFDM (F-OFDM).

[0088] In one embodiment, there may be more than 64 candidate SS / PBCH blocks within a predefined time period (e.g., half a frame), for example, And the 7th LSB of the candidate SS / PBCH block index needs to be indicated in the payload of the PBCH. The support only applies to subcarrier spacing (SCS) of SS / PBCH blocks greater than 120kHz (e.g., 480kHz and / or 960kHz), so that the examples described in the present disclosure regarding the 7th LSB of the candidate SS / PBCH block index in the payload of the PBCH only apply to the corresponding SCS.

[0089] In one embodiment, PHY bits are increased. In one embodiment, for the higher carrier frequency ranges considered in the present disclosure, the number of bits in the PBCH payload provided by the higher layers remains the same as NR Rel-15 and Rel-16, and the number of bits in the PBCH payload generated by the physical layer is increased from 8 to 8+X (e.g., increased from NR Rel-15 and Rel-16), where X is a positive integer.

[0090] In one example, the additional X bits corresponding to the timing information are related to an enlarged maximum number of candidate SS / PBCH block locations within a half-frame, e.g., additional most significant bits (MSBs) of the candidate synchronization signal block (SSB, SS / PBCH block) index. Greater than 64, then Examples are shown in Table 3.

[0091] Table 3. Example increased number of bits in PBCH.

[0092]

[0093] In one example, the additional X bits corresponding to timing information are related to an expanded maximum number of candidate SS / PBCH block locations within a half-frame, e.g., an additional MSB of the candidate SSB index, and an indication of the parameters of the QCL information. Greater than 64, then Examples are shown in Table 4.

[0094] Table 4. Example increased number of bits in PBCH.

[0095]

[0096] In one example, and are the 6th, 5th and 4th LSB of the candidate SSB index respectively, and It is the 7th bit of the candidate SSB index.

[0097] In another example, and They are the 7th, 6th, 5th and 4th LSB of the candidate SSB indexes respectively.

[0098] In yet another example, and are the 6th, 5th and 4th LSB of the candidate SSB index respectively, and and They are the 7th and 8th bits of the candidate SSB index respectively.

[0099] In yet another example, and They are the 8th, 7th, 6th, 5th and 4th LSB of the candidate SSB indexes respectively.

[0100] In yet another example, and are the 6th, 5th and 4th LSB of the candidate SSB index respectively, and and They are the 7th, 8th and 9th bits of the candidate SSB index respectively.

[0101] In another example, and They are the 9th, 8th, 7th, 6th, 5th and 4th LSB of the candidate SSB indexes respectively.

[0102] In another example, This is a 3-bit field whose value is from {1, 2, 4, 8, 16, 32, 64}.

[0103] In another example, is a 3-bit field with values ​​in {1, 2, 4, 8, 16, 32, 64, "Not Applicable"}, where a numerical value applies to channel occupancy with channel sensing (e.g., listen-before-talk (LBT)) and a non-numerical value applies to channel occupancy without channel sensing (e.g., LBT).

[0104] For example, X may be rounded up to the nearest integer that is an integer multiple of 8 so that the total number of bits generated by the physical layer is one octet, and bits that carry no information are reserved.

[0105] In another embodiment, for the higher carrier frequency ranges considered in the present disclosure, the number of bits in the PBCH payload provided by the higher layers remains the same as NR Rel-15 and Rel-16, and the number of bits in the PBCH payload generated by the physical layer also remains the same as NR Rel-15 and Rel-16, but some of the bits generated by the physical layer may be reinterpreted.

[0106] In one example, the burst of SS / PBCH blocks within the periodic transmission period is confined to the first half of the frame, so that there is no need to indicate the half-frame timing. Can be used for other purposes, among which, in Rel-15 and Rel-16, Used to indicate a half frame. For example, if the number of candidate SS / PBCH blocks is greater than 64, the bit The 7th bit can be used to indicate the candidate SSB index. For another example, the bit Potentially combined with other bits in the PBCH payload to indicate QCL parameters Examples are shown in Table 5A.

[0107] In another example, the burst of SS / PBCH blocks within the periodic transmission period is limited to the second half of the frame, so that there is no need to indicate the half-frame timing. Can be used for other purposes. For example, if the number of candidate SS / PBCH blocks is greater than 64, then bit Can be used to indicate the 7th LSB of the candidate SSB index. For another example, the bit Potentially combined with other bits in the PBCH payload to indicate QCL parameters Examples are shown in Table 5A.

[0108] Table 5A. Example PHY bits for higher carrier frequency range

[0109]

[0110] For yet another example, if the maximum number of candidate SS / PBCH block positions within a half-frame is greater than 64 (e.g., ), and more DM-RS sequences are supported (e.g., more than 8 per cell), then the DM-RS sequence can carry more LSBs of the candidate SS / PBCH block index, and the bits generated by the physical layer can have different interpretations. An example is shown in Table 5B.

[0111] Table 5B. Example PHY bits for higher carrier frequency range

[0112]

[0113] In yet another embodiment, for the higher carrier frequency ranges considered in the present disclosure, the number of bits in the PBCH payload provided by higher layers remains the same as NR Rel-15 and Rel-16, and the number of bits in the PBCH payload generated by the physical layer also remains the same as NR Rel-15 and Rel-16, but the fields provided by higher layers and the bits generated by the physical layer may have different sizes and meanings.

[0114] In one example, the MIB in the PBCH payload contains the 7 MSBs of the SFN (e.g., the 4th LSB of the SFN is also included in the MIB), and one bit is removed from the MIB (e.g., a field with 1 bit or 1 bit from a field with multiple bits in Rel-15 and Rel-16).

[0115] In one example, the one bit removed from the MIB may be the field of subCarrierSpacingCommon, and the corresponding example MIB is shown in Table 6A.

[0116] Table 6A. Example MIB for higher carrier frequency range

[0117] Fields value Number of bits systemFrameNumber-new BIT STRING(SIZE(7)) 7 ssb-SubcurrierOffset INTEGER(0..15) 4 dmrs-TypeA-Position ENUMERATED{pos2,pos3} 1 pdcch-ConfigSIB1 PDCCH-ConfigSTB1 8 cellBarred ENUMERATED{barred,notBarred} 1 intraFreqReselection ENUMERATED{allowed,notAllowed} 1 spare BIT STRING(SIZE(1)) 1

[0118] In another example, the one bit removed from the MIB may be 1 bit from the field of pdcch-ConfigSIB1 (eg, from 8 bits to 7 bits), and the corresponding example MIB is shown in Table 6B.

[0119] Table 6B. Example MIB for higher carrier frequency range

[0120] Fields value Number of bits systemFrameNumber-new BIT STRING(SIZE(7)) 7 subCarrierSpacingCommon-new ENUMERATED{scs1-new,scs2-new} 1 ssb-SubcarrierOffset INTEGER(0..15) 4 dmrs-TypeA-Position ENUMERATED{pos2,pos3} 1 pdcch-ConfigSIB1-new PDCCH-ConfigSIB1-new 7 cellBarred ENUMERATED{barred,notBarred} 1 intraFreqReselection ENUMERATED{allowed,notAllowed} 1 spare BIT STRING(SIZE(1)) 1

[0121] In yet another example, one bit removed from the MIB may be a field of spare, and the corresponding example MIB is shown in Table 6C.

[0122] Table 6C. Example MIB for higher carrier frequency range

[0123] Fields value Number of bits systemFrameNumber-new BIT STRING(SIZE(7)) 7 subCarrierSpacingCommon-new ENUMERATED{scs1-new,scs2-new} 1 ssb-SubcarrierOffset INTEGER(0..15) 4 dmrs-TypeA-Position ENUMERATED{pos2,pos3} 1 pdcch-ConfigSIBI PDCCH-ConfigSIB1 8 cellBarred ENUMERATED{barred,notBarred} 1 intraFreqReselection ENUMERATED{allowed,notAllowed} 1

[0124] In yet another example, the fields in the MIB may retain their names and bit widths, but these fields may be reinterpreted to indicate other information, as described in the examples of the present disclosure. For this example, some bits in the PHY bits may be reinterpreted, as shown in Table 7.

[0125] Table 7. Example PHY bits for higher carrier frequency range

[0126]

[0127] In one embodiment, for the higher carrier frequency ranges considered in this disclosure, there is an indication of the parameters for the QCL assumption in the PBCH payload, so that if the corresponding SS / PBCH block has ( mod ), the UE determines that the SS / PBCH block is QCLed within the transmission window of the SS / PBCH block or across the transmission window, where: is the candidate SS / PBCH block index, and are the indicated parameters assumed for the QCL.

[0128] In one example, for the higher carrier frequency range considered in this disclosure, The value is taken from {1, 4, 16, 64}, and 2 bits in the PBCH payload are used to indicate

[0129] In another example, for the higher carrier frequency range considered in this disclosure, The value is taken from {1, 2, 4, 8, 16, 32, 64}, and 3 bits in the PBCH payload are used to indicate

[0130] In yet another example, for the higher carrier frequency range considered in the present disclosure, The value is taken from {1, 2, 4, 8, 16, 32, 48, 64}, and 3 bits in the PBCH payload are used to indicate

[0131] In yet another example, for the higher carrier frequency range considered in the present disclosure, The value is taken from {1, 2, 4, 8, 16, 24, 32, 40, 48, 56, 64}, and 4 bits in the PBCH payload are used to indicate

[0132] Use 2 bits in the PBCH payload to indicate An example of may be the 2 LSBs of ssb-SubcarrierOffset.

[0133] Use 2 bits in the PBCH payload to indicate Another example may be the 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0134] Use 2 bits in the PBCH payload to indicate Yet another example may be the 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0135] Use 2 bits in the PBCH payload to indicate Yet another example of may be the 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1.

[0136] Use 2 bits in the PBCH payload to indicate Yet another example of may be the 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1.

[0137] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset and 1 bit of subCarrierSpacingCommon.

[0138] Use 2 bits in the PBCH payload to indicate Another example of may be a combination of 1 bit of spare and 1 bit of subCarrierSpacingCommon.

[0139] Use 2 bits in the PBCH payload to indicate Another example of may be a combination of 1 bit of spare and 1 LSB of ssb-SubcarrierOffset.

[0140] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of controlResourceSetZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0141] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of controlResourceSetZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0142] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of searchSpaceZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0143] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of searchSpaceZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0144] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of controlResourceSetZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0145] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of controlResourceSetZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0146] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of searchSpaceZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0147] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of searchSpaceZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0148] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of controlResourceSetZero and 1 bit of spare in pdcch-ConfigSIB1.

[0149] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of controlResourceSetZero and 1 bit of spare in pdcch-ConfigSIB1.

[0150] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of searchSpaceZero and 1 bit of spare in pdcch-ConfigSIB1.

[0151] Use 2 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of searchSpaceZero and 1 bit of spare in pdcch-ConfigSIB1.

[0152] Use 2 bits in the PBCH payload to indicate Another example of may be a combination of 1 LSB of searchSpaceZero in pdcch-ConfigSIB1 and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0153] Use 2 bits in the PBCH payload to indicate Another example of may be a combination of 1 MSB of searchSpaceZero in pdcch-ConfigSIB1 and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0154] Use 3 bits in the PBCH payload to indicate An example of may be the 3 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0155] Use 3 bits in the PBCH payload to indicate Another example may be the 3 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0156] Use 3 bits in the PBCH payload to indicate Yet another example of may be the 3 LSBs of searchSpaceZero in pdcch-ConfigSIB1.

[0157] Use 3 bits in the PBCH payload to indicate Yet another example may be the 3 MSBs of searchSpaceZero in pdcch-ConfigSIB1.

[0158] Use 3 bits in the PBCH payload to indicate Another example of may be the 3 MSBs of ssb-SubcarrierOffset.

[0159] Use 3 bits in the PBCH payload to indicate Yet another example of may be the 3 LSBs of ssb-SubcarrierOffset.

[0160] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of controlResourceSetZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0161] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 2 MSBs of controlResourceSetZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0162] Use 3 bits in the PBCH payload to indicate Yet another example may be a combination of 2 MSBs of searchSpaceZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0163] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of searchSpaceZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0164] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset and 1 bit of subCarrierSpacingCommon.

[0165] Use 3 bits in the PBCH payload to indicate Another example may be a combination of the 2 MSBs of ssb-SubcarrierOffset and 1 bit of subCarrierSpacingCommon.

[0166] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of controlResourceSetZero and 1 bit of spare in pdcch-ConfigSIB1.

[0167] Use 3 bits in the PBCH payload to indicate Another example may be a combination of the 2 MSBs of controlResourceSetZero and 1 bit of spare in pdcch-ConfigSIB1.

[0168] Use 3 bits in the PBCH payload to indicate Another example may be a combination of the 2 MSBs of searchSpaceZero and 1 bit of spare in pdcch-ConfigSIB1.

[0169] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of searchSpaceZero and 1 bit of spare in pdcch-ConfigSIB1.

[0170] Use 3 bits in the PBCH payload to indicate Yet another example may be a combination of 2 LSBs of ssb-SubcarrierOffset and 1 bit of spare.

[0171] Use 3 bits in the PBCH payload to indicate Another example may be a combination of the 2 MSBs of ssb-SubcarrierOffset and 1 bit of spare.

[0172] Use 3 bits in the PBCH payload to indicate Another example of may be a combination of the 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1 and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0173] Use 3 bits in the PBCH payload to indicate Another example of may be a combination of 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1 and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0174] Use 3 bits in the PBCH payload to indicate Another example of may be a combination of 1 MSB of searchSpaceZero in pdcch-ConfigSIB1 and 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0175] Use 3 bits in the PBCH payload to indicate Another example of may be a combination of 1 LSB of searchSpaceZero in pdcch-ConfigSIB1 and 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0176] Use 3 bits in the PBCH payload to indicate Another example may be a combination of the 2 MSBs of searchSpaceZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0177] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of searchSpaceZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0178] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of searchSpaceZero and 2 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0179] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of searchSpaceZero and 2 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0180] Use 3 bits in the PBCH payload to indicate Another example may be a combination of the 2 MSBs of controlResourceSetZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0181] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of controlResourceSetZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0182] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of controlResourceSetZero and 2 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0183] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of controlResourceSetZero and 2 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0184] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

[0185] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of controlResourceSetZero, 1 bit of subCarrierSpacingCommon, and 1 bit of spare in pdcch-ConfigSIB1.

[0186] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of controlResourceSetZero, 1 bit of subCarrierSpacingCommon, and 1 bit of spare in pdcch-ConfigSIB1.

[0187] Use 3 bits in the PBCH payload to indicate Yet another example may be a combination of 1 LSB of searchSpaceZero, 1 bit of subCarrierSpacingCommon, and 1 bit of spare in pdcch-ConfigSIB1.

[0188] Use 3 bits in the PBCH payload to indicate Yet another example may be a combination of 1 MSB of searchSpaceZero, 1 bit of subCarrierSpacingCommon, and 1 bit of spare in pdcch-ConfigSIB1.

[0189] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, and 1 LSB of searchSpaceZero in pdcch-ConfigSIB1.

[0190] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, and 1 MSB of searchSpaceZero in pdcch-ConfigSIB1.

[0191] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0192] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0193] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0194] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0195] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0196] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0197] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 LSB of searchSpaceZero in pdcch-ConfigSIB1.

[0198] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 MSB of searchSpaceZero in pdcch-ConfigSIB1.

[0199] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0200] Use 3 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0201] Use 3 bits in the PBCH payload to indicate Another example of may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0202] Use 3 bits in the PBCH payload to indicate Another example of may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0203] Use 4 bits in the PBCH payload to indicate An example of may be a combination of 3 LSBs of controlResourceSetZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0204] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 3 MSBs of controlResourceSetZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0205] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 3 MSBs of searchSpaceZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0206] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 3 LSBs of searchSpaceZero and 1 bit of subCarrierSpacingCommon in pdcch-ConfigSIB1.

[0207] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 3 LSBs of ssb-SubcarrierOffset and 1 bit of subCarrierSpacingCommon.

[0208] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 3 MSBs of ssb-SubcarrierOffset and 1 bit of subCarrierSpacingCommon.

[0209] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 3 LSBs of controlResourceSetZero and 1 bit of spare in pdcch-ConfigSIB1.

[0210] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 3 MSBs of controlResourceSetZero and 1 bit of spare in pdcch-ConfigSIB1.

[0211] Use 4 bits in the PBCH payload to indicate Yet another example may be a combination of the 3 MSBs of searchSpaceZero and 1 bit of spare in pdcch-ConfigSIB1.

[0212] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 3 LSBs of searchSpaceZero and 1 bit of spare in pdcch-ConfigSIB1.

[0213] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 3 LSBs of ssb-SubcarrierOffset and 1 bit of spare.

[0214] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 3 MSBs of ssb-SubcarrierOffset and 1 bit of spare.

[0215] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of the 3 MSBs of searchSpaceZero in pdcch-ConfigSIB1 and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0216] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of 3 LSBs of searchSpaceZero in pdcch-ConfigSIB1 and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0217] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of the 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1 and the 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0218] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of the 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1 and the 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0219] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of 1 MSB of searchSpaceZero in pdcch-ConfigSIB1 and 3 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0220] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of 1 LSB of searchSpaceZero in pdcch-ConfigSIB1 and 3 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0221] Use 4 bits in the PBCH payload to indicate Yet another example of may be a combination of the 3 MSBs of searchSpaceZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0222] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 3 LSBs of searchSpaceZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0223] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 2 MSBs of searchSpaceZero and the 2 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0224] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 2 LSBs of searchSpaceZero and the 2 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0225] Use 4 bits in the PBCH payload to indicate Yet another example may be a combination of 1 MSB of searchSpaceZero and 3 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0226] Use 4 bits in the PBCH payload to indicate Yet another example may be a combination of 1 LSB of searchSpaceZero and 3 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0227] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 3 MSBs of controlResourceSetZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0228] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 3 LSBs of controlResourceSetZero and 1 LSB of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0229] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 2 MSBs of controlResourceSetZero and the 2 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0230] Use 4 bits in the PBCH payload to indicate Another example may be a combination of the 2 LSBs of controlResourceSetZero and the 2 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0231] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of controlResourceSetZero and 3 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0232] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of controlResourceSetZero and 3 LSBs of ssb-SubcarrierOffset in pdcch-ConfigSIB1.

[0233] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

[0234] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of controlResourceSetZero, 1 bit of subCarrierSpacingCommon, and 1 bit of spare in pdcch-ConfigSIB1.

[0235] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 MSBs of controlResourceSetZero, 1 bit of subCarrierSpacingCommon, and 1 bit of spare in pdcch-ConfigSIB1.

[0236] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of searchSpaceZero, 1 bit of subCarrierSpacingCommon, and 1 bit of spare in pdcch-ConfigSIB1.

[0237] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 MSBs of searchSpaceZero, 1 bit of subCarrierSpacingCommon, and 1 bit of spare in pdcch-ConfigSIB1.

[0238] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of spare, and 1 LSB of searchSpaceZero in pdcch-ConfigSIB1.

[0239] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of spare, and 1 MSB of searchSpaceZero in pdcch-ConfigSIB1.

[0240] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, and 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1.

[0241] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, and 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1.

[0242] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of spare, and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0243] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of spare, and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0244] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, and 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0245] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, and 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0246] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0247] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0248] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0249] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0250] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0251] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0252] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0253] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0254] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 LSB of searchSpaceZero in pdcch-ConfigSIB1.

[0255] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 MSB of searchSpaceZero in pdcch-ConfigSIB1.

[0256] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1.

[0257] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1.

[0258] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0259] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0260] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0261] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 2 LSBs of ssb-SubcarrierOffset, 1 bit of subCarrierSpacingCommon, and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

[0262] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, and 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0263] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, and 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

[0264] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0265] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0266] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0267] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0268] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of 1 bit of spare, 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0269] Use 4 bits in the PBCH payload to indicate Another example of may be a combination of 1 bit of spare, 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

[0270] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0271] Use 4 bits in the PBCH payload to indicate Another example may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 bit of spare, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit of spare.

[0272] Use 4 bits in the PBCH payload to indicate Yet another example of may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB of searchSpaceZero in pdcch-ConfigSIB1, 1 bit of spare, and 1 bit of spare.

[0273] Use 4 bits in the PBCH payload to indicate Yet another example of may be a combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB of searchSpaceZero in pdcch-ConfigSIB1, 1 bit of spare, and 1 bit of spare.

[0274] In another embodiment, for the higher carrier frequency ranges considered in the present disclosure, the SIB (eg, SIB1) indicates In a further example, the PBCH payload and the SIB are both indicated Among them, PBCH The value of is in SIB For example, PBCH is used to indicate The bit width of the field(s) is smaller than that used in the SIB to indicate The bit width of the field indicated in the SIB Example values ​​of can refer to the PBCH payload indicated Example value of .

[0275] In one embodiment, for the higher carrier frequency ranges considered in the present disclosure, there is an indication in the PBCH payload as to whether the frequency layer is operating with shared spectrum channel access (e.g., whether an LBT process is required when initializing channel occupancy) where the corresponding SS / PBCH block is located. Figure 6 As shown, the first frequency band can operate using shared spectrum channel access (for example, an LBT process is required when initializing channel occupancy), and the second frequency band can operate without using shared spectrum channel access (for example, an LBT process is not required when initializing channel occupancy), wherein the first frequency band and the second frequency band overlap in the frequency domain.

[0276] If the SS / PBCH blocks are located on overlapping bandwidths, the indication in the PBCH payload may help the UE distinguish whether the corresponding SS / PBCH blocks are operating with shared spectrum channel access. For another example, a frequency band may operate with shared spectrum channel access in a first geographic region (e.g., an LBT process is required when initializing channel occupancy) and may operate without shared spectrum channel access in a second geographic region (e.g., an LBT process is not required when initializing channel occupancy), then the indication in the PBCH payload may help the UE distinguish whether the corresponding SS / PBCH blocks are operating with shared spectrum channel access.

[0277] Figure 6 Example overlapping frequency bands 600 are shown with and without shared spectrum channel access according to an embodiment of the present disclosure. Figure 6 The illustrated embodiment of overlapping strips 600 is for illustration only.

[0278] In one embodiment, based on the indication, the UE may interpret at least a portion of the content of the PBCH differently for operations utilizing shared spectrum channel access and operations not utilizing shared spectrum channel access. Figure 7 An example UE process for determining a payload for a PBCH based on an indication of whether operation with shared spectrum channel access is utilized is shown in FIG.

[0279] Figure 7 A flowchart of a method 700 for indicating whether to utilize a shared spectrum channel access operation according to an embodiment of the present disclosure is shown. Figure 7 The illustrated embodiment of method 700 is for illustration only. Figure 7 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described.

[0280] like Figure 7 As shown, method 700 starts at step 702. In step 702, a UE (e.g., Figure 1 111-116) shown in step 704) decodes the payload of the PBCH. Subsequently, the UE determines in step 704 an indication of whether to utilize the operation of the shared spectrum channel access. Next, in step 706, the UE determines whether the shared spectrum channel access is implemented. In step 706, if yes, the UE interprets at least a portion of the payload of the PBCH in a first manner in step 708. In step 706, if no, the UE interprets at least a portion of the payload of the PBCH in a second manner in step 710.

[0281] In one example, the indication of whether to operate with shared spectrum channel access may have 1 bit in the payload of the PBCH, where the 1-bit indication may be a reinterpretation of one bit in the payload of the PBCH.

[0282] For the first example, 1 bit indicates that 1 bit of ssb-SubcarrierOffset can be reinterpreted, for example, 1 LSB or MSB.

[0283] For the second example, 1 bit indicates that 1 bit of controlResourceSetZero in pdcch-ConfigSIB1 may be reinterpreted, for example, 1 LSB or MSB.

[0284] For the third example, 1 bit indicates that 1 bit of searchSpaceZero in pdcch-ConfigSIB1 may be reinterpreted, for example, 1 LSB or MSB.

[0285] For the fourth example, 1 bit indicates that 1 bit of subCarrierSpacingCommon may be reinterpreted.

[0286] For the fifth example, 1 bit indicates that the 1 bit of spare can be reinterpreted.

[0287] For the sixth example, the 1-bit indication can be reinterpreted 1 bit.

[0288] For the seventh example, the 1-bit indication can be reinterpreted 1 bit.

[0289] In another example, the indication of whether to operate with shared spectrum channel access may be the use of an unused field combination in the payload of the PBCH.

[0290] For example, when cellBarred is provided as "notBarred", if intraFreqReselection is provided as "allowed", the UE determines that the frequency layer operates using shared spectrum channel access; and if intraFreqReselection is provided as "notAllowed", the UE determines that the frequency layer does not operate using shared spectrum channel access.

[0291] In another example, when cellBarred is provided as "notBarred", if intraFreqReselection is provided as "allowed", the UE determines that the frequency layer does not operate with shared spectrum channel access; and if intraFreqReselection is provided as "notAllowed", the UE determines that the frequency layer operates with shared spectrum channel access.

[0292] In yet another example, an indication of whether to utilize a shared spectrum channel access operation is associated with a QCL parameter Joint encoding.

[0293] For example, QCL parameters A non-numeric value of may be used to indicate an operation that does not utilize shared spectrum channel access. In one example, is a 3-bit field taking values ​​from {1, 2, 4, 8, 16, 32, 64, “Not Applicable”}, where a numerical value indicates channel occupancy with channel sensing (e.g., LBT) and a non-numerical value indicates channel occupancy without channel sensing (e.g., LBT).

[0294] For another example, the same QCL parameter as the maximum number of candidate SS / PBCH blocks may be used. The value of is used to indicate operation that does not utilize shared spectrum channel access.

[0295] In another embodiment, an RRC parameter may be used to indicate whether the frequency layer is operating with shared spectrum channel access. For example, the indication may be in a cell-specific configuration, such as SIB1 and / or ServingCellConfigCommon. As another example, the indication may be in a UE-specific configuration.

[0296] In one embodiment, for the higher carrier frequency ranges considered in this disclosure, there may be an indication in the MIB on the 4th LSB of the SFN using 1 bit reinterpreted from Rel-15 or Rel-16.

[0297] For the first example, 1 bit indicates that 1 bit of ssb-SubcarrierOffset can be reinterpreted, for example, 1 LSB or MSB.

[0298] For the second example, 1 bit indicates that 1 bit of controlResourceSetZero in pdcch-ConfigSIB1 may be reinterpreted, for example, 1 LSB or MSB.

[0299] For the third example, 1 bit indicates that 1 bit of searchSpaceZero in pdcch-ConfigSIB1 may be reinterpreted, for example, 1 LSB or MSB.

[0300] For the fourth example, 1 bit indicates that 1 bit of subCarrierSpacingCommon may be reinterpreted.

[0301] For the fifth example, 1 bit indicates that the 1 bit of spare can be reinterpreted.

[0302] For this embodiment, the PHY bits The instructions can be reinterpreted. It is the 4th LSB of SFN in Rel-15 and Rel-16, and an example is shown in Table 7.

[0303] In one embodiment, for the higher carrier frequency ranges considered in this disclosure, the number k SSB From the public resource block The subcarrier offset from subcarrier 0 in the SS / PBCH block to subcarrier 0 of the SS / PBCH block, or used to provide information about an SS / PBCH block defined by another cell based on a value range.

[0304] In one example, for the higher carrier frequency range considered in this disclosure, the number k SSB It is expressed in terms of the subcarrier spacing of CORESET#0. For example, the subcarrier spacing of CORESET#0 is the same as the subcarrier spacing of the SS / PBCH block. For another example, the subcarrier spacing of CORESET#0 is provided by a higher layer parameter subCarrierSpacingCommon.

[0305] In one example, if the LSB of ssb-SubcarrierOffset is used to indicate other information (e.g., QCL parameter or whether to utilize the operation of shared spectrum channel access, or the 4LSB of SFN, etc.), as described in the example of the present disclosure, then (or equivalently, The 4 LSBs of ssb-SubcarrierOffset are given by the higher layer parameter ssb-SubcarrierOffset. otherwise,

[0306] In another example, if the 2 LSBs of ssb-SubcarrierOffset are used to indicate other information (e.g., QCL parameters or whether to utilize the operation of shared spectrum channel access, or the 4LSB of SFN, etc.), as described in the example of the present disclosure, then (or equivalently, The 4 LSBs of ssb-SubcarrierOffset are given by the higher layer parameter ssb-SubcarrierOffset. otherwise,

[0307] In yet another example, if the 3 LSBs of ssb-SubcarrierOffset are used to indicate other information (e.g., QCL parameters or whether to utilize the operation of shared spectrum channel access, or the 4LSB of SFN, etc.), as described in the example of the present disclosure, then (or equivalently, The 4 LSBs of ssb-SubcarrierOffset are given by the higher layer parameter ssb-SubcarrierOffset. otherwise,

[0308] In another example, if the field ssb-SubcarrierOffset is used to indicate other information (e.g., QCL parameter or whether to utilize the operation of shared spectrum channel access, or the 4LSB of SFN, etc.), as described in the example of the present disclosure, then (or equivalently, The 4 LSBs of ssb-SubcarrierOffset are given by the higher layer parameter ssb-SubcarrierOffset. Otherwise, k SSB =0.

[0309] In one embodiment, for the higher carrier frequency ranges considered in the present disclosure, when the bits in the PBCH payload are reinterpreted, the interleaved PBCH payload may have corresponding changes.

[0310] In one example, the interleaving of bits generated by the physical layer in the PBCH payload may be as follows: For one example, this example may apply to at least Example 1 in Table 5A.

[0311] Table 8. Interleaving of bits generated by the physical layer in the PBCH payload

[0312]

[0313] For another example, the interleaving of bits generated by the physical layer in the PBCH payload may be as follows: For one example, this example may apply to at least Example 2 in Table 5A.

[0314] Table 9. Interleaving of bits generated by the physical layer in the PBCH payload

[0315]

[0316] For yet another example, the interleaving of bits generated by the physical layer in the PBCH payload may be as follows. As an example, this example may be applicable to at least Example 1 in Table 7.

[0317] Table 10. Interleaving of bits generated by the physical layer in the PBCH payload

[0318]

[0319] For yet another example, the interleaving of bits generated by the physical layer in the PBCH payload may be as follows. As an example, this example may at least apply to Example 2 in Table 7.

[0320] Table 11. Interleaving of bits generated by the physical layer in the PBCH payload

[0321]

[0322] In one embodiment, for the higher carrier frequency ranges considered in this disclosure, when the bits in the PBCH payload are reinterpreted, the scrambling of the PBCH payload may have corresponding changes.

[0323] In one example, for Example 1 and Example 2 in Table 5A, the length of the segment of the scrambling sequence (eg, M) is determined to be M=A-6.

[0324] In another example, for Example 1 and Example 2 in Table 7, the length of the segment of the scrambling sequence (eg, M) is determined to be M=A-7.

[0325] In one embodiment, for the higher carrier frequency ranges considered in the present disclosure, the number of DM-RS sequences for the PBCH of each cell may be increased (eg, greater than 8).

[0326] In one example, the generation of the DM-RS sequence for the PBCH is based on a pseudo-random sequence c(i) with a change to the initial condition of the generator to support a larger number of sequences per cell, where the initial condition is based on: in, is the LSB of the candidate SS / PBCH block index, where and is the number of DM-RS sequences per cell.

[0327] In one example, Make are the 4 LSBs of the candidate SS / PBCH block index, and c 1 =2 11 , c 2 =2 6 .

[0328] In another example, Make are the 4 LSBs of the candidate SS / PBCH block index, and c 1 =2 0 , c 2 =2 14 .

[0329] In yet another example, Make are the 4 LSBs of the candidate SS / PBCH block index, and c 1 =2 16 , c 2 =2 3 .

[0330] In yet another example, Make are the 5 LSBs of the candidate SS / PBCH block index, and c 1 =2 11 , c 2 =2 6 .

[0331] In yet another example, Make are the 5 LSBs of the candidate SS / PBCH block index, and c 1 =2 16 , c 2 =2 3 .

[0332] In yet another example, Make are the 5 LSBs of the candidate SS / PBCH block index, and c 1 =2 12 , c 2 =2 4 .

[0333] In yet another example, Make are the 6 LSBs of the candidate SS / PBCH block index, and c 1 =2 11 , c 2 =2 6 .

[0334] In yet another example, Make are the 6 LSBs of the candidate SS / PBCH block index, and c 1 =2 16 , c 2 =2 3 .

[0335] The present disclosure focuses on CORESET#0 configuration. In particular, embodiments of the present disclosure are at least applicable to operations utilizing shared spectrum channel access. Embodiments regarding configuration design are based on the multiplexing pattern between SS / PBCH blocks and CORESET#0. Details of the present disclosure include: (1) CORESET#0 configuration of Mode 1; (2) CORESET#0 configuration of Mode 2; and (3) CORESET#0 configuration of Mode 3.

[0336] In NR Rel-15 and Rel-16, the MIB in the payload of the PBCH includes a field containing the configuration of the CORESET for monitoring the Type0-PDCCH common search space (CSS), which is denoted as CORESET#0. In NR Rel-15 and Rel-16, the multiplexing mode between the SS / PBCH block (SSB) and CORESET#0, the BW of CORESET#0, the number of symbols of CORESET#0, and the RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block are jointly coded using 4 bits, namely the controlResourceSetZero field in pdcch-ConfigSIB1.

[0337] In NR Rel-15 and Rel-16, three multiplexing modes between SS / PBCH blocks and CORESET#0 are already supported. In mode 1, the bandwidth of the SS / PBCH block overlaps with the bandwidth of CORESET#0, and the instance of the SS / PBCH block and the instance of CORESET#0 do not occur at the same time; in mode 2, the bandwidth of the SS / PBCH block and the bandwidth of CORESET#0 do not overlap, and the instance of the SS / PBCH block and the instance of CORESET#0 do not occur at the same time; in mode 3, the bandwidth of the SS / PBCH block and the bandwidth of CORESET#0 do not overlap, and the instance of the SS / PBCH block and the instance of CORESET#0 occur at the same time. The description of the multiplexing mode is as follows Figure 8 shown.

[0338] Figure 8 An example multiplexing pattern 800 between SSB and CORESET #0 is shown according to an embodiment of the present disclosure. Figure 8The illustrated embodiment of multiplexing pattern 800 is for illustration only.

[0339] For the new carrier frequency range between 52.6 GHz and 71 GHz, at least a new parameter set with a larger subcarrier spacing can be supported to accommodate larger phase noise and larger carrier bandwidth. When the NR supports a new parameter set (e.g., including a new subcarrier spacing), the CORESET#0 configuration can be enhanced to support this new parameter set. The present disclosure specifies the details of the CORESET#0 configuration for a higher frequency range, where the higher frequency range includes at least the carrier frequency range between 52.6 GHz and 71 GHz, and can be applicable to licensed (e.g., not operating with shared spectrum channel access) and unlicensed bands (e.g., operating with shared spectrum channel access) in this frequency range.

[0340] In the present disclosure, CORESET#0 refers to a control resource set (CORESET) of a Type0-PDCCH common search space set.

[0341] In one embodiment, for a given supported combination of SS / PBCH blocks and SCS of CORESET#0, a common configuration table can be used for both operations with and without shared spectrum channel access. For this example, for a given supported combination of SS / PBCH blocks and SCS of CORESET#0, the examples in this disclosure can be used for operations with and without shared spectrum channel access.

[0342] In another embodiment, for a given supported combination of SS / PBCH blocks and SCS of CORESET#0, separate configuration tables may be used for operation with or without shared spectrum channel access. For this example, for a given supported combination of SS / PBCH blocks and SCS of CORESET#0, one example in the present disclosure may be used for operation with shared spectrum channel access, and another example in the present disclosure may be used for operation without shared spectrum channel access.

[0343] In one embodiment, there may be a large granularity of channel grid spacing (e.g., as large as one nominal channel BW) and a large granularity of synchronization grid spacing (e.g., as large as one nominal channel BW) such that there is only one synchronization grid entry within the nominal channel BW. For example, the channelization and synchronization grid design may be suitable for operation with shared spectrum channel access, and the example CORESET#0 configuration in the present disclosure may be suitable for operation with shared spectrum channel access.

[0344] In one example, within a nominal channel BW (eg, BW may be 2.16 GHz), there is one sync grid entry within the nominal channel and one channel grid entry within the nominal channel. Figure 8 An illustration of this example is shown.

[0345] Fig. 9 An example second type of channelization and synchronization grid 900 is shown in accordance with an embodiment of the present disclosure. Fig. 9 The illustrated embodiment of the second type of channelization and synchronization grid 900 is for illustration only.

[0346] In one embodiment, the SCS supported by the nominal channel may be 960 kHz, and the corresponding number of available RBs (eg, excluding the guard band) may be For example, for a nominal bandwidth of around 2 GHz, For another example, for a nominal bandwidth around 2GHz,

[0347] In another embodiment, the SCS supported by the nominal channel may be 480 kHz, and the corresponding number of available RBs (eg, excluding the guard band) may be For example, for a nominal bandwidth of around 2 GHz, if the maximum FFT size is 4096, then

[0348] In yet another embodiment, at least one of Mode 2 and / or Mode 3 may be supported as a multiplexing mode between SS / PBCH blocks and Type0-PDCCH within CORESET#0 in addition to Mode 1. For example, in addition to Mode 1, both Mode 2 and Mode 3 are supported.

[0349] In one embodiment, at least Mode 1 may be supported and configured as the multiplexing mode between SS / PBCH blocks and associated CORESET#0.

[0350] In one example, Mode 1 may be configured for all supported combinations of SS / PBCH blocks and SCS for CORESET#0.

[0351] In another embodiment, in terms of RBs and with respect to the SCS of Type0-PDCCH in CORESET#0, the BW of CORESET#0 (e.g., represented as ) can be configured to be no less than the minimum requirement from the rules for operation utilizing shared spectrum channel access.

[0352] For example, at least one configurable Quantized to integer multiples of 6, for example, Where ρ is the bandwidth occupancy required by the rule, and BW carrier is the nominal carrier bandwidth. For an example, for SCS CORESET =960kHz, BW carrier = 2GHz and ρ = 70%, at least one configurable For another example, for SCS CORESET =480kHz, BW carrier = 2GHz and ρ = 70%, at least one configurable

[0353] As another example, at least one configurable Quantized to integer multiples of 12, for example, Where ρ is the bandwidth occupancy required by the rule, and BW carrier is the nominal carrier bandwidth. For an example, for SCS CORESET =960kHz, BW carrier = 2GHz and ρ = 70%, at least one configurable For another example, for SCS CORESET =480kHz, BW carrier = 2GHz and ρ = 70%, at least one configurable

[0354] In another embodiment, in terms of RBs and with respect to the SCS of Type0-PDCCH in CORESET#0, the BW of CORESET#0 (e.g., represented as ) can be configured to be no greater than the maximum number of channelized RBs from all supported carriers overlapping with the nominal channel.

[0355] For an example, at least one configurable is quantized to integers that are multiples of 6. For example, for SCS CORESET =960kHz, For example, for SCS CORESET =960kHz, For another example, for SCS CORESET =480kHz, For example, for SCS CORESET =480kHz,

[0356] For another example, at least one configurable quantized to integers that are multiples of 12. For example, for SCS CORESET =960kHz, For example, for SCS CORESET =960kHz, For another example, for SCS CORESET =480kHz, For example, for SCS CORESET =480kHz,

[0357] In one example, for Mode 1, in terms of RBs and relative to the SCS of Type0-PDCCH within CORESET#0, the BW of CORESET#0 (e.g., represented as ) is fixed to the maximum number of channelized RBs from all supported carriers overlapping with the nominal channel. In one example, when the SCS of Type0-PDCCH in CORESET#0 is 960kHz and Mode 1 is configured, In another example, when the SCS of Type0-PDCCH in CORESET#0 is 480kHz and Mode 1 is configured, It is determined to be 270 (or 264) RBs.

[0358] In another example, for Mode 1, in terms of RBs and with respect to the SCS of Type0-PDCCH within CORESET#0, the BW of CORESET#0 (e.g., represented as ) is fixed as a minimum requirement from the rules for operation with shared spectrum channel access. In one example, when the SCS of Type0-PDCCH in CORESET#0 is 960kHz and Mode 1 is configured, In another example, when the SCS of Type0-PDCCH in CORESET#0 is 480kHz and Mode 1 is configured, It is determined to be 264 RBs.

[0359] In yet another example, for Mode 1, in terms of RBs and with respect to the SCS of Type0-PDCCH within CORESET#0, the BW of CORESET#0 (e.g., represented as ) may be at least configurable to be at least one integer between the maximum number of channelized RBs from all supported carriers overlapping with the nominal channel and the minimum requirement from the rules for operation utilizing shared spectrum channel access. In one example, It can be configured from a set of integers, where when the SCS of Type0-PDCCH in CORESET#0 is 960kHz and Mode 1 is configured, the integer is selected from 132 to 174 (or 168) RBs. In another example, Configurable from a set of integers, where when the SCS of Type0-PDCCH in CORESET#0 is 480kHz and mode 1 is configured, the integer is selected from 264 to 270 RB.

[0360] In yet another example, for Mode 1, in terms of RBs and with respect to the SCS of Type0-PDCCH within CORESET#0, the BW of CORESET#0 (e.g., represented as ) may be configurable to at least 12·n, where n is an integer such that 12·n is not greater than the maximum number of RBs per carrier. In one example, when the SCS of Type0-PDCCH in CORESET#0 is 960 kHz, Available from {24, 48, 96, BW max}, where BW max It can be an integer from 132 to 174 (e.g., 174 or 168 or 132). In another example, when both the SCS of the SS / PBCH block and the SCS of the Type0-PDCCH in CORESET#0 are 480 kHz, Available from {24, 48, 96, 192, BW max}, where BW max It can be an integer from 264 to 270 (e.g., 264 or 270). In another example, when the SCS of the SS / PBCH block is 960 kHz and the SCS of the Type0-PDCCH in CORESET#0 is 480 kHz, Available from {48, 96, 192, BW max}, where BW max Can be an integer from 264 to 270 (eg, 264 or 270).

[0361] Fig.10 An example CORESET#0BW 1000 of Mode 1 according to an embodiment of the present disclosure is shown. Fig.10 The embodiment of CORESET#0BW 1000 shown is for illustration only.

[0362] In another embodiment, an RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block may be associated with the supported CORESET#0BW.

[0363] In one example, for a given supported CORESET#0BW, the RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block can be fixed to 0 RB. In one instance, this example can be applicable to CORESET#0BW is not BW max situation.

[0364] In another example, for a given supported CORESET#0 BW, the RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block may be configurable. max , and the SCS of Type0-PDCCH in CORESET#0 is the same as the SCS of the SS / PBCH block, the RB offset can be configured from a set or subset of {0, 1, 2, 3}. In another example, if CORESET#0 BW is BW max , and the SCS of Type0-PDCCH in CORESET#0 is greater than the SCS of SS / PBCH block, the RB offset can be configured from a set or subset of {0, 2}. In another example, if CORESET#0 BW is BW max , and the SCS of Type0-PDCCH in CORESET#0 is less than the SCS of the SS / PBCH block, the RB offset can be configured from a set or subset of {0, 2, 4, 6}.

[0365] In yet another embodiment, for Mode 1, the number of symbols of CORESET#0 can be configured between 1 and 2. In an additional example, if the BW of CORESET#0 is 48 RB or less, the number of symbols of CORESET#0 can be further configured to 3. Table 12A shows {SCS SSB , SCS CORESET} = {960kHz, 960kHz}, and may support at least a subset of the table, where BW max It can be an integer from 132 to 174 (for example, 174 or 168 or 132).

[0366] Table 12A. {SCS SSB , SCS CORESET Example CORESET#0 configuration where}={960kHz, 960kHz}

[0367]

[0368] Table 12B shows {SCS SSB , SCS CORESET}={480kHz, 960kHz}, and may support at least a subset of the table, where BW max It can be an integer from 132 to 174 (for example, 174 or 168 or 132).

[0369] Table 12B. {SCS SSB , SCS CORESET Example CORESET#0 configuration where}={480kHz, 960kHz}

[0370]

[0371] Table 12C shows {SCS SSB , SCS CORESET} = {960kHz, 480kHz}, and may support at least a subset of the table, where BW max It can be 270 or 264.

[0372] Table 12C. {SCS SSB , SCS CORESET Example CORESET#0 configuration where}={960kHz, 480kHz}

[0373]

[0374] In one embodiment, at least for some of the combinations of SS / PBCH blocks and SCS of CORESET#0, Mode 2 may be supported and configured as the multiplexing mode between SS / PBCH blocks and CORESET#0.

[0375] In one example, mode 2 may be configured at least for the case where the SCS of the SS / PBCH block is different from the SCS of CORESET#0 (e.g., the SCS of the SS / PBCH block is twice the SCS of CORESET#0 (1101), or the SCS of the SS / PBCH block is half the SCS of CORESET#0 (1102)). Fig.11 An illustration of this example is shown in 1101 and 1102 .

[0376] Fig.11 An example mode 2 1100 is shown in accordance with an embodiment of the present disclosure. Fig.11 The illustrated embodiment of Mode 2 1100 is for illustration only.

[0377] In another example, at least for the case where the SCS of the SS / PBCH block is the same as the SCS of CORESET#0, Mode 2 may be configured. Fig.11 An illustration of this example is shown in 1103 .

[0378] In one embodiment, Fig.12 As shown, the BW of CORESET#0 (e.g., BW CORESET ) and the BW of SSB (e.g., BW SSB ) can satisfy BW CORESET +BW SSB +O 1 +O 2 +O 3 =BW CH , where BW CH is the channel BW, and if the SCS of CORESET#0 is 480kHz, it can be interpreted as Or if the SCS of CORESET#0 is 960kHz, it can be interpreted as O 1 is the offset between the SSB and the channel boundary according to the position of the sync grid. 2 is the offset between SSB and CORESET#0, if floating synchronization is supported (e.g., k SSB can be greater than 0), the offset can be at least 1 RB, and if the SCS of the SS / PBCH block is different from the SCS of CORESET#0, the offset can be at least one additional RB. 2 The value of k depends on SSB Can it be greater than 0? 3 is the offset between CORESET#0 and the channel boundary, and for one example, O 3 Can be set to 0 to achieve maximum CORESET#0 bandwidth.

[0379] In such an embodiment, Fig.12 As shown, the RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block can be determined as −(BW SSB +O 2 ), where BW SSB and O 2The values ​​are all relative to the SCS of CORESET#0.

[0380] Fig.12 An example CORESET#0BW 1200 of Mode 2 or Mode 3 according to an embodiment of the present disclosure is shown. Fig.12 The embodiment of CORESET #0 BW 1200 shown is for illustration only.

[0381] In one example, for a SSB , SCS CORESET} = {960kHz, 960kHz} Mode 2, O 1 =0, and O 3 =0. For one example, the RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block may be determined as -20. For another example, if k SSB >0, the RB offset from the minimum RB index of the CORESET of the Type0-CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block can be determined as -25, and if k SSB =0, it is determined to be -26.

[0382] In another example, for a SSB , SCS CORESET} = {960kHz, 960kHz} Mode 2, O 3 > 0. For an example, if k SSB >0, the RB offset from the minimum RB index of the CORESET of the Type0-CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block may be determined as -21, and if k SSB =0, it is determined to be -20. For another example, the RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapped with the first RB of the SS / PBCH block may be determined to be -21.

[0383] In yet another example, for a system having {SCS SSB , SCS CORESET}, = {480kHz, 960kHz} mode 2, O 3 > 0. For an example, if k SSB>0, the RB offset from the minimum RB index of the CORESET of the Type0-CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block can be determined as -12, and if k SSB =0, it is determined to be -11. For another example, the RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapped with the first RB of the SS / PBCH block may be determined to be -12.

[0384] In yet another example, for a system having {SCS SSB , SCS CORESET} = {960kHz, 480kHz} Mode 2, O 3 > 0. For an example, if k SSB >0, the RB offset from the minimum RB index of the CORESET of the Type0-CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block can be determined as -42, and if k SSB =0, it is determined to be -41. For another example, the RB offset from the minimum RB index of the CORESET of the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapped with the first RB of the SS / PBCH block may be determined to be -42.

[0385] In another embodiment, the number of symbols of CORESET#0 may depend on the relationship between the SCS of CORESET#0 and the SCS of the SS / PBCH block.

[0386] In one example, if the SCS of the SS / PBCH block is twice the SCS of CORESET#0 (e.g. Fig.11 1101 in ), then for mode 2, the number of symbols of CORESET#0 can be determined to be 1 (for example, the number of symbols of PDSCH of RMSI is retained to 2).

[0387] In another example, if the SCS of the SS / PBCH block is half of the SCS of CORESET#0 (e.g. Fig.11 1102 in ), then for mode 2, the number of symbols of CORESET#0 can be configured between 1 and 2 (for example, the number of symbols of PDSCH for RMSI is kept at 4).

[0388] In yet another example, if the SCS of the SS / PBCH block is the same as the SCS of CORESET#0 (e.g., Fig.111103 in ), then for mode 2, the number of symbols of CORESET#0 can be configured between 1 and 2 (for example, keeping the number of symbols of PDSCH of RMSI at 4 or 7).

[0389] Table 13A shows the SSB , SCS CORESET} = {960kHz, 960kHz}, and may support at least a subset of the table, where BW max It can be 150 or 144.

[0390] Table 13A. {SCS SSB , SCS CORESET Example CORESET#0 configuration where}={960kHz, 960kHz}

[0391]

[0392] Table 13B shows the SSB , SCS CORESET}={480kHz, 960kHz}, and may support at least a subset of the table, where BW max It can be 162 or 156.

[0393] Table 13B. {SCS SSB , SCS CORESET Example CORESET#0 configuration where}={480kHz, 960kHz}

[0394]

[0395] Table 13C shows the SSB , SCS CORESET}={960kHz, 480kHz}, and may support at least a subset of the table, where BW max It can be 264 or 270.

[0396] Table 13C. SSSB , SCS CORESET Example CORESET#0 configuration where}={960kHz, 480kHz}

[0397]

[0398] Table 13D shows the SSB , SCS CORESET}={480kHz, 480kHz}, and may support at least a subset of the table, where BW max It can be 264 or 270.

[0399] Table 13D.{SCS SSB , SCS CORESET Example CORESET#0 configuration where}={960kHz, 480kHz}

[0400]

[0401] In one embodiment, at least for some of the combinations of SS / PBCH blocks and SCS of CORESET#0, Mode 3 may be supported and configured as the multiplexing mode between SS / PBCH blocks and CORESET#0.

[0402] In one example, at least for the case where the SCS of the SS / PBCH block is different from the SCS of CORESET#0 (e.g., the SCS of the SS / PBCH block is half of the SCS of CORESET#0), Mode 3 may be configured. Fig.13 An illustration of this example is shown in 1301 .

[0403] Fig.13 An example schema 31300 is shown in accordance with an embodiment of the present disclosure. Fig.13 The embodiment of mode 31300 shown is for illustration only.

[0404] In another example, at least for the case where the SCS of the SS / PBCH block is the same as the SCS of CORESET#0, Mode 3 may be configured. Fig.13 An illustration of this example is shown in 1302 .

[0405] In one embodiment, the BW of CORESET#0 (e.g., BW CORESET ) can be determined similarly to Mode 2 in the present disclosure, for example, BW CORESET +BW SSB +O 1 +O 2 +O 3 =BW CH , and the RB offset from the minimum RB index of the CORESET of the Type0-CSS set to the minimum RB index of the common RB overlapping the first RB of the SS / PBCH block can be determined as -(BW SSB +O 2 ), where BW SSB and O 2 The values ​​are all relative to the SCS of CORESET#0. Fig.12 An example is shown.

[0406] Table 14A shows the SSB , SCS CORESET}={960kHz, 960kHz}, and may support at least a subset of the table, where BW max It can be 150 or 144.

[0407] Table 14A. {SCS SSB , SCS CORESET Example CORESET#0 configuration where}={960kHz, 960kHz}

[0408]

[0409] Table 14B shows the SSB , SCS CORESET}={480kHz, 960kHz}, and may support at least a subset of the table, where BW max It can be 162 or 156.

[0410] Table 14B. {SCS SSB , SCS CORESET Example CORESET#0 configuration where}={480kHz, 960kHz}

[0411]

[0412] Table 14C shows the SSB , SCS CORESET}={960kHz, 480kHz}, and may support at least a subset of the table, where BW max It can be 264 or 270.

[0413] Table 14C. Example CORESET#0 Configuration or {SCS SSB , SCS CORESET}={960kHz,480kHz}

[0414]

[0415] Table 14D shows the SSB , SCS CORESET}={480kHz, 480kHz}, and may support at least a subset of the table, where BW max It can be 264 or 270.

[0416] Table 14D. {SCS SSB , SCS CORESET Example CORESET#0 configuration where}={480kHz, 480kHz}

[0417]

[0418] The present disclosure focuses on initial access in a carrier aggregation scenario. In particular, embodiments of the present disclosure are at least applicable to operations utilizing shared spectrum channel access. The present disclosure includes carrier channelization, common resource grid, synchronization grid design, and cross-carrier CORESET#0 design.

[0419] For the new carrier frequency range between 52.6 GHz and 71 GHz, it is necessary to support a large operating bandwidth, such as at least 2.16 GHz, to coexist with Wi-Fi operating on the same carrier frequency range. In one example, the large bandwidth can be achieved by carrier aggregation from multiple carriers with smaller carrier bandwidths (e.g., 400 MHz). The present disclosure details an example design of an initial access procedure using carrier aggregation. Fig.14 A diagram showing the use of carrier aggregation to achieve large operating bandwidth.

[0420] Fig.14 An example carrier aggregation 1400 that implements large bandwidth according to an embodiment of the present disclosure is shown. Fig.14 The illustrated embodiment of carrier aggregation 1400 is for illustration only.

[0421] In the present disclosure, CORESET#0 refers to a control resource set (CORESET) of a Type0-PDCCH common search space set.

[0422] In one embodiment, a wideband (eg, having a bandwidth of 2.16 GHz or higher) may operate using carrier aggregation from a set of narrow carriers (eg, each narrow carrier having a bandwidth of less than 2.16 GHz).

[0423] In one example, the narrow carrier set may include at least one example from Table 15, and the illustration of the example is in Fig.15 In one example, a narrow carrier with a given bandwidth is associated with a minimum subcarrier spacing. For one example, a 400 MHz bandwidth is associated with a minimum subcarrier spacing of 120 kHz; for another example, an 800 MHz bandwidth is associated with a minimum subcarrier spacing of 240 kHz; for yet another example, 1200 MHz or 1600 kHz is associated with a minimum subcarrier spacing of 480 kHz.

[0424] Fig.15An example set 1500 of narrow carriers using carrier aggregation to construct a wideband according to an embodiment of the present disclosure is shown. Fig.15 The illustrated embodiment of set 1500 of narrow carriers is for illustration only.

[0425] Table 15. Example of using carrier aggregation to build a narrow set of carriers for broadband.

[0426] Example# Bandwidth of narrow carrier set (MHz) 1 {400，400，400，400，400} 2 {800，400，400，400} 3 {400，800，400，400} 4 {400，400，800，400} 5 {400，400，400，800} 6 {800，800，400} 7 {800，400，800} 8 {400，800，800} 9 {1200，800} 10 {800，1200} 11 {400，1600} 12 {1600，400}

[0427] In one example, for the target broadband, the narrow carrier set using carrier aggregation to construct the broadband can utilize fixed channelization in the sense that the center of the narrow carrier is fixed. For example, in the example of Table 15, each of the narrow carriers constituting the broadband has a specified fixed carrier center.

[0428] In one example, fixed channelization is applicable to operations utilizing shared spectrum channel access.

[0429] In another embodiment, for a target broadband, a set of narrow carriers that use carrier aggregation to construct the broadband is configurable, and the locations of the narrow carriers are indicated to the UE.

[0430] In one example, fixed channelization is applicable for operations that do not utilize shared spectrum channel access.

[0431] In one example, the narrow carrier set is using the same subcarrier spacing and the same common resource grid. For example, the common resource grid of the narrow carrier set is determined from the same point A.

[0432] In one example, in terms of the SCS of the common resource grid, the guard band of the narrow carrier set is an integer number of RBs. For example, if the channelization of the narrow carrier set is fixed, the guard band of the narrow carrier set is also a fixed integer number of RBs. For another example, if the channelization of the narrow carrier set is configured, the guard band of the narrow carrier set can also be configured as an integer number of RBs.

[0433] In one example, for operation with shared spectrum channel access, each carrier of the narrowband set has a single synchronization grid point.

[0434] In one example, a single synchronization grid point corresponds to a Global Synchronization Channel Number (GSCN).

[0435] In another example, for operation not utilizing shared spectrum channel access, each carrier of the narrowband set has at least one synchronization grid point.

[0436] In one example, at least one synchronization grid point corresponds to GSCN(s).

[0437] In one example, the set of synchronization grid points for operations utilizing shared spectrum channel access (eg, unlicensed operation) is a subset of the set of synchronization grid points for operations not utilizing shared spectrum channel access (eg, licensed operation).

[0438] Fig.16 An illustration of this example is shown in (e.g., as shown in (a)). For this example, the total number of synchronization grid points for the wideband can be less, and the UE does not need to rely on the location of the synchronization grid points to distinguish between licensed or unlicensed operation. If the UE detects an SS / PBCH block located on a synchronization grid point for both licensed and unlicensed operation, the UE can distinguish whether the SS / PBCH block has licensed operation or unlicensed operation based on other indications.

[0439] Fig.16 An example synchronization grid design 1600 for unlicensed and licensed operations is shown according to an embodiment of the present disclosure. Fig.16 The illustrated embodiment of synchronization grid design 1600 is for illustration only.

[0440] In another example, a synchronization grid point set for operations utilizing shared spectrum channel access (e.g., unlicensed operations) does not overlap with a synchronization grid point set for operations not utilizing shared spectrum channel access (e.g., licensed operations). The GSCN value corresponding to the synchronization grid point set for operations utilizing shared spectrum channel access is different from the GSCN value corresponding to the synchronization grid point set for operations not utilizing shared spectrum channel access.

[0441] Fig.16 An illustration of this example is shown in (eg, as shown in (b)). For this example, the UE may distinguish whether the detected SS / PBCH has licensed operation or unlicensed operation based on the synchronization grid value.

[0442] In one example, when a narrow carrier set uses carrier aggregation to construct a wideband, and an SS / PBCH block is detected in one narrow carrier in the narrow carrier set, the associated CORESET#0 of the SS / PBCH block may be configured to be located in another narrow carrier in the narrow carrier set. For example, in the configuration set of CORESET#0 of the MIB, at least one configuration corresponds to a cross-carrier CORESET#0.

[0443] In one example, the initial DL BWP is not located in the same carrier as the detected SSB, where the BW of the initial DL BWP is the same as the BW of CORESET#0.

[0444] In another example, cross-carrier CORESET#0 is applicable only to the multiplexing mode of CORESET#0 and SS / PBCH blocks as Mode 2 or Mode 3.

[0445] In yet another example, an offset from the minimum RB index of a CORESET (e.g., CORESET#0) of a Type0-PDCCH CSS set to the minimum RB index of a common RB overlapping the first RB of the detected SS / PBCH block may be indicated by the MIB of the detected SS / PBCH block. Fig.17A and Fig. 17B A diagram of this example is shown.

[0446] Fig.17A An example cross-carrier indication 1700 of CORESET#0 is shown according to an embodiment of the present disclosure. Fig.17A The embodiment of the cross-carrier indication 1700 shown in FIG. 1 is for illustration only.

[0447] Fig. 17B Another example cross-carrier indication 1750 of CORESET #0 is shown according to an embodiment of the present disclosure. Fig. 17B The illustrated embodiment of the cross-carrier indication 1750 is for illustration only.

[0448] In one example, if the narrow carrier set has the same common resource grid, the value k SSB From the public resource block The subcarrier offset from subcarrier 0 in the resource block to subcarrier 0 of the SS / PBCH block, where resource block The center of subcarrier 0 of the resource block coincides with the center of subcarrier 0 of the common resource block.

[0449] In another example, if there is no requirement for alignment of the common resource grid, the value k SSB From the public resource block The subcarrier offset from subcarrier 0 in the resource block to subcarrier 0 of the SS / PBCH block, where resource block The center of subcarrier 0 of coincides with the center of subcarrier 0 of the common resource block containing the carrier of CORESET#0.

[0450] In one example, if Fig.17A As shown, CORESET#0 is located in a carrier having a higher frequency than the carrier containing the detected SS / PBCH block. The carriers are represented in a range from 1 to n (e.g., Fig.17AIf the detected SS / PBCH block is located in a carrier with an index of n=3) from a lower to a higher frequency, and the detected SS / PBCH block is located in a carrier with an index of 1, and CORESET#0 is located in a carrier with an index of n (e.g., n>1), then the frequency offset from the minimum RB index of CORESET#0 to the minimum RB index of the common RB overlapping with the first RB of the detected SS / PBCH block can be given by Equation 1.

[0451]

[0452] In equation 1, is the bandwidth of the carrier with index i in RBs relative to the SCS of CORESET#0, is the bandwidth of the guard bandwidth between adjacent carriers with index i and i+1 in RB units relative to the SCS of CORESET#0, Δ CORESET#O is the offset from the minimum RB index of CORESET#0 to the minimum RB index of the carrier containing CORESET#0 (e.g., the carrier with index n), and Δ SSB is the offset from the smallest RB index of the common RBs overlapping the first RB of the detected SS / PBCH block to the smallest RB index of the carrier containing the SS / PBCH block (eg, the carrier with index 1).

[0453] In another example, Fig. 17B As shown, CORESET#0 is located in a carrier having a lower frequency than the carrier containing the detected SS / PBCH block. The carriers are represented in a range from 1 to n (e.g., Fig. 17B If the detected SS / PBCH block is located in a carrier with an index of n (e.g., n>1) and CORESET#0 is located in a carrier with an index of 1, then the frequency offset from the minimum RB index of CORESET#0 to the minimum RB index of the common RB overlapping with the first RB of the detected SS / PBCH block can be given by Equation 2.

[0454]

[0455] In equation 2, is the bandwidth of the carrier with index i in RBs relative to the SCS of CORESET#0, is the bandwidth of the guard bandwidth between adjacent carriers with index i and i+1 in RB units relative to the SCS of CORESET#0, Δ CORESET#0 is the offset from the minimum RB index of CORESET#0 to the minimum RB index of the carrier containing CORESET#0 (e.g., the carrier with index 1), and ΔSSB is the offset from the smallest RB index of the common RBs overlapping the first RB of the detected SS / PBCH block to the smallest RB index of the carrier containing the SS / PBCH block (eg, the carrier with index n).

[0456] In one example, ΔSSB may be determined to be zero.

[0457] In one example, Δ CORESET#0 can be determined to be 0.

[0458] In one example, when the channelization of the narrow carrier set is fixed and the location of CORESET#0 within the carrier is also fixed (eg, Δ CORESET#0 is fixed and known to the UE), the UE can derive the offset Δ according to Equation 1 or Equation 2 SSB-CORESET#0 , and no explicit indication of the offset value is required.

[0459] In another example, when the channelization of the narrow carrier set is fixed, the index of the carrier of CORESET#0 may be provided to the UE, and the UE may derive the offset Δ according to Equation 1 or Equation 2. SSB-CORESET#0 , and no explicit indication of the offset value is required. For a sub-example, Equation 1 or Equation 2 can be simplified to Equation 3, where Δ 1 is the number of RBs of the carrier with the smallest bandwidth and the guard band in the narrow carrier set (e.g., ), Δ 2 =Δ CORESET#0 -Δ SSB , and the index k is provided by the gNB and indicated to the UE (e.g., via the PBCH payload). k can be positive or negative, corresponding to Equation 1 or Equation 2, respectively.

[0460] Δ SSB-CORESET#0 = k·Δ 1 +Δ 2 .....Equation 3

[0461] In yet another example, the UE is explicitly configured with an offset value by the MIB, where the offset value may be jointly encoded with other parameters of CORESET#0 (e.g., multiplexing mode of SS / PBCH blocks, number of symbols of CORESET#0, and / or bandwidth of CORESET#0). For example, at least one example in Table 16, Δ 1 is the number of RBs of the carrier with the smallest bandwidth and the guard band in the narrow carrier set (e.g., ) and Δ 2 =Δ CORESET#0 -Δ SSB .

[0462] Table 16. Example of cross-carrier CORESET#0 configuration provided by MIB.

[0463]

[0464] In yet another example, the UE is configured with an offset provided by the MIB of the detected SS / PBCH block, and the UE is also provided with information of the carrier containing CORESET#0 (e.g., through the PBCH payload), then the UE can derive the frequency offset from the minimum RB index of CORESET#0 to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block by its own calculation based on the indicated offset from the MIB and the information of the carrier containing CORESET#0 (without requiring an explicit indication of the offset value). In this example, Equation 4 can be used as a simplification of Equation 1 or Equation 2, where Δ 3 is the offset provided by the MIB, Δ 1 is the number of RBs of the carrier with the smallest bandwidth and the guard band in the narrow carrier set (e.g., ), and k is the carrier index difference. k can be positive or negative, corresponding to equation 1 or equation 2, respectively.

[0465] Δ SSB-CORESET#0 = k·Δ 1 +Δ 3 .....Equation 4

[0466] In one example, when the SCS of type0-PDCCH in CORESET#0 is 120 kHz, Δ 1 =284, when the SCS of type0-PDCCH in CORESET#0 is 240kHz, Δ 1 =142, when the SCS of type0-PDCCH in CORESET#0 is 480kHz, Δ 1 =71 or 72.

[0467] In another example of the above example, Δ 2 =0.

[0468] In yet another example, if the SCS of the SS / PBCH block is the same as the SCS of the type0-PDCCH in CORESET#0, then Δ 2 =0, and Δ 2 =-10 SCS SSB / SCS CORESET#0 , where SCS SSB is the SCS of the SS / PBCH block, and the SCS CORESET#0It is the SCS of the SCS of type0-PDCCH in CORESET#0.

[0469] In yet another example, k is directly indicated (eg, by the PBCH payload) as a value from k∈{-3, -2, -1, 0, 1, 2, 3}.

[0470] In another example of the above example, the index of the carrier containing CORESET#0 is provided to the UE, and the carrier index difference between the carrier containing CORESET#0 and the carrier containing the detected SS / PBCH block is determined, for example, to determine the value of k such that k∈{-3,-2,-1,0,1,2,3}.

[0471] Fig.18 A flowchart of a method 1800 for determining PBCH content according to an embodiment of the present disclosure is shown, which method may be performed by a UE (eg, Figure 1 111-116) shown in FIG. 111-116) shown in FIG. 111-116) shown in FIG. Figure 1 BS 102 in performs the corresponding supplementary process. Fig.18 The illustrated embodiment of method 1800 is for illustration only. Fig.18 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described.

[0472] The method begins with the UE receiving a SS / PBCH block (step 1802). For example, in step 1802, the UE SS / PBCH block may be received from the BS. The UE then decodes the content of the PBCH in the SS / PBCH block (step 1804).

[0473] Thereafter, the UE determines whether the wireless communication system is operating with shared spectrum channel access (step 1806). For example, in step 1806, the UE determines whether the wireless communication system is operating with shared spectrum channel access based on the content of the decoded PBCH. In one example, if the QCL parameter in the content of the PBCH is is determined as a value, the wireless communication system is determined to operate using shared spectrum channel access. In another example, if the QCL parameter in the content of the PBCH is If a non-numeric value is determined, the wireless communication system is determined not to operate using shared spectrum channel access.

[0474] If the UE determines that the wireless communication system operates using shared spectrum channel access, the UE determines the content of the PBCH in a first manner (step 1808). For example, in step 1808, for the first manner of determining the content of the PBCH, the UE sets the bits in the content of the PBCH to Determined as the seventh LSB of the candidate SS / PBCH block index. In another example, for the first way to determine the content of the PBCH, the UE determines the first field in the MIB in the content of the PBCH as the fourth LSB of the SFN. In another example, for the first way to determine the content of the PBCH, the UE determines the second field in the MIB in the content of the PBCH as the configuration of the CORESET for monitoring Type0-PDCCH. In one example, the configuration of the CORESET includes a multiplexing mode between the CORESET and the SS / PBCH block, and the multiplexing mode is one of a first mode, a second mode, or a third mode for a combination of the SCS of the CORESET and the SCS of the SS / PBCH block. In another example, wherein the configuration of the CORESET includes a frequency offset from a first resource block of the CORESET to a first resource block of the SS / PBCH block.

[0475] However, if the UE determines that the wireless communication system does not operate using shared spectrum channel access, the UE determines the content of the PBCH in a second manner (step 1810). For example, in step 1810, the UE may determine the content of the PBCH differently from the first manner described above.

[0476] The above flow charts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods shown in the flow charts herein. For example, although shown as a series of steps, the individual steps in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0477] Although the disclosure has been described with exemplary embodiments, various changes and modifications may be conceived by those skilled in the art. The disclosure is intended to include these changes and modifications that fall within the scope of the appended claims. Any description in this application should not be construed as implying that any particular element, step or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A method for receiving a synchronization signal and a physical broadcast channel SS / PBCH block by a user equipment UE (111, 112, 113, 114, 115, 116) in a wireless communication system supporting a frequency range between 52.6 GHz and 71 GHz, the method comprising: Receive SS / PBCH blocks; as well as identifying parameters for quasi co-sited QCL based on the SS / PBCH block, Among them, in ( mod ) is the same among the SS / PBCH blocks, the SS / PBCH blocks are quasi-co-located QCLed within or across transmission windows, wherein, is the candidate SS / PBCH block index and is a parameter used for QCL.

2. The method according to claim 1, wherein: The SS / PBCH block includes at least one PBCH, and Wherein, for operations utilizing shared spectrum channel access and operations not utilizing shared spectrum channel access, a portion of information in the at least one PBCH is interpreted differently by the UE.

3. The method according to claim 2, wherein: The portion of the information in the at least one PBCH includes at least a portion of subCarrierSpacingCommon.

4. The method according to claim 2, wherein: The global synchronization channel number GSCN value is different for operations using shared spectrum channel access and operations not using shared spectrum channel access.

5. A method for sending synchronization signals and physical broadcast channel SS / PBCH blocks by a base station BS (101, 102, 103) in a wireless communication system supporting a frequency range between 52.6 GHz and 71 GHz, the method comprising: Configuring parameters for quasi-co-located QCL; and Sending a SS / PBCH block including parameters for QCL; Among them, in ( mod ) is the same among the SS / PBCH blocks, the SS / PBCH blocks are quasi-co-located QCLed within or across transmission windows, wherein, is the candidate SS / PBCH block index and is a parameter used for QCL.

6. The method according to claim 5, wherein: The SS / PBCH block includes at least one PBCH, and Wherein, for operations utilizing shared spectrum channel access and operations not utilizing shared spectrum channel access, a portion of the information in the at least one PBCH is interpreted differently by the UE.

7. The method according to claim 6, wherein: The portion of the information in the at least one PBCH includes at least a portion of subCarrierSpacingCommon.

8. The method according to claim 6, wherein: The global synchronization channel number GSCN value is different for operations using shared spectrum channel access and operations not using shared spectrum channel access.

9. A user equipment UE (111, 112, 113, 114, 115, 116) in a wireless communication system supporting a frequency range between 52.6 GHz and 71 GHz, the UE comprising: a transceiver (310); and A processor (340) operably connected to the transceiver, wherein the processor is configured to: receiving, via the transceiver, a synchronization signal and a physical broadcast channel SS / PBCH block; and identifying parameters for quasi co-located QCL based on the SS / PBCH block; Among them, in ( mod ) is the same among the SS / PBCH blocks, the SS / PBCH blocks are quasi-co-located QCLed within or across transmission windows, wherein, is the candidate SS / PBCH block index and is a parameter used for QCL.

10. The UE according to claim 9, wherein: The SS / PBCH block includes at least one PBCH, and Wherein, for operations utilizing shared spectrum channel access and operations not utilizing shared spectrum channel access, a portion of information in the at least one PBCH is interpreted differently by the UE.

11. The UE according to claim 10, wherein: The portion of the information in the at least one PBCH includes at least a portion of subCarrierSpacingCommon.

12. The UE according to claim 10, wherein: The global synchronization channel number GSCN value is different for operations using shared spectrum channel access and operations not using shared spectrum channel access.

13. A base station BS (101, 102, 103) in a wireless communication system supporting a frequency range between 52.6 GHz and 71 GHz, the BS comprising: Transceivers (210a, 210b, 210n); and A processor (225) operably connected to the transceiver, wherein the processor is configured to: configuring parameters for the quasi-co-located QCL; and Sending a synchronization signal including parameters for QCL and a physical broadcast channel SS / PBCH block, wherein ( mod ) is the same among the SS / PBCH blocks, the SS / PBCH blocks are quasi-co-located QCLed within or across transmission windows, wherein, is the candidate SS / PBCH block index and is a parameter used for QCL.

14. The BS according to claim 13, wherein: The SS / PBCH block includes at least one PBCH, and Wherein, for operations utilizing shared spectrum channel access and operations not utilizing shared spectrum channel access, a portion of the information in the at least one PBCH is interpreted differently by the UE.

15. The BS according to claim 14, wherein: The global synchronization channel number GSCN value is different for operations using shared spectrum channel access and operations not using shared spectrum channel access.

Images