Method and apparatus for receiving RMSI from neighboring cells

By calculating the frequency domain offset between Type0-PDCCH and SS/PBCH blocks in the 5G communication system, the difficulty of receiving RMSI from neighboring cells is solved and the channel reception efficiency is improved.

CN114208294BActive Publication Date: 2024-11-15SAMSUNG ELECTRONICS CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202080055131.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-07-30
Filing Date
2020-08-28
Publication Date
2024-11-15
Estimated Expiration
2040-08-28

AI Technical Summary

Technical Problem

In 5G communication systems, it is difficult for the prior art to effectively receive RMSI (remain minimum system information) from neighboring cells, especially when the SS/PBCH block is not on the synchronous grid entry, resulting in inefficient channel reception.

Method used

By detecting the synchronization signal and the physical broadcast channel block (SS/PBCH block), the user equipment (UE) calculates between the Type0-PDCCH control resource set (CORESET) and the SS/PBCH block when the frequency position does not correspond to the synchronization raster entry. The frequency domain offset is determined by the sum of the first offset and the second offset. The first offset is configured by the main information block (MIB) in the SS/PBCH block, and the second offset is based on the SS/PBCH block. The frequency difference between the block and the synchronous raster entry.

Benefits of technology

The ability to receive RMSI from neighboring cells is improved, the accuracy and efficiency of channel reception is enhanced, and the reception difficulty problem of SS/PBCH blocks not located on synchronous grid entries is solved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114208294B_ABST
    Figure CN114208294B_ABST
Patent Text Reader

Abstract

A method and apparatus for a UE in a wireless communication system supporting shared spectrum channel access are provided. The method and apparatus include: detecting a synchronization signal and a physical broadcast channel block (SS / PBCH block); and determining an offset between a control resource set CORESET for Type0-PDCCH and the SS / PBCH block as a sum of a first offset and a second offset when the frequency position of the detected SS / PBCH block does not correspond to the frequency position of a synchronization grid entry, wherein the first offset is configured by a master information block MIB in the detected SS / PBCH block, and wherein the second offset is determined based on a frequency difference between the frequency position of the detected SS / PBCH block and the frequency position of the synchronization grid entry.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates generally to wireless communication systems, and more particularly, to receiving RMSI from neighboring cells. Background Art

[0002] The communication system includes a downlink (DL) that transmits signals from a transmission point such as a base station (BS) or NodeB to a user equipment (UE) and an uplink (UL) that transmits signals from the UE to a reception 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 computer device, or an automatic device. An eNodeB (eNB) referring to a NodeB in a long term evolution (LTE) communication system and a gNodeB (gNB) referring to a NodeB in a new radio (NR) communication system may also be referred to as an access point or other equivalent terms.

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

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

[0005] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud RAN, which is the above-mentioned big data processing technology, can also be considered as an example of the fusion between 5G technology and IoT technology.

[0006] As described above, according to the development of wireless communication systems, various services can be provided, and thus a method for easily providing these services is required. Summary of the invention

[0007] Technical solutions to the problem

[0008] The present disclosure relates to a quasi-5G or 5G communication system that provides for receiving RMSI from neighboring cells.

[0009] In one embodiment, a method performed by a user equipment UE in a wireless communication system is provided. The method includes: detecting a synchronization signal and a physical broadcast channel block (SS / PBCH block); and when the frequency position of the detected SS / PBCH block does not correspond to the frequency position of a synchronization raster entry, determining an offset between a control resource set CORESET for Type0-PDCCH and the SS / PBCH block as the sum of a first offset and a second offset, wherein the first offset is configured by a master information block MIB in the detected SS / PBCH block, and wherein the second offset is determined based on a frequency difference between the frequency position of the detected SS / PBCH block and the frequency position of the synchronization raster entry. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0014] Figure 4 An example transmitter structure using OFDM according to an embodiment of the present disclosure is shown;

[0015] Figure 5 An example receiver structure using OFDM according to an embodiment of the present disclosure is shown;

[0016] Figure 6 An example encoding process for a DCI format according to an embodiment of the present disclosure is shown;

[0017] Figure 7 An example decoding process for a DCI format for a UE according to an embodiment of the present disclosure is shown;

[0018] Figure 8 shows an example frequency domain offset between SS / PBCH blocks and CORESET#0 according to an embodiment of the present disclosure;

[0019] Fig. 9 A flow chart showing a UE process for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure;

[0020] Fig. 10A A flow chart showing a UE process for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure;

[0021] Fig. 10B A flow chart showing a UE process for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure;

[0022] Fig.11 shows an example relationship between frequency offsets according to an embodiment of the present disclosure;

[0023] Fig.12 shows an example SS / PBCH block with an SCS of 30 kHz and an SCS of 15 kHz at the same reference frequency location according to an embodiment of the present disclosure;

[0024] Fig.13 shows example SS / PBCH blocks with an SCS of 30 kHz and an SCS of 15 kHz at different reference frequency locations according to an embodiment of the present disclosure;

[0025] Fig.14 A flow chart showing a UE process for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure;

[0026] Fig.15A A flow chart showing a UE process for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure;

[0027] Fig. 15B Another flow chart of a UE process for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure is shown;

[0028] Fig.16 A flow chart showing a UE process for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure;

[0029] Fig.17 A flow chart of a method for RMSI reception according to an embodiment of the present disclosure is shown;

[0030] Fig.18 A user equipment UE according to an embodiment of the present disclosure is shown; and

[0031] Fig.19 A base station BS according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0032] In one embodiment, a method performed by a user equipment UE in a wireless communication system is provided. The method includes: detecting a synchronization signal and a physical broadcast channel block (SS / PBCH block); and when the frequency position of the detected SS / PBCH block does not correspond to the frequency position of a synchronization grid entry, determining an offset between a control resource set CORESET for Type0-PDCCH and the SS / PBCH block as the sum of a first offset and a second offset, wherein the first offset is configured by a master information block MIB in the detected SS / PBCH block, and wherein the second offset is determined based on a frequency difference between the frequency position of the detected SS / PBCH block and the frequency position of the synchronization grid entry.

[0033] In an embodiment, the offset is the frequency difference between the lowest resource block RB of the CORESET for Type0-PDCCH and the lowest RB of the SS / PBCH block.

[0034] In an embodiment, the method further comprises, in case the frequency position of the detected SS / PBCH block corresponds to the frequency position of the synchronization grid entry, determining the offset as a first offset.

[0035] In an embodiment, the synchronization grid entries are located in the same carrier as the SS / PBCH blocks.

[0036] In an embodiment, the offset is from the minimum resource block RB index of the CORESET for Type0-PDCCH to the minimum RB index of the common RB overlapping with the first RB of the SS / PBCH block.

[0037] In an embodiment, the second offset is determined based on an offset from a minimum resource block RB index of a common RB overlapping with a first RB of a SS / PBCH block to a minimum RB index of a common RB overlapping with a first RB of another SS / PBCH block assumed to be located at a frequency position of a synchronization grid entry.

[0038] In an embodiment, the frequency position of a synchronization grid entry is the global synchronization channel number GSCN of the synchronization grid entry.

[0039] In an embodiment, the method further comprises receiving, from the base station, a higher layer parameter ssbFrequency comprising a frequency location of the SS / PBCH block.

[0040] In an embodiment, the first offset and the second offset are defined for the subcarrier spacing SCS of the CORESET for Type0-PDCCH.

[0041] In one embodiment, a user equipment (UE) in a wireless communication system is provided. The UE includes: a transceiver; and at least one processor, the at least one processor is operably connected to the transceiver, and the at least one processor is configured to: detect a synchronization signal and a physical broadcast channel block (SS / PBCH block), and when the frequency position of the detected SS / PBCH block does not correspond to the frequency position of a synchronization grid entry, determine the offset between the control resource set CORESET for Type0-PDCCH and the SS / PBCH block as the sum of a first offset and a second offset, wherein the first offset is configured by a master information block MIB in the detected SS / PBCH block, and wherein the second offset is determined as a frequency difference between the frequency position of the detected SS / PBCH block and the frequency position of the synchronization grid entry.

[0042] In one embodiment, a user equipment (UE) in a wireless communication system supporting shared spectrum channel access is provided. The UE includes a processor configured to identify the frequency position of a synchronization signal and physical broadcast channel (SS / PBCH) block, and a transceiver operably connected to the processor, the transceiver configured to receive the SS / PBCH block from a base station (BS). The processor of the UE is also configured to: determine whether the frequency position of the SS / PBCH block corresponds to the global synchronization channel number (GSCN) of the synchronization grid entry; if the frequency position of the SS / PBCH block does not correspond to the GSCN of the synchronization grid entry, the offset is determined as the sum of the first offset and the second offset, and the offset is the difference from the minimum resource block (RB) index of the control resource set (CORESET) of the common search space (CSS) set for the Type0 physical downlink control channel (Type0-PDCCH) to the minimum RB index of the common RB overlapping with the first RB of the SS / PBCH block.

[0043] In an embodiment, the processor is further configured to identify the offset as a first offset if the frequency position of the SS / PBCH block corresponds to a GSCN of the synchronization grid entry.

[0044] In an embodiment, the transceiver is further configured to receive a higher layer parameter including ssbFrequency of the frequency location of the SS / PBCH block from the BS via a higher layer signal if the frequency location of the SS / PBCH block does not correspond to the GSCN of the synchronization grid entry.

[0045] In an embodiment, the transceiver is further configured to receive the first offset from the BS via a field of controlResourceSetZero included in a master information block (MIB) of the SS / PBCH block.

[0046] In an embodiment, the processor is further configured to identify a second offset determined as an offset from a minimum RB index of a common RB overlapping with a first RB of a SS / PBCH block to a minimum RB index of a common RB overlapping with a first RB of another SS / PBCH block assumed to be located at a GSCN of a synchronization grid entry.

