Enhancements for synchronization, random access and HARQ operations in non-terrestrial networks

By disabling HARQ feedback in NTN and adopting an enhanced PRACH preamble format, the downlink synchronization process is optimized, and the challenges of downlink synchronization and HARQ management in NTN are solved, improving the reliability and coverage of data transmission.

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

Patent Information

Application Number
CN202080052505.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-07-10
Filing Date
2020-07-24
Publication Date
2024-11-15
Estimated Expiration
2040-07-24

AI Technical Summary

Technical Problem

Downlink synchronization and hybrid automatic retransmission request (HARQ) management challenges exist in non-terrestrial networks (NTNs), especially performance degradation due to large propagation delays and Doppler shifts, as well as PRACH preamble format Problem of insufficient coverage.

Method used

By implementing disable management of HARQ feedback in user equipment (UE) and base station (BS), using enhanced PRACH preamble format, and optimizing SS/PBCH block design and CORESET#0 configuration during downlink synchronization, to Improve synchronization performance.

Benefits of technology

Effectively manage HARQ transmission, enhance downlink synchronization performance, adapt to large propagation delays and Doppler shifts in NTN, ensuring wider coverage and higher data rates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114128185B_ABST
    Figure CN114128185B_ABST
Patent Text Reader

Abstract

A user equipment (UE), a base station, and a method for managing hybrid automatic repeat request (HARQ) feedback for downlink synchronization. The UE includes: at least one transceiver configured to receive downlink control information (DCI) in a physical downlink control channel (PDCCH); and at least one processor operably connected to the at least one transceiver. The at least one processor is configured to: determine whether to disable hybrid automatic repeat request (HARQ) feedback based on a first field in the DCI; and if HARQ feedback is disabled, determine that a second field in the DCI is one of a reserved field or a zero-bit width field based on a DCI format.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a quasi-fifth generation (5G) or 5G communication system that will provide support for higher data rates than fourth generation (4G) communication systems such as long term evolution (LTE). More specifically, embodiments of the present disclosure relate to non-terrestrial networks. Even more specifically, embodiments of the present disclosure relate to downlink synchronization, HARQ transmission management, and enhanced PRACH preamble formats. Background Art

[0002] Wireless communication has become one of the most successful innovations in recent history. Recently, the number of subscribers to wireless communication services has exceeded five billion and continues to grow rapidly. Due to the increasing popularity of smart phones and other mobile data devices (such as tablet computers, "notebook" computers, netbooks, e-book readers, and machine-type devices) among consumers and business people, the demand for wireless data services is growing rapidly. In order to meet the high growth of mobile data services and support new applications and deployments, it is crucial to improve radio interface efficiency and coverage.

[0003] In order to meet the increasing demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also called "super 4G networks" or "post-LTE systems."

[0004] 5G communication systems are considered to be implemented at higher frequency (millimeter wave) bands (e.g., 60 GHz band) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology in 5G communication systems are discussed.

[0005] Furthermore, in the 5G communication system, development of system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communications, coordinated multipoint (CoMP), receiving-end interference cancellation, etc. is being conducted. In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) have been developed, as well as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies.

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

[0007] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine to machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs) as the above-mentioned big data processing technology can also be regarded as an example of the fusion between 5G technology and IoT technology. Summary of the invention

[0008] [Technical issues]

[0009] Embodiments of the present disclosure include a user equipment (UE), a base station (BS), and a method for managing hybrid automatic repeat request transmission in a wireless communication system.

[0010] [Technical solution]

[0011] One embodiment relates to a UE, comprising: at least one transceiver configured to receive downlink control information (DCI) in a physical downlink control channel (PDCCH); and at least one processor operably connected to the at least one transceiver. The at least one processor is configured to: determine whether to disable hybrid automatic repeat request (HARQ) feedback based on a first field in the DCI; and if HARQ feedback is disabled, determine that a second field in the DCI is one of a reserved field or a zero-bit width field based on a DCI format.

[0012] Another embodiment relates to a BS, the BS including a transceiver configured to transmit downlink control information (DCI) in a physical downlink control channel (PDCCH). The BS also includes a processor operably connected to the transceiver, the processor configured to determine whether to disable hybrid automatic repeat request (HARQ) feedback. The processor is also configured to generate a DCI having a first field indicating whether HARQ feedback is disabled. The DCI includes a second field, and if the first field indicates that HARQ feedback is disabled, the second field can be determined to be one of a reserved field or a zero-bit width field based on the DCI format.

[0013] Yet another embodiment relates to a method comprising the steps of receiving downlink control information (DCI) in a physical downlink control channel (PDCCH); determining whether to disable hybrid automatic repeat request (HARQ) feedback based on a first field in the DCI; and if HARQ feedback is disabled, determining, based on a DCI format, that a second field in the DCI is one of a reserved field or a zero-bit-width field.

[0014] Other technical features can be easily understood by those skilled in the art according to the attached drawings, descriptions and claims.

[0015] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document. The term "connection" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives cover both direct and indirect communication. The terms "include" and "comprise" and their derivatives are meant to include without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives are meant to include, include within, interconnect with, include, include within, connect to, or connect with, connect to, or connect with, communicate with, collaborate with, interweave, parallel, approach, be bound to, or bind with, have, have the characteristic of, have... with, etc. The term "controller" refers to any device, system or part thereof that controls at least one operation. Such a controller can be implemented with hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether local or remote. When the phrase "at least one of" is used with a list of items, it means that different combinations of one or more of the listed items may be used, and only one item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. Similarly, the term "group" means one or more. Thus, a group of items can be a single item or a collection of two or more items.

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

[0017] Throughout this patent document, definitions for certain other words and phrases are provided. 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.

[0018] [Beneficial Effects of the Invention]

[0019] According to the embodiments of the present disclosure, a UE or a base station can effectively manage hybrid automatic repeat request transmission. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1A and Figure 1B An exemplary wireless communication network according to various embodiments of the present disclosure is shown;

[0022] Figure 2 An exemplary base station (BS) in a wireless communication network according to various embodiments of the present disclosure is shown;

[0023] Figure 3 An exemplary user equipment (UE) in a wireless communication network according to various embodiments of the present disclosure is shown;

[0024] Figure 4A and Figure 4B illustrates exemplary transmit and receive paths according to various embodiments of the present disclosure;

[0025] Figure 5 An exemplary transmitter according to various embodiments of the present disclosure is shown;

[0026] Figure 6 An exemplary receiver according to various embodiments of the present disclosure is shown;

[0027] Figure 7 SS / PBCH block composition for NR Rel-15 according to various embodiments of the present disclosure is shown;

[0028] Figure 8 SS / PBCH block patterns in the time domain for NR Rel-15 according to various embodiments of the present disclosure are shown;

[0029] Fig. 9 SS / PBCH block locations within a half-frame for NR Rel-15 according to various embodiments of the present disclosure are shown;

[0030] Fig.10 shows beam footprints generated by satellites according to various embodiments of the present disclosure;

[0031] Fig.11 shows frequency repetition of SSB according to various embodiments of the present disclosure;

[0032] Fig.12 A PRACH format with a long sequence according to various embodiments of the present disclosure is shown;

[0033] Fig.13 A PRACH format with a short sequence according to various embodiments of the present disclosure is shown;

[0034] Fig.14A and Fig. 14B An exemplary PRACH format according to various embodiments of the present disclosure is shown;

[0035] Fig.15A and Fig. 15B Other exemplary PRACH formats according to various embodiments of the present disclosure are shown;

[0036] Fig.16 Other exemplary PRACH formats according to various embodiments of the present disclosure are shown;

[0037] Fig.17 Other exemplary PRACH formats according to various embodiments of the present disclosure are shown; and

[0038] Fig.18 A flow chart of a process for managing HARQ transmissions in a wireless network according to various embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0039] The accompanying drawings and various embodiments used to describe the principles of the present disclosure herein are merely exemplary illustrations and should not be interpreted in any way as limiting the scope of the present disclosure. In addition, those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged wireless communication system.

[0040] The following documents are hereby incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 v15.5.0 and v15.6.0, “NR; Physical Channels and Modulation”, hereinafter referred to as “REF 1”; 3GPP TS 38.212 v15.5.0 and v15.6.0, “NR; Multiplexing and Channel Coding”, hereinafter referred to as “REF 2”; 3GPP TS 38.213 v15.5.0 and v15.6.0, “NR; Physical Layer Procedures for Control”, hereinafter referred to as “REF 3”; 3GPP TS 38.214 v15.5.0 and v15.6.0, “NR; Physical Layer Procedures for Data”, hereinafter referred to as “REF 4”; 3GPP TS 38.331 v15.5.0 and v15.6.0, “NR; Radio Resource Control (RRC) Protocol Specification”, hereinafter referred to as “REF 5”. New Radio (NR) supports synchronization via a synchronization signal sent on the downlink. Compared to Long Term Evolution (LTE), NR supports a wider range of carrier frequencies and more flexible numerologies. This concept was later introduced in Figures 7 to 9 The novel aspects of the present disclosure recognize that for non-terrestrial networks (NTNs), there is typically a long delay spread between the transmitter and the receiver (e.g., from tens to hundreds of ms for different development scenarios), as well as significant Doppler shifts due to the high mobility of satellites in certain development scenarios. These aspects affect downlink synchronization performance. The present disclosure proposes enhancements to address downlink synchronization issues in NTNs.

