Method and apparatus for CORESET configuration in an unlicensed frequency band

Abstract

The present disclosure relates to a communication method and system for fusing a fifth-generation (5G) communication system supporting a higher data rate beyond a fourth-generation (4G) system with Internet of Things (IoT) technologies. The present disclosure may be applied to intelligent services based on 5G communication technologies and IoT-related technologies, such as smart home, smart building, smart city, smart car, connected car, healthcare, digital education, smart retail, security, and safety services. The present disclosure provides a method and an apparatus in a wireless communication system.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication systems, and more particularly, to control resource set (CORESET) configuration on an unlicensed frequency band. Background Art

[0002] 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. Therefore, 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post-LTE systems". The 5G communication system is considered to be implemented in a higher frequency (mmWave) band (e.g., 60 GHz band) in order to achieve higher data rates. 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 are discussed in the 5G communication system. In addition, in the 5G communication system, the development of system network improvement has been carried out 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 interference cancellation, and so on. In the 5G system, hybrid FSK and QAM amplitude modulation (FQAM) as advanced coding modulation (ACM) and sliding window superposition coding (SWSC), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0003] The Internet, a human-centered connectivity network in which people generate and use 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, which is a combination of IoT technology and big data processing technology realized through connection to a cloud server. Since technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology" have been required for IoT implementation, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), and so on have been recently studied. Such an IoT environment can provide intelligent Internet technology services, which create new value for human life by collecting and analyzing data generated between connected things. The IoT can be applied to a variety of fields, including smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliances, and advanced medical services, through the integration and combination of existing information technology (IT) and various industrial applications.

[0004] Accordingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communication (MTC), and machine-to-machine (M2M) communication can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access network (RAN) as the above big data processing technology can also be regarded as an example of the integration between 5G technology and IoT technology.

[0005] The present disclosure relates to a wireless communication system, and more particularly, to CORESET configuration in an unlicensed band. SUMMARY OF THE INVENTION

[0006] TECHNICAL PROBLEM

[0007] Recently, the number of users of wireless communication services has exceeded five billion and continues to grow rapidly. Due to the increasing popularity of smartphones and other mobile data devices such as tablet computers, "notepad" computers, netbooks, e-book readers, and machine type devices in consumers and businesses, the demand for wireless data traffic has increased rapidly. To meet the high growth of mobile data traffic and support new applications and deployments, improvements in radio interface efficiency and coverage are crucial.

[0008] PROBLEM SOLUTION

[0009] In one embodiment, a user equipment (UE) in a wireless communication system is provided. The UE includes a transceiver configured to receive a synchronization signal and a physical broadcast channel (SS / PBCH) block. The UE further includes a processor operably connected to the transceiver, the processor being configured to: determine the subcarrier spacing of the SS / PBCH block from a set of subcarrier spacings {SCS1, SCS2}, determine the subcarrier spacing of a type0 physical downlink control channel (Type0-PDCCH) common search space (CSS) set in a control resource set (CORESET), wherein the subcarrier spacing of the Type0-PDCCH CSS set is the same as the subcarrier spacing of the SS / PBCH block, determine the bandwidth of the CORESET based on the master information block (MIB) in the SS / PBCH block, determine the number of symbols of the CORESET based on the MIB, determine a frequency offset from a set of frequency offsets {O1, O2} based on the MIB and subcarrier spacing of the SS / PBCH block, wherein the frequency offset is determined as the minimum resource block (RB) index from the CORESET to the minimum RB index of a common RB overlapping with the first RB of the SS / PBCH block, and determine the frequency position of the CORESET based on the determined frequency offset, wherein the transceiver is further configured to receive the Type0-PDCCH based on the determined bandwidth, number of symbols, and frequency position of the CORESET.

[0010] In another embodiment, a base station (BS) in a wireless communication system is provided. The BS includes a transceiver configured to: transmit a synchronization signal and a physical broadcast channel (SS / PBCH) block; and transmit a type0 physical downlink control channel (Type0-PDCCH) based on the bandwidth, number of symbols, and frequency position of a control resource set (CORESET), where: the bandwidth of the CORESET is determined based on a master information block (MIB) in the SS / PBCH block; the number of symbols of the CORESET is determined based on the MIB; the frequency position of the CORESET is determined based on a frequency offset and the subcarrier spacing of the SS / PBCH block determined from a set of subcarrier spacings {SCS1, SCS2}, the frequency offset is determined from a set of frequency offsets {O1, O2} based on the MIB, the frequency offset is determined as the minimum resource block (RB) index from the CORESET to the minimum RB index of a common RB overlapping with the first RB of the SS / PBCH block; and the subcarrier spacing of the type0 physical downlink control channel common search space (CSS) set in the CORESET is configured to be the same as the subcarrier spacing of the SS / PBCH block.

[0011] In yet another embodiment, a method for a user equipment (UE) in a wireless communication system is provided. The method includes: receiving a synchronization signal and a physical broadcast channel (SS / PBCH) block; determining the subcarrier spacing of the SS / PBCH block from a set of subcarrier spacings {SCS1, SCS2}; determining the subcarrier spacing of the type0 physical downlink control channel common search space (CSS) set in a control resource set (CORESET), where the subcarrier spacing of the Type0-PDCCH CSS set is the same as the subcarrier spacing of the SS / PBCH block; determining the bandwidth of the CORESET based on a master information block (MIB) in the SS / PBCH block; determining the number of symbols of the CORESET based on the MIB; determining a frequency offset from a set of frequency offsets {O1, O2} based on the MIB of the SS / PBCH block and the subcarrier spacing, where the frequency offset is determined as the minimum resource block (RB) index from the CORESET to the minimum RB index of a common RB overlapping with the first RB of the SS / PBCH block; determining the frequency position of the CORESET based on the determined frequency offset; and receiving the Type0-PDCCH based on the determined bandwidth, number of symbols, and frequency position of the CORESET.

[0012] Those skilled in the art can easily understand other technical features according to the following drawings, description, and claims.

