阅读说明：本技术 无线系统中同步信号块索引和定时指示的方法和装置 (Method and apparatus for synchronization signal block index and timing indication in a wireless system ) 是由 陈浩 南映瀚 何超 维克拉姆·钱德拉塞卡 司洪波 黄文隆 于 2018-05-04 设计创作，主要内容包括：本公开涉及将被提供用于支持诸如长期演进(LTE)的超第四代(4G)通信系统的更高数据速率的Pre-5G(5Generation)或5G通信系统。提供了在无线通信系统中用于同步信号(SS)块索引和定时指示的设备和方法。用户设备(UE)包括：收发器,其被配置为从基站(BS)接收多个高层配置信息集；以及可操作地耦接到收发器的至少一个处理器。至少一个处理器被配置为,如果对SS和物理广播信道(PBCH)(SS/PBCH)块执行移动性测量,则基于多个高层配置信息集中的一个来确定针对移动性测量而配置的第一SS/PBCH块集；然后通过使用第一SS/PBCH块集来测量并报告移动性测量量。至少一个处理器被配置为：如果接收到物理下行链路共享信道(PDSCH),则基于所述多个高层配置信息集中的另一个,确定针对所述UE配置的第二SS/PBCH块集；以及经由所述收发器,接收在第二SS/PBCH块集中包括的SS/PBCH块附近速率匹配了的PDSCH。(The present disclosure relates to a Pre-5G (5Generation) or 5G communication system to be provided for supporting higher data rates of a super fourth Generation (4G) communication system such as Long Term Evolution (LTE). An apparatus and method for Synchronization Signal (SS) block index and timing indication in a wireless communication system are provided. A User Equipment (UE) includes: a transceiver configured to receive a plurality of higher layer configuration information sets from a Base Station (BS); and at least one processor operatively coupled to the transceiver. The at least one processor is configured to determine a first set of Physical Broadcast Channel (PBCH) (SS/PBCH) blocks configured for mobility measurements based on one of a plurality of higher layer configuration information sets if the mobility measurements are performed on SS and PBCH blocks; mobility measurements are then measured and reported by using the first set of SS/PBCH blocks. The at least one processor is configured to: determining a second set of SS/PBCH blocks configured for the UE based on another one of the plurality of higher layer configuration information sets if a Physical Downlink Shared Channel (PDSCH) is received; and receiving, via the transceiver, the rate-matched PDSCH in the vicinity of the SS/PBCH blocks included in the second set of SS/PBCH blocks.)

1. A User Equipment (UE), comprising:

a transceiver configured to receive a plurality of higher layer configuration information sets from a Base Station (BS);

at least one processor operably coupled to the transceiver and configured to:

if mobility measurements are performed on Synchronization Signal (SS) and Physical Broadcast Channel (PBCH) (SS/PBCH) blocks, then:

determining a first set of SS/PBCH blocks configured for the mobility measurements based on one of the plurality of higher layer configuration information sets; and

measuring and reporting mobility measurement quantities by using the first set of SS/PBCH blocks; and is

If a Physical Downlink Shared Channel (PDSCH) is received:

determining a second set of SS/PBCH blocks configured for the UE based on another one of the plurality of higher layer configuration information sets; and

receiving, via the transceiver, a PDSCH rate-matched near a SS/PBCH block in the second set of SS/PBCH blocks.

2. The UE of claim 1, wherein, if the mobility measurement is performed, the at least one processor is further configured to:

monitoring SS/PBCH block measurement timing configuration (SMTC) duration, and

measuring and reporting, via the transceiver, the mobility measurement quantity for the first set of SS/PBCH blocks that overlap the SMTC duration.

3. The UE of claim 1, wherein the mobility measurement quantity comprises an SS reference signal received power (SS-RSRP) for a subset of the first set of SS/PBCH blocks.

4. The UE of claim 1, wherein the mobility measurement quantity comprises an SS reference signal received quality (SS-RSRQ) for a subset of the first set of SS/PBCH blocks.

5. The UE of claim 1, wherein, if the PDSCH is received, the at least one processor is further configured to perform rate matching of the PDSCH at data resource block (PRB) boundaries near a set of consecutive Physical Resource Blocks (PRBs) that at least partially overlap with SS/PBCH blocks in Orthogonal Frequency Division Multiplexing (OFDM) symbols containing the SS/PBCH blocks.

6. The UE of claim 1, wherein, if the PDSCH is received, the at least one processor is further configured to perform rate matching of the PDSCH around an entire bandwidth part (BWP) bandwidth in an Orthogonal Frequency Division Multiplexing (OFDM) symbol containing the SS/PBCH block.

7. The UE of claim 1, wherein the SS/PBCH block periods are configured separately for PDSCH rate matching and mobility measurement purposes.

8. A Base Station (BS), comprising:

at least one processor configured to generate a plurality of higher layer configuration information sets for a User Equipment (UE); and

a transceiver operatively coupled to the at least one processor and configured to transmit the plurality of higher layer configuration information sets to the UE and receive reports from the UE based on the plurality of higher layer configuration information sets, wherein:

if the UE is configured to perform mobility measurements on Synchronization Signal (SS) and Physical Broadcast Channel (PBCH) (SS/PBCH) blocks, the at least one processor is further configured to generate one of the plurality of higher layer configuration information sets to indicate a first set of SS/PBCH blocks configured for the mobility measurements for reporting an amount of mobility measurements for the first set of SS/PBCH blocks; and

the at least one processor is further configured to, if the UE is configured to receive a Physical Downlink Shared Channel (PDSCH):

generating another one of the plurality of higher layer configuration information sets to indicate a second set of SS/PBCH blocks configured for the UE; and

transmitting, via the transceiver, the PDSCH rate-matched near the SS/PBCH block in the second set of SS/PBCH blocks.

9. The BS of claim 8, wherein the mobility measurement quantity comprises SS reference signal received power (SS-RSRP) for a subset of the first set of SS/PBCH blocks.

10. The BS of claim 8, wherein the mobility measurement quantity comprises an SS reference signal received quality (SS-RSRQ) for a subset of the first set of SS/PBCH blocks.

11. The BS of claim 8, wherein the at least one processor is further configured to configure the UE to perform rate matching of the PDSCH at data PRB boundaries near a set of consecutive Physical Resource Blocks (PRBs) that at least partially overlap with SS/PBCH blocks in Orthogonal Frequency Division Multiplexing (OFDM) symbols containing the SS/PBCH blocks.

12. The BS of claim 8, wherein the at least one processor is further configured to: configuring the UE to perform rate matching of the PDSCH around an entire bandwidth part (BWP) bandwidth in an Orthogonal Frequency Division Multiplexing (OFDM) symbol containing the SS/PBCH block.

13. The BS of claim 8, wherein SS/PBCH block periodicity is configured separately for PDSCH rate matching and mobility measurement purposes.

14. A method of operating a User Equipment (UE), the method comprising:

receiving a plurality of higher layer configuration information sets from a Base Station (BS);

if mobility measurements are performed on Synchronization Signal (SS) and Physical Broadcast Channel (PBCH) (SS/PBCH) blocks, then:

determining a first set of SS/PBCH blocks configured for the mobility measurements based on one of the plurality of higher layer configuration information sets; and

measuring and reporting mobility measurement quantities by using the first set of SS/PBCH blocks; and is

If a Physical Downlink Shared Channel (PDSCH) is received:

determining a second set of SS/PBCH blocks configured for the UE based on another one of the plurality of higher layer configuration information sets; and

receiving the PDSCH rate-matched near a SS/PBCH block in the second set of SS/PBCH blocks.

15. The method of claim 14, wherein the measuring and reporting mobility measurement quantities comprises:

monitoring a SS/PBCH block measurement timing configuration (SMTC) duration; and

measuring and reporting the mobility measurement quantity of the first set of SS/PBCH blocks that overlap the SMTC duration.

Technical Field

The present application relates generally to wireless communication systems. More particularly, the present disclosure relates to Synchronization Signal (SS) block index and timing indication in a wireless communication system.

Background

In order to meet the increasing demand for wireless data services since the deployment of 4G communication systems, efforts are made to develop improved 5G or pre-5G communication systems. Accordingly, the 5G or pre-5G communication system is also referred to as an "ultra 4G network" or a "post-LTE system".

The 5G communication system is considered to be implemented in a higher frequency (millimeter wave) band (for example, 60GHz band) to achieve a higher data rate. In order to reduce propagation loss of radio waves and increase transmission distance, beamforming, massive Multiple Input Multiple Output (MIMO), full-dimensional MIMO (FD-MIMO), array antenna, analog beamforming, massive antenna techniques are discussed in the 5G communication system.

In addition, in the 5G communication system, development for system network improvement is underway based on advanced small cells, cloud Radio Access Network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multipoint (CoMP), reception-side interference cancellation, and the like.

In 5G systems, hybrid FSK and QAM modulation (FQAM) and Sliding Window Superposition Coding (SWSC) have been developed as Advanced Coding Modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and Sparse Code Multiple Access (SCMA) as advanced access techniques.

In the 5G system, beamforming is performed on a synchronization signal or a broadcast signal. Thus, suitable structures for the synchronization signal and the broadcast signal are discussed.

Disclosure of Invention

Technical problem

Embodiments of the present disclosure provide Synchronization Signal (SS) block index and timing indication in a wireless communication system.

Solution to the problem

In one embodiment, a User Equipment (UE) is provided. The UE includes: a transceiver configured to receive a plurality of higher layer configuration information sets from a Base Station (BS); at least one processor operatively coupled to the transceiver. The at least one processor is configured to determine, based on one of the plurality of higher layer configuration information sets, a first set of Synchronization Signal (SS) and Physical Broadcast Channel (PBCH) (SS/PBCH) blocks configured for mobility measurements if the mobility measurements are performed on the SS and PBCH blocks; and measuring and reporting mobility measurement quantities by using the first set of SS/PBCH blocks. The at least one processor is configured to determine a second set of SS/PBCH blocks configured for the UE based on another one of the plurality of higher layer configuration information sets if a Physical Downlink Shared Channel (PDSCH) is received; and receiving, via the transceiver, a PDSCH rate-matched near a SS/PBCH block in the second set of SS/PBCH blocks.

In another embodiment, a BS is provided. The BS comprises at least one processor configured to generate a plurality of higher layer configuration information sets for a User Equipment (UE); and a transceiver operatively coupled to the at least one processor. The at least one processor is configured to transmit the plurality of higher layer configuration information sets to the UE and receive a report from the UE based on the plurality of higher layer configuration information sets. When the UE is configured to perform mobility measurements on Synchronization Signal (SS) and Physical Broadcast Channel (PBCH) (SS/PBCH) blocks, the at least one processor is configured to generate one of the plurality of higher layer configuration information sets to indicate a first set of SS/PBCH blocks configured for the mobility measurements for reporting a quantity of mobility measurements for the first set of SS/PBCH blocks. When the UE is configured to receive a Physical Downlink Shared Channel (PDSCH), the at least one processor is configured to generate another one of the plurality of higher layer configuration information sets to indicate a second set of SS/PBCH blocks configured for the UE; and transmitting, via the transceiver, the PDSCH rate-matched near SS/PBCH blocks in the second set of SS/PBCH blocks.

In yet another embodiment, a method of operating a UE is provided. The method includes receiving a plurality of higher layer configuration information sets from a BS. If mobility measurements are performed on SS/PBCH blocks, the UE determines a first set of SS/PBCH blocks configured for the mobility measurements based on one of the plurality of higher layer configuration information sets; and measuring and reporting mobility measurement amounts by using the first set of SS/PBCH blocks. If the PDSCH is received, the UE determines a second set of SS/PBCH blocks configured for the UE based on another one of the plurality of higher layer configuration information sets; receiving the PDSCH rate-matched near a SS/PBCH block in the second set of SS/PBCH blocks.

Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," as well as derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation. The term "or" is inclusive, meaning and/or. The phrase "associated with … …," and derivatives thereof, is intended to include, be included within, interconnect with … …, contain, be included within, connect to or connect with … …, couple to or couple with … …, communicate with … …, cooperate with … …, interleave, juxtapose, be proximate to, bound to or bound by … …, have the property of … …, have a relationship with … …, and the like. The term "controller" means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in 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. When the phrase "at least one of … … is used with a list of items, it is meant that different combinations of one or more of the listed items can be used, and only one item in the list may be required. For example, "at least one of A, B and C" includes any of the following combinations: A. b, C, A and B, A and C, B and C and A and B and C.

Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in 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 capable of being accessed by a computer, such as Read Only Memory (ROM), Random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of memory. A "non-transitory" computer-readable medium does not include a wired, wireless, optical, or other communication link that transmits transitory electrical 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 disks or erasable memory devices.

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, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

Advantageous effects of the invention

According to various embodiments of the present disclosure, information on a synchronization signal block index and a timing indication may be more efficiently provided.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which like reference numbers represent like parts:

fig. 1 illustrates an example wireless network in accordance with embodiments of the present disclosure;

fig. 2 illustrates an example eNB in accordance with an embodiment of the disclosure;

fig. 3 illustrates an example UE in accordance with an embodiment of the present disclosure;

fig. 4A illustrates an example high-level diagram of an orthogonal frequency division multiple access transmission path according to an embodiment of the present disclosure;

fig. 4B illustrates an example high-level diagram of an orthogonal frequency division multiple access receive path, according to an embodiment of the disclosure;

fig. 5 illustrates an example network slice in accordance with an embodiment of the present disclosure;

FIG. 6 illustrates an example number of digit chains in accordance with an embodiment of the disclosure;

fig. 7 illustrates an example LTE cell search operation in accordance with an embodiment of the disclosure;

figure 8 shows an example frame structure of PSS/SSS/PBCH transmission in FDD configuration according to embodiments of the present disclosure;

fig. 9A illustrates an example SS burst in an LTE system, according to an embodiment of the disclosure;

fig. 9B illustrates an example SS block/burst/set in accordance with an embodiment of the present disclosure;

fig. 10 shows a flow diagram of a method for beam ID reporting configuration in accordance with an embodiment of the present disclosure;

FIG. 11 shows a flow chart of a method for deriving a measurement quantity according to an embodiment of the present disclosure;

figure 12A illustrates an example PBCH BW, in accordance with embodiments of the disclosure;

figure 12B illustrates an example PSS/SSS OFDM symbol in accordance with embodiments of the disclosure;

fig. 13 illustrates a flow chart of a method for configuring a maximum of a band-specific number of SS blocks according to an embodiment of the present disclosure;

FIG. 14 shows a flow diagram of a method for indicating network-wide and band-specific information;

FIG. 15 illustrates an example mapping slot pattern in accordance with an embodiment of the disclosure;

FIG. 16A illustrates an example measurement gap configuration according to embodiments of the present disclosure;

16B and 16C illustrate configurations for rate matching near an SSB according to embodiments of the present disclosure;

fig. 17A illustrates an example mapped SS block in accordance with an embodiment of the present disclosure;

fig. 17B illustrates another example mapped SS block in accordance with an embodiment of the present disclosure;

fig. 17C illustrates yet another example mapped SS block in accordance with an embodiment of the present disclosure;

fig. 17D illustrates yet another example mapped SS block in accordance with an embodiment of the present disclosure;

fig. 17E illustrates yet another example mapped SS block in accordance with an embodiment of the present disclosure;

fig. 18A illustrates an example SS burst set composition, in accordance with an embodiment of the present disclosure;

fig. 18B illustrates another example SS burst set composition, in accordance with an embodiment of the present disclosure;

fig. 18C illustrates yet another example SS burst set composition, in accordance with an embodiment of the present disclosure;

fig. 19A illustrates yet another example SS burst set composition, in accordance with an embodiment of the present disclosure;

fig. 19B illustrates yet another example SS burst set composition, in accordance with an embodiment of the present disclosure;

fig. 19C illustrates yet another example SS burst set composition, in accordance with an embodiment of the present disclosure;

fig. 20 illustrates example split Beam State Information (BSI) in PUCCH according to an embodiment of the present disclosure;

fig. 21 illustrates example implicit signaling of Tx beam index information according to an embodiment of the present disclosure;

fig. 22 illustrates another example implicit signaling of Tx beam index information according to an embodiment of the present disclosure;

fig. 23 illustrates another example implicit signaling of Tx beam index information according to an embodiment of the present disclosure;

fig. 24 illustrates example implicit signaling of Rx beam set/group number according to embodiments of the present disclosure;

fig. 25 illustrates another example implicit signaling of Rx beam set/group number in accordance with an embodiment of the present disclosure;

fig. 26 illustrates yet another example implicit signaling of Rx beam set/group number in accordance with an embodiment of the present disclosure;

fig. 27 illustrates example implicit signaling of Rx beam set/group number and Tx beam index information, in accordance with an embodiment of the present disclosure;

fig. 28 illustrates another example implicit signaling of Rx beam set/group number and Tx beam index information, in accordance with an embodiment of the present disclosure;

fig. 29 illustrates yet another example implicit signaling of Rx beam set/group number and Tx beam index information according to an embodiment of the present disclosure;

fig. 30 illustrates an example short PUCCH transmission in accordance with an embodiment of the present disclosure;

fig. 31 illustrates an example long PUCCH transmission in accordance with an embodiment of the present disclosure;

figure 32 illustrates an example PUCCH beam indication in accordance with an embodiment of the present disclosure;