[0041] NR Rel-15 also supports multiple physical random access channel (PRACH) preamble formats. Formats 0, 1, 2, and 3 are used for long preamble lengths of 839, and subcarrier spacing (SCS) of 1.25kHz or 5kHz. Formats A1, A2, A3, B1, B2, B3, B4, C0, and C2 are used for short preamble lengths of 139, and SCS of 15kHz, 30kHz, 60kHz, and 120kHz. An illustration of the PRACH preamble format with long sequences is shown in Fig.12 and a diagram of the PRACH preamble format with a short sequence is shown in Fig.13 Shown in.

[0042] For new NR use cases beyond Rel-15, NTN considers networks or network segments using RF resources on satellite or UAS platforms, such as Figure 1BAs shown. For NTN, the size of the coverage area of ​​the transmit beam generated by the satellite is much larger than the terrestrial cell in NR Rel-15, so that the coverage of the PRACH preamble supported in Rel-15 may not be sufficient. Therefore, the novel aspects of the present disclosure recognize the need for an enhanced PRACH preamble format to support large cell sizes. As will be discussed in more detail herein, the enhancements may be directed to the sequence length used for the PRACH preamble, the SCS supporting the PRACH preamble, and the PRACH preamble composition. Two groups of PRACH preamble formats are described in the present disclosure. The first group of PRACH preamble formats is based on an SCS adjusted from 1.25kHz, and the second group of PRACH preamble formats is based on an SCS adjusted from 15kHz.

[0043] NR also supports hybrid automatic repeat request (HARQ) in both downlink and uplink. More precisely, both downlink and uplink support asynchronous HARQ, where multiple HARQ processes run in any order. In order to track each HARQ process, both the transmitter and the receiver in the HARQ process should know the exact number of HARQ processes in order to accurately receive the transmission or retransmission. At the same time, unlike LTE, the timing between data transmission and HARQ response in NR is flexible. The radio resource control (RRC) message configures a table of possible timing offsets between data transmission and HARQ response, and the downlink control information (DCI) further indicates which value in the configuration table to use between the scheduled data transmission and the corresponding HARQ response.

[0044] For NTN, there is usually a large propagation delay between the transmitter and the receiver, and the specific maximum round trip delay (RTD) depends on the real-time scenario. Table 7 shows exemplary maximum RTDs for some typical NTN scenarios. It can be seen that for geosynchronous equatorial orbit (GEO) satellites, the maximum RTD may exceed 500ms, while for low earth orbit (LEO) satellites, the maximum RTD may be as high as 40ms for extreme cases, which are much larger than those considered in terrestrial networks.

[0045] The large propagation delay in NTN challenges the effectiveness of HARQ, and also challenges the implementation of HARQ, while significantly increasing the buffer size of both the transmitter and the receiver. Therefore, the novel aspects of the present disclosure also recognize that, at least for some NTN scenarios, it is necessary to disable HARQ, and the present disclosure includes details of methods of disabling HARQ, and the corresponding impact when HARQ is disabled.

[0046] Figure 1A An exemplary wireless communication network 100a is shown in accordance with various embodiments of the present disclosure. Figure 1AThe illustrated embodiment of the wireless network 100a is for illustration only. Other embodiments of the wireless network 100a may be used without departing from the scope of the present disclosure.

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

[0048] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipments (UEs) within coverage area 120 of gNB 102. The first plurality of UEs include: UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WIFI hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of gNB 103. The second plurality of UEs include UE 115 and UE 116.

[0049] Depending on the type of network, the term "base station" may refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), a gNB, a macro cell, a femto cell, a WIFI access point (AP), or other wirelessly capable device. A base station may provide wireless access according to one or more wireless communication protocols, such as 5G3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. In addition, depending on the type of network, other well-known terms may be used instead of "user equipment" or "UE", such as "mobile station", "subscriber station", "remote terminal", "wireless terminal", or "user device". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses a gNB, regardless of whether the UE is a mobile device (such as a mobile phone or a smart phone) or is generally considered to be a fixed device (such as a desktop computer or a vending machine).

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

[0051] As described in more detail below, the wireless network 100a can be a 5G communication system in which a UE such as UE 116 can communicate with a BS such as BS 102 and / or network components for facilitating downlink synchronization, managing HARQ transmissions, and / or implementing enhanced PRACH preamble code formats in a non-terrestrial network.

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

[0053] Figure 1B Another exemplary wireless communication network according to various embodiments of the present disclosure is shown. The non-terrestrial network 100b may be a standalone network or part of a network using RF resources on a satellite or unmanned aerial system (UAS) platform.

[0054] NTN 100b shows a typical scenario of an NTN providing access to user equipment 156. NTN 100b typically includes one or more satellite gateways 151 connecting NTN 100b to a public data network. NTN 100b also includes GEO satellites 154 fed by one or more satellite gateways 151 deployed on a satellite target coverage area (e.g., a regional or even continental coverage area). It can be assumed that a UE in a cell (such as UE 156) is served by only one satellite gateway. Non-GEO satellites can be served continuously by one or more satellite gateways at a time, and the system ensures continuity of service and feeder links between continuously served satellite gateways, which have sufficient duration for mobility anchoring and switching.

[0055] NTN 100b may also include a UAS platform. The satellite 154 or UAS platform may implement a transparent payload or a regenerative payload with onboard processing. The transparent payload includes RF filtering, frequency conversion, and amplification so that the waveform signal repeated by the payload is unchanged. The regenerative payload includes RF filtering, frequency conversion, and amplification as well as demodulation / decoding, switching and / or routing, coding / modulation, which is effectively equivalent to having all or part of the base station functionality (e.g., gNB) on the satellite 154 or UAS platform.

[0056] A satellite 154 or UAS platform typically generates multiple beams over a given service area defined by its field of view, such as Fig.10 The beam footprint is generally elliptical. The field of view of the satellite 154 or UAS platform depends on the onboard antenna pattern and the minimum elevation angle.

[0057] Satellite 154 may be connected to one or more satellite gateways 151 via a feeder link or radio link 152. Satellite 154 may have a service link or radio link 153 with UE 156. Satellite 154 may also have an optional inter-satellite link (ISL) 155 for implementing a satellite constellation. This would require a regenerative payload on the satellite. ISL 155 may operate in RF frequencies or optical bands.

[0058] As described in more detail below, the NTN 100b may be used to facilitate downlink synchronization, manage HARQ transmissions, and / or implement enhanced PRACH preamble formats.

[0059] Figure 2 An exemplary base station (BS) according to various embodiments of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustration only, and gNB 101 and gNB 103 of FIG. 1 may have the same or similar configuration. However, gNBs have a variety of configurations, and Figure 2 The scope of the present disclosure is not limited to any particular implementation of the gNB. In addition, the BS may take the form of a satellite or UAS platform, such as Figure 1B shown.

[0060] like Figure 2 As shown, gNB 102 includes multiple antennas 280a to 280n, multiple RF transceivers 282a to 282n, transmit (TX) processing circuitry 284, and receive (RX) processing circuitry 286. gNB 102 also includes a controller / processor 288, a memory 290, and a backhaul or network interface 292.

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

[0062] The TX processing circuit 284 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 288. The TX processing circuit 284 encodes, multiplexes, and / or digitizes the output baseband data to generate processed baseband or IF signals. The RF transceivers 282a to 282n receive the output processed baseband or IF signals from the TX processing circuit 284 and up-convert the baseband or IF signals to RF signals that are transmitted via the antennas 280a to 280n.

[0063] The controller / processor 288 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 288 may control the RF transceivers 282a to 282n, the RX processing circuit 286, and the TX processing circuit 284 to receive forward channel signals and transmit reverse channel signals in accordance with well-known principles. The controller / processor 288 may also support other functions, such as more advanced wireless communication functions. For example, the controller / processor 288 may support beamforming or directional routing operations, weighting the output signals from multiple antennas 280a to 280n differently to effectively steer the output signals in a desired direction. The controller / processor 288 may support any of a wide variety of other functions in the gNB 102. In some embodiments, the controller / processor 288 includes at least one microprocessor or microcontroller.

[0064] Controller / processor 288 is also capable of executing programs and other processes, such as a basic OS, that reside in memory 290. Controller / processor 288 may move data into or out of memory 290 as required for the processing being executed.

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

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