[0013] Before presenting the following detailed embodiments, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "coupled" 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 "send," "receive," and "communicate" and their derivatives include both direct and indirect communication. The terms "comprise" and "include" and their derivatives mean including without limitation. The term "or" is inclusive and means and / or. The phrase "associated with" and its derivatives mean including, being included in, interconnecting with, containing, being contained in, connected to or connecting with, coupled to or coupling with, capable of communicating with, cooperating with, inserted in, juxtaposed with, proximate to, bound to or binding with, having, owning, related to, and so on. 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 locally or remotely. The phrase "at least one of" when used with a list of items 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.

[0014] In addition, the various functions described below may be implemented or supported by one or more computer programs, each of which is 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, programs, functions, objects, classes, instances, related data, or a portion thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of memory. A "non-transitory" computer-readable medium does not include wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer-readable medium includes media in which data can be permanently stored and media in which data can be stored and later overwritten, such as a rewritable compact disc or a rewritable storage device.

[0015] Certain other terms and phrases are defined throughout this patent document. One of ordinary skill in the art will understand that, in many if not most instances, these definitions apply to the prior and future use of the defined terms and phrases.

[0016] Advantages of the present invention

[0017] The main purpose of the embodiments herein is to provide a method and system for efficient CORESET configuration for a UE on an unlicensed frequency band. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] 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:

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

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

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

[0022] Figure 4 An example DL time slot structure according to an embodiment of the present disclosure is shown;

[0023] Figure 5 An example UL time slot structure for PUSCH transmission or PUCCH transmission according to an embodiment of the present disclosure is shown;

[0024] Figure 6A An example floating CORESET #0 in a carrier with 51 RBs according to an embodiment of the present disclosure is shown;

[0025] Figure 6B An example floating CORESET #0 in a carrier with 50 RBs according to an embodiment of the present disclosure is shown;

[0026] Figure 6C Another example floating CORESET #0 in a carrier with 50 RBs according to an embodiment of the present disclosure is shown;

[0027] Figure 7 An example mapping relationship between SCSs according to an embodiment of the present disclosure is shown; and

[0028] Figure 8 A flowchart of a method for configuring a CORESET according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0029] discussed below Figures 1 to 8 The various embodiments described below and used in this patent document to describe the principles of the present disclosure are merely illustrative 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 suitably arranged system or device.

[0030] The following documents are hereby 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".

[0031] as follows Figures 1 - 3 Described below are various embodiments implemented in a wireless communication system and using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. Figures 1 - 3 The description is not intended to imply physical or structural limitations on the ways in which different embodiments can be implemented. Different embodiments of the present disclosure can be implemented in any suitably arranged communication system.

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

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

[0034] gNB 102 provides wireless broadband access to the network 130 for a first plurality of user equipments (UEs) within the coverage area 120 of gNB 102. The first plurality of UEs includes: UE 111, which may be located in a small enterprise; UE 112, which may be located in an enterprise unit (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 mobile phone, a wireless laptop computer, a wireless PDA, and so on. gNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within the 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 / NR, LTE, LTE-A, WiMAX, WiFi, or other wireless communication technologies.

[0035] 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 transceiver point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a home base station, a WiFi access point (AP), or other wireless-enabled device. The base station may provide wireless access according to one or more wireless communication protocols (e.g., 5G / NR 3GPP new radio interface / access (NR), Long-Term Evolution (LTE), enhanced LTE (LTE-A), High-Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.). For simplicity, the terms "BS" and "TRP" may be used interchangeably in this patent document to denote the network infrastructure components that provide wireless access to remote terminals. Moreover, depending on the network type, the term "user equipment" or "UE" may refer to any component such as a "mobile station", "user station", "remote terminal", "wireless terminal", "receiving point", or "user equipment". For simplicity, the terms "user equipment" and "UE" are used in this patent document to denote the remote wireless devices that wirelessly access the BS, whether the UE is a mobile device (such as a mobile phone or a smartphone) or is generally considered a fixed device (such as a desktop computer or a vending machine).

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

[0037] As described in more detail below, one or more of UEs 111 - 116 include circuitry, programming, or a combination thereof for efficient CORESET configuration of the UE. In certain embodiments, one or more of gNBs 101 - 103 include circuitry, programming, or a combination thereof for efficient CORESET configuration of the UE.

[0038] Although Figure 1 an example of a wireless network is shown, various changes may be made Figure 1 to it. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. Also, gNB 101 may communicate directly with any number of UEs and provide wireless broadband access to network 130 to those UEs. Similarly, each of gNBs 102 - 103 may communicate directly with network 130 and provide direct wireless broadband access to network 130 to the UEs. Further, gNBs 101, 102, and / or 103 may provide access to other or additional external networks (such as an external telephone network or other types of data networks).

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

[0040] As Figure 2 shown, gNB 102 includes a plurality of antennas 205a - 205n, a plurality of 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.

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

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

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

[0044] The controller / processor 225 is also capable of executing programs and other processes resident in the memory 230, such as the OS. The controller / processor 225 can move data into or out of the memory 230 as needed for the execution of processes.

[0045] 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 communication system supporting 5G / NR, 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.

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

[0047] Although Figure 2 an example of the gNB 102 is shown, various changes may be made Figure 2 thereto. For example, the gNB 102 may include any number of Figure 2 each of the components shown. As a specific example, an access point may include a number of interfaces 235, and the controller / processor 225 may support routing functions to send 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 for each RF transceiver). Moreover, the various components in Figure 2 may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0048] Figure 3 An example UE 116 according to an embodiment of the present disclosure is shown. Figure 3 The illustrated embodiment of the UE 116 is for illustrative purposes only, and Figure 1 the UEs 111 - 115 may have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 the scope of the present disclosure is not limited to any particular implementation of the UE.

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

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

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

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

[0053] 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 may 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 program 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 the 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 a communication path between these accessories and the processor 340.

[0054] The processor 340 is also coupled to the touch screen 350 and the display 355. The operator of the UE 116 may use the touch screen 350 to input data into the UE 116. The display 355 may 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.

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

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

[0057] In order to meet the increased demand for wireless data traffic since the deployment of 4G communication systems and to enable various vertical applications, efforts have been made to develop and deploy improved 5G / NR or pre-5G / NR communication systems. Thus, the 5G / NR or pre-5G / NR communication systems are also referred to as "super 4G networks" or "post-LTE systems". The 5G / NR communication systems are considered to be implemented in a higher frequency (mmWave) band (e.g., 28 GHz or 60 GHz band) to achieve higher data rates or in a lower frequency band (such as 6 GHz) to achieve strong coverage and mobility support. Aspects of the present disclosure may also be applied to 5G communication systems, 6G, or even future versions of deployments that may use the terahertz (THz) band. 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 within the 5G / NR communication systems.

