User equipment (UE) in wireless communication system and method performed by same

Abstract

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

Description

[0001] This application is a divisional application, and the application number of its parent application is: 202080055131.3, the application date is: August 28, 2020, and the invention title is: Method and apparatus for receiving RMSI from an adjacent cell. Technical Field

[0002] This application generally relates to wireless communication systems, and more particularly, the present disclosure relates to receiving RMSI from an adjacent cell. Background Art

[0003] A 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 receiving point such as NodeB. A UE (which is also commonly referred to as a terminal or a mobile station) can be fixed or mobile, and can be a cellular phone, a personal computer device, or an automated device. An eNodeB (eNB) that refers to NodeB in a Long Term Evolution (LTE) communication system and a gNodeB (gNB) that refers to NodeB in a New Radio (NR) communication system can also be referred to as an access point or other equivalent terms.

[0004] In order to meet the demand for increased wireless data traffic since the deployment of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or pre-5G communication systems. 5G or pre-5G communication systems are also referred to as "ultra 4G networks" or "post-Long Term Evolution (LTE) systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (such as the 60 GHz band) 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 technologies have been discussed for 5G communication systems. In addition, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access network (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-point (CoMP), receiver-side interference cancellation, etc. In 5G systems, hybrid frequency shift keying (FSK) and Feher quadrature amplitude modulation (FQAM) as advanced coding modulation (ACM), and sliding window superposition coding (SWSC) have been developed, as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies.

[0005] The Internet, which is a human-centered connection network where 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 technologies and big data processing technologies through connections to cloud servers. Since 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. Such an 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 of existing information technology (IT) and various industrial applications, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services, etc.

[0006] 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 communication can be implemented through beamforming, MIMO, and array antennas. The application of cloud RAN as the above-mentioned big data processing technology can also be considered an example of the integration between 5G technology and IoT technology.

[0007] As described above, various services can be provided according to the development of wireless communication systems, so a method for easily providing these services is needed. Summary of the Invention

[0008] Technical Solution to Solve the Problem

[0009] The present disclosure relates to a quasi-5G or 5G communication system for receiving RMSI from an adjacent cell.

[0010] 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 in a case where a frequency position of the detected SS / PBCH block does not correspond to a frequency position of a synchronization raster entry, determining an offset between a control resource set CORESET for a Type0-PDCCH (Type 0 PDCCH) and the SS / PBCH block as a sum of a first offset and a second offset, where the first offset is configured by a master information block MIB in the detected SS / PBCH block, and where 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

[0011] To more fully understand the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like components:

[0012] Figure 1 FIG. 1 shows an example wireless network according to an embodiment of the present disclosure;

[0013] Figure 2 FIG. 2 shows an example gNB according to an embodiment of the present disclosure;

[0014] Figure 3 FIG. 3 shows an example UE according to an embodiment of the present disclosure;

[0015] Figure 4 FIG. 4 shows an example transmitter structure using OFDM according to an embodiment of the present disclosure;

[0016] Figure 5 FIG. 5 shows an example receiver structure using OFDM according to an embodiment of the present disclosure;

[0017] Figure 6 FIG. 6 shows an example encoding process for a DCI format according to an embodiment of the present disclosure;

[0018] Figure 7 FIG. 7 shows an example decoding process for a DCI format for a UE according to an embodiment of the present disclosure;

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

[0020] Figure 9 FIG. 9 shows a flowchart of a UE process for determining a frequency position of CORESET #0 according to an embodiment of the present disclosure;

[0021] Figure 10A The flowchart shows a UE process for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure;

[0022] Figure 10B The flowchart shows a UE process for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure;

[0023] Figure 11 The example relationship between frequency offsets according to an embodiment of the present disclosure is shown;

[0024] Figure 12 The example SS / PBCH blocks with 30 kHz SCS and 15 kHz SCS located at the same reference frequency position according to an embodiment of the present disclosure are shown;

[0025] Figure 13 The example SS / PBCH blocks with 30 kHz SCS and 15 kHz SCS located at different reference frequency positions according to an embodiment of the present disclosure are shown;

[0026] Figure 14 The flowchart shows a UE process for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure;

[0027] Figure 15A The flowchart shows a UE process for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure;

[0028] Figure 15B Another flowchart showing a UE process for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure is shown;

[0029] Figure 16 The flowchart shows a UE process for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure;

[0030] Figure 17 The flowchart shows a method for RMSI reception according to an embodiment of the present disclosure;

[0031] Figure 18 The user equipment UE according to an embodiment of the present disclosure is shown; and

[0032] Figure 19 The base station BS according to an embodiment of the present disclosure is shown. Detailed implementation manners

[0033] 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 in a case where a frequency position of the detected SS / PBCH block does not correspond to a 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 a sum of a first offset and a second offset, where the first offset is configured by a master information block (MIB) in the detected SS / PBCH block, and where 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.

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

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

[0036] In an embodiment, the synchronization raster entry is in the same carrier as the SS / PBCH block.

[0037] In an embodiment, the offset is a smallest RB index from a smallest RB of the CORESET for Type0-PDCCH to a smallest RB index of a common RB that overlaps with a first RB of the SS / PBCH block.

[0038] In an embodiment, the second offset is determined based on an offset from a smallest RB index of a common RB that overlaps with a first RB of the SS / PBCH block to a smallest RB index of a common RB that overlaps with a first RB of another SS / PBCH block hypothetically located at the frequency position of the synchronization raster entry.

[0039] In an embodiment, the frequency position of the synchronization raster entry is a global synchronization channel number (GSCN) of the synchronization raster entry.

[0040] In an embodiment, the method further includes receiving, from a base station, a higher layer parameter ssbFrequency including the frequency position of the SS / PBCH block.

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

[0042] In one embodiment, a user equipment (UE) in a wireless communication system is provided. The UE includes: a transceiver; and at least one processor operatively 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 in a case where a frequency position of the detected SS / PBCH block does not correspond to a frequency position of a synchronization raster entry, determine 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, where the first offset is configured by a master information block MIB in the detected SS / PBCH block, and where 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 raster entry.