[0047] In an embodiment, the synchronization grid entry is determined as a single entry within a bandwidth for shared spectrum channel access operation; and the bandwidth includes SS / PBCH blocks.

[0048] In an embodiment, the first offset, the second offset, and the SS / PBCH block assumed to be located at the GSCN of the synchronization grid entry are identified based on the subcarrier spacing of the CORESET for the Type0-PDCCH CSS set.

[0049] In another embodiment, a base station (BS) in a wireless communication system supporting shared spectrum channel access is provided. The BS includes: a transceiver configured to send a synchronization signal and physical broadcast channel (SS / PBCH) block to a user equipment (UE), wherein the frequency position of the SS / PBCH block is identified; determining whether the frequency position of the SS / PBCH block corresponds to a global synchronization channel number (GSCN) of a synchronization grid entry; if the frequency position of the SS / PBCH block does not correspond to the GSCN of the synchronization grid entry, determining an offset as the sum of a first offset and a second offset; and the offset is a difference from a minimum resource block (RB) index of a control resource set (CORESET) for a Type0 physical downlink control channel (Type0-PDCCH) common search space (CSS) set to a minimum RB index of a common RB overlapping with a first RB of the SS / PBCH block.

[0050] In an embodiment, if the frequency position of the SS / PBCH block corresponds to the GSCN of the synchronization grid entry, the offset is determined as the first offset.

[0051] In an embodiment, the transceiver is further configured to send a higher layer parameter of ssbFrequency including the frequency location of the SS / PBCH block to the UE via a higher layer signal if the frequency location of the SS / PBCH block does not correspond to the GSCN of the synchronization grid entry.

[0052] In an embodiment, the transceiver is further configured to send the first offset to the UE via a field of controlResourceSetZero included in a master information block (MIB) of the SS / PBCH block.

[0053] In an embodiment, a second offset is identified, which is determined as an offset from the minimum RB index of a common RB overlapping with the first RB of an SS / PBCH block to the minimum RB index of a common RB overlapping with the first RB of another SS / PBCH block assumed to be located at the GSCN of the synchronization grid entry.

[0054] In an embodiment, the synchronization grid entry is determined as a single entry within a bandwidth for shared spectrum channel access operation; and the bandwidth includes SS / PBCH blocks.

[0055] In an embodiment, the first offset, the second offset, and the SS / PBCH block assumed to be located at the GSCN of the synchronization grid entry are identified based on the subcarrier spacing of the CORESET for the Type0-PDCCH CSS set.

[0056] In yet another embodiment, a method for a user equipment (UE) in a wireless communication system supporting shared spectrum channel access is provided. The method includes: identifying a frequency position of a synchronization signal and physical broadcast channel (SS / PBCH) block; receiving the SS / PBCH block from a base station (BS); determining whether the frequency position of the SS / PBCH block corresponds to a global synchronization channel number (GSCN) of a synchronization grid entry; and if the frequency position of the SS / PBCH block does not correspond to the GSCN of the synchronization grid entry, determining an offset as the sum of a first offset and a second offset, wherein the offset is a difference from a minimum resource block (RB) index of a control resource set (CORESET) for a Type0 physical downlink control channel (Type0-PDCCH) common search space (CSS) set to a minimum RB index of a common RB overlapping with a first RB of the SS / PBCH block.

[0057] In an embodiment, the method further comprises identifying the offset as a first offset based on a frequency position of the SS / PBCH block corresponding to a GSCN of the synchronization grid entry.

[0058] In an embodiment, the method further comprises, based on the frequency position of the SS / PBCH block not corresponding to the GSCN of the synchronization grid entry, receiving a higher layer parameter of ssbFrequency including the frequency position of the SS / PBCH block from the BS via a higher layer signal.

[0059] In an embodiment, the method further includes receiving the first offset from the BS via a field of controlResourceSetZero included in a master information block (MIB) of the SS / PBCH block.

[0060] In an embodiment, the method also includes identifying a second offset, which is determined as an offset from a minimum RB index of a common RB overlapping with a first RB of a SS / PBCH block to a minimum RB index of a common RB overlapping with a first RB of another SS / PBCH block assumed to be located at a GSCN of a synchronization grid entry, wherein: the synchronization grid entry is determined as a single entry within a bandwidth for shared spectrum channel access operations; and the bandwidth includes the SS / PBCH blocks.

[0061] In an embodiment, the first offset, the second offset, and the SS / PBCH block assumed to be located at the GSCN of the synchronization grid entry are identified based on the subcarrier spacing of the CORESET for the Type0-PDCCH CSS set.

[0062] Other technical features may be clear to those skilled in the art from the following drawings, descriptions and claims.

[0063] Before the following detailed description, it may be advantageous to set forth the definitions of specific words and phrases used throughout this patent document. The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives include both direct and indirect communication. The terms "include" and "comprise" and their derivatives refer to inclusion and not limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives refer to including, being included, interconnected with..., including, being included, connected to... or connected with..., coupled to... or coupled with..., communicable with..., collaborative with..., intertwined, juxtaposed, adjacent, coupled to... or combined with..., having, having... properties, having a relationship with..., etc. The term "controller" refers to any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware. The functions associated with any particular controller can be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items may be used, and only one of the items in the list may be needed. For example, "at least one of A, B, and C" includes any combination of A, B, C, A and B, A and C, B and C, and A and B and C.

[0064] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and is embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or parts thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media such as rewritable optical disks or erasable memory devices in which data can be stored and then overwritten.

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

[0066] Wireless communication systems have evolved from providing initial voice-oriented services to broadband wireless communication systems that provide high-speed and high-quality packet data services, such as High Speed ​​Packet Access (HSPA); Long Term Evolution (LTE) of 3GPP or Evolved Universal Terrestrial Radio Access (E-UTRA) of 3GPP, and LTE-Advanced (LTE-A) of 3GPP; High Speed ​​Packet Data (HRPD) and Ultra Mobile Broadband (UMB) of 3GPP2, and communication standards such as IEEE 802.16e. The fifth generation (5G) or new radio (NR) communication standard is being developed together with the 5G wireless communication system.

[0067] Hereinafter, one or more embodiments will be described with reference to the accompanying drawings. In addition, in the description of the present disclosure, when it is considered that a specific detailed explanation of a related function or configuration may unnecessarily obscure the essence of the present disclosure, these detailed explanations are omitted. All terms including descriptive or technical terms used herein should be interpreted as having meanings that are obvious to those of ordinary skill in the art. However, according to the intention of those of ordinary skill in the art, precedents, or the emergence of new technologies, these terms may have different meanings, and therefore, the terms used herein must be defined based on the meanings of these terms and the descriptions throughout the specification. Hereinafter, a base station may be a subject that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, a multimedia system capable of performing a communication function, and the like. In the present disclosure, DL is a wireless transmission path for a signal sent from a base station to a terminal, and UL is a wireless transmission path for a signal sent from a terminal to a base station. Throughout the specification, a layer (or layer device) may also be referred to as an entity. In addition, hereinafter, one or more embodiments of the present disclosure will be described as examples of LTE or LTE-A systems, but the one or more embodiments may also be applied to other communication systems with similar technical backgrounds or channel forms. For example, 5G mobile communication technology (5G, New Radio (NR)) developed after LTE-A may be included. In addition, according to those skilled in the art, without departing from the scope of the present disclosure, one or more embodiments may be applied to other communication systems through some modifications within the scope of the present disclosure.

[0068] In the LTE system, which is a representative example of a broadband wireless communication system, an orthogonal frequency division multiplexing (OFDM) scheme is used in DL, and a single carrier frequency division multiplexing (SC-FDMA) scheme is used in UL. UL refers to a wireless link through which a terminal, UE, or MS sends data or a control signal to a BS or a gNode B, and DL refers to a wireless link through which a BS sends data or a control signal to a terminal. In this multiple access scheme, data or control information of each user is classified by generally allocating and operating the data or control information so that the time-frequency resources used to send the data or control information of each user do not overlap with each other, that is, orthogonality is established.

[0069] Terms such as physical channels and signals in existing LTE or LTE-A systems may be used to describe the methods and apparatuses proposed in the present disclosure. However, the content of the present disclosure is applied to wireless communication systems, not LTE or LTE-A systems.

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

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

[0072] The following Figure 1-Figure 3 Various embodiments are described that are implemented in a wireless communication system and implemented using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. Figure 1-Figure 3 The description is not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

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

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

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

[0076] Depending on the network type, the term "base station" or "BS" may refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eBN), a 5G base station (gNB), a macro cell, a femto cell, a WiFi access point (AP), or other wireless-enabled devices. The base station may provide wireless access according to one or more wireless communication protocols (e.g., 5G 3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.). For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. In addition, depending on the network type, the term "user equipment" or "UE" may refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "reception point", or "user device". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).

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

[0078] As described in more detail below, one or more of the UEs 111-116 include circuits, procedures, or a combination thereof for reception reliability of data and control information in an advanced wireless communication system. In certain embodiments, one or more of the gNBs 101-103 include circuits, procedures, or a combination thereof for efficiently receiving RMSI from neighboring cells.

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

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

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

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

[0083] The TX processing circuit 215 receives analog or digital data (such as voice data, web page data, email, or interactive video game data) from the controller / processor 225. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceivers 210a-210n receive the outgoing processed baseband or IF signal from the TX processing circuit 215 and up-convert the baseband or IF signal to an RF signal that is transmitted via the antennas 205a-205n.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0097] although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. As a specific example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE may be configured to operate as other types of mobile or stationary devices.