[0058] In addition, in the 5G / NR communication systems, the development of system network improvements has been carried out 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 interference cancellation, and so on.

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

[0060] The time unit of the DL signaling or UL signaling on a cell is called a time slot and may include one or more symbols. The symbol may also be used as an additional time unit. The frequency (or bandwidth (BW)) unit is called a resource block (RB). One RB includes many subcarriers (SC). For example, a time slot may have a duration of 0.5 ms or 1 ms, include 14 symbols, and an RB may include 12 SCs, with an interval of 15 KHz or 30 KHz between the SCs, and so on.

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

[0062] The gNB transmits one or more of various types of RS, including channel state information RS (CSI-RS) and demodulation RS (DMRS). The CSI-RS is mainly used to enable the UE to perform measurements and provide channel state information (CSI) to the gNB. For channel measurements, non-zero power CSI-RS (NZP CSI-RS) resources are used. For interference measurement reporting (IMR), CSI interference measurement (CSI-IM) resources associated with zero power CSI-RS (ZP CSI-RS) configurations are used. The CSI process consists of NZP CSI-RS and CSI-IM resources.

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

[0064] Figure 4 and Figure 5 FIG. shows an example wireless transmit and receive path according to the present disclosure. In the following description, the transmit path 400 may be described as being implemented in a gNB, such as gNB 102, while the receive path 500 may be described as being implemented in a UE, such as UE 116. However, it can be understood that the receive path 500 may be implemented in the gNB and the transmit path 400 may be implemented in the UE. In some embodiments, the receive path 500 is configured to support the codebook design and structure of a system with a 2D antenna array as described in the embodiments of the present disclosure.

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

[0066] As Figure 4 shown, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a series of frequency-domain modulated symbols.

[0067] The serial-to-parallel block 410 transforms (such as demultiplexes) the serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. The IFFT block 415 of size N performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. The parallel-to-serial block 420 transforms (such as multiplexes) the parallel time-domain output symbols from the IFFT block 415 of size N to generate a serial time-domain signal. The cyclic prefix addition block 425 inserts a cyclic prefix into the time-domain signal. The upconverter 430 modulates (such as upconverts) the output of the cyclic prefix addition block 425 to an RF frequency for transmission via the wireless channel. The signal can also be filtered at baseband before being transformed to the RF frequency.

[0068] The transmitted RF signal from gNB 102 arrives at UE 116 after passing through the wireless channel, and operations opposite to those at gNB 102 are performed at UE 116.

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

[0070] Each of gNBs 101 - 103 may implement a transmission path 400 as shown in Figure 4 (which is similar to transmission to UEs 111 - 116 in the downlink) and may implement a reception path 500 as shown in Figure 5 (which is similar to reception from UEs 111 - 116 in the uplink). Similarly, each of UEs 111 - 116 may implement a transmission path 400 for transmission to gNBs 101 - 103 in the uplink and may implement a reception path 500 for reception from gNBs 101 - 103 in the downlink.

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

[0072] In addition, although described as using FFT and IFFT, this is merely an illustrative way and should not be construed as limiting the scope of the present disclosure. Other types of transforms, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions, may be used. It can be understood that for DFT and IDFT functions, the value of variable N may be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N may be any integer that is a power of two (such as 1, 2, 4, 8, 16, etc.).

[0073] Although Figure 4 and Figure 5 illustrate examples of wireless transmission and reception paths, various changes may be made to Figure 4 and Figure 5 . For example, various components in Figure 4 and Figure 5 may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. Moreover, Figure 4 and Figure 5 are intended to illustrate examples of the types of transmission and reception paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communication in a wireless network.

[0074] The present disclosure provides mechanisms and methods to enable determination of the offset between a Synchronization Signal / Physical Broadcast Channel block (SSB) in an unlicensed band and CORESET#0, where CORESET#0 is the control resource set for type0 PDCCH. The present disclosure includes the following components: the frequency-domain offset of CORESET#0, the sub-RB level offset indication, and the CORESET#0 configuration.

[0075] The present disclosure provides the configuration (including the frequency-domain offset) of CORESET#0 in the unlicensed band in view of the different characteristics of the synchronization raster and channel raster design differences between the licensed band and the unlicensed band (e.g., operation with shared spectrum channel access), where the configuration of CORESET#0 may be included in the MIB of the SSB.

[0076] In one embodiment, the frequency-domain offset between a Synchronization Signal / Physical Broadcast Channel block (e.g., SSB) and CORESET#0 is defined as the difference between the lowest resource element (RE) of the SSB and the lowest RE of the associated CORESET#0, where the offset includes an RB-level offset (e.g., relative to the subcarrier spacing (SCS) of CORESET#0) and a sub-RB level offset (e.g., relative to the 15 kHz SCS of FR1). In one example, the sub-RB level offset also defines the offset between the lowest RE of the SSB and the common resource grid.

[0077] In one example, in the unlicensed band, the channel raster for a given carrier bandwidth is fixed. In another example, the synchronization raster within the nominal carrier bandwidth (e.g., 20 MHz) is fixed.

[0078] In one example, for a given combination of the carrier bandwidth and the SCS of the SSB and CORESET#0, when CORESET#0 is located at the lowest edge of the channel, the frequency offset between the SSB and CORESET#0 can be calculated based on the fixed synchronization raster and the fixed channel raster.

[0079] In one example, the RB-level offset can be given by ΔF_RB = floor(ΔF / (SCS_CORESET*N_SC)); and the sub-RB-level offset can be given by ΔF_subRB = (ΔF - (SCS_CORESET*N_SC)*ΔF_RB) / SCS_ref; where ΔF = (F_sync - N_SSB / 2*SCS_SSB*N_SC) - (F_channel - N_carrier / 2*SCS_CORESET*N_SC), and F_sync is the frequency of the synchronization raster entry, F_channel is the frequency of the channel raster entry, N_SSB is the number of RBs of the SSB bandwidth (e.g., 20 RBs), N_carrier is the number of RBs of the carrier bandwidth, SCS_SSB is the subcarrier spacing of the SSB, SCS_CORESET is the subcarrier spacing of CORESET#0, N_SC is the number of subcarriers in an RB (e.g., 12), and SCC_ref is the reference subcarrier spacing used to define the common resource grid (e.g., 15 kHz for FR1).

