Method and apparatus for SS / PBCH block frequency location indication

Abstract

To provide a method and an apparatus for a synchronization signal and physical broadcast channel (SS / PBCH) block frequency location indication.SOLUTION: A base station BS: generates an SS / PBCH block 1202; identifies a first frequency location (GSCN-Current) based on a predefined synchronization raster set determined by a Global Synchronization Channel Number (GSCN) 1204; determines a configuration associated or un-associated with a Physical Downlink Control Channel (PDCCH) 1206; when un-associated, determines a configuration that includes a frequency range determined based on the GSCN, or at least one of second frequency locations, as a frequency range where no other SS / PBCH blocks are transmitted 1208; based on the determined configuration, identifies PBCH content 1210; and transmits the SS / PBCH block to user equipment UE via a downlink channel 1212.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] This application relates generally to signal indication. More specifically, this disclosure relates to SS / PBCH block frequency location indication in advanced wireless communication systems. [Background technology]

[0002] 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 known as 'Beyond 4G Networks' or 'Post LTE'. 5G communication systems are implemented in high-frequency (mmWave) bands, such as the 60 GHz band, and are considered to achieve higher data rates. To reduce radio wave loss and increase transmission distances, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna techniques are being discussed in 5G communication systems. Furthermore, in the 5G communication system, development is underway to improve the system network based on advanced small cells, cloud Radio Access Network (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, moving networks, cooperative communications, Coordinated Multi-Point (CoMP), and reception-end interference cancellation.In 5G systems, hybrid FQAM (FSK and QAM modulation) has been developed as an advanced coding modulation (ACM), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) have been developed as advanced access technologies.

[0003] The Internet, a human-centered network where humans generate and consume information, is evolving into the Internet of Things (IoT), where distributed entities like things exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, combining IoT technology with big data processing technology through connections to cloud servers. Technological elements required for the realization of IoT, such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, have led to recent research into sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC). This IoT environment can provide intelligent Internet technology services that create new value in human life by collecting and analyzing data generated by connected things.Through the convergence and combination of 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] As a result, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC (Machine Type Communication), and M2M (Machine-to-Machine) communication can be implemented using beamforming, MIMO, and array antennas. The application of Cloud Radio Access Network (RAN) as a big data processing technology mentioned above can also be seen as an example of the integration of 5G and IoT technologies.

[0005] In the case of new radio (NR) licensed spectrum, each synchronization and physical broadcasting channel (PBCH) signal block (SS / PBCH block) includes one symbol for the NR-primary synchronization signal (NR-PSS), two symbols for the NR-PBCH, and one symbol for the NR-secondary synchronization signal (NR-SSS) and NR-PBCH, where the four symbols are contiguously mapped and time-division multiplexed. NR-SS is a unified design that includes NR-PSS and NR-SSS sequence designs for all carrier frequency ranges supported by NR. The transmission bandwidth of the NR-PSS and NR-SSS is smaller than the transmission bandwidth of the entire SS / PBCH block. For initial cell selection for NR cells, the UE assumes a default SS burst set periodicity of 20 ms. To detect non-independent NR cells, the network provides the UE with one SS burst set periodicity per frequency carrier to provide information for deriving measurement timing / duration. Besides the master information block (MIB), the remaining minimum system information (RMSI) is carried by the physical downlink shared channel (PDSCH) with scheduling information carried by the corresponding physical downlink control channel (PDCCH). A control resource set (CORESET) for receiving the common control channel needs to be configured and can be transmitted on the PBCH. Summary of the Invention [Problem to be solved by the invention]

[0006] Embodiments of the present disclosure provide SS / PBCH block frequency location indication in an advanced wireless communication system. [Means for solving the problem]

[0007] In one embodiment, a base station (BS) in a wireless communication system is provided, wherein the BS generates a synchronization signal and physical broadcast channel (SS / PBCH) block, identifies a first frequency location (GSCN-Current) based on a set of predefined synchronization rasters determined by a global synchronization channel number (GSCN) to transmit the SS / PBCH block, and calculates a remaining minimum system activity (RMSI) on the GSCN-Current based on the GSCN-Current. The BS further includes a processor configured to determine a configuration for at least one of an SS / PBCH block associated with a physical downlink control channel (PDCCH) including scheduling information for RMSI on the GSCN-Current, or an SS / PBCH block not associated with a PDCCH including scheduling information for RMSI on the GSCN-Current, and when the SS / PBCH block is not associated with a PDCCH including scheduling information for RMSI on the GSCN-Current, determine a configuration including at least one of a frequency range determined based on the GSCN in which another SS / PBCH block configured with a PDCCH including scheduling information for RMSI is not transmitted, or a second frequency location determined based on the GSCN in which another SS / PBCH block configured with a PDCCH including scheduling information for RMSI is transmitted, and identify content of the PBCH included in the SS / PBCH block based on the determined configuration. The BS further includes a transceiver operably connected to the processor, the transceiver configured to transmit the SS / PBCH block including the PBCH using the GSCN-Current to a user equipment (UE) via a downlink channel.

[0008] In another embodiment, a user equipment (UE) in a wireless communication system is provided, the UE including a transceiver configured to receive a synchronization signal and a physical broadcast channel (SS / PBCH) block including a PBCH using a first frequency location (GSCN-Current), where the GSCN-Current is based on a set of predefined synchronization rasters determined by a global synchronization channel number (GSCN), from a base station (BS) over a downlink channel. The UE further includes a processor operably connected to the transceiver, wherein the processor is configured to decode the PBCH included in the SS / PBCH block, identify content of the decoded PBCH, and determine a configuration for at least one of an SS / PBCH block associated with a physical downlink control channel (PDCCH) including scheduling information for RMSI (remaining minimum system information) on the GSCN-Current or an SS / PBCH block not associated with a PDCCH including scheduling information for the RMSI on the GSCN-Current, and when the SS / PBCH block is not associated with a PDCCH including scheduling information for the RMSI on the GSCN-Current, determine a configuration including at least one of a frequency range determined based on the GSCN in which other SS / PBCH blocks for which PDCCHs including scheduling information for the RMSI are not transmitted, or a second frequency location (the GSCN-Current is determined based on the GSCN) in which other SS / PBCH blocks for which PDCCHs including scheduling information for the RMSI are transmitted.

[0009] In yet another embodiment, a method for a user equipment (UE) in a wireless communication system is provided, the method including the steps of receiving a synchronization signal and a physical broadcast channel (SS / PBCH) block including a PBCH using a first frequency location (GSCN-Current) over a downlink channel from a base station (BS), the GSCN-Current being based on a set of predefined synchronization rasters determined by a global synchronization channel number (GSCN), decoding the PBCH included in the received SS / PBCH block, identifying the content of the decoded PBCH, and determining a remaining minimum system activity (RMSI) on the GSCN-Current. determining a configuration for at least one of an SS / PBCH block associated with a physical downlink control channel (PDCCH) including scheduling information for RMSI on the GSCN-Current, or an SS / PBCH block not associated with a PDCCH including scheduling information for RMSI on the GSCN-Current; and when the SS / PBCH block is not associated with a PDCCH including scheduling information for RMSI on the GSCN-Current, determining a configuration including at least one of a frequency range determined based on the GSCN in which other SS / PBCH blocks for which PDCCHs including scheduling information for RMSI are not transmitted, or a second frequency position (the GSCN-Current is determined based on the GSCN) in which other SS / PBCH blocks for which PDCCHs including scheduling information for RMSI are transmitted.

[0010] Other technical features will be readily apparent to one of ordinary skill in the art from the following drawings, description and claims.

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

[0012] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof, adapted for implementation in appropriate 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 read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transient, electrical, or other signals. Non-transitory computer-readable media include media on which data can be permanently stored, and media on which data can be stored and later overwritten, such as re-recordable optical disks or erasable memory devices.

[0013] Definitions for other specific words and phrases are provided throughout this patent document, and one of ordinary skill in the art should understand that in most cases, such definitions apply to previous and subsequent uses of such defined words and phrases. [Effects of the Invention]

[0014] Embodiments of the present disclosure provide SS / PBCH block frequency location indication in an advanced wireless communication system. [Brief explanation of the drawings]

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

[0016] [Figure 1] 1 illustrates an exemplary wireless network according to an embodiment of the present disclosure. [Figure 2] 1 illustrates an exemplary eNB according to an embodiment of the present disclosure. [Figure 3] 1 illustrates an exemplary UE according to an embodiment of the present disclosure. [Figure 4A] 1 illustrates a high-level diagram of an orthogonal frequency division multiple access transmission path according to an embodiment of the present disclosure. [Figure 4B] 1 illustrates a high-level diagram of an orthogonal frequency division multiple access receive path according to an embodiment of the present disclosure. [Figure 5] 1 illustrates a transmitter block diagram for PDSCH in a subframe according to an embodiment of the present disclosure. [Figure 6] 1 illustrates a receiver block diagram for PDSCH in a subframe according to an embodiment of the present disclosure. [Figure 7] 1 illustrates a transmitter block diagram for a PUSCH in a subframe according to an embodiment of the present disclosure. [Figure 8] 1 illustrates a receiver block diagram for PUSCH in a subframe according to an embodiment of the present disclosure. [Figure 9] 1 illustrates exemplary time-domain locations for PSS / SSS mapping for FDD and TDD according to an embodiment of the present disclosure. [Figure 10] 1 illustrates an example SS / PBCH block multiplexed with a CORESET of RMSI according to an embodiment of the present disclosure. [Figure 11]1 illustrates a flowchart of a method for a UE according to an embodiment of the present disclosure. [Figure 12] 1 shows a flowchart of a method for a BS according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0017] 1 through 12 discussed below, and various embodiments used in this patent document to explain the principles of the present disclosure, are for illustrative purposes only and should not be construed as limiting the scope of the present disclosure in any way. Those of ordinary skill in the art will appreciate that the principles of the present disclosure can be embodied in any suitably arranged system or device.

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

[0019] To meet the increased demand for wireless data traffic since the deployment of the 4G communication system, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called 'Beyond 4G Networks' or 'Post LTE Systems'.

[0020] The 5G communication system will be implemented in the higher frequency (mmWave) band, i.e., the 60 GHz band, and is expected to achieve higher data rates. To reduce radio wave loss and increase transmission coverage, beamforming, massive MIMO (multiple-input multiple-output), FD-MIMO (full dimensional MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed for the 5G communication system.

[0021] Furthermore, developments are underway to improve the system network based on advanced small cells, cloud radio access network (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP) transmission and reception, and interference mitigation and cancellation in the 5G communications system.

[0022] In 5G systems, hybrid frequency shift keying and quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as adaptive modulation and coding (AMC) technologies, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) have been developed as advanced access technologies.

[0023] 1 to 4b illustrate various embodiments implemented using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technology in a wireless communication system. The descriptions of FIGS. 1 to 3 do not imply physical or architectural limitations on how different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any appropriately arranged communication system.

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

[0025] 1, wireless network 100 includes eNB 101, eNB 102, and eNB 103. eNB 101 communicates with eNB 102 and eNB 103. eNB 101 further communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

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

[0027] Depending on the network type, the term "base station" or "BS" can refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmit point (TP), transmit-receive point (TRP), enhanced base station (eNodeB or eNB), gNB, macrocell, femtocell, WiFi access point (AP), or other wirelessly enabled device. A base station can provide wireless access via one or more wireless communication protocols, such as 5G 3GPP (registered trademark) new radio interface / access (NR), long term evolution (LTE), LTE-advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "eNodeB" and "eNB" are used in this patent document to refer to a network infrastructure component that provides wireless access to a remote terminal. Also, depending on the network type, other well-known terms may be used instead of "user equipment" or "UE," such as "mobile station," "subscriber station," "remote terminal," "wireless terminal," 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 an eNB, regardless of whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a stationary device (such as a desktop computer or vending machine).

[0028] The dotted lines indicate the approximate extent of coverage areas 120 and 125, which are shown as nearly 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, can have other shapes, including irregular shapes, depending on the configuration of the gNB and changes in the radio environment due to natural and man-made obstructions.

[0029] As described in more detail below, one or more of the UEs 111-116 include circuitry, programming, or a combination thereof for efficient SS / PBCH block frequency location indication. In particular embodiments, one or more of the eNBs 101-103 include circuitry, programming, or a combination thereof for efficient SS / PBCH block frequency location indication.

[0030] Although Figure 1 illustrates an example of wireless network 100, various modifications to Figure 1 may be made. For example, wireless network 100 may include any number of eNBs and any number of UEs in any suitable arrangement. Additionally, eNB 101 may communicate directly with any number of UEs and provide such UEs with wireless broadband access to network 130. Similarly, each eNB 102-103 may communicate directly with network 130 and provide UEs with direct wireless broadband access to the network. Furthermore, eNBs 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.

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

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

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

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

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