[0098] The present disclosure relates generally to wireless communication systems, and more particularly to reducing power consumption of a user equipment (UE) communicating with a base station, and to operating with dual connectivity by transmitting a physical downlink control channel (PDCCH) to and receiving a physical downlink control channel from the UE. The communication system includes a downlink (DL) referring to transmissions from a base station or one or more transmission points to a UE and an uplink (UL) referring to transmissions from a UE to a base station or one or more reception points.

[0099] In order to meet the demand for wireless data traffic that has increased since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60GHz bands) in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed for 5G communication systems. In addition, in 5G communication systems, development of system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoint (CoMP), receiving-end interference elimination, etc. is underway.

[0100] The time unit for DL ​​signaling or UL signaling on a cell is called a time slot and may include one or more symbols. Symbols may also be used as additional time units. The frequency (or bandwidth (BW)) unit is called a resource block (RB). An RB includes multiple subcarriers (SC). For example, a time slot may include 14 symbols with a duration of 1 ms or 0.5 ms, and an RB may have a BW of 180 kHz or 360 kHz and include 12 SCs with a spacing of 15 kHz or 30 kHz, respectively.

[0101] DL signals include data signals that convey information content, control signals that convey DL control information (DCI) formats, and reference signals (RS) also known as pilot signals. The gNB can send data information (e.g., transport blocks) or DCI formats through the corresponding physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). The gNB can send one or more of multiple types of RS including channel state information RS (CSI-RS) and demodulation RS (DMRS). CSI-RS is intended for UEs to measure channel state information (CSI) or perform other measurements (such as measurements related to mobility support). DMRS can only be sent in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0102] The UL signal also includes a data signal that transmits information content, a control signal that transmits UL control information (UCI), and an RS. The UE transmits data information (e.g., transport block) or UCI through a corresponding physical UL shared channel (PUSCH) or a physical UL control channel. When the UE transmits data information and UCI simultaneously, the UE may multiplex both the data information and the UCI in the PUSCH, or transmit the data information and the UCI separately in the corresponding PUSCH and PUCCH. The UCI includes hybrid automatic repeat request acknowledgement (HARQ-ACK) information indicating correct or incorrect detection of a data transport block (TB) by the UE, a scheduling request (SR) indicating whether the UE has data in the buffer of the UE, and a CSI report that enables the gNB to select appropriate parameters to perform link adaptation for PDSCH or PDCCH transmission to the UE.

[0103] The CSI report from the UE may include: a channel quality indicator (CQI), which informs the gNB of the modulation and coding scheme (MCS) used for the UE to detect data TBs with a predetermined block error rate (BLER) (such as 10% BLER); a precoding matrix indicator (PMI), which informs the gNB how to precode the signaling to the UE; and a rank indicator (RI), which indicates the transmission rank for the PDSCH. The UL RS includes a DMRS and a sounding RS (SRS). The DMRS is transmitted only in the BW of the corresponding PUSCH or PUCCH transmission. The gNB can use the DMRS to demodulate the information in the corresponding PUSCH or PUCCH. The SRS is sent by the UE to provide the gNB with UL CSI and, for TDD or flexible duplex systems, also provides the PMI for DL ​​transmissions. The UL DMRS or SRS transmission may be based on, for example, a Zadoff-Chu (ZC) sequence, or generally based on a CAZAC sequence.

[0104] DL and UL transmissions may be based on an Orthogonal Frequency Division Multiplexing (OFDM) waveform including a variant using DFT precoding known as DFT-spread-OFDM.

[0105] Figure 4 An example transmitter structure 400 using OFDM is shown according to an embodiment of the present disclosure. Figure 4 The illustrated embodiment of transmitter structure 400 is for illustration only. Figure 4 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0106] The information bits 410 such as DCI bits or data bits are encoded by the encoder 420, rate matched to the allocated time / frequency resources by the rate matcher 430, and modulated by the modulator 440. Subsequently, the modulated coded symbols and DMRS or CSI-RS 450 are mapped to the SC 460 by the SC mapping unit 460, inverse fast Fourier transform (IFFT) is performed by the filter 470, a cyclic prefix (CP) is added by the CP insertion unit 480, and the resulting signal is filtered by the filter 480 and transmitted by the radio frequency (RF) unit 490.

[0107] Figure 5 An example receiver structure 500 using OFDM is shown according to an embodiment of the present disclosure. Figure 5 The illustrated embodiment of receiver structure 500 is for illustration only. Figure 5 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0108] The received signal 510 is filtered by a filter 520, a CP removal unit removes the CP 530, a filter 540 applies a fast Fourier transform (FFT), an SC demapping unit 550 demaps the SC selected by the BW selector unit 555, the received symbols are demodulated by a channel estimator and demodulator unit 560, a rate dematcher 570 restores rate matching, and a decoder 580 decodes the resulting bits to provide information bits 590.

[0109] The UE typically monitors multiple candidate locations for corresponding potential PDCCH transmissions to decode multiple candidate DCI formats in a time slot. Monitoring PDCCH candidates means receiving and decoding PDCCH candidates according to the DCI format that the UE is configured to receive. The DCI format includes cyclic redundancy check (CRC) bits so that the UE confirms the correct detection of the DCI format. The DCI format type is identified by a radio network temporary identifier (RNTI) that scrambles the CRC bits. For DCI formats that schedule PDSCH or PUSCH for a single UE, the RNTI can be a cell RNTI (C-RNTI) and is used as a UE identifier.

[0110] For a DCI format that schedules a PDSCH that conveys system information (SI), the RNTI may be an SI-RNTI. For a DCI format that schedules a PDSCH that provides a random access response (RAR), the RNTI may be an RA-RNTI. For a DCI format that schedules a PDSCH or PUSCH for a single UE before the UE establishes a radio resource control (RRC) connection with the serving gNB, the RNTI may be a temporary C-RNTI (TC-RNTI). For a DCI format that provides TPC commands for a group of UEs, the RNTI may be a TPC-PUSCH-RNTI or a TPC-PUCCH-RNTI. Each RNTI type may be configured to the UE via higher layer signaling, such as RRC signaling. A DCI format that schedules PDSCH transmissions to a UE is also referred to as a DL DCI format or DL ​​allocation, while a DCI format that schedules PUSCH transmissions from a UE is also referred to as a UL DCI format or UL grant.

[0111] The PDCCH transmission may be within a physical RB (PRB) set. The gNB may configure one or more PRB sets (also referred to as control resource sets) for the UE for PDCCH reception. The PDCCH transmission may be in a control channel element (CCE) included in the control resource set. The UE determines the CCE for PDCCH reception based on a search space such as a UE-specific search space (USS) for PDCCH candidates in a DCI format with a CRC scrambled by an RNTI such as C-RNTI (configured to the UE via UE-specific RRC signaling for scheduling PDSCH reception or PUSCH transmission) and a common search space (CSS) for PDCCH candidates in a DCI format with a CRC scrambled by other RNTIs. The set of CCEs that may be used for PDCCH transmission to the UE defines the PDCCH candidate locations. An attribute of the control resource set is a transmission configuration indication (TCI) state that provides quasi-location information of the DMRS antenna ports for PDCCH reception.

[0112] Figure 6 An example encoding process 600 for a DCI format according to an embodiment of the present disclosure is shown. Figure 6 The illustrated embodiment of encoding process 600 is for illustration only. Figure 6 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0113] The gNB encodes and sends each DCI format separately in the corresponding PDCCH. The RNTI masks the CRC of the DCI format codeword to enable the UE to identify the DCI format. For example, the CRC and RNTI may include, for example, 16 bits or 24 bits. A CRC calculation unit 620 is used to determine the CRC of the (unencoded) DCI format bits 610, and an exclusive OR (XOR) operation unit 630 between the CRC bits and the RNTI bits 640 is used to mask the CRC. The XOR operation is defined as XOR(0,0)=0, XOR(0,1)=1, XOR(1,0)=1, XOR(1,1)=0. The masked CRC bits are attached to the DCI format information bits using a CRC attachment unit 650. The encoder 660 performs channel coding (such as tail-biting convolutional coding or polar coding), followed by rate matching of the allocated resources by a rate matcher 670. Interleaving and modulation unit 680 applies interleaving and modulation (such as QPSK), and an output control signal 690 is transmitted.

[0114] Figure 7 An example decoding process 700 for a DCI format for a UE according to an embodiment of the present disclosure is shown. Figure 7 The illustrated embodiment of decoding process 700 is for illustration only. Figure 7 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0115] The received control signal 710 is demodulated and deinterleaved by a demodulator and deinterleaver 720. The rate matching applied at the gNB transmitter is recovered by a rate matcher 730 and the resulting bits are decoded by a decoder 740. After decoding, a CRC extractor 750 extracts the CRC bits and provides DCI format information bits 760. The DCI format information bits are demasked 770 by an XOR operation with the RNTI 780 (when applicable) and a CRC check is performed by a unit 790. When the CRC check succeeds (checksum is zero), the DCI format information bits are considered valid. When the CRC is not successful, the DCI format information bits are considered invalid.

[0116] In the New Radio (NR) standard, the remaining minimum system information (RMSI) is configured to be monitored by the master system information (MIB) in the cell-defined synchronization signal and physical broadcast channel block (SS / PBCH block). The UE first obtains the frequency domain offset between the detected SS / PBCH block and the control resource set (CORESET) #0 by reading the content of the PBCH, where CORESET #0 contains the frequency domain resources of the physical downlink control channel (PDCCH) for monitoring the scheduling RMSI.

[0117] The configuration of the frequency domain offset between the SS / PBCH block and CORESET#0 is designed based on the assumption that the SS / PBCH block is located on the synchronization grid entry, which means that the configuration of the offset between the SS / PBCH block and CORESET#0 may not be applicable to the SS / PBCH block that is not located on the synchronization grid entry in NRRel-15.