[0080] For a 20 MHz channel and {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, example offsets are given in Table 1-1.

[0081] [Table 1-1]

[0082]

[0083] For a 40 MHz channel and {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, example offsets are given in Table 1-2.

[0084] Table 1-2. Example offsets for a 40 MHz channel and {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}

[0085] [Table 1-2]

[0086]

[0087] For a 60 MHz channel and {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, example offsets are given in Table 1-3.

[0088] Table 1-3. Example offsets for a 60 MHz channel and {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}

[0089] [Table 1-3]

[0090]

[0091] For an 80 MHz channel and {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, example offsets are given in Table 1-4.

[0092] Table 1-4. Example Offsets for 80 MHz Channel and {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}

[0093] [Table 1-4]

[0094]

[0095] For a 20 MHz channel and {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, example offsets are given in Table 1-5.

[0096] Table 1-5. Example Offsets for 20 MHz Channel and {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}

[0097] [Table 1-5]

[0098]

[0099] For a 40 MHz channel and {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, example offsets are given in Table 1-6.

[0100] Table 1-6. Example Offsets for 40 MHz Channel and {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}

[0101] [Table 1-6]

[0102]

[0103] In another example, for a given carrier bandwidth and a given combination of the SCS of the SSB and CORESET#0, when CORESET#0 is at the highest edge of the channel, the frequency offset between the SSB and CORESET#0 can be calculated based on a fixed synchronization raster and a fixed channel raster.

[0104] In one example, the RB-level offset can be given by ΔF_RB = N_CORESET - ceiling(ΔF / (SCS_CORESET*N_SC)) - N_SSB; and the sub-RB-level offset can be given by ΔF_subRB = (N_CORESET + (SCS_CORESET*N_SC)*ΔF_RB + N_SSB - ΔF) / SCS_ref; where ΔF = (F_channel + N_carrier / 2*SCS_CORESET*N_SC) - (F_sync + N_SSB / 2*SCS_SSB*N_SC), and F_sync is the frequency of the synchronization raster entry, F_channel is the frequency of the channel raster entry, N_SSB is the number of RBs of the SSB bandwidth (e.g., 20 RBs), N_carrier is the number of RBs of the carrier bandwidth, N_CORESET is the number of RBs of CORESET#0, SCS_SSB is the subcarrier spacing of the SSB, SCS_CORESET is the subcarrier spacing of CORESET#0, N_SC is the number of subcarriers in an RB (e.g., 12), and SCC_ref is the reference subcarrier spacing used to define the common resource grid (e.g., 15 kHz for FR1).

[0105] Table 2-1 to Table 2-4 show a summary of the RB-level offset and the RE-level offset of channels with all supported bandwidths.

[0106] Table 2-1. Example offsets for 20 MHz channels

[0107] [Table 2-1]

[0108]

[0109] Table 2-2. Example offsets for 40 MHz channels.

[0110] [Table 2-2]

[0111]

[0112] Table 2-3. Example offsets for 60 MHz channels.

[0113] [Table 2-3]

[0114]

[0115] Table 2-4. Example offsets for 80 MHz channels.

[0116] [Table 2-4]

[0117]

[0118] Figure 6A Shows an example floating CORESET#0 in carrier 600 with 51 RBs according to an embodiment of the present disclosure. Figure 6A The embodiment of the floating CORESET#0 in carrier 600 with 51 RBs shown is for illustration only. Figure 6A One or more of the components shown may be implemented in a dedicated circuit configured to perform the proposed functions or one or more of the components may be implemented by one or more processors executing instructions to perform the proposed functions.

[0119] In one example, to channelize a 20 MHz LBT bandwidth into 51 RBs with respect to 30 kHz, for each given channel supported in NR-U, Figure 6A the possible offsets are shown and the corresponding table is given in Table 3-1. Then, two CORESET#0 offsets selected as (0, 2), or (0, 3) or (0, 4) may be applicable to all cases ( Figure 6A showing the two CORESET#0 offsets as (0, 4)).

[0120] Table 3-1. CORESET#0 offsets required for 51 RBs.

[0121] [Table 3-1]

[0122]

[0123] In another example, to channelize a 20 MHz LBT bandwidth into 50 RBs with respect to 30 kHz, for each given channel supported in NR-U, Figure 6B and Figure 6C the possible offsets are shown and the corresponding table is given in Table 3-2. It should be noted that there are two cases where the highest RB ( Figure 6C ) or the lowest RB ( Figure 6B ) from 51 RBs is truncated (e.g., due to guard band requirements). Then, two CORESET#0 offsets selected as (0, 3) may be applicable to all cases ( Figure 6B and Figure 6C showing the two CORESET#0 offsets as (0, 3)), or (0, 2) may be applicable to the case where the lowest RB is truncated.

[0124] Figure 6B Shows an example floating CORESET#0 in carrier 650 with 50 RBs according to an embodiment of the present disclosure. Figure 6B The embodiment of the floating CORESET#0 in carrier 650 with 50 RBs shown is for illustration only. Figure 6BOne or more of the components shown may be implemented in a dedicated circuit configured to perform the noted function or one or more of the components may be implemented by one or more processors executing instructions to perform the noted function.

[0125] Figure 6C Another example floating CORESET#0 in a carrier 670 with 50 RBs according to an embodiment of the present disclosure is shown. Figure 6C The embodiment of the floating CORESET#0 in the carrier 670 with 50 RBs shown is for illustration only. Figure 6C One or more of the components shown may be implemented in a dedicated circuit configured to perform the noted function or one or more of the components may be implemented by one or more processors executing instructions to perform the noted function.

[0126] Table 3-2. CORESET#0 bias required for 50 RBs.

[0127] [Table 3-2]

[0128]

[0129] To channelize a 20 MHz LBT bandwidth into 49 RBs with respect to 30 kHz, for each given channel supported in NR-U, the possible biases are shown in Table 3-3. It should be noted that there are three cases where the highest 2 RBs or the lowest 2 RBs or the highest and lowest RBs from 51 RBs are truncated (e.g., due to guard band requirements). Then, the three CORESET#0 biases selected as (0, 2, 4) can be applicable to all cases.

[0130] Table 3-3. CORESET#0 bias required for 49 RBs.

[0131] [Table 3-3]

[0132]

[0133] To channelize a 20 MHz LBT bandwidth into 48 RBs with respect to 30 kHz, for each given channel supported in NR-U, the possible biases are shown in Table 3-4. It should be noted that there are four cases where the highest 3 RBs or the highest 2 and the lowest 1, or the highest 1 and the lowest 2, or the lowest 3 RBs from 51 RBs are truncated (e.g., due to guard band requirements). Then, 6 CORESET#0 biases can be applicable to all cases.

[0134] Table 3-4. CORESET#0 bias required for 48 RBs.

[0135] [Table 3-4]

[0136]

[0137] In one embodiment, the sub-RB level offset is hard-coded in the specification. In one example, for a given synchronization raster entry and a given carrier bandwidth, the sub-RB level offset is given by the examples in Tables 1-1 to 1-6.

[0138] In one example, the sub-RB level offset is indicated in the PBCH payload. For example, 5 bits are used to indicate the sub-RB level offset, for example the same as in Rel-15 and denoted as k_SSB. In another example, the candidate values of the sub-RB level offset are given by {0,2,4,6,8,10,12,14,16,18,20,22}, and 4 bits (e.g., in the MIB) are sufficient for this purpose. In yet another example, the candidate values of the sub-RB level offset are given by {0,4,8,12,16,20}, and 3 bits (e.g., in the MIB) are sufficient for this purpose.

[0139] In one embodiment, the RB level offset is hard-coded in the specification. In one example, for a given synchronization raster entry and a given carrier bandwidth, the RB level offset is given by the examples in Tables 1-1 to 1-6.

[0140] In another embodiment, as part of the CORESET#0 configuration, the RB level offset is indicated by the PBCH payload (e.g., the MIB) together with the multiplexing pattern with the SSB, the number of symbols of CORESET#0, and the bandwidth of CORESET#0.

[0141] In one example, for {SCS_SSB,SCS_CORESET} = {30kHz,30kHz}, the RB level offset can be configured from {0,1,2,3,4,5} (it should be noted that this set is the set of all possible values calculated in the present disclosure required for {SCS_SSB,SCS_CORESET} = {30kHz,30kHz}), and an example configuration table is given by Table 4-1. In one example, reserved rows can be added to Table 4-1 such that the total number of rows is 16 (e.g., maintaining the same table size as in Rel-15).

[0142] Table 4-1. Example CORESET#0 configuration table for {SCS_SSB,SCS_CORESET} = {30kHz,30kHz}

[0143] [Table 4-1]

[0144]

[0145] In another example, for {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, the RB-level offset can be configured from a subset of {0, 1, 2, 3, 4, 5}. In one instance, by noting that the BW of CORESET#0 is less than the BW of the carrier, CORESET#0 can float within the carrier such that one configuration of the RB-level offset can be reused for multiple carriers. For example, for {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, the BW of the SSB is 48 RBs, and for 20 MHz, the BW of CORESET#0 is 51 RBs, then one configuration of the RB-level offset can be reused for carriers with 4 different adjacent RB-level offset values and based on the calculations in the present disclosure, up to 6 different adjacent RB-level offset values from {0, 1, 2, 3, 4, 5} are apparent. Thus, at least 2 configurations regarding the RB-level offset are sufficient.

[0146] Table 4-1 shows an illustration of the floating CORESET#0 within the carrier. In one consideration, although the minimum number of required offsets is 2, the number of supported offsets to be configured can be greater than 2 to allow for better flexibility as long as the total number of configurations can conform to 4 bits as in NR Rel-15. Example configuration tables are given in Tables 4-2 to 4-8. In one consideration of the example tables, reserved rows can be added to Tables 4-2 to 4-8 such that the total number of rows is 16 (e.g., maintaining the same table size as Rel-15).

[0147] Table 4-2. Example CORESET#0 Configuration Table for {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}

[0148] [Table 4-2]

[0149]

[0150] Table 4-3. Example CORESET#0 Configuration Table for {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}

[0151] [Table 4-3]

[0152]

[0153] Table 4-4. Example CORESET#0 Configuration Table for {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}

[0154] [Table 4-4]

[0155]

[0156] Table 4-5. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {30kHz, 30kHz}

[0157] [Table 4-5]

[0158]

[0159] Table 4-6. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {30kHz, 30kHz}

[0160] [Table 4-6]

[0161]

[0162] Table 4-7. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {30kHz, 30kHz}

[0163] [Table 4-7]

[0164]

[0165] Table 4-8. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {30kHz, 30kHz}

[0166] [Table 4-8]

[0167]

[0168] In yet another example, for {SCS_SSB, SCS_CORESET} = {15kHz, 15kHz}, the RB-level offset can be configured from {13, 14, 15, 16, 17, 18, 19, 20} (it should be noted that this set is the set of all possible values calculated in the present disclosure required for {SCS_SSB, SCS_CORESET} = {15kHz, 15kHz}), and an example configuration table is given in Table 5-1. It should be noted that this example assumes that when the SCS of the SSB is 15kHz, the SSB is located at the synchronization raster as a reference for designing the table.

[0169] Table 5-1. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15kHz, 15kHz}

[0170] [Table 5-1]

[0171]

[0172] In yet another example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, the RB-level offset can be configured from {0, 1, 2, 3, 4, 5, 6, 7} (it should be noted that this set is the set of all possible values calculated in the present disclosure required for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, and the values are defined using a predefined offset of 13 RBs), and an example configuration table is given in Table 5-2. It should be noted that this example assumes that when the SCS of the SSB is 15 kHz, the SSB is located 13 RBs from the synchronization raster as a reference for designing the table.

[0173] Table 5-2. Example CORESET#0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}

[0174] [Table 5-2]

[0175]

[0176] In yet another example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, by noting that the BW of CORESET#0 is less than the BW of the carrier, CORESET#0 can float within the carrier such that one configuration of the RB-level offset can be reused for multiple carriers. For example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, the BW of the SSB is 96 RBs, and for 20 MHz, the BW of CORESET#0 is 106 RBs, then one configuration of the RB-level offset can be reused for carriers with 11 different adjacent RB-level offset values and based on the calculations in the present disclosure, up to 11 different adjacent RB-level offset values are evident in Table 1-5 and Table 1-6. Therefore, an example configuration table is given in Table 5-3, where X can be a value selected from {10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21}, for example X = 10, or X = 13, or X = 20, or X = 21, or X = 17, or X = 11. It should be noted that this example assumes that when the SCS of the SSB is 15 kHz, the SSB is located at the synchronization raster as a reference for designing the table.

[0177] Table 5-3. Example CORESET#0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}

[0178] [Table 5-3]

[0179]

[0180] In yet another example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, by noting that the BW of CORESET#0 is less than the BW of the carrier, CORESET#0 can float within the carrier such that one configuration of RB-level offset can be reused for multiple carriers. For example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, the BW of the SSB is 96 RBs, and for 20 MHz, the BW of CORESET#0 is 106 RBs, then one configuration of RB-level offset can be reused for carriers with 11 different adjacent RB-level offset values and based on the calculations in the present disclosure, up to 11 different adjacent RB-level offset values are evident in Table 1-5 and Table 1-6. Thus, an example configuration table is given in Table 5-3, where X can be a value selected from {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11}, for example X = 0 or X = 3. It should be noted that this example assumes that when the SCS of the SSB is 15 kHz, the SSB is located at 10 RBs or 13 RBs from the synchronization raster as a reference for designing the table.

[0181] In yet another example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, by noting that the BW of CORESET#0 is less than the BW of the carrier, CORESET#0 can float within the carrier such that one configuration of RB-level offset can be reused for multiple carriers. For example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, the BW of the SSB is 96 RBs, and for 20 MHz, the BW of CORESET#0 is 106 RBs, then one configuration of RB-level offset can be reused for carriers with 11 different adjacent RB-level offset values.

[0182] Therefore, an example configuration table is given in Table 5-4, where X and Y can be values selected from {10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21} such that Y - X ≤ 10. For example, {X, Y} = {10, 20}, or {X, Y} = {13, 20}, or {X, Y} = {13, 14}, or {X, Y} = {19, 20}, or {X, Y} = {20, 21}, or {X, Y} = {10, 11}, or {X, Y} = {10, 12}, or {X, Y} = {10, 14}, or {X, Y} = {10, 16}, or {X, Y} = {10, 18}, or {X, Y} = {13, 21}, or {X, Y} = {11, 21}. It should be noted that this example assumes that when the SCS of the SSB is 15 kHz, the SSB is located at the synchronization raster as a reference for designing the table.

[0183] Table 5-4. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}

[0184] [Table 5-4]

[0185]

[0186] In another example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, by noting that the BW of CORESET #0 is less than the BW of the carrier, CORESET #0 can float within the carrier such that one configuration of the RB-level offset can be reused for multiple carriers. For example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, the BW of the SSB is 96 RBs, and for 20 MHz, the BW of CORESET #0 is 106 RBs. Then one configuration of the RB-level offset can be reused for carriers with 11 different adjacent RB-level offset values. Therefore, an example configuration table is given in Table 5-4, where X and Y can be values selected from {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11} such that Y - X ≤ 10. For example, {X, Y} = {0, 10}, or {X, Y} = {3, 10}, or {X, Y} = {0, 7}, or {X, Y} = {0, 1}, or {X, Y} = {3, 4}, or {X, Y} = {9, 10}, or {X, Y} = {10, 11}, or {X, Y} = {0, 2}, or {X, Y} = {0, 4}, or {X, Y} = {0, 6}, or {X, Y} = {0, 8}. It should be noted that this example assumes that when the SCS of the SSB is 15 kHz, the SSB is located 10 RBs or 13 RBs from the synchronization raster as a reference for designing the table.

[0187] In yet another example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, the number of biases in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz} is the same as the number of biases in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, and the values of the biases in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz} have a one-to-one mapping with the values of the biases in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, for example, O_15 = O_30 * 2 + 10, where O_15 is the value of the bias in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, and O_30 is the value of the bias in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}.

[0188] Tables 6-1 to 6-8 show example configuration tables for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz} using the mapping relationship of this example. In one instance, reserved rows can be added to Tables 6-1 to 6-8 such that the total number of rows is 16 (e.g., maintaining the same table size as Rel-15).

[0189] Table 6-1. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}