[0036] The controller / processor 225 can also run programs and other processes that reside in memory 230, such as an operating system. The controller / processor 225 can move data in and out of memory 230 as required by the executing processes.

[0037] The controller / processor 225 is further coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the eNB 102 to communicate with other devices or systems via a backhaul connection or network. The interface 235 may support communication over any suitable wired or wireless connection. For example, when the eNB 102 is embodied as part of a cellular communication system (such as supporting 5G, LTE, or LTE-A), the interface 235 may allow the eNB 102 to communicate with other eNBs over a wired or wireless backhaul connection. When the eNB 102 is embodied as an access point, the interface 235 may allow the eNB 102 to communicate with a wired or wireless local area network or a larger network (such as the Internet) over a wired or wireless connection. The interface 235 may include any suitable structure supporting communication over a wired or wireless connection, such as an Ethernet or RF transceiver.

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

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

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

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

[0042] The RF transceiver 310 receives incoming RF signals transmitted by eNBs of the network 100 from the antenna 305. The RF transceiver 310 downconverts the incoming RF signals to generate intermediate frequency (IF) or baseband signals. The IF or baseband signals are transmitted to the RX processing circuitry 325, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The RX processing circuitry 325 transmits the processed baseband signals to a speaker 330 (such as voice data) or to a processor 340 for further processing (such as web browsing data).

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

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

[0045] Processor 340 may also execute other processes and programs resident in memory 360, such as processes for CSI reporting over the uplink channel. Processor 340 may move data in and out of memory 360 as required by executing processes. In some embodiments, processor 340 is configured to execute applications 362 based on OS 361 or in response to signals received from an eNB or operator. Processor 340 is further coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I / O interface 345 is a communication path between such accessories and processor 340.

[0046] Processor 340 is further coupled to touchscreen 350 and display 355. An operator of UE 116 can use touchscreen 350 to input data into UE 116. Display 355 can be a liquid crystal display, a light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as a website.

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

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

[0049] FIG. 4a is a high-level diagram of transmit path circuitry 400. For example, the transmit path circuitry 400 can be used for orthogonal frequency division multiple access (OFDMA) communications. FIG. 4b is a high-level diagram of receive path circuitry 450. For example, the receive path circuitry 450 can be used for OFDMA communications. In FIGS. 4a and 4b, for downlink communications, the transmit path circuitry 400 can be implemented in a base station (eNB) 102 or a relay station (RS), and the receive path circuitry 450 can be implemented in a user equipment (e.g., the user equipment 116 in FIG. 1). In another example, for uplink communications, the receive path circuitry 450 can be implemented in a base station (e.g., the eNB 102 in FIG. 1) or an RS, and the transmit path circuitry 400 can be implemented in a user equipment (e.g., the user equipment 116 in FIG. 1).

[0050] The transmit path circuitry includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a size-N inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an up-converter (UC) 430. The receive path circuitry 450 includes a down-converter (DC) 455, a remove cyclic prefix block 460, a serial-to-parallel (S-to-P) block 465, a size-N fast Fourier transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

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

[0052] Furthermore, although the present disclosure relates to embodiments implementing a fast Fourier transform and an inverse fast Fourier transform, this is for illustrative purposes only and should not be construed as limiting the scope of the present disclosure. It will be understood that in alternative embodiments of the present disclosure, the fast Fourier transform function and the inverse fast Fourier transform function can be easily replaced with a discrete Fourier transform (DFT) function and an inverse discrete Fourier transform (IDFT) function, respectively. For DFT and IDFT functions, the value of the N variable can be any integer (e.g., 1, 4, 3, 4, etc.), while for FFT and IFFT functions, the value of the N variable can be any power of an integer (e.g., 1, 2, 4, 8, 16, etc.).

[0053] In the transmit path circuitry 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., LDPC coding), and modulates (e.g., quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) the input bits to generate a series of frequency-domain modulation symbols. The serial-to-parallel block 410 converts (i.e., de-multiplexes) the serial modulated symbols with parallel data to generate N parallel symbol streams, where N is the IFFT / FFT magnitude used by the BS 102 and the UE 116. The magnitude N IFFT block 415 then performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. The parallel-to-serial block 420 converts (i.e., multiplexes) the parallel time-domain output symbols from the magnitude-N IFFT block 415 to generate a serial time-domain signal. Next, the add cyclic prefix block 425 inserts a cyclic prefix into the time-domain signal. Finally, the upconverter 430 modulates (e.g., upconverts) the output of the add cyclic prefix block 425 to an RF frequency for transmission over a wireless channel. The signal may be further baseband filtered before converting to an RF frequency.

[0054] The transmitted RF signal reaches the UE 116 after passing through a wireless channel, where the reverse operation of that performed by the eNB 102 is performed. A downconverter 455 downconverts the received signal to a baseband frequency, and a remove cyclic prefix block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. A serial-to-parallel block 465 converts the time-domain baseband signal into a parallel time-domain signal. A magnitude-N FFT block 470 then performs an FFT algorithm to generate N parallel frequency-domain signals. A parallel-to-serial block 475 converts the parallel frequency-domain signals into a series of modulated data symbols. A channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0055] Each of the eNBs 101-103 may implement a transmit path corresponding to the architecture for transmitting to the user equipment 111-116 on the downlink and a receive path corresponding to the architecture for receiving from the user equipment 111-116 on the uplink. Similarly, each of the user equipment 111-116 may implement a transmit path corresponding to the architecture for transmitting to the eNBs 101-103 on the uplink and a receive path corresponding to the architecture for receiving from the eNBs 101-103 on the downlink.

[0056] Use cases for 5G communication systems have been identified and described. These use cases can be roughly categorized into three groups. For example, enhanced mobile broadband (eMBB) is defined by high bit / s requirements associated with less stringent latency and reliability requirements. Another example is ultra reliable and low latency (URLL), which is defined by less stringent bit / s requirements. Another example is massive machine type communication (mMTC), which is defined by the number of devices in km.2 It may be determined that the number of devices may be as high as 100,000 to 1 million per device, but the reliability / throughput / standby time requirements may be less stringent. Such a scenario may also include power efficiency requirements in that battery consumption must be minimized as much as possible.

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

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

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

[0060] The DL signal also includes the transmission of a logical channel carrying system control information. The BCCH is mapped to a transmission channel designated as the broadcast channel (BCH) when the BCCH carries a master information block (MIB), or to the DL shared channel (DL-SCH) when the BCCH carries a system information block (SIB). Most system information is contained in different SIBs transmitted using the DL-SCH. The presence of system information on the DL-SCH in a subframe can be indicated by the transmission of a corresponding PDCCH carrying a codeword with a cyclic redundancy check (CRC) scrambled with a special system information RNTI (SI-RNTI). Alternatively, scheduling information for SIB transmissions can be provided in the previous SIB, and scheduling information for the first SIB (SIB-1) can be provided by the MIB.

[0061] DL resource allocation is performed in units of subframes and groups of physical resource blocks (PRBs). The transmission BW includes frequency resource units referred to as resource blocks (RBs). Each RB is

number

number

number

[0062] UL signals can include data signals carrying data information, control signals carrying UL control information (UCI), and UL RSs. UL RSs include DMRSs and SRSs (Sounding RSs). The UE transmits DMRSs only in the bandwidth of the respective PUSCHs or PUCCHs. The eNodeB can demodulate data signals or UCI signals using the DMRSs. The UE transmits SRSs to provide UL CSI to the eNodeB. The UE transmits data information or UCI via the respective physical UL shared channels (PUSCHs) or physical UL control channels (PUCCHs). If the UE needs to transmit data information and UCI in the same UL subframe, the UE can multiplex both onto the PUSCH. The UCI includes Hybrid Automatic Repeat request acknowledgment (HARQ-ACK) information indicating correct (ACK) or incorrect (NACK) detection of a data TB on the PDSCH or the absence of PDCCH detection (DTX), a scheduling request (SR) indicating whether the UE has data in its buffer, a rank indicator (RI), and channel state information (CSI) that enables the eNodeB to perform link adaptation for PDSCH transmission to the UE. HARQ-ACK information is also transmitted by the UE in response to PDCCH / EPDCCH detection, indicating the release of a semi-permanently scheduled PDSCH.

[0063] The UL subframe includes two slots, each for transmitting data information, UCI, DMRS, or SRS.

number

number

number

number

number

number

number

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

[0065] As shown in FIG. 5, information bits 510 are encoded by an encoder 520, such as a turbo encoder, and modulated by a modulator 530 using, for example, quadrature phase shift keying (QPSK) modulation. A serial-to-parallel (S / P) converter 540 generates M modulation symbols that are subsequently provided to a mapper 550 to be mapped to REs selected by a transmit BW selection unit 555 for an assigned PDSCH transmit BW. Unit 560 applies an inverse fast Fourier transform (IFFT), and the output is serialized by a parallel-to-serial (P / S) converter 570 to generate a time-domain signal. Filtering is applied by a filter 580, and the signal is transmitted (590). Additional functions such as data scrambling, cyclic prefix insertion, time windowing, interleaving, etc. are well known in the art and are not shown for the sake of brevity.

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

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

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

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

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

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

[0072] A variety of use cases are envisioned for next-generation cellular systems that go beyond the capabilities of LTE systems. One of the requirements for 5G or fifth-generation cellular systems is a system that can operate below and above 6 GHz (e.g., mmWave regime). 3GPP® specifications identify and describe 74 5G use cases; these can be broadly categorized into three distinct groups. The first group is called 'eMBB (enhanced mobile broadband)' and targets high data rates and services with less stringent latency and reliability requirements. The second group is called 'URLL (ultra-reliable and low latency)' and targets applications with less stringent data rate requirements but low latency tolerance. The third group is called 'km' and targets applications with less stringent reliability, data rate, and latency requirements. 2 This is called "massive MTC (mMTC)," which aims to connect a large number of low-power devices, such as 1 million per network.

[0073] To enable 5G networks to support such diverse services with different quality of service (QoS), one method has been identified in the LTE specification called network slicing. A flexible, self-contained frame or subframe design is utilized to efficiently utilize PHY resources and multiplex various slices (with different resource allocation schemes, numerologies, and scheduling strategies) on the DL-SCH.

[0074] Power consumption and battery life are very important for terminals in the Internet of Things (IoT). In narrowband IoT (NB-IoT) or enhanced machine type communication (eMTC) systems, the power of terminal devices can be saved by configuring power saving mode (PSM) or extended discontinuous reception (eDRX) mode. However, the UE cannot hear paging messages while sleeping in PSM mode or eDRX mode. In some IoT application scenarios, the UE must establish a connection with the network within a specific period after receiving a network command. Therefore, UEs with such requirements cannot configure PSM mode or eDRX mode, which has a relatively long period of time.

[0075] In an enhanced version of the NB-IoT and eMTC systems, a wake-up or slip signal / channel is introduced after research and investigation to allow the UE to be paged while saving power. The wake-up signal / channel is configured to wake up the UE, i.e., when the UE needs to continuously monitor the subsequent MTC physical downlink control channel (MPDCCH) used to indicate paging messages. The slip signal / channel is configured to indicate that the UE can enter a slip state, i.e., when the UE does not need to monitor the subsequent MPDCCH used to indicate paging messages.

[0076] In a multi-carrier system, the carrier that transmits the synchronization signal is called the anchor carrier, and in an LTE system, a paging signal is transmitted on the anchor carrier. In an NB-IoT system, a method of transmitting a paging message on a non-anchor carrier is introduced. In an eMTC system, multiple narrowbands, each with six physical resource blocks (PRBs), are defined, introducing the concept of a paging narrowband. Furthermore, in an eMTC system, a downlink control channel (MPDCCH) for MTC is configured to indicate paging messages, and different UEs can monitor the MPDCCH on different narrowbands. Similarly, in an upcoming 5G new radio (NR) system, there is a situation where the UE's bandwidth is smaller than the system bandwidth, and in this case, multiple bandwidth portions can be defined for the paging channel. In the case of multiple carriers, narrowbands, or partial bandwidths, the method of transmitting and receiving wake-up or slip signals remains to be solved.

[0077] 9 illustrates an example time-domain location 900 for PSS / SSS mapping for FDD and TDD in accordance with an embodiment of the present disclosure. The embodiment of the time-domain location 900 illustrated in FIG. 9 is for illustrative purposes only. FIG. 9 does not limit the scope of the present disclosure to any particular implementation.