[0043] 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 a frequency position of a synchronization signal and a physical broadcast channel (SS / PBCH) block, and a transceiver operatively connected to the processor, the transceiver being configured to receive an SS / PBCH block from a base station (BS). The processor of the UE is further configured to: determine whether the frequency position of the SS / PBCH block corresponds to a global synchronization channel number (GSCN) of a synchronization raster entry; if the frequency position of the SS / PBCH block does not correspond to the GSCN of the synchronization raster entry, determine the offset as a sum of a first offset and a second offset, and the offset is a difference between a minimum resource block (RB) index of a control resource set (CORESET) of a common search space (CSS) set for a Type0 physical downlink control channel (Type0-PDCCH) and a minimum RB index of a common RB overlapping with a first RB of the SS / PBCH block.

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

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

[0046] 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.

[0047] In an embodiment, the processor is further configured to identify a second offset, which is determined as the offset from the minimum resource block (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 global synchronization channel number (GSCN) of a synchronization raster entry.

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

[0049] In an embodiment, the first offset, the second offset, and the SS / PBCH block assumed to be located at the GSCN of the synchronization raster entry are identified based on the subcarrier spacing of a control resource set (CORESET) for a Type0-PDCCH common search space (CSS) set.

[0050] 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 a 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 the global synchronization channel number (GSCN) of a synchronization raster entry; if the frequency position of the SS / PBCH block does not correspond to the GSCN of the synchronization raster entry, determining the offset as the sum of a first offset and a second offset; and the offset is the difference between the 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 and the minimum RB index of a common RB overlapping with the first RB of the SS / PBCH block.

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

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

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

[0054] In an embodiment, a second offset is identified, which is determined as the offset from the minimum resource block (RB) index of a common RB that overlaps with the first RB of an SS / PBCH block to the minimum RB index of a common RB that overlaps with the first RB of another SS / PBCH block assumed to be located at the global synchronization channel number (GSCN) of a synchronization raster entry.

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

[0056] In an embodiment, the first offset, the second offset, and the SS / PBCH block assumed to be located at the GSCN of a synchronization raster entry are identified based on the subcarrier spacing of a control resource set (CORESET) for a Type0-PDCCH common search space (CSS) set.

[0057] 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 the 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 the global synchronization channel number (GSCN) of a synchronization raster entry; and if the frequency position of the SS / PBCH block does not correspond to the GSCN of a synchronization raster entry, determining an offset as the sum of a first offset and a second offset, where the offset is the difference between the 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 and the minimum RB index of a common RB that overlaps with the first RB of the SS / PBCH block.

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

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

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

[0061] In an embodiment, the method further includes identifying a second offset, which is determined as the offset from the minimum resource block (RB) index of a common RB that overlaps with the first RB of an SS / PBCH block to the minimum RB index of a common RB that overlaps with the first RB of another SS / PBCH block assumed to be located at the GSCN of a synchronization raster entry, where: the synchronization raster entry is determined as a single entry within a bandwidth for shared spectrum channel access operation; and the bandwidth includes SS / PBCH blocks.

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

[0063] Based on the following figures, description, and claims, other technical features may be clear to those skilled in the art.

[0064] Before the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with each other. The terms "transmit," "receive," and "communicate" and their derivatives include both direct and indirect communication. The terms "include" and "comprise" and their derivatives mean including without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with" and its derivatives mean including, being included within, interconnected with, containing, being contained within, connected to or coupled with, communicable with, cooperating with, interlacing, juxtaposing, adjacent to, bound to or bound with, having, having the property of, related to, etc. The term "controller" refers to any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or in a combination of hardware and software and / or firmware. The functions associated with any particular controller may 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 item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0065] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of the one or more computer programs being formed of computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof that are adapted to be implemented in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drives, compact discs (CDs), digital versatile discs (DVDs), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored and media such as rewritable optical discs or erasable memory devices in which data can be stored and then overwritten.

[0066] Definitions of 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 the prior and future use of such defined words and phrases.

[0067] Wireless communication systems have evolved from providing initial voice-oriented services to broadband wireless communication systems that provide, for example, 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 standards are being developed in conjunction with 5G wireless communication systems.

[0068] In the following, one or more embodiments will be described with reference to the accompanying drawings. Further, in the description of the present disclosure, when a specific detailed explanation of a relevant function or configuration may unnecessarily obscure the essence of the present disclosure, such detailed explanations are omitted. All terms used herein, including descriptive or technical terms, should be construed as having meanings that are obvious to those of ordinary skill in the art. However, depending on the intention of those of ordinary skill in the art, precedent, or the emergence of new technologies, these terms may have different meanings. Therefore, the terms used herein must be defined based on the meanings of these terms and the description throughout the specification. In the following, a base station may be a subject that performs resource allocation for a terminal and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a radio access unit, a base station controller, and a node on a network. A 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 communication functions, and the like. In the present disclosure, DL is a radio transmission path of a signal transmitted from a base station to a terminal, and UL is a radio transmission path of a signal transmitted from a terminal to a base station. Throughout the specification, a layer (or layer device) may also be referred to as an entity. Further, in the following, one or more embodiments of the present disclosure will be described as an example of an LTE or LTE-A system, but the one or more embodiments may also be applied to other communication systems having a similar technical background or channel form. For example, it may include 5G mobile communication technology (5G, New Radio (NR)) developed after LTE-A. Further, according to those skilled in the art, one or more embodiments may be applied to other communication systems with some modifications within the scope of the present disclosure without departing from the scope of the present disclosure.

[0069] In an 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 radio link through which a terminal, UE, or MS transmits data or a control signal to a BS or gNode B, and DL refers to a radio link through which a BS transmits data or a control signal to a terminal. In such a multiple access scheme, data or control information for each user is classified by generally allocating and operating the data or control information such that the time-frequency resources used for transmitting data or control information for each user do not overlap with each other, that is, orthogonality is established.

[0070] 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 a wireless communication system, rather than an LTE or LTE-A system.

[0071] The following discussion Figures 1 to 17Moreover, the various embodiments used in this patent document to describe the principles of the present disclosure are merely exemplary and should not be construed in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0072] 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".

[0073] The following Figures 1 - 3 describes various embodiments implemented in a wireless communication system and implemented using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The description of Figures 1 - 3 does not imply a physical or architectural limitation on the ways in which different embodiments can be implemented. Different embodiments of the present disclosure can be implemented in any appropriately arranged communication system.

[0074] Figure 1 illustrates an example wireless network according to an embodiment of the present disclosure. Figure 1 The illustrated embodiment of the wireless network is for illustrative purposes only. Other embodiments of the wireless network 100 can be used without departing from the scope of the present disclosure.