[0190] [Table 6-1]

[0191]

[0192] Table 6-2. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}

[0193] [Table 6-2]

[0194]

[0195] Table 6-3. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}

[0196] [Table 6-3]

[0197]

[0198] Table 6-4. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15kHz, 15kHz}

[0199] [Table 6-4]

[0200]

[0201] Table 6-5. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15kHz, 15kHz}

[0202] [Table 6-5]

[0203]

[0204] Table 6-6. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15kHz, 15kHz}

[0205] [Table 6-6]

[0206]

[0207] Table 6-7. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15kHz, 15kHz}

[0208] [Table 6-7]

[0209]

[0210] Table 6-8. Example CORESET #0 Configuration Table for {SCS_SSB, SCS_CORESET} = {15kHz, 15kHz}

[0211] [Table 6-8]

[0212]

[0213] In one example, for the SS / PBCH block and the CORESET multiplexing pattern 1, when multiple SCSs are supported for the SS / PBCH block and its associated CORESET #0, for a given configured bandwidth of CORESET #0, the number of biases in the configurable bias set corresponding to the given CORESET #0 bandwidth is the same for all supported SCSs, and the values of the biases in the configurable bias set corresponding to the given CORESET #0 bandwidth have a one-to-one mapping relationship among all supported SCSs.