[0078] Referring to Figure 9, for FDD, from every frame 905, PSS 925 is transmitted in the last symbol of the first slot of subframes 0 and 5 (910 and 915), where a subframe contains two slots. SSS 920 is transmitted in the second last symbol of the same slot. For TDD, for every frame 955, PSS 990 is transmitted in the third symbol of subframes 1 and 6 (965 and 980), while (SSS) 985 is transmitted in the last symbol of subframes 0 and 5 (960 and 970). This difference allows duplexing to be detected in the cell. Resource elements for PSS and SSS are not available for transmission of any other type of DL signal.

[0079] For simplicity, in this disclosure, both FDD and TDD are considered as dual methods for both DL and UL signaling. Although the following exemplary description and embodiments assume orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), this disclosure can be extended to other OFDM-based transmit waveforms or multiple access methods such as filtered OFDM (F-OFDM).

[0080] The present disclosure includes many components that can be combined or used in combination with each other or can operate as stand-alone systems.

[0081] A communication system includes a downlink (DL) that transmits signals from a transmitting point, such as a base station (BS) or NodeB, to a user equipment (UE), and an uplink (UL) that transmits signals from a UE to a receiving point, such as a NodeB. A UE, also commonly referred to as a terminal or mobile station, may be fixed or mobile and may be a cellular phone, a personal computing device, or an automated device. An eNodeB, which is generally a fixed station, may also be referred to as an access point or other equivalent term. In an LTE system, a NodeB is often referred to as an eNodeB. In an NR system, a NodeB is often referred to as a gNodeB.

[0082] In this disclosure, numerology refers to a set of signal parameters that may include subframe duration, subcarrier spacing, cyclic prefix length, transmission bandwidth, or any combination of such signal parameters.

[0083] For LTE initial access, primary and secondary synchronization signals (PSS and SSS, respectively) are used for coarse timing and frequency synchronization and cell ID acquisition. PSS / SSS are transmitted twice per 10 ms radio frame, and time-domain enumeration is implemented using the system domain number (SFN (system frame number) included in the MIB). Therefore, frame timing can be detected from PSS / SSS without increasing the detection burden from the PBCH. Furthermore, the cyclic prefix (CP) length and, if unknown, the duplex mode can be detected from PSS / SSS.

[0084] The PSS consists of a frequency-domain ZC sequence of length 63, with the middle element truncated to prevent the use of dc subcarriers. Three roots are selected for the PSS to represent the identities of the three physical layers within each cell group. The SSS sequence is based on a maximum-length sequence (also known as an M-sequence).

[0085] Each SSS sequence is constructed by interleaving two length-31 BPSK modulated sequences in the frequency domain, where the two source sequences before modulation are different cyclic shifts of the same M-sequence. The cyclic shift index is constructed from the physical cell ID group. Because PSS / SSS detection can be flawed (e.g., due to non-idealities in the auto- and cross-correlation properties of the PSS / SSS and lack of CRC protection), the cell ID hypothesis detected from the PSS / SSS can sometimes be confirmed via PBCH detection.

[0086] The PBCH is primarily used to signal Master Block Information (MIB), which consists of DL and UL system bandwidth information (3 bits), PHICH information (3 bits), and SFN (8 bits). Adding 10 reserved bits (for other uses, such as MTC), the MIB payload becomes 24 bits. After a 16-bit CRC is added, rate-1 / 3 tail-biting convolutional coding, 4x repetition, and QPSK modulation are applied to the 40-bit codeword. The resulting QPSK symbol stream is transmitted over four subframes spread across four radio frames. In addition to detecting the MIB, blind detection of the number of CRS ports for the PBCH is also required.

[0087] For NR licensed spectrum, each synchronization and PBCH signal block (SS / PBCH block) includes one symbol for NR-PSS, two symbols for NR-PBCH, and one symbol for NR-SSS and NR-PBCH, where the four symbols are contiguously mapped and time-division multiplexed. NR-SS is a unified design that includes NR-PSS and NR-SSS sequence designs for all carrier frequency ranges supported by NR. The transmission bandwidth of NR-PSS and NR-SSS (e.g., 12 PRBs) is smaller than the transmission bandwidth of the entire SS / PBCH block (e.g., 20 PRBs). For initial cell selection for an NR cell, the UE assumes a default SS burst set periodicity of 20 ms. To detect non-independent NR cells, the network provides the UE with one SS burst set periodicity per frequency carrier, and, if possible, information for deriving measurement timing / duration.

[0088] A control resource set (CORESET) for receiving common control channels such as RMSI, OSI, SIBx, and RAR must be configured. According to recent 3GPP RAN1 agreements, one CORESET configuration is provided via PBCH (or MIB) for at least RMSI scheduling, and another CORESET configuration is provided via RMSI (or SIB1) for at least RAR scheduling. A CORESET (control resource set) can be characterized by slot timing, OFDM symbol number in each slot, and frequency resource. Such CORESET attributes are indicated or pre-configured for each CORESET.

[0089] In the case of RMSI / SIB scheduling, the CORESET attribute is provided to the PBCH. In the case of RAR scheduling, the CORESET attribute is provided to the RMSI. Among the CORESET attributes set by the PBCH / RMSI, the OFDM symbol number and frequency resource can be commonly applied to all common channels (e.g., SIBx / RAR, etc.), but the slot timing can be specifically determined for different SIBx / RAR. In NR, multiple SS / PBCH blocks within a wideband carrier are supported, and some SS / PBCH blocks on the same carrier may not be associated with any RMSI. For such SS / PBCH blocks without an associated RMSI, one code point (e.g., 4 bits for > 6 GHz, 5 bits for < 6 GHz) in the PRB grid offset indication is used to indicate the absence of an RMSI, and the 8 bits for setting the RMSI CORESET and search space in the MIB can be used for other purposes.

[0090] This disclosure contemplates the use of 8 bits for RMSI CORESET and search space configuration in the MIB, potentially along with other fields or reserved codepoints, when the associated RMSI is not indicated.

[0091] In one embodiment, when multiple SS / PBCH blocks are supported in a wideband, at least one of the SS / PBCH blocks can be located on a predefined synchronization raster to define a cell for initial access purposes. For such SS / PBCH blocks, which may or may not be associated with an RMSI, the presence or absence of an associated RMSI is indicated by a code point in the PRB grid offset indication. If the UE successfully detects an SS / PBCH block on the synchronization raster and further detects that no RMSI associated with the SS / PBCH block exists, the UE can use a field originally used for RMSI setting, e.g., 8 bits, to indicate the exact location of the next or other SS / PBCH block so that the UE can skip some of the synchronization raster positions to perform a blind search.

[0092] In one subembodiment, some other fields of the PBCH content or some reserved code points from other fields of the PBCH content can be combined with the 8 bits for the RMSI CORESET setting to obtain a larger indication range. For example, if one extra bit can be combined, the indication range can be expanded to 511 or 512 (depending on which code point indicates that there is no cell-defining SS / PBCH block in the band). In another example, if up to four other reserved code points can be combined, the indication range can be expanded to up to 1023 or 1024 (depending on which code point indicates that there is no cell-defining SS / PBCH block in the band).

[0093] In one embodiment, the exact position of the synchronization raster where the next SS / PBCH block is associated with the RMSI can be located, where each code point indicates the exact position of the synchronization raster where the SS / PBCH block can be located. After decoding the code point, the UE can directly find the frequency position of the synchronization raster that the UE can search.

[0094] In one subembodiment, the partner location relative to the synchronization raster on which the SS / PBCH block was detected is measured by the number of synchronization rasters, and such number is always non-negative, meaning that the partner location is always defined by the initial cell search procedure within the band. The codepoint defining the partner location of "0" in the next SS / PBCH block is mandatory because if the codepoint is within the indication capability (e.g., for a bandwidth of 255 synchronization rasters using 8 bits), and there is no cell-defined SS / PBCH block with which the RMSI is associated, the UE can skip all possible synchronization rasters within the search range and continue blind searching from the first synchronization raster for partner locations beyond the search range from the current SS / PBCH block.

[0095] [Table 1]

[0096] Table 1. pdcch-ConfigSIB1 (e.g., 8-bit)

[0097] In Table 1, GSCN-Current is the GSCN (global synchronization channel number) value for the current SS / PBCH block indicating that no RMSI exists. During initial cell selection, the UE can assume that no associated RMSI exists if the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3}, and the UE can assume that the mapping of pdcch-ConfigSIB1 to the GSCN of the synchronization raster where the UE can search for cell-defined SS / PBCH blocks within the search band is according to Table 1. If pdcch-ConfigSIB1=0, the UE assumes that there is no cell-defined SS / PBCH block in the range of GSCN-Current to GSCN-Current+255.

[0098] Note that Table 1 can be equivalently given by the formula: In initial cell selection, the UE may assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3} corresponding to the index-reserved-ssb-SubcarrierOffset taking values ​​{0,1,2,3}, respectively, and the UE may assume that the GSCN of the synchronization raster for which the UE can search for cell-defined SS / PBCH blocks within the search band is calculated as GSCN-cell-defined-SSB=GSCN-Current+pdcch-ConfigSIB1 when pdcch-ConfigSIB1>0; the UE may assume that there is no cell-defined SS / PBCH block within the range of GSCN-Current to GSCN-Current+255 when pdcch-ConfigSIB1=0, where GSCN-cell-defined-SSB is the next cell-defined where GSCN is the GSCN for the SS / PBCH block, GSCN-Current is the GSCN value for the current SS / PBCH block indicated by the absence of RMSI, index-reserved-ssb-SubcarrierOffset is the index of the reserved codepoint for ssb-SubcarrierOffset (takes values ​​from {0,1,2,3}), and pdcch-ConfigSIB1 takes values ​​from {0,1,...,254,255}.

[0099] [Table 2]

[0100] Table 2. pdcch-ConfigSIB1 with reserved codepoints for ssb-SubcarrierOffset (e.g., 8 bits)

[0101] In Table 2, GSCN-Current is the GSCN value for the current SS / PBCH block, which is indicated by the absence of an RMSI. During initial cell selection, the UE may assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3}. The UE may assume that the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 to the GSCN of the synchronization raster that allows the UE to search for cell-defined SS / PBCH blocks within the search band is according to Table 2. The UE may assume that no cell-defined SS / PBCH blocks exist within the range of GSCN-Current to GSCN-Current+1023 when {ssb-SubcarrierOffset, pdcch-ConfigSIB1}={r_0,0}.

[0102] Note that Table 2 can be equivalently given by the formula: In initial cell selection, the UE can assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3} corresponding to the index-reserved-ssb-SubcarrierOffset which takes a value from {0,1,2,3} respectively, and the UE can search for cell-defined SS / PBCH blocks within the search band when the GSCN of the synchronization raster is {index-reserved-ssb-SubcarrierOffset, pdcch-ConfigSIB1}{0,0}. -cell-defined-SSB = GSCN-Current + 256 * index-reserved-ssb-SubcarrierOffset + pdcch-ConfigSIB1; the UE assumes that there are no cell-defined SS / PBCH blocks in the range GSCN-Current to GSCN-Current + 1023 when {index-reserved-ssb-SubcarrierOffset, pdcch-ConfigSIB1} = {0,0}, where GSCN-cell-defined-SSB is the GSCN for the next cell-defined SS / PBCH block, GSCN-Current is the GSCN value for the current SS / PBCH block indicated by the absence of RMSI, index-reserved-ssb-SubcarrierOffset is the index of the reserved codepoint in ssb-SubcarrierOffset (takes values ​​from {0,1,2,3}), and pdcch-ConfigSIB1 takes values ​​from {0,1,...,254,255}.

[0103] In another subembodiment, the partner position relative to the synchronization raster on which the SS / PBCH block was detected is determined by the number of synchronization rasters (i.e., the GSCN value), where such number may be a positive or negative number to define the partner position on any one of the SS / PBCH blocks. For example, a code point defining a "0" partner position for the next SS / PBCH block (e.g., for a bandwidth of 255 synchronization rasters using 8 bits) can indicate that there is no SS / PBCH synchronization block with which the RMSI is associated within the indication capability, and the UE can skip all synchronization rasters in the table and continue the blind search on the remaining synchronization rasters.

[0104] For example, more codepoints may not indicate such cell-defined SS / PBCH blocks within the range given by the GSCN index (eg, starting and ending GSCN).

[0105] [Table 3]

[0106] Table 3. pdcch-ConfigSIB1 (e.g., 8-bit)

[0107] In Table 3, GSCN-Current is the GSCN value for the current SS / PBCH block indicating that no RMSI exists. During initial cell selection, the UE can assume that no associated RMSI exists if the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3}, and the UE can assume that the mapping of pdcch-ConfigSIB1 to the GSCN of the synchronization raster that allows the UE to search for cell-defined SS / PBCH blocks within the search band is according to Table 3. If pdcch-ConfigSIB1=0, the UE assumes that there is no cell-defined SS / PBCH block in the range of GSCN-Current-128 to GSCN-Current+127.