[0075] As Figure 1 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 networks.

[0076] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UEs) within coverage area 120 of gNB 102. The first plurality of UEs includes UE 111, which may be located in a small business; 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 computer, 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 includes 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.

[0077] 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. A 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), LTE-Advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.). For convenience, the terms "BS" and "TRP" may be used interchangeably in this patent document to refer to the network infrastructure components that provide wireless access to remote terminals. Additionally, 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 remote wireless devices that wirelessly access a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or a device that is typically considered fixed (such as a desktop computer or a vending machine).

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

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

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

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

[0086] Controller / processor 225 is also capable of executing programs and other processes residing in memory 230, such as an OS. Controller / processor 225 may move data into or out of memory 230 as needed for the execution of processes.

[0087] 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 via 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 via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure that supports communication via a wired or wireless connection, such as an Ethernet or RF transceiver.

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

[0089] Although Figure 2 one example of the gNB 102 is shown, various changes may be made Figure 2 thereto. For example, the gNB 102 may include Figure 2 any number of each of the components shown. As a specific example, an 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 circuitry 215 and a single instance of the RX processing circuitry 220, the gNB 102 may include multiple instances of each (such as one instance per RF transceiver). Additionally, Figure 2 the various components in

[0090] Figure 3 Figure 3 Figure 1 The example UE 116 shown is for illustration only, and Figure 3 the UEs 111 - 115 may have the same or similar configurations. However, UEs have a wide variety of configurations, and

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

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

[0093] The TX processing circuit 315 receives analog or digital voice data from the microphone 320, or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing 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 transmitted via the antenna 305.

[0094] The processor 340 may include one or more processors or other processing devices, and executes 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 RF transceiver 310, the RX processing circuit 325, and the TX processing circuit 315 to receive forward channel signals and transmit reverse channel signals according to well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0095] 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 execution of the processes. In some embodiments, the processor 340 is configured to execute the application 362 based on the OS 361 or in response to signals received from the gNB or the operator. The processor 340 is also coupled to an I / O interface 345, which provides the UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0096] The processor 340 is also coupled to a touch screen 350 and a display 355. An operator of the UE 116 can use the touch screen 350 to input data into the UE 116. The display 355 can be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics such as from a website.

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

[0098] Although Figure 3 an example of the UE 116 is shown, various changes may be made Figure 3 to it. For example, Figure 3 the various components in it can be combined, further subdivided, or omitted, and additional components can be added according to specific requirements. As a specific example, the processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Additionally, although Figure 3 the UE 116 is shown configured as a mobile phone or smartphone, the UE can be configured to operate as other types of mobile or fixed devices.

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

[0100] In order to meet the demand for increased wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". The 5G communication system is considered to be implemented in a higher frequency (millimeter wave) band (e.g., 60 GHz band) 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 technologies have been discussed for 5G communication systems. In addition, in the 5G communication system, the development of system network improvements based on advanced small cells, cloud radio access network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-point (CoMP), receiver-side interference cancellation, etc. is underway.

[0101] A time unit used for DL signaling or UL signaling on a cell is called a time slot and may include one or more symbols. A symbol can also be an additional time unit. A frequency (or bandwidth (BW)) unit is called a resource block (RB). One RB includes multiple subcarriers (SC). For example, a time slot can include 14 symbols, have a duration of 1 millisecond or 0.5 millisecond, and an RB can have a BW of 180 kHz or 360 kHz and include 12 SCs, with the spacing between SCs being 15 kHz or 30 kHz, respectively.

[0102] DL signals include data signals that carry information content, control signals that carry DL control information (DCI) formats, and reference signals (RS) that are also referred to as pilot signals. The gNB can transmit 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 transmit one or more of various types of RSs including channel state information RS (CSI-RS) and demodulation RS (DMRS). CSI-RS is intended for the UE to measure channel state information (CSI) or perform other measurements (such as measurements related to mobility support). DMRS can only be transmitted within the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0103] The UL signal also includes a data signal for transmitting information content, a control signal for transmitting UL control information (UCI), and RS. The UE sends data information (e.g., a transport block) or UCI through a corresponding physical UL shared channel (PUSCH) or physical UL control channel. When the UE sends data information and UCI simultaneously, the UE can multiplex both the data information and UCI in the PUSCH, or send the data information and UCI separately in the corresponding PUSCH and PUCCH. The UCI includes hybrid automatic repeat request acknowledgment (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 CSI reports enabling the gNB to select appropriate parameters to perform link adaptation for PDSCH or PDCCH transmission to the UE.

[0104] The CSI report from the UE can include: a channel quality indicator (CQI) that notifies the gNB of the modulation and coding scheme (MCS) for the UE to detect a data TB with a predetermined block error rate (BLER) (such as 10% BLER); a precoding matrix indicator (PMI) that notifies the gNB of how to precode the signaling to the UE; and a rank indicator (RI) that indicates the transmission rank for the PDSCH. The UL RS includes DMRS and sounding RS (SRS). The DMRS is only sent 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 UL CSI to the gNB and, for a TDD or flexible duplex system, also provides a PMI for DL transmission. The UL DMRS or SRS transmission can be based on, for example, a transmission based on Zadoff-Chu (ZC) sequences or generally a transmission based on CAZAC sequences.

[0105] The DL transmission and UL transmission can be based on an orthogonal frequency division multiplexing (OFDM) waveform including a variant using DFT precoding (referred to as DFT-spread-OFDM).

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

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

[0108] Figure 5 An example receiver structure 500 using OFDM according to an embodiment of the present disclosure is shown. Figure 5 The illustrated embodiment of the receiver structure 500 is for illustrative purposes only. Figure 5 One or more of the illustrated components 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0109] The received signal 510 is filtered by a filter 520, the CP is removed by a CP removal unit 530, a fast Fourier transform (FFT) is applied by a filter 540, the SC selected by a BW selector unit 555 is demapped by an SC demapping unit 550, the received symbols are demodulated by a channel estimator and demodulator unit 560, the rate dematching is restored by a rate dematcher 570, and the resulting bits are decoded by a decoder 580 to provide information bits 590.

[0110] A UE generally monitors multiple candidate positions 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 formats that the UE is configured to receive. The DCI formats include cyclic redundancy check (CRC) bits so that the UE can confirm the correct detection of the DCI formats. The DCI format type is identified by a radio network temporary identifier (RNTI) that scrambles the CRC bits. For a DCI format that schedules a PDSCH or PUSCH for a single UE, the RNTI can be a cell RNTI (C-RNTI) and is used as a UE identifier.