[0118] In NR Rel-16, there is a motivation to read RMSI from a neighboring cell to resolve the confusion of the Cell Global Identity (CGI), where the neighboring cell may be a secondary cell (SCell) so that the SS / PBCH blocks in the neighboring cell may or may not be located on the synchronization grid entry, which gives the motivation to enhance the reception of RMSI in NR Rel-16.

[0119] Figure 8 An example frequency domain offset 800 between SS / PBCH blocks and CORESET #0 is shown according to an embodiment of the present disclosure. Figure 8 The illustrated embodiment of frequency domain offset 800 is for illustration only. Figure 8 One or more of the components shown may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors that execute instructions to perform the functions. Other embodiments may be used without departing from the scope of the present disclosure.

[0120] Figure 8 The frequency domain offset between SS / PBCH blocks and CORESET#0 in NR Rel-15 is shown.

[0121] The present disclosure focuses on mechanisms and methods to support a UE to receive Remaining Minimum System Information (RMSI) from a neighboring cell, for example, where the associated SS / PBCH block is not located on a synchronization grid entry. If the associated SS / PBCH block is located on a synchronization grid entry, the NR Rel-15 determination method can be reused, i.e., the UE determines the offset based on the MIB of the associated SS / PBCH block.

[0122] In one embodiment, the UE may be configured by the gNB to monitor Type0-PDCCH and decode the corresponding PDSCH of RMSI upon successful decoding of Type0-PDCCH in the cell.

[0123] In one example, the UE may be configured with at least a frequency location of a SS / PBCH block where the Type0-PDCCH and the corresponding RMSI are quasi-co-located with the SS / PBCH block. For example, this example is applicable to a scenario where the UE is configured by the gNB to read (e.g., from a neighboring cell) the content of the RMSI.

[0124] In one example, in addition to the frequency location of the configured SS / PBCH blocks, the subcarrier spacing (SCS) of the SS / PBCH blocks is also configured to the UE.

[0125] In another example, in addition to the configured frequency location of the SS / PBCH block, if the frequency location does not correspond to a synchronization grid entry, the SCS of the SS / PBCH block is also configured to the UE.

[0126] In yet another example, the SCS of the SS / PBCH block is not configured to the UE, and the UE blindly detects the SCS of the SS / PBCH block (eg, between 15 kHz and 30 kHz).

[0127] In yet another example, in addition to the frequency position of the configured SS / PBCH block, a frequency offset is also configured to the UE, where the frequency offset can be used by the UE to determine the frequency domain difference between the lowest RB of the SS / PBCH block and the lowest RB of CORESET#0.

[0128] In yet another example, in addition to the configured frequency position of the SS / PBCH block, a second frequency position is also configured to the UE, wherein the second frequency position can be used by the UE as a reference frequency position to determine the frequency domain difference between the lowest RB of the SS / PBCH block and the lowest RB of CORESET#0. In one aspect, the second frequency position can be a synchronization grid entry (e.g., defined by a GSCN value).

[0129] In one example, the UE can determine a frequency domain offset (e.g., represented as 0) based on the MIB of the detected SS / PBCH block, and the UE can determine that the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block is the same as the determined frequency domain offset (e.g., O).

[0130] In one example, the frequency domain difference between the lowest RB of the SS / PBCH block and the lowest RB of CORESET#0 is directly configured to the UE (eg, via the MIB), regardless of whether the SS / PBCH block is located on a synchronization grid entry.

[0131] In another instance, the frequency offset can potentially be jointly encoded with other configurations in the MIB for the UE to determine the frequency domain difference between the lowest RB of the SS / PBCH block and the lowest RB of CORESET#0, and the candidate values ​​of the frequency offset to be configured can be divided into 2 groups: one group corresponding to SS / PBCH blocks located on the synchronization grid entry, and the other group corresponding to SS / PBCH blocks not located on the synchronization grid entry.

[0132] In yet another example, the first set of offsets is applicable only to a primary cell (PCell) and / or a primary secondary cell (PSCell), for example, only for initial cell search purposes. In yet another example, the second set of offsets may be applicable to any cell (eg, one of a PCell, SCell, or PSCell).

[0133] Fig. 9 A flow chart of a UE process 900 for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure is shown. Fig. 9 The illustrated embodiment of UE process 900 is for illustration only. Fig. 9 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0134] like Fig. 9 As shown, the UE process 900 starts at step 901. In step 901, the UE determines the frequency position of the SS / PBCH block. In step 902, the UE detects the SS / PBCH block. In step 903, the UE obtains the configuration of the frequency domain offset according to the MIB. Finally, in step 904, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the obtained frequency domain offset.

[0135] In one example, there may be two candidate frequency offset values. For one example, if the detected SS / PBCH block is on a synchronization grid entry, one of the frequency offset values ​​(e.g., 0) is used, and if the detected SS / PBCH block is not on the synchronization grid entry, another frequency offset value (e.g., BW_CORESET-BW_SSB) is used. For another example, if the detected SS / PBCH block is on the synchronization grid entry or within a small range from the synchronization grid entry, one of the frequency offset values ​​(e.g., 0 RBs) is used, otherwise another frequency offset value (e.g., BW_CORESET-BW_SSB) is used.

[0136] In one example, BW_CORESET is the bandwidth of CORESET#0, e.g., 48 RBs for SCS of 30 kHz or 96 RBs for SCS of 15 kHz, and BW_SSB is the bandwidth of the SS / PBCH block, e.g., 20 RBs.

[0137] In one instance, the UE may read the MIB to obtain the configuration of the offset from a configuration table, where the table is common regardless of whether the SS / PBCH block is on a synchronization grid entry or not, and is determined by a combination of the SCS of the SS / PBCH block and the SCS of CORESET#0.

[0138] Table 1 shows an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 30kHz. In one aspect, for example, during the initial cell search process, only configurations with indices 0 and 2 are expected by the UE on the PCell and / or PSCell. Table 1 is an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 30kHz.

[0139]

Table 1

[0140]

[0141] Table 2 shows an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz. In one aspect, only configurations with indices 0 and 2 are expected by the UE on the PCell and / or PSCell (e.g., during the initial cell search process). Table 2 is an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz.

[0142]

Table 2

[0143]

[0144] In one instance, the UE may read the MIB to obtain the configuration of the offset from a configuration table, where the table is defined separately for whether the SS / PBCH block is located on a synchronization grid entry (or within range of a synchronization grid entry) and is determined by a combination of the SCS of the SS / PBCH block and the SCS of CORESET#0.

[0145] For a sub-example, for an SS / PBCH block located on the synchronization grid (or within range of a synchronization grid entry), when the SCS of the SS / PBCH block and the SCS of CORESET#0 are both 30kHz, the example configuration table in the MIB is Table 1 with only row indices 0 and 2.

[0146] For another sub-example, for an SS / PBCH block located outside the synchronization grid (or out of range from a synchronization grid entry), when the SCS of the SS / PBCH block and the SCS of CORESET#0 are both 15kHz, the example configuration table in the MIB is Table 1 with only row indices 1 and 3.

[0147] For another sub-example, for an SS / PBCH block located on the synchronization grid (or within range of a synchronization grid entry), when the SCS of the SS / PBCH block and the SCS of CORESET#0 are both 15kHz, the example configuration table in the MIB is Table 2 with only row indices 0 and 2.

[0148] For another sub-example, for an SS / PBCH block located outside the synchronization grid (or outside the range of a synchronization grid entry), when the SCS of the SS / PBCH block and the SCS of CORESET#0 are both 15kHz, the example configuration table in the MIB is Table 2 with only row indices 1 and 3.

[0149] In another example, there may be more than two candidate frequency offset values. For one example, if the detected SS / PBCH block is on a synchronization grid entry, at least one of the frequency offset values ​​(e.g., 0 RBs) may be used, and if the detected SS / PBCH block is not on the synchronization grid entry, at least one of the remaining frequency offset values ​​may be used. For another example, if the detected SS / PBCH block is within range of the synchronization grid entry, at least one of the frequency offset values ​​(e.g., 0 RBs) may be used, and if the detected SS / PBCH block is out of range of the synchronization grid entry, at least one of the remaining frequency offset values ​​may be used.

[0150] In one instance, the configuration table in the MIB is common regardless of whether the SS / PBCH block is located on (or within range of) a synchronization grid entry, and is determined by a combination of the SCS of the SS / PBCH block and the SCS of CORESET#0.

[0151] In another instance, the configuration table in the MIB is defined separately for whether the SS / PBCH block is located on a synchronization grid entry (or within a range from a synchronization grid entry), and is determined for a combination of the SCS of the SS / PBCH block and the SCS of CORESET#0. For this aspect, for SS / PBCH blocks that are located on a synchronization grid entry (or within a range from a synchronization grid entry) (e.g., those rows with an offset of 0 RBs), the example configuration table in the MIB may adopt a subset of the rows in the example table in the present disclosure, and for SS / PBCH blocks that are not located on a synchronization grid entry (or outside a range from a synchronization grid entry), the example configuration table in the MIB may adopt the remaining subset of the rows in the example table in the present disclosure.

[0152] Table 3 shows an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 30kHz. In one aspect, only configurations with indices 0 and 3 are expected by the UE on the PCell and / or PSCell (e.g., during initial cell search). Table 3 is an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz.

[0153]

Table 3

[0154]

[0155] Table 4 shows an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz. In one aspect, only configurations with indices 0 and 3 are expected by the UE on the PCell and / or PSCell (e.g., during initial cell search). Table 4 is an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz.

[0156]

Table 4

[0157]