[0108] Note that Table 3 can be equivalently given by a formula. In the initial cell selection, the UE can assume that there is no associated RMSI when the UE takes a value from {r_0, r_1, r_2, r_3} corresponding to index-reserved-ssb-SubcarrierOffset where the upper layer parameter ssb-SubcarrierOffset takes values of {0, 1, 2, 3} respectively; the UE can assume that when 0 < pdcch-ConfigSIB1 < 128, the GSCN of the synchronization raster where the UE can search for cell-defined SS / PBCH blocks within the search band is calculated by GSCN-cell-defined-SSB = GSCN-Current + pdcch-ConfigSIB1; the UE assumes that there is no cell-defined SS / PBCH block within the range of GSCN-Current - 128 to GSCN-Current + 127 when pdcch-ConfigSIB1 = 0, where GSCN-cell-defined-SSB is the GSCN for the next cell-defined SS / PBCH block, GSCN-Current is the GSCN value for the current SS / PBCH block indicated by the absence of RMSI, index-reserved-ssb-SubcarrierOffset is the index of the reserved code point of ssb-SubcarrierOffset (taking values from {0, 1, 2, 3}), and pdcch-ConfigSIB1 takes values from {0, 1,..., 254, 255}.

[0109] [Table 4]

[0110] Table 4. pdcch-ConfigSIB1 (e.g., 8 bits) together with the reserved code points of ssb-SubcarrierOffset

[0111] In Table 4, GSCN-Current is the GSCN value for the current SS / PBCH block, which is indicated by the absence of an RMSI. During initial cell selection, the UE may assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3}. The UE may assume that the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 to the GSCN of the synchronization raster that allows the UE to search for cell-defined SS / PBCH blocks within the search band is according to Table 4. The UE may assume that no cell-defined SS / PBCH blocks exist within the range of GSCN-Current-512 to GSCN-Current+511 when {ssb-SubcarrierOffset, pdcch-ConfigSIB1}={r_0,0}.

[0112] Note that Table 4 can be equivalently given by the formula: In initial cell selection, the UE can assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3} corresponding to index-reserved-ssb-SubcarrierOffset taking values ​​{0,1,2,3}, respectively, and the UE can search for cell-defined SS / PBCH blocks within the search band when the GSCN of the synchronization raster reserved-ssb-SubcarrierOffset<2 and {index-reserved-ssb-SubcarrierOffset, pdcch-ConfigSIB1}{0,0}. pdcch-ConfigSIB1; when index-reserved-ssb-SubcarrierOffset > 1, it can be assumed that GSCN-cell-defined-SSB = GSCN-Current-256 * (index-reserved-ssb-SubcarrierOffset-2 - pdcch-ConfigSIB1); the UE assumes that there is no cell-defined SS / PBCH block within the range of GSCN-Current-512 to GSCN-Current+511 when {index-reserved-ssb-SubcarrierOffset, pdcch-ConfigSIB1} = {0,0}, where GSCN-cell-defined-SSB is the next cell-defined where GSCN is the GSCN for the SS / PBCH block, GSCN-Current is the GSCN value for the current SS / PBCH block indicated by the absence of RMSI, index-reserved-ssb-SubcarrierOffset is the index of the reserved codepoint for ssb-SubcarrierOffset (takes values ​​from {0,1,2,3}), and pdcch-ConfigSIB1 takes values ​​from {0,1,...,254,255}.

[0113] [Table 5-1] [Table 5-2] [Table 5-3]

[0114] Table 5. Summary of ssb-SubcarrierOffset code points and MSB of FR1 subcarrier offset (e.g.,

number

[0115] [Table 6-1] [Table 6-2]

[0116] Table 6. pdcch-ConfigSIB1 (e.g., 8 bits) with reserved code points for ssb-SubcarrierOffset to indicate for FR2

[0117] In Tables 5 and 6, GSCN-Current is the GSCN value for the current SS / PBCH block, indicated by the absence of an RMSI. During initial cell selection, the UE may assume that no associated RMSI exists when the higher layer parameter ssb-SubcarrierOffset takes a value from {12, 13, 14, 15} (or equivalently {r_0, r_1, r_2, r_3}), and the UE may use the ssb-SubcarrierOffset for the GSCN of the synchronization raster for which the UE can search for cell-defined SS / PBCH blocks within the search band.

number

[0118] Note that Tables 5 and 6 can be equivalently given by the formula: In initial cell selection, the UE can assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {12, 13, 14, 15} (or equivalently {r_0, r_1, r_2, r_3}), and the UE can search for cell-defined SS / PBCH blocks within the search band when the GSCN of the synchronization raster is ssb-SubcarrierOffset=12, then GSCN-cell-defined-SSB=GSCN-Current+256*a SSB +pdcch-ConfigSIB1+1;GSCN-cell-defined-SSB=GSCN-Current-256*a when ssb-SubcarrierOffset=13 SSB -pdcch-ConfigSIB1-1; UE assumes that GSCN-Current-512*a when ssb-SubcarrierOffset=14 or 15. SSB+256*(ssb-SubcarrierOffset-14)+pdcch-ConfigSIB1) / 32 to GSCN-Current+512*a SSB +256*(ssb-SubcarrierOffset-14)+pdcch-ConfigSIB1)mod32, where GSCN-cell-defined-SSB is the GSCN for the next cell-defined SS / PBCH block, GSCN-Current is the GSCN value for the current SS / PBCH block indicated by the absence of RMSI, and a SSB is for FR1

number

[0119] [Table 7-1] [Table 7-2]

[0120] Table 7. ssb-SubcarrierOffset reserved codepoints and MSB of FR1 subcarrier offset (e.g.,

number

[0121] [Table 8]

[0122] Table 8. Using pdcch-ConfigSIB1 (e.g., 8 bits) with reserved codepoints in ssb-SubcarrierOffset to indicate for FR2

[0123] In Tables 7 and 8, GSCN-Current is the GSCN value for the current SS / PBCH block, indicated by the absence of RMSI. At initial cell selection, the UE determines whether the higher layer parameter ssb-SubcarrierOffset takes a value from {12,13,14,15} for FR2 or {16,17,18,19} for FR1.

number

number

number

[0124] Note that Tables 7 and 8 can be given by the formula: In the initial cell selection, the UE determines whether the upper layer parameter ssb-SubcarrierOffset takes a value from {12,13,14,15} for FR2 or {16,17,18,19} for FR1.

number

number

number

number

[0125] [Table 9-1] [Table 9-2]

[0126] Table 9. ssb-SubcarrierOffset reserved codepoints and MSB of FR1 subcarrier offset (e.g.,

number

[0127] [Table 10-1] [Table 10-2]

[0128] Table 10. pdcch-ConfigSIB1 (e.g., 8 bits) with reserved codepoints for ssb-SubcarrierOffset to indicate for FR2

[0129] In Tables 9 and 10, GSCN-Current is the GSCN value for the current SS / PBCH block, indicated by the absence of an RMSI. During initial cell selection, the UE may assume that no associated RMSI exists when the higher layer parameter ssb-SubcarrierOffset takes a value from {12, 13, 14, 15} (or equivalently {r_0, r_1, r_2, r_3}), and the UE may use the ssb-SubcarrierOffset for the GSCN of the synchronization raster for which the UE can search for cell-defined SS / PBCH blocks within the search band.

number

[0130] Note that Tables 9 and 10 can be equivalently given by the formula: In initial cell selection, the UE can assume that no associated RMSI exists if the upper layer parameter ssb-SubcarrierOffset takes a value from {12, 13, 14, 15} (or equivalently {r_0, r_1, r_2, r_3}), and the UE can search for cell-defined SS / PBCH blocks within the search band if the GSCN of the synchronization raster is FR1.

number

number

number

[0131] In one embodiment, the 8 bits are used to indicate a range of frequency locations within which the SS / PBCH block can be located after being associated with the RMSI, where each of the 256 code points indicates a range of frequency locations within which the SS / PBCH block can be located. After decoding the 8 bits, the UE can proceed directly to the indicated frequency range and blindly search all synchronization rasters within the indicated range if there are multiple synchronization rasters within the indicated range, or directly search the indicated synchronization raster if there is only a single synchronization raster within the indicated range.

[0132] For example, in Table 11, for a given band, assume the lowest carrier frequency is F_1 and the highest carrier frequency is F_2. The entire band is divided into 256 frequency location ranges, possibly including synchronization rasters, where the spacing between each range is I_F = (F_2 - F_1) / 255, and each of the 256 code points represents one of the frequency location ranges.

[0133] [Table 11]

[0134] Table 11. F_1 and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization rasters (e.g., F_1 ​​is the position of the first synchronization raster for a given band, and F_2 is the position of the last synchronization raster for a given band).

[0135] In another example, in Table 12, for a given band, assume the lowest carrier frequency is F_1, the highest carrier frequency is F_2, and the current position (on the synchronization raster) where the UE detects an SS / PBCH block without RMSI is F_S. The remainder of the band to be searched, possibly including the synchronization raster, is divided into 256 frequency location ranges, where the spacing between each range is I_F = (F_2 - F_c) / 255 if the search procedure is assumed to be from low to high in the frequency domain (I_F = (F_c - F_1) / 255 if the search procedure is assumed to be from high to low in the frequency domain), and each of the 256 code points represents one of the frequency location ranges.

[0136] [Table 12]

[0137] Table 12. F_1 and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization rasters (e.g., F_1 ​​is the position of the first synchronization raster for a given band, and F_2 is the position of the last synchronization raster for a given band).

[0138] In one embodiment, if there is only one synchronization raster within all of the indicated ranges (note that the divided ranges may not be uniform), the above embodiment is effectively identical to indicating the exact location of the synchronization raster in such bands. Still, one of the code points can be used to indicate the absence of a cell-defined SS / PBCH block within the band, and the code point can be a separate code point indicating the synchronization raster position, or it can be the synchronization raster position corresponding to the currently searched position in the frequency domain (i.e., the synchronization raster).

[0139] In one subembodiment, if the number of synchronization rasters exceeds 255 for a band, some reserved bits of the PBCH content or some reserved code points from other fields of the PBCH content can be combined with the 8 bits for the RMSI CORESET setting to obtain a larger indication range. For example, if one extra bit can be combined, the indication range can be extended to 511 or 512 (depending on which code point indicates that there are no cell-defined SS / PBCH blocks in the band). In another example, if up to four other reserved code points can be combined, the indication range can be extended to up to 1023 or 1024 (depending on which code point indicates that there are no cell-defined SS / PBCH blocks in the band), which is sufficient to indicate a raster index within the band for NR.

[0140] For example, the PBCH contend or other field of a reserved codepoint can be used to indicate the band number so that the current synchronization raster where the SSB / PBCH block is not associated with RMSI is located in the overlapping bandwidth between the two bands.

[0141] For example, an 8-bit RMSI CORESET configuration (i.e., pdcch-ConfigSIB1) together with a reserved codepoint for ssb-SubcarrierOffset in the MIB (note that there are four reserved codepoints for ssb-SubcarrierOffset, which can be represented as r_0, r_1, r_2, r_3) is used as shown in Table 13, where GSCN-first is the first GSCN value for the currently searched band, GSCN-step-size is the step size of the GSCN value for the currently searched band (e.g., specific values ​​of GSCN-first and GSCN-step-size for each band can be found in the wireless communication specification), and a separate codepoint is used to indicate that there is no cell-defined SS / PBCH block in the currently searched band (e.g., ssb-SubcarrierOffset takes a value of r_0 and pdcch-ConfigSIB1 takes a value of 0).

[0142] During initial cell selection, the UE can assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0, r_1, r_2, r_3}, and the UE can assume that the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 to the GSCN of the synchronization raster that allows the UE to search for cell-defined SS / PBCH blocks within the search band is according to Table 13. Note that the maximum number of GSCNs for the supported NR band is 620, which determines the GSCN range shown in Table 13 as maxGSCN-first to GSCN-first + 619 * GSCN-step-size.

[0143] As new bands are defined for NR, the remaining reserved codepoint combinations can be used to further expand the indication range. For example, if the maximum number of GSCNs for the supported NR bands is determined as X, the GSCN range shown in Table 13 can be GSCN-first to GSCN-first+(X-1)*GSCN-step-size. Note that the indication capability in Table 13 can be X, up to 1023.

[0144] Also, note that Table 13 can be given by the formula: In initial cell selection, the UE can assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3} corresponding to index-reserved-ssb-SubcarrierOffset which takes a value of {0,1,2,3}, respectively, and the UE can select GSCN-cell-def when the GSCN of the synchronization raster in which the UE can search for cell-defined SS / PBCH blocks within the search band is {index-reserved-ssb-SubcarrierOffset, pdcch-ConfigSIB1}{0,0}. It can be assumed that the index-reserved-ssb is calculated by GSCN-first+256*index-reserved-ssb-SubcarrierOffset*GSCN-step-size+(pdcch-ConfigSIB1-1)*GSCN-step-size, and the UE assumes that there is no cell-defined SS / PBCH block in the currently searched band when {index-reserved-ssb-SubcarrierOffset, pdcch-ConfigSIB1}={0, 0}, where GSCN-cell-defined-SSB is the next cell-defined SS / PBCH block in the currently searched band. GSCN for the SS / PBCH block, GSCN-first is the first GSCN value for the currently searched band, GSCN-step-size is the step size of the GSCN value for the currently searched band, index-reserved-ssb-SubcarrierOffset is the index of the reserved codepoint for ssb-SubcarrierOffset (takes a value from {0,1,2,3}), and pdcch-ConfigSIB1 takes a value from {0,1,...,254,255}.

