Method and apparatus for resource mapping of PDSCH in unlicensed spectrum

Abstract

A method for operating a terminal in a wireless communication system is provided. The method includes: receiving a radio resource control (RRC) message associated with a transmission position of a synchronization signal / physical broadcast channel (SS / PBCH) block in the time domain from a base station, the RRC message including information about a bitmap; identifying an index of at least one SS / PBCH block transmitted from the base station within a window for receiving the SS / PBCH block based on each bit value included in the bitmap; and receiving the at least one SS / PBCH block at a position corresponding to the identified index from the base station.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems, and more particularly to methods and apparatus for resource mapping of a physical downlink shared channel (PDSCH) on an unlicensed spectrum. Background Art

[0002] In order to meet the demand for wireless data services that are increasing after the commercialization of the 4th generation (4G) communication system, efforts have been made to develop advanced 5th generation (5G) or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are also referred to as super 4G network communication systems or post-long term evolution (LTE) systems. The implementation of a 5G communication system using an overclocked millimeter wave (mmWave) band (e.g., a 60 gigahertz (GHz) band) is considered to obtain a higher data transfer rate. In order to reduce the propagation loss of radio waves and increase the transmission range in the overclocked band, beamforming, massive multiple input multiple output (MIMO), full dimensional MIMO (FD-MIMO), array antennas, analog beamforming and massive antenna technology are discussed. In order to improve the system network, technologies for advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoint (CoMP), receiving end interference elimination, etc. are also developed in 5G communication systems. In addition, in 5G systems, advanced coding modulation (ACM) (e.g., hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) modulation (FQAM) and sliding window superposition coding (SWSC)) and advanced access technologies (e.g., filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA)) are being developed.

[0003] At the same time, the Internet is evolving from a human-centric connected network where humans generate and consume information to an Internet of Things (IoT) network where distributed entities such as things send, receive, and process information without human intervention. Internet of Everything (IoE) technologies, combined with IoT, such as big data processing technologies connected to cloud servers, have also emerged. Implementing the IoT requires various technologies, such as sensing, wired / wireless communications and network infrastructure, service interface technologies, and security technologies. Recently, research is underway into sensor networks, machine-to-machine (M2M), and machine-type communications (MTC) for connecting things. Such an IoT environment can provide intelligent Internet of Things (IT) services that create new value for human life by collecting and analyzing data generated by connected things. IoT can be applied to a variety of fields, such as smart homes, smart buildings, smart cities, smart cars or connected vehicles, smart grids, healthcare, smart home appliances, and advanced medical services, by integrating and combining existing information technology (IT) with various industrial applications.

[0004] In this regard, various attempts are underway to apply 5G communication systems to IoT networks. For example, technologies related to sensor networks, M2M, and MTC are enabled by 5G communication technologies such as beamforming, MIMO, and array antenna schemes. Even the application of cloud radio access networks (cloud RAN), as a technology for processing big data, can be considered an example of the convergence of 5G and IoT technologies.

[0005] As described above, with the development of mobile communication systems, a method for efficient resource mapping of PDSCH is needed.

[0006] The communication system includes a downlink (DL) that transmits signals from a transmission point such as a base station (BS) or NodeB to a user equipment (UE), and an uplink (UL) that transmits signals from the UE to a reception point such as a NodeB. A UE, also commonly referred to as a terminal or mobile station, can be fixed or mobile and can be a cellular phone, a personal computer, or an automated device. An eNodeB (eNB) (referring to a NodeB in a Long Term Evolution (LTE) communication system) and a gNodeB (gNB) (referring to a NodeB in a New Radio (NR) communication system) may also be referred to as an access point or other equivalent terms. Summary of the Invention

[0007] Solution to the problem

[0008] The present disclosure relates to a pre-5G or 5G communication system to provide resource mapping for PDSCH on an unlicensed spectrum. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

[0017] Figure 8 shows an example SS / PBCH block pattern within a time slot according to an embodiment of the present disclosure;

[0018] Figure 9 shows an example configuration of CORESET / CSS for SSB pattern 1 according to an embodiment of the present disclosure;

[0019] Figure 10 shows an example configuration of CORESET / CSS for SSB pattern 2 according to an embodiment of the present disclosure;

[0020] Figure 11 shows example PDSCH resource mapping according to SS / PBCH blocks in DRS according to an embodiment of the present disclosure;

[0021] Figure 12 shows an exemplary potentially actually transmitted SS / PBCH block within a DRS transmission window according to an embodiment of the present disclosure;

[0022] Figure 13A shows an example Type A PDSCH resource mapping according to an embodiment of the present disclosure;

[0023] Figure 13Bshows an example Type B PDSCH resource mapping according to an embodiment of the present disclosure;

[0024] Figure 14A A flow chart of a method for determining PDSCH time domain resource allocation according to an embodiment of the present disclosure is shown;

[0025] Figure 14B Another flow chart showing a method for determining PDSCH time domain resource allocation according to an embodiment of the present disclosure is shown; and

[0026] Figure 15 A flowchart of a method for resource mapping of a PDSCH according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0027] In one embodiment, a user equipment (UE) in a wireless communication system supporting shared spectrum channel access is provided. The UE includes at least one transceiver configured to receive a downlink channel set supporting shared spectrum channel access from a base station (BS). The UE also includes at least one processor operatively connected to at least one transceiver, the at least one processor configured to: identify a window for synchronization signal / physical broadcast channel (SS / PBCH) block transmission, a bitmap for SS / PBCH blocks (ssb-PositionsInBurst), and a parameter Q for quasi co-location (QCL) assumption from a downlink channel set; determine, based on the identified window for SS / PBCH block transmission, the identified bitmap for ssb-PositionsInBurst, and the identified parameter Q for QCL assumption, an SS / PBCH block in the identified window for SS / PBCH block transmission as one of the following: a first SS / PBCH block set assumed to be transmitted by the base station (BS) or a second SS / PBCH block set not transmitted by the BS; and determine a resource set unavailable for at least one physical downlink shared channel (PDSCH) as overlapping with the first SS / PBCH block set. The at least one transceiver of the UE is further configured to receive at least one PDSCH from the base station based on resources other than the determined resource set.

[0028] In another embodiment, a base station (BS) in a wireless communication system supporting shared spectrum channel access is provided. The BS includes at least one processor configured to determine a window for synchronization signal / physical broadcast channel (SS / PBCH) block transmission, a bitmap for the SS / PBCH block (ssb-PositionsInBurst), and a parameter Q for quasi co-location (QCL) assumption. The base station also includes at least one transceiver operatively connected to at least one processor, the at least one transceiver configured to transmit a downlink channel set including a window for SS / PBCH block transmission, a bitmap for ssb-PositionsInBurst, and a parameter Q for QCL assumption to a user equipment (UE), wherein the at least one processor is further configured to: indicate the SS / PBCH blocks to the UE based on the window for SS / PBCH block transmission, the bitmap for ssb-PositionsInBurst, and the parameter Q for QCL assumption, wherein the SS / PBCH blocks identified in the window for SS / PBCH block transmission are determined at the UE as one of the following: a first SS / PBCH block set assumed to be transmitted by the base station, or a second SS / PBCH block set assumed to be transmitted by the base station, and a resource set unavailable for at least one physical downlink shared channel (PDSCH) is determined to overlap with the first SS / PBCH block set. The at least one transceiver of the base station is further configured to transmit at least one PDSCH to the UE using resources other than the determined resource set.

[0029] In yet another embodiment, a method of a user equipment (UE) in a wireless communication system supporting shared spectrum channel access is provided. The method includes: receiving a downlink channel set supporting shared spectrum channel access from a base station (BS); identifying a window for synchronization signal / physical broadcast channel (SS / PBCH) block transmission, a bit map for SS / PBCH blocks (ssb-PositionsInBurst) and a parameter Q for quasi co-location (QCL) assumption from the downlink channel set; based on the identified window for SS / PBCH block transmission, the identified bit map for ssb-PositionsInBurst and the identified parameter for QCL assumption Q, determining the SS / PBCH blocks in the identified window for SS / PBCH block transmission as one of the following: a first SS / PBCH block set assumed to be sent by the BS, or a second SS / PBCH block set not sent by the BS; determining a resource set unavailable for at least one physical downlink shared channel (PDSCH) as overlapping with the first SS / PBCH block set; and receiving at least one PDSCH from the BS based on resources other than the determined resource set.

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

[0031] Before proceeding to the following inventive mode, it may be beneficial to set forth the 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, regardless of whether those elements are in physical contact with each other. The terms "send," "receive," and "communicate" and their derivatives encompass direct and indirect communication. The terms "include" and "comprises" and their derivatives are intended to include but are not limited to. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives are intended to include, be included within, be interconnected with, include, be contained within, be connected to or connected with, be coupled to or coupled with, be communicable with, cooperate with, interlace, be parallel, be close to, be bound to or bound with, have, have the property of, have a relationship with, or have a relationship with, etc. The term "controller" means any device, system, or part thereof that controls at least one operation. Such a controller can be implemented with hardware or a combination of hardware and software and / or firmware. The functionality 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, B, and C.

[0032] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed of a 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, processes, functions, objects, classes, instances, related data, or a portion thereof that are suitable for being implemented in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), random access memory (RAM), hard drive, compact disc (CD), digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store and later rewrite data, such as rewritable optical discs or erasable storage devices.

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

[0034] Discussed below Figures 1 to 15 The various embodiments used to describe the principles of the present disclosure in this patent document are intended only as illustrations and should not be interpreted 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.

[0035] The following documents are hereby incorporated by reference into this 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”; 3GPP TS 38.215 v15.4.0, “NR; Physical Layer Measurements”; and 3GPP TS 38.331 v15.4.0, “NR; Radio Resource Control (RRC) Protocol Specification”.

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

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

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

[0039] 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 (SB); 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 cell phone, wireless laptop, 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.

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

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

[0042] As described in greater detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for achieving reception reliability of data and control information in an advanced wireless communication system. In certain embodiments, one or more of gNBs 101-103 include circuitry, programming, or a combination thereof for efficient resource mapping of PDSCH in DRS over unlicensed spectrum.

[0043] although Figure 1 An example of a wireless network is shown, but Figure 1 Various variations are possible. For example, the wireless network can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide the UEs with direct wireless broadband access to network 130. Furthermore, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as an external telephone network or other types of data networks.

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

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

[0046] RF transceivers 210a-210n receive incoming RF signals, such as signals transmitted by UEs, from antennas 205a-205n 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 processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 220 sends the processed baseband signals to controller / processor 225 for further processing.

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