[0111] For the DCI format of PDSCH that schedules the transmission of system information (SI), the RNTI can be the SI-RNTI. For the DCI format of PDSCH that schedules the provision of a random access response (RAR), the RNTI can be the RA-RNTI. For the DCI format that schedules PDSCH or PUSCH for a single UE before the UE establishes a radio resource control (RRC) connection with the serving gNB, the RNTI can be a temporary C-RNTI (TC-RNTI). For the DCI format that provides a TPC command for a UE group, the RNTI can be the TPC-PUSCH-RNTI or the TPC-PUCCH-RNTI. Each RNTI type can be configured for the UE via higher layer signaling (such as RRC signaling). The DCI format that schedules PDSCH transmission to the UE is also referred to as the DL DCI format or DL allocation, and the DCI format that schedules PUSCH transmission from the UE is also referred to as the UL DCI format or UL grant.

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

[0113] Figure 6 An example encoding process 600 for DCI formats according to an embodiment of the present disclosure is shown. Figure 6 The embodiment of the encoding process 600 shown is for illustration only. Figure 6 One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors that execute instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0114] The gNB separately encodes and transmits each DCI format in the corresponding PDCCH. The RNTI masks the CRC of the DCI format codeword so that the UE can identify the DCI format. For example, the CRC and the RNTI may include, for example, 16 bits or 24 bits. A CRC calculation unit 620 is used to determine the CRC of the (uncoded) 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. An encoder 660 performs channel coding (such as tail-biting convolutional coding or polar coding), and then rate matching of the allocated resources is performed by a rate matcher 670. An interleaving and modulation unit 680 applies interleaving and modulation (such as QPSK), and an output control signal 690 is transmitted.

[0115] 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 embodiment of the decoding process 700 shown is for illustration only. Figure 7 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0116] The received control signal 710 is demodulated and deinterleaved by a demodulator and deinterleaver 720. The rate matching applied at the gNB transmitter is restored 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 unit 790 performs a CRC check. When the CRC check is successful (the 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.

[0117] 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 Control Resource Set (CORESET) #0 by reading the content of the PBCH, where CORESET #0 contains the frequency-domain resources for monitoring the Physical Downlink Control Channel (PDCCH) for scheduling the RMSI.

[0118] 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 a Synchronization Grid entry, which means that the configuration of the offset between the SS / PBCH block and CORESET #0 may not be applicable to SS / PBCH blocks in NR Rel-15 that are not located on Synchronization Grid entries.

[0119] In NR Rel-16, there is a motivation to read the RMSI from an adjacent cell to resolve the confusion of the Cell Global Identity (CGI), where the adjacent cell can be a Secondary Cell (SCell), such that the SS / PBCH block in the adjacent cell may or may not be located on a Synchronization Grid entry, which gives a motivation to enhance the reception of the RMSI in NR Rel-16.

[0120] Figure 8 An example frequency-domain offset 800 between the SS / PBCH block and CORESET #0 according to an embodiment of the present disclosure is shown. Figure 8 The embodiment of the shown frequency-domain offset 800 is for illustration only. Figure 8 One or more of the shown components 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

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

[0122] The present disclosure focuses on mechanisms and methods for supporting a UE to receive the Remaining Minimum System Information (RMSI) from an adjacent 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.

[0123] In one embodiment, the UE can be configured by the gNB to monitor Type0-PDCCH and decode the corresponding RMSI's PDSCH when successfully decoding the Type0-PDCCH in the cell.

[0124] In one example, the UE can be configured with at least the frequency position of the SS / PBCH block, where the Type0-PDCCH and the corresponding RMSI are quasi-co-located with the SS / PBCH block. For example, this example applies to the scenario where the UE is configured by the gNB to read the content of the RMSI (e.g., from an adjacent cell).

[0125] In one example, in addition to the configured frequency position of the SS / PBCH block, the subcarrier spacing (SCS) of the SS / PBCH block is also configured for the UE.

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

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

[0128] In yet another example, in addition to the configured frequency position of the SS / PBCH block, a frequency offset is also configured for 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.

[0129] In yet another example, in addition to the configured frequency position of the SS / PBCH block, a second frequency position is also configured for the UE, where 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 raster entry (e.g., defined by a GSCN value).

[0130] In one example, the UE can determine a frequency domain offset (e.g., represented as 0) based on the detected MIB of the 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 with the first RB of the detected SS / PBCH block is the same as the determined frequency domain offset (e.g., O).

[0131] In one example, the frequency-domain difference between the lowest resource block (RB) of the SS / PBCH block and the lowest RB of CORESET #0 (e.g., via the master information block (MIB)) is directly configured for the user equipment (UE), regardless of whether the SS / PBCH block is located on a synchronization raster entry.

[0132] In another example, the frequency offset can potentially be jointly coded 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 two groups: one group corresponds to the SS / PBCH blocks located on the synchronization raster entries, and the other group corresponds to the SS / PBCH blocks not located on the synchronization raster entries.

[0133] In yet another example, the first group of offsets is applicable only to the primary cell (PCell) and / or the primary-secondary cell (PSCell), e.g., only for the purpose of initial cell search. In yet another example, the second group of offsets can be applicable to any cell (e.g., one of the PCell, secondary cell (SCell), or PSCell).

[0134] Figure 9 FIG. 900 is a flow chart of a UE process for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure. Figure 9 The embodiment of the UE process 900 shown is for illustrative purposes only. Figure 9 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0135] As Figure 9 shown, the UE process 900 begins 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.

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

[0137] In one example, BW_CORESET is the bandwidth 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 bandwidth of the SS / PBCH block, e.g., 20 RBs.

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

[0139] 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 30 kHz. In one aspect, e.g., during the initial cell search process, on the PCell and / or PSCell, only the configurations with indices 0 and 2 are expected by the UE. 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 30 kHz.

[0140]

Table 1

[0141] Index SS / PBCH block and CORESET multiplexing pattern CORESET bandwidth (e.g., BW_CORESET in terms of RBs) Number of symbols of the CORESET Offset (e.g., O in terms of RBs) 0 1 48 1 0 1 1 48 1 28 2 1 48 2 0 3 1 48 2 28