[0145] In one embodiment, GSCN-cell-defined-SSB can be restricted to be less than or equal to GSCN-first+619*GSCN-step-size at this time, and all other code points are reserved for forward compatibility.

[0146] [Table 13]

[0147] Table 13. Indication capabilities

[0148] In another example, using an 8-bit RMSI CORESET configuration (i.e., pdcch-ConfigSIB1) with reserved code points for ssb-SubcarrierOffset in the MIB (note that there are four reserved code points for ssb-SubcarrierOffset, which can be represented as r_0, r_1, r_2, r_3), is shown in Table 14, where GSCN-first is the first GSCN value for the currently searched band, and GSCN-step-size is the step size of the GSCN value for the currently searched band (which can be found, for example, in the wireless communication specification for the specific values ​​of GSCN-first and GSCN-step-size for each band). The code point corresponding to the GSCN of the currently located SS / PBCH block is used to indicate a cell-defined SS / PBCH block in the currently searched band, so a separate code point is not used to indicate the absence of a cell-defined SS / PBCH block in the currently searched band.

[0149] During initial cell selection, the UE can assume that no associated RMSI exists when the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3}, and the UE can assume that the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 to the GSCN of the synchronization raster in which the UE can search for cell-defined SS / PBCH blocks within the search band is according to Table 14.

[0150] If the GSCN for the cell-defined SS / PBCH block determined by Table 14 is the same as the GSCN of the current SS / PBCH block, the UE assumes that there is no cell-defined SS / PBCH block in the currently searched band. The maximum number of GSCNs for a supported NR band is 620, which determines the GSCN range shown in Table 14 as GSCN-first to GSCN-first+619*GSCN-step-size, if any.

[0151] As new bands are defined for NR, the remaining reserved codepoint combinations can be used to further expand the indication range. For example, if the maximum number of GSCNs for the supported NR bands is determined as X, the GSCN range shown in Table 14 can be GSCN-first to GSCN-first+(X-1)*GSCN-step-size. Note that the indication capability in Table 14 can be X up to 1024. Also, note that Table 14 can be given by the formula:

[0152] During initial cell selection, the UE may assume that no associated RMSI exists if the upper layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3} corresponding to index-reserved-ssb-SubcarrierOffset taking values ​​{0,1,2,3}, respectively. The UE may assume that the GSCN of the synchronization raster for which the UE can search for cell-defined SS / PBCH blocks within the search band is calculated as GSCN-cell-defined-SSB=GSCN-first+256*index-reserved-ssb-SubcarrierOffset*GSCN-step-size+pdcch-ConfigSIB1*GSCN-step-size. The UE may assume that no cell-defined SS / PBCH block exists within the currently searched band if GSCN-cell-defined-SSB is the same as the GSCN of the current SS / PBCH block, where GSCN-cell-defined-SSB is the next cell-defined SS / PBCH block within the currently searched band. where GSCN for the SS / PBCH block, GSCN-first is the first GSCN value for the currently searched band, GSCN-step-size is the step size of the GSCN value for the currently searched band, index-reserved-ssb-SubcarrierOffset is the index of the reserved codepoint in ssb-SubcarrierOffset (takes values ​​from {0, 1, 2, 3}), and pdcch-ConfigSIB1 takes values ​​from {0, 1, ..., 254, 255}. In one embodiment, GSCN-cell-defined-SSB can be constrained at this point to be less than or equal to GSCN-first + 619 * GSCN-step-size, and all other codepoints are reserved for forward compatibility.

[0153] [Table 14]

[0154] Table 14. Indication capabilities

[0155] In one embodiment, a field in the PBCH payload is used to indicate a bitmap of frequency location or carrier ranges where the SS / PBCH block associated with the RMSI can be located. After decoding the field in the PBCH payload, the UE can find all ranges of frequency locations where the SS / PBCH block associated with the RMSI can be located. The UE can select one of the indicated location ranges (e.g., indicated as "1" in the bitmap for that frequency range) and blindly search all synchronization rasters within the indicated range.

[0156] For example, assume the lowest carrier frequency is F_1 and the highest carrier frequency is F_2. The entire band is divided into N frequency location ranges, possibly including synchronization rasters [F_1, F_1+I_F), [F_1+I_F, F_1+2*I_F), ..., [F_1+(N-1)*I_F, F_2], where the spacing between each range is I_F=(F_2-F_1) / (N-1), and each of the 2^N code points represents a bitmap indicating which of the N ranges includes an SS / PBCH block with RMSI. Table 15 shows an example where N=8. Table 16 shows an example where N=4.

[0157] [Table 15]

[0158] Table 15. N=8, F_1 ​​and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization rasters (i.e., F_1 ​​is the position of the first synchronization raster for a given band, and F_2 is the position of the last synchronization raster for a given band).

[0159] [Table 16]

[0160] Table 16. N=4, F_1 ​​and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization rasters (i.e., F_1 ​​is the position of the first synchronization raster for a given band, and F_2 is the position of the last synchronization raster for a given band).

[0161] In another example, assume the lowest carrier frequency as F_1, the highest carrier frequency as F_2, and the current position (on the synchronization raster) where the UE detects the SS / PBCH block without RMSI as F_S. The remainder of the search band is divided into N frequency location ranges possibly including the synchronization raster [F_c, F_c + I_F), [F_c + I_F, F_c + 2*I_F), ..., [F_c + (N-1)*I_F, F_2], where the spacing of each range is I_F = (F_2-F_c) / (N-1) if the search procedure is assumed to be low to high in the frequency domain (I_F = (F_c-F_1) / (N-1)), and the ranges are [F_1, F_1 ​​+ I_F), [F_1 + I_F, F_1 ​​+ 2*I_F), ..., [F_1 + (N-1)*I_F, F_c] if the search procedure is assumed to be high to low in the frequency domain, and each of the 2^N code points represents a bitmap indicating one of the N ranges containing SS / PBCH blocks with RMSI. Table 17 shows an example where N=8, and Table 18 shows an example where N=4.

[0162] [Table 17]

[0163] Table 17. N=8, F_1 ​​and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization rasters (i.e., F_1 ​​is the position of the first synchronization raster for a given band, and F_2 is the position of the last synchronization raster for a given band).

[0164] [Table 18]

[0165] Table 18. N=4, F_1 ​​and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization rasters (i.e., F_1 ​​is the position of the first synchronization raster for a given band, and F_2 is the position of the last synchronization raster for a given band).

[0166] In one embodiment, when multiple SS / PBCH blocks are supported in a wideband, there may be SS / PBCH blocks that are not located on the synchronization raster. For such SS / PBCH blocks, which may or may not be associated with an RMSI, whether or not there is an associated RMSI is indicated by a code point in the PRB grid offset indication. If the UE successfully detects an SS / PBCH block on the synchronization raster and further detects that there is no RMSI associated with the SS / PBCH block, the UE can use the 8 bits originally used for RMSI setting to indicate the exact location of the next or other SS / PBCH block on the synchronization raster, thereby allowing the UE to skip some synchronization raster positions for blind searching. If the indicated SS / PBCH is on the synchronization raster, all of the methods shown in component I can be reused here.

[0167] In another embodiment, when multiple SS / PBCH blocks are supported in a wideband, there may be SS / PBCH blocks that are not located on the synchronization raster. For such SS / PBCH blocks, which may or may not be associated with an RMSI, whether or not there is an associated RMSI is indicated by a code point in the PRB grid offset indication. If the UE successfully detects an SS / PBCH block that is not on the synchronization raster and further detects that there is no RMSI associated with the SS / PBCH block, the UE can use the 8 bits originally used for RMSI setting to indicate the exact location of the next or other SS / PBCH block. Such SS / PBCH blocks may or may not be on the synchronization raster and may or may not have an associated RMSI.

[0168] For example, 8 bits are used to indicate the exact location of another SS / PBCH block, which may or may not be associated with an RMSI, where each of 256 code points indicates a more accurate peer location relative to the current SS / PBCH block without an RMSI. After decoding these 8 bits from the MIB, the UE can directly find the frequency location of the other indicated SS / PBCH block. The peer location relative to the current synchronization raster where the SS / PBCH block is detected is determined by the number of PRBs in the SS numerology for that band, where this number is always non-negative, meaning that the peer location is always defined by the initial cell search procedure within the band. The code point defining the "0" peer location of the next SS / PBCH block is mandatory because, if the code point uses 8 bits (e.g., for a bandwidth of 255 PRBs), there is no SS / PBCH synchronization associated with the RMSI within the indication capability, and the UE can skip all 255 possible PRBs to search for the SS / PBCH block.

[0169] In another embodiment, when multiple SS / PBCH blocks are supported in a wideband, there may be SS / PBCH blocks that are not located on the synchronization raster. For such SS / PBCH blocks, which may or may not be associated with an RMSI, whether or not there is an associated RMSI is indicated by a code point in the PRB grid offset indication (i.e., a reserved code point in ssb-SubcarrierOffset, e.g., r_0). 8 bits of pdcch-ConfigSIB1 may be reserved for other purposes (e.g., measurement parameter configuration).

[0170] At least some or all of the following fields are provided within the content of a compact DCI format designed specifically for the common control channel, which may include at least one of transmission of remaining minimum system information (RMSI) on a 4-stage RACH or 2-stage RACH, broadcast of other system information (OSI), paging, and random access response (RAR).

[0171] Generally, two types of PDSCH resource allocation are defined, where Type 0 indicates a resource allocation with configurable granularity of frequency resources determined by the size of the BWP (e.g., one RBG generally consists of multiple VRBs) using a bitmap, and Type 1 indicates the length of the starting VRB and consecutive VRBs in the frequency domain with a granularity of one VRB using a resource indication value (RIV).

[0172] In one embodiment, for the common control channels provided in this disclosure, only a single type of resource allocation scheme is supported in the compact DCI format, and no header bit is essentially required to indicate the type of resource allocation (or to still maintain a hear bit with a fixed value indicating the single type of resource allocation supported).

[0173] For example, for a common control channel, since messages can be received by all UEs in a cell, it is advantageous to attempt to maximize the utilization of configured resources with a granularity of X VRB. Therefore, only Type 1 resource allocation schemes are supported in the compact DCI format. Generally, the bit width of Type 1 resource allocation used for defining the RIV can be related to the size of the BWP, but for the common control channel provided in this disclosure, the definition of the RIV is not as flexible as for PDSCH data, where the size of the BWP for the PDSCH is common.

[0174] For example, the size of the BWP for defining the RIV is fixed for all common control channels, e.g., 96 (the maximum RB share for the CORESET BW set in the MIB). Then, the bit width of the field is common to all common control channels. The RIV can be defined by RIV = 96 * (L_VRB-1) + S_VRB, where L_VRB is the length of the VRB and S_VRB is the starting VRB index.

[0175] 10 illustrates an exemplary SS / PBCH block multiplexed with a CORESET of RMSI 1000 according to an embodiment of the present disclosure. The embodiment of an SS / PBCH block multiplexed with a CORESET of RMSI 1000 illustrated in FIG. 10 is for illustrative purposes only. FIG. 10 does not limit the scope of the present disclosure to any particular implementation.

[0176] A particular sub-example of the above example is L_VRB=CORESET_BW and S_VRB=0, which means that the PDSCH BW is the same as CORESET_BW and can be applied to some multiplexing patterns (e.g., at least Pattern 2 and / or Pattern 3 as shown in FIG. 10, and / or some cases of Pattern 1 where the PDSCH coverage is limited by a small BW and / or a small number of OFDM symbols). In this sub-example, no bits are required and the RIV values ​​(or equivalently L_VRB and S_VRB) can be hard-coded in the specification.