[0067] As described in more detail below, BS 102 may transmit information over the network to a UE, such as UE 116 in FIG. 1, for facilitating downlink synchronization, managing HARQ transmissions, and / or implementing an enhanced PRACH preamble format.

[0068] Although Figure 2 An example of a gNB 102 is shown, but the Figure 2 For example, gNB 102 may include any number of Figure 2 As a specific example, the access point can include multiple interfaces 292, and the controller / processor 288 can support routing functions for routing data between different network addresses. As another specific example, although shown as including an example of a single TX processing circuit 284 and an example of a single RX processing circuit 220, the gNB 102 can include multiple examples such as one TX processing circuit 284 and one RX processing circuit 220 per RF transceiver. In addition, Figure 2 Various components in may be combined, further subdivided, or omitted, and other components may be added according to specific needs.

[0069] Figure 3 An exemplary user equipment (UE) according to various embodiments of the present disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustration only, and UE 111 to UE 115 of FIG. 1 may have the same or similar configuration. However, UEs have a variety of configurations, and Figure 3The scope of the present disclosure is not limited to any particular implementation of the UE.

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

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

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

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

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

[0075] Main processor 340 is also coupled to keypad 350 and display unit 355. An operator of UE 116 may use keypad 350 to enter data into UE 116. Display 355 may be a liquid crystal display or other display capable of presenting text (such as from a website) and / or at least limited graphics.

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

[0077] As described in more detail below, UE 116 may communicate with a network such as Figure 2 BS communications with BS 102 in the system to facilitate downlink synchronization, manage HARQ transmissions, and / or implement enhanced PRACH preamble formats.

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

[0079] Figure 4A and Figure 4B Exemplary wireless transmit and receive paths according to various embodiments of the present disclosure are shown. Figure 4A and Figure 4BIn the example, for downlink communication, the transmit path circuit may be implemented in a base station (gNB) 102 or a relay station, and the receive path circuit may be implemented in a user equipment (e.g., user equipment 116 of FIG. 1 ). In other examples, for uplink communication, the receive path circuit 450 may be implemented in a base station (e.g., gNB 102 of FIG. 1 ) or a relay station, and the transmit path circuit may be implemented in a user equipment (e.g., user equipment 116 of FIG. 1 ).

[0080] The transmit path 400 includes a channel coding and modulation block 405, a serial to parallel (S to P) block 410, an inverse fast Fourier transform (IFFT) block of size N 415, a parallel to serial (P to S) block 420, an add cyclic prefix block 425, and an upconverter (UC) 430. The receive path 450 includes a downconverter (DC) 455, a remove cyclic prefix block 460, a serial to parallel (S to P) block 465, a fast Fourier transform (FFT) block of size N 470, a parallel to serial (P to S) block 475, and a channel decoding and demodulation block 480.

[0081] At least some components of the transmit path 400 and the receive path 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 block and IFFT block described in the present disclosure may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation.

[0082] In addition, although the present disclosure is directed to embodiments for implementing fast Fourier transform and inverse fast Fourier transform, this is merely exemplary and cannot be construed as limiting the scope of the present disclosure. It will be appreciated that in alternative embodiments of the present disclosure, the fast Fourier transform function and the inverse fast Fourier transform function can be easily replaced by a discrete Fourier transform (DFT) function and an inverse discrete Fourier transform (IDFT) function, respectively. It will be appreciated that for DFT and IDFT functions, the value of the N variable can be any integer (i.e., 1, 4, 3, 4, etc.), while for FFT and IFFT functions, the value of the N variable can be any integer as a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).

[0083] In the following example, the transmit path 400 is implemented in the BS and the receive path is implemented in the UE. In the transmit path 400, the 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 frequency domain modulation symbol sequence. The serial to parallel block 410 converts (i.e., demultiplexes) the serial modulation symbols into parallel data to produce N parallel symbol strings, where N is the IFFT / FFT size used in the BS 102 and the UE 116. Then, the size N IFFT block 415 performs an IFFT operation on the N parallel symbol strings to produce a time domain output signal. The parallel to serial block 420 converts (i.e., multiplexes) the parallel time domain output symbols from the size N IFFT block 415 to produce a serial time domain signal. Then, the add cyclic prefix block 425 inserts a cyclic prefix into the time domain signal. Finally, upconverter 430 modulates (ie, upconverts) the output of add cyclic prefix block 425 to RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before being converted to RF frequency.

[0084] The transmitted RF signal may reach the UE after passing through the wireless channel, and the reverse operation of the operation at the gNB is performed. The down converter 455 downconverts the received signal to the baseband frequency, and the cyclic prefix removal block 460 removes the cyclic prefix to generate a serial time domain baseband signal. The serial to parallel block 465 converts the time domain baseband signal into a parallel time domain signal. Then, the FFT block 470 of size N performs an FFT algorithm to generate N parallel frequency domain signals. The parallel to serial block 475 converts the parallel frequency domain signals into a modulated data symbol sequence. The channel decoding and demodulation block 480 demodulates and decodes the modulation symbols to recover the original input data stream.

[0085] Each of gNB 101 to gNB 103 may implement a transmit path 400 similar to transmitting in the downlink to user equipment 111 to 116, and may implement a receive path 450 similar to receiving in the uplink from user equipment 111 to 116. Similarly, each of user equipment 111 to 116 may implement a transmit path 400 corresponding to the architecture for transmitting in the uplink to gNB 101 to gNB 103, and may implement a receive path 450 corresponding to the architecture for receiving in the downlink from gNB 101 to gNB 103.

[0086] As described in more detail below, the transmit path 400 and the receive path 450 may be implemented in a UE such as Figure 3 UE 116 in the Figure 2The BS 102 is implemented in the BS 102 to facilitate downlink synchronization, manage HARQ transmissions and / or implement an enhanced PRACH preamble format.

[0087] Although Figure 4A and Figure 4B An example of a wireless transmit and receive path is shown, but the Figure 4A and Figure 4B Make various changes. For example, Figure 4A and Figure 4B The various components in the can be combined, further subdivided or omitted, and other components can be added according to specific needs. Figure 4A and Figure 4B It is intended to illustrate examples of the types of transmit and receive paths that may be used in a wireless network.Any other suitable architecture may be used to support wireless communications in a wireless network.

[0088] Figure 5 An exemplary transmitter according to various embodiments of the present disclosure is shown. The transmitter 500 can be implemented in an electronic device (such as gNB 101 or UE 111) that communicates via a wireless communication network.

[0089] Information bits 510, such as DCI bits or data bits, are encoded by encoder 520 and then rate matched to the allocated time / frequency resources by rate matcher 530. The output from rate matcher 530 is modulated by modulator 540. The modulated and coded symbols 545 and DMRS or CSI-RS 550 are mapped by SC mapping unit 560 based on the SC selected by BW selector unit 565. An inverse fast Fourier transform (IFFT) is performed by IFFT unit 570, and a cyclic prefix (CP) is added by CP insertion unit 580. The resulting signal is filtered by filter 590 to generate a filtered signal 595, which is transmitted by a radio frequency (RF) unit (not shown).

[0090] Figure 6 An exemplary receiver according to various embodiments of the present disclosure is shown. The receiver 600 may be implemented in an electronic device (such as gNB 101 or UE 111) that communicates via a wireless communication network.

[0091] The received signal 610 is filtered by a filter 620 and then passes through a CP removal unit 630 which removes a cyclic prefix. An IFFT unit 640 applies a Fast Fourier Transform (FFT) and provides the resulting signal to an SC demapping unit 650. The SC demapping unit 650 demaps the SC selected by the BW selector unit 655. The received symbols are demodulated by a channel estimator and demodulator unit 660. A rate dematcher 670 recovers the rate matching, and a decoder 280 decodes the resulting bits to provide information bits 690.

[0092] Each of gNB 101 to gNB 103 may implement a transmit path 400 for transmitting in the downlink to UE 111 to UE 116, and may implement a receiver 600 for receiving in the uplink from UE 111 to UE 116. Similarly, each of UE 111 to UE 116 may implement a transmit path 400 for transmitting in the uplink to gNB 101 to gNB 103, and may implement a receiver 600 for receiving in the downlink from gNB 101 to gNB 103.

[0093] As described in more detail below, transmitter 500 and receiver 600 may be included in a UE and a BS, such as UE 116 and BS 102, for facilitating downlink synchronization, managing HARQ transmissions, and / or implementing enhanced PRACH preamble formats.

[0094] Figure 5 and Figure 6 Each of the components in may be implemented using hardware only or a combination of hardware and software / firmware. As a specific example, Figure 5 and Figure 6 At least some of the components in can be implemented with software, while other components can be implemented by configurable hardware, or a combination of software and configurable hardware. For example, IFFT block 570 can be implemented as a configurable software algorithm.

[0095] Furthermore, although described as using IFFT, this is merely an exemplary illustration and should not be construed as limiting the scope of the present disclosure. Other types of transforms may be used, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions.