[0142] 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 15 kHz. In one aspect, (e.g., during the initial cell search process) on the PCell and / or PSCell, only the configurations with indices 0 and 2 are expected by the UE. 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 15 kHz.

[0143]

Table 2

[0144] Index SS / PBCH block and CORESET multiplexing pattern CORESET bandwidth (e.g., BW_CORESET in terms of RBs) Number of symbols of the CORESET Offset (e.g., O in terms of RBs) 0 1 96 1 0 1 1 96 1 76 2 1 96 2 0 3 1 96 2 76

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

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

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

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

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

[0150] In another example, there may be more than two candidate frequency offset values. For one instance, if the detected SS / PBCH block is on a synchronization raster 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 a synchronization raster entry, at least one of the remaining frequency offset values may be used. For another instance, if the detected SS / PBCH block is within a range from the synchronization raster entry, at least one of the frequency offset values (e.g., 0 RBs) may be used, and if the detected SS / PBCH block is outside the range from the synchronization raster entry, at least one of the remaining frequency offset values may be used.

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

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

[0153] 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 30 kHz. In one aspect, on the PCell and / or PSCell (e.g., during the initial cell search process), only the configurations with indexes 0 and 3 are expected by the UE. 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 15 kHz.

[0154]

Table 3

[0155] Index SS / PBCH block and CORESET multiplexing pattern CORESET bandwidth (e.g., BW_CORESET in terms of RBs) Number of symbols of the CORESET Offset (e.g., O in terms of RBs) 0 1 48 1 0 1 1 48 1 14 2 1 48 1 28 3 1 48 2 0 4 1 48 2 14 5 1 48 2 28

[0156] 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 15 kHz. In one aspect, on the PCell and / or PSCell (e.g., during the initial cell search process), only the configurations with indexes 0 and 3 are expected by the UE. 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 15 kHz.

[0157]

Table 4

[0158] Index SS / PBCH block and CORESET multiplexing pattern CORESET bandwidth (e.g., BW_CORESET in terms of RBs) Number of symbols of the CORESET Offset (e.g., O in terms of RBs) 0 1 96 1 0 1 1 96 1 38 2 1 96 1 76 3 1 96 2 0 4 1 96 2 38 5 1 96 2 76

[0159] Table 5 shows an example configuration table in the MIB when the SCS of the SS / PBCH block and the SCS of CORESET #0 are both 30 kHz. A set or subset of entries can be used. In one aspect, (e.g., during the initial cell search process) on the PCell and / or PSCell, only the configurations with indices 0 and 8 are expected by the UE. Note that the interval between the 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 30 kHz, BW_CH - BW_CORESET + 1 = 51 - 48 + 1 = 4 RBs. Table 5 is an example configuration table in the MIB when the SCS of the SS / PBCH block and the SCS of CORESET #0 are both 30 kHz.

[0160]

Table 5

[0161] Index SS / PBCH block and CORESET multiplexing pattern CORESET bandwidth (e.g., BW_CORESET in terms of RBs) Number of symbols of the CORESET Offset (e.g., O in terms of RBs) 0 1 48 1 0 1 1 48 1 4 2 1 48 1 8 3 1 48 1 12 4 1 48 1 16 5 1 48 1 20 6 1 48 1 24 7 1 48 1 28 8 1 48 2 0 9 1 48 2 4 10 1 48 2 8 11 1 48 2 12 12 1 48 2 16 13 1 48 2 20 14 1 48 2 24 15 1 48 2 28

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

[0163]

Table 6

[0164] Index SS / PBCH block and CORESET multiplexing pattern CORESET bandwidth (e.g., BW_CORESET in terms of RBs) Number of symbols of the CORESET Offset (e.g., O in terms of RBs) 0 1 96 1 0 1 1 96 1 12 2 1 96 1 24 3 1 96 1 38 4 1 96 1 52 5 1 96 1 64 6 1 96 1 76 7 1 96 2 0 8 1 96 2 12 9 1 96 2 24 10 1 96 2 38 11 1 96 2 52 12 1 96 2 64 13 1 96 2 76

[0165] 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 15 kHz. A set or subset of entries can be used. In one aspect, (e.g., during the initial cell search process) on the PCell and / or PSCell, only the configurations with indices 0 and 8 are expected by the UE. Note that the interval between the offset values is at most 11 RBs, which corresponds to the flexibility of reusing the configuration by shifting CORESET #0 within the carrier, where this 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 15 kHz, 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 15 kHz.

[0166]

Table 7

[0167] Index SS / PBCH block and CORESET multiplexing pattern CORESET bandwidth (e.g., BW_CORESET in terms of RBs) Number of symbols of the CORESET Offset (e.g., O in terms of RBs) 0 1 96 1 0 1 1 96 1 11 2 1 96 1 22 3 1 96 1 33 4 1 96 1 44 5 1 96 1 55 6 1 96 1 66 7 1 96 1 76 8 1 96 2 0 9 1 96 2 11 10 1 96 2 22 11 1 96 2 33 12 1 96 2 44 13 1 96 2 55 14 1 96 2 66 15 1 96 2 76

[0168] 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 15 kHz. A set or subset of entries can be used. In one aspect, (e.g., during the initial cell search process) on the PCell and / or PSCell, only the configurations with indices 0 and 8 are expected by the UE. Note that the interval between the offset values is at most 11 RBs, which corresponds to the flexibility of reusing the configuration by shifting CORESET #0 within the carrier, where this 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 15 kHz, 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 15 kHz.

[0169]

Table 8

[0170] Index SS / PBCH block and CORESET multiplexing pattern CORESET bandwidth (e.g., BW_CORESET in terms of RBs) Number of symbols of the CORESET Offset (e.g., O in terms of RBs) 0 1 96 1 0 1 1 96 1 11 2 1 96 1 22 3 1 96 1 33 4 1 96 1 43 5 1 96 1 54 6 1 96 1 65 7 1 96 1 76 8 1 96 2 0 9 1 96 2 11 10 1 96 2 22 11 1 96 2 33 12 1 96 2 43 13 1 96 2 54 14 1 96 2 65 15 1 96 2 76