[0177] In another example, the size of the BWP for defining the RIV is the same as the CORESET BW actually set in the MIB, and can be different for different common control channels. The RIV can be defined as RIV = CORESET_BW * (L_VRB - 1) + S_VRB, where L_VRB is the length of the VRB, S_VRB is the starting VRB index, and CORESET_BW is the BW of the CORESET set in the MIB.

[0178] One particular sub-example of such an example is L_VRB=CORESET_BW and S_VRB=0, which means that the PDSCH BW is the same as CORESET_BW and can be applied to some multiplexing patterns (e.g., at least for Pattern 2 and / or Pattern 3 as shown in FIG. 10, and / or for some cases of Pattern 1 where the PDSCH coverage is limited by a small BW and / or a small number of OFDM symbols). In this sub-example, no bits are required and the RIV values ​​(or equivalently L_VRB and S_VRB) can be hard-coded in the specification.

[0179] For example (which can be applied to all the examples above), the lengths of the starting VRB and the consecutive VRBs can be set based on the number of CCEs, for example, to make the coverage of PDCCH and PDSCH compatible.

[0180] In the above-described embodiment / example of the Type 1 resource allocation scheme, X is the number of VRBs as the granularity for resource allocation. Note that the value of X determines the number of bits for representing the frequency domain resource field. For example, the number of bits can be determined by log2[(N_RB^BWP / X)*(N_RB^BWP / X+1) / 2], where N_RB^BWP is the number of RBs in the provided BWP. In the case of RMSI, N_RB^BWP may be equal to the CORESET BW in terms of RBs.

[0181] For example, X is predefined in the specification and takes a common value when the Type 1 resource allocation method is used. For example, X=1 corresponds to the most flexible resource allocation case, but may require a larger number of bits to indicate such a field. In other examples, X=2, 4, or 6 corresponds to a less flexible resource allocation case than X=1, but may require a smaller number of bits. In other examples, X is equal to the granularity of the interleaver.

[0182] In other examples, X is predefined in the specification, and specific values ​​are defined based on the CORESET BW. In such examples, there can be multiple values ​​for X depending on the CORESET BW. The purpose of such multiple granularity for X is to attempt to align the number of bits for representing the frequency domain resource field when the total BW varies, e.g., the CORESET BW of RB / X is an integer for at least some values ​​of CORESET BW. Some specific examples of such examples are shown in Tables 11 to 13.

[0183] [Table 19]

[0184] Table 19. RB / X CORESET BW

[0185] [Table 20]

[0186] Table 20. RB / X CORESET BW

[0187] [Table 21]

[0188] Table 21. CORESET BW for RB / X

[0189] In another example, X can be configured by the RRC, and a default value is assumed by the UE at initial access. For example, the default X=1 corresponds to the most flexible resource allocation case, but may require more bits to indicate such a field, e.g., for a CORESET BW of 96 RBs, the number of bits required is 13. In another example, the default X=2, 4, or 6 corresponds to a less flexible resource allocation case than X=1, but may require fewer bits. In another example, the default X is equal to the interleaver granularity.

[0190] In another embodiment, for the common control channel provided in the present disclosure, two types of resource allocation schemes are supported in the compact DCI format to provide full flexibility for PDSCH resource allocation in the frequency domain, and the definition of bitmap in Type 0 and the definition of RIV in Type 1 refer to the definition for the general case or can be used as described in the above embodiment where only Type 1 resource allocation is supported.

[0191] Generally, block interleaved VRB to PRB mapping is supported for Type 1 resource allocation to obtain frequency diversity gain, and an indication of block interleaved or non-block interleaved VRB to PRB mapping can be carried by one bit in the DCI format.

[0192] In one embodiment, when only the Type 1 resource allocation scheme is supported for the common control channel provided in the present disclosure, only block interleaved VRB-to-PRB mapping is supported to obtain frequency diversity gain, and no indication is required in the compact DCI format. In this case, since only the initially active BWP is used to transmit the common control channel, block interleaved VRB-to-PRB mapping can be performed within the entire initially active BWP, which is much simpler than the general case where multiple BWPs exist and may overlap. In such an embodiment, the VRB-to-PRB mapping field can be hard-coded in the specification as block interleaved VRB-to-PRB mapping, and the block size for interleaving can also be hard-coded in the specification (e.g., the same as the granularity for resource allocation).

[0193] In other embodiments, both block interleaved and non-block interleaved VRB-to-PRB mappings are supported for the common control channels provided in this disclosure, and one bit in the compact DCI format is used to indicate the VRB-to-PRB mapping pattern (e.g., block interleaved or non-block interleaved).

[0194] Generally, a time-domain PDSCH resource is specified by the slot-level timing difference between the slot containing the corresponding CORESET and the slot containing the PDSCH (e.g., denoted as T_slot), along with the starting OFDM symbol within the slot (e.g., denoted as S_sym) and the length of the OFDM symbol for the PDSCH (e.g., denoted as L_sym).

[0195] In one embodiment, for the common control channel provided in this disclosure, a time-domain PDSCH resource can be defined for each multiplexing pattern of SS / PBCH blocks and CORESET / PDSCH. Note that, as shown in Figure 10, three multiplexing patterns of SS / PBCH blocks and CORESET / PDSCH are supported in NR.

[0196] For example, pattern 1 refers to a multiplexing pattern in which the SS / PBCH block and the RMSI CORESET occur at different time instances, and the SS / PBCH block TX BW and the initially active DL BWP including the RMSI CORESET overlap. Note that the time difference between the SS / PBCH block and the CORESET / PDSCH can be 0 or greater than one slot.

[0197] In another example, pattern 2 refers to a multiplexing pattern in which the SS / PBCH block and the RMSI CORESET occur at different time instances, and the SS / PBCH block TX BW and the initial active DL BWP including the RMSI CORESET do not overlap.

[0198] In another example, pattern 3 refers to a multiplexing pattern in which the SS / PBCH block and the RMSI CORESET occur at the same time instance, and the SS / PBCH block TX BW and the initially active DL BWP including the RMSI CORESET do not overlap.

[0199] For example, when the multiplexing pattern of the SS / PBCH block and CORESET / PDSCH is set as pattern 1 indicated in the MIB for the NR-PBCH in the SS / PBCH block, T_slot may be a configurable integer having many values, and S_sym and L_sym may be jointly coded by the RIV. For example, the slot level difference T_slot may be set from 0, 2*u, 5*u, 7*u if < 6 GHz, and from 0, 2.5*u, 5*u, 7.5*u if > 6 GHz, where u = SS_SCS / 15 kHz. In another example, S_sym and L_sym may be jointly coded by the RIV by RIV = 14 * (L_sym-1) + S_sym if L_sym-1 < 7; otherwise, RIV = 14 * (14 - L_sym+1) + 14 - 1 - S_sym).

[0200] For example, the time domain PDSCH resources (e.g., L_sym, S_sym, and T_slot) for pattern 1 can be determined based on the value M of the parameter table for the PDCCH monitoring case, where M refers to the time difference (measured in slots) between slots containing CORESETs corresponding to SS / PBCH blocks with indexes i and i+1.

[0201] For example, when M=2, T_slot>0, which means that cross-slot scheduling of PDSCH can be supported when the slot difference between CORESETs is 2 slots in.

[0202] For example, when M=1 / 2 and M=1, T_slot=0, which means that when the slot difference between CORESETs is 1 / 2 and 1 slot in, the same slot scheduling of PDSCH can be supported.

[0203] In this example, the time domain PDSCH resources (e.g., L_sym, S_sym, and T_slot) for pattern 1 may be determined based on the RMSI configuration in the MIB, i.e., RMSI-PDCCH-Config. If a 4-bit table containing up to 16 configurations is defined for the PDSCH time domain resources in the general case, at least one configuration in the table may be used for each configuration of RMSI (i.e., each value of RMSI-PDCCH-Config).

[0204] In one particular example, only one setting in the table is used for each setting of the RMSI, and the association can be hard-coded in the specification, so no bits are required for such a field. In another particular example, a maximum Y setting in the table is used for each setting of the RMSI, and then a maximum of log2(Y) bits are required for such a field, e.g., Y=4 for a comprehensive example of complexity and flexibility.

[0205] In other examples, the above-described embodiments / examples may be combined with or independent of such examples, and the scrambling sequence of the PDCCH in the CORESET may be based on the SS / PBCH block index, thereby allowing the UE to detect the SS / PBCH block index within the monitoring window duration and store the transmission of some SS / PBCH blocks.

[0206] In another example, if the multiplexing pattern of the SS / PBCH block and CORESET / PDSCH is set as Pattern 2 indicated in the MIB for the NR-PBCH in the SS / PBCH block, T_slot can be hard-coded as 0 (or absent in such a field in the DCI format for Pattern 2), and S_sym and L_sym can be determined by the symbol in the slot mapped to the SS / PBCH block (e.g., determined from the SS block index I_SSB and the subcarrier spacing of the SS / PBCH block SCS_SS). In one embodiment, S_sym and L_sym can still be jointly coded by the RIV using the same method as Pattern 1, or S_sym and L_sym can be hard-coded in the specification, and it is noted that a field for the time domain PDSCH resource is not required in the DCI format.

[0207] For example, S_sym may be the symbol mapped to the first symbol of the corresponding SS / PBCH block (i.e., the symbol mapped to NR-PSS), and L_sym may be hard-coded as 4. Table 22 shows a list of examples for such instances.

[0208] [Table 22]

[0209] Table 22. S_sym and L_sym

[0210] In other instances, S_sym may be a symbol mapped to the first symbol of the corresponding SS / PBCH block (i.e., a symbol mapped to the NR-PSS), and for specific values ​​of T_slot for each SCS_SS, refer to Table 22, and L_sym can be set (e.g., can be set among 1, 2, 3, and 4).

[0211] In another example, if the multiplexing pattern of the SS / PBCH block and CORESET / PDSCH is set as Pattern 3 indicated in the MIB for the NR-PBCH in the SS / PBCH block, T_slot can be hard-coded as 0 (or absent in such a field in the DCI format for Pattern 3), and S_sym and L_sym can be determined by the symbol in the slot mapped to the SS / PBCH block (e.g., determined from the SS block index I_SSB and the subcarrier spacing of the SS / PBCH block SCS_SS). In one embodiment, S_sym and L_sym can still be jointly coded by the RIV using the same method as Pattern 1, or S_sym and L_sym can be hard-coded in the specification, and it is noted that a field for the time domain PDSCH resource is not required in the DCI format.

[0212] For example, S_sym may be the symbol mapped to the third symbol of the corresponding SS / PBCH block (i.e., the symbol mapped to NR-SSS and NR-PBCH), and L_sym may be hard-coded as 2. Table 23 shows a list of examples for such instances.

[0213] [Table 23]

[0214] Table 23. S_sym and L_sym

[0215] In another embodiment, for the common control channel provided in this disclosure, the time-domain PDSCH resource can be jointly coded with the frequency-domain PDSCH resource and can be defined for each multiplexing pattern of the SS / PBCH block and CORESET / PDSCH (using the same or different bit widths for each multiplexing pattern). Note that three multiplexing patterns of the SS / PBCH block and CORESET / PDSCH are supported in NR, as shown in FIG.

[0216] For example, when the multiplexing pattern of the SS / PBCH block and the CORESET / PDSCH is set as Pattern 1, the time domain and frequency domain resources can be jointly coded, where the total number of REs is configurable, e.g., the total number of REs can be compatible with the number of CCEs of the CORESET in terms of similar coverage.

[0217] In another example, when the multiplexing pattern of the SS / PBCH block and CORESET / PDSCH is set as pattern 2, the time domain and frequency domain resources can be jointly coded, where both the time domain and frequency domain resources are hard coded.

[0218] In another example, when the multiplexing pattern of the SS / PBCH block and CORESET / PDSCH is set as pattern 3, the time domain and frequency domain resources can be jointly coded, where both the time domain and frequency domain resources are hard coded.

[0219] Generally, the modulation and coding scheme of the PDSCH is captured by an MCS table. In one embodiment, for the common control channel provided in this disclosure, the modulation and coding scheme of the PDSCH can be captured by a compact version of the MCS table, where only low-order modulation schemes are supported in the compact DCI format, and the bit width of such fields in the compact DCI format may be smaller than in other DCI formats.

[0220] In one embodiment, among all common control channels provided in the present disclosure, some channels, such as broadcast OSI and RMSI, encode messages in multiple blocks and map them for different transmissions, so that a redundancy version is required to mark different encoded blocks. Therefore, only for such channels, the compact DCI format may have a redundancy version field with different values ​​(e.g., 4 values ​​represented by 2 bits or 8 values ​​represented by 3 bits), and for other channels, the compact DCI format may leave the corresponding field as a default value (e.g., 0).