[0158] Table 5 shows an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 30kHz. A set or subset of entries may be used. In one aspect, only configurations with indices 0 and 8 are expected by the UE on the PCell and / or PSCell (e.g., during initial cell search). Note that the spacing between offset values ​​is at most 4 RBs, which corresponds to the flexibility of reusing configurations by shifting CORESET#0 within the carrier, where the flexibility is given by BW_CH-BW_CORESET+1, and BW_CH is the bandwidth of the carrier, BW_CORESET is the bandwidth of CORESET#0, such that when the SCS of the SS / PBCH block and the SCS of CORESET#0 are 30kHz, BW_CH-BW_CORESET+1=51-48+1=4 RBs. Table 5 is an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 30kHz.

[0159]

Table 5

[0160]

[0161] Table 6 shows an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz. A set or subset of entries may be used. In one aspect, only configurations with indices 0 and 7 are expected by the UE on the PCell and / or PSCell (e.g., during initial cell search). Table 6 is an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz.

[0162]

Table 6

[0163]

[0164] Table 7 shows an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz. A set or subset of entries may be used. In one aspect, only configurations with indices 0 and 8 are expected by the UE on the PCell and / or PSCell (e.g., during initial cell search). Note that the interval between offset values ​​is at most 11 RBs, which corresponds to the flexibility of reusing configurations by shifting CORESET#0 within the carrier, where the flexibility is given by BW_CH-BW_CORESET+1, and BW_CH is the bandwidth of the carrier, BW_CORESET is the bandwidth of CORESET#0, such that when the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz, BW_CH-BW_CORESET+1=106-96+1=11 RBs. Table 7 is an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz.

[0165]

Table 7

[0166]

[0167] Table 8 shows an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz. A set or subset of entries may be used. In one aspect, only configurations with indices 0 and 8 are expected by the UE on the PCell and / or PSCell (e.g., during initial cell search). Note that the interval between offset values ​​is at most 11 RBs, which corresponds to the flexibility of reusing configurations by shifting CORESET#0 within the carrier, where the flexibility is given by BW_CH-BW_CORESET+1, and BW_CH is the bandwidth of the carrier, BW_CORESET is the bandwidth of CORESET#0, such that when the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz, BW_CH-BW_CORESET+1=106-96+1=11 RBs. Table 8 is an example configuration table in the MIB when both the SCS of the SS / PBCH block and the SCS of CORESET#0 are 15kHz.

[0168]

Table 8

[0169]

[0170] In one instance, the UE may determine a frequency domain offset (e.g., represented as O) based on the MIB of the detected SS / PBCH block, and the UE may determine an offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping with the first RB of the detected SS / PBCH block based on the determined frequency domain offset (e.g., O).

[0171] In this case, the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block is determined as the sum (e.g., O) of a first frequency domain offset determined according to the MIB (e.g., O) and a second frequency domain offset calculated by the UE (e.g., denoted as X), where the offset is defined for the SCS of the CORESET for the Type0-PDCCH CSS set. In one instance, X can be determined as the frequency difference between the frequency position of the detected SS / PBCH block and a reference frequency position known to the UE.

[0172] Fig. 10A A flow chart of a UE process 1000 for determining the frequency location of CORESET#0 according to an embodiment of the present disclosure is shown. Fig. 10A The illustrated embodiment of UE process 1000 is for illustration only. Fig. 10A One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0173] like Fig. 10A As shown, the UE process starts at step 1001. In step 1001, the UE determines the frequency position of the SS / PBCH block. In step 1002, the UE detects the SS / PBCH block. In step 1003, the UE obtains the configuration of the first frequency domain offset according to the MIB. In step 1004, the UE calculates the second frequency domain offset based on the frequency position of the detected SS / PBCH block and the reference frequency position known to the UE. In step 1005, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the sum of the first frequency domain offset and the second frequency domain offset.

[0174] Fig. 10B A flow chart of a UE process 1050 for determining the frequency location of CORESET #0 according to an embodiment of the present disclosure is shown. Fig. 10B The illustrated embodiment of the UE process 1050 is for illustration only. Fig. 10B One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0175] like Fig. 10B As shown, UE process 1050 starts at step 1011. In step 1011, the UE determines the frequency position of the SS / PBCH block. In step 1012, the UE detects the SS / PBCH block. In step 1013, the UE obtains the configuration of the first frequency domain offset according to the MIB. In step 1014, the UE determines whether the detected SS / PBCH block is on the synchronization grid entry. In step 1014, if the UE determines that the detected SS / PBCH block is on the synchronization grid entry, the UE process 1050 proceeds to step 1015. In step 1014, if the UE determines that it is not, the UE process 1050 proceeds to step 1016. In step 1015, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the first frequency domain offset according to the MIB. In step 1016, the UE calculates the second frequency domain offset based on the frequency position of the detected SS / PBCH block and the reference frequency position known to the UE. Finally, in step 1017, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the sum of the first frequency domain offset and the second frequency domain offset.

[0176] Fig. 10A or Fig. 10B An illustration of an example UE process for determining the frequency location of CORESET#0 is shown in FIG. 1. Note that if the second offset is calculated to be 0 when the detected SS / PBCH block is located on a synchronization grid entry, then Fig. 10A and Fig. 10B may be equivalent.

[0177] Fig.11 A relationship 1100 between frequency offsets according to an example of an embodiment of the present disclosure is shown. Fig.11 The embodiment of the relationship between the frequency offsets 1100 shown in FIG. 1 is for illustration only. Fig.11 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0178] Fig.11 The relationship between the frequency offsets in the above examples and / or instances is shown.

[0179] In one example, the reference frequency position can be selected as the frequency position corresponding to the GSCN of a synchronization grid entry that is in the same nominal carrier / subband / LBT bandwidth as the detected SS / PBCH block in which channel sensing is performed (assuming there is only one such synchronization grid entry).

[0180] In another example, the reference frequency position can be selected as a synchronization grid entry such that the offset (e.g., O+X) is an integer between 0 and BW_CORESET-BW_SSB, where BW_CORESET is the BW of CORESET#0 (e.g., 48 RBs for a 30 kHz SCS or 96 RBs for a 15 kHz SCS) and BW_SSB is the BW of the SSB (e.g., 20 RBs).

[0181] In yet another example, the reference frequency position may be selected to be the synchronization grid entry that is closest and has a lower frequency than the frequency position of the detected SS / PBCH block.

[0182] In yet another example, the reference frequency position may be selected to be the synchronization grid entry that is closest and has a higher frequency than the frequency position of the detected SS / PBCH block.

[0183] In yet another example, the reference frequency position may be selected as a synchronization grid entry that is the lowest one in a group of synchronization grid entries predefined in the same nominal carrier / subband / LBT bandwidth in which channel sensing is performed as the detected SS / PBCH block.

[0184] In yet another example, the reference frequency position may be selected as a synchronization raster entry that is the highest one in a group of synchronization raster entries predefined in the same nominal carrier / subband / LBT bandwidth as the detected SS / PBCH block in which channel sensing is performed.

[0185] In yet another example, the reference frequency location may be selected as a location configured by the gNB (e.g., a GSCN value).

[0186] In one example, the UE first determines the frequency position for detecting the SS / PBCH block (e.g., the frequency position can be configured by the gNB through the higher layer parameter ssbFrequency), and reads the MIB of the detected SS / PBCH block to obtain a first frequency offset (e.g., from the field of controlResourceSetZero in pdcch-ConfigSIB1), and calculates a second frequency offset based on the difference between the frequency position of the detected SS / PBCH block and the synchronization grid entry (in units of RB relative to the SCS of CORESET#0), and then determines the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block as the sum of the first determined frequency domain offset read from the MIB and the second frequency domain offset calculated by the UE.

[0187] In one instance, the second frequency offset (e.g., X) can be determined by an offset from the minimum RB index of a common RB overlapping the first RB of a detected SS / PBCH block (e.g., having a position configured by the gNB via a higher layer parameter ssbFrequency) to the minimum RB index of a common RB overlapping the first RB of a SS / PBCH block assumed to be located at a reference frequency location (e.g., a frequency location corresponding to the GSCN of a synchronization grid entry within the same nominal carrier / subband / LBT bandwidth in which channel sensing is performed), where the SS / PBCH block at the reference frequency location is assumed to have the same SCS as the detected SS / PBCH block.

[0188] In another instance, the second frequency offset (e.g., X) can be determined by the sum of two parts: the first part is an offset from the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block to the RB index of the common RB overlapping a reference frequency position (e.g., a frequency position corresponding to the GSCN of a synchronization grid entry within the same nominal carrier / subband / LBT bandwidth in which channel sensing is performed); and the second part is a fixed offset, e.g., half the BW of the SS / PBCH block of 10 RBs.

[0189] In another instance, a second frequency offset (e.g., X) can be determined as an offset from an RB index of a common RB that overlaps with a frequency position of a detected SS / PBCH block (e.g., higher layer parameter ssbFrequency) to an RB index of a common RB that overlaps with a reference frequency position (e.g., a synchronization grid entry within the same nominal carrier / subband / LBT bandwidth in which channel sensing is performed).

[0190] In another example, the second frequency offset may be determined by the formula: X = (F_REF-SS_REF) / SCS_CORESET / N_RE, where F_REF is the RF reference frequency in MHz corresponding to the NR-ARFCN of the ssbFrequency, SS_REF is the RF reference frequency in MHz corresponding to the GSCN of the synchronization grid entry (in the example, such as the reference frequency position of the example), SCS_CORESET is the SCS of CORESET#0 (e.g., 15kHz or 30kHz), and N_RE is the number of REs in RBs (e.g., N_RE=12).

[0191] In one example, the UE expects the second frequency offset (e.g., X) to be an integer (e.g., the RE level offset k_SSB is the same for SS / PBCH blocks on synchronization grid entries in the nominal carrier / subband / LBT bandwidth where channel sensing is performed and outside the synchronization grid entries).

[0192] In one example, the second frequency offset (eg, X) may be negative (eg, F_REF <SS_REF)。

[0193] In one example, the UE expects the offset (e.g., O+X) to be an integer between 0 and BW_CORESET-BW_SSB, where BW_CORESET is the BW of CORESET#0 (e.g., 48 RBs for an SCS of 30 kHz or 96 RBs for an SCS of 15 kHz), and BW_SSB is the BW of SSB (e.g., 20 RBs).

[0194] In one example, the UE expects the offset (e.g., O+X) to be an integer between 0 and BW_CH-BW_SSB, where BW_CH is the BW of the nominal carrier / subband / LBT bandwidth in which channel sensing is performed (e.g., 51 RBs for an SCS of 30 kHz or 106 RBs for an SCS of 15 kHz), and BW_SSB is the BW of the SSB (e.g., 20 RBs). In yet another aspect, the example is applicable to a scenario where SS / PBCH blocks with an SCS of 30 kHz and an SCS of 15 kHz are located at the same reference frequency position (synchronization grid entry) when determining the frequency offset configuration for the PCell and / or PSCell. Fig.12 A diagram of this scenario is shown.

[0195] Fig.12 An example SS / PBCH block 1200 with an SCS of 30 kHz and an SCS of 15 kHz located at the same reference frequency position is shown according to an embodiment of the present disclosure. Fig.12The illustrated embodiment of SS / PBCH block 1200 is for illustration only. Fig.12 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0196] In one example, the second frequency offset may be determined by the following formula: X=floor((F_REF-SS_REF) / SCS_CORESET / N_RE), where F_REF is the RF reference frequency in MHz corresponding to the NR-ARFCN of ssbFrequency, SS_REF is the RF reference frequency in MHz corresponding to the GSCN of the synchronization grid entry (in an example, such as the reference frequency position of this example), SCS_CORESET is the SCS of CORESET#0 (e.g., 15kHz or 30kHz), and N_RE is the number of REs in RBs (e.g., N_RE=12). "floor(x)" refers to the floor operation that gives the largest integer less than or equal to x.