[0171] In one example, a UE may determine a frequency-domain offset (e.g., denoted 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 that overlaps with the first RB of the detected SS / PBCH block based on the determined frequency-domain offset (e.g., O).

[0172] 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 that overlaps with the first RB of the detected SS / PBCH block is determined as the sum (e.g., O+X) of a first frequency-domain offset (e.g., O) determined according to the MIB and a second frequency-domain offset (e.g., denoted as X) calculated by the UE, where the offset is defined for the SCS of the CORESET for the Type0-PDCCH CSS set. In one example, X may 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.

[0173] Figure 10A A flowchart of a UE procedure 1000 for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure is shown. Figure 10A The illustrated embodiment of the UE procedure 1000 is for illustrative purposes only. Figure 10A One or more of the illustrated components 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0174] As Figure 10A As shown, the UE procedure begins 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 a 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.

[0175] Figure 10B A flowchart of a UE procedure 1050 for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure is shown. Figure 10B The illustrated embodiment of the UE procedure 1050 is for illustrative purposes only.Figure 10B One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0176] As Figure 10B shown, UE procedure 1050 starts at step 1011. At step 1011, the UE determines the frequency position of the SS / PBCH block. At step 1012, the UE detects the SS / PBCH block. At step 1013, the UE obtains the configuration of the first frequency domain offset according to the MIB. At step 1014, the UE determines whether the detected SS / PBCH block is on the synchronization grid entry. At step 1014, if the UE determines that the detected SS / PBCH block is on the synchronization grid entry, UE procedure 1050 proceeds to step 1015. At step 1014, if the UE determines no, UE procedure 1050 proceeds to step 1016. At 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. At 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, at 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.

[0177] Figure 10A Or Figure 10B illustrates a diagram of an example UE procedure for determining the frequency position of CORESET #0. Note that if the second offset is calculated as 0 when the detected SS / PBCH block is on the synchronization grid entry, Figure 10A and Figure 10B can be equivalent.

[0178] Figure 11 illustrates the relationship 1100 between example frequency offsets according to an embodiment of the present disclosure. Figure 11 The embodiment of the relationship 1100 between the frequency offsets shown in is for illustration only. Figure 11 One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0179] Figure 11 illustrates the relationship between the frequency offsets in the above examples and / or instances.

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

[0181] In another example, the reference frequency position can be selected as a synchronization raster 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 30 kHz SCS or 96 RBs for 15 kHz SCS), and BW_SSB is the BW of the SSB (e.g., 20 RBs).

[0182] In yet another example, the reference frequency position can be selected as the synchronization raster entry that is closest and has a lower frequency compared to the frequency position of the detected SS / PBCH block.

[0183] In yet another example, the reference frequency position can be selected as the synchronization raster entry that is closest and has a higher frequency compared to the frequency position of the detected SS / PBCH block.

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

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

[0186] In yet another example, the reference frequency position can be selected as the position (e.g., GSCN value) configured by the gNB.

[0187] In one example, the UE first determines the frequency position for detecting the SS / PBCH block (e.g., this frequency position can be configured by the gNB via the higher layer parameter ssbFrequency), and reads the MIB of the detected SS / PBCH block to obtain the first frequency offset (e.g., from the field of controlResourceSetZero in pdcch-ConfigSIB1), and calculates the second frequency offset based on the difference between the frequency position of the detected SS / PBCH block and the synchronization raster entry (in terms of RB with respect 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 with 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.

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

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

[0190] In yet another instance, the second frequency offset (e.g., X) can be determined as the offset from the RB index of the common RB overlapping with the frequency position of the detected SS / PBCH block (e.g., the higher layer parameter ssbFrequency) to the RB index of the common RB overlapping with the reference frequency position (e.g., the synchronization raster entry within the same rated carrier / subband / LBT bandwidth where channel sensing is performed).

[0191] In yet another example, the second frequency offset can be determined by the following 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 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., 15 kHz or 30 kHz), and N_RE is the number of REs in terms of RBs (e.g., N_RE = 12).

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

[0193] In one example, the second frequency offset (e.g., X) can be negative (e.g., F_REF < SS_REF).

[0194] 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 30 kHz SCS or 96 RBs for 15 kHz SCS), and BW_SSB is the BW of the SSB (e.g., 20 RBs).

[0195] 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 rated carrier / subband / LBT bandwidth where channel sensing is performed (e.g., 51 RBs for 30 kHz SCS or 106 RBs for 15 kHz SCS), and BW_SSB is the BW of the SSB (e.g., 20 RBs). In yet another aspect, this example is applicable to the scenario where the SS / PBCH blocks with 30 kHz SCS and 15 kHz SCS are located at the same reference frequency position (synchronization raster entry) when determining the frequency offset configuration for the PCell and / or PSCell. Figure 12 A diagram illustrating this scenario is shown.

[0196] Figure 12 An example SS / PBCH block 1200 with 30 kHz SCS and 15 kHz SCS located at the same reference frequency position according to an embodiment of the present disclosure is shown. Figure 12The illustrated embodiment of the SS / PBCH block 1200 is for illustration only. Figure 12 One or more of the illustrated components 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0197] In one example, the second frequency offset can be determined by the 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 the example, such as the reference frequency position of this example), SCS_CORESET is the SCS of CORESET #0 (e.g., 15 kHz or 30 kHz), and N_RE is the number of REs in terms of RBs (e.g., N_RE = 12). "floor(x)" refers to the floor operation that gives the largest integer less than or equal to x.

[0198] In one example, the UE desired 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 30 kHz SCS or 96 RBs for 15 kHz SCS), and BW_SSB is the BW of the SSB (e.g., 20 RBs).

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

[0200] In one example, 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 raster entry (in the example, such as the reference frequency position of this example), SCS_CORESET is the SCS of CORESET #0 (e.g., 15 kHz or 30 kHz), and N_RE is the number of REs in terms of RBs (e.g., N_RE = 12).

[0201] In one example, the UE desired 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).

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

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

[0204] 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 * 15 kHz / 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 grid entry (in the example, like the reference frequency position of this instance), 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), and N_SC is the remaining number of subcarriers calculated based on the offset given by: 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).

[0205] "floor(x)" refers to the floor operation that gives the largest integer less than or equal to x. In one instance, 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).

[0206] In another 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 rated carrier / subband / LBT bandwidth in which channel sensing is performed (e.g., 51 RBs for 30kHz SCS or 106 RBs for 15kHz SCS), and BW_SSB is the BW of the SSB (e.g., 20 RBs). In another aspect, this instance applies to the scenario where the SS / PBCH blocks with 30kHz SCS and 15kHz SCS are located at the same reference frequency position (synchronization grid entry) when determining the frequency offset configuration for the PCell and / or PSCell. Figure 12 A diagram illustrating this scenario is shown.

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