[0096] although Figure 5 and Figure 6 Examples of wireless transmitters and receivers are shown, but various changes can be made. For example, Figure 5 and Figure 6 The various components in the can be combined, further subdivided or omitted, and other components can be added according to specific needs. Figure 5 and Figure 6 It is intended to illustrate examples of the types of transmitters and receivers that may be used in a wireless network.Any other suitable architecture may be used to support wireless communications in a wireless network.

[0097] As described below, downlink synchronization in NTN can be achieved by enhancing SS / PBCH block design, configuration of CORESET#0 and / or downlink synchronization procedures.

[0098] Figure 7 The SS / PBCH block composition for NR Rel-15 according to various embodiments of the present disclosure is shown. NR Rel-15 supports multiple synchronization signal and physical broadcast channel blocks (SS / PBCH blocks or SSBs) on each carrier frequency range.

[0099] Each SS / PBCH block 700 has four consecutive orthogonal frequency division multiplexing (OFDM) symbols. The first symbol is mapped for the primary synchronization signal (PSS), the second and fourth symbols are mapped for the PBCH, and the third symbol is mapped for the secondary synchronization signal (SSS) and the PBCH. The same SS / PBCH block composition applies to all carrier frequency ranges supported in NR, covering from 0 GHz to 52.6 GHz. The transmission bandwidth of PSS and SSS (e.g., 12 resource blocks (RBs)) is smaller than the transmission bandwidth of the entire SS / PBCH block (e.g., 20 RBs). In each RB mapped for PBCH, 3 of the 12 resource elements (REs) are mapped for the demodulation reference signal (DMRS) of PBCH, and these 3 REs are evenly distributed in the PRB, and the starting position of the first RE is based on the cell identity (ID). In addition, NR Rel-15 supports one or two subcarrier spacings (SCS) for SS / PBCH blocks, and for a given frequency band, PSS, SSS and PBCH (including its DMRS) use the same SCS. For a carrier frequency range of 0 GHz to 6 GHz, 15 kHz and / or 30 kHz may be used for the SCS of the SS / PBCH block. For a carrier frequency range of 6 GHz to 52.6 GHz, 120 kHz and / or 240 kHz may be used for the SCS of the SS / PBCH block.

[0100] In some embodiments, the sequence for constructing the PSS is based on an M-sequence with a cyclic shift to represent the cell ID information carried by the PSS, and the sequence for constructing the SSS is based on a Gold-sequence (an exclusive OR of two M-sequences). Each M-sequence for constructing the Gold-sequence performs a cyclic shift to represent the cell ID information carried by the SSS.

[0101] Figure 8SS / PBCH block patterns in the time domain for NR Rel-15 according to various embodiments of the present disclosure are shown.

[0102] In NR Rel-15, SS / PBCH blocks can be transmitted in a beam scanning manner until the network is realized, and multiple candidate positions for transmitting SS / PBCH blocks are predefined in half-frame units. Figure 8 It can be seen that the mapping mode 800a of the SS / PBCH block to 1 time slot is relative to 15kHz as the reference SCS of the frequency range 1 (FR1) from 410MHz to 7.125GHz, and the mapping mode 800b is relative to 60kHz as the reference SCS of the frequency range 2 (FR2) from 24.25GHz to 52.6GHz. Two mapping modes of 30kHz SCS for SS / PBCH blocks are designed. Mode 1 is used for non-LTE-NR coexistence bands, and mode 2 is used for LTE-NR coexistence bands.

[0103] Fig. 9 SS / PBCH block locations within a half-frame for NR Rel-15 according to various embodiments of the present disclosure are shown.

[0104] The maximum number of SS / PBCH blocks in a period, denoted as L_SSB, is determined based on the carrier frequency range. For a carrier frequency range of 0 GHz to 3 GHz, L_SSB is 4; for a carrier frequency range of 3 GHz to 6 GHz, L_SSB is 8; for a carrier frequency range of 6 GHz to 52.6 GHz, L_SSB is 64. Fig. 9 9 shows the determination of the time slots within the half-frame unit 900 containing the candidate positions of the SS / PBCH blocks for each combination of SSBSCS and L_SSB.

[0105] In initial cell selection, the user equipment (UE) assumes a default SSB burst set period of 20ms and to detect non-standalone NR cells, the network provides the UE with one SSB burst set period per frequency carrier and (if possible) information for deriving measurement timing / duration.

[0106] Due to the delay spread between transmitter and receiver in NTN, NR enhancements are proposed to address the downlink synchronization problem in NTN. The downlink synchronization aspects include SS / PBCH block design, CORESET#0 configuration, and enhancements to the downlink (DL) synchronization procedure.

[0107] In NTN, a satellite or UAS platform typically generates multiple beams within a given service area defined by its field of view. The coverage area of ​​the beam is typically elliptical and depends on the onboard antenna pattern and the minimum elevation angle. Fig.10A diagram of the coverage area of ​​the beam is shown in .

[0108] Fig.10 The beam coverage areas generated by satellites according to various embodiments of the present disclosure are shown. In particular, TNT 1000 includes satellites 154 that generate beam coverage areas 1002, each beam coverage area corresponding to a cell. In one aspect of this embodiment, there can be frequency reuse between different coverage areas, such as coverage areas with sufficiently long distances.

[0109] In one approach, a UE in a given coverage area may assume that at most one SS / PBCH block is sent during a period in which the SS / PBCH block is sent. In one example, if there is no frequency reuse between different coverage areas, at most one SS / PBCH block is sent on each frequency layer corresponding to the synchronization raster. In another example, if there is frequency reuse between different coverage areas, multiple SS / PBCH blocks may be sent on each frequency layer corresponding to the synchronization raster, but a UE in a given coverage area may assume at most one of them.

[0110] In another method, UEs in a given coverage area assume that at most one or more SS / PBCH blocks can be sent within a period of SS / PBCH block transmission, and UEs in a given coverage area also assume that the SS / PBCH blocks sent on a given frequency layer are quasi-colocated (QCLed). On the one hand, the number of quasi-colocated SS / PBCH blocks within a period can be predefined in the specification, and if any of the quasi-colocated SS / PBCH blocks is detected, the UE assumes that all quasi-colocated SS / PBCH blocks are sent. On the other hand, the quasi-colocated SS / PBCH blocks actually sent within a period are indicated by the remaining minimum system information (RMSI) content (e.g., a bitmap).

[0111] In another embodiment, the UE assumes that at least one coverage area corresponds to a cell.

[0112] In one method, UEs in a given coverage area are assumed to transmit at most one SS / PBCH block within a period of SS / PBCH block transmission.

[0113] In another method, UEs in a given coverage area assume that at most one or more SS / PBCH blocks can be sent within a period in which the SS / PBCH blocks are sent, and UEs in a given coverage area also assume that the SS / PBCH blocks sent on a given frequency layer are quasi-colocated. On the one hand, the number of quasi-colocated SS / PBCH blocks within a period is predefined in the specification, and if any one of the quasi-colocated SS / PBCH blocks is detected, the UE assumes that all quasi-colocated SS / PBCH blocks are sent. On the other hand, the quasi-colocated SS / PBCH blocks actually sent within a period are indicated by RMSI content (e.g., a bitmap).

[0114] In one embodiment, the frequency band for operating NTN has a minimum carrier bandwidth of 30 MHz, which is 160 RBs for 15 kHz SCS or 78 RBs for 30 kHz SCS.

[0115] In one method, a 15kHz SCS for SS / PBCH blocks is supported on a frequency band with a minimum carrier bandwidth of 30MHz for operating NTN, and the channel center of the frequency band with a minimum carrier bandwidth of 30MHz for operating NTN can be varied with a small step size (e.g., 15kHz or 30kHz or 100kHz).

[0116] In one example of the present method, for a 15kHz SCS, CORESET#0 with a 24RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be 2RB.

[0117] In another example of the present method, for a 15kHz SCS, CORESET#0 with a 48RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be one of 0RB or 28RB.

[0118] In another example of the present method, for a 15kHz SCS, CORESET#0 with a 96RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and has overlapping bandwidth. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be one of 0RB, 38RB or 76RB.

[0119] In another example of the present method, for a 30kHz SCS, CORESET#0 with a 24RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be one of 0RB or 14RB.

[0120] In another example of the present method, for a 30kHz SCS, CORESET#0 with a 48RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be one of 0RB, 19RB or 38RB.

[0121] In yet another method, a 30 kHz SCS for SS / PBCH blocks is supported on a frequency band with a minimum carrier bandwidth of 30 MHz for operating NTN, and the channel center of the frequency band with a minimum carrier bandwidth of 30 MHz for operating NTN can be varied with a small step size (e.g., 15 kHz or 30 kHz or 100 kHz).

[0122] In one example of the present method, for a 15kHz SCS, CORESET#0 with a 48RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and has overlapping bandwidths. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be one of 0RB or 8RB.

[0123] In another example of the present method, for a 15kHz SCS, CORESET#0 with a 96RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be one of 0RB or 56RB.