[0197] In one example, the UE expects the offset (e.g., O+X) to be an integer between 0 and BW_CORESET-BW_SSB, where BW_CORESET is the BW of CORESET#0 (e.g., 48 RBs for an SCS of 30 kHz or 96 RBs for an SCS of 15 kHz), and BW_SSB is the BW of SSB (e.g., 20 RBs).

[0198] In another example, the UE expects the offset (e.g., O+X) to be an integer between 0 and BW_CH-BW_SSB, where BW_CH is the BW of the nominal carrier / subband / LBT bandwidth in which channel sensing is performed (e.g., 51 RBs for an SCS of 30 kHz or 106 RBs for an SCS of 15 kHz), and BW_SSB is the BW of the SSB (e.g., 20 RBs). In another aspect, the example is applicable to a scenario where SS / PBCH blocks with an SCS of 30 kHz and an SCS of 15 kHz are located at the same reference frequency position (synchronization grid entry) when determining the frequency offset configuration for the PCell and / or PSCell. Fig.12 A diagram of this scenario is shown.

[0199] In one instance, the second frequency offset can be determined by the following formula: X = ((F_REF-SS_REF) / SCS_CORESET-k_SSB) / N_RE, where F_REF is the RF reference frequency in MHz corresponding to the NR-ARFCN of ssbFrequency, SS_REF is the RF reference frequency in MHz corresponding to the GSCN of the synchronization grid entry (in the example, such as the reference frequency position of this instance), SCS_CORESET is the SCS of CORESET#0 (e.g., 15kHz or 30kHz), and N_RE is the number of REs in RBs (e.g., N_RE=12).

[0200] In one example, the UE expects the offset (e.g., O+X) to be an integer between 0 and BW_CORESET-BW_SSB, where BW_CORESET is the BW of CORESET#0 (e.g., 48 RBs for an SCS of 30 kHz or 96 RBs for an SCS of 15 kHz), and BW_SSB is the BW of SSB (e.g., 20 RBs).

[0201] In one instance, the UE expects the offset (e.g., O+X) to be an integer between 0 and BW_CH-BW_SSB, where BW_CH is the BW of the nominal carrier / subband / LBT bandwidth in which channel sensing is performed (e.g., 51 RBs for an SCS of 30 kHz or 106 RBs for an SCS of 15 kHz), and BW_SSB is the BW of the SSB (e.g., 20 RBs).

[0202] In one example, when determining the frequency offset configuration for the PCell and / or PSCell, it is applicable that the SS / PBCH blocks with an SCS of 30 kHz and an SCS of 15 kHz are located at the same reference frequency position (synchronization grid entry). Fig.12 A diagram of this scenario is shown.

[0203] In one example, the second frequency offset can be determined by the following formula: X = floor((F_REF - SS_REF) / SCS_CORESET / N_RE) if k_SSB*15kHz / SCS_CORESET ≥ N_SC; and X = floor((F_REF - SS_REF) / SCS_CORESET / N_RE) + 1 if k_SSB*15kHz / SCS_CORESET < N_SC, where F_REF is the RF reference frequency in MHz corresponding to the NR-ARFCN of ssbFrequency, SS_REF is the RF reference frequency in MHz corresponding to the GSCN of the synchronization raster entry (in the example, such as the reference frequency position of this example), SCS_CORESET is the SCS of CORESET#0 (e.g., 15kHz or 30kHz), N_RE is the number of REs in terms of RBs (e.g., N_RE = 12), N_SC is the remaining number of subcarriers calculated based on the offset given by the following formula: N_SC = (F_REF - SS_REF) / SCS_CORESET - X*N_RE, where (F_REF - SS_REF) / SCS_CORESET is expected to be an integer, and k_SSB is given by the PBCH payload of the detected SS / PBCH block (e.g., the offset between the boundary of the SS / PBCH block and the common resource grid).

[0204] "floor(x)" refers to the floor operation that gives the largest integer less than or equal to x. In one example, the offset X can be negative (e.g., F_REF < SS_REF). In a further consideration, the UE expects the offset (e.g., O + X) to be an integer between 0 and BW_CORESET - BW_SSB, where BW_CORESET is the BW of CORESET#0 (e.g., 48 RBs for 30kHz SCS or 96 RBs for 15kHz SCS), and BW_SSB is the BW of the SSB (e.g., 20 RBs).

[0205] In another example, the UE expects the offset (e.g., O+X) to be an integer between 0 and BW_CH-BW_SSB, where BW_CH is the BW of the nominal carrier / subband / LBT bandwidth in which channel sensing is performed (e.g., 51 RBs for an SCS of 30 kHz or 106 RBs for an SCS of 15 kHz), and BW_SSB is the BW of the SSB (e.g., 20 RBs). In another aspect, the example is applicable to a scenario where SS / PBCH blocks with an SCS of 30 kHz and an SCS of 15 kHz are located at the same reference frequency position (synchronization grid entry) when determining the frequency offset configuration for the PCell and / or PSCell. Fig.12 A diagram of this scenario is shown.

[0206] In one example, all of the above examples and / or instances apply to when determining the frequency offset configuration for the PCell and / or PSCell, SS / PBCH blocks with different SCSs (e.g., an SCS of 30 kHz and an SCS of 15 kHz) can be located at different reference frequency positions, so that there can be an offset between the synchronization grid entry (which is the reference frequency position for determining the frequency offset configuration for the SCS of 30 kHz) and the reference frequency position for determining the frequency offset configuration for another SCS (e.g., 15 kHz).

[0207] Fig.13 An example SS / PBCH block 1300 with an SCS of 30 kHz and an SCS of 15 kHz at different reference frequency locations is shown according to an embodiment of the present disclosure. Fig.13 The illustrated embodiment of SS / PBCH block 1300 is for illustration only. Fig.13 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0208] If the reference frequency position of the SCS of 15 kHz and the reference frequency position of the SCS of 30 kHz are selected differently, a further offset may be applied to X for the SCS of the SS / PBCH block of 15 kHz (while no change is made to the SCS of the SS / PBCH block of 30 kHz), such that the second offset may be determined as X+X', where X is the offset specified in the instance of the method and X' is the further offset between the two reference positions.

[0209] In one example, X'=10 RBs, so that the lowest boundaries of SS / PBCH blocks located at two different reference positions are aligned. In another example, X' corresponds to the minimum RB level offset from the SS / PBCH block with an SCS of 15kHz and located on a synchronization grid entry to the channel boundary, for example, X'=13 RBs.

[0210] In one example, the UE may determine a frequency domain offset (e.g., represented as O) based on the MIB of the detected SS / PBCH block, and the UE may determine an offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping with the first RB of the detected SS / PBCH block based on the determined frequency domain offset (e.g., O).

[0211] In such an example, the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping with the first RB of the corresponding SS / PBCH block is determined by a one-to-one mapping of the frequency domain offset (e.g., O) determined according to the MIB.

[0212] Fig.14 A flow chart of a UE process 1400 for determining the frequency location of CORESET #0 according to an embodiment of the present disclosure is shown. Fig.14 The illustrated embodiment of the UE process 1400 is for illustration only. Fig.14 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0213] like Fig.14 As shown, the UE process 1400 starts at step 1401. In step 1401, the UE determines the frequency location of the SS / PBCH block. In step 1402, the UE detects the SS / PBCH block. In step 1403, the UE obtains the configuration of the frequency domain offset according to the MIB. Finally, in step 1404, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 based on a one-to-one mapping to the obtained frequency domain offset.

[0214] In one example, the frequency domain difference between the lowest RB of the SS / PBCH block and the lowest RB of CORESET#0 is determined as the determined frequency domain offset + X (e.g., O+X), where X is a fixed value, e.g., the SCS is fixed for each SS / PBCH block.