[0208] Figure 13 An example SS / PBCH block 1300 with an SCS of 30 kHz and an SCS of 15 kHz located at different reference frequency positions according to an embodiment of the present disclosure is shown. Figure 13 The embodiment of the shown SS / PBCH block 1300 is for illustration only. Figure 13 One or more of the shown components can be implemented in a dedicated circuit configured to perform the function, or one or more of the components can be implemented by one or more processors executing instructions to perform the function. Other embodiments are used without departing from the scope of the present disclosure.

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

[0210] In one example, X' = 10 RBs, such that the lowest boundaries of the 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 15 kHz and located on the synchronization raster entry to the channel boundary, e.g., X' = 13 RBs.

[0211] In one example, the UE can determine the frequency domain offset (e.g., denoted as O) based on the detected MIB of the SS / PBCH block, and 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 with the first RB of the detected SS / PBCH block based on the determined frequency domain offset (e.g., O).

[0212] 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.

[0213] Figure 14 FIG. 1400 is a flow chart of a UE process for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure. Figure 14 The embodiment of the UE process 1400 shown is for illustrative purposes only. Figure 14 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0214] As Figure 14 As shown, the UE process 1400 begins at step 1401. In step 1401, the UE determines the frequency position 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.

[0215] 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 to be the determined frequency domain offset + X (e.g., O + X), where X is a fixed value, e.g., fixed for the SCS of each SS / PBCH block.

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

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

[0218] In yet another sub-example, for the SCS of the SS / PBCH block with 30 kHz, X = 24.

[0219] In yet another sub-example, for the SCS of the SS / PBCH block with 15 kHz, X = 48.

[0220] In yet another sub-example, for the SCS of the SS / PBCH block with 30 kHz, X = 14.

[0221] In yet another sub - example, for the SCS of the SS / PBCH block being 15 kHz, X = 38.

[0222] 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 - the frequency - domain - determined offset (e.g., X - O), where X is a fixed value, e.g., fixed for each SCS of the SS / PBCH block.

[0223] In one sub - example, for the SCS of the SS / PBCH block being 30 kHz, X = 48.

[0224] In another sub - example, for the SCS of the SS / PBCH block being 15 kHz, X = 96.

[0225] In yet another sub - example, for the SCS of the SS / PBCH block being 30 kHz, X = 28.

[0226] In yet another sub - example, for the SCS of the SS / PBCH block being 15 kHz, X = 76.

[0227] In one example, when the UE is configured to detect the SS / PBCH block, the UE can be configured with a frequency - domain offset (e.g., O_SSB), and the UE 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 that overlaps with the first RB of the detected SS / PBCH block based on the configured frequency - domain offset (e.g., O_SSB).

[0228] In one example, 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 that overlaps with the first RB of the detected SS / PBCH block as the configured frequency - domain offset (e.g., O_SSB).

[0229] In one example, the UE still needs to read the content of the PBCH of the detected SS / PBCH block to determine the number of symbols for CORESET #0, and cover the frequency - domain offset (e.g., O) configured in the MIB of the detected SS / PBCH block by 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 that overlaps with the first RB of the detected SS / PBCH block.

[0230] In one example, the above example can be combined with the examples and / or methods mentioned in this disclosure. If a frequency offset configuration (e.g., O_SSB) is provided to the UE, 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 that overlaps with 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 that overlaps with the first RB of the detected SS / PBCH block as the sum of two offsets, where 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 this disclosure.

[0231] Figure 15A An example of the UE procedure for this aspect of this example is shown.

[0232] Figure 15A A flowchart of a UE procedure 1500 for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure is shown. Figure 15A The embodiment of the UE procedure 1500 shown is for illustration only. Figure 15A One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0233] As Figure 15AAs shown, UE procedure 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, UE procedure 1500 proceeds to step 1507. In step 1503, if the UE determines that no frequency domain offset is provided to the UE, UE procedure 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, UE procedure 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, UE procedure 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 the 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 the 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.

[0234] 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 that overlaps with the first RB of the detected SS / PBCH block as the sum of a first offset as the 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.

[0235] 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.

[0236] In one example, the above examples may be combined with the examples and / or instances mentioned in this disclosure. If a frequency offset configuration (e.g., O_SSB) is provided to the UE, the UE may determine a second offset that constitutes 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 that overlaps with 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 that constitutes 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 that overlaps with 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 this disclosure. Figure 15B An example of the UE procedure for this aspect of this example is shown.

[0237] Figure 15B Another flowchart of the UE procedure 1550 for determining the frequency position of CORESET #0 according to an embodiment of this disclosure is shown. Figure 15B The embodiment of the UE procedure 1550 shown is for illustration only. Figure 15B 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of this disclosure.

[0238] As Figure 15BAs shown, UE procedure 1550 starts at step 1511. In step 1511, the UE determines the frequency position 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 a synchronization raster entry. In step 1514, if the UE determines that the detected SS / PBCH block is on a synchronization raster entry, then UE procedure 1550 proceeds to step 1515. In step 1514, if the UE determines that the detected SS / PBCH block is not on a synchronization raster entry, then UE procedure 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 a 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, then UE procedure 1550 proceeds to step 1517. In step 1516, if the UE determines that no frequency-domain offset is provided to the UE, then UE procedure 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.

[0239] In one example, 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 that overlaps with the first RB of the detected SS / PBCH block based on whether the detected SS / PBCH block is located on (or within the range of) a synchronization raster entry.

[0240] In one example, if the UE determines that the detected SS / PBCH block is located on (or within the range of) a synchronization raster entry, the UE 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 that overlaps with the first RB of the detected SS / PBCH block according to the 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 (or outside the range of) a synchronization raster entry, the UE 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 that overlaps with the first RB of the detected SS / PBCH block as the second frequency domain offset.

[0241] Figure 16 FIG. 1600 is a flowchart of a UE procedure for determining the frequency position of CORESET #0 according to an embodiment of the present disclosure. Figure 16 The embodiment of the UE procedure 1600 shown is for illustrative purposes only. Figure 16 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 executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0242] As Figure 16 As shown, the UE procedure 1600 begins 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 a synchronization raster entry. In step 1604, if the UE determines that the detected SS / PBCH block is on a synchronization raster entry, the UE procedure 1600 proceeds to step 1605. In step 1604, if the UE determines that the detected SS / PBCH block is not on a synchronization raster entry, the UE procedure 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.

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

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

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