[0214] For example, for a given configured bandwidth of CORESET #0, and for a first supported SCS_1 (i.e., {SCS_SSB, SCS_CORESET} = {SCS_1, SCS_1}) and a second supported SCS_2 (i.e., {SCS_SSB, SCS_CORESET} = {SCS_2, SCS_2}), the value of the bias in the configurable bias set corresponding to the first SCS (denoted as O_1) and the value of the bias in the configurable bias set corresponding to the second SCS (denoted as O_2) have a relationship such as O_2 = O_1 * R_SCS + BW_SSB * R_SCS / 2 - BW_SSB / 2, where R_SCS = SCS_1 / SCS_2 is the ratio of SCSs, and BW_SSB is the BW of the SS / PBCH block in terms of its SCS (e.g., BW_SSB = 20 RB). The generalization of this example is based on the assumption that SS / PBCH blocks with different SCSs are centered at the same reference frequency position (e.g., synchronization raster entry), and Figure 7 illustrates the mapping relationship between different SCSs.

[0215] Figure 7 illustrates an example mapping relationship between SCSs 700 according to an embodiment of the present disclosure. Figure 7 The embodiment of the mapping relationship between the illustrated SCSs 700 is for illustration only. Figure 7 One or more of the components shown therein may be implemented in a dedicated circuit configured to perform the proposed functions or one or more of the components may be implemented by one or more processors executing instructions to perform the proposed functions.