[0215] In one sub-example, X=1 for SCS of all SS / PBCH blocks.

[0216] In another sub-example, X=4 for SCS of all SS / PBCH blocks.

[0217] In yet another sub-example, for SCS of SS / PBCH blocks of 30 kHz, X=24.

[0218] In yet another sub-example, for an SCS of SS / PBCH blocks of 15 kHz, X=48.

[0219] In yet another sub-example, for SCS of SS / PBCH blocks of 30 kHz, X=14.

[0220] In yet another sub-example, for an SCS of SS / PBCH blocks of 15 kHz, X=38.

[0221] In one example, the frequency domain difference between the lowest RB of the SS / PBCH block and the lowest RB of CORESET#0 is determined as X-frequency domain determined offset (e.g., XO), where X is a fixed value, e.g., the SCS is fixed for each SS / PBCH block.

[0222] In one sub-example, for SCS with SS / PBCH blocks of 30 kHz, X=48.

[0223] In another sub-example, for SCS with SS / PBCH blocks of 15 kHz, X=96.

[0224] In yet another sub-example, for SCS of SS / PBCH blocks of 30 kHz, X=28.

[0225] In yet another sub-example, for an SCS of SS / PBCH blocks of 15 kHz, X=76.

[0226] In one example, when the UE is configured to detect an SS / PBCH block, the UE may be configured with a frequency domain offset (e.g., O_SSB), and the UE determines an offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of a common RB overlapping with the first RB of the detected SS / PBCH block based on the configured frequency domain offset (e.g., O_SSB).

[0227] In one example, the UE may determine the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block as the configured frequency domain offset (eg, O_SSB).

[0228] In one example, the UE still needs to read the contents of the PBCH of the detected SS / PBCH block to determine the number of symbols used for CORESET#0, and overwrite the frequency domain offset (e.g., O) configured in the MIB of the detected SS / PBCH block with the configured frequency domain offset (e.g., O_SSB) to determine the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping with the first RB of the detected SS / PBCH block.

[0229] In one example, the above example can be combined with the examples and / or methods mentioned in the present disclosure. If a frequency offset configuration is provided to the UE (e.g., O_SSB), the UE can determine the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block as the configured frequency domain offset (e.g., O_SSB); otherwise, the UE can determine the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block as the sum of two offsets, wherein the first offset is obtained from the MIB (e.g., O), and the second offset is calculated by the UE (e.g., X) according to the examples and / or instances mentioned in the present disclosure.

[0230] Fig.15A An example of a UE procedure for this aspect of this example is shown.

[0231] Fig.15A A flow chart of a UE process 1500 for determining the frequency location of CORESET #0 according to an embodiment of the present disclosure is shown. Fig.15A The illustrated embodiment of the UE process 1500 is for illustration only. Fig.15A One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0232] like Fig.15AAs shown, UE process 1500 starts at step 1501. In step 1501, the UE determines the frequency position of the SS / PBCH block. In step 1502, the UE detects the SS / PBCH block. In step 1503, the UE determines whether a frequency domain offset is provided to the UE. In step 1503, if the UE determines that a frequency domain offset is provided to the UE, the UE process 1500 proceeds to step 1507. In step 1503, if the UE determines that a frequency domain offset is not provided to the UE, the UE process 1500 proceeds to step 1504. In step 1504, the UE obtains the configuration of the first frequency domain offset according to the MIB. In step 1505, the UE determines whether the detected SS / PBCH block is on a synchronization grid entry. In step 1505, if the UE determines that the detected SS / PBCH block is on a synchronization grid entry, the UE process 1500 proceeds to step 1506. In step 1505, if the UE determines that the detected SS / PBCH block is not on a synchronization grid entry, the UE process 1500 proceeds to step 1508. In step 1506, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as a first frequency domain offset according to the MIB. In step 1507, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the configured offset. In step 1508, the UE calculates a second frequency domain offset based on the frequency position of the detected SS / PBCH block and a reference frequency position known to the UE. In step 1509, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the sum of the first frequency domain offset and the second frequency domain offset.

[0233] In another example, the UE may determine the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block as the sum of a first offset that is a configured frequency domain offset (e.g., O_SSB) and a second frequency domain offset (e.g., O) obtained from the MIB of the detected SS / PBCH block, e.g., O+O_SSB.

[0234] In such an example, the configured frequency domain offset (e.g., O_SSB) is an additional offset to the offset (e.g., O) obtained from the MIB of the detected SS / PBCH block.

[0235] In one instance, the above example may be combined with the examples and / or instances mentioned in the present disclosure. If a configuration of a frequency offset is provided to the UE (e.g., O_SSB), the UE may determine the second offset constituting an offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block as the configured frequency domain offset (e.g., O_SSB); otherwise, the UE may determine the second offset constituting an offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB overlapping the first RB of the detected SS / PBCH block as the offset calculated by the UE according to the examples, embodiments and / or instances mentioned in the present disclosure. Fig. 15B An example of a UE procedure for this aspect of this example is shown.

[0236] Fig. 15B Another flow diagram of a UE process 1550 for determining the frequency location of CORESET #0 according to an embodiment of the present disclosure is shown. Fig. 15B The embodiment of the UE process 1550 shown in FIG. 1 is for illustration only. Fig. 15B One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0237] like Fig. 15BAs shown, the UE process 1550 starts at step 1511. In step 1511, the UE determines the frequency location of the SS / PBCH block. In step 1512, the UE detects the SS / PBCH block. In step 1513, the UE obtains the configuration of the first frequency domain offset according to the MIB. In step 1514, the UE determines whether the detected SS / PBCH block is on the synchronization grid entry. In step 1514, if the UE determines that the detected SS / PBCH block is on the synchronization grid entry, the UE process 1550 proceeds to step 1515. In step 1514, if the UE determines that the detected SS / PBCH block is not on the synchronization grid entry, the UE process 1550 proceeds to step 1516. In step 1515, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the first frequency domain offset according to the MIB. In step 1516, the UE determines whether the frequency domain offset is provided to the UE. In step 1516, if the UE determines that a frequency domain offset is provided to the UE, the UE process 1550 proceeds to step 1517. In step 1516, if the UE determines that a frequency domain offset is not provided to the UE, the UE process 1550 proceeds to step 1519. In step 1517, the UE determines the second frequency domain offset as the configured frequency offset. In step 1518, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the sum of the first frequency domain offset and the second frequency domain offset. In step 1519, the UE calculates the second frequency domain offset based on the frequency position of the detected SS / PBCH block and the reference frequency position known to the UE. In step 1520, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the sum of the first frequency domain offset and the second frequency domain offset.

[0238] In one example, the UE may determine an offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB that overlaps with the first RB of the detected SS / PBCH block based on whether the detected SS / PBCH block is located on a synchronization grid entry (or within a range from the synchronization grid entry).

[0239] In one instance, if the UE determines that the detected SS / PBCH block is located on a synchronization grid entry (or within a range from the synchronization grid entry), the UE determines an offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of a common RB overlapping with the first RB of the detected SS / PBCH block based on a first frequency offset configured by the MIB of the detected SS / PBCH block, and if the UE determines that the detected SS / PBCH block is not located on the synchronization grid entry (or outside the range from the synchronization grid entry), the UE determines an offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of a common RB overlapping with the first RB of the detected SS / PBCH block as a second frequency domain offset.

[0240] Fig.16 A flow chart of a UE process 1600 for determining the frequency location of CORESET #0 according to an embodiment of the present disclosure is shown. Fig.16 The illustrated embodiment of the UE process 1600 is for illustration only. Fig.16 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0241] like Fig.16 As shown, UE process 1600 starts at step 1601. In step 1601, the UE determines the frequency position of the SS / PBCH block. In step 1602, the UE detects the SS / PBCH block. In step 1603, the UE obtains the configuration of the first frequency domain offset according to the MIB. In step 1604, the UE determines whether the detected SS / PBCH block is on the synchronization grid entry. In step 1604, if the UE determines that the detected SS / PBCH block is on the synchronization grid entry, the UE process 1600 proceeds to step 1605. In step 1604, if the UE determines that the detected SS / PBCH block is not on the synchronization grid entry, the UE process 1600 proceeds to step 1606. In step 1605, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the first frequency domain offset according to the MIB. In step 1606, the UE determines the frequency domain difference between the detected SS / PBCH block and CORESET#0 as the second frequency domain offset.

[0242] In one example, the second frequency domain offset may be a fixed value, for example, the SCS for each SS / PBCH block is fixed.

[0243] In one sub-example, for an SCS with an SS / PBCH block of 30 kHz, the second frequency domain offset may be 28 RBs.

[0244] In another sub-example, for an SCS with an SS / PBCH block of 15 kHz, the second frequency domain offset may be 76 RBs.

[0245] In one example, the second frequency domain offset can have a one-to-one mapping with the first frequency domain offset (e.g., the first frequency offset represented as O).

[0246] In a sub-example, the second frequency domain offset may be O+X, where X is a fixed value, for example, the SCS for each SS / PBCH block is fixed. For example, X=1 for the SCS of all SS / PBCH blocks, or X=4 for the SCS of all SS / PBCH blocks, or X=14 for the SCS of SS / PBCH blocks of 30 kHz, or X=38 for the SCS of SS / PBCH blocks of 15 kHz.

[0247] In another sub-example, the second frequency domain offset may be XO, where X is a fixed value, for example, the SCS for each SS / PBCH block is fixed. For example, for an SCS of a 30 kHz SS / PBCH block, X=28, and for an SCS of a 15 kHz SS / PBCH block, X=76.

[0248] In one example, the second frequency domain offset is determined based on a separate configuration table that is designed differently from the configuration table for the SS / PBCH block located on the synchronization grid entry. For example, the first frequency domain offset is determined based on the first configuration table, and the second frequency domain offset is determined based on the second configuration table.