[0221] In another embodiment, among all common control channels provided in the present disclosure, some channels, such as broadcast OSI and RMSI, encode messages in multiple blocks and map them for different transmissions, so that a redundancy version is required to mark the different encoded blocks. The redundancy version can be determined based on the SFN value (i.e., timing within the TTI), and can be known to the UE so that a bit for the redundancy version field is not required for the common control channels provided in the present disclosure.

[0222] In general, TPC (Transmission Power Control) commands may be transmitted as part of a DCI format having a common search space. In one embodiment, for common control channels provided in this disclosure, a compact DCI format may have a field for TPC commands for the PUCCH (e.g., having 2 bits). In another embodiment, for common control channels provided in this disclosure, a field for the compact DCI format is not required before an RRC connection.

[0223] The header field for the compact DCI format is only necessary when the compact DCI format for the common control channel has the same DCI size as another DCI format (e.g., a partial fallback DCI format for msg4 of RACH or another compact DCI format), in which case the header field is used to distinguish different DCI formats. If there is no DCI format that has the same DCI size as the compact DCI format for the common control channel, the header field is basically not necessary.

[0224] Generally, such a flag is used to indicate whether reserved resources in both the frequency domain and the time domain are excluded from the rectangular resources allocated to the PDSCH, where the reserved resources can be used for other purposes, such as forward compatibility or LTE-NR coexistence. In one embodiment, for the same purpose, such a flag still exists for the compact DCI format designed for the common control channel. In another embodiment, such a field does not exist before the RRC connection and is not necessary for the common control channel provided in this disclosure.

[0225] At least some or all of the following fields are not provided in the content of the compact DCI format designed specifically for common voice channels that may include at least one of RMSI, OSI, paging, and RAR transmissions:

[0226] The common control channel provided in the present disclosure is primarily for initial access purposes, and therefore, the carrier and BWP for transmitting the common control channel provided in the present disclosure do not need to be configured or indicated. In one embodiment, the compact DCI format for the common control channel provided in the present disclosure does not include a carrier indicator or BWP indicator field.

[0227] In one embodiment, the bundling size for the PDSCH for the common control channel provided in the present disclosure is fixed (e.g., 6 PRB), and the compact DCI format for the common control channel provided in the present disclosure does not include a bundling size indicator field.

[0228] The common control channels provided in this disclosure may not have new data transmissions, and therefore the new data indicator is not applicable. In one embodiment, the compact DCI format for the common control channels provided in this disclosure does not include a new data indicator field.

[0229] The common control channel provided in this disclosure may have only a single codeword, and parameters related to the second codeword may not be applicable to the common control channel. In one embodiment, the compact DCI format for the common control channel provided in this disclosure does not include fields for parameters related to the second codeword, including modulation and coding scheme, new data indicator, and redundancy version.

[0230] The common control channel provided in the present disclosure may not have any HARQ process, and therefore, parameters related to HARQ may not be applicable to the common control channel. In one embodiment, the compact DCI format for the common control channel provided in the present disclosure does not include fields for parameters for HARQ processes, including HARQ process number, CBGFI, CBGTI, ACK / NACK resource index, HARQ timing indicator, and downlink allocation index.

[0231] It is noted that in one embodiment, if the compact DCI format is also applicable to msg4 of the RACH, the HARQ process related parameters may be provided as fields in the compact DCI format.

[0232] The common control channel provided in the present disclosure cannot have multiple configurations for antenna ports and can only support single-layer transmission, so the configuration for antenna ports can be fixed for the PDSCH of the common control channel. In one embodiment, the compact DCI format for the common control channel provided in the present disclosure does not include a field for antenna ports.

[0233] Generally, a Transmission Configuration Indication (TCI) is used to provide a beam indication to indicate the QCL assumption between a DL RS antenna port and a DMRS antenna port of a DL data channel, at least in terms of spatial QCL parameters. For the common control channels provided in this disclosure, the common control channels are QCL'd in the corresponding SS / PBCH blocks so that TCI is not required for the common control channels. In one embodiment, the compact DCI format for the common control channels provided in this disclosure does not include a field for TCI.

[0234] An example of a compact DCI format design for the common control channel is shown in Table 24, where the total DCI size is about 20 to 30 bits, which is much smaller than other DCI formats (e.g., at least about 40 to 50 bits).

[0235] [Table 24]

[0236] Table 24. Compact DCI format design

[0237] Another example of a compact DCI format design for the common control channel is shown in Table 25, where all DCI sizes are based on the SS / PBCH block and CORESET multiplexing pattern, which is approximately 15 bits for Pattern 1 and less than 5 bits for Pattern 2 and Pattern 3.

[0238] [Table 25]

[0239] Table 25. Compact DCI format design

[0240] The DMRS sequence of the PDCCH is composed of a QPSK modulated Gold sequence, where the XOR of two length-LM sequences is the M-sequence s A One of (n) is generator g A (x) and initial condition c A and other M-sequences s B (n) is the generator g B (x) and initial condition c B The QPSK modulated Gold sequence s(n)=1-2*((s A (2n+N c )+s B(2n+Nc))mod2) / v2+j*1-2*((s A (2n+N c +1)+s B (2n+N c +1))mod2) / v2, and a possible output shift offset N so that s(n) is truncated to the desired DMRS sequence length N_DMRS. c (For example, N c = 1600). The length of the Gold-sequence L is the same as in LTE-CRS (e.g., 2^31-1), and the length of the M-sequence s A One of (n) is the initial condition c A (e.g., c A = 1) is fixed g A (x)=x 31 +x 3 +1, and other M-sequences s B (n) is the initial condition c B g with B (x)=x 31 +x 3 +x 2 +x+1. The initial condition c B carries an ID (one of the cell ID or C-RNTI) and a timing related index so that the DMRS sequence varies with time.

[0241] In one embodiment, the timing-related index includes a slot index and a symbol index, and the initial condition is the product form of the ID and the timing-related index.

[0242] For example, c B =mod(c_1*(N_ID+1)*14*N_slot+N_symbol+1)+c_2*14*N_slot+N_symbol+1)+c_3*(N_ID+1), 2^31), where c_1, c_2, and c_3 are predefined integers. Note that c_1>2^12 so that in this example mod 2^31 is required.

[0243] In other examples, c B=mod(c_1*(2*N_ID+1)*14*N_slot+N_symbol+1)+c_2*14*N_slot+N_symbol+1)+c_3*(2*N_ID+1), 2^31), where c_1, c_2, and c_3 are predefined integers. Note that c_1>2^11 so that in this example mod 2^31 is required.

[0244] In other examples, c B = c_1*(N_ID+1)*14*N_slot+N_symbol+1)+c_2*14*N_slot+N_symbol+1)+c_3*(N_ID+1), where c_1, c_2, and c_3 are predefined integers. In this example, c_1≦2^12. For example, c_1=2, c_2=2^12, and c_3=0, i.e., c B =2*(N_ID+1)*14*N_slot+N_symbol+1)+2^12*14*N_slot+N_symbol+1).

[0245] In other examples, c B = c_1 * (2 * N_ID + 1) * 14 * N_slot + N_symbol + 1) + c_2 * 14 * N_slot + N_symbol + 1) + c_3 * (2 * N_ID + 1), where c_1, c_2 and c_3 are predefined integers. In such an example, c_1 ≦ 2^11.

[0246] 11 illustrates a flowchart of a method 1100 for a UE according to an embodiment of the present disclosure. The embodiment of the method 1100 illustrated in FIG. 11 is for illustrative purposes only. FIG. 11 does not limit the scope of the present disclosure to any particular implementation.

[0247] As shown in Figure 11, method 1100 begins at start. In step 1102, a UE (e.g., 111-116 as shown in Figure 1) receives a synchronization signal and physical broadcast channel (SS / PBCH) block including a PBCH using a first frequency location (GSCN-Current) - GSCN-Current is based on a set of predefined synchronization rasters determined by a global synchronization channel number (GSCN) - from a base station (BS) over a downlink channel.

[0248] In one embodiment, in step 1102, the SS / PBCH block associated with the PDCCH including scheduling information for the RMSI on the determined GSCN-Current is determined as follows: for the first carrier frequency range, the ssb-SubcarrierOffset field in the PBCH content is based on a value from {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15} and ...

number

number

[0249] In one embodiment, in step 1102, the SS / PBCH block not associated with the PDCCH containing scheduling information for the RMSI on the determined GSCN-Current is a field of ssb-SubcarrierOffset in the content of the PBCH based on a value from {8, 9, 10, 11, 12, 13, 14, 15} for the first frequency range and a field of ssb-SubcarrierOffset in the content of the PBCH with a value of 1.

number

[0250] In this embodiment, the frequency range in which other SS / PBCH blocks configured with a PDCCH containing scheduling information for RMSI are not transmitted is the first carrier frequency range, where the ssb-SubcarrierOffset field in the PBCH content has a value of 15 and the ssb-SubcarrierOffset field in the PBCH content has a value of 1.

number

[0251] In this embodiment, the frequency range in which other SS / PBCH blocks configured with a PDCCH containing scheduling information for RMSI are not transmitted is given by GSCN-Current when pdcch-ConfigSIB1=0.

[0252] In this embodiment, the second frequency location at which the other SS / PBCH blocks configured with the PDCCH containing scheduling information for RMSI are transmitted is the first carrier frequency range 1, where the ssb-SubcarrierOffset field in the PBCH content is based on a value from {8,9,10} and the ssb-SubcarrierOffset field in the PBCH content has a value of 1.

number

number

[0253] In such an embodiment, pdcch-ConfigSIB1 is the content of the PBCH and is 8 bits in length.

[0254] In one embodiment, when configuring a PDCCH including scheduling information for the RMSI on the determined GSCN-Current for the SS / PBCH block, the processor is further configured to determine scheduling information for the RMSI based on a multiplexing pattern of the SS / PBCH block and a control resource set (CORESET) including the PDCCH, where the scheduling information for the RMSI includes at least a time domain resource allocation of a physical downlink shared channel (PDSCH) for the RMSI.

[0255] In step 1104, the UE decodes the PBCH included in the received SS / PBCH block.

[0256] In step 1106, the UE identifies the content of the decoded PBCH.

[0257] In step 1108, the UE determines a configuration for at least one of an SS / PBCH block associated with a physical downlink control channel (PDCCH) containing scheduling information for RMSI (remaining minimum system information) on the GSCN-Current or an SS / PBCH block not associated with a PDCCH containing scheduling information for RMSI on the GSCN-Current.

[0258] In step 1110, the UE determines the GSCN-Current based on the GSCN to determine a configuration to include at least one of the frequency range determined based on the GSCN as a frequency range in which other SS / PBCH blocks configured with a PDCCH including scheduling information for RMSI are not transmitted when the SS / PBCH block is not associated with a PDCCH including scheduling information for RMSI on the GSCN-Current, or a second frequency position in which other SS / PBCH blocks configured with a PDCCH including scheduling information for RMSI are transmitted.

[0259] 12 illustrates a flowchart of a method 1200 for a BS according to an embodiment of the present disclosure. The embodiment of the method 1200 illustrated in FIG. 12 is for illustrative purposes only. FIG. 12 does not limit the scope of the present disclosure to any particular implementation.

[0260] As shown in Figure 12, method 1200 begins at step 1202. A BS (e.g., 101-103 as shown in Figure 1) generates a synchronization signal and physical broadcast channel (SS / PBCH) block at step 1202.

[0261] In one embodiment, in step 1202, the SS / PBCH block associated with the PDCCH including scheduling information for the RMSI on the determined GSCN-Current is determined as follows: for the first carrier frequency range, the ssb-SubcarrierOffset field in the PBCH content is based on a value from {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15} and ...

number

number

[0262] In one embodiment, in step 1202, the SS / PBCH block not associated with the PDCCH containing scheduling information for the RMSI on the determined GSCN-Current is a field of ssb-SubcarrierOffset in the content of the PBCH based on a value from {8, 9, 10, 11, 12, 13, 14, 15} for the first frequency range and a field of ssb-SubcarrierOffset in the content of the PBCH with a value of 1.

number

[0263] In this embodiment, the frequency range in which other SS / PBCH blocks configured with a PDCCH containing scheduling information for RMSI are not transmitted is the first carrier frequency range, where the ssb-SubcarrierOffset field in the PBCH content has a value of 15 and the ssb-SubcarrierOffset field in the PBCH content has a value of 1.

number

[0264] In such an embodiment, pdcch-ConfigSIB1 contains an 8-bit length on the contents of the PBCH.