[0216] In yet another example, for {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, the number of biases in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz} is the same as the number of biases in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, and the values of the biases in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz} have a one-to-one mapping with the values of the biases in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, e.g., O_15 = O_30 * 2 + Z, where O_15 is the value of the bias in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {15 kHz, 15 kHz}, O_30 is the value of the bias in the configurable bias set corresponding to {SCS_SSB, SCS_CORESET} = {30 kHz, 30 kHz}, and Z is an integer constant, e.g., Z = 13.

[0217] In one example, for SS / PBCH block and CORESET multiplexing mode 1, when multiple SCSs are supported for the SS / PBCH block and its associated CORESET#0, for a given configured bandwidth of CORESET#0, the number of biases in the configurable bias set corresponding to the given CORESET#0 bandwidth is the same for all supported SCSs, and the values of the biases in the configurable bias set corresponding to the given CORESET#0 bandwidth have a one-to-one mapping relationship among all supported SCSs. For example, for a given configured bandwidth of CORESET#0, and for a first supported SCS_1 (i.e., {SCS_SSB, SCS_CORESET} = {SCS_1, SCS_1}) and a second supported SCS_2 (i.e., {SCS_SSB, SCS_CORESET} = {SCS_2, SCS_2}), the value of the bias in the configurable bias set corresponding to the first SCS (denoted as O_1) and the value of the bias in the configurable bias set corresponding to the second SCS (denoted as O_2) have a relationship such as O_2 = O_1 * R_SCS + Z, where R_SCS = SCS_1 / SCS_2 is the ratio of SCSs, and Z is an integer constant, e.g., Z = 0.

[0218] Figure 8 illustrates a flowchart of a method 800 for configuring a CORESET according to an embodiment of the present disclosure that may be performed by a user equipment (UE) (e.g., as Figure 1 shown in 111 - 116). Figure 8The embodiments of the method 800 shown are for illustration only. Figure 8 One or more of the components shown therein may be implemented in a dedicated circuit configured to perform the proposed functions or one or more of the components may be implemented by one or more processors executing instructions to perform the proposed functions.

[0219] As Figure 8 shown, the method 800 begins at step 802. In step 802, the UE receives a Synchronization Signal and Physical Broadcast Channel (SS / PBCH) block.

[0220] Subsequently, the UE in step 804 determines the subcarrier spacing of the SS / PBCH block from a set of subcarrier spacings {SCS1, SCS2}.

[0221] Subsequently, the UE in step 806 determines the subcarrier spacing of the common search space (CSS) set of the type 0 Physical Downlink Control Channel (Type0-PDCCH) in a control resource set (CORESET), where the subcarrier spacing of the Type0-PDCCH CSS set is the same as the subcarrier spacing of the SS / PBCH block.

[0222] Subsequently, the UE in step 808 determines the bandwidth of the CORESET based on the Master Information Block (MIB) in the SS / PBCH block.

[0223] Subsequently, the UE in step 810 determines the number of symbols of the CORESET based on the MIB.

[0224] Then, the UE in step 812 determines a frequency offset from a set of frequency offsets {O1, O2} based on the MIB of the SS / PBCH block and the subcarrier spacing, where the frequency offset is determined as the minimum resource block (RB) index from the CORESET to the minimum RB index of the common RB overlapping with the first RB of the SS / PBCH block.

[0225] In step 812, O1 and O2 are determined based on a one-to-one mapping given by O2 = O1·R SCS +BW SSB ·R SCS / 2 - BW SSB / 2, where R SCS = SCS1 / SCS2, and BW SSB is the bandwidth of the SS / PBCH block in terms of RBs.

[0226] In one embodiment, O1 and O2 are determined based on a one-to-one mapping given by O2 = 2·O1 + 10.

[0227] Next, the UE in step 814 determines the frequency position of the CORESET based on the determined frequency offset.

[0228] Finally, the UE in step 816 receives the Type0-PDCCH based on the determined bandwidth, number of symbols, and frequency position of the CORESET.

[0229] In one embodiment, the UE determines the frequency offset as O1 based on determining the subcarrier spacing of the SS / PBCH block as SCS1, and determines the frequency offset as O2 based on determining the subcarrier spacing of the SS / PBCH block as SCS2.

[0230] In one embodiment, the UE determines whether it supports shared spectrum channel access in frequency range 1 (FR1), and based on determining support for shared spectrum channel access in FR1, sets SCS1 to 30 kHz, sets SCS2 to 15 kHz, and sets BW SSB to 20 RBs.

[0231] In one embodiment, the UE determines the subcarrier spacing of the SS / PBCH block as 30 kHz based on the MIB of the SS / PBCH block and determines the frequency offset as one of 0, 1, 2, or 3 RBs.

[0232] In one embodiment, the UE determines the subcarrier spacing of the SS / PBCH block as 15 kHz based on the MIB of the SS / PBCH block and determines the frequency offset as one of 10, 12, 14, or 16 RBs.

[0233] The above flowcharts illustrate example methods that can be implemented in accordance with the principles of the present disclosure, and various changes can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the various steps in each figure can overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps can be omitted or replaced by other steps.