[0249] In one example, the second frequency domain offset is configured by the gNB, for example, associated with a configured frequency position of a detected SS / PBCH block.

[0250] Fig.17 1700 according to an embodiment of the present disclosure, the method 1700 may be performed by a user equipment (UE) (eg, Figure 1 111-116) as shown. Fig.17 The illustrated embodiment of method 1700 is for illustration only. Fig.17 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described. Other embodiments may be used without departing from the scope of the present disclosure.

[0251] like Fig.17 As shown, method 1700 starts at step 1702. In step 1702, a UE supporting shared spectrum channel access identifies a frequency location of a synchronization signal and physical broadcast channel (SS / PBCH) block.

[0252] Then, in step 1704, the UE receives an SS / PBCH block from a base station (BS).

[0253] Next, in step 1706, the UE determines whether the frequency position of the SS / PBCH block corresponds to the global synchronization channel number (GSCN) of the synchronization grid entry.

[0254] Finally, if the frequency position of the SS / PBCH block does not correspond to the GSCN of the synchronization grid entry, then in step 1708, the UE determines the offset as the sum of the first offset and the second offset.

[0255] In one embodiment, in step 1708, the offset is the difference from the minimum resource block (RB) index of the control resource set (CORESET) for the Type0 physical downlink control channel (Type0-PDCCH) common search space (CSS) set to the minimum RB index of the common RB overlapping with the first RB of the SS / PBCH block.

[0256] In one embodiment, in step 1708, the first offset, the second offset, and the SS / PBCH block assumed to be located at the GSCN of the synchronization grid entry are identified based on the subcarrier spacing of the CORESET for the Type0-PDCCH CSS set.

[0257] In one embodiment, if the frequency position of the SS / PBCH block corresponds to the GSCN of the synchronization grid entry, the UE identifies the offset as a first offset.

[0258] In one embodiment, if the frequency position of the SS / PBCH block does not correspond to the GSCN of the synchronization grid entry, the UE receives a higher layer parameter of ssbFrequency including the frequency position of the SS / PBCH block from the BS via a higher layer signal.

[0259] In one embodiment, the UE receives the first offset from the BS via a field of controlResourceSetZero included in a master information block (MIB) of the SS / PBCH block.

[0260] In one embodiment, the UE identifies a second offset determined as an offset from the minimum RB index of a common RB overlapping the first RB of a SS / PBCH block to the minimum RB index of a common RB overlapping the first RB of a SS / PBCH block assumed to be located at the GSCN of the synchronization grid entry.

[0261] In such an embodiment, the synchronization grid entry is determined as a single entry within a bandwidth used for shared spectrum channel access operations, and the bandwidth includes the received SS / PBCH blocks.

[0262] Fig.18 A user equipment UE according to an embodiment of the present disclosure is shown.

[0263] The above UE may correspond to Fig.18 UE.

[0264] refer to Fig.18 , the UE may include a processor 1805, a transceiver 1810, and a memory 1815. However, not all components shown in the figure are required. The UE may include: Fig.18 Furthermore, according to another embodiment, the processor 1805, the transceiver 1810, and the memory 1815 may be implemented as a single chip.

[0265] The above-mentioned components will now be described in detail.

[0266] The processor 1805 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. The operation of the UE may be implemented by the processor 1805.

[0267] The processor 1805 may detect the PDCCH on the configured control resource set. The processor 1805 determines the method for dividing the CB and the method for rate matching the PDSCH according to the PDCCH. The processor 1805 may control the transceiver 1810 to receive the PDSCH according to the PDCCH. The processor 1805 may generate HARQ-ACK information according to the PDSCH. The processor 1805 may control the transceiver 1810 to send the HARQ-ACK information.

[0268] The transceiver 1810 may include an RF transmitter for up-converting and amplifying transmitted signals, and an RF receiver for down-converting received signal frequencies. However, according to another embodiment, the transceiver 1810 may be implemented by more or fewer components than shown in the components.

[0269] The transceiver 1810 may be connected to the processor 1805 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 1810 may receive signals through a wireless channel and output the signals to the processor 1805. The transceiver 1810 may transmit signals output from the processor 1805 through a wireless channel.

[0270] The memory 1815 may store control information or data included in the signal obtained by the UE. The memory 1815 may be connected to the processor 1805 and store at least one instruction or protocol or a parameter for the proposed function, process and / or method. The memory 1815 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0271] Fig.19 A base station BS according to an embodiment of the present disclosure is shown.

[0272] The above BS can correspond to Fig.19 BS.

[0273] refer to Fig.19 , the base station may include a processor 1905, a transceiver 1910, and a memory 1915. However, not all components shown in the figure are required. The base station may include a processor 1905, a transceiver 1910, and a memory 1915. Fig.19 Furthermore, according to another embodiment, the processor 1905, the transceiver 1910, and the memory 1915 may be implemented as a single chip.

[0274] The above-mentioned components will now be described in detail.

[0275] The processor 1905 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. The operations of the BS may be implemented by the processor 1905.

[0276] The transceiver 1910 may include an RF transmitter for up-converting and amplifying transmitted signals, and an RF receiver for down-converting received signal frequencies. However, according to another embodiment, the transceiver 1910 may be implemented by more or fewer components than shown in the components.

[0277] The transceiver 1910 may be connected to the processor 1905 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 1910 may receive signals through a wireless channel and output the signals to the processor 1905. The transceiver 1910 may transmit signals output from the processor 1905 through a wireless channel.

[0278] The memory 1915 may store control information or data included in the signal obtained by the BS. The memory 1915 may be connected to the processor 1905 and store at least one instruction or protocol or a parameter for the proposed function, process and / or method. The memory 1915 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

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

[0280] Those skilled in the art will appreciate that all or part of the steps performed by the above-described method embodiments may be implemented by a program through commands to associated hardware, and the program may be stored in a computer-readable storage medium. When the program is executed, one of the steps of the method embodiments or a combination thereof is also included.

[0281] In addition, the functional unit in various embodiments of the present application can be integrated in the processing module, or each unit can exist physically independently, or two or more units can be integrated in one module. The integrated module can be implemented in the form of hardware, or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, the integrated module can also be stored in a computer-readable storage medium.

[0282] While the invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the invention as defined by the following claims.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method include: Detect synchronization signal and physical broadcast channel block SS / PBCH block; In the case where the SS / PBCH block is not located at the frequency position of the synchronization grid entry, identifying an offset from a minimum resource block RB index of a control resource set CORESET for Type0-PDCCH to a minimum RB index of a common RB overlapping with a first RB of the SS / PBCH block based on a sum of a first offset and a second offset; as well as Based on the identified offset, monitoring the Type0-PDCCH, The first offset is configured based on the master information block MIB in the SS / PBCH block, and The second offset is identified based on an offset from a minimum RB index of a common RB overlapping with a first RB of a SS / PBCH block to a minimum RB index of a common RB overlapping with a first RB of another SS / PBCH block assumed to be located at a frequency position of the synchronization grid entry.

2. The method of claim 1, further comprising identifying the offset as a first offset if an SS / PBCH block is located at a frequency position of the synchronization grid entry.

3. The method according to claim 1, in, The synchronization grid entry is located in the same carrier as the SS / PBCH block.

4. The method according to claim 1, in, The frequency position of the synchronization grid entry corresponds to the global synchronization channel number GSCN of the synchronization grid entry.

5. The method according to claim 1, further comprising: include: A higher layer parameter ssbFrequency including the frequency position of the SS / PBCH block is received from the base station.

6. The method according to claim 1, in, The first offset and the second offset are defined relative to the subcarrier spacing SCS of the CORESET for Type0-PDCCH.

7. A user equipment UE in a wireless communication system, the UE include: Transceiver; as well as at least one processor operably connected to the transceiver and configured to: Detect synchronization signal and physical broadcast channel block SS / PBCH block; In the case where the SS / PBCH block is not located at the frequency position of the synchronization grid entry, identifying an offset from a minimum resource block RB index of a control resource set CORESET for Type0-PDCCH to a minimum RB index of a common RB overlapping with a first RB of the SS / PBCH block based on a sum of a first offset and a second offset; as well as Based on the identified offset, monitoring the Type0-PDCCH, The first offset is configured based on the master information block MIB in the SS / PBCH block, and The second offset is identified based on an offset from a minimum RB index of a common RB overlapping with a first RB of a SS / PBCH block to a minimum RB index of a common RB overlapping with a first RB of another SS / PBCH block assumed to be located at a frequency position of the synchronization grid entry.

8. The UE according to claim 7, in, The at least one processor is further configured to identify the offset as a first offset if an SS / PBCH block is located at a frequency location of the synchronization raster entry.

9. The UE according to claim 7, in, The synchronization grid entry is located in the same carrier as the SS / PBCH block.

10. The UE according to claim 7, in, The frequency position of the synchronization grid entry corresponds to the global synchronization channel number GSCN of the synchronization grid entry.

11. The UE according to claim 7, in, The at least one processor is further configured to receive, via the transceiver, from a base station a higher layer parameter ssbFrequency including a frequency location of a SS / PBCH block.

12. The UE according to claim 7, in, The first offset and the second offset are defined for a subcarrier spacing SCS of a CORESET for a Type0-PDCCH.

Citation Information

Patent Citations

  • Method and apparatus for system information delivery in wireless communication system

    CN110168972A

  • The method and apparatus for receiving system information in the wireless communication

    KR1020180132548A

  • Method and apparatus of NR RMSI coreset configuration in mib

    US20190132170A1

  • Method and apparatus for SS / PBCH block frequency location indication

    US20190200307A1

  • Method for transmitting and receiving downlink channel and device therefor

    WO2019098768A1