[0265] In this embodiment, the frequency range in which other SS / PBCH blocks configured with a PDCCH containing scheduling information for RMSI are not transmitted is given by GSCN-Current when pdcch-ConfigSIB1=0.

[0266] In this embodiment, the second frequency location at which the other SS / PBCH blocks configured with the PDCCH containing scheduling information for RMSI are transmitted is the first carrier frequency range 1, where the ssb-SubcarrierOffset field in the PBCH content is based on a value from {8,9,10} and the ssb-SubcarrierOffset field in the PBCH content has a value of 1.

number

number

[0267] In this embodiment, pdcch-ConfigSIB1 is the content of the PBCH and is 8 bits in length, and the SS / PBCH block configures a PDCCH including scheduling information for the RMSI on the determined GSCN-Current, and determines the scheduling information for the RMSI based on the multiplexing pattern of the SS / PBCH block and a control resource set (CORESET) including the PDCCH, and the scheduling information for the RMSI includes at least a time domain resource allocation of the physical downlink shared channel (PDSCH) for the RMSI.

[0268] In step 1204, the BS identifies a first frequency location (GSCN-Current) based on a set of predefined synchronization rasters determined by a global synchronization channel number (GSCN) for transmitting the SS / PBCH block.

[0269] In step 1206, the BS determines, based on the GSCN-Current, a configuration for at least one of an SS / PBCH block associated with a physical downlink control channel (PDCCH) including scheduling information for RMSI (remaining minimum system information) on the GSCN-Current or an SS / PBCH block not associated with a PDCCH including scheduling information for RMSI on the GSCN-Current.

[0270] In step 1208, the BS determines a configuration to include at least one of the frequency range determined based on the GSCN as a frequency range in which other SS / PBCH blocks configured with PDCCHs including scheduling information for RMSI are not transmitted when the SS / PBCH block is not associated with a PDCCH including scheduling information for RMSI on the GSCN-Current, or a second frequency location in which other SS / PBCH blocks configured with PDCCHs including scheduling information for RMSI are transmitted, where the GSCN-Current is determined based on the GSCN.

[0271] In step 1210, the BS identifies the content of the PBCH contained in the SS / PBCH block based on the determined configuration.

[0272] In step 1212, the BS transmits an SS / PBCH block including a PBCH using GSCN-Current to a user equipment (UE) via a downlink channel.

[0273] While the present disclosure has been described in exemplary embodiments, various changes and modifications may occur to those of ordinary skill in the art, and the present disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

[0274] Nothing in this application should be construed as implying that any particular element, step, or function is essential to its inclusion in the claims. The scope of patented subject matter is defined solely by the claims. Furthermore, no claim is intended to invoke 35 U.S.C. § 112(f) without the precise words "means for" followed by a participle. [Explanation of symbols]

[0275] 130 Internet 210a RF Transceiver 210b RF Transceiver 210n RF Transceiver 215 TX processing circuit 220 RX processing circuit 225 Controller / Processor 230 Memory 235 Backhaul / Network IF 310 RF Transceiver 315 TX processing circuit 320 microphone 325 RX processing circuit 330 speakers 340 processor 350 Touchscreen 355 Display 360 Memory 362 Applications

Claims

1. A method performed by a terminal of a wireless communication system, receiving a first synchronization signal / physical broadcast channel (SS / PBCH) block from a base station; determining, based on a subcarrier offset value determined based on the first SS / PBCH block, that there is no control resource set (CORESET) for remaining minimum system information (RMSI) corresponding to the first SS / PBCH block; determining a global synchronization channel number (GSCN) value of a second SS / PBCH block having a CORESET for the RMSI based on the subcarrier offset value, or determining that the second SS / PBCH block having a CORESET for the RMSI is not within a GSCN range; In the case of FR1, when the subcarrier offset value is 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value and the subcarrier offset value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​ranging from -768 to -1 and from 1 to 768 according to the subcarrier offset value; In the case of FR1, if the subcarrier offset value is 31, the second SS / PBCH block having a CORESET for the RMSI does not exist within the GSCN range.

2. In the case of FR1, the PDCCH information is 8 bits, 2. The method of claim 1, wherein when the subcarrier offset value is 24, the GSCN offset value is designated as 1 to 256; when the subcarrier offset value is 25, the GSCN offset value is designated as 257 to 512; when the subcarrier offset value is 26, the GSCN offset value is designated as 513 to 768; when the subcarrier offset value is 27, the GSCN offset value is designated as -1 to -256; when the subcarrier offset value is 28, the GSCN offset value is designated as -257 to -512; and when the subcarrier offset value is 29, the GSCN offset value is designated as -513 to -768.

3. In the case of FR1, the PDCCH information is 8 bits, 2. The method of claim 1, wherein, when the subcarrier offset value is 31, the GSCN range is determined based on the GSCN value of the first SS / PBCH block and a value for a GSCN range indicated by the PDCCH information.

4. In the case of FR2, when the subcarrier offset value is 12 to 13, the GSCN value of the second SS / PBCH block is indicated by the GSCN value and the subcarrier offset value of the first SS / PBCH block and the PDCCH information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​ranging from -256 to -1 and from 1 to 256 depending on the subcarrier offset value; 2. The method of claim 1, wherein, in the case of FR2, if the subcarrier offset value is 15, the second SS / PBCH block having a CORESET for the RMSI does not exist in the GSCN range.

5. In the case of FR2, the PDCCH information is 8 bits, 5. The method of claim 4, wherein when the subcarrier offset value is 12, the GSCN offset value is instructed to be between 1 and 256, and when the subcarrier offset value is 13, the GSCN offset value is instructed to be between -1 and -256.

6. A method performed by a base station in a wireless communication system, comprising: transmitting a first SS / PBCH block (synchronization signal / physical broadcast channel block); If it is determined that a control resource set (CORESET) for remaining minimum system information (RMSI) corresponding to the first SS / PBCH block does not exist based on a subcarrier offset value included in the first SS / PBCH block, the subcarrier offset value indicates a global synchronization channel number (GSCN) value of a second SS / PBCH block having a CORESET for the RMSI, or indicates that the second SS / PBCH block having a CORESET for the RMSI does not exist within a GSCN range; In the case of FR1, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block, the subcarrier offset value of 24 to 29, and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​ranging from -768 to -1 and from 1 to 768 according to the subcarrier offset value; In the case of FR1, the subcarrier offset value of 31 indicates that the second SS / PBCH block having a CORESET for the RMSI is not within a GSCN range.

7. In the case of FR1, the PDCCH information is 8 bits, 7. The method of claim 6, wherein when the subcarrier offset value is 24, the GSCN offset value is designated as 1 to 256; when the subcarrier offset value is 25, the GSCN offset value is designated as 257 to 512; when the subcarrier offset value is 26, the GSCN offset value is designated as 513 to 768; when the subcarrier offset value is 27, the GSCN offset value is designated as -1 to -256; when the subcarrier offset value is 28, the GSCN offset value is designated as -257 to -512; and when the subcarrier offset value is 29, the GSCN offset value is designated as -513 to -768.

8. In the case of FR1, the PDCCH information is 8 bits, 7. The method of claim 6, wherein, when the subcarrier offset value is 31, the GSCN range is determined based on the GSCN value of the first SS / PBCH block and a value for a GSCN range indicated by the PDCCH information.

9. In the case of FR2, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block, the subcarrier offset value of 12 to 13, and the PDCCH information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​ranging from -256 to -1 and from 1 to 256 depending on the subcarrier offset value; 7. The method of claim 6, wherein in the case of FR2, the subcarrier offset value of 15 indicates that the second SS / PBCH block having a CORESET for the RMSI is not in the GSCN range.

10. In the case of FR2, the PDCCH information is 8 bits, 10. The method of claim 9, wherein when the subcarrier offset value is 12, the GSCN offset value is instructed to be between 1 and 256, and when the subcarrier offset value is 13, the GSCN offset value is instructed to be between -1 and -256.

11. In a terminal of a wireless communication system, a transmitter / receiver; receiving a first synchronization signal / physical broadcast channel (SS / PBCH) block from a base station; determining, based on a subcarrier offset value determined based on the first SS / PBCH block, that there is no control resource set (CORESET) for remaining minimum system information (RMSI) corresponding to the first SS / PBCH block; a controller configured to check a global synchronization channel number (GSCN) value of a second SS / PBCH block having a CORESET for the RMSI based on the subcarrier offset value, or to check that the second SS / PBCH block having a CORESET for the RMSI is not within a GSCN range, In the case of FR1, when the subcarrier offset value is 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value and the subcarrier offset value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​ranging from -768 to -1 and from 1 to 768 according to the subcarrier offset value; In the case of FR1, when the subcarrier offset value is 31, the second SS / PBCH block having a CORESET for the RMSI does not exist within the GSCN range.

12. In the case of FR1, the PDCCH information is 8 bits, 12. The terminal of claim 11, wherein when the subcarrier offset value is 24, the terminal indicates 1 to 256 as the GSCN offset value; when the subcarrier offset value is 25, the terminal indicates 257 to 512; when the subcarrier offset value is 26, the terminal indicates 513 to 768; when the subcarrier offset value is 27, the terminal indicates -1 to -256; when the subcarrier offset value is 28, the terminal indicates -257 to -512; and when the subcarrier offset value is 29, the terminal indicates -513 to -768.

13. In the case of FR1, the PDCCH information is 8 bits, 12. The terminal of claim 11, wherein, when the subcarrier offset value is 31, the GSCN range is determined based on the GSCN value of the first SS / PBCH block and a value for a GSCN range indicated by the PDCCH information.

14. In the case of FR2, when the subcarrier offset value is 12 to 13, the GSCN value of the second SS / PBCH block is indicated by the GSCN value and the subcarrier offset value of the first SS / PBCH block and the PDCCH information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​ranging from -256 to -1 and from 1 to 256 depending on the subcarrier offset value; The terminal of claim 11, wherein in the case of FR2, when the subcarrier offset value is 15, the second SS / PBCH block having a CORESET for the RMSI does not exist in the GSCN range.

15. In the case of FR2, the PDCCH information is 8 bits, The terminal of claim 14, wherein when the subcarrier offset value is 12, the terminal indicates a value from 1 to 256 as the GSCN offset value, and when the subcarrier offset value is 13, the terminal indicates a value from -1 to -256.

16. In a base station of a wireless communication system, a transmitter / receiver; a control unit configured to control transmission of a first SS / PBCH block (synchronization signal / physical broadcast channel block); If it is determined that a control resource set (CORESET) for remaining minimum system information (RMSI) corresponding to the first SS / PBCH block does not exist based on a subcarrier offset value included in the first SS / PBCH block, the subcarrier offset value indicates a global synchronization channel number (GSCN) value of a second SS / PBCH block having a CORESET for the RMSI, or indicates that the second SS / PBCH block having a CORESET for the RMSI does not exist within a GSCN range; In the case of FR1, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block, the subcarrier offset value of 24 to 29, and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​ranging from -768 to -1 and from 1 to 768 according to the subcarrier offset value; In the case of FR1, the subcarrier offset value of 31 indicates that the second SS / PBCH block having a CORESET for the RMSI is not within a GSCN range.

17. In the case of FR1, the PDCCH information is 8 bits, 17. The base station of claim 16, wherein when the subcarrier offset value is 24, the base station indicates a value from 1 to 256 as the GSCN offset value; when the subcarrier offset value is 25, the base station indicates a value from 257 to 512; when the subcarrier offset value is 26, the base station indicates a value from 513 to 768; when the subcarrier offset value is 27, the base station indicates a value from -1 to -256; when the subcarrier offset value is 28, the base station indicates a value from -257 to -512; and when the subcarrier offset value is 29, the base station indicates a value from -513 to -768.

18. In the case of FR1, the PDCCH information is 8 bits, 17. The base station of claim 16, wherein, when the subcarrier offset value is 31, the GSCN range is determined based on the GSCN value of the first SS / PBCH block and a value for the GSCN range indicated by the PDCCH information.

19. In the case of FR2, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block, the subcarrier offset value of 12 to 13, and the PDCCH information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​ranging from -256 to -1 and from 1 to 256 depending on the subcarrier offset value; 17. The base station of claim 16, wherein in the case of FR2, the subcarrier offset value of 15 indicates that the second SS / PBCH block having a CORESET for the RMSI does not exist in the GSCN range.

20. In the case of FR2, the PDCCH information is 8 bits, 20. The base station of claim 19, wherein when the subcarrier offset value is 12, the base station indicates a value from 1 to 256 as the GSCN offset value, and when the subcarrier offset value is 13, the base station indicates a value from -1 to -256.

Images