[0234] Although the present disclosure has been described using exemplary embodiments, various changes and modifications can occur to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. The description in this application should not be misconstrued as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A method for accessing operations using a shared spectrum channel performed by a user equipment (UE) in a wireless communication system, the method comprising: Receive a synchronization signal and a Physical Broadcast Channel (SS / PBCH) block; Determine the subcarrier spacing (SCS) of the SS / PBCH block, Based on the Master Information Block (MIB) in the SS / PBCH block, determine the SCS of the Control Resource Set (CORESET) for the Common Search Space (CSS) set of the Type0 Physical Downlink Control Channel (Type0-PDCCH). For a frequency band operating using shared spectrum channel access, the SCS of the CORESET is the same as the SCS of the SS / PBCH block, Based on the MIB, determine the number of symbols and the number of Resource Blocks (RBs) for the CORESET, Based on the MIB, determine the offset in frequency, where the offset is determined as the minimum RB index from the minimum RB index of the CORESET to the minimum RB index of the common RB overlapping with the first RB of the SS / PBCH block, and Monitor the PDCCH in the Type0-PDCCH CSS set, Where, when the SCS of the SS / PBCH block and the SCS of the CORESET are 15 kHz, the value of the offset is one of 10, 12, 14, or 16, and Where, when the SCS of the SS / PBCH block and the SCS of the CORESET are 30 kHz, the value of the offset is one of 0, 1, 2, or 3.

2. The method according to claim 1, wherein The number of configurable offsets of the offset is 16.

3. The method according to claim 2, wherein Determine the offset for the SCS of 15 kHz and the offset for the SCS of 30 kHz based on the one-to-one mapping of the following equation: O1 = 2 * O2 + 10 Where, O1 is the offset for the SCS of 15 kHz and O2 is the offset for the SCS of 30 kHz.

4. A user equipment (UE) for accessing operations using a shared spectrum channel in a wireless communication system, the UE comprising: A transceiver, configured to transmit and receive signals; And A processor, coupled to the transceiver, where the processor is configured to: Receive a synchronization signal and a Physical Broadcast Channel (SS / PBCH) block; Determine the subcarrier spacing (SCS) of the SS / PBCH block, Based on the Master Information Block (MIB) in the SS / PBCH block, determine the SCS of the Control Resource Set (CORESET) for the Common Search Space (CSS) set of the Type0 Physical Downlink Control Channel (Type0-PDCCH). For a frequency band operating using shared spectrum channel access, the SCS of the CORESET is the same as the SCS of the SS / PBCH block, Based on the MIB, determine the number of symbols and the number of Resource Blocks (RBs) for the CORESET, Based on the MIB, determine the offset in frequency, where the offset is determined as the minimum RB index from the minimum RB index of the CORESET to the minimum RB index of the common RB overlapping with the first RB of the SS / PBCH block, and Monitor the PDCCH in the Type0-PDCCH CSS set, Where, when the SCS of the SS / PBCH block and the SCS of the CORESET are 15 kHz, the value of the offset is one of 10, 12, 14, or 16, and Where, when the SCS of the SS / PBCH block and the SCS of the CORESET are 30 kHz, the value of the offset is one of 0, 1, 2, or 3.

5. The UE according to claim 4, wherein The number of configurable offsets described above is 16.

6. The UE according to claim 5, wherein A one-to-one mapping based on the following equation determines the offset for SCS at 15 kHz and the offset for SCS at 30 kHz: O1 = 2 * O2 + 10 where O1 is the offset for SCS at 15 kHz and O2 is the offset for SCS at 30 kHz.

7. A method for accessing operations using a shared spectrum channel performed by a base station in a wireless communication system, the method comprising: Transmit the synchronization signal and the physical broadcast channel SS / PBCH block; and Transmit the PDCCH in the type0 physical downlink control channel Type0-PDCCH common search space CSS set, where, based on the master information block MIB in the SS / PBCH block, the subcarrier spacing SCS of the control resource set CORESET for the Type0-PDCCH CSS set is determined, and for the frequency band operating with shared spectrum channel access, the SCS of the CORESET is the same as the SCS of the SS / PBCH block, where the number of symbols and the number of resource blocks RB for the CORESET are determined based on the MIB, where the offset in frequency is determined as the minimum RB index of the CORESET to the minimum RB index of the common RB overlapping with the first RB of the SS / PBCH block, where, when the SCS of the SS / PBCH block and the SCS of the CORESET are 15 kHz, the value of the offset is one of 10, 12, 14, or 16, and where, when the SCS of the SS / PBCH block and the SCS of the CORESET are 30 kHz, the value of the offset is one of 0, 1, 2, or 3.

8. The method according to claim 7, wherein, The number of configurable offsets described above is 16.

9. The method according to claim 8, wherein, A one-to-one mapping based on the following equation determines the offset for SCS at 15 kHz and the offset for SCS at 30 kHz: O1 = 2 * O2 + 10 where O1 is the offset for SCS at 15 kHz and O2 is the offset for SCS at 30 kHz.

10. A base station for accessing and operating using a shared spectrum channel in a wireless communication system, the base station comprising: A transceiver, configured to transmit and receive signals; and A processor, coupled to the transceiver, where the processor is configured to: Transmit the synchronization signal and the physical broadcast channel SS / PBCH block; and Transmit the PDCCH in the type0 physical downlink control channel Type0-PDCCH common search space CSS set, where, based on the master information block MIB in the SS / PBCH block, the subcarrier spacing SCS of the control resource set CORESET for the Type0-PDCCH CSS set is determined, and for the frequency band operating with shared spectrum channel access, the SCS of the CORESET is the same as the SCS of the SS / PBCH block, where the number of symbols and the number of resource blocks RB for the CORESET are determined based on the MIB, where the offset in frequency is determined as the minimum RB index of the CORESET to the minimum RB index of the common RB overlapping with the first RB of the SS / PBCH block, Wherein, when the SCS of the SS / PBCH block and the SCS of the CORESET are 15 kHz, the value of the offset is one of 10, 12, 14, or 16, and Wherein, when the SCS of the SS / PBCH block and the SCS of the CORESET are 30 kHz, the value of the offset is one of 0, 1, 2, or 3.

11. The base station according to claim 10, wherein, The number of configurable offsets of the offset is 16.

12. The base station according to claim 11, wherein, A one-to-one mapping based on the following equation determines the offset for the 15 kHz SCS and the offset for the 30 kHz SCS: O1 = 2 * O2 + 10 Wherein, O1 is the offset for the 15 kHz SCS, and O2 is the offset for the 30 kHz SCS.

Images