fig. 33 illustrates an example DCI triggering aperiodic PUCCH according to an embodiment of the present disclosure;

fig. 34 shows an example DL DCI trigger aperiodic PUCCH according to an embodiment of the present disclosure; and

fig. 35 illustrates an example UL DCI trigger aperiodic PUCCH and PUSCH in accordance with an embodiment of the present disclosure.

Detailed Description

Figures 1 through 35, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

The following documents are incorporated by reference into this disclosure as if fully set forth herein: 3GPP TS 36.211 v13.0.0, "E-UTRA, Physical channels and modulation; "3 GPP TS 36.212 v13.0.0," E-UTRA, Multiplexing and Channel coding; "3 GPP TS 36.213 v13.0.0," E-UTRA, physical layer Procedures; "3 GPP TS 36.214 v14.1.0," Physical Layer Measurement; "3 GPP TS36.321 v13.0.0," E-UTRA, Medium Access Control (MAC) protocol specification; "3 GPP PTS 36.331 v13.0.0", "E-UTRA, Radio Resource Control (RRC) Protocol Specification", "and 3GPP TR 38.802 v1.1.0", "Study on New Radio Access Technology physical layer assessment"

The first commercialization of the fifth generation (5G) mobile communications is expected to proceed in the year 2020, with all recent trends coming from the industry and academiaThe development of 5G mobile communication is more and more in the progress of global technical activities of technology selection. Candidate contributing factors for 5G mobile communications include massive antenna technologies providing beamforming gain and supporting scalability from traditional cellular bands to high frequencies, new waveforms (e.g., new Radio Access Technologies (RATs)) with various different required services/applications, new multiple access schemes supporting massive connections, and so on, that can be flexibly accommodated. The International Telecommunications Union (ITU) has divided the usage scenarios of International Mobile Telecommunications (IMT) in 2020 and beyond into 3 main categories, such as enhanced mobile broadband, large-scale Machine Type Communication (MTC), and ultra-reliable and low-latency communication. In addition, the ITC specifies target requirements, such as a peak data rate of 20 gigabits per second (Gb/s), a user-experienced data rate of 100 megabits per second (Mb/s), a 3-fold increase in spectral efficiency, support of mobility up to 500 kilometers per hour (km/h), a delay of 1 millisecond (ms), and 106 devices/km²The network energy efficiency is improved by 100 times, and the regional flow is 10Mb/s/m². Although not required to meet all requirements simultaneously, the design of a 5G network may provide flexibility on a case basis to support a variety of applications that meet the above requirements.

Fig. 1 through 4B below describe various embodiments implemented in a wireless communication system and utilizing Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. The descriptions of fig. 1-3 are not intended to imply physical or architectural limitations to the manner in which different embodiments may be implemented. The different embodiments of the present disclosure may be implemented in any suitably arranged communication system.

Fig. 1 illustrates an example wireless network in accordance with an embodiment of the present disclosure. The embodiment of the wireless network shown in fig. 1 is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of this disclosure.

As shown in fig. 1, the wireless network includes an eNB101, an eNB102, and an eNB 103. The eNB101 communicates with the eNB102 and the eNB 103. The eNB101 also communicates with at least one network 130, such as the internet, a proprietary Internet Protocol (IP) network, or other data network.

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

Depending on the network type, the term "base station" or "BS" may refer to any component (or collection of components) configured to provide wireless access to the 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 macrocell, a femtocell, a WiFi Access Point (AP), or other wireless enabled device. The base station may provide wireless access in accordance with one or more wireless communication protocols (e.g., 5G 3GPP new radio interface/access (NR), Long Term Evolution (LTE), LTE-advanced (LTE-a), High Speed Packet Access (HSPA), Wi-Fi 802.11a/b/G/n/ac, etc.). For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to a remote terminal. Also, depending on the network type, the term "user equipment" or "UE" may refer to any component such as a "mobile station," subscriber station, "" remote terminal, "" wireless terminal, "" reception point, "or" user equipment. 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 what is commonly considered a stationary device (such as a desktop computer or vending machine).

The dashed lines show an approximate extent of the coverage areas 120 and 125, which coverage areas 120 and 125 are shown as approximately circular areas for purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with an eNB (such as coverage areas 120 and 125) may have other shapes, including irregular shapes, depending on the configuration of the eNB and variations in the wireless environment associated with natural and man-made obstructions.

As described in more detail below, one or more of the UEs 111-116 include circuitry, procedures, or a combination thereof for efficient SS block indexing and timing indication in advanced wireless communication systems. In certain embodiments, one or more of the enbs 101-103 comprise circuitry, programming, or a combination thereof for efficient SS block indexing and timing indication in advanced wireless communication systems.

Although fig. 1 illustrates one example of a wireless network, various changes may be made to fig. 1. For example, a wireless network may include any number of enbs and any number of UEs in any suitable arrangement. Also, the eNB101 may communicate directly with any number of UEs and provide those UEs wireless broadband access to the network 130. Similarly, each eNB102-103 may communicate directly with network 130 and provide direct wireless broadband access to network 130 for UEs. Further, the enbs 101, 102 and/or 103 may provide access to other or additional external networks, such as an external telephone network or other types of data networks.

Fig. 2 illustrates an example eNB102 in accordance with an embodiment of the disclosure. The embodiment of eNB102 shown in fig. 2 is for illustration only, and enbs 101 and 103 of fig. 1 may have the same or similar configurations. However, enbs have various configurations, and fig. 2 does not limit the scope of the disclosure to any particular implementation of an eNB.

As shown in FIG. 2, the eNB102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, Transmit (TX) processing circuitry 215, and Receive (RX) processing circuitry 220. The eNB102 also includes a controller/processor 225, a memory 230, and a backhaul or network interface 235.

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

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

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

Controller/processor 225 is also capable of executing programs and other processes resident in memory 230, such as an OS. Controller/processor 225 may move data into and out of memory 230 as needed to execute processes.

The controller/processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the eNB102 to communicate with other devices or systems over a backhaul connection or over a network. The interface 235 may support communication via any suitable wired or wireless connection. For example, when eNB102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G, LTE or LTE-a), interface 235 can allow eNB102 to communicate with other enbs by way of a wired or wireless backhaul connection. When eNB102 is implemented as an access point, interface 235 may allow eNB102 to communicate with a larger network (such as the internet) through a wired or wireless local area network or through a wired or wireless connection. Interface 235 includes any suitable structure that supports communication via a wired or wireless connection, such as an ethernet or RF transceiver.

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

Although fig. 2 shows one example of eNB102, various changes may be made to fig. 2. For example, eNB102 may include any number of each of the components shown in fig. 2. As a particular example, the access point may include a number of interfaces 235, and the controller/processor 225 may support routing functionality to route data between different network addresses. As another particular example, while shown as including a single instance of the TX processing circuitry 215 and a single instance of the RX processing circuitry 220, the eNB102 may include multiple instances of each TX processing circuitry 215 and RX processing circuitry 220 (such as one per RF transceiver). Also, the various components in FIG. 2 may be combined, further subdivided, or omitted, and additional components can be added according to particular needs.

Fig. 3 illustrates an example UE 116 in accordance with an embodiment of the disclosure. The embodiment of the UE 116 shown in fig. 3 is for illustration only, and the UE 111 and 115 of fig. 1 can have the same or similar configuration. However, the UE has various configurations, and fig. 3 does not limit the scope of the present disclosure to any particular implementation of the UE.

As shown in fig. 3, the UE 116 includes an antenna 305, a Radio Frequency (RF) transceiver 310, TX processing circuitry 315, a microphone 320, and Receive (RX) processing circuitry 325. The UE 116 also includes a speaker 330, a processor 340, an input/output (I/O) Interface (IF)345, a touchscreen 350, a display 355, and a memory 360. The memory 360 includes an Operating System (OS)361 and one or more applications 362.

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

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

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

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

The processor 340 is also coupled to a touch screen 350 and a display 355. The operator of the UE 116 may use the touch screen 350 to enter data into the UE 116. The display 355 may be a liquid crystal display, a light emitting diode display, or other display capable of rendering text and/or at least limited graphics, such as from a web site.

The memory 360 is coupled to the processor 340. A portion of memory 360 can include Random Access Memory (RAM) while another portion of memory 360 can include flash memory or other Read Only Memory (ROM).

Although fig. 3 shows one example of UE 116, various changes may be made to fig. 3. For example, the various components in FIG. 3 can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. As a particular example, 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). Also, while fig. 3 shows the UE 116 configured as a mobile phone or smartphone, the UE can be configured to operate as other types of mobile or fixed devices.

Fig. 4A is a high level diagram of the transmit path circuitry. For example, the transmit path circuitry may be used for Orthogonal Frequency Division Multiple Access (OFDMA) communications. Fig. 4B is a high level diagram of the receive path circuitry. For example, the receive path circuitry may be used for Orthogonal Frequency Division Multiple Access (OFDMA) communications. In fig. 4A and 4B, for downlink communications, transmit path circuitry may be implemented in the base station (eNB)102 or relay station, and receive path circuitry may be implemented in a user equipment (e.g., user equipment 116 of fig. 1). In other examples, for uplink communications, the receive path circuitry 450 may be implemented in a base station (e.g., eNB102 of fig. 1) or a relay station, and the transmit path circuitry may be implemented in a user equipment (e.g., user equipment 116 of fig. 1).

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

At least some of the components in fig. 4a 400 and 4B 450 may be implemented in software, while other components may be implemented in configurable hardware or a mixture of software and configurable hardware. In particular, it should be noted that the FFT blocks and IFFT blocks described in the present disclosure document may be implemented as configurable software algorithms, wherein the value of size N may be modified according to the implementation.

Furthermore, although the present disclosure is directed to embodiments implementing a fast fourier transform and an inverse fast fourier transform, this is by way of illustration only and should not be construed to limit the scope of the present disclosure. It should be understood that in alternative embodiments of the present disclosure, the fast fourier transform function and the inverse fast fourier transform function are readily replaced with a Discrete Fourier Transform (DFT) function and an Inverse Discrete Fourier Transform (IDFT) function, respectively. It should be understood that the value of the N variable may be any integer (i.e., 1, 4, 3, 4, etc.) for DFT and IDFT functions, and any power of 2 integer (i.e., 1,2, 4, 8, 16, etc.) for FFT and IFFT functions.

In transmit path circuitry 400, a channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., LDPC coding) and modulates (e.g., Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) the input bits to produce a sequence of frequency domain modulation symbols. Serial-to-parallel block 410 converts (i.e., demultiplexes) the serial modulation symbols into parallel data to produce N parallel symbol streams, where N is the IFFT/FFT size used in BS 102 and UE 116. Size NIFFT block 415 then performs an IFFT operation on the N parallel symbol streams to produce a time domain output signal. Parallel-to-serial block 420 converts (i.e., multiplexes) the parallel time-domain output symbols from size-N IFFT block 415 to produce a serial time-domain signal. Add cyclic prefix block 425 then inserts a cyclic prefix into the time domain signal. Finally, up-converter 430 modulates (i.e., up-converts) the output of add cyclic prefix block 425 to RF frequency for transmission over a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.

The transmitted RF signals arrive at the UE 116 after passing through the wireless channel and perform operations that are the reverse of those at the eNB 102. The down converter 455 down converts the received signal to baseband frequency and the remove cyclic prefix block 460 removes the cyclic prefix to produce a serial time-domain baseband signal. Serial-to-parallel block 465 converts the time-domain baseband signal to a parallel time-domain signal. Size N FFT block 470 then performs an FFT algorithm to generate N parallel frequency domain signals. Parallel-to-serial block 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decode and demodulation block 480 demodulates and then decodes the modulated symbols to recover the original input data stream.

each of the enbs 101 and 103 may implement a transmit path similar to the transmission to the user equipment 111 and 116 in the downlink and may implement a receive path similar to the reception from the user equipment 111 and 116 in the uplink. Similarly, each of the user equipments 111 and 116 may implement a transmission path corresponding to an architecture for transmission in uplink to the eNB101 and 103 and may implement a reception path corresponding to an architecture for reception in downlink from the eNB101 and 103.

A 5G communication system use case has been determined and described. Those use cases can be roughly classified into three different groups. In one example, enhanced mobile broadband (eMBB) is determined to be a high bit/second requirement, less stringent delay and reliability requirements. In another example, the ultra-reliable and low delay (URLL) are determined by less stringent bit/second requirements. In yet another example, large-scale machine type communication (mtc) is determined as the number of devices may reach every km²As many as 100,000 to 1 million, but the reliability/throughput/delay requirements may be less stringent. Such a scenario may also involve power efficiency requirements, as battery consumption should be takenAs minimal as possible.

Fig. 5 illustrates a network slice 500 according to an embodiment of the disclosure. The embodiment of the network slice 500 shown in fig. 5 is for illustration only. One or more of the components shown in fig. 5 may be implemented by dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

As shown in fig. 5, the network slice 500 includes an operator's network 510, a plurality of RANS 520, a plurality of enbs 530a, 530b, a plurality of small cell base stations 535a, 535b, a URLL slice 540a, a smart watch 545a, a car 545b, a truck 545c, smart glasses 545d, a power supply 555a, a temperature 555b, a mtc slice 550a, an eMBB slice 560a, a smart phone (e.g., cell phone) 565a, a laptop 565b, and a tablet 565c (e.g., tablet PC).

The operator's network 510 includes a number of radio access networks 520-RAN associated with network equipment (e.g., enbs 530a and 530b, small cell base stations (femto/pico enbs or Wi-Fi access points) 535a and 535b, etc.). The operator's network 510 may support various services that rely on the concept of slicing. In one example, the network supports four slices 540a, 550b, and 560 a. The URLL slice 540a serves UEs that require URLL services (e.g., car 545b, truck 545c, smart watch 545a, smart glasses 545d, etc.). Two mtc slices 550a and 550b serve UEs requiring mtc services, such as a power meter and a temperature control (e.g., 555b), and one eMBB slice 560a requiring eMBB serves UEs, such as a cell phone 565a, a laptop 565b, a tablet 565 c.

In summary, network slicing is a method for handling various different quality of service (QoS) in the network layer. Slice-specific PHY optimization may also be necessary to efficiently support these various qoss. Devices 545a/b/c/d, 555a/b, 565a/b/c are examples of different types of User Equipment (UE). The different types of User Equipment (UE) shown in fig. 5 are not necessarily associated with a particular type of slice. For example, cell phone 565a, laptop 565b, and tablet 565c are associated with eMBB slice 560a, but this is for illustration only, and these devices may be associated with any type of slice.

In some embodiments, a device is configured with more than one slice. In one embodiment, the UE (e.g., 565a/b/c) is associated with two slices, a URLL slice 540a and an eMBB slice 560 a. This may be useful to support an online gaming application where graphical information is sent through the eMBB slice 560a, while user interaction related information is exchanged through the URLL slice 540 a.

In the current LTE standard, no slice layer PHY exists, and most PHY functions are used as slice agnostic. The UE is typically configured with a single set of PHY parameters (including Transmission Time Interval (TTI) length, OFDM symbol length, subcarrier spacing, etc.), which may prevent the network (1) from adapting quickly to dynamically changing QoS; and (2) support various QoS simultaneously.

In some embodiments, respective PHY designs for handling different QoS with network slicing concepts are disclosed. It should be noted that "slice" is a term introduced for convenience only to refer to logical entities associated with common features, such as parameter sets, upper layers, including medium access control/radio resource control (MAC/RRC), and shared UL/DL time-frequency resources. Alternative names for "slice" include virtual cell, super cell, etc.

Fig. 6 illustrates an example number of digit chains 600 in accordance with an embodiment of the disclosure. The embodiment of the number of digit chains 600 shown in fig. 6 is for illustration only. One or more of the components shown in fig. 6 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

The LTE specification supports a maximum of 32 CSI-RS antenna ports, which enables the eNB to be equipped with a large number of antenna elements (such as 64 or 128). In this case, a plurality of antenna elements are mapped onto one CSI-RS port. For next generation cellular systems, such as 5G, the maximum number of CSI-RS ports may remain the same or increase.

For the mmWave frequency band, although the number of antenna elements may be large for a given form factor, the number of CSI-RS ports, which may correspond to the number of digital precoding ports, is often limited due to hardware constraints as shown in fig. 6 (such as the feasibility of installing a large number of ADCs/DACs at mmWave frequencies). In this case, one CSI-RS port is mapped onto a large number of antenna elements, which can be controlled by a set of analog phase shifters 601. One CSI-RS port may then correspond to a sub-array that produces a narrow analog beam by analog beamforming 605. This analog beam may be configured to scan over a wider angular range 620 by varying the set of phase shifters between symbols or subframes. The number of sub-arrays (equal to the number of RF chains) and the number of CSI-RS ports N_CSI-PORTThe same is true. Digital beam forming unit 610 pairs N_CSI-PORTThe analog beams perform linear combining to further increase the precoding gain. Although the analog beams are wideband (and thus not frequency selective), the digital precoding may vary between frequency sub-bands or resource blocks.