[0246] In one example, the second frequency-domain offset and the first frequency-domain offset (e.g., the first frequency offset denoted as O) may have a one-to-one mapping.

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

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

[0249] In one example, the second frequency-domain offset is determined according to a separate configuration table, which 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.

[0250] In one example, the second frequency-domain offset is configured by the gNB, e.g., associated with the configured frequency position of the detected SS / PBCH block.

[0251] Figure 17 A flowchart of a method 1700 for receiving RMSI according to an embodiment of the present disclosure is shown. The method 1700 may be performed by a user equipment (UE) (e.g., as Figure 1 shown by 111 - 116). Figure 17 The embodiments of the method 1700 shown are for illustration only. Figure 17 One or more of the components shown may be implemented in a dedicated circuit configured to perform the function, or one or more of the components may be implemented by one or more processors that execute instructions to perform the function. Other embodiments are used without departing from the scope of the present disclosure.

[0252] As Figure 17 shown, method 1700 begins at step 1702. In step 1702, a UE supporting shared spectrum channel access identifies the frequency location of a Synchronization Signal and Physical Broadcast Channel (SS / PBCH) block.

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

[0254] Next, in step 1706, the UE determines whether the frequency location of the SS / PBCH block corresponds to the Global Synchronization Channel Number (GSCN) of a synchronization grid entry.

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

[0256] In one embodiment, in step 1708, the offset is the difference between the 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 and the minimum RB index of a common RB that overlaps the first RB of the SS / PBCH block.

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

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

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

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

[0261] In one embodiment, the UE identifies a second offset that is determined as the offset from the minimum RB index of a common RB that overlaps with the first RB of the SS / PBCH block to the minimum RB index of a common RB that overlaps with the first RB of the SS / PBCH block assumed to be at the GSCN of the synchronization raster entry.

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

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

[0264] The above UE may correspond to Figure 18 the UE of.

[0265] Referring to Figure 18 , the UE may include a processor 1805, a transceiver 1810, and a memory 1815. However, not all of the illustrated components are required. The UE may be implemented by more or fewer components than Figure 18 shown. Additionally, according to another embodiment, the processor 1805, the transceiver 1810, and the memory 1815 may be implemented as a single chip.

[0266] The above components will now be described in detail.

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

[0268] The processor 1805 may detect the PDCCH on the configured control resource set. The processor 1805 determines a method for dividing the CB and a 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.

[0269] The transceiver 1810 may include an RF transmitter for upconverting and amplifying the transmitted signal, and an RF receiver for downconverting the frequency of the received signal. However, according to another embodiment, the transceiver 1810 may be implemented by more or fewer components than those shown in the components.

[0270] The transceiver 1810 can be connected to the processor 1805 and send and / or receive signals. The signals can include control information and data. In addition, the transceiver 1810 can receive signals via a wireless channel and output the signals to the processor 1805. The transceiver 1810 can send the signals output from the processor 1805 via a wireless channel.

[0271] The memory 1815 can store the control information or data included in the signals obtained by the UE. The memory 1815 can be connected to the processor 1805 and store at least one instruction or protocol or parameters for the proposed functions, processes, and / or methods. The memory 1815 can 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.

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

[0273] The above BS can correspond to Figure 19 the BS of

[0274] Reference Figure 19 , the base station can include a processor 1905, a transceiver 1910, and a memory 1915. However, not all of the illustrated components are required. The base station can be implemented with more or fewer components than Figure 19 shown. In addition, according to another embodiment, the processor 1905, the transceiver 1910, and the memory 1915 can be implemented as a single chip.

[0275] The above components will now be described in detail.

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

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

[0278] The transceiver 1910 can be connected to the processor 1905 and send and / or receive signals. The signals can include control information and data. In addition, the transceiver 1910 can receive signals via a wireless channel and output the signals to the processor 1905. The transceiver 1910 can send the signals output from the processor 1905 via a wireless channel.

[0279] The memory 1915 may store control information or data included in the signals obtained by the BS. The memory 1915 may be connected to the processor 1905 and store at least one instruction or protocol or parameters for the proposed functions, processes, and / or methods. 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.

[0280] 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 that fall within the scope of the appended claims. Any description in this application should not be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the claimed subject matter is defined by the claims.

[0281] Those skilled in the art can understand that all or part of the steps implemented by the above method embodiments can be realized by a program through hardware associated with commands. The program can be stored in a computer-readable storage medium. When the program is executed, one or a combination of the steps of the method embodiments is also included.

[0282] In addition, the functional units in various embodiments of this application can be integrated in a processing module, or each unit can physically exist 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.

[0283] Although the present invention has been specifically shown and described with reference to exemplary embodiments of the present invention, those skilled in the art will understand that various changes can be made in form and detail without departing from the spirit and scope of the present invention defined by the appended claims.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising: Detecting a synchronization signal and a physical broadcast channel block SS / PBCH block; 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; And Wherein, when the SS / PBCH block is located at a frequency position of a synchronization grid entry, the offset is identified based on a first offset, and Based on the identified offset, monitoring the Type0-PDCCH, Wherein the first offset is configured based on a master information block MIB in the SS / PBCH block.

2. The method according to claim 1, wherein When the SS / PBCH block is not located at the frequency position of the synchronization grid entry, the offset is identified based on the sum of the first offset and a second offset.

3. The method according to claim 2, wherein The second offset is identified based on an offset from a minimum RB index of a common RB overlapping with a first RB of the 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 the frequency position of the synchronization grid entry.

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

5. A user equipment UE in a wireless communication system, the UE comprising: A transceiver; And At least one processor coupled to the transceiver and configured to: Detect a synchronization signal and a physical broadcast channel block SS / PBCH block; 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; And Wherein, when the SS / PBCH block is located at a frequency position of a synchronization grid entry, the offset is identified based on a first offset, and Based on the identified offset, monitoring the Type0-PDCCH, Wherein the first offset is configured based on a master information block MIB in the SS / PBCH block.

6. The UE according to claim 5, wherein, When the SS / PBCH block is not located at the frequency position of the synchronization grid entry, the offset is identified based on the sum of the first offset and a second offset.

7. The UE according to claim 6, wherein, The second offset is identified based on an offset from a minimum RB index of a common RB overlapping with a first RB of the 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 the frequency position of the synchronization grid entry.

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

Images