[0048] The controller / processor 225 can 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 via the RF transceivers 210a-210n, the RX processing circuitry 220, and the TX processing circuitry 215 in accordance with well-known principles. The controller / processor 225 can also support additional functionality, such as more advanced wireless communication functions. For example, the controller / processor 225 can support beamforming or directional routing operations, in which outgoing signals from multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. Any of a variety of other functions can be supported in the gNB 102 by the controller / processor 225.

[0049] The controller / processor 225 can also execute programs and other processes, such as the OS, that reside in the memory 230. The controller / processor 225 can move data into and out of the memory 230 as needed by the executing processes.

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

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

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

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

[0054] like Figure 3As shown, 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. 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.

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

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

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

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

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

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

[0061] although Figure 3 An example of a UE 116 is shown, but may be Figure 3 Make various changes. For example, it is possible to combine, further subdivide or omit Figure 3 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). In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or stationary devices.

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

[0063] In order to meet the demand for wireless data services that have increased since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (mmWave) 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 technology are discussed in 5G communication systems. In addition, the development of system network improvements in 5G communication systems is based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference cancellation, etc.

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

[0065] DL signals include data signals conveying information content, control signals conveying DL control information (DCI) formats, and reference signals (RSs), also known as pilot signals. The gNB can transmit data information (e.g., transport blocks) or DCI formats via the corresponding physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). The gNB can transmit one or more of several types of RSs, including channel state information RS (CSI-RS) and demodulation RS (DMRS). CSI-RS is intended for UEs to measure channel state information (CSI) or perform other measurements, such as those related to mobility support. DMRS can be transmitted only within the bandwidth of the corresponding PDCCH or PDSCH, and UEs can use DMRS to demodulate data or control information.

[0066] UL signals also include data signals conveying information content, control signals conveying UL control information (UCI), and RSs. The UE transmits data information (e.g., transport blocks) or UCI via the corresponding physical UL shared channel (PUSCH) or physical UL control channel (PUCCH). When a UE transmits data information and UCI simultaneously, it can multiplex both on the PUSCH or transmit them separately on the corresponding PUSCH and PUCCH. UCI includes Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information indicating correct or incorrect detection of a data transport block (TB) by the UE, a Scheduling Request (SR) indicating whether the UE has data in its buffer, and CSI reporting that enables the gNB to select appropriate parameters for link adaptation for PDSCH or PDCCH transmissions to the UE.

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

[0068] DL and UL transmissions can be based on Orthogonal Frequency Division Multiplexing (OFDM) waveforms, including using a variant of DFT precoding known as DFT-spread-OFDM.

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

[0070] Information bits (such as DCI bits or data bits 410) are encoded by an encoder 420, rate matched to the assigned 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 an SC 460 by an SC mapping unit 465, an inverse fast Fourier transform (IFFT) is performed 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 490 and transmitted by a radio frequency (RF) unit 495.

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

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

[0073] The UE typically 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 format that the UE is configured to receive. The DCI format includes cyclic redundancy check (CRC) bits to allow the UE to confirm correct detection of the DCI format. The DCI format type is identified by a radio network temporary identifier (RNTI) that scrambles the CRC bits. For DCI formats that schedule PDSCH or PUSCH to a single UE, the RNTI can be a cell RNTI (C-RNTI) and is used as a UE identifier.

[0074] For DCI formats scheduling PDSCH conveying system information (SI), the RNTI may be an SI-RNTI. For DCI formats scheduling PDSCH providing random access responses (RARs), the RNTI may be an RA-RNTI. For DCI formats scheduling PDSCH or PUSCH to a single UE before the UE establishes a radio resource control (RRC) connection with the serving gNB, the RNTI may be a temporary C-RNTI (TC-RNTI). For DCI formats providing TPC commands to a group of UEs, the RNTI may be either a TPC-PUSCH-RNTI or a TPC-PUCCH-RNTI. Each RNTI type can be configured to the UE via higher-layer signaling, such as RRC signaling. DCI formats scheduling PDSCH transmissions to a UE are also referred to as DL DCI formats or DL ​​assignments, whereas DCI formats scheduling PUSCH transmissions from a UE are also referred to as UL DCI formats or UL grants.

[0075] PDCCH transmissions can be within a physical RB (PRB) set. The gNB can configure one or more PRB sets, also known as control resource sets, for a UE to use for PDCCH reception. PDCCH transmissions can be within control channel elements (CCEs) included in the control resource set. The UE determines CCEs for PDCCH reception based on search spaces, such as the UE-specific search space (USS) for PDCCH candidates with a DCI format containing a CRC scrambled by the RNTI (e.g., C-RNTI) configured to the UE via UE-specific RRC signaling for scheduling PDSCH reception or PUSCH transmission, and the common search space (CSS) for PDCCH candidates with a DCI format containing a CRC scrambled by another RNTI. The set of CCEs that can be used for PDCCH transmission to the UE defines the PDCCH candidate location. A property of a control resource set is the transmission configuration indicator (TCI) state, which provides quasi-co-location information for the DMRS antenna ports used for PDCCH reception.

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

[0077] The gNB encodes and transmits each DCI format separately in the corresponding PDCCH. The RNTI masks the CRC of the DCI format codeword to enable the UE to identify the DCI format. For example, the CRC and RNTI can include 16 bits or 24 bits. The CRC of the (uncoded) DCI format bits 610 is determined using a CRC calculation unit 620, and the CRC is masked using an exclusive OR (XOR) operation unit 630 between the CRC bits and the RNTI bits 640. 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 appended to the DCI format information bits using a CRC appending unit 650. The encoder 660 performs channel coding (such as tail-biting convolutional coding or polar coding), followed by rate matching to the allocated resource rate by a rate matcher 670. The interleaving and modulation unit 680 applies interleaving and modulation (such as QPSK) and transmits an output control signal 690 .

[0078] Figure 7 An example decoding process 700 of a DCI format for use with 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. It can be implemented in dedicated circuits configured to perform the indicated functions. Figure 7 One or more of the components shown, or one or more of these components, can be implemented by one or more processors executing instructions to perform the indicated functions.Other embodiments may be used without departing from the scope of this disclosure.

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

[0080] The Federal Communications Commission defines unlicensed carriers to provide free public access spectrum. UEs are allowed to use unlicensed carriers only under the provision that the UE does not generate significant interference to communications in the licensed carrier and that communications in the unlicensed carrier are not protected from interference. For example, unlicensed carriers include industrial, scientific, and medical carriers and unlicensed national information infrastructure carriers that can be used by IEEE 802.11 devices. It is possible to deploy LTE radio access technology (RAT) on unlicensed frequency spectrum, which is also referred to as LTE-Unlicensed or LTE-U or Licensed Assisted Access (LAA).

[0081] The present disclosure focuses on the design of PDSCH resource mapping on unlicensed spectrum, where PDSCH includes PDSCH within DRS and DRS contains SS / PBCH blocks and configurable CORESET and PDSCH for RMSI, OSI or paging, and configurable channel state indicator reference signal (CSI-RS), which can also be considered as an enhancement of the discovery signal in LTE for the purpose of initial cell acquisition. The terminology of DRS can also be referred to as other equivalent terms, such as discovery burst, discovery reference signal and channel, discovery block, discovery signal, discovery signal and channel (DSCH), discovery burst (DB), etc. The transmission window for DRS can also refer to the transmission window for the components in DRS (e.g., the transmission window of the SS / PBCH block).

[0082] Since DRS contains SS / PBCH blocks and configured PDSCH for RMSI / OSI / paging, the UE's rate matching behavior for RMSI / OSI / paging PDSCH around SS / PBCH blocks needs to be defined. In order to properly define the rate matching behavior, an indication of the presence of SS / PBCH blocks within the timeslot used for rate matching purposes may be required.

[0083] At the same time, DRS is a compact unit in the time domain, so that the components within the DRS can use the same LBT to initiate transmission. Therefore, it is necessary to enhance the resource mapping configuration to achieve a compact unit in the time domain.

[0084] Figure 8 An example SS / PBCH block pattern within slot 800 is shown in accordance with an embodiment of the present disclosure. Figure 8 The illustrated embodiment of the SS / PBCH block pattern within time slot 800 is for illustration only. Figure 7 It does not limit the scope of the present disclosure.

[0085] Figure 8Two SS / PBCH block patterns within a time slot are shown, where pattern 1 801 has two possible SS / PBCH block positions as symbols #{2, 3, 4, 5} and #{9, 10, 11, 12}, respectively, and pattern 2 802 has two possible SS / PBCH block positions as symbols #{2, 3, 4, 5} and #{8, 9, 10, 11}, respectively.

[0086] In the present disclosure, the physical downlink shared channel (PDSCH) can refer to a PDSCH within a DRS that is scheduled by at least one of Type 0-PDCCH (e.g., RMSI), Type 0A-PDCCH (e.g., OSI), or Type 2-PDCCH (e.g., paging). In the present disclosure, the physical downlink shared channel (PDSCH) can also refer to a PDSCH scheduled by a UE-specific PDCCH.

[0087] The time domain resource mapping of PDSCH is represented as a start length indicator SLIV, where SLIV is determined by the start indicator S and the length indicator L as follows: if (L-1)≤7, then SLIV=14*(L-1)+S; otherwise, SLIV=14*(14-L+1)+(14-S-1), where 0 <L≤14-S。

[0088] In one embodiment, the PDSCH is assumed to be in the same slot as the associated PDCCH, and K_0=0.

[0089] In another embodiment, if a single CORESET is configured within a time slot and the CSS starts from symbol #0, then the time domain configuration of the resource mapping of at least the PDSCH can include a configuration starting from the middle of the time slot (e.g., symbol #7 or #8) and ending no earlier than the last symbol of the second SS / PBCH block (e.g., symbol #12 or #13).

[0090] In another embodiment, the UE determines the time domain configuration of the resource mapping of the PDSCH according to the position of the received SS / PBCH block in the time slot. For example, when the received SS / PBCH block is the first SS / PBCH block in the time slot, the UE determines the starting symbol as S, and when the received SS / PBCH block is the second SS / PBCH block in the time slot, the UE determines the starting symbol as S+X, where X is fixed in one example (for example, X=7 in SS / PBCH block pattern 1 or X=6 in SS / PBCH block pattern 2), and in another example, X is determined by the configuration of the CORESET and / or CSS.

[0091] In another embodiment, the UE determines the time domain configuration of the resource mapping of the PDSCH according to the configuration of the CORESET and / or CSS. For example, for each configuration of the CORESET and / or CSS, there can be a PDSCH time domain resource allocation table.