The gbb may cover the entire area of one cell with one or more transmit beams. The gNB may form a transmit beam by applying appropriate gain and phase settings to the antenna array. The transmit gain (i.e., the power amplification of the transmit signal provided by the transmit beam) is generally inversely proportional to the width or area of the beam coverage. At lower carrier frequencies, more benign propagation losses are feasible for the gbb to provide coverage of a single transmit beam, i.e., it is feasible to ensure adequate received signal quality at the UE location within the coverage area by using a single transmit beam. That is, at lower transmit signal carrier frequencies, the transmit power amplification provided by a transmit beam having a sufficiently wide width to cover the area is sufficient to overcome propagation losses, thereby ensuring sufficient received signal quality at the UE location within the coverage area.

However, at higher signal carrier frequencies, the transmit beam power amplification corresponding to the same coverage area may not be sufficient to overcome the higher propagation loss, resulting in degraded received signal quality at the UE location within the coverage area. To overcome such received signal quality degradation, the gNB may form multiple transmit beams, each covering an area narrower than the entire coverage area, but providing transmit power sufficient to overcome the higher signal propagation losses caused by using a higher transmit signal carrier frequency.

Fig. 7 illustrates example LTE cell search operations 700 in accordance with embodiments of the disclosure. The embodiment of the LTE cell search operation 700 shown in fig. 7 is for illustration only. One or more of the components shown in fig. 7 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

Before the UE can receive data or transmit data to the eNB, the UE first needs to perform a cell search procedure to acquire time and frequency synchronization with the eNB. The 4 main synchronization requirements are: symbol, subframe, frame timing; carrier Frequency Offset (CFO) correction; synchronizing sampling clocks; physical cell id (pci) detection and potentially some other cell specific parameters.

The following steps are taken during synchronization. In one example of step 1, after start-up, the UE would tune the RF of the UE and attempt to measure the wideband Received Signal Strength Indicator (RSSI) one by one at a particular frequency (channel commanded by higher layers) on a set of supported frequency bands and rank the associated elements according to their respective RSSI values.

In one example of step 2, the UE uses downlink synchronization channels, i.e., locally stored Primary Synchronization Signals (PSS) and Secondary Synchronization Signals (SSS), to correlate with the received signals. The UE first finds the PSS located in, for example, an FDD system in the last symbol of the first slot of the first and sixth subframes in the frame. This enables the UE to synchronize with the eNB on the subframe. PSS detection may help the UE perform slot timing detection and physical layer cell identity (PCI) detection based on 3 sequences (0, 1, 2). These 3 sequences are used for PSS to mitigate the so-called Single Frequency Network (SFN) effect, where the correlation output may exceed the Cyclic Prefix (CP) length.

In one example of step 3, the SSS symbol is also located in the same subframe as the PSS, rather than in the symbol preceding the PSS for FDD systems. The UE may obtain the PCI group number (0 to 167) from the SSS. The SSS enables determination of additional parameters, such as radio subframe timing determination, CP length determination, and whether the eNB uses FDD or TDD. This procedure is described in the LTE cell search procedure shown in fig. 7.

In one example of step 4, once the UE knows the PCI of a given cell, the UE also knows the location of cell-specific reference signals (CRSs) used for channel estimation, cell selection/reselection, and handover procedures. After channel estimation using the CRS, equalization is performed to remove channel impairments from the received symbols.

In one example of step 5, with initial synchronization, the UE may decode the Primary Broadcast Channel (PBCH) to obtain a Master Information Block (MIB) carrying critical system information such as DL bandwidth, CRS transmit power, number of eNB transmitter antennas, System Frame Number (SFN), and configuration of physical hybrid ARQ channel (PHICH).

Table 1 shows SSS locations relative to PSS locations for TDD-based and FDD-based systems. In case of FDD, PSS is transmitted in the last symbol of a slot so that a UE can acquire slot timing regardless of CP length. Since the UE does not know the CP length in advance, when the UE searches for an FDD or TDD cell, the UE needs to check a total of 4 possible SSS locations. Using two SSS codes that alternate between first SSS transmission and second SSS transmission in a subframe enables a UE to determine radio timing from a single observation for SSS, which is beneficial for the UE to switch from another RAT to LTE.

TABLE 1 SSS location

Fig. 8 illustrates an example frame structure of PSS/SSS/PBCH transmission 800 in an FDD configuration according to an embodiment of the disclosure. The embodiment of the frame structure of the PSS/SSS/PBCH transmission 800 shown in fig. 8 is for illustration only. One or more of the components shown in fig. 8 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

As shown in fig. 8, the PSS and SSS are transmitted in the middle 6 RBs so that even the smallest bandwidth UE can detect the signal. With multiple transmit antennas, the PSS and SSS are transmitted from the same antenna port in a given subframe, and may be switched between subframes to achieve antenna diversity. The PBCH carries MIB of only 14 bits, the 14 bits carrying some of the most frequently transmitted parameters (e.g., DL system bandwidth, PHICH size and SFN sequence number) used for initial access to the cell. Repeated every 40 milliseconds.

The PSS and SSS are transmitted in the middle 6 Resource Blocks (RBs) of the DL system bandwidth, so, assuming the minimum DL system bandwidth is 6 RBs, the UE may detect the PSS and SSS before the UE determines the DL system bandwidth. The PSS is generated from a length-63 Zadoff-chu (zc) sequence in the frequency domain with the middle elements punctured to avoid transmission on the DC subcarrier. ZC sequences satisfy Constant Amplitude Zero Autocorrelation (CAZAC) properties that give PSS time/frequency flatness (resulting in low PAPR/CM and no dynamic range in the frequency domain), good autocorrelation/cross correlation properties, low complexity detection at the UE end (by exploiting complex conjugate properties, e.g., u1 ═ 29 and u2 ═ 63-29 ═ 34, and by exploiting central symmetry properties in the time and frequency domains), etc.

However, due to the duality of CAZAC properties in the time and frequency domains, the shifting of ZC sequences in the frequency domain also occurs in the time domain and vice versa. Therefore, in the case of timing synchronization using ZC sequences, frequency/time offsets show time/frequency offsets, respectively, and the offsets in these two dimensions cannot be distinguished. The center root index in the available root ZC sequence index vector has a smaller frequency offset sensitivity, and therefore, the root indices u-25, 29 and 34 are selected in LTE to provide three cell IDs in the cell ID group.

The selection of the root index also takes into account local correlation to overcome the large frequency offset in the initial cell search. Since a large frequency offset causes a phase rotation in the time domain, local correlations need to be considered not only for ZC sequences but also for other sequences under large frequency offset operation (especially initial cell search), although the window size of each local correlation may be different in particular depending on the exact design.

PSS sequence x (N) of length N_ZCRoot of each occurrence is u_iAnd is given by the following formula:

the LTE ZC sequence is mapped to achieve a central symmetric property (i.e. index 5 corresponds to the DC carried by the RB sub-carriers, which include 12 sub-carriers indexed from 0 to 11). The SSS sequence depends on the M sequence. 168 sequences are generated by frequency-domain interleaving two length-31 BPSK-modulated M-sequences, where the two length-31M-sequences are derived from two different cyclic shifts of a single length-31M-sequence. The two-part structure of the SSS results in side lobes during cross-correlation and scrambling is used to mitigate the side lobes. For SSS, coherent detection may be performed when channel estimation may be obtained by PSS detection.

To achieve better performance for coherent detection of SSS by estimating the channel from the PSS, multiple PSS sequences are used and a tradeoff is made in PSS complexity detection. The different PSS sequences can improve the accuracy of channel estimation by relaxing the SFN effect that exists due to obtaining a single PSS sequence from all cells. Thus, the aforementioned PSS/SSS design may support coherent SSS detection and non-coherent SSS detection. The UE needs to operate three parallel correlators for three different PSS sequences.

However, the root indices 29 and 34 are complex conjugates of each other, so a "one-shot" correlator can be implemented, and the two correlation outputs of u-29 and u-34 can be obtained from correlations with u-34 or u-29. For any sampling rate, the conjugate property holds in both the time and frequency domains, and has a centrosymmetric mapping in the frequency domain. Thus, only two parallel correlators are required (one for u-25 and the other for u-29 (or u-34)).

There is a need to enhance existing synchronization and cell search procedures for new communication systems, such as 5G, for at least the following reasons.

In one example of beamforming support, the transmission of an eNB (possibly also including a UE) requires beamforming in order to meet link budget requirements for operation in high carrier bands, such as above 6 GHz. Therefore, the aforementioned synchronization and cell search procedures need to be updated to support beamforming.

In one example of large bandwidth support, for operation with larger system bandwidths (e.g., 100MHz or higher), a different subcarrier spacing may be applied than for operation with smaller system bandwidths, and this design needs to be considered for synchronization and cell search process design.

In one example of improved coverage, for certain applications, such as applications related to increased coverage requirements that may result from UE placement in locations experiencing greater path loss, the synchronization and cell search procedures need to support enhanced coverage and increase the number of synchronization signal repetitions.

In one example of improving performance, the synchronization performance of the above process is limited due to false alarms caused by dividing the cell ID into 1 PSS and 2 SSS, resulting in a PSS/SSS invalid combination that cannot be fully resolved by scrambling. A new synchronization process with improved ghosting performance can be devised.

In one example of supporting variable TTIs, in the current LTE specification, the TTI duration is fixed. However, for 5G systems, the TTI is expected to be variable due to support for different subcarrier spacing, low delay considerations, and the like. In such a case with variable TTI, the mapping of synchronization sequences and cell search within the frame needs to be specified.

In the present disclosure, the set of SS bursts is repeated periodically with a period P (where P is an integer), e.g., 5, 10, 20, 40, 80, 100, etc., in milliseconds.

In this disclosure, an SS burst refers to a set of consecutive N' s₂An SS block of which N₂Are integers such as 1,2, 3, 4.

In the present disclosure, the SS block includes a combination of a synchronization signal, a broadcast signal, and a reference signal, which are multiplexed in TDM, FDM, CDM, or hybrid manner.

In the present disclosure, cell coverage is provided over an SS block comprising a set of SS bursts by means of beam scanning. Different Tx beams may be used for different SS blocks within a set of SS bursts.

In LTE design, there is no concept of SS bursts/blocks/sets. However, the current LTE architecture can be seen as a special case in the framework of SS bursts/blocks/sets, where one set of SS bursts comprises four SS bursts; each SS burst consists of only one SS block, and one SS block consists of PSS, SSs, and PBCH symbols.

Fig. 9A illustrates an example SS burst 900 in an LTE system, according to an embodiment of the disclosure. One or more of the components shown in fig. 9A may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

Fig. 9B illustrates an example SS block/burst/set 950 in accordance with an embodiment of the present disclosure. The embodiment of SS block/burst/set 950 shown in fig. 9B is for illustration only. One or more of the components shown in fig. 9B may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In some embodiments of the present disclosure, a "subframe" or a "slot" is another name that refers to a "time interval X", or vice versa.

In some embodiments 1, the timing information is carried by DMRS and explicit NR-PBCH content.

In one embodiment, hybrid PBCH DMRS and PBCH content for carrying SS block index and half radio frame timing indication is considered. The SS block index is denoted X. X is 0 to 63 for NR above 6GHz, 0 to 7 for NR 1 to 6GHz, and 0 to 3 for NR below 1 GHz. M is denoted as the total assumption for DMRS. Y is a DMRS sequence number, Z is a half frame timing index, Z-0 indicates the first 5ms frame, and Z-1 indicates the second 5ms frame. "W" is denoted as a number in NR-PBCH, which denotes additional information of SS block index in NR above 6 GHz. In an alternative, half radio frame timing is conveyed by DMRS hypotheses. X, Y, Z, W, M can be determined by Y ═ X modular (M/2) + (M/2) × Z and W ═ floor (X/M × 2).

In one example, the design of PBCH DMRS is the same for both NR below 6GHz and above 6 GHz. To indicate more SS block indices above NR of 6GHz, additional 3 bits of information are put in PBCH. For NR below 6GHz, PBCH DMRS carries SS block index and half radio frame timing. As indicated in the LTE standard, a maximum of 8 SS blocks are indicated. The NR-PBCH DMRS may have at least 16 hypotheses before scrambling the cell ID. The 16 hypotheses may be used to indicate a half radio frame timing and 8 SS block indices. Thus, for NR below 6GHz, there may be no other assumptions in the NR-PBCH.

The complexity of the initial access may not exceed that in LTE. For NR above 6GHz, an additional 3 bits in the NR-PBCH are needed to indicate this additional information in the NR-PBCH, since the maximum SS block index is 64. The SS block index is denoted X. X is 0 to 63 for NR above 6GHz, 0 to 7 for NR 1 to 6GHz, and 0 to 3 for NR below 1 GHz. Y is a DMRS sequence number (0-15), Z is a half frame timing index, Z-0 means the first 5ms frame, and Z-1 means the second 5ms frame. "W" is denoted as a 3-bit number in NR-PBCH, which represents additional information of SS block index in NR above 6 GHz.

The indication of the SS block index and the half radio frame may be achieved by transmitting DMRS hypothesis sequence number Y and NR-PBCH information W. Note that the DMRS assumption here is different from the DMRS sequence. Because different cell IDs may be scrambled on top of PBCH DMRS, the same DMRS hypothesis may be mapped to different DMRS sequences. The mapping from SS block index and half radio frame timing to DMRS hypothesis and NR-PBCH information may be determined by the following equation: y ═ X modulator 8+8 × Z and W ═ floor (X/8).

Using this mapping scheme, the UE may still obtain some coarse beam index indication information without decoding the PBCH. Alternatively, the mapping from SS block index and half radio frame timing to DMRS hypothesis and NR-PBCH information bits is captured in table 2.

TABLE 2 mapping of SS Block index and half radio frame timing

In one embodiment, half the radio frame timing is indicated by the PBCH information payload along with additional SS block index information. The relationship between X, Y, Z, W and M can be determined by Y ═ X modulator (M) and W ═ floor (X/Y) + M × Z.

In some embodiments 2 RRM reports based on indications from the network are considered.

For NR above 6GHz, the SS block index may be larger than the hypothetical number in PBCH DMRS. For beam measurement, if the UE does not decode the PBCH, the UE may not be able to indicate/report the exact beam index and RSRP to the network. However, in some cases, the UE does not need to report the fine beam measurement RSRP to the network. Unless otherwise noted, the UE is configured to report the DMRS sequence index and the corresponding RSRP.

When the UE finds multiple SS blocks with the same DMRS sequence index in an SS burst set, the UE averages RSRP by the multiple SS blocks. The UE may be explicitly instructed to report the SS burst index for a given carrier frequency (RRC or SIB) through the network. When so indicated, the UE is configured to measure RSRP for each "beam" determined by the "SS burst index" and the "DMRS sequence index". The SS burst index may be conveyed by NR-PBCH payload information.

In one example, an SS burst is defined by every eight SS blocks starting from the beginning of the first SS block. The mapping from SS block index and half radio frame to DMRS sequence index/hypothesis is defined by the above-described embodiment (e.g., embodiment 1).

For each SS block in the same set of SS bursts, the SS blocks may share the same DMRS sequence index/hypothesis. The eNB may transmit the SS blocks using consecutive beams. After receiving SS blocks with the same PBCH DMRS sequence, the UE may average the RSRP and report the average of RSRP to the network.

In some embodiments of mobility beam index reporting, X of the X-bit beam index₁-bit part carried on PBCH DMRS, and another X of beam index₂-the bit portion is carried as at least one of a PBCH payload and PBCH scrambling, wherein X ═ X₁+X₂. In one example, X₁3. In another example, X₁4. Channel measurements are made on corresponding SS blocks (i.e., SSs) and optionally on PBCH DMRS.

In such embodiments, the (full) beam index may refer to the SS block index, and the total number of such indices is 2^ X. The partial beam index refers to a part of beam indexes carried by PBCH DMRS, and the total number of the indexes is 2^ X₁. The partial beam index may correspond to LSB or MSB of the entire beam index.

Fig. 10 shows a flow diagram of a method 1000 for beam ID reporting configuration in accordance with an embodiment of the present disclosure. The embodiment of the method 1000 shown in fig. 10 is for illustration only. One or more of the components shown in fig. 10 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

For mobility measurement reporting, it may be desirable that the UE may not need to decode the PBCH. This means that it would be desirable if the UE could generate a measurement report by detecting only PBCH DMRS sequences. If the total number of beams 2^ X is less than 2^ X₁This may be possible. However, if the total number of beams is greater than 2^ X, the UE must decode PBCH.

Therefore, it is proposed to indicate whether the UE is able to indicate to the SS blocks RSRP/RSRQ and the complete beam ID selected from among 2^ X beam IDs, or from 2^ X detected only on PBCH DMRS₁Selected ones of the beam IDs are reported together. This scheme is shown in figure 10.

Referring to fig. 10, the UE determines which beam ID type is configured for reporting. When a full beam ID report is configured, the UE derives and reports the SS blocks RSRP/RSRQ and the full beam ID, where each full beam ID is detected by detecting the sequence ID from PBCH DMRS and decoding the explicit bits from PBCH. When reporting partial beam IDs are configured, the UE derives and reports SS block RSRP/RSRQ and partial beam IDs, where each partial beam ID corresponds to a detected sequence ID in pbch mrss from the SS block.

If the UE does not receive this indication signaling, a default UE behavior needs to be defined. In a first alternative, the default UE behavior is to report the full beam ID. In a second alternative, the default UE behavior is to report a partial beam ID. The first alternative may be beneficial to the network (i.e. the full beam ID may be obtained), but the first alternative increases the burden on the UE side (e.g. the measured power consumption is larger). The second alternative is beneficial for the UE side (e.g., the measured power consumption is smaller).