[0124] In another example of the present method, for a 30kHz SCS, CORESET#0 with a 24RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be one of 0RB or 4RB.

[0125] In another example of the present method, for a 30kHz SCS, CORESET#0 with a 48RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be configured to be one of 0RB or 28RB.

[0126] In yet another method, a 15kHz SCS for SS / PBCH blocks is supported on a frequency band with a minimum carrier bandwidth of 30MHz for operation of NTN, and the channel center of the frequency band with a minimum carrier bandwidth of 30MHz for operation of NTN is fixed. For this method, there may be a single synchronization grid entry within the minimum carrier bandwidth of 30MHz, and the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block may be fixed, if the multiplexing between CORESET#0 and the SS / PBCH block is performed in a manner that occurs at different time instances and the bandwidth overlaps, and if CORESET#0 and the SS / PBCH block are center-aligned in the frequency domain, the fixed frequency offset may be determined by the following formula:

[0127] F_offset=(BW_CORESET#0-BW_SSB*SCS_SSB / SCS_CORESET#0) / 2.

[0128] Alternatively, if CORESET#0 and SS / PBCH blocks are edge-aligned (highest RB) in the frequency domain, the fixed frequency offset can be determined by:

[0129] F_offset=BW_CORESET#0-BW_SSB*SCS_SSB / SCS_CORESET#0.

[0130] Alternatively, if CORESET#0 and SS / PBCH blocks are edge-aligned (lowest RB) in the frequency domain, the fixed frequency offset can be determined by:

[0131] F_offset=0, where BW_CORESET#0 is the bandwidth of CORESET#0, BW_SSB is the bandwidth of the SS / PBCH block, SCS_SSB is the SCS of the SS / PBCH block, and SCS_CORESET#0 is the SCS of CORESET#0.

[0132] In one example of the present method, for a 15kHz SCS, CORESET#0 with a 24RB bandwidth is supported and multiplexed with SS / PBCH blocks in a manner that appears in different time instances and has overlapping bandwidths. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 2RB (e.g., center aligned).

[0133] In another example of the present method, for 15kHz SCS, CORESET#0 with 24RB bandwidth is supported and multiplexed with SS / PBCH blocks in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 0RB or 4RB (e.g., edge-aligned).

[0134] In another example of the present method, for 15kHz SCS, CORESET#0 with 48RB bandwidth is supported and multiplexed with SS / PBCH blocks in a manner that appears in different time instances and the bandwidth overlaps. Then, for the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 14RB (e.g., center aligned).

[0135] In another example of the present method, for 15kHz SCS, CORESET#0 with a bandwidth of 48RB is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 0RB or 28RB (e.g., edge-aligned).

[0136] In another example of the present method, for a 15kHz SCS, CORESET#0 with a bandwidth of 96RB is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and has overlapping bandwidth. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 38RB (e.g., center aligned).

[0137] In another example of the present method, for 15kHz SCS, CORESET#0 with a bandwidth of 96RB is supported and multiplexed with SS / PBCH blocks in a manner that appears in different time instances and has overlapping bandwidth. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 0RB or 76RB (e.g., edge-aligned).

[0138] In another example of the present method, for a 15kHz SCS, CORESET#0 with a bandwidth of 144RB is supported and multiplexed with SS / PBCH blocks in a manner that appears in different time instances and has overlapping bandwidths. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 62RB (e.g., center aligned).

[0139] In another example of the present method, for a 15kHz SCS, CORESET#0 with a bandwidth of 144RB is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 0RB or 124RB (e.g., edge-aligned).

[0140] In another example of the present method, for a 30kHz SCS, CORESET#0 with a 24RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 7RB (e.g., center aligned).

[0141] In another example of the present method, for a 30kHz SCS, CORESET#0 with a 24RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and has overlapping bandwidth. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 0RB or 14RB (e.g., edge-aligned).

[0142] In another example of the present method, for a 30kHz SCS, CORESET#0 with a 48RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and has overlapping bandwidth. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 19RB (e.g., center aligned).

[0143] In another example of the present method, for a 30kHz SCS, CORESET#0 with a 48RB bandwidth is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and has overlapping bandwidth. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 0RB or 38RB (e.g., edge-aligned).

[0144] In another example of the present method, for a 30kHz SCS, CORESET#0 with a bandwidth of 72RB is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 31RB (e.g., center aligned).

[0145] In another example of the present method, for a 30kHz SCS, CORESET#0 with a bandwidth of 72RB is supported and multiplexed with the SS / PBCH block in a manner that appears in different time instances and the bandwidth overlaps. For the SCS of CORESET#0, the frequency offset between the lowest RB of CORESET#0 and the lowest RB of the SS / PBCH block can be fixed to 0RB or 62RB (e.g., edge-aligned).

[0146] The performance of downlink synchronization may be degraded due to Doppler shift, so the downlink synchronization process needs to be enhanced.

[0147] In one embodiment, the UE for NTN operation assumes that the SS / PBCH blocks within a period (e.g., 20ms for initial access) can be repeated in the time domain for coverage enhancement. The repetition is based on the QCL assumption, and the specific signal / channel (e.g., DMRS sequence of PBCH) can vary in the repeated SS / PBCH blocks.

[0148] In one method, the UE assumes that SS / PBCH blocks with SS / PBCH block indexes i and i+1 are quasi-colocated, where i is an even number. For example, two SS / PBCH blocks in the same time slot are quasi-colocated. In one aspect of the method, the UE assumes that quasi-colocated SS / PBCH blocks are all transmitted, or are not transmitted. In another aspect of the method, the UE assumes that a bitmap is used to indicate the SS / PBCH blocks actually transmitted, and the (i-1)th bit and the i-th bit take the same value (e.g., 0 or 1).

[0149] In another method, the UE assumes that the SS / PBCH blocks are quasi-colocated during the period in which the SS / PBCH blocks are transmitted. In one example, for NTN, the number of SS / PBCH blocks actually transmitted may be fixed, and it is assumed that all SS / PBCH blocks actually transmitted are quasi-colocated. In another example, the number of SS / PBCH blocks actually transmitted may be configurable, and it is assumed that all SS / PBCH blocks actually transmitted are quasi-colocated.

[0150] In yet another method, the UE assumes that SS / PBCH blocks are repeated based on its Global Navigation Satellite System (GNSS) capabilities. For example, if the UE does not have GNSS capabilities, the UE may assume SS / PBCH blocks within a repeatable period (e.g., 20 ms for initial access).

[0151] In another embodiment, the UE assumes at least one parameter set for SS / PBCH block detection during the initial access procedure, and if the supported parameter sets are greater than 1, the UE may need to blindly detect the parameter set of the SS / PBCH block.

[0152] In one approach, if the UE is able to distinguish the type of payload, such as whether transparent or regenerated, the UE may determine a single set of parameters for the SS / PBCH block upon initial access.

[0153] In yet another embodiment, the UE for NTN operation assumes that SS / PBCH blocks may be repeated in the frequency domain for coverage enhancement, where the repetition refers to a QCL assumption and specific signals / channels (eg, PSS / SSS) may vary in the repeated SS / PBCH blocks.

[0154] Fig.11An example of SS / PBCH block repetition in the frequency domain according to various embodiments of the present disclosure is shown.

[0155] In one aspect, the number of repeated SS / PBCH blocks in the frequency domain is fixed. For example, the UE assumes that the set of SS / PBCH block burst 1100a is repeated once in another frequency location as SS / PBCH block burst 1100b.

[0156] In another aspect, the UE assumes that a SS / PBCH block burst set and its repetitions share the same time domain information about the transmission, including at least one of the periodicity, the half-frame containing its transmission, or the actual transmitted SS / PBCH blocks.

[0157] In yet another aspect, the UE assumes that the parameter set for the first SS / PBCH block burst set and its repetitions are the same.

[0158] On the other hand, if the first SS / PBCH block and the second SS / PBCH block have the same SS / PBCH block index, the UE assumes that the first SS / PBCH block in the SS / PBCH block burst set is quasi-colocated with the second SS / PBCH block in the repeated SS / PBCH block burst set in the frequency domain.

[0159] On the other hand, the UE may assume that the first SS / PBCH block burst set is located on a synchronization grid entry, and that the first SS / PBCH block burst set serves as a cell-defining SS / PBCH block, and that repetitions of the first SS / PBCH block burst set are not located on a synchronization grid entry (making them invisible in the initial cell search).

[0160] In yet another aspect, the UE may assume a fixed relative position in the frequency domain between the first SS / PBCH block burst set and its repetition. In one approach, the offset between the lowest RB of the first SS / PBCH block burst set and the lowest RB of its repetition may be fixed. For example, the offset is fixed to 20 RBs (e.g., two SS / PBCH block burst sets are adjacent to each other in the frequency domain and there is no frequency gap between them).

[0161] In yet another aspect, the UE may assume a fixed relationship between the cell ID carried by the first SS / PBCH block burst set and its repetitions. In one approach, the UE may assume that the cell ID carried by the first SS / PBCH block burst set is the same as the cell ID carried by its repetitions. In another approach, the UE may assume that the cell ID carried by the first SS / PBCH block burst set has a fixed offset compared to the cell ID carried by its repetitions. For one example of the present method, the cell IDs of the SS / PBCH block burst set and its repetition groups are consecutive and increase according to the frequency position within the group.

[0162] Fig.12A conventional PRACH preamble format with a long sequence is shown, and Fig.13 A conventional PRACH preamble format with a short sequence is shown. Aspects of the enhanced PRACH preamble format design according to various embodiments of the present disclosure may relate to the sequence length for the PRACH preamble, the SCS supported for the PRACH preamble, and the PRACH preamble composition. The present disclosure describes two groups of PRACH preamble formats. The first group of PRACH preamble formats is an SCS adjusted based on 1.25kHz, and the second group of PRACH preamble formats is an SCS adjusted based on 15kHz.

[0163] In one embodiment, the enhanced PRACH preamble code format has a ZC sequence (e.g., denoted as L_RA) with a length of at least 839 (e.g., L_RA≥839) and a subcarrier spacing (e.g., denoted as SCS_RA) adjusted from 1.25kHz (e.g., SCS_RA 1.25kHz / ρ).

[0164] For example, at least one of the L_RAs in the following Table 1 may be supported.

[0165] Table 1 Examples of ZC sequence lengths

[0166]

Table 1

[0167] index L_RA 1 835 2 1723 3 3449 4 6911

[0168] In one method of this embodiment, a PRACH format without a gap after the sequence is supported.

[0169] Fig.14A and Fig. 14B An exemplary PRACH format without reserved gaps according to various embodiments of the present disclosure is shown. These PRACH formats are also shown in Table 2. In this example, the ZC sequence length (e.g., L_RA) can be one of the examples in Table 1, and the SCS (e.g., SCS_RA) can be adjusted from 1.25kHz so that SCS_RA=1.25 / ρ, where ρ is an SCS adjustment factor relative to 1.25kHz (e.g., ρ can be in the form of ρ=2^v, where v is an integer, positive, zero, or negative). Note that N_CP, N_SEQ, and N_total are adjusted with ρ.

[0170] Table 2 Example PRACH preamble format

[0171]

Table 2

[0172]

[0173] In another method of this embodiment, a PRACH format with a post-sequence reserved gap is supported.

[0174] Fig.15A and Fig. 15B PRACH formats that reserve gaps according to various embodiments of the present disclosure are shown. These exemplary PRACH formats are also shown in Table 3.

[0175] The ZC sequence length (e.g., L_RA) can be one of the examples in Table 1, and the SCS (e.g., SCS_RA) can be adjusted from 1.25kHz so that SCS_RA=1.25 / ρ, where ρ is the SCS adjustment factor relative to 1.25kHz (e.g., ρ can be in the form of ρ=2^v, where v is an integer, positive, zero, or negative). Note that N_CP, N_SEQ, N_GAP, and N_total adjust with ρ.

[0176] Table 3 Example PRACH preamble format

[0177]

Table 3

[0178]

[0179] In one embodiment, the enhanced PRACH preamble code format has a ZC sequence (e.g., denoted as L_RA) with a length of at least 139 (e.g., L_RA≥139) and a subcarrier spacing (e.g., denoted as SCS_RA) adjusted from 15kHz (e.g., SCS_RA 15 / ρ).

[0180] For example, at least one of the L_RAs in the following Table 4 may be supported, and SCS_RA=15 / ρ, where ρ is the SCS ratio relative to 15 kHz (eg, ρ may be in the form of ρ=2^v, where v is an integer, positive, zero, or negative).

[0181] Table 4 Examples of ZC sequence lengths

[0182]

Table 4

[0183] index L_RA 1 139 2 283 3 571 4 1151 5 2297 6 4603

[0184] In one method of this embodiment, a PRACH format without a gap after the sequence is supported.

[0185] Fig.16PRACH preamble formats without reserved gaps according to various embodiments of the present disclosure are shown. These exemplary PRACH formats are also shown in Table 5. In this example, the ZC sequence length (e.g., L_RA) can be one of the examples in Table 4, and the SCS (e.g., SCS_RA) can be adjusted from 15kHz so that SCS_RA=15 / ρ, where ρ is an SCS adjustment factor relative to 15kHz (e.g., ρ can be in the form of ρ=2^v, where v is an integer, positive, zero, or negative). Note that N_CP and N_SEQ are adjusted with ρ.

[0186] Table 5 Example PRACH preamble format

[0187]

Table 5

[0188]

[0189]

[0190] In another method of this embodiment, a PRACH format with a post-sequence reserved gap is supported.

[0191] Fig.17 Other PRACH formats with gaps according to various embodiments of the present disclosure are shown. The PRACH format is also shown in Table 6.

[0192] In this example, the ZC sequence length (e.g., L_RA) can be one of the examples in Table 4, and the SCS (e.g., SCS_RA) can be adjusted from 15kHz so that SCS_RA=15 / ρ, where ρ is the SCS adjustment factor relative to 15kHz (e.g., ρ can take the form of ρ=2^v, where v is an integer, positive, zero, or negative). Note that N_CP and N_SEQ adjust with ρ.

[0193] Table 6 Example PRACH preamble format

[0194]

Table 6

[0195]

[0196]

[0197] As mentioned previously, for NTN, there is usually a large propagation delay between the transmitter and the receiver, and the specific maximum round trip delay (RTD) depends on the real-time scenario. Table 7 shows exemplary maximum RTDs for some typical NTN scenarios.

[0198] Table 7 Example maximum round trip delay for NTN scenario

[0199]

Table 7

[0200]

[0201] Disabling HARQ feedback may be beneficial for some NTN scenarios. Therefore, additional aspects of the present disclosure include methods for HARQ feedback disabling, priority rules for HARQ feedback disabling, HARQ enhancement with UE assistance information, DCI format after HARQ feedback disabling, and reliability recovery after HARQ feedback disabling.

[0202] In one embodiment, HARQ feedback may be configured to be disabled by the gNB. Various methods of this embodiment are discussed below.

[0203] Method 1. HARQ feedback may be configured to be disabled by a higher layer parameter (eg, RRC parameter). The UE assumes that HARQ feedback remains disabled for all transmissions until the higher layer parameter indicates that HARQ feedback is enabled. At least one method or combination of methods for this method may be supported.

[0204] In the first method of method 1, the high-level parameters for disabling HARQ feedback may be cell-specific. For example, at least one field in ServingCellConfigCommon is used to indicate whether HARQ feedback is disabled. For another example, at least one field in ServingCellConfig is used to indicate whether HARQ feedback is disabled.

[0205] In the second method of method 1, the high-level parameter for disabling HARQ feedback may be cell group specific. For example, at least one field in CellGroupConfig is used to indicate whether to disable HARQ feedback.

[0206] In the third method of method 1, the high-level parameters for disabling HARQ feedback may be UE-specific. For example, at least one field in ServingCellConfig is used to indicate whether to disable HARQ feedback.

[0207] In a fourth method of method 1, at least one higher layer parameter is used to configure whether to disable DL HARQ feedback.

[0208] In a fifth method of the present method, at least one higher layer parameter is used to configure whether to disable UL HARQ feedback.

[0209] In a sixth method of method 1, at least one higher layer parameter is used to configure whether to jointly disable DL HARQ feedback and UL HARQ feedback.

[0210] Method 2. HARQ feedback may be configured to be disabled by DCI format. At least one method or a combination of methods for this method may be supported.

[0211] In the first method of method 2, the DCI format may be a DCI format scheduling of a PUSCH of a cell (eg, DCI format 0_0 and / or DCI format 0_1). The UE assumes that the PUSCH scheduled by the DCI format transmits disabled HARQ feedback.

[0212] In the second method of method 2, the DCI format may be a DCI format scheduled by a PDSCH of a cell (eg, DCI format 1_0 and / or DCI format 1_1). The UE assumes that the PDSCH scheduled by the DCI format transmits disabled HARQ feedback.

[0213] In a third method of method 2, the DCI format may be a DCI format (eg, DCI format 2_0 and / or DCI format 2_1) that notifies a group of UE information. The UE assumes that HARQ feedback is disabled for the same duration as the duration when the notification information is valid.

[0214] In a fourth method of Method 2, a new separate field in the DCI format may be used to indicate whether HARQ feedback is disabled. In a non-limiting embodiment, the field is 1 bit wide.

[0215] In the fifth method of method 2, the value of an existing field in the DCI format (e.g., a reserved value) can be used to indicate disabling HARQ feedback (e.g., by setting the field to a non-numeric value). For one example, the value of an existing field of the number of HARQ processors in the DCI format (e.g., a reserved value) can be used to indicate disabling HARQ feedback (e.g., by setting the field to a non-numeric value). For another example, the value of an existing field of a downlink allocation index in the DCI format (e.g., a reserved value) can be used to indicate disabling HARQ feedback (e.g., by setting the field to a non-numeric value). For another example, the value of an existing field of a PUCCH resource indicator in the DCI format (e.g., a reserved value) can be used to indicate disabling HARQ feedback (e.g., by setting the field to a non-numeric value). For another example, the value of an existing field of a PDSCH-to-HARQ_feedback timing indicator in the DCI format (e.g., a reserved value) can be used to indicate disabling HARQ feedback (e.g., by setting the field to a non-numeric value). For yet another example, a value of an existing field (e.g., a reserved value) of a TPC command for a scheduled PUCCH in a DCI format may be used to indicate disabling HARQ feedback (e.g., by setting the field to a non-numeric value). For yet another example, a value of an existing field (e.g., a reserved value) of a TPC command for a scheduled PUSCH in a DCI format may be used to indicate disabling HARQ feedback (e.g., by setting the field to a non-numeric value).

[0216] Method 3. HARQ feedback may be configured to be disabled by system information. In the first method of method 3, whether HARQ feedback is disabled may be indicated in the content of PBCH. In the second method of method 3, whether HARQ feedback is disabled may be indicated in RMSI. In the third method of method 3, whether HARQ feedback is disabled may be indicated in OSI. In the fourth method of method 3, whether HARQ feedback is disabled may be indicated in paging.

[0217] In one embodiment, at least one method and / or manner may be supported to disable HARQ feedback as previously described, and a priority rule indicated by the at least one method and / or manner may be specified from the perspective of the UE.

[0218] In one method, if both the method of using higher layer parameters to indicate whether HARQ feedback is enabled and the method of using system information to indicate whether HARQ feedback is enabled are supported, the UE assumes that during the validity period of the higher layer parameters, the indication by the higher layer parameters takes precedence over the indication by the system information.

[0219] In another method, if both a method of using a higher layer parameter to indicate whether HARQ feedback is enabled and a method of using a DCI format to indicate whether HARQ feedback is enabled are supported, the UE assumes that for PUSCH transmission or PDSCH transmission scheduled by the DCI format, the indication by the DCI format takes precedence over the indication by the higher layer parameter.

[0220] In another method, if both the method of using system information to indicate whether HARQ feedback is enabled and the method of using DCI format to indicate whether HARQ feedback is enabled are supported, the UE assumes that for PUSCH transmission or PDSCH transmission scheduled by the DCI format, the indication by the DCI format takes precedence over the indication by the system information.

[0221] In one embodiment, the UE may notify the gNB of assistance information related to HARQ operation. In one method, the UE may notify the gNB of assistance information related to HARQ feedback disabling via a higher layer parameter. In one aspect, the assistance information related to HARQ disabling may be included in the RRC parameter UEAssistanceInformation. In another aspect, the assistance information related to HARQ operation may include soft buffer information for receiving transmission.

[0222] In yet another aspect, the auxiliary information related to the HARQ operation may include a request to explicitly disable or enable HARQ feedback. In yet another aspect, the auxiliary information related to the HARQ operation may include a request to disable a set of HARQ feedback and / or enable a set of HARQ feedback (e.g., by indicating an index of the HARQ feedback). In yet another aspect, the auxiliary information related to the HARQ operation may include a request to increase the number of HARQ feedback. In yet another aspect, the auxiliary information related to the HARQ operation may include a request to reduce the number of HARQ feedback.

[0223] On the other hand, a UE capable of providing auxiliary information related to HARQ operations in RRC_CONNECTED may initiate a process if at least one of the following occurs: the UE is configured to do so, or when it detects that the soft buffer is fully utilized, or when it detects that the soft buffer is no longer fully utilized, or when it chooses to send a HARQ feedback disable request, or when it chooses to send a HARQ feedback enable request, or when it chooses to send a request to increase the number of HARQ feedback, or when it chooses to send a request to reduce the number of HARQ feedback, or when it chooses to send a request to disable a set of HARQ feedback and / or enable a set of HARQ feedback.

[0224] On the other hand, the UE shall set the content of the UEAssistanceInformation message for auxiliary information related to the HARQ operation if at least one of the following occurs: when it is detected that the soft buffer is fully utilized, or when it is detected that the soft buffer is no longer fully utilized, or when a HARQ feedback disable request is selected to be sent, or when a HARQ feedback enable request is selected to be sent, or when a request for increasing the number of HARQ feedback is selected to be sent, or when a request for reducing the number of HARQ feedback is selected to be sent, or when a request for disabling a set of HARQ feedback and / or enabling a set of HARQ feedback is selected.

[0225] On the other hand, the UE assumes that DL HARQ feedback is disabled immediately after it notifies the gNB that the soft buffer is fully used or a HARQ feedback disabling request is made.

[0226] In another method, the UE can notify the gNB of the auxiliary information related to the HARQ operation through HARQ ACK / NACK feedback.

[0227] In one aspect, the auxiliary information related to the HARQ operation may include soft buffer information for receiving transmissions.

[0228] In another aspect, the assistance information related to HARQ operation may include a request to explicitly disable or enable HARQ feedback.

[0229] In yet another aspect, in addition to ACK and NACK, a new separate status may be reported in the HARQ ACK / NACK feedback to indicate the UE request for HARQ operation.

[0230] In yet another aspect, there may be a HARQ codebook mode indicating a UE request for HARQ operation. For example, the UE may use an all-NACK codebook to notify the gNB to disable HARQ feedback.

[0231] In one embodiment, after HARQ feedback is disabled, at least one HARQ-related field in the DCI format may be reserved or determined to be 0 bit wide.

[0232] In one aspect, according to the DCI format, after HARQ feedback is disabled, at least one field related to HARQ in the DCI format may be reserved or determined to be 0 bit wide.

[0233] In one method, if the DCI format is DCI format 1_0, at least one field related to DL HARQ in the DCI format may be retained after HARQ feedback is disabled.

[0234] In one example, for DCI format 1_0 with a CRC scrambled by C-RNTI (but not for a random access procedure initialized by a PDCCH command) or CS-RNTI or MCS-C-RNTI, after DL HARQ feedback is disabled, at least one of the following fields in the DCI format may be retained: number of HARQ processes, downlink allocation index, TPC command for scheduled PUCCH, PUCCH resource indicator, or PDSCH-to-HARQ_feedback timing indicator.

[0235] In another example, for DCI format 1_0 with CRC scrambled by TC-RNTI, after DL HARQ feedback is disabled, at least one of the following fields in the DCI format may be retained: number of HARQ processes, TPC command for scheduled PUCCH, PUCCH resource indicator, or PDSCH-to-HARQ_feedback timing indicator. Note that for this example, the downlink allocation index is retained regardless of enabling or disabling DL HARQ.

[0236] In another method, if the DCI format is DCI format 1_1, after DL HARQ feedback is disabled, at least one field related to DL HARQ in the DCI format may be determined to be 0 bit wide.

[0237] In one example, for DCI format 1_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI, after DL HARQ feedback is disabled, at least one of the following fields in the DCI format may be determined to be 0 bit wide: number of HARQ processes, downlink allocation index, TPC command for scheduled PUCCH, PUCCH resource indicator, or PDSCH-to-HARQ_feedback timing indicator.

[0238] In yet another method, if the DCI format is DCI format 0_0, after UL HARQ feedback is disabled, at least one field related to UL HARQ in the DCI format may be retained.

[0239] In one example, for DCI format 0_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI, after UL HARQ feedback is disabled, at least one of the following fields in the DCI format may be retained: number of HARQ processes, or TPC command for scheduled PUCCH.

[0240] In another example, for DCI format 0_0 with CRC scrambled by TC-RNTI, after UL HARQ feedback is disabled, at least one of the following fields in the DCI format may be retained: the number of HARQ processes, or the TPC command for scheduling PUSCH.

[0241] In yet another method, if the DCI format is DCI format 0_1, after UL HARQ feedback is disabled, at least one field related to UL HARQ in the DCI format may be determined to be 0 bits wide.

[0242] In one example, for DCI format 0_1 ​​with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI, after UL HARQ feedback is disabled, at least one of the following fields in the DCI format may be determined to be 0 bit wide: number of HARQ processes, or 1st downlink allocation index, or 2nd downlink allocation index, or TPC command for scheduling PUSCH.

[0243] On the other hand, when at least one field related to HARQ in the DCI format may be reserved, in addition, the reserved field may be set to a default value (eg, an all-zero value).

[0244] In one embodiment, after HARQ feedback is disabled, transmission for reliability recovery may be enhanced. In one enhanced transmission method, one transmission may be repeated in each transmission with the same RV, and the parameters for enhanced transmission include at least one of a repetition number or a repetition index.

[0245] In another enhanced transmission method, a TB may be transmitted multiple times in each transmission with different RVs, and the parameters for enhanced transmission include at least one of the number of transmissions or the RV value for each transmission. In one example, the RV value for enhanced transmission may be only one of 0 or 3.

[0246] In one method, enhanced transmission is assumed by the UE without explicit configuration when the UE knows that HARQ feedback is disabled.For this method, when the UE knows that HARQ feedback is disabled, the parameters for enhanced transmission may be fixed and known to the UE.

[0247] In another method, enhanced transmission is configured by the gNB to the UE. In one aspect of this method, the configuration of enhanced transmission can be indicated separately from the configuration of HARQ feedback disable / enable, and enhanced transmission does not have to be associated with HARQ feedback disable. For this method, parameters for enhanced transmission can be configured to the UE.

[0248] In yet another approach, enhanced transmission is configured jointly with HARQ disabling / enabling. For example, parameters for enhanced transmission may be jointly encoded with a HARQ feedback disabling indicator.

[0249] Fig.18 1800 is a flowchart of a process for managing HARQ transmissions in a wireless network according to various embodiments of the present disclosure. The operations in flowchart 1800 may be performed in a UE (such as Figure 3 The method is implemented in the UE 116 in the example.

[0250] Flowchart 1800 begins at operation 1802 by receiving downlink control information (DCI) in a physical downlink control channel (PDCCH) from a base station.

[0251] In operation 1804, it is determined whether to disable hybrid automatic repeat request (HARQ) feedback. The determination may be based on a first field in the DCI. In one embodiment, the first field may be a dedicated field that indicates HARQ using a reserved bit in the DCI format. In another embodiment, the first field may be an existing field in the DCI format, which may be interpreted as disabling HARQ feedback.

[0252] In operation 1806, if HARQ feedback is disabled, it is determined based on the DCI format whether the second field in the DCI is a reserved field or a zero-bit-width field. In one embodiment, when the DCI format is DCI format 0_0 or DCI format 1_0, the second field may be determined to be a reserved field. In another embodiment, when the DCI format is DCI format 0_1 ​​or DCI format 1_1, the second field is determined to be a zero-bit-width field.

[0253] In some embodiments, when the DCI format is DCI format 0_0 or DCI format 0_1, the second field may be a HARQ feedback quantity field, or a transmit power control (TPC) command field for scheduling a physical uplink shared channel (PUSCH).

[0254] In other embodiments, when the DCI format is DCI format 1_0 or DCI format 1_1, the second field can be a HARQ feedback quantity field, a transmit power control (TPC) command field for scheduling a physical uplink control channel (PUCCH), a PUCCH resource indicator field, or a PDSCH-to-HARQ_feedback timing indicator field.

[0255] In some embodiments, flowchart 1800 may also include other steps of generating high-layer parameters including auxiliary information, wherein the auxiliary information includes at least one of soft buffer information for reception, a request for disabling HARQ feedback, a request for enabling HARQ feedback, a request for increasing the number of HARQ feedback, or a request for reducing the number of HARQ feedback, and sending the high-layer parameters to the BS via an uplink channel.

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

Claims

1. A user equipment UE (116) in a wireless communication system, the UE include: At least one transceiver (310) configured to receive downlink control information DCI in a physical downlink control channel PDCCH; as well as At least one processor (340) operably connected to the at least one transceiver, the at least one processor configured to: determining whether to disable hybrid automatic repeat request HARQ feedback based on a first field in the DCI, and After determining that the HARQ feedback is disabled: In the case where the DCI format is the first format, determining that the second field in the DCI is a reserved field, and When the DCI format is the second format, it is determined that the second field in the DCI is a zero-bit-width field.

2. The UE according to claim 1, in, The first field is one of a dedicated field in the DCI format that uses a reserved bit to indicate disabling of the HARQ feedback or an existing field in the DCI format, and wherein the existing field is interpreted as being used to disable the HARQ feedback.

3. The UE according to claim 1, in, The first format is one of DCI format 0_0 or DCI format 1_0.

4. The UE according to claim 1, in, The second format is one of DCI format 0_1 ​​or DCI format 1_1.

5. The UE according to claim 1, in, In a case where the DCI format is one of DCI format 0_0 or DCI format 0_1, the second field is one of a HARQ feedback quantity field or a transmit power control TPC command field for scheduling a physical uplink shared channel PUSCH.

6. The UE according to claim 1, in, In the case where the DCI format is one of DCI format 1_0 or DCI format 1_1, the second field is one of a HARQ feedback quantity field, a transmit power control TPC command field for scheduling a physical uplink control channel PUCCH, a PUCCH resource indicator field, or a PDSCH-to-HARQ feedback timing indicator field.

7. The UE according to claim 1, in: The at least one processor is further configured to generate a higher layer parameter including auxiliary information related to the HARQ operation, wherein the auxiliary information includes at least one of: soft buffer information for reception, a request for disabling the HARQ feedback, a request for enabling the HARQ feedback, a request for increasing the number of the HARQ feedback, or a request for decreasing the number of the HARQ feedback, and The at least one transceiver is further configured to transmit the higher layer parameters over an uplink channel.

8. A base station BS (102), include: transceivers (282a, 282b, 282n); as well as A processor (288) operably connected to the transceiver, the processor being configured to: Determine whether to disable hybrid automatic repeat request HARQ feedback, and generating downlink control information DCI having a first field indicating whether the HARQ feedback is disabled, wherein, in the case where the HARQ feedback is disabled, The DCI includes a second field: In the case where the DCI format is the first format, the second field is a reserved field, and When the DCI format is the second format, the second field is a zero-bit-width field, The transceiver is configured to send the DCI in a physical downlink control channel PDCCH.

9. The BS according to claim 8, in, The first field is one of a dedicated field in the DCI format that uses a reserved bit to indicate disabling of the HARQ feedback or an existing field in the DCI format, and wherein the existing field is interpreted as being used to disable the HARQ feedback.

10. The BS according to claim 8, in, The first format is one of DCI format 0_0 or DCI format 1_0.

11. The BS according to claim 8, in, The second format is one of DCI format 0_1 ​​or DCI format 1_1.

12. The BS according to claim 8, in, In a case where the DCI format is one of DCI format 0_0 or DCI format 0_1, the second field is one of a HARQ feedback quantity field or a transmit power control TPC command field for scheduling a physical uplink shared channel PUSCH.

13. The BS according to claim 8, in, In the case where the DCI format is one of DCI format 1_0 or DCI format 1_1, the second field is one of a HARQ feedback quantity field, a transmit power control TPC command field for scheduling a physical uplink control channel PUCCH, a PUCCH resource indicator field, or a PDSCH-to-HARQ feedback timing indicator field.

14. The BS according to claim 8, in, The transceiver is configured as follows: A higher layer parameter is received via an uplink channel, wherein the higher layer parameter includes auxiliary information related to HARQ operation, and wherein the auxiliary information includes at least one of the following: soft buffer information for reception, a request for disabling the HARQ feedback, a request for enabling the HARQ feedback, a request for increasing the number of the HARQ feedback, or a request for reducing the number of the HARQ feedback.

15. A method for managing hybrid automatic repeat request (HARQ) transmission in a wireless communication system, performed by a user equipment (UE), the method include: Receiving downlink control information DCI in a physical downlink control channel PDCCH; Determining whether to disable hybrid automatic repeat request (HARQ) feedback based on a first field in the DCI; as well as After determining that the HARQ feedback is disabled: In the case where the DCI format is the first format, determining that the second field in the DCI is a reserved field, and When the DCI format is the second format, it is determined that the second field in the DCI is a zero-bit-width field.

16. The method according to claim 15, in, The first field is one of a dedicated field in the DCI format that uses a reserved bit to indicate disabling of the HARQ feedback or an existing field in the DCI format, and wherein the existing field is interpreted as being used to disable the HARQ feedback.

17. The method according to claim 15, in, The first format is one of DCI format 0_0 or DCI format 1_0, and the second format is one of DCI format 0_1 ​​or DCI format 1_1.

18. The method according to claim 15, in, In a case where the DCI format is one of DCI format 0_0 or DCI format 0_1, the second field is one of a HARQ feedback quantity field or a transmit power control TPC command field for scheduling a physical uplink shared channel PUSCH.

19. The method according to claim 15, in, In the case where the DCI format is one of DCI format 1_0 or DCI format 1_1, the second field is one of a HARQ feedback quantity field, a transmit power control TPC command field for scheduling a physical uplink control channel PUCCH, a PUCCH resource indicator field, or a PDSCH-to-HARQ feedback timing indicator field.

20. The method according to claim 15, further comprising: include: generating a higher layer parameter including auxiliary information related to HARQ operation, wherein the auxiliary information includes at least one of: soft buffer information for reception, a request for disabling the HARQ feedback, a request for enabling the HARQ feedback, a request for increasing the number of the HARQ feedback, or a request for decreasing the number of the HARQ feedback; and The higher layer parameters are sent via an uplink channel.