[0092] In yet another embodiment, if a single CSS is configured, there is at least one configuration such that the PDSCH is not mapped to the last symbol (eg, #13), or if two CSSs are configured, both CSSs are configured at the beginning of the slot.

[0093] In yet another embodiment, if two CSSs are configured with starting symbols #0 and #7, respectively, there is at least one configuration such that the PDSCH is not mapped to symbol #6 and symbol #13.

[0094] In yet another embodiment, the UE determines the PDSCH mapping type based on the configuration of the CORESET and / or CSS.

[0095] If the SS / PBCH block pattern is pattern 1, such as Figure 8 As shown in (e.g., 801), the following examples or part of the following examples (e.g., Tables 1-1 to 1-5) can be supported.

[0096] Figure 9 An example configuration of CORESET / CSS for SSB pattern 1 900 is shown according to an embodiment of the present disclosure. Figure 9 The illustrated embodiment of the CORESET / CSS configuration for SSB pattern 1 900 is for illustration only. Figure 9 It does not limit the scope of the present disclosure.

[0097] When the number of symbols for CORESET is configured as 1 and 1 common search space (CSS) is configured within CORESET and starting from symbol #0 (e.g., Figure 9 As shown in 201), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Table 1-1. Table 1-1 shows an example of PDSCH time domain resource mapping configuration.

[0098] [Table 1-1]

[0099] index PDSCH mapping type K_0 S L 1 Type A 0 1 5 2 Type A 0 8 5 3 Type A 0 1 6 4 Type A 0 8 6 5 Type A 0 1 12 6 Type A 0 1 13

[0100] When the number of symbols for CORESET is configured as 2 and 1 CSS is configured starting from symbol #0 within CORESET (e.g. Figure 9As shown in 902), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Table 1-2. Table 1-2 shows an example of PDSCH time domain resource mapping configuration.

[0101] [Table 1-2]

[0102] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 9 4 3 Type A 0 2 5 4 Type A 0 9 5 5 Type A 0 2 11 6 Type A 0 2 12

[0103] When the number of symbols for CORESET is configured as 1 and 2 CSSs are configured starting from symbols #0 and #7 within CORESET accordingly (e.g. Figure 9 As shown in 903), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Table 1-3. Table 1-3 shows an example of PDSCH time domain resource mapping configuration.

[0104] [Table 1-3]

[0105] index PDSCH mapping type K_0 S L 1 Type A 0 1 5 2 Type A 0 1 6 3 Type B 0 8 5 4 Type B 0 8 6

[0106] When the number of symbols for a CORESET is configured as 1 and two CSSs are configured within the CORESET starting from symbols #0 and #1 accordingly (e.g., Figure 9 As shown in 904), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Tables 1-4. Tables 1-4 show examples of PDSCH time domain resource mapping configurations.

[0107] [Table 1-4]

[0108] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type B 0 9 4 3 Type A 0 2 5 4 Type B 0 9 5 5 Type A 0 2 6 6 Type B 0 8 6

[0109] Figure 10 An example configuration of CORESET / CSS for SSB pattern 2 1000 is shown according to an embodiment of the present disclosure. Figure 10 The illustrated embodiment of the configuration of CORESET / CSS for SSB pattern 2 1000 is for illustration only. Figure 10 It does not limit the scope of the present disclosure.

[0110] When the number of symbols for CORESET is configured as 2 and 2 CSSs are configured starting from symbols #0 and #7 within CORESET accordingly (e.g., Figure 9 As shown in 905), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Tables 1-5. Tables 1-5 show examples of PDSCH time domain resource mapping configurations.

[0111] [Table 1-5]

[0112] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 2 5 3 Type B 0 9 4 4 Type B 0 9 5

[0113] If the SS / PBCH block pattern is pattern 2, such as Figure 8 As shown in (e.g., 802), at least the following configurations can be supported.

[0114] When the number of symbols for CORESET is configured as 1 and 1 common search space (CSS) is configured within CORESET and starting from symbol #0 (e.g., Figure 10 As shown in 1001), PDSCH time domain resource allocation can support at least one of the following configurations as shown in Table 2-1. Table 2-1 shows an example of PDSCH time domain resource mapping configuration.

[0115] [Table 2-1]

[0116] index PDSCH mapping type K_0 S L 1 Type A 0 1 5 2 Type A 0 7 5 3 Type A 0 1 6 4 Type A 0 7 6 5 Type A 0 1 12 6 Type A 0 1 13

[0117] When the number of symbols for CORESET is configured as 2 and 1 CSS is configured starting from symbol #0 within CORESET (e.g. Figure 10 As shown in 1002), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Table 2-2. Table 2-2 shows an example of PDSCH time domain resource mapping configuration.

[0118] [Table 2-2]

[0119] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 8 4 3 Type A 0 2 5 4 Type A 0 8 5 5 Type A 0 2 6 6 Type A 0 8 6 7 Type A 0 2 11 8 Type A 0 2 12

[0120] When the number of symbols for CORESET is configured as 1 and 2 CSSs are configured within CORESET starting from symbols #0 and #7 accordingly (e.g., Figure 10 As shown in 1003), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Table 2-3. Table 2-3 shows an example of PDSCH time domain resource mapping configuration.

[0121] [Table 2-3]

[0122] index PDSCH mapping type K_0 S L 1 Type A 0 1 5 2 Type A 0 1 6 3 Type B 0 8 5 4 Type B 0 8 6

[0123] When the number of symbols for a CORESET is configured as 1 and two CSSs are configured within the CORESET starting from symbols #0 and #1 accordingly (e.g., Figure 10 As shown in 1004), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Table 2-4. Table 2-4 shows an example of PDSCH time domain resource mapping configuration.

[0124] [Table 2-4]

[0125]

[0126]

[0127] When the number of symbols for CORESET is configured as 2 and 2 CSSs are configured starting from symbols #0 and #6 within CORESET (e.g., Figure 10 As shown in 1005), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Table 2-5. Table 2-5 shows an example of PDSCH time domain resource mapping configuration.

[0128] [Table 2-5]

[0129] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type B 0 8 4

[0130] When the number of symbols for CORESET is configured as 1 and 2 CSSs are configured starting from symbols #0 and #6 within CORESET (e.g., Figure 10 As shown in 1006), PDSCH time domain resource allocation may support at least one of the following configurations as shown in Table 2-6. Table 2-6 shows an example of PDSCH time domain resource mapping configuration.

[0131] [Table 2-6]

[0132] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type B 0 8 4 3 Type A 0 1 5 4 Type B 0 7 5

[0133] In yet another embodiment, the UE determines the PDSCH mapping type regardless of the configuration of the CORESET or CSS.

[0134] If the SS / PBCH block pattern is pattern 1, such as Figure 8 As shown (e.g., 801), and the duration of the symbols used for type B PDSCH mapping is limited to 2, 4, and 7, at least the following examples or part of the following examples (e.g., Tables 3-1, 3-2, and 3-3) can be supported. Table 3-1 shows an example of a PDSCH time domain resource mapping configuration.

[0135] [Table 3-1]

[0136] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 1 5 3 Type A 0 1 6 4 Type A 0 1 12 5 Type A 0 1 13 6 Type A 0 2 5 7 Type A 0 2 11 8 Type A 0 2 12 9 Type B 9 4

[0137] In one variation of this set of examples (e.g., Table 3-1), at least one additional entry as in Table 3-2 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 3-2 shows an example of a PDSCH time domain resource mapping configuration.

[0138] [Table 3-2]

[0139] index PDSCH mapping type K_0 S L - Type A 0 9 4 - Type A 0 9 5 - Type A 0 8 5 - Type A 0 8 6

[0140] In another variation of this set of examples (eg, Table 3-1), one additional entry is supported as in Table 3-3. Table 3-3 shows an example of a PDSCH time domain resource mapping configuration.

[0141] [Table 3-3]

[0142] index PDSCH mapping type K_0 S L - Type A 0 2 6

[0143] If the SS / PBCH block pattern is pattern 1, such as Figure 8 As shown (e.g., 801), and the duration of the symbols used for type B PDSCH mapping is limited to 2, 4, 5, and 7, at least the following examples or part of the following examples (e.g., Tables 4-1, 4-2, and 4-3) can be supported. Table 4-1 shows an example of a PDSCH time domain resource mapping configuration.

[0144] [Table 4-1]

[0145] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 1 5 3 Type A 0 1 6 4 Type A 0 1 12 5 Type A 0 1 13 6 Type A 0 2 5 7 Type A 0 2 11 8 Type A 0 2 12 9 Type B 0 9 4 10 Type B 0 9 5 11 Type B 0 8 5

[0146] In one variation of this set of examples (e.g., Table 4-1), at least one additional entry as in Table 4-2 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 4-2 shows an example of a PDSCH time domain resource mapping configuration.

[0147] [Table 4-2]

[0148] index PDSCH mapping type K_0 S L - Type A 0 9 4 - Type A 0 9 5 - Type A 0 8 5 - Type A 0 8 6

[0149] In another variation of this set of examples (eg, Table 4-1), one additional entry is supported as in Table 4-3. Table 4-3 shows an example of a PDSCH time domain resource mapping configuration.

[0150] [Table 4-3]

[0151] index PDSCH mapping type K_0 S L - Type A 0 2 6

[0152] If the SS / PBCH block pattern is pattern 1, such as Figure 8 As shown (e.g., 801), and the duration of the symbols used for type B PDSCH mapping is limited to 2, 4, 6, and 7, at least the following examples or part of the following examples (e.g., Tables 5-1 and 5-2) can be supported. Table 5-1 shows an example of a PDSCH time domain resource mapping configuration.

[0153] [Table 5-1]

[0154] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 1 5 3 Type A 0 1 6 4 Type A 0 1 12 5 Type A 0 1 13 6 Type A 0 2 5 7 Type A 0 2 11 8 Type A 0 2 12 9 Type B 0 9 4 10 Type B 0 8 6 11 Type A 0 2 6

[0155] In one variation of this set of examples (e.g., Table 5-1), at least one additional entry as in Table 5-2 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 5-3 shows an example of a PDSCH time domain resource mapping configuration.

[0156] [Table 5-3]

[0157] index PDSCH mapping type K_0 S L - Type A 0 9 4 - Type A 0 9 5 - Type A 0 8 5 - Type A 0 8 6

[0158] If the SS / PBCH block pattern is pattern 1, such as Figure 8 As shown (e.g., 801), and the duration of the symbols used for type B PDSCH mapping is limited to 2, 4, 5, 6, and 7, at least the following examples or part of the following examples (e.g., Tables 6-1 and 6-2) can be supported. Table 6-1 shows an example of a PDSCH time domain resource mapping configuration.

[0159] [Table 6-1]

[0160] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 1 5 3 Type A 0 1 6 4 Type A 0 1 12 5 Type A 0 1 13 6 Type A 0 2 5 7 Type A 0 2 11 8 Type A 0 2 12 9 Type B 0 9 4 10 Type B 0 8 6 11 Type A 0 2 6 12 Type B 0 9 5 13 Type B 0 8 5

[0161] In one variation of this set of examples (e.g., Table 6-1), at least one additional entry as in Table 6-2 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 6-2 shows an example of a PDSCH time domain resource mapping configuration.

[0162] [Table 6-2]

[0163] index PDSCH mapping type K_0 S L - Type A 0 9 4 - Type A 0 9 5 - Type A 0 8 5 - Type A 0 8 6

[0164] If the SS / PBCH block pattern is pattern 2, such as Figure 8As shown (e.g., 802), and the duration of symbols for Type B PDSCH mapping is limited to 2, 4, and 7, at least the following examples or part of the following examples (e.g., Tables 7-1 to 7-2) can be supported.

[0165] For example, one of the following Type B examples with {K_0, S, L} = {0, 6, 7} or {0, 7, 7} (e.g., indices 10 and 11 in Table 7-1) may be supported to address scenarios with a single SS / PBCH block (e.g., the first SS / PBCH block in a slot), such as Figure 8 Table 7-1 shows an example of PDSCH time domain resource mapping configuration.

[0166] [Table 7-1]

[0167]

[0168]

[0169] In one variation of this set of examples (e.g., Table 7-1), at least one additional entry as in Table 7-2 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 7-2 shows an example of a PDSCH time domain resource mapping configuration.

[0170] [Table 7-2]

[0171] index PDSCH mapping type K_0 S L - Type A 0 8 4 - Type A 0 7 5 - Type A 0 8 5 - Type A 0 7 6 - Type A 0 8 6 - Type A 0 6 7 - Type A 0 7 7 - Type A 0 9 4 - Type A 0 10 5

[0172] In another variation of this set of examples (eg, Table 7-2), one additional entry is supported as in Table 7-3. Table 7-3 shows an example of a PDSCH time domain resource mapping configuration.

[0173] [Table 7-3]

[0174] index PDSCH mapping type K_0 S L - Type A 0 2 6

[0175] If the SS / PBCH block pattern is pattern 2, such as Figure 8 As shown (e.g., 802), and the duration of the symbols used for type B PDSCH mapping is limited to 2, 4, 5, and 7, at least the following examples or part of the following examples (e.g., Tables 8-1, 8-2, and 8-3) can be supported. Table 8-1 shows an example of a PDSCH time domain resource mapping configuration.

[0176] [Table 8-1]

[0177] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 1 5 3 Type A 0 1 6 4 Type A 0 1 12 5 Type A 0 1 13 6 Type A 0 2 5 7 Type A 0 2 11 8 Type A 0 2 12 9 Type B 0 8 4 10 Type B 0 8 5 11 Type B 0 7 5

[0178] In one variation of this set of examples (e.g., Table 8-1), at least one additional entry as in Table 8-2 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 8-2 shows an example of a PDSCH time domain resource mapping configuration.

[0179] [Table 8-2]

[0180]

[0181]

[0182] In another variation of this set of examples (e.g., Table 8-1), an additional entry as in Table 8-3 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 8-3 shows an example of a PDSCH time domain resource mapping configuration.

[0183] [Table 8-3]

[0184] index PDSCH mapping type K_0 S L - Type A 0 2 6

[0185] If the SS / PBCH block pattern is pattern 2, such as Figure 8 As shown (e.g., 802), and the duration of the symbols used for type B PDSCH mapping is limited to 2, 4, 6, and 7, at least the following examples or part of the following examples (e.g., Tables 9-1 and 9-2) can be supported. Table 9-1 shows an example of a PDSCH time domain resource mapping configuration.

[0186] [Table 9-1]

[0187] index PDSCH mapping type K_0 S L 1 Type A 0 2 4 2 Type A 0 1 5 3 Type A 0 1 6 4 Type A 0 1 12 5 Type A 0 1 13 6 Type A 0 2 5 7 Type A 0 2 11 8 Type A 0 2 12 9 Type B 0 8 4 10 Type B 0 8 6 11 Type B 0 7 6 12 Type A 0 2 6

[0188] In one variation of this set of examples (e.g., Table 9-1), at least one additional entry as in Table 9-2 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 9-2 shows an example of a PDSCH time domain resource mapping configuration.

[0189] [Table 9-2]

[0190] index PDSCH mapping type K_0 S L - Type A 0 8 4 - Type A 0 7 5 - Type A 0 8 5 - Type A 0 7 6 - Type A 0 8 6

[0191] If the SS / PBCH block pattern is pattern 2, such as Figure 8 As shown (e.g., 802), and the duration of the symbols used for type B PDSCH mapping is limited to 2, 4, 5, 6, and 7, at least the following examples or part of the following examples (e.g., Tables 10-1 and 10-2) can be supported. Table 10-1 shows an example of a PDSCH time domain resource mapping configuration.

[0192] [Table 10-1]

[0193]

[0194]

[0195] In one variation of this set of examples (e.g., Table 10-1), at least one additional entry as in Table 10-2 is supported or merged with a configuration having the same K_0, S, and L but with PDSCH mapping type B (e.g., the corresponding value for PDSCH mapping type in the table is changed to "Type A and Type B"). Table 10-2 shows an example of a PDSCH time domain resource mapping configuration.

[0196] [Table 10-2]

[0197] index PDSCH mapping type K_0 S L - Type A 0 8 4 - Type A 0 7 5 - Type A 0 8 5 - Type A 0 7 6 - Type A 0 8 6

[0198] In yet another embodiment, the UE determines the PDSCH mapping type based on the position of the received SS / PBCH block in the slot. For example, if there are two CSSs configured with starting symbols #0 and #7, respectively, the UE assumes PDSCH mapping type A if the received SS / PBCH block is the first SS / PBCH block in the slot, and assumes PDSCH mapping type B if the received SS / PBCH block is the second SS / PBCH block in the slot.

[0199] In one embodiment, in addition to the supported indication of the SS / PBCH blocks actually transmitted within the burst as in the NR standard specification, there may be at least one indication of the SS / PBCH blocks actually transmitted, and at least one of the following methods can be supported for this purpose.

[0200] In one example, there is an indication via the PBCH payload (eg, MIB) of all actually transmitted SS / PBCH blocks within the DRS transmission window.

[0201] In one example, the indication is a bitmap whose length is equal to the maximum number of potential SS / PBCH blocks within the DRS transmission window, and each bit in the bitmap indicates whether the corresponding SS / PBCH block is actually sent (e.g., 1 means sent, and 0 means not sent).

[0202] In another example, the indication is a bitmap having a length equal to the maximum number of SS / PBCH blocks actually sent within the DRS transmission window, and each bit in the bitmap indicates whether the corresponding SS / PBCH block is actually sent (for example, 1 means sent, and 0 means not sent).

[0203] In one example, the indication of the actual transmitted SS / PBCH block by the PBCH content can be consistent with the indication of the actual transmitted SS / PBCH block by the RMSI and / or RRC.

[0204] In another example, the indication of the actual transmitted SS / PBCH block by RMSI and / or RRC can override the indication of the actual transmitted SS / PBCH block by PBCH content.

[0205] In yet another example, there is an indication via the PBCH payload (eg, a bit not in the MIB) of the SS / PBCH blocks actually transmitted within the timeslot containing the SS / PBCH blocks.

[0206] In one example, the indication is a bitmap having a length of 2, where the first bit in the bitmap indicates whether the first SS / PBCH block in the time slot is actually transmitted, and the second bit in the bitmap indicates whether the second SS / PBCH block in the time slot is actually transmitted (e.g., 1 means transmitted, and 0 means not transmitted).

[0207] In another example, the indication uses 1 bit, which is used to indicate whether other SS / PBCH blocks in the same time slot of the received SS / PBCH block are actually transmitted.

[0208] In yet another example, the indication uses one bit, where the one bit indicates which of the two SS / PBCH blocks in the timeslot is actually transmitted. In one aspect of this example, if one SS / PBCH block in the timeslot is actually transmitted, the position of the SS / PBCH block actually transmitted is known to the UE, for example, by being fixed as the first or second potential SS / PBCH block in the timeslot.

[0209] In one example, the indication of the SS / PBCH blocks actually transmitted in a time slot by the PBCH content can be consistent with the indication of the SS / PBCH blocks actually transmitted by the RMSI and / or RRC.

[0210] In another example, the indication of the SS / PBCH blocks actually transmitted via RMSI and / or RRC may override the indication of the SS / PBCH blocks actually transmitted in the timeslot via PBCH content.

[0211] In yet another example, there is an indication of all actually transmitted SS / PBCH blocks within the DRS transmission window via a DCI format containing scheduling information for the PDSCH.

[0212] In one example, the indication is a bitmap having a length equal to the maximum number of SS / PBCH blocks that may be sent within the DRS transmission window, and each bit in the bitmap indicates whether the corresponding SS / PBCH block is actually sent (e.g., 1 means sent, and 0 means not sent).

[0213] In another example, the indication is a bitmap having a length equal to the maximum number of SS / PBCH blocks actually sent within the DRS transmission window, and each bit in the bitmap indicates whether the corresponding SS / PBCH block is actually sent (for example, 1 means sent, and 0 means not sent).

[0214] In one example, the indication of the SS / PBCH block actually sent through the DCI format can be consistent with the indication of the SS / PBCH block actually sent through the RMSI and / or RRC.

[0215] In another example, the indication of the SS / PBCH block actually sent via RMSI and / or RRC may overwrite the indication of the SS / PBCH block actually sent via DCI format.

[0216] In yet another example, the indication of the SS / PBCH block actually transmitted via the DCI format may overlay the indication of the SS / PBCH block actually transmitted via the RMSI and / or RRC.

[0217] In yet another example, the DCI formats considered in this method may be limited to DCI formats with CRC scrambled by SI-RNTI, and the corresponding CSS set is a Type 0-PDCCH CSS set (eg, a DCI format for RMSI).

[0218] In yet another example, the DCI formats considered in this method may be limited to DCI formats carried by at least one of a DCI format with a CRC scrambled by SI-RNTI (e.g., DCI for RMSI or OSI) or a DCI format with a CRC scrambled by P-RNTI (e.g., DCI format for paging).

[0219] In yet another example, there is an indication of the SS / PBCH blocks actually transmitted within the time slot containing the SS / PBCH blocks through a DCI format containing scheduling information for the PDSCH.

[0220] In one example, the indication is a bitmap having a length of 2, where the first bit in the bitmap indicates whether the first SS / PBCH block in the time slot is actually transmitted, and the second bit in the bitmap indicates whether the second SS / PBCH block in the time slot is actually transmitted (e.g., 1 means transmitted, and 0 means not transmitted).

[0221] In another example, one bit is used to indicate whether other SS / PBCH blocks that are not QCLed with the DMRS of the PDCCH containing the DCI format are actually transmitted. For example, a bit in the DCI format carried by the PDCCH associated with the first SS / PBCH block indicates whether the second SS / PBCH block is actually transmitted, while a bit in the DCI format carried by the PDCCH associated with the second SS / PBCH block indicates whether the first SS / PBCH block is actually transmitted (for example, 1 means transmitted, and 0 means not transmitted).

[0222] If the UE detects that the indicator value in the DCI format is 1, the UE assumes that both SS / PBCH blocks in the time slot are actually transmitted and the RBs / REs used for the SS / PBCH blocks are not available for PDSCH. If the UE detects that the indicator value in the DCI format is 0, the UE assumes that only the SS / PBCH block in the received time slot is actually transmitted, while other SS / PBCH blocks in the time slot are not actually transmitted, and the RBs / REs used for the received SS / PBCH block are not available for PDSCH, while the RBs / REs used for other SS / PBCH blocks in the time slot may be available for PDSCH.

[0223] In another example, the indication uses 1 bit, which is used to indicate whether 1 or 2 SS / PBCH blocks are actually transmitted. For example, if the UE detects that the indicator value in the DCI format is 1, the UE assumes that two SS / PBCH blocks in the time slot are actually transmitted, and the RB / RE used for the SS / PBCH block is not available for PDSCH. If the UE detects that the indicator value in the DCI format is 0, the UE assumes that only one SS / PBCH block in the time slot is actually transmitted and which SS / PBCH block in the SS / PBCH block actually transmitted in the time slot is predefined (for example, fixed as the first SS / PBCH block or the second SS / PBCH block), and the RB / RE used for the SS / PBCH block actually transmitted is not available for PDSCH, while the RB / RE used for the other SS / PBCH blocks in the time slot can be used for PDSCH.

[0224] In one example, the indication of the SS / PBCH blocks actually transmitted in a time slot through the DCI format may be consistent with the indication of the SS / PBCH blocks actually transmitted through the RMSI and RRC.

[0225] In another example, the indication of the actually transmitted SS / PBCH block via RMSI and / or RRC can overlay the indication of the actually transmitted SS / PBCH block via DCI format.

[0226] In yet another example, the indication of the SS / PBCH block actually transmitted via the DCI format can overlay the indication of the SS / PBCH block actually transmitted via the RMSI and / or RRC.

[0227] In yet another example, the DCI formats considered in this method may be limited to DCI formats with CRC scrambled by SI-RNTI, and the corresponding CSS set is a Type 0-PDCCH CSS set (eg, a DCI format for RMSI).

[0228] In yet another example, the DCI formats considered in this method may be limited to DCI formats carried by at least one of a DCI format with a CRC scrambled by SI-RNTI (e.g., DCI for RMSI or OSI) or a DCI format with a CRC scrambled by P-RNTI (e.g., DCI format for paging).

[0229] Figure 11 An example PDSCH resource mapping 1100 according to SS / PBCH blocks in DRS is shown according to an embodiment of the present disclosure. Figure 11 The illustrated embodiment of the PDSCH resource mapping 1100 is for illustration only. Figure 11 It does not limit the scope of the present disclosure.

[0230] In one embodiment, the UE assumes that the RBs / REs mapped for all potential SS / PBCH blocks that are part of the NR-U DRS are not available for PDSCH, e.g., where the NR-U DRS is within the DRS transmission window. For example, the gNB may rate match around the RBs / REs mapped for all potential SS / PBCH blocks that are part of the NR-U DRS, regardless of the actual SS / PBCH blocks transmitted.

[0231] In one aspect of this embodiment, the gNB indicates to the UE the time domain position of the DRS within the DRS transmission window. Figure 11 (e.g., 1101) shows an example of this embodiment, where RBs / REs mapped for all potential SS / PBCH blocks that are part of DRS are not available for PDSCH, while RBs / REs mapped for all potential SS / PBCH blocks that are not part of DRS are available for PDSCH.

[0232] In one example, the DCI formats considered in this method may be limited to DCI formats with CRC scrambled by SI-RNTI, and the corresponding CSS set is a Type 0-PDCCH CSS set (eg, a DCI format for RMSI).

[0233] In another embodiment, the UE assumes that the RBs / REs mapped for all potential SS / PBCH blocks within the DRS transmission window are not available for PDSCH. For example, the gNB may rate match around the RBs / REs mapped for all potential SS / PBCH blocks within the DRS transmission window, regardless of the actual SS / PBCH blocks transmitted.

[0234] Figure 11 (eg, 1102) shows an example of this embodiment, where RBs / REs mapped for all potential SS / PBCH blocks within the DRS transmission window are unavailable for PDSCH.

[0235] In one example, the PDSCH used for this embodiment may be limited to PDSCH scheduled by Type 0-PDCCH with CRC scrambled by SI-RNTI (eg, PDSCH of RMSI).

[0236] In yet another embodiment, the UE assumes that the RBs / REs mapped for the SS / PBCH blocks actually transmitted as part of the NR-U DRS are not available for PDSCH. For example, the gNB may rate match around the RBs / REs mapped for the SS / PBCH blocks actually transmitted as part of the NR-U DRS.

[0237] Figure 11 (e.g., 1103) shows an example of this embodiment, where RBs / REs mapped for SS / PBCH blocks actually transmitted as part of NR-U DRS are not available for PDSCH (e.g., SSB#0 is actually transmitted in 1103), while RBs / REs not mapped for SS / PBCH blocks actually transmitted as part of DRS are available for PDSCH.

[0238] In one example, the actually transmitted SS / PBCH block as part of the NR-U DRS can be indicated as the actually transmitted SS / PBCH block in the time slot (e.g., by the PBCH content or DCI format according to an embodiment of the present disclosure), and the PDSCH for this embodiment may be limited to the PDSCH scheduled by the Type0-PDCCH with the CRC scrambled by the SI-RNTI (e.g., the PDSCH of the RMSI). For example, the UE assumes that the RB / RE mapped for the actually transmitted SS / PBCH block in the time slot is not available for the PDSCH, where the PDSCH is scheduled by the Type0-PDCCH with the CRC scrambled by the SI-RNTI and in the same time slot as the actually transmitted SS / PBCH block.

[0239] In another example, there may not be an indication of the actual transmitted SS / PBCH blocks within a slot, and the UE can determine the rate matching behavior based on the resource mapping information of the PDSCH. For example, if the symbols of the resource mapping for the PDSCH overlap with the symbols containing the SS / PBCH blocks within the same slot without the DMRS of the PDCCH containing the QCL assumption of the DCI format, the UE assumes that the SS / PBCH blocks within the same slot without the DMRS of the PDCCH containing the QCL assumption of the DCI format are not actually transmitted.

[0240] In yet another embodiment, the UE assumes that the RBs / REs mapped for the potentially actually transmitted SS / PBCH blocks within the DRS transmission window are not available for PDSCH. The potentially actually transmitted SS / PBCH blocks within the DRS transmission window are selected from the candidate SS / PBCH blocks within the DRS transmission window based on an indication of the actually transmitted SS / PBCH blocks (e.g., RMSI and / or ssb-PositionsInBrst in RRC) and a wrapping modulus value (e.g., QCL assumption indicated by PBCH or RMSI).

[0241] In one example, the SS / PBCH blocks potentially actually transmitted within the DRS transmission window can be a bitmap, where the first Q bits in the bitmap indicate the SS / PBCH blocks actually transmitted (e.g., via RMSI and / or RRC) repeated until the end of the DRS transmission window, where Q is a wrap-around modulus value (e.g., a QCL assumption), and the bits in the bitmap for the SS / PBCH blocks potentially actually transmitted within the DRS transmission window indicate whether the corresponding SS / PBCH blocks within the DRS transmission window are potentially transmitted.

[0242] In another example, if the (i+1)th bit in the bitmap indicating the SS / PBCH block actually transmitted (e.g., ssb-PositionsInBurst in RMSI and / or RRC) takes the value '1', the SS / PBCH block with the candidate position indexed as (i+n*Q) within the DRS transmission window is assumed to be potentially actually transmitted (e.g., can be transmitted by the gNB); and if the (i+1)th bit in the bitmap indicating the SS / PBCH block actually transmitted (e.g., If the ssb-PositionsInBurst) in the RMSI and / or RRC takes the value '0', the SS / PBCH block with the candidate position index (i+n*Q) within the DRS transmission window is assumed to be not actually transmitted (e.g., not transmitted by the gNB), where Q is the wrap modulus value, (i+1) is the index in the bitmap, where 0≤i≤Q-1, and n is a non-negative integer such that i+n*Q is less than or equal to the maximum number of candidate SS / PBCH blocks within the DRS transmission window. The UE assumes that the number of SS / PBCH blocks actually transmitted in the DRS transmission window is the number of '1's in the first Q bits of the bitmap indicating the SS / PBCH blocks actually transmitted (e.g., by RMSI and / or RRC), and if bits other than the first Q bits take the value '0' in the bitmap, it is equivalent to the number of '1's in the bitmap indicating the SS / PBCH blocks actually transmitted (e.g., by RMSI and / or RRC).

[0243] Figure 12 An exemplary potentially actually transmitted SS / PBCH block within a DRS transmission window 1200 according to an embodiment of the present disclosure is shown. Figure 12 The illustrated example of potentially actually transmitted SS / PBCH blocks within the DRS transmission window 1200 is for illustration only. Figure 12 It does not limit the scope of the present disclosure.

[0244] Figure 12 An example of potentially actually transmitted SS / PBCH blocks within a DRS transmission window is shown, where the considered DRS transmission window is configured with 20 candidate SS / PBCH block positions and a wrapping modulus value Q=4, and then the first 4 bits of the bitmap indicating the actually transmitted SS / PBCH blocks (e.g., RMSI and / or ssb-PositionsInburst in RRC) are repeated 5 times (e.g., n=0, 1, 2, 3, or 4) in the DRS transmission window.

[0245] Figure 11(e.g., 1104) shows an example of this embodiment, where RBs / REs mapped for SS / PBCH blocks potentially actually transmitted within the DRS transmission window are not available for PDSCH (e.g., SSB#0 in 1104 is the indicated actually transmitted SSB and the wrap modulus value is 2), while RBs / REs not mapped for SS / PBCH blocks potentially actually transmitted within the DRS transmission window are available for PDSCH.

[0246] In one example, the PDSCH used for this embodiment may be limited to PDSCHs that are not scheduled by a Type 0-PDCCH containing a DCI format with a CRC scrambled by the SI-RNTI (e.g., PDSCH for RMSI). For example, the UE assumes that RBs / REs mapped for potentially actually transmitted SS / PBCH blocks within the DRS transmission window are not available for PDSCHs that are scheduled by a DCI format other than the DCI format for RMSI.

[0247] In another example, the SS / PBCH blocks that are potentially actually transmitted within the DRS transmission window are also used for radio link monitoring. For example, the RLM-RS corresponding to the SS / PBCH blocks that are potentially actually transmitted within the DRS transmission window is used for synchronization and out-of-sync evaluation, while the RLM-RS that does not correspond to the SS / PBCH blocks that are potentially actually transmitted within the DRS transmission window is not used for synchronization and out-of-sync evaluation.

[0248] In yet another example, the SS / PBCH blocks potentially actually transmitted within the DRS transmission window are also used for PDCCH monitoring. In one method, if a PDCCH candidate in a time slot is mapped to one or more REs / RBs that overlap with the REs / RBs of the SS / PBCH block positions as the SS / PBCH blocks potentially actually transmitted within the DRS transmission window, the UE does not expect to monitor the PDCCH candidate. In one example, the PDCCH considered in this method may be limited to any PDCCH other than a Type 0-PDCCH containing a DCI format with a CRC scrambled by the SI-RNTI (e.g., a PDCCH of RMSI).

[0249] In one embodiment, to support enhanced configuration of PDSCH resource allocation for RMSI, as described in this disclosure, the NR standard specification default PDSCH time domain resource allocation A for normal CP may be modified or enhanced.

[0250] Figure 13A An example Type A PDSCH resource mapping 1300 is shown according to an embodiment of the present disclosure. Figure 13A The illustrated embodiment of a Type A PDSCH resource mapping 1300 is for illustration only. Figure 13A It does not limit the scope of the present disclosure.

[0251] Figure 13B An example Type B PDSCH resource mapping 1350 is shown according to an embodiment of the present disclosure. Figure 13B The shown embodiment of the Type B PDSCH resource mapping 1350 is for illustration only. Figure 13B It does not limit the scope of the present disclosure.

[0252] For PDSCH mapping types as type A and type B respectively, Figure 13A and Figure 13B A summary of the default PDSCH time domain resource allocation for RMSI support is shown in FIG.

[0253] In one example, the enhanced configuration of PDSCH resource allocation for RMSI as described in this disclosure can replace some of the supported NR standard specification configurations, or partially replace some of the supported NR standard specification configurations by branching on the value of dmrs-TypeA-Position (one value corresponds to the NR standard specification configuration, and the other value corresponds to the enhanced configuration as in this disclosure).

[0254] In one example, at least one of the configurations in which the PDSCH mapping type is "Type A", the starting symbol S is "3", and the dmrs-TypeA-Position is "3" can be replaced with an enhanced configuration of PDSCH resource allocation for RMSI as described in the present disclosure, because the number of supported symbols for CORESET#0 is only 1 or 2 in the unlicensed band, which limits the application scenarios with these configurations. For example, at least one of these configurations includes (row index, dmrs-TypeA-Position) of at least one of (1, 3), (2, 3), (3, 3), (4, 3), or (5, 3).

[0255] In one example, the starting symbol (e.g., S) of the PDSCH of at least one of these configurations can be pre-shifted by Δ symbols, and the length (e.g., L) of the PDSCH of at least one of these configurations remains the same, where Δ can be one of 1, 2, or 3. For example, the resulting change in the default PDSCH time domain resource allocation A for normal CP is as in Table 11-1 (only the changed portion is shown, and it is possible to select downward from the table), where Δ can be one of 1, 2, or 3 for operation with shared spectrum channel access, and 0 for operation without shared spectrum channel access.

[0256] In another example, the resulting change can be described as an additional restriction on the default PDSCH time domain resource allocation A for normal CP without changing the contents of the table, where the restriction is "For operation with shared spectrum channel access, when the PDSCH mapping type is provided as "Type A", the starting symbol S is provided as "3", and the dmrs-TypeA-Position is provided as "3", the starting symbol of PDSCH is determined to be 3-Δ", where Δ can be one of 1, 2, or 3. In further consideration of this aspect, Δ can be selected for each configuration independently of {1, 2, 3}. Table 11-1 shows an example change to the NR standard specification default PDSCH time domain resource allocation A for normal CP.

[0257] [Table 11-1]

[0258] Row Index dmrs-TypeA-Position PDSCH mapping type K_0 S L 1 3 Type A 0 3-Δ 11 2 3 Type A 0 3-Δ 9 3 3 Type A 0 3-Δ 8 4 3 Type A 0 3-Δ 6 5 3 Type A 0 3-Δ 4

[0259] In another example, the starting symbol (e.g., S) of the PDSCH of at least one of these configurations can be pre-shifted by Δ symbols, and the length (e.g., L) of the PDSCH of at least one of these configurations is expanded by Δ symbols, where Δ can be one of 1, 2, or 3. For example, the resulting change in the default PDSCH time domain resource allocation A for normal CP is as shown in Table 11-2 (only the changed portion is shown, and it is possible to select downward from the table), where Δ can be one of 1, 2, or 3 for operation with shared spectrum channel access, and 0 for operation without shared spectrum channel access.

[0260] In one example, the resulting change can be described as an additional restriction on the default PDSCH time domain resource allocation A for normal CP without changing the contents of the table, where the restriction is "For operation with shared spectrum channel access, when the PDSCH mapping type is provided as "Type A", the starting symbol S is provided as "3", and the dmrs-TypeA-Position is provided as "3", the starting symbol of the PDSCH is determined to be 3-Δ, and the length of the PDSCH is determined to be L+Δ", where Δ can be one of 1, 2, or 3. In a further consideration of this aspect, Δ can be selected for each configuration independently of {1, 2, 3}. Table 11-2 shows an example change to the NR standard specification default PDSCH time domain resource allocation A for normal CP.

[0261] [Table 11-2]

[0262] Row Index dmrs-TypeA-Position PDSCH mapping type K_0 S L 1 3 Type A 0 3-Δ 11+Δ 2 3 Type A 0 3-Δ 9+Δ 3 3 Type A 0 3-Δ 8+Δ 4 3 Type A 0 3-Δ 6+Δ 5 3 Type A 0 3-Δ 4+Δ

[0263] In another example, at least one of the configurations with a PDSCH mapping type of "Type B" and a PDSCH length L of "2" can be replaced or partially replaced with an enhanced configuration for PDSCH resource allocation for RMSI (e.g., by separating the configuration with a dmrs-TypeA-Position of "2" or "3"), as described in this disclosure (e.g., the example in Table 7-1). Because the location of the PDSCH conflicts with the SS / PBCH block, the application scenarios with these configurations are limited. For example, at least one of these configurations includes (row index, dmrs-TypeA-Position) of at least one of (9, 2, or 3), (10, 2, or 3), or (11, 2, or 3). For one example, when a UE is configured with a row index of 9 and a dmrs-TypeA-Position of 2 or 3, if the operation is without shared spectrum channel access, the UE determines the set of {S, L} to be {5, 2}; if the operation is with shared spectrum channel access, the UE determines the set of {S, L} to be {6, 7}. exist Figure 14B An example UE procedure for determining PDSCH time domain resource allocation for this example is shown in FIG.

[0264] For another example, when the UE is configured with a row index of 9 and a dmrs-TypeA-Position of 2 or 3, if the operation is without shared spectrum channel access, the UE determines the set of {S, L} to be {5, 2}; if the operation is with shared spectrum channel access, the UE determines the set of {S, L} to be {7, 7}. Figure 14B An example UE procedure for determining PDSCH time domain resource allocation for this example is shown in FIG.

[0265] For another example, when the UE is configured with a row index of 10 and a dmrs-TypeA-Position of 2 or 3, if the operation does not have shared spectrum channel access, the UE determines the set of {S, L} to be {9, 2}; if the operation has shared spectrum channel access, the UE determines the set of {S, L} to be {6, 7}. Figure 14B An example UE procedure for determining PDSCH time domain resource allocation for this example is shown in FIG.

[0266] For another example, when the UE is configured with a row index of 10 and a dmrs-TypeA-Position of 2 or 3, if the operation does not have shared spectrum channel access, the UE determines the set of {S, L} to be {9, 2}; if the operation has shared spectrum channel access, the UE determines the set of {S, L} to be {7, 7}. Figure 14B An example UE procedure for determining PDSCH time domain resource allocation for this example is shown in FIG.

[0267] For another example, when the UE is configured with a row index of 11 and a dmrs-TypeA-Position of 2 or 3, if the operation does not have shared spectrum channel access, the UE determines the set of {S, L} to be {12, 2}; if the operation has shared spectrum channel access, the UE determines the set of {S, L} to be {6, 7}. Figure 14B An example UE procedure for determining PDSCH time domain resource allocation for this example is shown in FIG.

[0268] For another example, when the UE is configured with a row index of 11 and a dmrs-TypeA-Position of 2 or 3, if the operation does not have shared spectrum channel access, the UE determines the set of {S, L} to be {12, 2}; if the operation has shared spectrum channel access, the UE determines the set of {S, L} to be {7, 7}. Figure 14B An example UE procedure for determining PDSCH time domain resource allocation for this example is shown in FIG.

[0269] In one example, the starting symbol (e.g., S) of the PDSCH of at least one of these configurations can be pre-shifted by Δ symbols, and the length (e.g., L) of the PDSCH of at least one of these configurations remains the same, where Δ can be one of 1, 2, or 3. For example, the resulting change in the default PDSCH time domain resource allocation A for normal CP is as in Table 11-3 (only the changed portion is shown, and it is possible to select downward from the table), where Δ can be one of 1, 2, or 3 for operation with shared spectrum channel access, and 0 for operation without shared spectrum channel access.

[0270] In one example, the resulting change can be described as an additional restriction on the default PDSCH time domain resource allocation A for normal CP without changing the contents of the table, where the restriction is "For operation with shared spectrum channel access, when the PDSCH mapping type is provided as "Type B" and the length L of the PDSCH is provided as "2", the starting symbol of the PDSCH is determined to be S-Δ", where Δ can be one of 1, 2, or 3. In a further consideration of this aspect, Δ can be selected for each configuration independently of {1,2,3}. Table 11-3 shows an example change to the NR standard specification default PDSCH time domain resource allocation A for normal CP.

[0271] [Table 11-3]

[0272] Row Index dmrs-TypeA-Position PDSCH mapping type K_0 S L 9 2、3 Type B 0 5-Δ 2 10 2、3 Type B 0 9-Δ 2 11 2、3 Type B 0 12-Δ 2

[0273] In another aspect of this example, for one of the configuration values ​​of dmrs-TypeA-Position (e.g., "2" or "3"), the starting symbol (e.g., S) of the PDSCH of at least one of these configurations can be pre-shifted by Δ symbols, and the length (e.g., L) of the PDSCH of at least one of these configurations remains unchanged, where Δ can be one of 1, 2, or 3; and for another of the configuration values ​​of dmrs-TypeA-Position, the starting symbol and length of the PDSCH remain unchanged. For example, the resulting changes in the default PDSCH time domain resource allocation A for normal CP are as shown in Tables 11-1 to 11-4 (only the changed portion is shown, and it can be selected downward from the table), where Δ can be one of 1, 2, or 3 for operation with shared spectrum channel access, and 0 for operation without non-shared spectrum channel access.

[0274] In another example, the resulting change can be described as an additional restriction on the default PDSCH time domain resource allocation A for normal CP without changing the contents of the table, where the restriction is "For operation with shared spectrum channel access, when the PDSCH mapping type is provided as "Type B", dmrs-TypeA-Position is provided as "3" (or "2"), and the length L of the PDSCH is provided as "2", the starting symbol of the PDSCH is determined to be S-Δ", where Δ can be one of 1, 2, or 3. In a further consideration of this aspect, Δ can be selected from {1, 2, 3} independently for each configuration. Table 11-4 shows an example change to the NR standard specification default PDSCH time domain resource allocation A for normal CP.

[0275] [Table 11-4]

[0276]

[0277] In another example, at least one of the configurations in which the PDSCH mapping type is "Type B" and the length L of the PDSCH is "4" can be replaced or partially replaced with an enhanced configuration of PDSCH resource allocation for RMSI (for example, by separating the configuration in which dmrs-TypeA-Position is "2" or "3"), as described in the present disclosure, because the position of the PDSCH conflicts with the SS / PBCH block, which limits the application scenarios with these configurations.

[0278] In another example, at least one of the configurations in which the PDSCH mapping type is "Type B" and the PDSCH length L is "7" can be replaced or partially replaced with an enhanced configuration of PDSCH resource allocation for RMSI (for example, by separating the configuration in which dmrs-TypeA-Position is "2" or "3"), as described in the present disclosure, because the position of the PDSCH conflicts with the SS / PBCH block, the application scenarios with these configurations are limited. For example, at least one of these configurations includes (row index, dmrs-TypeA-Position) being at least one of (8, 2, or 3) or (15, 2, or 3).

[0279] In one example, the starting symbol (e.g., S) of the PDSCH of at least one of these configurations can be shifted by Δ symbols to a later time instant, and the length (e.g., L) of the PDSCH of at least one of these configurations remains unchanged, where Δ is 2. For example, the resulting change in the default PDSCH time domain resource allocation A for normal CP is as in Table 11-5 (only the changed portion is shown, and it can be selected downward from the table), where Δ is 2 for operation with shared spectrum channel access and 0 for operation without shared spectrum channel access.

[0280] In another example, the resulting change can be described as an additional restriction on the default PDSCH time domain resource allocation A for a normal CP without changing the contents of the table, where the restriction is "For operation with shared spectrum channel access, when the PDSCH mapping type is provided as "Type B" and the length L of the PDSCH is provided as "7", the starting symbol of the PDSCH is determined to be S+2, where S is provided in the table." Table 11-5 shows an example change to the NR standard specification default PDSCH time domain resource allocation A for a normal CP.

[0281] [Table 11-5]

[0282] Row Index dmrs-TypeA-Position PDSCH mapping type K_0 S L 8 2、3 Type B 0 5+Δ 7 15 2、3 Type B 0 4+Δ 7

[0283] In another example, for one of the configuration values ​​of dmrs-TypeA-Position (e.g., "2" or "3"), the starting symbol (e.g., S) of the PDSCH of at least one of these configurations can be shifted to a later time by Δ symbols, and the length (e.g., L) of the PDSCH of at least one of these configurations remains unchanged, where Δ may be 2; while for another of the configuration values ​​of dmrs-TypeA-Position, the starting symbol and length of the PDSCH remain unchanged. For example, the resulting change in the default PDSCH time domain resource allocation A for a normal CP is as shown in Table 11-6 (only the changed portion is shown, and it can be selected downward from the table), where Δ is 2 for operation with shared spectrum channel access and 0 for operation without shared spectrum channel access.

[0284] In another example, the resulting change can be described as an additional restriction on the default PDSCH time domain resource allocation A for normal CP without changing the contents of the table, where the restriction is "When the PDSCH mapping type is provided as "Type B", dmrs-TypeA-Position is provided as "3" (or "2"), and the length L of the PDSCH is provided as "7", the starting symbol of the PDSCH is determined to be S+2, where S is provided in the table." Table 11-6 shows an example change to the NR standard specification default PDSCH time domain resource allocation A for normal CP.

[0285] [Table 11-6]

[0286]

[0287] exist Figure 14A An example UE process for determining PDSCH time domain resource allocation according to examples in this disclosure is shown in FIG.

[0288] Figure 14A shows how a user equipment (UE) (e.g., Figure 1 111-116) shown is a flowchart of a method 1400 for determining PDSCH time domain resource allocation according to an embodiment of the present disclosure. Figure 14A The illustrated embodiment of method 1400 is for illustration only. Figure 14A It does not limit the scope of the present disclosure.

[0289] like Figure 14AAs shown, in step 1402 the UE determines the row index of the configuration table. In step 1404, the UE determines the values ​​of S and L, respectively. In step 1406, the UE determines whether the operation with shared spectrum channel access is completed. In step 1406, the operation is completed, and the UE determines the offset values ​​for S and / or L, respectively, in step 1408. The UE determines the starting symbol of the PDSCH as the sum of S and the offset to S (if the offset is applicable from the previous step, otherwise the offset is considered to be 0) in step 1412, and determines the length of the PDSCH as the sum of L and the offset to L (if the offset is applicable from the previous step, otherwise the offset is considered to be 0). In step 1406, if the operation with shared spectrum channel access is not completed, the UE determines the starting symbol of the PDSCH as S and the length of the PDSCH as L in step 1410.

[0290] exist Figure 14B Another example UE process for determining PDSCH time domain resource allocation according to examples in this disclosure is shown in FIG.

[0291] Figure 14B shows how a user equipment (UE) (e.g., Figure 1 111-116) shown is another flow chart of a method 1450 for determining PDSCH time domain resource allocation according to an embodiment of the present disclosure. Figure 14B The illustrated embodiment of method 1450 is for illustration only. Figure 14B It does not limit the scope of the present disclosure.

[0292] like Figure 14B As shown, method 1450 begins at step 1452. At step 1452, method 1450 determines a row index of a configuration table. Subsequently, at step 1454, method 1450 determines whether to perform operations with shared spectrum channel access. At step 1454, if operations with shared spectrum channel access are to be performed, method 1450 determines a first set of S and L at step 1456. At step 1454, if operations with shared spectrum channel access are not to be performed, method 1450 determines a second set of S and L at step 1458.

[0293] Figure 15 shows how a user equipment (UE) (e.g., Figure 1 111-116) shown is a flowchart of a method 1500 for resource mapping for PDSCH according to an embodiment of the present disclosure. Figure 15 The illustrated embodiment of method 1500 is for illustration only. Figure 15 It does not limit the scope of the present disclosure.

[0294] like Figure 15As shown, method 1500 begins at step 1502. In step 1502, a UE receives a set of downlink channels supporting shared spectrum channel access from a base station (BS).

[0295] Subsequently, in step 1504, the UE identifies the window for synchronization signal / physical broadcast channel (SS / PBCH) block transmission, the bit map for SS / PBCH blocks (ssb-PositionsInBurst), and the parameter Q for quasi co-location (QCL) assumption from the downlink channel set.

[0296] Subsequently, in step 1506, the UE determines the SS / PBCH blocks in the identified window for SS / PBCH block transmission as one of the following: a first SS / PBCH block set assumed to be sent by the BS, or a second SS / PBCH block set not sent by the BS based on the identified window for SS / PBCH block transmission, the identified bitmap for ssb-PositionsInBurst, and the identified parameter Q for QCL assumption.

[0297] In one embodiment, the SS / PBCH blocks in the window for SS / PBCH block transmission, having indices given by i+n·Q, where 0≤i≤Q-1 and n is a non-negative integer, are determined to be one of: in the first SS / PBCH block set if the (i+1)th bit in ssb-PositionsInBurst is identified as one; or in the second SS / PBCH block set if the (i+1)th bit in ssb-PositionsInBurst is identified as zero.

[0298] Next, in step 1508, the UE determines a set of resources unavailable for at least one physical downlink shared channel (PDSCH) as overlapping with the first SS / PBCH block set.

[0299] In one embodiment, at least one PDSCH does not carry Remaining Minimum System Information (RMSI).

[0300] Finally, in step 1510, the UE receives at least one PDSCH from the BS based on resources other than the determined resource set.

[0301] In one embodiment, if i≥Q, the UE identifies the (i+1)th bit in ssb-PositionsInBurst as a zero value.

[0302] In one embodiment, the UE determines the number of SS / PBCH blocks transmitted in the identified window for SS / PBCH block transmission as the number of bits having a value of one in ssb-PositionsInBurst.

[0303] In one embodiment, the UE determines a default time-domain resource allocation including a start symbol S and a length L of the symbol of at least one PDSCH. In this embodiment, if the at least one PDSCH is operated due to shared spectrum channel access, the start symbol S and the length L of the symbol include a first value set determined as {S, L}={6, 7}, and if the at least one PDSCH is operated without shared spectrum channel access, the start symbol S and the length L of the symbol include a second value set determined as {S, L}={5, 2}.

[0304] According to one embodiment of the present disclosure, a method for operating a terminal in a wireless communication system is provided, the method comprising: receiving a radio resource control (RRC) message associated with a transmission position of a synchronization signal / physical broadcast channel (SS / PBCH) block in a time domain from a base station, the RRC message including information about a bitmap; identifying an index of at least one SS / PBCH block sent from the base station within a window for receiving the SS / PBCH block based on each bit value included in the bitmap; and receiving at least one SS / PBCH block at a position corresponding to the identified index from the base station.

[0305] In an embodiment, a window for receiving SS / PBCH blocks may include candidate SS / PBCH blocks, and at least one SS / PBCH block may be selected from the candidate SS / PBCH blocks.

[0306] In an embodiment, identifying the index of at least one SS / PBCH block may include: when a value of a first bit included in the bitmap is 1, determining that the SS / PBCH block having the index corresponding to the first bit is transmitted from the base station; and when a value of a second bit included in the bitmap is 0, determining that the SS / PBCH block having the index corresponding to the second bit is not transmitted from the base station.

[0307] In an embodiment, identifying the index of at least one SS / PBCH block may also include: determining the index of the SS / PBCH block sent from the base station among the candidate SS / PBCH blocks included in the window for receiving the SS / PBCH block based on the wrapping modulus value associated with the bits included in the bitmap and the index corresponding to the first bit.

[0308] In an embodiment, identifying the index of at least one SS / PBCH block may also include: determining the index of the SS / PBCH block that is not transmitted from the base station among the candidate SS / PBCH blocks included in the window for receiving the SS / PBCH block based on the wrapping modulus value associated with the quasi-co-location of the bits included in the bitmap and the index corresponding to the second bit.

[0309] In an embodiment, the number of at least one SS / PBCH block transmitted from the base station within a window for receiving the SS / PBCH block may be equal to or smaller than the number of bit sets included in the bitmap.

[0310] In an embodiment, the method may further include: determining a start symbol and a length of a symbol for allocating time domain resources to a physical downlink shared channel (PDSCH) based on whether the PDSCH uses a shared spectrum channel access operation.

[0311] In an embodiment, determining the starting symbol and the length of the symbol may include: when PDSCH uses shared spectrum channel access operation, determining the value of the starting symbol to be equal to 6 and determining the length of the symbol to be equal to 7, and the starting symbol and the length of the symbol correspond to the same row index.

[0312] According to another embodiment of the present disclosure, a terminal in a wireless communication system is provided. The terminal includes a transceiver and at least one processor, the at least one processor being configured to: control the transceiver to receive a radio resource control (RRC) message associated with a transmission position of a synchronization signal / physical broadcast channel (SS / PBCH) block in the time domain from a base station, the RRC message including information about a bitmap; identify an index of at least one SS / PBCH block sent from the base station within a window for receiving the SS / PBCH block based on each bit value included in the bitmap; and receive at least one SS / PBCH block at a position corresponding to the identified index from the base station.

[0313] In another embodiment, the window for receiving the SS / PBCH block includes candidate SS / PBCH blocks, at least one SS / PBCH block is selected from the candidate SS / PBCH blocks, and the number of the at least one SS / PBCH block transmitted from the base station within the window for receiving the SS / PBCH block is equal to or less than the number of bit sets included in the bitmap.

[0314] In another embodiment, at least one processor may also be configured to: when the value of the first bit included in the bitmap is 1, determine that the SS / PBCH block with the index corresponding to the first bit is sent from the base station; and when the value of the second bit included in the bitmap is 0, determine that the SS / PBCH block with the index corresponding to the second bit is not sent from the base station.

[0315] In another embodiment, at least one processor may be further configured to determine an index of an SS / PBCH block transmitted from the base station among candidate SS / PBCH blocks included in a window for receiving the SS / PBCH block based on a wrap modulus value associated with the quasi co-location of bits included in the bitmap and an index corresponding to the first bit.

[0316] In another embodiment, at least one processor may also be configured to determine an index of an SS / PBCH block that is not transmitted from the base station among the candidate SS / PBCH blocks included in the window for receiving the SS / PBCH block based on a wrap modulus value associated with a bit included in the bitmap and an index corresponding to the second bit.

[0317] In another embodiment, the at least one processor may be further configured to determine a starting symbol and a length of a symbol for allocating time domain resources for a physical downlink shared channel (PDSCH) based on whether the PDSCH uses a shared spectrum channel access operation.

[0318] In another embodiment, at least one processor may be further configured to determine the value of the starting symbol to be equal to 6 and the length of the symbol to be equal to 7 when the PDSCH uses a shared spectrum channel access operation, the starting symbol and the length of the symbol corresponding to the same row index.

[0319] The methods according to the embodiments of the present disclosure described in the claims or specification of the present disclosure can be implemented by hardware, software, or a combination of hardware and software.

[0320] When implemented using software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs may include instructions for causing the electronic device to execute the method according to the embodiments described in the claims or specification of the present disclosure.

[0321] The program (software module, software) may be stored in random access memory (RAM), non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable ROM (EEPROM), magnetic disk storage, compact disk (CD)-ROM, digital versatile disk (DVD) or other types of optical storage devices and / or magnetic cartridges. Alternatively, the program may be stored in a memory comprising a combination of some or all of these. The memory may be provided in plurality.

[0322] The program may also be stored in an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), or a storage area network (SAN), or a combination thereof. The storage device may be connected to an apparatus for executing embodiments of the present disclosure via an external port. Alternatively, a separate storage device in the communication network may be connected to an apparatus for executing embodiments of the present disclosure.

[0323] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.

[0324] Nothing in the description in this application should be read as implying that any particular element, step, or function is essential to be included in the claims scope. The scope of the patented subject matter is defined solely by the claims.

Claims

1. A method, performed by a terminal in a wireless communication system, for operating using shared spectrum channel access, the method comprising: receiving a radio resource control (RRC) message from a base station, the RRC message including an indication of a position of a candidate synchronization signal / physical broadcast channel (SS / PBCH) block in a time domain, wherein the indication of the position of the candidate SS / PBCH block includes information about a bitmap of the candidate SS / PBCH block; identifying an index of at least one SS / PBCH block within a transmission window for the SS / PBCH block based on the bitmap of the candidate SS / PBCH blocks and parameters for a quasi-co-located QCL assumption between SS / PBCH blocks; and Determine the starting symbol and symbol length in the time domain resources for the physical downlink shared channel PDSCH, In which, when the PDSCH is operated using shared spectrum channel access, determining the starting symbol and the length of the symbol includes: when the row index of the PDSCH time domain resource allocation table is 9 and the dmrs-TypeA-Position is 2 or 3, determining that the value of the starting symbol is equal to 6 and the length of the symbol is equal to 7.

2. The method according to claim 1, in, The parameters used for the QCL assumption are obtained based on PBCH or Remaining Minimum System Information (RMSI).

3. The method according to claim 1, wherein The index identifying the at least one SS / PBCH block includes: In a case where a value of a bit included in the bitmap is 1, determining that an SS / PBCH block having an index corresponding to the bit is assumed to be transmitted from the base station; and In case that a value of the bit included in the bitmap is 0, it is determined that the SS / PBCH block having the index corresponding to the bit is assumed not to be transmitted from the base station.

4. The method according to claim 3, wherein: Identifying the index of the at least one SS / PBCH block further includes: In a case where the value of the i+1th bit in the bitmap is 1, it is assumed that an SS / PBCH block with an i+n*Q index among the candidate SS / PBCH blocks within the transmission window for the SS / PBCH block is to be transmitted from the base station, where 0≤i≤Q-1, Q is a parameter for the QCL assumption, and n is a non-negative integer.

5. The method according to claim 3, wherein Identifying the index of the at least one SS / PBCH block further includes: In a case where the value of the i+1th bit in the bitmap is 0, it is assumed that the SS / PBCH block with the i+n*Q index among the candidate SS / PBCH blocks within the transmission window for the SS / PBCH block is not transmitted from the base station, where 0≤i≤Q-1, Q is a parameter for the QCL assumption, and n is a non-negative integer.

6. The method according to claim 1, wherein The number of the at least one SS / PBCH block within a transmission window for the SS / PBCH block is equal to or less than the parameter for QCL assumption.

7. The method according to claim 1, wherein The identified index is determined based on the first Q bits of the bitmap, where Q is a parameter for the QCL assumption.

8. The method according to claim 1, comprising: determining a first SS / PBCH block set assumed to be transmitted by the base station; determining a second SS / PBCH block set that is assumed not to be transmitted by the base station; as well as A resource set unavailable for at least one PDSCH is determined to overlap with the first SS / PBCH block set.

9. A terminal for operating using shared spectrum channel access in a wireless communication system, the terminal comprising: transceiver; as well as at least one processor configured to: controlling the transceiver to receive a radio resource control (RRC) message from a base station, the RRC message including an indication of a position of a candidate synchronization signal / physical broadcast channel (SS / PBCH) block in a time domain, wherein the indication of the position of the candidate SS / PBCH block includes information about a bitmap of the candidate SS / PBCH block, identifying an index of at least one SS / PBCH block within a transmission window for the SS / PBCH block based on the bitmap of the candidate SS / PBCH blocks and parameters for quasi-co-location QCL assumption between SS / PBCH blocks, and Determine the starting symbol and symbol length in the time domain resources for the physical downlink shared channel PDSCH, In which, when the PDSCH is operated using shared spectrum channel access, determining the starting symbol and the length of the symbol includes: when the row index of the PDSCH time domain resource allocation table is 9 and the dmrs-TypeA-Position is 2 or 3, determining that the value of the starting symbol is equal to 6 and the length of the symbol is equal to 7.

10. The terminal according to claim 9, in, The number of the at least one SS / PBCH block within a transmission window for the SS / PBCH block is equal to or less than the parameter for QCL assumption.

11. The terminal according to claim 9, wherein The at least one processor is further configured to: In case a value of a bit included in the bitmap is 1, determining that an SS / PBCH block having an index corresponding to the bit is assumed to be transmitted from the base station, and In case that a value of the bit included in the bitmap is 0, it is determined that the SS / PBCH block having the index corresponding to the bit is assumed not to be transmitted from the base station.

12. The terminal according to claim 11, wherein: The at least one processor is further configured to: In a case where the value of the i+1th bit in the bitmap is 1, it is assumed that an SS / PBCH block with an i+n*Q index among the candidate SS / PBCH blocks within the transmission window for the SS / PBCH block is to be transmitted from the base station, where 0≤i≤Q-1, Q is a parameter for the QCL assumption, and n is a non-negative integer. The terminal according to claim 11 , wherein: The at least one processor is further configured to: In a case where the value of the i+1th bit in the bitmap is 0, it is assumed that the SS / PBCH block with the i+n*Q index among the candidate SS / PBCH blocks within the transmission window for the SS / PBCH block is not transmitted from the base station, where 0≤i≤Q-1, Q is a parameter for the QCL assumption, and n is a non-negative integer. The terminal according to claim 9 , wherein: The identified index is determined based on the first Q bits of the bitmap, where Q is a parameter for the QCL assumption. The terminal according to claim 9 , wherein: The at least one processor is further configured to: determining a first SS / PBCH block set assumed to be transmitted by the base station; determining a second set of SS / PBCH blocks that are assumed not to be transmitted by the base station; and A resource set unavailable for at least one PDSCH is determined to overlap with the first SS / PBCH block set.

Images