The indication may be conveyed in RRC signaling or SIB/RMSI signaling per cell or per frequency band. When the UE is configured to report a full beam ID selected from among 2^ X beam IDs, the UE derives each detected SS block measurement (e.g., RSRP/RSRQ) by applying L3 filtering to the measurements of SS blocks with the same full beam ID in subsequent SS burst sets. For this measurement, the UE needs to deduce the beam ID under detection of PBCH DMRS sequence and decoding of PBCH explicit bits.

When the UE is configured to report only 2^ X detected from PBCH DMRS₁The UE needs to handle two cases for a selected partial beam ID among the beam IDs. In one example, during a SS burst set duration (or measurement window/duration) of 5 milliseconds, the UE has detected at most one SS block corresponding to each partial beam ID. In another example, the UE has detected more than one SS block corresponding to at least one partial beam ID during the same time duration.

In such an example, the UE may derive a measurement quantity (e.g., RSRP/RSRQ) for each detected SS block by applying L3 filtering to measurements from SS blocks with the same partial beam ID in subsequent SS burst sets. In such an example, an SS block with a certain partial beam ID may appear in a detected SS block multiple times within a 5 millisecond SS burst set duration.

In one case, the UE is configured to take an average of the measurement quantities with the same partial beam ID for each SS burst set duration and L3 filter the average of the measurement results from SS blocks with the same partial beam ID in subsequent SS burst sets.

In another example, the UE is configured to select a maximum of the measurement quantities having the same partial beam ID for each SS burst set duration, and L3 filter the maximum of the measurement results from SS blocks having the same partial beam ID in subsequent SS burst sets. Such examples and instances may be pre-configured or indicated through RRC or SIB signaling.

When the UE is configured to report a full beam ID selected from among 2^ X beam IDs, the UE derives a measurement quantity (e.g., RSRP/RSRQ) for each detected SS block by applying L3 filtering to the measurement results from SS blocks with the same full beam ID in subsequent SS burst sets. To make this measurement, the UE needs to deduce the beam ID in case of detecting the PBCH DMRS sequence and decoding the PBCH explicit bits.

Fig. 11 shows a flow diagram of a method 1100 for deriving a measurement quantity according to an embodiment of the disclosure. The embodiment of the method 1100 shown in FIG. 11 is for illustration only. One or more of the components shown in fig. 11 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one example, the design is the same for PBCH DMRS below 6GHz and PBCH DMRS above 6 GHz. To indicate more SS block indices above NR of 6GHz, additional 3 bits of information are put in PBCH. An indication of half a radio frame is also carried in the PBCH. For NR below 6GHz, the SS block index is carried by PBCH DMRS. As described in the LTE standard, a maximum of 8 SS blocks are indicated. The NR-PBCH DMRS may have at least 8 hypotheses before scrambling the cell ID.

8 hypotheses may be used to indicate 8 SS block indices. For NR above 6GHz, an additional 3 bits in the NR-PBCH are needed to indicate this additional timing information for the SS block, since the maximum SS block index is 64, and another bit is used to indicate half the radio frame timing.

The SS block index is denoted X. For NR above 6GHz, X is 0-63; for NR at 3-6GHz, X is 0-7; for NR below 3Ghz, X is 0-3. Y is represented as a DMRS sequence number (0-7), Z is represented as a half frame timing index, Z-0 represents a first 5ms frame, and Z-1 represents a second 5ms frame.

"W" is denoted as a number of 3 bits in NR-PBCH, which represents additional information of SS block index in NR higher than 6 GHz. The indication of the SS block index and half a radio frame may be achieved by transmitting the DMRS hypothesis sequence number Y and the NR-PBCH information W and Z. Note that the DMRS assumption here is different from the DMRS sequence. Because different cell IDs can be scrambled on top of PBCH DMRS, the same DMRS hypothesis can be mapped to different DMRS sequences. The mapping of SS block indices to PBCH and DMRS sequences may be detailed in table 2 below.

In one example, a half radio frame is indicated by two different scrambles of PBCH DMRS. In another example, half a radio frame is indicated by two different scrambles of the PBCH. In yet another example, half of the radio frame is indicated by an explicit bit in the PBCH.

In some embodiments, an indication of the actual number of SS blocks is considered.

In NR, the maximum value of the number of SS blocks in an SS burst set may be 64 for frequencies from 6GHz to 52 GHz; the maximum number of SS blocks is 8 for frequencies from 3GHz to 6 GHz; the maximum number of SS blocks may be 4 for frequencies up to 3 GHz. The number of SS blocks actually transmitted may be less than the maximum of the number of SS blocks. Therefore, the gNB needs to inform the number of actually transmitted SS blocks. After obtaining the information/indication from the gNB, the UE can know where the SS block is in the nominal SS block location defined by the SS block mapping pattern. There are different alternatives to indicate the number of actual SS blocks.

In an alternative, the actual number of SS blocks is indicated directly to the UE by PBCH or RMSI or DCI. For example, 2-bit information for NR below 3GHz, 3-bit information for NR 3GHz to 6GHz, 6-bit information for NR above 6GHz is transmitted to the UE in PBCH/RMSI/SIB/RRC/MAC CE/DCI to indicate the actual number of SS blocks.

In another alternative, the number of actual SS blocks is quantized to X bits of information and indicated to the UE, where X may be 2/3/4/5 bits. For example, for NR above 6GHz, 3 bits of information may be sent to the UE to indicate one of the actual number of SS blocks from the following set {8, 16, 24, 32, 40, 48, 56, 64 }. In another example, 4 bits of information may be sent to the UE to indicate one of the number of actual SS blocks from the following set {4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64 }.

In another example, 5 bits of information may be sent to the UE to indicate one of the number of actual SS blocks from the following set 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64. For frequencies from 3GHz to 6GHz, 2 bits of information may be sent to the UE to indicate one of the following actual SS blocks {2, 4, 6, 8 }. For frequencies below NR of 3GHz, 1 bit of information may be sent to the UE to indicate one of the following actual SS blocks {2, 4 }.

In some embodiments, it is contemplated to indicate the actual location of the SS block using a bitmap or a quantization bitmap. In such embodiments, the bitmap is used to indicate the actual location of the SS blocks. In one alternative, the number of bits used to indicate the location of the SS blocks is equal to the number of SS blocks per frequency band.

For example, for the case up to 3GHz, the bitmap is 4 bits; for frequencies from 3GHz to 6GHz, the bitmap is 8 bits; for frequencies above 6GHz, the bitmap is 64 bits. Each bit in the bitmap corresponds to whether an SS block defined in the SS block mapping pattern is transmitted. For example, a "1" in the bitmap indicates that the corresponding SS block was sent; a "0" in an SS block indicates that the corresponding SS block is not transmitted. For example, if the bitmap below 3GHz is 1000, it means that only the first SS block defined in the SS block mapping pattern is transmitted, and the other SS blocks are not transmitted. The UE can know the SS block actually transmitted by counting the total number of "1" s in the bitmap. The bitmap may be transmitted in RRC/DCI/SIB/RMSI.

In another alternative, the number of bits for indicating the position of the SS block that is less than or equal to the maximum value of the number of SS blocks per frequency band, i.e., the transmission of two or more consecutive SS blocks, is represented by 1 bit. In this way, the overhead of the bitmap can be compressed. For example, for a frequency band higher than 6GHz, a 32-bit bitmap may be used, and the ith bit (i ═ 1,2, …,32) in the bitmap may indicate whether to transmit (i-1) × 2 and (i-1) × 2+1 SS blocks, where we assume that the indices of the SS blocks are {0,1,2, …,63 }.

In another example, for the case above 6GHz, a 16-bit bitmap may be used, and the ith bit (i ═ 1,2, …,16) in the bitmap may indicate whether to transmit (i-1) × 4, (i-1) × 4+1, (i-1) × 4+2, and (i-1) × 4+3 SS blocks. In another example, for the case above 6GHz, an 8-bit bitmap may be used, and the ith bit (i ═ 1,2, …,8) in the bitmap may indicate whether to transmit (i-1) × 8, (i-1) × 8+1, (i-1) × 8+2, (i-1) × 8+3, (i-1) × 8+4, (i-1) × 8+5, (i-1) × 8+6, and (i-1) × 8+7 SS blocks.

Further, when an 8-bit bitmap is used, the i-th bit in the bitmap may indicate whether an SS block having the same 3-bit timing indication in the PBCH payload is transmitted. In another example, for frequencies from 3GHz to 6GHz, a 4-bit bitmap is used, and the ith bit (i ═ 1,2, …,4) in the bitmap may indicate whether to transmit (i-1) × 2 and (i-1) × 2+1 SS blocks.

For frequencies higher than 6GHz, a 4-bit bitmap is used, and the ith bit (i ═ 1,2, …,4) in the bitmap can indicate whether or not (i-1) × 16, (i-1) × 16+1, (i-1) × 16+2, (i-1) × 16+3, (i-1) × 16+4, (i-1) × 16+5, (i-1) × 16+6, (i-1) × 16+7, (i-1) × 16+8, (i-1) × 16+9, (i-1) × 16+10, (i-1) × 16+11, (i-1) × 16+12, (i-1) × 16+13, (i-1) × 16+14, and (i-1) × 16+15 SS blocks are transmitted. The actual SS blocks may be mapped consecutively starting from the start of the nominal SS block location defined by the SS block mapping pattern.

In some embodiments that contemplate indicating SS blocks using DCI, DCI information is used to indicate whether SS blocks are sent for connected UEs in an upcoming time slot. When the UE reads information from the DCI, the UE may decide whether to transmit an SS block in a slot. If no SS block in a slot is transmitted, the UE may assume that potential data or control may be transmitted in the corresponding PRB. Several configurations exist.

In one example, a 2-bit configuration information/bitmap (referred to as an "indicator bit") in the DCI is provided to indicate whether to send an SS block, or which SS block to send in a nominal SS block position in a slot. The 2-bit configuration information and the corresponding 4 states of the SS block transmission are specified in table 3 below.

TABLE 3 bit configuration information

Figure 12A illustrates an example PBCH BW 1200 in accordance with an embodiment of the disclosure. The embodiment of PBCH BW 1200 shown in figure 12A is for illustration only. One or more of the components shown in fig. 12A may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one example, when the UE is instructed to rate match around REs corresponding to SS blocks, the UE may assume that the SS blocks occupy a rectangular resource region comprising 4 consecutive OFDM symbols and 288 REs corresponding to PBCH BW, as shown in fig. 12A.

Fig. 12B illustrates an example PSS/SSS OFDM symbol 1250 in accordance with an embodiment of the disclosure. The embodiment of the PSS/SSS OFDM symbol 1250 shown in fig. 12B is for illustration only. One or more of the components shown in fig. 12B may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In another example, when a UE is indicated to rate match around REs corresponding to SS blocks, the UE may assume that the SS blocks occupy only the PSS/SSs/PBCH RE area (PSS/SSs/PBCH resource area). In this case, the UE may assume that the network transmits PDSCH data in BW that is not mapped with PSS/SSS in PSS/SSS OFDM symbols, as shown in fig. 12B.

In still another example, in the present embodiment, rate matching can be performed in the vicinity of "reserved resources" like the "SS block" in the present embodiment. The UE is configured with a number of reserved resources. For a scheduled PDSCH in a time slot, one or more of the configured reserved resources overlap with the scheduled PDSCH. The "configured reserved resources" in this method may also include potential SS block locations. The network may then indicate, via the DCI, whether rate matching may be performed around at least one of the one or more reserved resources, e.g., via the table above. Here, "reserved resources" may be used for forward compatibility reasons, and may be dynamically determined by the network and indicated to the UE.

In yet another example, when the UE is indicated to rate match around REs corresponding to SS blocks, the UE may assume that 12 RBs for PSS/SSs OFDM symbols are occupied while occupying 24 RBSS blocks for two PBCH OFDM symbols. In this case, the UE may assume that the network transmits PDSCH data in BW that is not mapped with PSS/SSS in PSS/SSS OFDM symbols.

In yet another example, a 4-bit configuration information/bitmap in DCI is provided to indicate whether four SS blocks are transmitted in nominal SS block positions in two consecutive special slots. Here, the special slot is defined as a slot in which an SS block can be mapped according to an SS block mapping mode.

In yet another example, a 2N bit configuration information/bitmap in DCI is provided to indicate whether 2N SS blocks are sent in a nominal SS block location if N special slots are aggregated. Each bit in the 2N-bit configuration information/bitmap may indicate whether a corresponding SS block is transmitted.

In yet another example, an N-bit configuration information/bitmap in DCI is provided to indicate whether 2N SS blocks are sent in a nominal SS block location if N special slots are aggregated. Each bit in the N-bit configuration information/bitmap may indicate whether the corresponding two SS blocks in a particular time slot are transmitted.

Depending on the slot type, the indication bit may or may not be present. For example, if the PDCCH in CORESET is transmitted in a slot whose slot number corresponds to a slot number in which an SS block can be transmitted, an indication bit exists in the PDCCH. Otherwise, the indication bit is not present in the PDCCH.

In some embodiments of network-wide and band-specific indication of actually transmitted SS blocks, the UE indicates to the UE, through the network, network-wide, band-specific information that is generally applicable to a superset of SS block locations belonging to all cells in the network in the same frequency band. The superset may be referred to as the "SS measurement set". The superset of SS block locations is a subset of the SS block locations for a particular frequency band defined in the standard specification.

Alternatively, the network-wide upper limit of the actual number of SS blocks for a particular frequency band may be configured by the network to be less than or equal to the maximum value of the number of SS blocks defined in the specification. The configuration of the superset or upper limit value may be conveyed in MIB, SIB or RRC messages. The benefits include saving UE power, reducing network overhead, and saving signaling overhead. Given the superset of configurations, the actual SS block location of the serving cell may be indicated for the UE for purposes of rate matching and/or for mobility measurements on neighboring cells.

The actual SS block locations configured may be a subset of the superset. The actual SS block location may be cell specific and thus information may be provided for each cell. The actual SS block location may be provided by way of a bitmap. Assume a superset has M SS blocks; the bitmap size is M bits and the ith bit indicates whether the ith SS block of the M SS blocks is on or off.

Fig. 13 shows a flow diagram of a method 1300 for configuring a maximum value of a band-specific number of SS blocks in accordance with an embodiment of the present disclosure. The embodiment of the method 1300 shown in FIG. 13 is for illustration only. One or more of the components shown in fig. 13 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

The actual SS block location may be provided in the MIB/SIB/RRC. If no more information is provided than the superset, the UE may assume that the actual SS block location for rate matching and measurement is based on the superset of SS block locations. A similar design is applicable when the upper limit value is configured. Fig. 13 shows details of UE processing based on configuration of a superset of SS block locations.

Fig. 14 shows a flow diagram of a method 1400 for indicating network-wide and band-specific information. The embodiment of the method 1400 shown in FIG. 14 is for illustration only. One or more of the components shown in fig. 14 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

Details of the UE processing based on the configuration of the band-specific maximum number of SS blocks are shown in fig. 14.

Several alternatives are possible to indicate the actual number of network wide and band specific information of SS block locations.

A first alternative is to indicate the network-wide and band-specific SS block location by the actual SS block number M. In this case, the M SS blocks may be mapped to the first M nominal SS block locations according to an SS block mapping pattern. For example, for a frequency band with a maximum number of SS blocks of 64 as defined by the standard in the network, it has turned out that a maximum of 48 SS blocks is sufficient for all cells. The value 48 may then be indicated to the UE by the gNB.

The UE may know that neither the serving cell nor the neighbor cell can use more than 48 SS blocks, and the UE may reduce the UE's measurement window during RRM measurements or neighbor cell measurements to measure no more than 48 SS blocks. The UE may further reduce the measurement effect of the UE if more information of the number of actual SS blocks of the cell is provided. Information may be provided for a serving cell and/or a selected set of neighboring cells. For example, the maximum number of network-wide SS blocks may be 48, while the actual number of SS blocks for a cell is 32. The UE may then further reduce the UE's measurement window for that cell to 32 to further reduce power consumption and complexity. If no number is provided to the neighbor cells, the UE may assume an upper limit value of the SS blocks for mobility measurement.

A second alternative is to indicate the network range and SS block location of a particular band by a bitmap or a quantization bitmap. For higher than 6GHz, 64 or 32 or 16 or 8 or 4 bits are sent from the network to the UE to indicate the maximum number of SS blocks within the UE network. If a 64-bit bitmap is used, the ith bit in the bitmap may indicate whether an SS block i in an SS block mapping pattern may be transmitted. If a 32-bit bitmap is used, the ith bit in the bitmap may indicate whether the SS blocks (i-1) × 2 and (i-1) × 2+1 in the SS block mapping pattern may be transmitted. If a 16-bit bitmap is used, the ith bit in the bitmap may indicate whether an SS block (i-1). times.4, (i-1). times.4 +1, (i-1). times.4 +2, and (i-1). times.4 +3 in the SS block mapping mode may be transmitted. If an 8-bit bitmap is used, the ith bit in the bitmap may indicate whether an SS block (i-1). times.8, (i-1). times.8 +1, (i-1). times.8 +2, (i-1). times.8 +3, (i-1). times.8 +4, (i-1). times.8 +5, (i-1). times.8 +6, and (i-1). times.8 + 7) in the SS block mapping mode may be transmitted.

In some embodiments where the actual SS block locations are indicated separately for mobility measurement and for rate matching, the actual SS block locations are indicated separately for mobility measurement purposes and for rate matching purposes.

For the purpose of mobility measurements, the following configuration and UE impact are explained below. In one example, there is a complete set of SS bursts for a particular frequency band specified in the LTE specification. In another example, a UE may be additionally indicated with a subset of the complete set of SS bursts, referred to as the "SS measurement set. The measurement set is valid for all cells of the same carrier frequency, i.e. carrier specific. The motivation for introducing this is that it is good for the UE to know this information when the network decides to implement only a few SS blocks in the carrier frequency to reduce the RSRP measurement burden of the UE. Reducing the UE burden can be explained as follows: if the UE is configured such that a certain SS block location may never have SS blocks, the UE does not need to measure RSRP in that SS block location.

In yet another example, the UE may be additionally configured with an SS/PBCH block measurement timing configuration (SMTC) duration. In yet another example, when both "SS measurement set" and SMTC durations are configured, the UE may monitor RSRP belonging to the "SS measurement set" only for the SMTC duration.

Although SMTC is used for the purpose of mobility measurement, the actual transmitted SS blocks in the serving cell may be different from what SMTC indicates. For example, the network may configure the SMTC so that the UE performs mobility measurements on the IDEL and CONNECTED UEs in a period of 80 milliseconds. However, the network can still send SS blocks at a 20 ms period to support initial access to the UE. In this case, the CONNECTED UE receiving the PDSCH in the serving cell may perform rate matching around the SS blocks transmitted at a period of 20 ms instead of 80 ms. This leads to a separate SS block periodicity indication from the SS block periodicity indication in the SMTC for rate matching.

In some embodiments, the SS block periodicity may be indicated for PDSCH rate matching purposes, which is configured separately from the SMTC configuration. In addition, the SS blocks to be rate matched in each set of SS bursts may not be consistent with the set of SS measurements.

In one example, an SS measurement set is provided for all TRPs in a cell, but the UE cannot detect energy in resources of SS blocks in the measurement set from a subset of TRPs. In this case, the network may still decide to send PDSCH for the UE on those SS block time-frequency resources, and may allow the UE to not rate-match around those time-frequency locations, although the time-frequency locations still belong to the measurement set.

The network may indicate to the UE a separate set of SS blocks, i.e., an "SS rate matching set," which is a subset of the complete set of SS bursts or the set of SS measurements. After receiving a DL assignment on a timeslot belonging to the SS measurement set, the expected UE behavior is as follows: if the SS block belongs to a rate matching set, performing rate matching on a PDSCH of the UE near the SS block; and/or not rate matching a PDSCH of the UE in the vicinity of the SS block if the SS block does not belong to the SS rate matching set.

To facilitate this indication scheme, a separate set of SS blocks, "SS rate matching set," may be indicated to the UE that is a subset of the complete set of SS bursts, such that the UE rate matches the PDSCH only in the vicinity of the SS blocks indicated in the SS rate matching set. The indication may be conveyed in SIB signaling, RRC signaling, MAC-CE signaling, or DCI signaling. In an alternative, the UE may/the UE may assume that the SS rate matching set corresponds to SS blocks activated by the MAC-CE.

As a result, the UE may be configured with parameters for the SS measurement set and parameters for the SS rate matching set. The periodicity of the set of SS measurements is the periodicity provided by the SMTC configuration, and the periodicity of the set of SS rate matches is indicated separately from the periodicity provided by the SMTC configuration.

The SS measurement set is a subset of the SS burst set, and is indicated by SIB/RRC; and applies to all cells in the carrier frequency (i.e. a particular band/carrier frequency configuration). The SS rate matching set is configured for each serving cell through SIB/RRC/MAC-CE/DCI and is a subset of the SS burst set. When the SS rate matching set is configured, the UE can perform rate matching near the SS block time-frequency position belonging to the SS rate matching set; the UE may not rate match around SS block time-frequency locations that do not belong to the SS rate matching set.

In some embodiments of the indication of the actual SS block location according to the SS block mapping pattern, the actual SS block location is indicated according to the SS block mapping pattern.

Fig. 15 illustrates an example mapping slot pattern 1500 in accordance with an embodiment of the disclosure. The embodiment of the map slot pattern 1500 shown in fig. 15 is for illustration only. One or more of the components shown in fig. 15 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In an alternative, a bitmap may be used to indicate whether a minimum repeating mapping slot pattern is transmitted. For example, when SCS is 5kHz and L is 4, the smallest mapping slot pattern is 1ms, and there are 2 mapping slot patterns of 1ms in total, as shown in fig. 15.

Thus, the use of a 2-bit bitmap in PBCH/DCI/RMSI/SIB to indicate which mapping slot pattern to transmit, where "00" in the bitmap indicates that no 1ms mapping slot pattern is transmitted; "01" in the bitmap indicates that the second 1ms mapping slot pattern is transmitted, and "10" in the bitmap indicates that the first 1ms mapping slot pattern is transmitted; "11" in the bitmap indicates that two 1ms mapping slot patterns are transmitted simultaneously.

In another example, as shown in fig. 15, when SCS is 15kHz and L is 8, the smallest mapping slot pattern is 1ms, for a total of 41 ms mapping slot patterns. Therefore, a 4-bit bitmap is used in PBCH/DCI/RMSI/SIB to indicate which 1ms mapped slot pattern to transmit. The ith bit in the bitmap may indicate whether the corresponding ith 1ms mapping slot pattern was sent.

In another example, as shown in fig. 15, when SCS is 30kHz and L is 4, the minimum mapping slot pattern is 0.5ms, and there are 2 mapping slot patterns of 0.5ms in total. Thus, a 2-bit bitmap is used in PBCH/DCI/RMSI/SIB to indicate which 0.5ms mapped slot pattern to send. The ith bit in the bitmap may indicate whether the corresponding ith 0.5ms mapping slot pattern was sent.

In another example, as shown in fig. 15, when SCS is 30kHz and L is 8, the minimum mapping slot pattern is 0.5ms, for a total of 4 mapping slot patterns of 0.5 ms. Thus, a 4-bit bitmap is used in the PBCH/DCI/RMSI/SIB to indicate which 0.5ms mapped slot pattern to transmit. The ith bit in the bitmap may indicate whether the corresponding ith 0.5ms mapping slot pattern was sent.

In another example, as shown in fig. 15, when SCS is 120kHz and L is 64, the minimum mapping slot pattern is 0.625ms, for a total of 8 mapping slot patterns of 0.625 ms. Therefore, which 0.625ms mapped slot pattern to send is indicated in a bitmap of 8 bits used in PBCH/DCI/RMSI/SIB. The ith bit in the bitmap may indicate whether the corresponding ith 0.625ms mapped slot pattern was sent.

In another example, as shown in fig. 15, when SCS is 240kHz and L is 64, the minimum mapping slot pattern is 0.625ms, for a total of 4 mapping slot patterns of 0.625 ms. Therefore, a 4-bit bitmap is used in PBCH/DCI/RMSI/SIB to indicate which 0.625ms mapped slot pattern to transmit. The ith bit in the bitmap may indicate whether the corresponding ith 0.625ms mapped slot pattern was sent.

In some embodiments of UE operation after receiving actual SS block location information from the network, after receiving information about the actual transmitted SS blocks (e.g., by a combination of actual SS block number, or bitmap or quantization bitmap, or actual SS block number, SS block offset, and SS block spacing), the UE may rate match or adjust the UE's measurement window around the SS blocks indicated as the actual transmitted SS block locations to make neighbor cell measurements.

Otherwise, the UE may assume that the maximum number of SS blocks is used and may rate match around all nominal SS block locations or use a maximum of 5ms measurement window for neighbor cell measurements. For example, in a network that sends a real number of SS blocks to the UE to indicate the real location of the SS blocks, the UE may know that the SS blocks may be mapped from the beginning of the nominal SS block location defined in the specification.

Specifically, in this example, when the SCS is 120kHz, when the UE receives 32 SS blocks of actual transmission, the UE may know that slots {0,1,2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18} have SS blocks, and slots {20, 21, 22, 23, 25, 26, 27, 28, 30, 31, 32, 33, 35, 36, 37, 38} have no SS blocks, and the corresponding time-frequency resources of the SS blocks may be used for data/control transmission. Also, if the information of the 32 actual SS blocks is related to neighbor cells, the UE can use only a 2.5ms measurement window for neighbor cell measurements.

In some embodiments of rate matching behavior outside of the SMTC window/duration comparison, the UE may be configured with SMTC windows for on-frequency measurements. Within each SMTC window, the UE is configured to perform mobility measurements or BM measurements based on SS blocks. During the mobility measurement, the UE may perform Rx beam scanning to find the best Rx beam for each Tx beam. In this case, the UE may be allowed to receive OFDM symbols having SS blocks using an Rx beam, which may be different from an Rx beam indicated by the network for receiving PDSCH data.

As seen in the foregoing embodiments of the present disclosure, the UE may be indicated with a transmitted SS block location, which may also be referred to as an "activated SS block location. The UE may perform rate matching around the location of the transmitted SS block, which may be repeated at a specified periodicity. However, the detailed UE behavior for rate matching near the transmitted SS block location may be specified in different ways to allow Rx beam scanning during SMTC windows for mobility measurements and optimal DL signal reception during non-SMTC windows/durations.

Given that the network and TRP may have multiple TXRUs to support multiple digital beams in the same OFDM symbol, the UE may be allowed to rate match around the actual transmission BW of the SS block, as in the previous embodiments. At the same time, the UE may also be allowed to rate match around the active BWP BW of the SS block OFDM symbols to cope with the case where the network/TRP has a single TXRU, in which case the analog beamforming constraints are still applicable.

Therefore, it seems necessary to introduce signaling to control the behavior of rate matching near the activated SS blocks. The signaling may be 1-bit RRC or MAC-CE signaling that specifies UE behavior for rate matching around active SS blocks. The indication (i.e., SS block rate matching indication) is used to inform the UE to rate match around (1) the active BWP BW for SS block OFDM symbols or (2) the SS block BW. This behavior can be maintained as long as the UE does not make mobility/BM measurements.

In case the UE performs mobility measurement/BM measurement, the UE may be allowed to perform Rx beam scanning, in which case action (2) does not apply. Therefore, it is also proposed to cover the behavior of rate matching near the SS block for PDSCH received within the SMTC window (i.e., using behavior (1)). Of course, outside the SMTC window, the rate matching behavior is based on the indication (i.e., (1) or (2)).

The UE treats the SMTC duration configured for inter-frequency measurements as a measurement interval, while still allowing the UE to receive PDSCH during the SMTC duration configured for intra-frequency measurements, based on applicable constraints, e.g., assuming rate matching and RE mapping of PDSCH around the entire active BWP BW of the active SS block OFDM symbols.

The same mechanism (i.e. rate matching around the entire BW) also applies for P/SP-CSI-RS configured for beam management (this may correspond to a specific CSI-RS pattern index for 1 port resource) to allow for Rx beam scanning. Alternatively, the UE may be explicitly configured with two status indications: (1) rate matching around the entire BW or (2) rate matching around the configured CSI-RS RE locations.

For intra-frequency measurements, the UE has been allowed to receive PDSCH/PDCCH during the measurement duration in LTE and preferably maintains the same principles. However, if the UE performs Rx beam scanning for SSB reception of the neighboring cell, the UE is less likely to receive PDSCH/PDCCH in the SSB OFDM symbol with good Rx beam for the serving cell.

This problem can be analyzed in different ways for the two cases: (1) when network synchronization is indicated; (2) when network synchronization is not indicated. In case (1) where network synchronization is indicated, the UE may still be able to receive PDSCH/PDCCH in the remaining OFDM symbols that are not used for SSB mapping. To this end, SSB set composition indicated for mobility measurement purposes (not one configured for rate matching purposes indicated in RRC/RMSI) may be used.

In case (2) network synchronization is not indicated, the UE may need to attempt to receive the SSBs of the neighboring cells in those OFDM symbols that are not used for SSB transmission of the serving cell. To allow Rx beam scanning of the UE, it seems impossible to transmit any PDSCH data during SMTC when the synchronous network is not indicated. Therefore, in case (2), it is proposed that the UE consider the entire on-frequency SMTC duration as the measurement interval.

In some embodiments, in intra-frequency SMTC durations, the scheduled PDSCH may be rate matched around the entire BWP BW corresponding to the SSB OFDM symbol if network synchronization is indicated. This is denoted as behavior 1. In such embodiments, SSB set compositions indicated for mobility measurement purposes may be used for this purpose (not one configured for rate matching purposes indicated in RRC/RMSI). In such embodiments, the UE is allowed to perform Rx beam scanning in the SSB OFDM symbol during the SMTC duration for intra-frequency measurements.

In some embodiments, in an intra-frequency SMTC duration, if network synchronization is not indicated, the UE may consider the entire intra-frequency SMTC duration as a measurement interval, i.e., the UE does not wish to receive PDSCH/PDCCH during the intra-frequency SMTC duration. This is referred to as action 2.

In some embodiments, outside of the same frequency SMTC duration, the UE uses the serving cell SSB set composition information for rate matching, which is indicated by RRC/RMSI. The rate matching BW (entire BWP BW and pbhbw) may be determined from two status indications.

Alternatively, RRC or SIBx may explicitly indicate to the UE for UE behavior during the on-frequency SMTC duration: depending on the frequency carrier (or component carrier, or serving cell), whether rate matching is done around the indicated SS block (i.e. action 1) or the SMTC duration is taken as the measurement interval (i.e. action 2).

Alternatively, the UE may be configured to use the union of two sets of SSBs (a first set of SSBs configured for serving cell rate matching purposes (i.e., RRC configuration of SSB-transmitted or RMSI configuration of SSB-transmitted-SIB 1) and a second set of SSBs configured for mobility measurement purposes for rate matching around PDSCH in the same frequency SMTC duration.

Fig. 16A shows an example measurement interval configuration 1600 in accordance with an embodiment of the present disclosure. The embodiment of the measurement interval configuration 1600 shown in FIG. 16A is for illustration only. One or more of the components shown in fig. 16A may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

The UE's assumption of a slot is shown in fig. 16A, depending on whether MG (measurement interval) is configured for the slot.

In some embodiments, the rate matching behavior of the coverage in the SMTC window duration is determined according to at least one of MG configuration, UE capabilities (related to Rx beam scanning), and carrier frequency of the SMTC window.

When the MG is not configured, the UE is allowed to receive FDM and/or TDM processed data through the SSB. When the UE does not perform Rx beam scanning, the UE may receive FDM/TDM processed data and SSB, as shown in fig. 16A.

As shown in fig. 16A, when the UE performs Rx beam scanning, the UE can receive only TDM-processed data and SSB. The UE may inform the network about the UE's capability for Rx beam scanning. Then, if the UE has indicated that the UE performs Rx beam scanning, the UE may assume TDM processed data and SSBs in the SMTC window duration (as shown in FIG. 16A; otherwise, the UE may assume FDM/TDM processed data and SSBs in the SMTC window duration (as shown in FIG. 16A.) or the UE assumes a carrier frequency dependent (i.e., the UE assumed configuration is a particular band and specified by the LTE specification.) for example, for a first band (e.g., for BWs below 6 GHz),

the UE assumption in SMTC window duration may be FDM/TDM, as shown in fig. 16A; for the second band (e.g., for BW above 6 GHz), the UE assumption in SMTC window duration may be TDM, as shown in fig. 16A. When MG is configured, the UE is not expected to receive PDSCH/PDCCH during the entire time slot belonging to the measurement interval duration.

Fig. 16B-16C illustrate configurations for rate matching near SSBs, according to embodiments of the disclosure. The embodiments of the configurations for rate matching near the SSB shown in fig. 16B-16C are for illustration only. One or more of the components shown in fig. 16B-16C may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In some embodiments, the rate matching bandwidth is configured around REs in the SS block OFDM symbol, as shown in alternative 1(1650) in fig. 16B.

In some embodiments, the rate matching bandwidth is configured around PBCH BW in the SS block OFDM symbols, as shown in candidate 2(1660) in fig. 16B.

In some embodiments, the rate matching bandwidth is configured at the data PRB edges near the PBCH BW in the SS block OFDM symbols, as shown in candidate 3(1670) shown in fig. 16C.

In some embodiments, the rate matching bandwidth is configured around the entire SS block of an OFDM symbol, as shown by candidate 4(1680) in fig. 16C.

In some embodiments, rate matching behavior that depends on CORESET or search space is considered. In this disclosure, SS burst set composition may refer to SS block mapping in half a frame.

In some embodiments, three different SS burst set compositions are considered at the UE side: complete SS burst set composition of a carrier frequency band, and first SS burst set composition indicated by RMSI; a second set of SS bursts indicated by RRC.

When the UE receives the PDSCH, the UE may apply rate matching and RE mapping around the SS block based on the selected set of SS bursts components.

The DCI carries at least one RNTI field that indicates the purpose of the DCI. Some examples are described below. If C-RNTI (also called UE-ID) is used, the DCI scheduled PDSCH/PUSCH is UE specific. If SI-RNTI is used, the DCI scheduled PDSCH is cell specific and the PDSCH carries system information. If RA-RNTI is used, DCI scheduled PDSCH is used for RACH response.

DCI containing C-RNTI is received during the CONNECTED mode. The DCI including the SI-RNTI and the P-RNTI may be received during all of the CONNECTED and IDLE modes and the initial cell selection period. The DCI including the temporary C-RNTI and the RA-RNTI may be received in a RACH procedure, an initial cell selection, or a handover procedure.

For different purposes, it is proposed to determine the rate matching behavior of the respective PDSCH/PUSCH from the RNTI type contained in the DCI, in view of the use cases of different RNTI types. When the first type of RNTI is used for the DCI, rate matching and RE mapping for the scheduled PDSCH/PUSCH are based on the first indication value; when the second type of RNTI is used for the DCI, rate matching and RE mapping for the scheduled PDSCH/PUSCH are based on the second indication value.

During initial cell selection, the UE receives DCI through the PDCCH in CORESET, and the PDCCH indicates the PDSCH containing RMSI (or SIB 1). Since the PBCH (or MIB) does not carry any information about the transmitted SS blocks, the UE may employ default SS burst set composition for rate matching and RE mapping to receive PDCCH. In this disclosure, "rate matching" may imply "rate matching and RE mapping".

After the UE receives the RMSI including the first indication of the SS burst set composition, PDSCH rate matching and RE mapping for the UE may be performed according to the SS burst set composition signaled by the RMSI. The DL indications received during this phase (after RMSI reception but before RRC signaling is received regarding updated SS burst set composition) include RACH response (msg2, msg4) and SIBx (x > 1).

Therefore, it is suggested that a PDSCH carrying SIBx (x >1) and RACH response (msg2, msg4) may be rate matched around an SS block indicated by a first indication consisting of a set of SS bursts. To achieve this operation depending on the type of RNTI, separate RNTIs may be allocated to SIB1 (or RMSI) and SIBx (x > 1).

For paging, since the paging PDSCH can be received in CONNECTED and IDLE modes, it seems that the processing of SIBx (x >1) is desirable. Thus, if the RNTI type is P-RNTI, the UE may use the first indication of SS burst set composition for PDSCH RE mapping and rate matching.

The UE may also receive the second indication via RRC signaling over the set of SS bursts in the CONNECTED mode. Since the purpose of this indication is to facilitate PDSCH reception by the UE on these non-serving SS block time-frequency resources in the same cell, the information is UE-specific. Therefore, it seems inappropriate to use the second indication for rate matching and RE mapping for cell-specific signaling. The use of the second indication may be limited to UE-specific PDSCH reception only.

That is, when the UE receives DCI with the C-RNTI that schedules the PDSCH, the UE may assume that the PDSCH is rate matched near the SS block indicated by the second indication (and PDSCH RE mapping is performed near the SS block).

Table 4 summarizes the PDSCH/PUSCH rate matching and PDSCH RE mapping behavior determined based on PDSCH content and/or RNTI types. The "full" set of SS bursts for the carrier band is used for RMSI PDSCH reception, which is scheduled for SIB1 by DCI with SI-RNTI.

The first indication carried in RMSI is for SIBx, RACH msg2/4 and paging reception, which is scheduled by DCI with SI-RNTI for SIBx (x >1), RA-RNTI, temporary C-RNTI, P-RNTI. The first indication may also be used for UE-specific dedicated message reception, which is scheduled by DCI with the C-RNTI until the UE receives RRC signaling containing the second indication. After the UE receives a second indication of the set of SS bursts through RRC signaling, the second indication is for UE-specific dedicated message reception scheduled by DCI with the C-RNTI.

TABLE 4 Rate pairing and PDSCH RE mapping

An alternative embodiment is described in table 5. The rate matching and PDSCH RE mapping behavior of PDSCH/PUSCH is determined based on CORESET type and/or RNTI type instead of PDSCH content and/or RNTI type. The "full" set of SS bursts for the carrier band is for RMSI PDSCH reception, which is scheduled by DCI with SI-RNTI for carrying SIB1 in MIB configured CORESET.

The first indication carried in RMSI is used for SIBx, RACH msg2/4 and paging reception, which is scheduled by DCI with SI-RNTI for SIBx (x >1), RA-RNTI, temporary C-RNTI, P-RNTI carried in MIB configured CORESET. The first indication may also be used for UE-specific dedicated message reception, scheduled by DCI with C-RNTI carried in the core set configured by the MIB; or in RRC configured core set until the UE receives RRC signaling containing the second indication. The second indication is for UE-specific dedicated message reception, which is scheduled by DCI with C-RNTI carried in RRC configured CORESET after the UE receives the second indication of SS burst set composition through RRC signaling.

TABLE 5 alternative rate pairing and PDSCH RE mapping

In an alternative embodiment, the protocol may use timing information of the RMSI transmission to indicate different rate matching behavior of the SIB1 (or RMSI) PDSCH instead of using a separate SI-RNTI. And according to the configuration carried in the PBCH, periodically sending the CORESET configured by the MIB in the appointed time slot. When the UE receives DCI in a PDCCH in a MIB-configured CORESET with SI-RNTI in these time slots, the UE may rate match around a complete SS burst set composition for receiving DCI-scheduled PDSCH; when the UE receives DCI with SI-RNTI in other time slots, the UE may rate match around the SS blocks according to the first SS burst set composition.

The remaining UE behavior related to rate matching may be according to table 4 or table 5. In one example, SIB1 PDSCH timing depends on the following.

In some embodiments, the network may activate/deactivate a subset of SS blocks by MAC-CEs in a set of SS bursts constructed from the complete set. In this case, the rate matching behavior can be further updated based on just the "activated SS blocks". The PDSCH is rate matched and RE mapped near the activated SS blocks, where the PDSCH is scheduled by DCI with C-RNTI (or DCI carried in RRC configured CORESET).

In an alternative embodiment, the PDSCH rate matching behavior is determined differently depending on the search space on which the PDCCH conveys the DL scheduling assignment. In one such example: behavior 1 RMSI PDSCH for receiving PDCCH scheduling sent in type0PDCCH search space on MIB configured CORESET (with CRS scrambled for SIB0 with SI-RNTI); action 2 is used to receive PDSCH with SI-RNTI, RA-RNTI, temporary C-RNTI, P-RNTI, C-RNTI for SIBx (x > 1). In an alternative, all these PDSCHs are scheduled by PDCCH sent in type1PDCCH search space on RMRESET configured by RMSI (SIB 1). In another alternative, a PDSCH with SI-RNTI for SIBx (x >1) is scheduled by a PDCCH sent on type0PDCCH search space on the MIB configured CORESET; scheduling a PDSCH having RA-RNTI, temporary C-RNTI, P-RNTI, C-RNTI, etc., by a PDCCH transmitted on a type1PDCCH search space on CORESET configured by RMSI (SIB 1); action 3 is used to receive PDSCH with C-RNTI to receive UE specific dedicated data scheduled by PDCCH sent in UE specific search space sent on RRC configured CORESET.

In one embodiment, a method of indicating SS burst set composition in a plurality of subbands in a wideband carrier is presented.

If the set of SS bursts are transmitted by the same set of TXRUs in a wideband carrier, SS blocks in different BWPs may be beamformed with the same analog beam due to analog beamforming constraints. Under this constraint, the composition of the set of SS bursts is the same on each subband of the wideband carrier.

For WB UEs configured with a single BWP over the entire wide bandwidth, the signaling content may indicate multiple frequency locations to map SS blocks (SSBs). This may be achieved by configuring a list of N starting PRB indices (common PRB indices) to map the N SSBs in the frequency domain (either through RRC signaling or SIB signaling).

In alternative embodiments, the end or intermediate PRB index may be indicated instead. After receiving this signaling, the UE may assume that the SS burst set composition corresponds to a full mapping, the first and second indications apply to all N SSBs in the frequency domain, and the UE may also assume that the indices of SSBs with the same SSB mapped to different subbands map to different subbands are QCL processed in a set of parameters (subset of delay or full set, doppler, average gain, and spatial parameters). The UE may apply PDSCH rate matching according to these information and also according to the first embodiment of the present disclosure.

In this disclosure, "subframe" or "slot" refers to another name of "time interval X" and vice versa.

Mapping from SS blocks to SS burst sets requires consideration of LTE-NR coexistence, especially when TDM sharing is used for LTE and NR to share the same spectrum. In this case, the mapping of SS blocks may also avoid "always on" LTE signals, such as CRS, synchronization signals (PSS/SSs/PBCH), and PDCCH, so as not to affect the operation of legacy LTE devices. In the LTE-NR coexistence scenario, the subcarrier spacing of the LTE signal may be fixed at 15 kHz. However, the subcarrier spacing of the NR SS may be 15kHz and 30 kHz. Specific configurations/designs of mapping SS blocks to slots and SS burst sets with respect to subcarrier spacing are contemplated in this disclosure.

In some embodiments, the mapping structure/pattern from SS blocks to slots is considered. Since SS blocks are "always on" signals in NR, mapping SS blocks to slots may avoid the location of potential "always on" signals in LTE, e.g., PSS/SSs; mapping SS blocks to slots may also avoid the location of potential control/reference signals such as PDCCH/CRS/PBCH in LTE.

Fig. 17A illustrates an example mapped SS block 1700 according to an embodiment of the present disclosure. The embodiment of mapped SS block 1700 shown in fig. 17A is for illustration only. One or more of the components shown in fig. 17A may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, as shown in fig. 17A, the NR SS subcarrier spacing is 30kHz and mapped SS blocks on OFDM symbols #4 to #7 are configured in the slot. In this example, the SSs in the NR may not overlap with control and reference signals in the LTE normal subframe.

Fig. 17B illustrates another example mapped SS block 1720 according to an embodiment of the present disclosure. The embodiment of mapped SS block 1720 shown in fig. 17B is for illustration only. One or more of the components shown in fig. 17B may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In another embodiment, as shown in fig. 17B, the NR SS subcarrier spacing is 30kHz, and mapped SS blocks on OFDM symbols #4 to #11 are configured and two SS blocks are mapped to one NR slot.

Fig. 17C illustrates yet another example mapped SS block 1740 according to an embodiment of the present disclosure. The embodiment of mapping the SS block 1740 shown in fig. 17C is for illustration only. One or more of the components shown in fig. 17C may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In yet another embodiment, some LTE subframes are configured as MBSFN subframes. Meanwhile, NR uses a 15kHz subcarrier spacing, and one SS block is mapped to OFDM symbols #2 to #5 in a slot aligned with the LTE MBSFN subframe, as shown in fig. 17C.

Fig. 17D illustrates yet another example mapped SS block 1760 in accordance with an embodiment of the disclosure. The embodiment of the map SS block 1760 shown in fig. 17D is for illustration only. One or more of the components shown in fig. 17D may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In yet another embodiment, some LTE subframes are configured as MBSFN subframes. Meanwhile, NR uses a 15kHz subcarrier spacing, and two SS blocks are mapped to OFDM symbols #2 to #5 and #8 to #11 in a slot aligned with the LTE MBSFN subframe, as shown in fig. 17D.

Fig. 17E illustrates another example mapped SS block 1780 in accordance with embodiments of the present disclosure. The embodiment of the map SS block 1780 shown in fig. 17E is for illustration only. One or more of the components shown in fig. 17E may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In yet another embodiment, some LTE subframes are configured as MBSFN subframes. Meanwhile, NR uses a 30kHz subcarrier spacing and maps two SS blocks to OFDM symbols #4 to #7 and #8 to #11 in a slot aligned with the LTE MBSFN subframe, as shown in fig. 17E.

In some embodiments, the SS burst set mapping pattern is different whether the frequency band is for LTE-TDD or LTE-FDD.

In some embodiments, a common SS burst set mapping mode is configured regardless of whether the frequency band is for LTE-TDD or LTE-FDD.

In some embodiments, in an LTE-FDD system, the SSs are in subframe 0 and subframe 5. Further, subframes 0, 4, 5, 9 cannot be configured as MBSFN subframes. In the LTE-NR coexistence scenario, SS burst set composition may avoid mapping SS blocks to subframes that overlap LTE subframe 0 and subframe 5. An alternative to this embodiment is to configure the subcarrier spacing of NR SS to 30kHz and map SS blocks to two of the following LTE subframes: subframe 1, subframe 2, subframe 3, subframe 4, subframe 6, subframe 7, subframe 8, and subframe 9. These selected subframes may be normal subframes or MBSFN subframes.

Fig. 18A illustrates an exemplary SS burst integration 1800, according to an embodiment of the disclosure. The embodiment of the SS burst set composition 1800 shown in fig. 18A is for illustration only. One or more of the components shown in fig. 18A may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In each selected NR slot, one SS block is mapped according to the SS block-to-slot pattern in the foregoing embodiment. Fig. 18A shows an example of such an alternative. In fig. 18A, the NR slot having the NR SS block can be considered as an SSB slot. The NR SS block is mapped to slot 2 to slot 5 aligned with LTE subframe 1 and subframe 2. In each selected slot or SSB slot, one SS block is mapped to OFDM symbols #4 to # 7.

Fig. 18B illustrates another example SS burst set composition 1820, in accordance with an embodiment of the disclosure. The embodiment of the SS burst set composition 1820 shown in fig. 18B is for illustration only. One or more of the components shown in fig. 18B may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In another alternative, LTE configures MBSFN subframes such that more SS blocks can be transmitted in NR slots. The other subframes may be normal subframes or MBSFN subframes. The candidates for MBSFN subframes may be subframe 1, subframe 2, subframe 3, subframe 6, subframe 7, and subframe 8. NR may configure the NR's SS subcarrier spacing to 30kHz and select the slot aligned with the LTE MBSFN subframe as the SSB slot. In the above embodiment, 2 SS blocks are transmitted using an SS block-to-slot mode in each selected slot or SSB slot. Fig. 18B shows an example. In this example, LTE selects subframe 1 as the MBSFN subframe. In NR, slot 2 and slot 3 are aligned with the LTE MBSFN subframe, so slot 2 and slot 3 are selected as SSB slots. According to embodiment 1, two SS blocks are mapped in each selected slot or SSB slot.

Fig. 18C illustrates yet another example SS burst set composition 1840, in accordance with an embodiment of the disclosure. The embodiment of the SS burst set composition 1840 shown in fig. 18C is for illustration only. One or more of the components shown in fig. 18C may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In another alternative, LTE configures MBSFN subframes such that more SS blocks can be transmitted in NR slots. The candidates for MBSFN subframes may be subframe 1, subframe 2, subframe 3, subframe 6, subframe 7, and subframe 8. NR may configure the NR's SS subcarrier spacing to 15kHz and select the slot aligned with the LTE MBSFN subframe as the SSB slot. In the above embodiment, 2 SS blocks are transmitted using an SS block-to-slot mode in each selected slot or SSB slot. Fig. 18C shows an example. In this example, LTE selects subframe 1 and subframe 2 as MBSFN subframes. The other subframes may be MBSFN subframes or normal subframes. In NR, slot 1 and slot 2(14 symbol slots) are aligned with the LTE MBSFN subframe, and thus slot 1 and slot 2 are selected as the SSB slots. In each selected slot or SSB slot, two SS blocks are mapped according to the foregoing embodiments.

Fig. 19A illustrates yet another example SS burst integration 1900 in accordance with an embodiment of the disclosure. The embodiment of SS burst set composition 1900 shown in fig. 19A is for illustration only. One or more of the components shown in fig. 19A may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In the LTE-TDD system, SSs are located in subframe 0, subframe 1, subframe 5, and subframe 6. Further, subframes 0,1,2, 5, and 6 cannot be configured as MBSFN subframes. In the LTE-NR coexistence scenario, SS burst set composition may avoid mapping SS blocks to subframes that overlap LTE subframe 0, subframe 1, subframe 5, and subframe 6. An alternative to this embodiment is to configure the subcarrier spacing of the NR SS to 30kHz and map SS blocks aligned with two of the LTE subframes, subframe 2, subframe 3, subframe 4, subframe 7, subframe 8 and subframe 9. In each selected NR slot, one SS block is mapped according to the SS block to slot pattern in the foregoing embodiment. Fig. 19A shows an example of such an alternative. The NR SS block is mapped to slot 4 to slot 7 aligned with LTE subframe 2 and subframe 3. In each selected slot or SSB slot, one SS block is mapped to OFDM symbols #4 to # 7.

Fig. 19B illustrates yet another example SS burst integration 1920, in accordance with an embodiment of the present disclosure. The embodiment of SS burst set composition 1920 shown in fig. 19B is for illustration only. One or more of the components shown in fig. 19B may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In another alternative, LTE configures MBSFN subframes such that more SS blocks can be transmitted in NR slots. The candidates for MBSFN subframes may be subframe 3, subframe 4, subframe 7, subframe 8, and subframe 9. NR may configure the NR's SS subcarrier spacing to 30kHz and select the slot aligned with the LTE MBSFN subframe as the SSB slot. In the above embodiment, 2 SS blocks are transmitted using an SS block-to-slot mode in each selected slot or SSB slot. Fig. 19B shows an example. In this example, LTE selects subframe 3 as the MBSFN subframe. In NR, slot 6 and slot 7 are aligned with the LTE MBSFN subframe, so slot 6 and slot 7 are selected as SSB slots. In each selected slot or SSB slot, two SS blocks are mapped according to the foregoing embodiments.

Fig. 19C illustrates yet another example SS burst integration 1940, according to an embodiment of the disclosure. The embodiment of the SS burst set composition 1940 shown in fig. 19C is for illustration only. One or more of the components shown in fig. 19C may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In another alternative, LTE configures two MBSFN subframes such that more SS blocks can be transmitted in the NR slot. The candidates for MBSFN subframes may be subframe 3, subframe 4, subframe 7, subframe 8, and subframe 9. NR may configure the NR's SS subcarrier spacing to 15kHz and select the slot aligned with the LTE MBSFN subframe as the SSB slot. In each selected slot or SSB slot (14 symbols), a maximum of two SS blocks are transmitted using the SS block to slot pattern in embodiment 1. One example is shown in fig. 19C. In this example, LTE selects subframe 3 and subframe 4 as MBSFN subframes. In NR, slot 3 and slot 4 are aligned with the LTE MBSFN subframe, so slot 3 and slot 4 are selected as SSB slots. In each selected slot or SSB slot, two SS blocks are mapped according to the foregoing embodiments. If a slot of 15kHz subcarrier spacing in NR is defined as 7 symbols. The selected time slots may be time slot 6 and time slot 7.

In one embodiment, the UL control channel may be transmitted within a short duration around the last transmitted UL symbol of the slot. The UL control channel is time and/or frequency multiplexed with the UL data channel within the time slot. For short duration UL control channels, transmission within one symbol duration of a slot is supported.

In one example, short UCI and data are frequency division multiplexed within and between UEs, at least where PRBs of the short UCI and data do not overlap.

In one example, to support TDM of short PUCCH from different UEs in the same slot, a mechanism to tell the UE on which symbol in the slot to send the short PUCCH is supported at least above 6 GHz.

The PUCCH supports at least the following for the duration of 1 symbol. In one example, if the RS is multiplexed, the UCI and the RS are multiplexed in a given OFDM symbol in an FDM manner. In one example, the same subcarrier spacing between DL/UL data and PUCCH within a short duration in the same slot.

In one example, PUCCH is supported at least in a short duration spanning 2 symbol durations of a slot. In such an example, the same subcarrier spacing between DL/UL data and PUCCH is within a short duration in the same slot.

In one example, at least the following semi-static configurations are supported. In such an example, PUCCH resources within a slot for a given UE (i.e., short PUCCH for a different UE) may be time division multiplexed for a given duration in the slot.

In one example, PUCCH resources include the time domain, the frequency domain, and, where applicable, the code domain.

In one example, from the UE perspective, a short duration PUCCH may span until the end of the slot. In such an example, no explicit gap symbol is needed after the short duration PUCCH.

In one example of a slot with a short UL portion (i.e., a DL-centric slot), if data is scheduled on the short UL portion, the "short UCI" and the data may be frequency division multiplexed by one UE. The UL control channel may be transmitted over multiple UL symbols for long periods to improve coverage. The UL control channel is frequency division multiplexed with the UL data channel within the time slot.

In one example, UCI carried by a long-duration UL control channel with at least a low PAPR design may be transmitted in one or more slots.

In one example, transmission across multiple slots may allow, for example, a total duration of 1ms, at least in some cases.

In one example, for a UL control channel with a long duration, TDM between RS and UCI is supported for at least DFT-S-OFDM.

In one example, the long UL portion of the slot may be used for transmission of a long duration PUCCH, i.e., a slot for UL only and a slot with a variable number of symbols and in which a minimum of 4 symbols are used for PUCCH transmission both support a long duration PUCCH.

In one example, the repetition may occur in N slots (N >1), either adjacent or non-adjacent, at least for 1 or 2 UCI bits, and the N slots allow for a long duration PUCCH.

In one example, simultaneous transmission of PUSCH and PUCCH is supported at least for long PUCCH formats, i.e., uplink control is transmitted on PUCCH resources even in the presence of data. In addition to simultaneous PUCCH-PUSCH transmission, UCI on PUSCH is also supported.

In one example, intra-TTI slot hopping is supported.

In one example, DFT-s-OFDM waveforms are supported.

In one example, transmit antenna diversity is supported.

TDM and FDM are supported between short-duration PUCCH and long-duration PUCCH, at least for different UEs in one slot. In the frequency domain, one PRB (or multiple PRBs) is the size of the smallest resource unit of the UL control channel. If frequency hopping is used, the frequency resources and hopping may not be spread over the carrier bandwidth. UE-specific RS is used for NR-PUCCH transmission. A set of PUCCH resources is configured by higher layer signaling, and PUCCH resources within the configured set are indicated by DCI

The timing between data reception and hybrid ARQ acknowledgement transmission as part of the DCI may be dynamically indicated (at least in conjunction with RRC). The combination of semi-static configuration and (at least for certain types of UCI information) dynamic signaling is used to determine PUCCH resources for "long PUCCH format and short PUCCH format", where PUCCH resources include time domain, frequency domain and, where applicable, code domain. In case UCI and data are simultaneous, UCI on PUSCH is supported, i.e. some scheduled resources are used for UCI.

To further discuss the short duration of PUCCH, the UCI payload is assumed to be 1 to at least several tens of bits (or SR). To further discuss the long duration operation of PUCCH, a UCI payload of 1 to at least several hundred bits (or SRs) is assumed.

In one embodiment of a short PUCCH with 1 symbol greater than 2 UCI bits, the following is supported. In one example of option 1, QPSK for UCI and X1 to X2 PRBs may be configured to support various UCI payload sizes: support both local (contiguous) and distributed (non-contiguous) allocations; detailed PRB allocation and configuration signaling; and values of X1 and X2. In one example of DMRS overhead, a downward selection of the following options is provided: option 1: a value (e.g., 1/2, 1/3, 1/4, 1/5 … …); and option 2: depending on a number of values, e.g., UCI payload size, etc.

The radio channel, especially the higher frequency radio channel, may change rapidly due to movement of the UE or blockage by surrounding objects, etc. Therefore, the UE needs assistance to find and maintain the best or proper Rx and Tx beams to ensure efficient transmission and reception. For this reason, future NR systems will require a beam management process. In NR, beam management is defined as follows.

In one example of beam management, the L1/L2 program set is used to acquire and maintain a set of TRP and/or UE beams available for DL and UL transmission/reception, which includes at least the following:

in one example of beam determination, the TRP or UE selects the TRP or UE's own Tx/Rx beam.

In one example of beam measurement, a TRP or UE is used to measure characteristics of a received beamformed signal

In one example of beam reporting, information for the UE to report beamformed signals based on beam measurements.

In one example of beam scanning, the operation of covering a spatial region, transmits and/or receives beams in a predetermined manner during a time interval.

The following is defined as Tx/Rx beam correspondence at the TRP and the UE. The Tx/Rx beam correspondence at the TRP holds if at least one of the following is satisfied: the TRP is capable of determining a TRPRx beam for uplink reception based on downlink measurements by the UE on one or more Tx beams of the TRP; the TRP is capable of determining a TRP Tx beam for downlink transmission based on uplink measurements of the TRP on one or more Rx beams; the Tx/Rx beam correspondence at the UE is established if at least one of the following is satisfied. The UE is able to determine a UE Tx beam for uplink transmission based on downlink measurements on one or more Rx beams of the UE; the UE is able to determine a UE Rx beam for downlink reception based on TRP indications of uplink measurements for one or more Tx beams; capability indication of UE beam correspondence related information to TRP is supported.

Note that the definition/terminology of Tx/Rx beam correspondence is for ease of discussion. The detailed performance condition is at most RAN 4. The following DL L1/L2 beam management procedures are supported within one or more TRPs. In one example, P-1 is used to enable the UE to measure on different TRP Tx beams to support selection of TRP Tx beam/UE Rx beam.

In one example, for beamforming at a TRP, it typically includes intra/inter TRP Tx beam scanning from a set of different beams. Beamforming at the UE typically includes UE Rx beam scanning from a set of different beams.

In one example, P-2: for enabling the UE to measure different TRP Tx beams to possibly change the TRP Tx beams between/within TRPs.

In one example, beam refinement is made from a beam set that may be smaller than P-1. Note that P-2 may be a special case of P-1.

In one example, where the UE uses beamforming, P-3 is used to enable the UE to measure the same TRP Tx beam to change the UE Rx beam.

At least network triggered aperiodic beam reporting is supported under operations related to P-1, P-2, and P-3. UE measurements based on RS for beam management (at least CSI-RS) consist of K (═ total number of configured beams) beams, and the UE reports measurements of L selected Tx beams, where L is not necessarily a fixed number. Note that RS-based procedures for mobility are not excluded. If L < K, the report information includes at least the measurement quantities of the L beams and information indicating the L DL Tx beams. In particular, when the UE is configured as a non-zero power (NZP) CSI-RS resource with K' >1, the UE may report a set of L UE-selected CSI-RS resource-related indices.

The UE may be configured with the following higher layer parameters for beam management: n is more than or equal to 1 report setting, and M is more than or equal to 1 resource setting; the link between the reporting setup and the resource setup is configured in the agreed CSI measurement setup (resource and reporting setup supports CSI-RS based P-1 and P-2); p-3 can be supported regardless of whether a report is set; the report setting includes at least: information indicative of the selected beam; l1 measurement report; time domain behavior: for example, aperiodic, periodic, semi-permanent; if multiple frequency granularities are supported, then frequency granularity is included; the resource setting at least comprises: time domain behavior: for example, aperiodic, periodic, semi-permanent; the RS type: at least NZP CSI-RS; at least one CSI-RS resource set, each CSI-RS resource set having K ≧ 1 CSI-RS resource; and some parameters of the K CSI-RS resources may be the same, such as port number, time domain behavior, density, and periodicity (if any).

At least one of these two alternatives to beam reporting is supported. In one example of alternative 1, the UE reports information about TRP Tx beams that may be received using a selected UE Rx beam set, wherein Rx beam set refers to the UE Rx beam set used to receive DL signals. The problem on how to construct the Rx beam set is a problem for UE implementation. One example is that each Rx beam in the UE Rx beam set corresponds to a selected Rx beam in each panel. For UEs with more than one UE Rx beam set, the UE may report TRP Tx beams and identifiers of the associated UE Rx beam set for each reported Tx beam.

Different TRP Tx beams reported for the same Rx beam set may be received simultaneously at the UE.

It may not be possible to receive different TRP TX beams reported for different UE Rx beam sets at the UE at the same time.

In one example of alternative 2, the UE reports information about the TRP Tx beam on a per UE antenna group basis, where the UE antenna group refers to a receiving UE antenna panel or sub-array. For a UE with more than one UE antenna group, the UE may report TRP Tx beams and an identifier of the associated UE antenna group for each reported Tx beam.

Different TX beams reported for different antenna groups may be received simultaneously at the UE.

It may not be possible to receive at the UE simultaneously the different TX beams reported for the same UE antenna group.

Fig. 20 illustrates example split Beam State Information (BSI) in a PUCCH 2000 according to an embodiment of the present disclosure. The embodiment of split BSI in PUCCH 2000 shown in fig. 20 is for illustration only. One or more of the components shown in fig. 20 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

When BSI is reported through PUCCH, at least the sequence number of beam Rx set/group, Tx beam information, and RSRP may be explicitly or implicitly provided to the gNB. It may be a part of the CSI-RS resource ID, the antenna port index, and the Tx beam time index, or a combination thereof.

If BSI reports are divided according to Rx beam sets or according to beam groups or according to beam-to-link (BPL) or even according to Tx beams, as shown in fig. 20, the split BSIs may be transmitted in different transmission instances. The transmission instance may be a frequency domain instance or a time domain instance, or even a code domain instance. BSI reporting per Rx beam group or group BSI or per BPL or per Tx beam is helpful for carrying BSIs for the following reasons.

In one example, this is useful when the UE is able to have varying numbers of Rx beam sets or Rx beam groups or BPL or Tx beams that will constitute varying payloads. By splitting the BSI, scalability to different number of Rx beam sets or Rx beam groups or BPL or Tx beams and variation of payload size can be supported, and the payload is the same in each PUCCH.

In one example, the short PUCCH may be transmitted within a short duration around the last transmitted one or two UL symbols of the slot. This is particularly useful for DL-centric time slots. It may be used for each transmission instance to carry one split BSI. After measurement, the short PUCCH can provide fast UCI feedback in several symbols, so that scheduling efficiency can be improved. The maximum payload supported by the short PUCCH may be up to several tens of bits, which is sufficient to support split BSI. For example, BSI reporting is considered where beam Rx set/group number, Tx beam index information, and RSRP are reported. The corresponding number of bits may be, for example, 4 bits, 3 bits and 7 bits, respectively, and the total payload bits will be 14 bits. Considering beam management listening, it is possible to report only one service beam RSRP, and thus it is not necessary to report Tx beam index information, and then the payload is 11 bits. The BSI report may provide a differential RSRP if the reference RSRP has been configured and is known by the UE to be configured, and the payload of the total split BSI is 8 bits for a 4-bit differential RSRP.

In one example, for a long PUCCH, when better coverage is needed, the split BSI may be used to carry a similar payload as the short PUCCH.

In one example, a long PUCCH or a long PUSCH may be used with a short PUCCH. When the entire payload of L BSIs is reported, a longer period may be configured for the long PUCCH or the long PUSCH. The short PUCCH may be used to transmit the small BSI payload of the selected BPL or the serving BPL with a smaller periodicity.

In one example, when the gNB needs to know the beam quality information of the selected BPL or the serving BPL. The BSI information may be small because only beam quality information for the selected BPL or the serving BPL needs to be reported. The short PUCCH used in this case may be periodic or aperiodic.

The at least semi-static configuration may support PUCCH resource allocation for a given UE within the slot. PUCCH resources include the time domain, the frequency domain, and, where applicable, the code domain. When PUCCH is used to carry BSI, a set of N PUCCH resources may be semi-statically allocated and configured, where some periodic transmission instances are configured through RRC signaling, and may be frequency domain instances or time domain instances or code domain instances. In the resource allocation, each transmission instance is linked with a sequence number of an Rx beam set/group or a Tx beam index or a combination of the sequence number of the Rx beam set/group and the Tx beam index. Through this linking, the combination of the sequence number of the Rx beam set/group or the Tx beam index or the sequence number of the Rx beam set/group may be implicitly indicated, and some signaling bits in the PUCCH may be saved.

The set of N PUCCH resources may be configured by an indication of one PUCCH resource index. For example, for a first PUCCH resource in a PUCCH resource set, the UE is indicated with a sequence number of one OFDM symbol (i.e., l). The OFDM symbols for the remaining portion of the (N-1) PUCCH resources are then determined by an l function. In one example, the OFDM symbols for the N PUCCH resources are: l, l +1, …, l + N-1. In another example, the OFDM symbols for the N PUCCH resources are L-1, L-2, …, L-N, where L is the number of OFDM symbols in the slot. All these N PUCCH resources are allocated in the same slot.

Fig. 21 illustrates example implicit signaling of Tx beam index information 2100, according to an embodiment of the present disclosure. The embodiment of implicit signaling of Tx beam index information 2100 shown in fig. 21 is for illustration only. One or more of the components shown in fig. 21 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, PUCCH resource allocation for BSI reporting in PUCCH is shown in fig. 21. A set of PUCCH resources is configured for each Tx beam index through RRC signaling, and the Tx beam index is implicitly reported in the PUCCH. If a set of PUCCH resources is semi-statically allocated for each Tx beam index, where each transmission instance corresponds to one Tx beam index information in one Rx beam set/group number, the correspondence between Tx beam index information and transmission instances may be implicit, and thus there is no need to explicitly transmit Tx beam index information in the payload, resulting in a smaller payload. For example, when the Rx beam set/group number, Tx beam index information, and RSRP are reported in each PUCCH, the number of bits may be 4 bits, 3 bits, and 7 bits, respectively, and the total payload is 14 bits. Then, if only beam Rx set/group number and RSRP are reported, the total payload in each PUCCH will be reduced to 11 bits. The Tx beam index information is implicitly indicated by the selected resource index, for which the UE is configured with 2³8 PUCCH resources. In one such case, the UE sends PUCCH in resource n for reporting Rx set/group number and RSRP n of the Tx beam. The network may configure the UE to report N reports corresponding to the N Tx beams. In this situationIn case, the selected N resource sets will indicate the selected N Tx beams to be used for reporting.

The foregoing embodiments may also be applied to replacing the Tx beam index in fig. 21 with a beam pair linkage (i.e., a pair of Tx beam index and Rx beam set index). In this case, in each PUCCH report in resource n, the RSRP for beam pair link n is reported. In this case, the network also configures N beam pair links and N PUCCH resources for PUCCH reporting. The beam pair linkage may be updated by MAC/CE signaling or the N beam pair linkages may be indicated in the DCI.

Fig. 22 illustrates another example implicit signaling of Tx beam index information 2200 in accordance with an embodiment of the present disclosure. The embodiment of implicit signaling of the Tx beam index information 2200 shown in fig. 22 is for illustration only. One or more of the components shown in fig. 22 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, the UE transmits PUCCH in all allocated resources. In the example shown in fig. 22, Tx beam index information is implicitly conveyed. In this example, it may be assumed that PUCCH resources of 4 Tx beams are respectively configured. The PUCCHs in examples 1-4 are transmitted for Tx beam indices 1-4, respectively.

Fig. 23 illustrates another example implicit signaling of Tx beam index information 2300, according to an embodiment of the present disclosure. The embodiment of implicit signaling of Tx beam index information 2300 shown in fig. 23 is for illustration only. One or more of the components shown in fig. 23 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, the UE transmits PUCCH only in a fraction of all allocated resources, since not all Tx beams are suitable for reporting. In one example, it may be assumed that PUCCH resources of 4 Tx beams are respectively configured. As shown in fig. 23, PUCCH instance 3 implicitly indicates that information of Tx beam index 3 in one Rx beam set/group number is reported in the BSI report, without transmitting the PUCCH in instances 1,2, and 4.

Fig. 24 illustrates example implicit signaling of an Rx beam set/group number 2400 in accordance with an embodiment of the disclosure. The embodiment of implicit signaling of Rx beam set/group number 2400 shown in fig. 24 is for illustration only. One or more of the components shown in fig. 24 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, PUCCH resource allocation for BSI reporting in PUCCH is as shown in fig. 24. A set of PUCCH resources is configured for each Rx beam set/group through RRC signaling, and an Rx beam set group number is implicitly reported in the PUCCH. If each Rx beam set/group number semi-statically allocates a set of PUCCH resources, where each transmission instance belongs to one of the Rx beam sets/groups, the correspondence between Rx beam set/group number and transmission instance may be implicit, and therefore, there is no need to explicitly send the Rx beam set/group number in the payload, resulting in a smaller payload. For example, when the Rx beam set/group number, Tx beam index information, and RSRP are reported in each PUCCH, the number of bits may be 4 bits, 3 bits, and 7 bits, respectively, and the total payload is 14 bits. Then, if only Tx beam index information and RSRP are reported, the total payload in each PUCCH will be reduced to 10 bits.

Fig. 25 illustrates another example implicit signaling of an Rx beam set/group number 2500 in accordance with an embodiment of the present disclosure. The embodiment of implicit signaling of Rx beam set/group number 2500 shown in fig. 25 is for illustration only. One or more of the components shown in fig. 25 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, the UE transmits PUCCH in all allocated resources. In the example shown in fig. 25, the Rx beam set/group number is implicitly conveyed. In this example, it may be assumed that PUCCH resources of 4 Rx beam sets/groups are respectively configured. PUCCH instance 3 implicitly indicates that Rx beam set/group 3 is reported in the BSI report, while PUCCHs in instances 1,2, and 4 are transmitted for Rx beam set/group number 1,2, and 4, respectively.

Fig. 26 illustrates another example implicit signaling of an Rx beam set/group number 2600 in accordance with an embodiment of the disclosure. The embodiment of implicit signaling of Rx beam set/group number 2600 shown in fig. 26 is for illustration only. One or more of the components shown in fig. 26 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, the UE transmits PUCCH only in a fraction of all allocated resources since not all Rx beam sets/groups are eligible for reporting. In an example, it may be assumed that PUCCH resources of 4 Rx beam sets/groups are respectively configured. As shown in fig. 26, PUCCH instance 3 implicitly indicates that Rx beam set/group 3 is reported in BSI report, and the PUCCH in instances 1,2, and 4 is not transmitted.

In one embodiment, PUCCH resource allocation for BSI reporting in PUCCH is shown in fig. 27. A set of PUCCH resources is configured for each Rx beam set/group and Tx beam index through RRC signaling, and the Rx beam set/group number and Tx beam index are implicitly reported in the PUCCH. If a set of PUCCH resources is semi-statically allocated for each Rx beam set/group number, where each transmission instance in one Rx beam set/group number corresponds to one of the Tx beam index information in that Rx beam set/group number, the correspondence between Tx beam index information and transmission instances may be implicit, and thus there is no need to explicitly transmit Tx beam index information in the payload, resulting in a smaller payload. Each set of PUCCH resources also corresponds to a particular Rx beam set/group number, which may then also be sent implicitly in the payload. For example, when an Rx beam set/group number, Tx beam index information, and RSRP are reported in each PUCCH, the number of bits may be 4 bits, 3 bits, and 7 bits, respectively, and the total payload is 14 bits. Then, if only RSRP is reported, the total payload in each PUCCH will be reduced to 7 bits.

Fig. 27 illustrates example implicit signaling of Rx beam set/group number and Tx beam index information 2700 according to an embodiment of the present disclosure. The embodiment of the implicit signaling of the Rx beam set/group number and the Tx beam index information 2700 shown in fig. 27 is for illustration only. One or more of the components shown in fig. 27 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

Fig. 28 illustrates another example implicit signaling of Rx beam set/group number and Tx beam index information 2800 according to an embodiment of the present disclosure. The embodiment of the implicit signaling of the Rx beam set/group number and the Tx beam index information 2800 shown in fig. 28 is for illustration only. One or more of the components shown in fig. 28 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, the UE transmits PUCCH in all allocated resources. In the example shown in fig. 28, Rx beam set/group number and Tx beam index information are implicitly conveyed. In this example, it may be assumed that PUCCH resources of n Rx beam sets/groups and 4 Tx beams in each Rx beam set/group are respectively configured. Each PUCCH instance implicitly indicates which Rx beam set/group and Tx beam index information is reported in the BSI report.

Fig. 29 shows another example implicit signaling of Rx beam set/group number and Tx beam index information 2900 according to an embodiment of the present disclosure. The embodiment of implicit signaling of the Rx beam set/group number and Tx beam index information 2900 shown in fig. 29 is for illustration only. One or more of the components shown in fig. 29 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, since not all Rx beam sets/groups or Tx beams are eligible for reporting, the UE transmits PUCCH only in a fraction of all allocated resources. In an example, it may be assumed that PUCCH resources of n Rx beam sets/groups and 4 Tx beams in each Rx beam set/group are respectively configured. As shown in fig. 29, PUCCH instance 3 in Rx beam set/group 1 and PUCCH instance 2 in Rx beam set/group n implicitly indicate that Tx beam index 3 in Rx beam set/group 1 and Tx beam index 2 in Rx beam set/group n are reported in BSI report, without transmitting other PUCCH instances.

Fig. 30 shows an example short PUCCH transmission 3000 according to embodiments of the present disclosure. The embodiment of short PUCCH transmission 3000 shown in fig. 30 is for illustration only. One or more of the components shown in fig. 33 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

For short PUCCHs, each short PUCCH may have a separate Tx beam configured by implicit signaling or semi-static RRC signaling, as shown in fig. 30. Tx beams for different PUCCHs may be directed to different TRPs, e.g., to support multiple connections (e.g., multiple BSIs for different TRPs in case of non-ideal backhaul).

In one embodiment, the Tx beam of each short PUCCH is configured as semi-static RRC signaling if the beam correspondence is not established.

In one embodiment, when each short PUCCH resource is configured for each BPL, if a beam correspondence relationship holds, a Tx beam of each short PUCCH is selected based on each configured BPL, wherein the Tx beam and the Rx beam are associated by the beam correspondence relationship.

In one embodiment, each short PUCCH resource is configured for each Rx beam set. If the beam correspondence is established, a Tx beam of each short PUCCH is selected based on each configured Rx beam set, wherein the Tx beam is associated with an Rx beam in each Rx beam set through the beam correspondence.

Fig. 31 illustrates an example long PUCCH transmission 3100 in accordance with an embodiment of the disclosure. The embodiment of the long PUCCH transmission 3100 shown in fig. 31 is for illustration only. One or more of the components shown in fig. 31 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

For the long PUCCH, the foregoing embodiments of the short PUCCH may also be applicable. For a long PUCCH, as shown in fig. 31, each PUCCH symbol may use a separate Tx beam.

In one embodiment, a time domain beam cycle is used, where each PUCCH symbol uses a Tx beam predefined by a particular beam selection function. In one embodiment, each PUCCH symbol uses a Tx beam that is semi-statically explicitly transmitted by RRC.

The network may dynamically perform PUCCH beam indication through implicit signaling, semi-static RRC signaling, or DCI signaling of the PDCCH depending on what content the PUCCH channel carries, whether beam correspondence is established, etc. The beam indication of PUCCH may be SRI or (SRI + antenna port). When different UCIs are multiplexed in the same resource or the same OFDM symbol, there may be a mechanism to resolve beam indication collisions.

A common solution for PUCCH beam indication is as follows. In one example, PUCCH beams are configured separately for each UCI case. The PUCCH Tx beam may be configured through DCI, RRC, or MAC CE. Configuring a first PUCCH beam aiming at a PUCCH comprising A/N/SR; for a PUCCH that does not include an a/N/SR, a second PUCCH beam is configured. In one example, a common PUCCH beam is configured for all PUCCHs. In one example, separate beams or a common beam is configured for PUCCH and PUSCH.

In one embodiment, PUCCH and PUSCH may be configured separately for Tx beams for certain reasons, e.g., PUCCH may have a wider beam than PUSCH and PUCCH and PUSCH may be directed to different TRPs for better reliability.

In one embodiment, the Tx beams may also change if they are directed to different TRPs for different UCI cases and are configured separately. They may or may not be in conflict, depending on their respective configurations.

Fig. 32 illustrates an example PUCCH beam indication 3200 according to an embodiment of the disclosure. The embodiment of PUCCH beam indication 3200 shown in fig. 32 is for illustration only. One or more of the components shown in fig. 32 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

The process of resolving beam collisions for all UCI cases is shown in fig. 32.

When the PDCCH and PUCCH beams are in a beam correspondence for the A/N/SR-only PUCCH, the A/N/SR-only PUCCH beam is implicitly selected by the PDCCH beam or indicated by DCI signaling or MAC CE or RRC signaling.

When the PDCCH and the PUCCH beam are in a beam correspondence relationship for the A/N/SR-only PUCCH, the A/N/SR-only PUCCH beam is indicated by DCI signaling or MAC CE or RRC signaling.

For CQI/BSI PUCCH, beams are configured by semi-static RRC for periodic reporting or DCI for aperiodic reporting.

When a CQI/BSI PUCCH and an A/N/SR PUCCH are transmitted in different OFDM symbols, respectively, different beams are used for the CQI/BSI PUCCH and the A/N/SR PUCCH through different beam indications.

When multiplexing CQI/BSI and a/N/SR in PUCCH, if a common beam is configured for CQI/BSI and a/N/SR, the common beam is used, otherwise, the a/N/SR beam can be selected.

When the UCI is multiplexed on the PUSCH, if a common beam is configured for the PUCCH and the PUSCH, the common beam is selected, otherwise the UE may select the PUSCH beam.

For reporting L BSIs, PUSCH, long PUCCH, or short PUCCH may be considered. PUSCH may be used for aperiodic BSI reporting. The long PUCCH and the short PUCCH may be used for periodic reporting and aperiodic reporting. When long PUCCH and short PUCCH are used for aperiodic reporting, CSI/BSI triggers are embedded in PDCCH transmitted in the same slot as PUCCH. For example, the UE may be triggered to report a beam quality corresponding to a preconfigured DL BPL or a serving BPL through the PDCCH. The PUSCH and long PUCCH may carry the entire payload of the L BSIs without compression. However, the short PUCCH may not be sufficient to carry the entire payload of the L BSIs.

For aperiodic PUSCH reporting, the entire payload of L BSIs, gNB configured BPL's/served DL BPL may be carried in a single report.

For aperiodic PUCCH reporting, aperiodic PUCCH is used for one case of sending BSI reports: when the gbb needs to know the beam quality information of the BPL configured or served by the gbb. This BSI information may be small because only beam quality information for a single BPL (e.g., a gbb configured BPL or a serving BPL) needs to be reported. Aperiodic PUCCH is also very useful for faster BSI reporting in self-contained subframes when the triggering of aperiodic PUCCH reporting in DCI is in the same subframe as PUCCH.

Fig. 33 illustrates an example DCI triggering aperiodic PUCCH 3300 according to an embodiment of the present disclosure. The embodiment of the DCI triggering aperiodic PUCCH 3300 shown in fig. 33 is for illustration only. One or more of the components shown in fig. 33 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

Fig. 33 shows that DCI in the same subframe triggers aperiodic PUCCH. For aperiodic PUCCH reporting, both short and long PUCCH may be used. When a long PUCCH is used, coverage may be improved.

Fig. 34 shows an example DL DCI trigger aperiodic PUCCH 3400 according to an embodiment of the present disclosure. The embodiment of the DL DCI trigger aperiodic PUCCH 3400 shown in fig. 34 is for illustration only. One or more of the components shown in fig. 34 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, DCI triggering PUCCH aperiodic reporting with DL DCI is shown in fig. 34.

Fig. 35 shows an example UL DCI trigger aperiodic PUCCH and PUSCH 3500 in accordance with embodiments of the present disclosure. The embodiment of UL DCI triggering aperiodic PUCCH and PUSCH 3500 shown in fig. 35 is for illustration only. One or more of the components shown in fig. 35 may be implemented in the form of dedicated circuitry configured to perform the indicated functions, or one or more of these components may 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.

In one embodiment, DCI triggered PUCCH aperiodic reporting is through UL DCI, where PUCCH and PUSCH are triggered by a single UL DCI and multiplexed in different resources through TDM or FDM or other means. For example, PUCCH and PUSCH are triggered together by UL DCI to be transmitted in different slots, as shown in fig. 35. It is beneficial when the gNB needs to report PUCCH immediately and there are not enough resources for PUSCH transmission in the same slot as UL DCI. Another benefit is that if PUSCH is done in the following slot instead of the same slot as UL DCI, the UE may have more time to process PUSCH, but the gNB needs to report UCI immediately in the same slot as UL DCI.

For multi-beam operation with aperiodic PUSCH and PUCCH reporting, the network needs to indicate the UE Tx beam to be used for these UL signals so that the network can apply the appropriate TRP Rx beam for UL signal reception. Considering the case where the UE beam correspondence relationship holds, a UE tx beam for both aperiodic PUCCH and PUSCH can be implicitly derived from a DL Rx beam. However, when the UE beam correspondence is not established, it is explicitly indicated that the UE tx beams of the aperiodic PUCCH and PUSCH are either semi-static, dynamic, or both. More specifically, in case of aperiodic PUSCH reporting, the UE Tx beam may be dynamically indicated in UL DCI signaling. On the other hand, in case of aperiodic PUCCH reporting, the UE Tx beam may be semi-statically or dynamically configured, or both.

When configured or served DL BPLs are to be reported in an aperiodic BSI report, the configured or served BPLs may be dynamically indicated or derived from semi-statically configured resources. For example, PUCCH resource pools may be semi-statically configured for every DL BPL, while a selected one of the PUCCH resources from the pool is dynamically indicated in the DCI to implicitly indicate the DL BPL to be reported in the aperiodic BSI report. Likewise, when an entire BSI report is to be reported, the request for the entire BSI report may be dynamically indicated.

For aperiodic PUCCH resource allocation, a pool of PUCCH resources that can be shared by multiple users may be semi-statically configured, while one PUCCH resource selected from the pool is dynamically indicated in DCI. One benefit is that this approach can more efficiently utilize uplink resources.

In one embodiment, DCI indication for aperiodic (short or long) PUCCH BSI is provided. In one example of alternative 1, when a PUCCH Tx beam is configured in PUCCH resources, 1 bit is used to trigger BPL BSI reporting on semi-statically configured PUCCH resources (PUCCH Tx beam is also semi-statically configured).

In one example of alternative 2, when a PUCCH Tx beam is not configured in PUCCH resources, (1 bit for triggering BPL BSI reporting on semi-statically configured PUCCH resources) + (x bit for indicating PUCCH beam).

In one example of alternative 3, when a PUCCH Tx beam is configured in a PUCCH resource, X bits are used to trigger on a PUCCH resource selected from a pool of semi-statically configured PUCCH resources.

In one example of alternative 4, when a PUCCH Tx beam is not configured in a PUCCH resource, X bits are used to trigger + (X bits are used to indicate a PUCCH beam) on a PUCCH resource selected from a pool of semi-statically configured PUCCH resources. In such an example, the following applies to all alternatives described above to indicate the BPL of the DL service or the selected BPL: an additional Y bit indicating the DL selected BPL; 0 bit if a BPL BSI of service is reported; and 0 bit if the indicated PUCCH resource is associated with the selected DL BPL. In such an example, the following applies to the entire BSI request indicating a long PUCCH: the 1 bit indicates the entire BSI request.

In one embodiment, DCI indication for BSI of aperiodic (PUSCH) is provided. In such an embodiment, 1 bit for triggering the BPL BSI report is provided. In such embodiments, the following applies to the BPL indicating the DL service or the selected BPL: an additional Y bit to indicate the DL selected BPL; or 0 bit if the service's BPLBSI is reported. In such embodiments, the following applies to indicate an entire BSI request: the 1 bit indicates the entire BSI request.

Although the present disclosure has been described with an exemplary embodiment, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to embrace such alterations and modifications as fall within the scope of the appended claims.

None of the description in this application should be read as implying that any particular element, step, or function is an essential element which must be included in the claim scope. The scope of patented subject matter is defined only by the claims.