Uplink transmission and reception for RACH-free handover
By employing a RACH-free handover process in the wireless communication system and utilizing the repetition and spatial configuration of PUSCH, the problem of low RACH operation efficiency in the high-frequency band is solved, achieving a more efficient handover process, reducing signaling overhead and latency, and improving system performance.
Patent Information
- Application Number
- CN202480023693.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-03-25
- Filing Date
- 2024-04-02
- Publication Date
- 2025-11-11
AI Technical Summary
Existing wireless communication systems require random access channel (RACH) operations during handover, which increases signaling overhead and handover delay, especially in high-frequency bands such as millimeter wave and terahertz bands where efficiency is low.
The RACH-free handover process is adopted by configuring and determining the spatial settings between the user equipment (UE) and the base station (BS), and utilizing the repetition number and spatial settings of the Physical Uplink Shared Channel (PUSCH) to achieve a handover process without RACH.
It reduces signaling overhead and handover latency, improves the handover efficiency of wireless communication systems in high-frequency bands, especially in millimeter-wave and terahertz bands, and enhances system performance.
Smart Images

Figure CN120937432A_ABST
Abstract
Description
Technical Field
[0001] This disclosure generally relates to wireless communication systems, and more specifically, to uplink (UL) transmission and reception for a random access channel (RACH) handover process. Background Technology
[0002] Fifth-generation (5G) mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5 GHz, but also in "above 6GHz" bands, including 28 GHz and 39 GHz, known as millimeter waves (mmWave). Furthermore, sixth-generation (6G) mobile communication technology (called Super 5G systems) has been considered for implementation in terahertz (THz) bands (e.g., the 95 GHz to 3 THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.
[0003] At the outset of 5G mobile communication technology development, to support services and meet performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization was underway for beamforming and massive multiple-input multiple-output (MIMO) to mitigate radio wave path loss and increase radio wave transmission distance in millimeter waves; dynamic operation supporting parameter sets (e.g., operating multiple subcarrier spacings) and time slot formats for efficient utilization of millimeter wave resources; initial access technologies to support multi-beam transmission and broadband; the definition and operation of bandwidth portions (BWP); new channel coding methods such as low-density parity-check (LDPC) codes for large-volume data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing for providing dedicated networks for specific services.
[0004] Currently, given the services that 5G mobile communication technology needs to support, there is ongoing discussion about improvements and performance enhancements to the initial 5G mobile communication technology, and there is already physical layer standardization for technologies such as: Vehicle-to-Everything (V2X) for assisting autonomous vehicle driving determination based on information sent by the vehicle about its location and status and for enhancing user convenience; New Radio Unlicensed (NR-U) for system operation aimed at complying with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Networks (NTNs) for UE-satellite direct communication to provide coverage in areas where communication with terrestrial networks is unavailable; and positioning.
[0005] Furthermore, standardization is underway regarding air interface architectures / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interoperability and convergence with other industries, Integrated Access and Backhaul (IAB) for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner, mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover, and Two-Step Random Access (NR Two-Step RACH) for simplifying the random access process. Standardization is also underway for 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, as well as system architectures / services for Mobile Edge Computing (MEC) based on UE location reception services.
[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will connect to communication networks, and correspondingly, enhanced functionality and performance of 5G mobile communication systems, as well as the integrated operation of connected devices, are expected to be necessary. To this end, new research is planned related to: Extended Reality (XR) for effectively supporting Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), etc.; 5G performance enhancement and complexity reduction through the utilization of Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communications.
[0007] Furthermore, this development of 5G mobile communication systems will not only lay the foundation for: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas for improving coverage of terahertz band signals; high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM); and reconfigurable smart surfaces (RIS); but also lay the foundation for: full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technologies for system optimization by leveraging satellites and AI from the design phase and internalizing end-to-end AI support functions; and next-generation distributed computing technologies for providing services at a level of complexity exceeding the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources. Summary of the Invention
[0008] Technical issues
[0009] This disclosure relates to a RACH-less switching process for use in UL.
[0010] Technical solution
[0011] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive information from a system information block (SIB) of a source cell regarding a first configuration for a RACH-free handover procedure, a first synchronization signal (SS), a physical broadcast channel (PBCH) (SS / PBCH) block index set, a PUSCH for transmission on a physical uplink shared channel (PUSCH) in a target cell, and the number of repetitions of the PUSCH transmission in the target cell. The UE also includes a processor operatively coupled to the transceiver. The processor is configured to determine spatial settings for PUSCH transmission. The transceiver is further configured to transmit the PUSCH with the repetition count using the spatial settings in the target cell.
[0012] In another embodiment, a base station (BS) is provided. The BS includes a transceiver configured to transmit a first configuration for a RACH-free handover procedure, a first SS / PBCH block index set, a PUSCH for reception on a target cell, and the number of repetitions of the PUSCH received on the target cell, from an SIB of a source cell. The BS also includes a processor operatively coupled to the transceiver. The processor is configured to determine spatial settings for PUSCH reception. The transceiver is further configured to receive the PUSCH with the number of repetitions on the target cell using the spatial settings.
[0013] In yet another embodiment, a method is provided. The method includes receiving, from a source cell's SIB, a first configuration for a RACH-free handover procedure, a first SS / PBCH block index set, a PUSCH for transmission on a target cell, and a number of repetitions of the PUSCH transmission on the target cell. The method further includes determining spatial settings for PUSCH transmission and transmitting the PUSCH with the number of repetitions on the target cell using the spatial settings.
[0014] Other technical features will be apparent to those skilled in the art from the following figures, description and claims.
[0015] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives, cover both direct and indirect communication. The terms “including” and “comprising,” and their derivatives, mean including but not limited to. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives, mean including, being included in, interconnected with, containing, being contained within, connected to or connected to, coupled to or coupled with, able to communicate with, cooperate with, interleaved, juxtaposed, proximate, bound to or bound to, having, possessing the attributes of, having a relationship to or with, etc. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, local or remote. The phrase "at least one of..." when used with a list of items means that different combinations of one or more of the listed items may be used, and it is possible that only one item from the list is needed. 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.
[0016] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable medium includes media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical discs or erasable memory devices.
[0017] Definitions of certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many cases (if not most), such definitions apply to the prior and future use of the words and phrases defined in this way.
[0018] Beneficial effects
[0019] According to embodiments of this disclosure, a RACH-free handover process for UL can be performed. Attached Figure Description
[0020] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:
[0021] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;
[0022] Figure 2 An example BS according to an embodiment of this disclosure is shown;
[0023] Figure 3 An example UE according to an embodiment of the present disclosure is shown;
[0024] Figure 4A An example wireless transmission path according to an embodiment of the present disclosure is shown;
[0025] Figure 4B An example wireless reception path according to an embodiment of the present disclosure is shown;
[0026] Figure 5 A block diagram of an example transmitter structure using orthogonal frequency division multiplexing (OFDM) according to an embodiment of the present disclosure is shown;
[0027] Figure 6 A block diagram of an example receiver structure using OFDM according to an embodiment of the present disclosure is shown;
[0028] Figure 7A An example of satellite coverage in an NTN according to an embodiment of this disclosure is shown;
[0029] Figure 7B Another example of satellite coverage in an NTN according to an embodiment of this disclosure is shown;
[0030] Figure 8 The UE procedure for RACH-free handover to a target satellite according to this disclosure is shown;
[0031] Figure 9The present disclosure illustrates various embodiments of a UE procedure for a RACH-free handover having repeated first uplink transmissions scheduled by a DCI format received in the target cell.
[0032] Figure 10 Various embodiments of this disclosure illustrate RACH-free handover procedures for a UE with repeated first uplink transmissions in a target cell scheduled by configured licenses;
[0033] Figure 11 This illustrates various embodiments of the present disclosure of a UE procedure for a RACH-free handover in a target cell with repeated first PUCCH transmissions; and
[0034] Figure 12 This is an example method performed by a UE in a wireless communication system according to embodiments of this disclosure. Detailed Implementation
[0035] The following discussion Figures 1 to 12 The various embodiments used to describe the principles of this disclosure in this patent document are merely illustrative and should not be construed in any way as limiting the scope of this disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.
[0036] The following literature and standards descriptions are incorporated herein by reference as if fully set forth herein: 3GPP TS 38.211 v17.3.0, “NR; Physical channels and modulation” (REF1); 3GPP TS 38.212 v17.3.0, “NR; Multiplexing and channelcoding” (REF2); 3GPP TS 38.213 v17.3.0, “NR; Physical Layer Procedures for Control” (REF3); 3GPP TS 38.214 v17.3.0, “NR; Physical Layer Procedures for Data” (REF4); 3GPP TS 38.321 v17.2.0, “NR; Medium Access Control (MAC) protocol specification” (REF5); and 3GPP TS 38.331 v17.2.0, “NR; Radio Resource Control (RRC) Protocol Specification” (REF6).
[0037] To meet the increasing demand for wireless data services since the deployment of 4G communication systems and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (such as 6 GHz) to achieve robust coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G / NR communication systems.
[0038] In addition, in 5G / NR communication systems, the development of system network improvements is based on advanced small cells, cloud radio access networks (RAN) ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation.
[0039] The discussion of 5G systems and their associated frequency bands is for reference only, as certain embodiments of this disclosure can be implemented in 5G systems. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be used in conjunction with any frequency band. For example, aspects of this disclosure can also be applied to the deployment of 5G communication systems, 6G, or even later versions that may use terahertz (THz) frequency bands.
[0040] The following Figures 1-3 Various embodiments are described in wireless communication systems and implemented using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technologies. Figures 1-3 The description does not imply any physical or architectural limitation on the ways in which different embodiments may be implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system.
[0041] Figure 1 An example wireless network according to an embodiment of this disclosure is shown. Figure 1 The embodiments of the wireless network shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.
[0042] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., a base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data network).
[0043] gNB 102 provides wireless broadband access to network 130 to a first plurality of user equipments (UEs) within its coverage area 120. The first plurality of UEs includes UE 111, which may be located in a small business; UE 112, which may be located in an enterprise; UE 113, which may be a WiFi hotspot; UE 114, which may be located in a first residence; UE 115, which may be located in a second residence; and UE 116, which may be a mobile device, such as a cellular phone, wireless laptop computer, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, Long Term Evolution (LTE), LTE-A Advanced, WiMAX, WiFi, or other wireless communication technologies.
[0044] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmitting point (TP), a transmitting-receiving point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femtocell, a WiFi access point (AP), or other wireless enabling devices. A base station can provide wireless access according to one or more wireless communication protocols, such as 5G / NR 3rd Generation Partnership Project (3GPP) NR, Long Term Evolution (LTE), LTE Advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11 a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Furthermore, depending on the network type, the term "user equipment" or "UE" can refer to any component, such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user equipment." For convenience, the terms “user equipment” and “UE” are used in this patent document to refer to a remote wireless device for wireless access to a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered to be a fixed device (such as a desktop computer or vending machine).
[0045] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with the gNB (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.
[0046] As discussed in more detail below, wireless network 100 may have communications facilitated via one or more communication satellites 104 that can move on Earth. Communication satellites 104 may communicate directly with BS 102 and BS 103 to provide network access, for example, in cases where BS 102 and BS 103 are remotely located or otherwise require network access connections beyond traditional fronthaul and / or backhaul connections. Various UEs (e.g., as depicted in UE 116) may be able to have at least some direct communication and / or positioning with communication satellites 104, for example, to receive positioning information or coordinates.
[0047] NTN refers to a network or network segment that utilizes RF resources carried on communication satellites (or unmanned aerial vehicle system platforms) (e.g., communication satellite 104). Envisioned to provide wide coverage and reliable service, NTN ensures ubiquitous service availability and continuity. For example, NTN could support communication services in unserved areas not covered by terrestrial networks, in underserved areas experiencing limited communication services, for devices and passengers on mobile platforms, and for future rail / marine / aviation communications, etc.
[0048] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof to facilitate uplink transmission during a RACH-free handover process. In some embodiments, one or more of BSs 101-103 include circuitry, programming, or a combination thereof to facilitate uplink transmission during a RACH-free handover process.
[0049] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1 Various modifications can be made. For example, the wireless network can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.
[0050] Figure 2 An example gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 gNBs 101 and 103 can have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 2 This disclosure is not intended to limit the scope of any particular implementation of gNB.
[0051] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.
[0052] Transceivers 210a-210n receive incoming RF signals from antennas 205a-205n, such as signals transmitted by a UE in network 100. Transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in transceivers 210a-210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. Controller / processor 225 can further process the baseband signals.
[0053] The transmit (TX) processing circuitry in transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. Transceivers 210a-210n up-convert the baseband or IF signal into an RF signal transmitted via antennas 205a-205n.
[0054] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the transceivers 210a-210n to receive UL channel signals and transmit DL channel signals according to well-known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 225 may support beamforming or directional routing operations, wherein outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively guide outgoing signals in the desired direction. The controller / processor 225 may support any of a wide variety of other functions within the gNB 102.
[0055] The controller / processor 225 is also capable of executing programs and other processes resident in the memory 230, such as processes supporting radio link monitoring in the FD system, as discussed in more detail below. The controller / processor 225 can move data into or out of the memory 230 as needed for the execution process.
[0056] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. Interface 235 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 (such as a cellular communication system supporting 5G / NR, LTE, or LTE-A), interface 235 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, interface 235 can allow the gNB 102 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. Interface 235 includes any suitable architecture supporting communication via a wired or wireless connection, such as Ethernet or a transceiver.
[0057] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.
[0058] although Figure 2 An example of gNB 102 is shown, but more can be found on... Figure 2 Various changes can be made. For example, gNB 102 can include... Figure 2 Each component, in any number as shown. Furthermore, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. In embodiments of this disclosure, gNB 102 can support or receive uplink transmissions for RACH-free handover procedures.
[0059] Figure 3 An example UE 116 according to an embodiment of the present disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 This disclosure is not intended to limit the scope of any particular implementation of the UE.
[0060] like Figure 3 As shown, UE 116 includes an antenna 305, a transceiver 310, and a microphone 320. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and memory 360. Memory 360 includes an operating system (OS) 361 and one or more applications 362.
[0061] Transceiver 310 receives incoming RF signals transmitted by the gNB of network 100 from antenna 305. Transceiver 310 down-converts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in transceiver 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry sends the processed baseband signal to speaker 330 (e.g., for voice data) or to processor 340 (e.g., for web browsing data). In embodiments of this disclosure, gNB 102 may support and facilitate uplink transmission without a RACH handover process via antenna 305.
[0062] The TX processing circuitry in transceiver 310 and / or processor 340 receives analog or digital voice data from microphone 320, or other outgoing baseband data (such as web data, email, or interactive video game data) from processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. Transceiver 310 up-converts the baseband or IF signal into an RF signal transmitted via antenna 305.
[0063] Processor 340 may include one or more processors or other processing devices and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control transceiver 310 to receive DL channel signals and transmit UL channel signals according to well-known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.
[0064] Processor 340 is also capable of executing other processes and programs residing in memory 360. For example, as discussed in more detail below, processor 340 can execute processes to perform uplink transmissions for RACH-free handover procedures. Processor 340 can move data into or out of memory 360 as needed to execute the processes. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.
[0065] The processor 340 is also coupled to an input 350 and a display 355, the input 350 including, for example, a touchscreen, a keyboard, etc. An operator of the UE 116 can use the input 350 to input data into the UE 116. The display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics from a website.
[0066] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), and another portion of the memory 360 may include flash memory or other read-only memory (ROM).
[0067] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, you can combine, further subdivide, or omit. Figure 3 The various components within it can be added, and additional components can be added as needed. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 can include any number of transceivers and signal processing chains, and can be connected to any number of antennas. Furthermore, although... Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.
[0068] Figure 4A and Figure 4B Example wireless transmit and receive paths according to this disclosure are shown. In the following description, transmit path 400 may be described as being implemented in a gNB (such as gNB 102), and receive path 450 may be described as being implemented in a UE (such as UE 116). However, it should be understood that receive path 450 may be implemented in the gNB, and transmit path 400 may be implemented in the UE. According to embodiments of this disclosure, transmit path 400 and receive path 450 may each support uplink transmission for RACH-free handover procedures.
[0069] The transmit path 400 includes a channel coding and modulation block 405, a serial-to-parallel (S to P) block 410, an N-size inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial (P to S) block 440, a cyclic prefix addition block 445, and an up-converter (UC) 430. The receive path 450 includes a down-converter (DC) 455, a cyclic prefix removal block 460, a serial-to-parallel (S to P) block 465, an N-size fast Fourier transform (FFT) block 470, a parallel-to-serial (P to S) block 475, and a channel decoding and demodulation block 480.
[0070] In transmit path 400, channel coding and modulation block 405 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. Serial-to-parallel block 410 converts (such as demultiplexes) the serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. IFFT block 415 of size N performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 440 converts (such as multiplexes) the parallel time-domain output symbols from IFFT block 415 of size N to generate a serial time-domain signal. Cyclic prefix addition block 445 inserts a cyclic prefix into the time-domain signal. Upconverter 430 modulates (such as upconverts) the output of cyclic prefix addition block 445 to an RF frequency for transmission via a radio channel. The signal can also be filtered at the baseband before being converted to the RF frequency.
[0071] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and UE 116 performs the opposite operation to that at gNB 102. Downconverter 455 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 465 converts the time-domain baseband signal into a parallel time-domain signal. An N-size FFT block 470 performs an FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial block 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.
[0072] Each of gNBs 101-103 can implement a transmit path 400 similar to that sent to UEs 111-116 in the downlink, and a receive path 450 similar to that received from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 can implement a transmit path 400 for sending to gNBs 101-103 in the uplink, and a receive path 450 for receiving from gNBs 101-103 in the downlink. In embodiments, according to this disclosure, transmit path 400 and receive path 450 are each configured to support uplink transmissions for RACH-free handover procedures.
[0073] Figure 4A and Figure 4B Each component in the system can be implemented using only hardware or a combination of hardware and software / firmware. As a specific example, Figure 4A and Figure 4B At least some components can be implemented in software, while others can be implemented using configurable hardware or a combination of software and configurable hardware. For example, FFT block 470 and IFFT block 415 can be implemented as configurable software algorithms, where the value of size N can be modified depending on the implementation method.
[0074] Furthermore, although described as using FFT and IFFT, this is by way of illustration only and should not be construed as limiting the scope of this disclosure. Other types of transforms, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, may be used. It should be understood that for the DFT and IDFT functions, the value of the variable N can be any integer (such as 1, 4, 3, 4, etc.), while for the FFT and IFFT functions, the value of the variable N can be any integer that is a power of two (such as 1, 4, 4, 8, 16, etc.).
[0075] although Figure 4A and Figure 4B An example of a wireless transmit and receive path is shown, but it is possible to modify it further. Figure 4A and Figure 4B Make various changes. For example, you can combine, further subdivide, or omit. Figure 4A and Figure 4B It includes various components and allows for the addition of additional components as needed. Furthermore, Figure 4A and Figure 4B This is intended to illustrate examples of the types of send and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.
[0076] The unit used for DL or UL signaling on a cell is called a time slot and may include one or more symbols. The bandwidth (BW) unit is called a resource block (RB). An RB includes multiple subcarriers (SCs). For example, a time slot may have a duration of one millisecond, and an RB may have a bandwidth of 180 kHz and include 12 SCs with an inter-SC spacing of 15 kHz. The subcarrier spacing (SCS) can be configured by the SCS. Determined as kHz. A cell of a subcarrier on a symbol is called a resource element (RE). A cell of an RB on a symbol is called a physical RB (PRB).
[0077] DL signals include data signals conveying information content, control signals conveying DL control information (DCI), and reference signals (RS), also known as pilot signals. The gNB transmits data information or DCI via the corresponding Physical DL Shared Channel (PDSCH) or Physical DL Control Channel (PDCCH). PDSCH or PDCCH can be transmitted over a variable number of time slot symbols, each including one time slot symbol. PDCCH transmission is performed via multiple control channel elements (CCEs) from a predetermined number of CCE sets known as CCE aggregation levels. PDSCH transmission is scheduled by the DCI format or by semi-persistent scheduling (SPS) configured by higher layers and activated by the DCI format. UE PDSCH reception provides one or more transport blocks (TBs), where each TB is associated with a Hybrid Automatic Repeat Request (HARQ) procedure and a Redundancy Version (RV). The HARQ procedure is indicated by the HARQ procedure number field in the DCI format used to schedule PDSCH reception or activate SPPSS reception, and the RV is indicated by the RV field in the DCI format when incremental redundancy is used to encode the TB. TB transmissions can be initial transmissions or retransmissions, as identified by the New Data Indicator (NDI) field in the DCI format of a scheduled PDSCH reception, which provides TB retransmissions for a given HARQ procedure number.
[0078] The gNB transmits one or more of several types of RS, including Channel State Information RS (CSI-RS) and Demodulation RS (DM-RS) (see also REF 1). CSI-RS is primarily intended for the UE to perform measurements and provide Channel State Information (CSI) to the gNB. For channel measurements or time tracking, the Non-Zero Power CSI-RS (NZP CSI-RS) resource is used. For Interference Measurement Reporting (IMR), the CSI Interference Measurement (CSI-IM) resource is used (see also REF 3). The CSI-IM resource can also be associated with Zero Power CSI-RS (ZP CSI-RS) configuration. The UE can determine CSI-RS reception parameters via DL control signaling or higher-layer signaling, such as Radio Resource Control (RRC) signaling from the gNB (see also REF 5). DM-RS is typically transmitted only within the BW of the corresponding PDCCH or PDSCH, and the UE can use DM-RS to demodulate data or control information.
[0079] The UE typically monitors multiple candidate locations for corresponding potential PDCCH reception to decode multiple DCI formats in the time slot, such as those described in REF 3. The DCI format includes Cyclic Redundancy Check (CRC) bits to allow the UE to verify the correct detection of the DCI format. The DCI format type is identified by a Radio Network Temporary Identifier (RNTI) that scrambles the CRC bits (see also REF 2).
[0080] For DCI formats that schedule PDSCH or PUSCH to a single UE, the RNTI can be the cell RNTI (C-RNTI), the configured scheduling RNTI (CS-RNTI), or the MCS-C-RNTI, and is used as the UE identifier. For brevity, only the C-RNTI will be mentioned below when necessary. The UE typically receives / monitors PDCCHs according to its UE-specific search space (USS) to detect DCI formats with CRCs scrambled by the C-RNTI. For DCI formats 0_0 and 1_0, which schedule PUSCH transmission and PDSCH reception to the UE respectively, the UE can be additionally configured to monitor the corresponding PDCCHs according to the common search space (CSS). For DCI formats 0_1 and 0_2, primarily used for scheduling PUSCH transmission, or for DCI formats 1_1 and 1_2, primarily used for scheduling PDSCH reception, the UE monitors the corresponding PDCCHs according to the USS. PDCCH monitoring implies the reception of PDCCH candidates and the decoding of potential DCI formats.
[0081] For the DCI format of the PDSCH that dispatches System Information (SI), the RNTI can be SI-RNTI. For the DCI format of the PDSCH that dispatches to provide Random Access Response (RAR), the RNTI can be RA-RNTI. For the DCI format of the PDSCH that dispatches to provide paging information, the RNTI can be P-RNTI. The UE monitors the PDCCH used for these DCI formats according to the corresponding CSS on the primary cell. There are also several other RNTIs provided to the UE via UE-specific RRC signaling, and these RNTIs are associated with DCI formats that provide various control information and have corresponding PDCCHs that the UE monitors according to Type 3 CSS on the primary or secondary cell. Such DCI formats include DCI format 2_0, DCI format 2_2, DCI format 2_3, etc. DCI format 2_0 provides a time slot structure based on DL, UL, or flexible / reserved symbols on multiple time slots. DCI format 2_2 provides transmit power control (TPC) commands for PUSCH or PUCCH transmissions. DCI format 2_3 provides TPC commands for SRS transmissions and also potentially triggers SRS transmissions on multiple cells. The corresponding CSS is called Type 3-PDCCH CSS.
[0082] UL signals also include data signals conveying information content, control signals conveying UL control information (UCI), DM-RS associated with data or UCI demodulation, phase tracking RS (PT-RS) for phase tracking in symbols of the PUSCH, probe RS (SRS) enabling the gNB to perform UL channel measurements, and random access (RA) preamble enabling the UE to perform random access (see also REF 1). The UE transmits data information or UCI via the corresponding Physical UL Shared Channel (PUSCH) or Physical UL Control Channel (PUCCH). The PUSCH or PUCCH can be transmitted on a variable number of symbols in a time slot comprising one symbol. When the UE transmits both data information and UCI simultaneously, the UE can multiplex both in the PUSCH, or, depending on the UE's capabilities, at least when transmitting on different cells, transmit both a PUSCH with data information and a PUCCH with UCI.
[0083] UL RS includes DM-RS, PT-RS, and SRS. DM-RS is typically transmitted within the BW of the corresponding PUSCH or PUCCH. The gNB can use DM-RS to demodulate information in the corresponding PUSCH or PUCCH. SRS is transmitted by the UE to provide UL CSI to the gNB, and for TDD systems, it also provides PMI for DL transmission. In addition, the UE may transmit the Physical Random Access Channel (PRACH) as part of the random access procedure or for other purposes.
[0084] UCI includes a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) message indicating whether a TB or Code Block Group (CBG) in the PDSCH has been correctly or incorrectly decoded, a Schedule Request (SR) indicating whether the UE has data to transmit in its buffer, and a CSI report enabling the gNB to select appropriate parameters for PDSCH / TB or PDCCH / DCI format transmissions to the UE. The UE transmits the PUCCH on the primary cell of the cell group. The HARQ-ACK message is an affirmative acknowledgment (ACK) if the TB is correctly decoded, or a negative acknowledgment (NACK) if the TB is incorrectly decoded. ACK can be represented by a binary "1" value, and NACK can be represented by a binary "0" value.
[0085] DL reception and UL transmission performed by the UE can be configured to occur in the corresponding DL bandwidth portion (BWP) and UL BWP. The DL / UL BWP is less than or equal to the DL / UL bandwidth of the serving cell. DL transmissions from the gNB and UL transmissions from the UE can be based on Orthogonal Frequency Division Multiplexing (OFDM) waveforms, including variants using DFT precoding, which are referred to as DFT-Extended-OFDM (see also REF 1).
[0086] Figure 5 A block diagram of an example transmitter structure 500 using OFDM according to this disclosure is shown. Figure 5 The example transmitter structure 500 shown is for illustrative purposes only. Figure 5 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function. Figure 5 This disclosure is not intended to limit the scope of any particular implementation of the example transmitter structure 500.
[0087] Information bits (such as DCI bits or data bits 510) are encoded by encoder 520, rate-matched to the assigned time / frequency resources by rate matcher 530, and modulated by modulator 540. Subsequently, the modulated coded symbols and DM-RS or CSI-RS 550 are mapped to SC 560 via SC mapping unit 565, an inverse fast Fourier transform (IFFT) is performed via filter 570, a cyclic prefix (CP) is added via CP insertion unit 580, and the resulting signal is filtered via filter 590 and transmitted via radio frequency (RF) unit 595. In this embodiment, transmitter structure 500 can be used to support enhanced CSI measurements and network-adapted reporting.
[0088] Figure 6 A block diagram of an example receiver structure 600 using OFDM according to this disclosure is shown. Figure 6 The example receiver structure 600 shown is for illustrative purposes only. Figure 5 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function. Figure 6 This disclosure is not intended to limit the scope of any particular implementation of the example receiver structure 600.
[0089] The received signal 610 is filtered by filter 620, the CP removal unit removes the CP 630, filter 640 applies a Fast Fourier Transform (FFT), SC demapping unit 650 demaps the SC selected by BW selector unit 655, the received symbols are demodulated by channel estimator and demodulator unit 660, rate dematcher 670 restores rate matching, and decoder 680 decodes the obtained bits to provide information bits 690. In this embodiment, receiver structure 600 can be used to support enhanced CSI measurements and network-adapted reporting.
[0090] The UE (e.g., UE 114) multiplexes HARQ-ACK information associated with a DCI format (such as the DCI format for scheduling PDSCH reception) in the PUCCH. The UE transmits the PUCCH in the slot indicated by the value of the PDSCH-HARQ feedback timing indicator field in the last DCI format associated with the HARQ-ACK information and indicating the slot. The value K1 of the field can come from a set of slot timing values K1, or it can be indicated by a higher layer, as in the case of SPS PDSCH reception as described in REF3. When the UE (e.g., UE 114) has received UE-specific RRC signaling providing a PUCCH resource set, the UE determines the PUCCH resource set for multiplexing in the PUCCH based on the UCI payload and determines the PUSCH resources within the PUCCH resource set based on the PUCCH resource index (PRI) in the DCI format.
[0091] A random access (RA) procedure can be initiated to achieve one of the following purposes: establishing an RRC connection (to transition from RRC_IDLE to RRC_CONNECTED), re-establishing an RRC connection after a radio link failure (RLF), requesting System Information on Demand (SI), UL synchronization, scheduling request (SR), location, or link recovery (also known as beam fault recovery (BFR)). The physical random access procedure is triggered when a higher layer or PDCCH command requests a PRACH transmission. Random access (RA) can operate in two modes: (i) contention-based random access (CBRA), where UEs within the serving cell can share the same RA resources, thus creating the possibility of conflicts between RA attempts from different UEs; and (ii) contention-free random access (CFRA), where a UE has dedicated RA resources indicated by the serving gNB and can not share them with other UEs, thereby avoiding RA conflicts.
[0092] The 4-step random access procedure, also known as the Type 1 L1 random access procedure, includes: Step 1: The UE sends a Physical Random Access Channel (PRACH) preamble (Msg1); Step 2: The gNB sends a Random Access Response (RAR) message (Msg2) using the PDCCH / PDSCH; Step 3: The UE sends a contention resolution message and, where applicable, a PUSCH scheduled by the RAR UL (Msg3); and Step 4: The gNB sends a contention resolution message (Msg4). An alternative RA procedure may consist of only two steps and is referred to herein as a 2-step RA or Type 2 L1 random access procedure. In a 2-step RA, Msg1 and Msg3 are combined into MsgA for transmission, and Msg2 and Msg4 are combined into MsgB for reception. MsgA combines the PRACH preamble transmission during the RACH timing (RO) and the PUSCH transmission during the PUSCH timing (PO).
[0093] Before initiating a physical random access procedure, Layer 1 receives a set of SS / PBCH block indices from higher layers and provides the corresponding set of RSRP measurements to higher layers. Layer 1 receives the configuration of PRACH transmission parameters (PRACH preamble format, time resources for PRACH transmission, and frequency resources). The UE transmits PRACH using the selected PRACH format at a transmission power that depends on whether the PRACH transmission is triggered upon request from a higher layer or in response to the UE detecting a PDCCH command, and on the action associated with the PDCCH command.
[0094] The RAR is the PDCCH / PDSCH transmission received by the UE on the DL BWP of the SpCell: the initial DL BWP of the PCell / SpCell for initial access (i.e., (re)establishing an RRC connection), or the active DL BWP of the SpCell (with the same BWP index as the active UL BWP) for other random access triggered besides initial access. If the active DL BWP index (of the SpCell) is not equal to the active UL BWP index (of the serving cell), then the active DL BWP is switched to one with the same BWP index. The SCS used for PDCCH in the RAR message is the SCS used for the Type 1-PDCCH CSS set. The SCS used for any future PDSCH is also the same SCS used for PDSCH in the RAR, unless the UE is configured with an SCS. The PDCCH used for RAR is DCI format 1_0. The UE monitors this DCI format 1_0 within the common search space (CSS) set of type 1-PDCCH for SpCells identified by the RA-RNTI during a configured time window, or, for BFRs with CFRA, within the search space indicated by the recoverySearchSpaceId of the SpCell identified by the C-RNTI. The PDSCH portion of the RAR contains the gNB response.
[0095] For BFR based on contention-free random access (CFRA), receiving a PDCCH within the time window and correctly addressing it to the C-RNTI in the SpCell's indication search space is sufficient to consider RAR successful. For other cases, such as contention-based random access (CBRA) and SI requests, RAR is successful if (i) a PDCCH in the SpCell's type 1-PDCCH common search space (CSS) set is received and addressed to the RA-RNTI within the configured time window; and (ii) the corresponding PDSCH is correctly decoded; and (iii) the MAC RAR contained in the PDSCH portion of the RAR contains a random access preamble ID (RAPID); and (iv) the RAPID in the MAC RAR matches the preamble selected and transmitted by the UE in Msg1. Then, for the serving cell where the PRACH preamble / Msg1 is transmitted, the UE applies TA to adjust / correct the timing between the UE and gNB, stores the TC-RNTI for future transmissions, and processes the RAR UL permission to transmit Msg3.
[0096] For CFRA or SI requests, correct reception of Msg2 / RAR is the final step in the random access procedure. For CBRA, multiple UEs may have used the same preamble, and further steps are required to resolve contention. Furthermore, for random access prior to the RRC_CONNECTED state (i.e., for initial access), the UE and gNB need to exchange further information to establish a connection: an uplink PUSCH transmission (Msg3) for the contention resolution request and possibly also for the connection establishment request, and a downlink transmission (Msg4) for the contention resolution response and possibly also for the connection establishment response. If the UE receives Msg4 within a time window after the transmission of Msg3, and if the UE does not yet have a C-RNTI, the contention resolution ID in Msg4 matches the ID transmitted by the UE in Msg3, then contention resolution (and connection establishment, if applicable) is considered successful. Otherwise, the random access channel (RACH) attempt is considered unsuccessful, and the UE needs to make another RACH attempt unless the configured maximum number of RACH attempts has been exhausted, in which case the entire random access procedure is declared unsuccessful.
[0097] In response to a PUSCH transmission scheduled by RAR UL permission when the UE (e.g., UE 113) has not yet been provided with a C-RNTI, the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding TC-RNTI of the PDSCH transmission, which includes the UE contention resolution identifier. In response to the reception of a PDSCH with the UE contention resolution identifier, the UE sends a HARQ-ACK message in the PUCCH. The PUCCH transmission occurs within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol of the received PDSCH and the first symbol of the corresponding PUCCH transmission with the HARQ-ACK message is equal to N. T,1 +0.5 milliseconds. N T,1 It is the duration of N1 symbols corresponding to the PDSCH processing time of UE processing capability 1 when additional PDSCHDM-RS is configured.
[0098] When a UE (e.g., UE 113) transmits a PUCCH providing HARQ-ACK information in response to a PDSCH reception scheduled by DCI format 1_0 with a CRC scrambled by TC-RNTI, the PUCCH resource set is provided by pucch-ResourceCommon through indexes of rows in a table used for transmitting HARQ-ACK information on the PUCCH in the initial UL BWP. This table comprises sixteen rows corresponding to sixteen resources, each row corresponding to the PUCCH format, first symbol, duration, PRB offset, and a cyclic shift index set for PUCCH transmission. If a UE provides HARQ-ACK information in a PUCCH transmission in response to the detection of a scheduled PDSCH reception or with associated HARQ-ACK information but without a scheduled PDSCH reception DCI format, the UE will have index r PUCCH , 0≤r PUCCH PUCCH resources with a value of ≤15 are determined as , where N CCE It is the number of CCEs in the CORESET received by the PDCCH with DCI format, n CCE,0 It is the index of the first CCE used for PDCCH reception, and It is the value of the PUCCH resource indicator field in the DCI format.
[0099] When a PUSCH transmission scheduled by RAR UL permission is detected, or when a corresponding PUSCH retransmission with a DCI format 0_0 scrambled by a CRC provided in the corresponding RAR message is detected, the UE may assume that the PDCCH carrying the DCI format has the same DM-RS antenna port quasi-co-address attributes as the SS / PBCH block associated with the PRACH by the UE, regardless of whether the UE is provided with a CORESET TCI state for the UE to receive PDCCHs with the DCI format.
[0100] In the following text, unless otherwise explicitly stated, parameter values provided by higher layers include those provided by System Information Blocks (SIBs) (such as SIB1), or by public RRC signaling, or by UE-specific RRC signaling. The following description discusses satellite implementation of transparent payloads, but these descriptions also apply directly to regenerable payloads. The following descriptions and implementations for satellites are also directly applicable to or adapted to any airborne platform. Throughout this disclosure, the terms source or target satellite and source or target gNB are used interchangeably to refer to any component (or set of components) configured to provide radio access to a network to a remote terminal.
[0101] The following descriptions and embodiments for non-terrestrial networks (NTN) also apply directly to terrestrial networks (TN), and vice versa. The satellite's function can be the same as that of a gNB in a TN, or it can be adjusted to account for the change in the LEO satellite's coverage area (footprint) due to the satellite's movement relative to the Earth. The GEO satellite's coverage area is fixed, similar to a cell in a TN.
[0102] Ensuring reliable reception of UL channels is particularly challenging in NTNs compared to TNs due to the limited link budget associated with significant path loss. NTNs are networks that utilize RF resources carried on satellites or unmanned airborne service (UAS) platforms (e.g., Satellite 104). NTNs comprise radio links between satellites, satellite gateways, and satellite or UAS platforms, and radio links between UEs and satellites or UAS platforms. Satellites can be geostationary orbit (GEO) satellites served by one or more satellite gateways deployed across satellite target coverage, or low Earth orbit (LEO) satellites continuously served by one or more satellite gateways at a time. Satellites or UAS platforms can implement transparent or regenerated (with onboard processing) payloads. Satellites or UAS platforms typically generate several beams over a given service area defined by their field of view, which depends on the onboard antenna pattern and elevation angle. The coverage area of the beams has an elliptical shape and is considered a cell within the terrestrial network.
[0103] 3GPP (3rd Generation Partnership Project) has developed technical specifications and standards to define a new 5G radio access technology known as 5G NR (New Radio). In Release 17, 5G NR supports Non-Terrestrial Networks (NTNs) as a vertical function. The NTN provides non-terrestrial NR access to the UE via an NTN payload (e.g., satellite 104 operating within the NTN) and an NTN gateway. The NTN payload transparently forwards radio protocols received from the UE (via the service link, i.e., the radio link between the NTN payload and the UE) to the NTN gateway (via the feeder link, i.e., the radio link between the NTN gateway and the NTN payload) and vice versa. Given the NTN's ability to provide wide coverage and reliable service, it is envisioned to ensure ubiquitous service availability and continuity. For example, the NTN can support communication services in unserved areas not covered by traditional terrestrial networks, in underserved areas experiencing limited communication services, for devices and passengers on mobile platforms, and for future rail / marine / aviation communications, etc. To support NTN in 5G NR, various features need to be introduced or enhanced to accommodate the nature of radio access to NTN, which differs from that of terrestrial networks (TN), such as larger cell coverage, longer propagation delays, and non-static cells / satellites.
[0104] In an NTN, the NTN payload can be GSO (Geostationary Orbit), which is a geocentric orbit at approximately 35,786 km above the Earth's surface and synchronized with the Earth's rotation, or NGSO (Low Earth Orbit), which is a low Earth orbit (LEO) at an altitude between approximately 300 km and 1,500 km and a medium Earth orbit (MEO) at an altitude between approximately 7,000 km and 25,000 km. Depending on the NTN payload, three types of service links are supported: Earth-fixed, provided by beams that continuously cover the same geographic area (e.g., in the case of GSO satellites); Quasi-Earth-fixed, provided by beams that cover one geographic area for a limited time and a different geographic area for another time (e.g., in the case of NGSO satellites generating steerable beams); and Earth-moving, provided by beams whose coverage area slides across the Earth's surface (e.g., in the case of NGSO satellites generating fixed or unsteerable beams). Using NGSO satellites, a gNB can provide quasi-Earth-fixed cell coverage or Earth-moving cell coverage, while a gNB operating using GSO satellites can provide Earth-fixed cell coverage. Due to the different attributes of GSO and NGSO, NTN can support different types of cells: fixed earth cells, quasi-fixed earth cells, and mobile earth cells. For a certain type of NTN payload / cell, it is expected that the UE supports specific features or functions for radio access.
[0105] For cell selection / reselection, the UE typically measures neighboring cells to search for suitable or acceptable cells to camp on. The gNB (e.g., gNB 102) can provide configuration regarding neighboring cell measurements and cell (re)selection. This configuration may include common cell reselection information for intra-frequency, inter-frequency, and / or inter-RAT cell reselection, per-frequency cell reselection information (i.e., information about other NR frequencies and inter-frequency neighboring cells related to cell reselection), and cell-specific cell reselection information for intra-frequency, inter-frequency, and / or inter-RAT neighboring cells.
[0106] For a UE in a connected state (e.g., RRC_CONNECTED) (e.g., UE 114), the gNB can provide measurement configurations for the measurement object (e.g., adjacent cells within or between frequencies). Based on the UE's measurement results, the gNB can prepare a handover (HO) from the current serving cell (i.e., the source cell) to the target cell and trigger HO execution by sending an HO command in an RRC message (e.g., RRCReconfiguration). The gNB can also prepare a conditional HO (CHO) with multiple candidate cells for the UE and trigger CHO evaluation by sending a CHO configuration in an RRC message (e.g., RRCReconfiguration).
[0107] When a HO is configured, the UE follows a contention-free procedure using a dedicated RACH preamble, or a contention-based procedure via RACH to access the target cell if the dedicated RACH preamble is unavailable. The UE uses the dedicated preamble until the handover procedure is complete (successfully or unsuccessfully). In an NTN, due to the large distance between the UE (e.g., UE 114) and the gNB (e.g., gNB 102), HO delays and interruptions caused by message exchange between the UE and the gNB can be significant. Furthermore, due to the large size of NTN cells, for quasi-fixed cells, a large number of UEs may need to perform HOs almost simultaneously. To reduce HO delays and overhead, a RACH-free HO can be used in an NTN. If a RACH-free HO is configured, the UE accesses the target cell via an uplink clearance provided to the UE in an RRC message. If the UE does not receive an uplink clearance from the source gNB in an RRC message, the UE monitors the target cell's PDCCH for dynamic scheduling. If access to the target cell using RACH or without RACH fails within a certain time, the UE can use a suitable cell to initiate radio link failure recovery.
[0108] Figure 7A and Figure 7B Examples of satellite coverage in an NTN according to various embodiments of this disclosure are shown. For example, satellites 701 and 702 may be used as... Figure 1 An example of satellite 104, which is part of network 100. Figure 7A and Figure 7B The depiction of satellite coverage in the text is for illustrative purposes only; other embodiments may be used without departing from the scope of this disclosure.
[0109] In one example, a handover from a source cell to a target cell involves a satellite switching from a source satellite with source coverage area to a target satellite with target coverage area. For example... Figure 7A As shown, the first satellite 701 and the second satellite 702 provide coverage over the same area or satellite coverage area 703. Over time, the satellite coverage area changes due to the relative movement of the satellite and the Earth, and the same area has coverage from the first satellite in a first time period and coverage from the second satellite in a second time period. The first and second time periods may overlap within time period T (referred to as soft satellite handover) or may not overlap (referred to as hard satellite handover). This is a typical example of an NGSO scenario.
[0110] In one example, the satellite operates using multiple beams within its coverage area. Each beam within the coverage area can be considered a cell, and the handover from the source cell to the target cell occurs within the coverage area encompassing both the source and target cells. Figure 7B As shown, satellite 710 uses a source beam to provide coverage on source cell 720 and a target beam to provide coverage on target cell 730. A handover from the source cell to the target cell occurs when the satellite turns its corresponding beam on and off. Whether a beam within the satellite's coverage area can be considered a cell depends on the configuration. The example in Figure 7 is also directly applicable to terrestrial networks. For example, the gNB turning a beam on and off triggers a UE beam change and provides the UE with an indication of the target beam that can be used based on UE measurements reported to the gNB. For example, the gNB triggers a UE serving cell change and provides information about the configuration of the target cell that can be used based on UE measurements reported to the gNB.
[0111] The following description and examples are directly applicable to Figure 7A and Figure 7B The example scenario shown illustrates a RACH-free handover process.
[0112] When access to the first target cell using a no-RACH procedure fails within a specific time period, the UE initiates a RACH or no-RACH procedure on a second cell different from the first cell. Whether the UE initiates a RACH or no-RACH procedure on the second cell depends on the configuration, for example, provided by the higher-layer parameter `rach-lessHO` present in `reconfigurationWithSync`, and depends on the RSRP measurement being greater than one or more thresholds. `rach-lessHO` can be associated with a non-terrestrial network, a terrestrial network, or both; the RSRP measurement can be associated with SS / PBCH block reception or CSI-RS reception; and the RSRP thresholds are provided by higher-layer parameters, such as `rach-lessHO`, the configuration for initial uplink transmission to the target cell, or higher-layer parameters or SIBs (e.g., SIB19) for the RACH procedure. The UE may receive information from the source cell or the target cell regarding a first SS / PBCH block index set in a first configuration and a second SS / PBCH index set in a second configuration, and the second set may be a different set from the first set or included in the first set. The first and second sets may also be received from different cells.
[0113] When access to a target cell (also known as a candidate cell or candidate target cell) using a RACH-free handover procedure is in progress, or during a specific time period during which the UE attempts to access the target cell using a RACH-free handover procedure, or before completing an ongoing RACH-free handover procedure, where, depending on the configuration, the UE may or may not indicate to the upper layers that a RACH-free handover has been successfully completed, or the target gNB may or may not indicate to the upper layers that a RACH-free handover has been successfully completed: (i) in one example, the UE may initiate a RACH procedure to a cell different from the target cell; (ii) in one example, the UE may initiate a RACH procedure to the same target cell; (iii) in one example, the UE may not initiate a RACH procedure to the same target cell, but may initiate a RACH procedure to a cell different from the target cell; (iv) in one example, the UE may not initiate a RACH procedure to the same or different cells, or a combination of the above examples. The specific time period may be a period before a timer expires, and this specific time period may be the same or different for both RACH and RACH-free handover procedures, or for subsequent RACH-free handover procedures in the same or different cells.
[0114] The UE can receive information required for the RACH-free handover process to the target satellite or cell from the source satellite or cell in the SIB. This information may include the target satellite's configuration for uplink transmission, the SS / PBCH block index, and / or the time offset for detecting the target satellite's SS / PBCH block. After the UE detects the target satellite's SS / PBCH block and acquires DL synchronization, the UE receives the information from the target satellite in the SIB. The UE resets the N_TA value to 0 before the initial UL transmission, or, if configured, sets the N_TA value according to the value provided by the RRC. The initial UL transmission to the target satellite during the RACH-free handover process can be performed using dynamic uplink grants, or, if configured, by uplink grants pre-allocated by the RRC.
[0115] For example, the source satellite provides information on more than one candidate satellite for the RACH-free handover process. The RACH-free handover signaling provided via RRC may include beam information (also known as spatial configuration information) and N_TA information for N candidate satellites, and the UE selects a target satellite from the N candidate satellites, determines the target beam and target N_TA value corresponding to the target satellite and associated target cell from the configuration, monitors the PDCCH for reception of DCI format including dynamic licensing for PUSCH transmission using the target beam, and transmits PUSCH using the target beam and target N_TA.
[0116] For example, the UE can receive a configuration for N candidate satellites and receive the SS / PBCH block index and / or time offset for each of the N candidate satellites. The UE can perform measurements based on the SS / PBCH blocks from the candidate satellites and select a target satellite from the N candidate satellites for the RACH-free handover procedure based on the measurement being greater than the RSRP threshold (if configured). For all N candidate satellites, depending on the RACH-free configuration, the initial uplink transmission for the RACH-free handover procedure to the target satellite will be performed using either dynamic uplink grant or a configured uplink grant as configured by the RRC. It is possible that for some of the N candidate satellites, the initial uplink transmission for the RACH-free handover procedure will be performed using dynamic uplink grant, and for some of the other N candidate satellites, the initial uplink transmission for the RACH-free handover procedure will be performed using a configured uplink grant as configured by the RRC.
[0117] In one sub-example, the UE selects a first candidate satellite. For this first candidate satellite, dynamic licensing will be used to perform the initial uplink transmission for initiating the first RACH-free handover procedure. If the first RACH-free handover procedure fails, the UE selects a second candidate satellite. For this second candidate satellite, dynamic licensing (if configured) will be used to perform the initial uplink transmission. The UE will select a candidate satellite configured with UL dynamic licensing for the first and subsequent RACH-free handover attempts.
[0118] In one sub-example, the initial uplink transmission used to initiate the first RACH-free handover procedure is configured without dynamic clearance, and the UE uses UL clearance configured via RRC or provided via PDCCH.
[0119] In one sub-example, the UE is provided with information for RACH-free handover to multiple candidate satellites, and the initial uplink transmission is configured with dynamic clearance for a first set of candidate satellites and configured clearance for a second set of candidate satellites. The UE may be provided with a first RRC parameter and a second RRC parameter, the first RRC parameter including information for a RACH-free handover procedure for the initial transmission with dynamic clearance for the first set of candidate satellites, and the second RRC parameter including information for a RACH-free handover procedure for the initial transmission with configured clearance.
[0120] Figure 8 A UE procedure 800 for RACH-free handover to a target satellite according to various embodiments of the present disclosure is shown. Figure 8 The process 800 can be made by Figure 1 Any of UE 111-116 (such as Figure 3Execution of UE 116). Figure 8 The process 800 is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.
[0121] Procedure 800 begins with, in 810, the UE receiving from the source satellite in the SIB the information required for a RACH-free handover procedure for one or more candidate satellites, and additionally receiving the SS / PBCH block index and time offset for each candidate satellite. In 820, the UE performs measurements based on the corresponding SS / PBCH block index and time offset of the candidate satellite and selects the target satellite for the RACH-free handover. In 830, the UE determines the N_TA value, where the N_TA value is provided by the source satellite through higher-layer parameters (if configured), otherwise the N_TA value is set to zero. In 840, the UE determines UL resources from the UL resources provided by the configured uplink grant for PUSCH transmission. In 850, the UE transmits the PUSCH in the determined UL resources using the spatial settings provided by the source satellite in higher-layer parameters and / or associated with the SS / PBCH block (reception) of the target satellite. Instead of 820, the UE can perform measurements based on the corresponding SS / PBCH block index and time offset of the candidate satellite, and report the measurements to the source satellite using MAC CE or RRC signaling. This source satellite triggers a RACH-free handover procedure for the first target satellite from the candidate satellite. It is possible that the target satellite determination is completed at the source satellite or at the corresponding source gNB on the ground.
[0122] Similar to Figure 8 In a RACH-free handover process, a UE can hand over from a source cell to a target cell, where both the source and target cells cover areas within satellite coverage. The source cell is associated with a source beam, and the target cell is associated with a target beam. The UE can receive the information required for the RACH-free handover process in the target cell via RRC signaling, and also receives information about the target beam for the first UL transmission in the target cell. Beam information can be provided by RACH-free RRC parameters or MACCE. The triggering of the RACH-free handover process can be indicated by MACCE.
[0123] When the target gNB indicates the completion of the RACH-free handover by providing HARQ-ACK information for the transport block of the initial transmission performed by the UE in the target cell, it is assumed that the RACH-free handover process has been successfully completed. If the HARQ-ACK information value is ACK, the UE assumes that the transport block has been correctly decoded; otherwise, the UE assumes that the transport block has not been correctly decoded. The target gNB may not provide HARQ-ACK information for the transport block of the initial transmission performed by the UE in the target cell and instead send a PDSCH scheduled by the PDCCH. In response to the reception of the PDSCH, the UE sends a PUCCH with HARQ-ACK information. When sending the PUCCH, it is assumed that the RACH-free handover has been completed, and the upper layers can be notified.
[0124] When a UE (e.g., UE 114) is provided with a RACH HO-free configuration, in order to improve the reception reliability of PUSCH sent by the UE at the target gNB (e.g., gNB 102) when the UE is in the RRC_CONNECTED state in the source cell, the UE can send duplicated PUSCHs to the target gNB, where the PUSCH is scheduled by UL permission in the RACH HO-free configuration provided by the source gNB or by DCI format sent by the target gNB. The UE can also send duplicated PUCCHs to the target gNB, where the PUCCH provides HARQ-ACK information in response to PDSCH reception before receiving duplicated PUCCH resource information via UE-specific RRC signaling.
[0125] Therefore, it is necessary to indicate to the UE the number of repetitions of PUSCH transmission during a no-RACH HO process. Another requirement is to indicate to the UE the number of repetitions of PUCCH transmission when no PUCCH resources are provided to the UE via UE-specific RRC signaling during a no-RACH HO period, or during the first PUCCH transmission after the first PUSCH transmission in the target cell.
[0126] When a UE (e.g., UE 114) is configured with no RACH HO by a source gNB, it can be provided with a UL permission to transmit a PUSCH to a target gNB in the no RACH HO configuration. This transmission can correspond to a configured permission type 1, which is semi-statically configured to operate upon receiving higher-layer parameters without detecting the UL permission in the DCI. The UE receiving the no RACH configuration is in a connected state in the source cell, and it is assumed that if the UE can transmit a repeating Msg3 PUSCH during a 4-step RA procedure, or a repeating MsgA PUSCH during a 2-step RA procedure, then the UE can also transmit a repeating PUSCH configured for no RACH HO. The no RACH HO configuration can include a value for the number of repetitions for the configured PUSCH transmission, or can include more than one value, and the UE can determine which value to use based on RSRP measurements or based on RSRP measurements and an RSRP threshold provided in the no RACH HO configuration. It is possible that when multiple values for the number of repetitions are provided, if the first transmission attempt fails, the first value is used for the first PUSCH transmission, and the second value is used for the second PUSCH transmission. For example, the UE can be configured with more than one UL license, and for each UL license, the UE can be provided with a number of repetitions that may be the same as or different from the number of repetitions associated with another UL license, or the UE can be provided with a single value for the number of repetitions associated with all configured UL licenses.
[0127] In embodiments, spatial setting information for repeated PUSCH transmissions is also provided to the UE (e.g., UE 114) in a RACH-free configuration. For example, a first spatial setting associated with a first UL license and a first number of repetitions in a first configuration, and a second spatial setting associated with a second UL license and a second number of repetitions in a second configuration, are provided to the UE, and the UE uses the corresponding spatial setting to transmit repeated PUSCHs. In embodiments, the spatial setting information is associated with both the first and second UL licenses, and if the first PUSCH transmission corresponding to the first UL license fails, the UE uses the same spatial setting to transmit the second PUSCH transmission corresponding to the second UL license. When multiple UL licenses are provided to the UE, the associations of the multiple licenses with the same or different number of repetitions or the same or different spatial settings can be different. In a first example, the same spatial setting is used over time intervals that may include multiple PUSCH transmissions associated with corresponding multiple UL licenses, and each PUSCH transmission has a corresponding number of repetitions. In a second example, the same number of repetitions is used over time intervals that may include multiple PUSCH transmissions associated with corresponding multiple UL licenses, and each PUSCH transmission has a corresponding spatial setting.
[0128] When a UE (e.g., UE 114) is configured with a no-RACH HO by the source gNB and no UL clearance for transmitting PUSCH to the target gNB is provided to the UE in the no-RACH HO configuration, the UE monitors PDCCHs from the target cell that include the UL clearance for PUSCH transmission. PUSCH transmissions can be scheduled by repetitions, and the number of repetitions can be included in the scheduling DCI format, or the DCI format can include a field providing a row index of a table that provides the number of repetitions. For no-RACH procedures in an NTN, the number of repetitions can be included in the no-RACH HO configuration, and the UL clearance is not included in the no-RACH HO configuration. When the UE (e.g., UE 114) receives the UL clearance from the target gNB, the UE transmits the PUSCH with the configured number of repetitions. The UE can indicate the number of repetitions for PUSCH transmission to the target gNB. The UE can use a 2-bit field to indicate one of four possible values configured in the SIB, or a 1-bit field to indicate one of two possible values, or a 1-bit field to indicate whether the PUSCH is repeated. If the PUSCH is repeated, this value can be a predetermined value or configured in the SIB. It is also possible that when the UE is configured with no RACH HO in the NTN and provides UL clearance in the PDCCH received from the target gNB, the number of repetitions can be a predetermined number, a number configured in the SIB, a number provided in the no RACH HO configuration, or a number provided in the NTN configuration.
[0129] Figure 9 A UE procedure 900 for RACH-free handover with repeated first uplink transmissions scheduled by DCI format received in the target cell is illustrated according to various embodiments of the present disclosure. Figure 9 The UE process 900 can be handled by Figure 1 Any of UE 111-116 (such as Figure 3 Execution of UE 116). Figure 9 The process 900 is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.
[0130] Procedure 900 begins with, in 910, the source gNB provides the UE with a RACH-free handover configuration, which includes the spatial settings and repetition count for the first PUSCH transmission in the target cell from the SIB. In 920, the UE monitors the provision of a PDCCH in DCI format, which uses the spatial settings in the target cell to schedule the transmission of the first PUSCH. In 930, the UE transmits the first PUSCH with the repetition count using the spatial settings in the target cell.
[0131] Figure 10 A RACH-free handover procedure 1000 for a target cell with repeated first uplink transmissions scheduled by configured licenses is illustrated according to various embodiments of the present disclosure. Figure 10 The UE process 1000 can be performed by Figure 1 Any of UE 111-116 (such as Figure 3 Execution of UE 116). Figure 10 The process 1000 is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.
[0132] Process 1000 begins with the following steps: In 1010, the source gNB provides the UE with a RACH-free handover configuration in the SIB. In 1020, the source gNB provides the UE with the configured permission settings and the number of repetitions for the first PUSCH transmission in the target cell from the SIB. In 1030, the UE determines the spatial settings based on SS / PBCH block reception and the RSRP threshold provided in the SIB. In 1040, the UE transmits the first PUSCH with the configured repetition count according to the spatial settings in the target cell.
[0133] When a UE is configured by the source gNB to have a no-RACH HO procedure and is configured to transmit an initial PUSCH with K repetitions in multiple slots on the target cell, the UE can also be configured to have AvailableSlotCounting enabled. The UE will then transmit the initial PUSCH repetitions in multiple slots, and if at least one of the symbols transmitted in a slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided), or a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, the slot is not counted in the number of slots used for the K slots with repetitions of the initial PUSCH transmission.
[0134] When the UE is configured by the source gNB to have a no-RACH HO procedure and is configured to transmit an initial PUSCH with K repetitions on multiple time slots on the target cell, the UE can also be configured to have pusch-DMRS-Bundling enabled, and the procedure in Section 6.1.7 of TS38.214 v18.1.0 applies to initial PUSCH transmissions with repetitions on the target cell.
[0135] A UE operating in an NTN and configured with no RACH HO (e.g., UE 114) can use resources indicated by the SIB to transmit a PUCCH as the first PUCCH transmission on the target cell, as well as a PUCCH with HARQ-ACK information, such as when the PUCCH transmission occurs before the UE establishes a dedicated RRC connection with the target cell, or before the UE receives dedicated PUCCH resources in the RRC_connected state.
[0136] When a UE (e.g., UE 114) is configured by a source gNB with no RACH HO, and the UE is granted UL permission to send PUSCH to the target gNB in a no RACH HO configuration or in a PDCCH from the target cell, and the UE is configured for NTN operation, when the UE is not provided with PUCCH resources via UE-specific RRC signaling with repetitions, the UE may send a PUCCH with HARQ-ACK information, and the repetition count may be provided in the System Information Block (SIB), or when the PUCCH transmission provides HARQ-ACK information associated with the DCI format, where the DCI format schedules PDSCH reception, and the PUCCH with HARQ-ACK responds to PDSCH reception, it may also be indicated by the DCI format. This indication may be based on a separate field in the DCI format indicating the repetition count of the PUCCH transmission, or it may be included in the configuration of the PUCCH resources, and the PUCCH resources may be indicated by the DCI format. In addition to parameters such as PUCCH format, start symbol and number of symbols, or start RB and number of RBs, PUCCH resources may also include the number of repetitions for PUCCH transmissions using PUCCH resources. In an embodiment, the UE (e.g., UE 114) is instructed by a MAC CE in a PDSCH reception to transmit a PUCCH with repeated HARQ-ACK information. Different types of MAC CEs can be used to indicate RA procedures without RACH and transmissions with repeated PUCCHs in type 1 or type 2 RA procedures. In an embodiment, if a PUSCH transmission based on a UL clearance configured in a RACH-free HO configuration or based on a UL clearance received from the target cell in the PDCCH is repeated, the PUCCH is repeated, and the same number of repetitions can be used for both PUSCH and PUCCH, unless a number of repetitions for PUCCH repetitions is provided.
[0137] The UE (e.g., UE 114) may transmit the PUCCH with the same spatial settings as the PUSCH transmission, or it may receive an indication from the target gNB to use a different spatial settings. The UE may transmit the PUCCH with the same spatial settings as the PUSCH transmission, and in the event that the PUSCH transmission fails and the target gNB schedules a retransmission, the target gNB indicates a new spatial settings for the retransmission of the PUSCH in the scheduled retransmission DCI format and for the transmission of the first PUCCH following the PUSCH transmission.
[0138] Figure 11 The present disclosure illustrates various embodiments of a UE procedure for a RACH-free handover in a target cell with repeated first or initial PUCCH transmissions. Figure 11 The UE process 1100 can be performed by Figure 1 Any of UE 111-116 (such as Figure 3 Execution of UE 116). Figure 11 The process described herein is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.
[0139] In step 1110, the source gNB provides the UE with a RACH-free handover configuration in the SIB. In step 1120, in response to the initial PUSCH transmission to the target gNB, the UE is provided with the number of repetitions for the PUCCH transmission after receiving the PDCCH. In step 1130, the UE determines the spatial settings for the PUCCH transmission based on the indication from the target gNB. In step 1140, the UE transmits a PUCCH with the number of repetitions using the spatial settings in the target cell. Alternatively, in step 1130, the UE determines the spatial settings for the PUCCH transmission based on the indication from the source gNB, and these spatial settings are the same as those used for the initial PUSCH transmission during the RACH-free handover process. The indication of the spatial settings by the target gNB can be provided by RRC signaling, by MAC CE, or by dynamic signaling. For example, the spatial settings indication can be included in the DCI format of the PDCCH received after the transmission of the first PUSCH, or in the PDSCH scheduled by the DCI format of the PDCCH. Spatial settings can also be determined by UE measurements of common signaling (such as SS / PBCH blocks) received from the target gNB, or based on reference signals (such as CSI-RS) received from the target gNB, and used for initial PUSCH and PUCCH transmissions.
[0140] Figure 12 An example method 1200 performed by a UE in a wireless communication system according to an embodiment of the present disclosure is shown. Figure 12 Method 1200 can be derived from Figure 1 Any of UE 111-116 (such as Figure 3 The UE 116) is executed, and the corresponding method can be performed by Figure 1 Any of BS 101-103 (such as Figure 2 The method is performed using BS 102. Method 1200 is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.
[0141] Method 1200 begins with, in 1210, the UE receiving information in the SIB from the source cell regarding a first configuration for a RACH-free handover procedure. In 1220, the UE also receives information about a first SS / PBCH block index set. In 1230, the UE also receives information about the PUSCH to be transmitted on the target cell. In 1240, the UE also receives information about the number of repetitions of the PUSCH transmission on the target cell. For example, in 1210-1240, the UE may receive information together in the same signal or channel or in separate signals or channels.
[0142] In step 1250, the UE then determines the spatial settings for transmitting the PUSCH. In step 1260, the UE then transmits the PUSCH with the specified number of repetitions using the spatial settings on the target cell.
[0143] In various embodiments, the UE receives second configuration information from the source cell for PUSCH transmission, wherein the PUSCH is a configured permitted PUSCH, and a mapping between a first SS / PBCH block index set and PUSCH transmission timings. Then, based on the mapping, the UE determines a first PUSCH transmission timing within the PUSCH transmission timings if the repetition count is one, or determines one or more first PUSCH transmission timings within the PUSCH transmission timings if the repetition count is greater than one. Here, the one or more first PUSCH transmission timings are associated with SS / PBCH block indices according to the mapping. The UE then transmits the configured permitted PUSCH on the target cell within one or more first PUSCH transmission timings.
[0144] In various embodiments, the SIB also provides information about a first RSRP value, and the UE determines an RSRP value associated with the reception of an SS / PBCH block associated with a first SS / PBCH block index set, wherein the RSRP value is greater than or equal to the first RSRP value, and a spatial setting based on the RSRP value. In various embodiments, the UE receives one or more second configurations for the transmission of PUSCH. In various embodiments, the SIB also provides information about a second SS / PBCH block index set, and the second SS / PBCH block index set is included in the first SS / PBCH block index set.
[0145] In various embodiments, the SIB also provides information on a first SS / PBCH block index, and the UE determines a spatial setting for PUSCH transmission based on the first SS / PBCH block index, and uses the spatial setting to receive a PDCCH from the target cell, the PDCCH providing a DCI format for scheduling PUSCH transmission.
[0146] In various embodiments, the UE receives information from a higher layer for a first spatial setting and a second spatial setting, and receives a PDCCH using the first spatial setting, which provides a DCI format for scheduling the transmission of PUSCH. Here, the spatial setting for PUSCH transmission is the second spatial setting.
[0147] The flowcharts above illustrate example methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the various steps in each diagram can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps can be omitted or replaced by other steps.
[0148] Any of the above-described variations can be used independently or in combination with at least one other variation. The flowcharts above illustrate example methods that can be implemented according to the principles of this disclosure, and various changes can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the various steps in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.
[0149] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims. None of the descriptions in this application should 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 defined by the claims.
Claims
1. A user equipment (UE), comprising: The transceiver is configured to receive the following information: The first configuration for the handover procedure without a random access channel (RACH) from the System Information Block (SIB) of the source cell. First synchronization signal (SS) and physical broadcast channel (PBCH) (SS / PBCH) block index set, The PUSCH used for transmitting the Physical Uplink Shared Channel (PUSCH) on the target cell, and The number of times the PUSCH is repeated in the target cell; and At least one processor, operatively coupled to the transceiver, is configured to determine spatial settings for transmitting PUSCH. The transceiver is also configured to send PUSCHs with a repetition count on the target cell using spatial settings.
2. The UE according to claim 1, wherein: The transceiver is also configured to receive the following information from the source cell: The second configuration for sending PUSCH, where PUSCH is the configured permitted PUSCH, and Mapping between the first SS / PBCH block index set and the PUSCH transmission timing; The at least one processor is also configured to determine one of the following based on the mapping: When the repetition count is one, the first PUSCH transmission timing in the PUSCH transmission timing, and When the repetition count is greater than 1, one or more first PUSCH transmission opportunities are included in the PUSCH transmission opportunities, wherein the one or more first PUSCH transmission opportunities are associated with the SS / PBCH block index according to the mapping; and The transceiver is also configured to transmit the configured permitted PUSCH on the target cell during one or more first PUSCH transmission times.
3. The UE according to claim 2, wherein: The SIB also provides information on the first reference signal received power (RSRP) value or information on the second SS / PBCH block index set; The second SS / PBCH block index set is included in the first SS / PBCH block index set; and The at least one processor is also configured to determine: The RSRP value associated with the reception of an SS / PBCH block, which is associated with a first SS / PBCH block index set. The RSRP value is greater than or equal to the first RSRP value, and Spatial settings based on RSRP values.
4. The UE according to claim 1, wherein, The transceiver is also configured to receive a physical downlink control channel (PDCCH) from the target cell if no configuration is provided for transmitting a PUSCH with configured permission. The physical downlink control channel (PDCCH) provides downlink control information (DCI) format for scheduling the transmission of PUSCH.
5. The UE according to claim 1, wherein: SIB also provides information on the first SS / PBCH block index; The at least one processor is further configured to determine the space settings for PUSCH transmission based on the first SS / PBCH block index; and The transceiver is also configured to receive a physical downlink control channel (PDCCH) from the target cell using spatial settings. The physical downlink control channel (PDCCH) provides downlink control information (DCI) format for scheduling the transmission of PUSCH.
6. The UE according to claim 1, wherein: The transceiver is also configured as follows: Receive information about the first and second space settings from higher levels, and The Physical Downlink Control Channel (PDCCH) is received using a first spatial configuration. The PDCCH provides the downlink control information (DCI) format for scheduling the transmission of the PUSCH, and... The space settings for sending PUSCH are the second space settings.
7. A base station (BS), comprising: The transceiver is configured to send the following information: The first configuration for the handover procedure without a random access channel (RACH) from the System Information Block (SIB) of the source cell. First synchronization signal (SS) and physical broadcast channel (PBCH) (SS / PBCH) block index set, The PUSCH used for receiving the Physical Uplink Shared Channel (PUSCH) on the target cell, and The number of times the PUSCH is received on the target cell; and At least one processor, operatively coupled to the transceiver, is configured to determine spatial settings for receiving PUSCH. The transceiver is also configured to receive PUSCHs with a repetition count on the target cell using spatial settings.
8. The BS according to claim 7, wherein: The transceiver is also configured to send the following information from the source cell: A second configuration for receiving PUSCH, wherein PUSCH is a configured permitted PUSCH, and Mapping between the first SS / PBCH block index set and the PUSCH reception timing; The at least one processor is also configured to determine one of the following based on the mapping: When the repetition count is one, the first PUSCH reception timing in the PUSCH reception timing, and When the repetition count is greater than 1, one or more first PUSCH reception opportunities are included in the PUSCH reception opportunities, wherein the one or more first PUSCH reception opportunities are associated with the SS / PBCH block index according to the mapping; and The transceiver is also configured to receive a configured licensed PUSCH on the target cell during one or more first PUSCH reception times.
9. The BS according to claim 7, wherein: SIB also provides information on the second SS / PBCH block index set or the first SS / PBCH block index; The second SS / PBCH block index set is included in the first SS / PBCH block index set; The at least one processor is further configured to determine the spatial settings for receiving PUSCH based on the first SS / PBCH block index; and The transceiver is also configured to transmit a physical downlink control channel (PDCCH) from the target cell using spatial settings. The physical downlink control channel (PDCCH) provides downlink control information (DCI) format for scheduling the reception of PUSCH.
10. The BS according to claim 7, wherein: The transceiver is also configured as follows: Send information about the first and second space settings from higher up, and The Physical Downlink Control Channel (PDCCH) is transmitted using a first spatial configuration. The PDCCH provides the downlink control information (DCI) format for scheduling the received PUSCH, and... The space settings for receiving PUSCH are the second space settings.
11. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Receive the following information: The first configuration for the handover procedure without a random access channel (RACH) from the System Information Block (SIB) of the source cell. First synchronization signal (SS) and physical broadcast channel (PBCH) (SS / PBCH) block index set, The PUSCH used for transmitting the Physical Uplink Shared Channel (PUSCH) on the target cell, and The number of times the PUSCH is repeated in the target cell; Determine the space settings for sending PUSCH; and Send a PUSCH with a repetition count using spatial settings on the target cell.
12. The method of claim 11, further comprising: Receive the following information from the source cell: The second configuration for sending PUSCH, where PUSCH is the configured permitted PUSCH, and The mapping between the first SS / PBCH block index set and the PUSCH transmission timing; and Based on the mapping, determine one of the following: When the repetition count is one, the first PUSCH transmission timing in the PUSCH transmission timing, and When the repetition count is greater than 1, one or more first PUSCH transmission opportunities are selected from the PUSCH transmission opportunities, wherein the one or more first PUSCH transmission opportunities are associated with the SS / PBCH block index according to the mapping. The method of sending a PUSCH with a repetition number on the target cell using spatial settings also includes sending a configured permitted PUSCH on the target cell during the one or more first PUSCH sending opportunities.
13. The method according to claim 12, wherein: The SIB also provides information on the first reference signal received power (RSRP) value or information on the second SS / PBCH block index set; The second SS / PBCH block index set is included in the first SS / PBCH block index set; The method further includes determining: The RSRP value associated with the reception of the SS / PBCH block, the SS / PBCH block being associated with a first SS / PBCH block index set, and The RSRP value is greater than or equal to the first RSRP value; and The determination of the space settings for PUSCH transmission also includes determining the space settings based on the RSRP value.
14. The method of claim 11, wherein: SIB also provides information on the first SS / PBCH block index; Determining the space settings for PUSCH transmission also includes determining the space settings for PUSCH transmission based on the first SS / PBCH block index; and The method further includes receiving a physical downlink control channel (PDCCH) from a target cell using spatial settings, the physical downlink control channel (PDCCH) providing downlink control information (DCI) format for scheduling the transmission of PUSCH.
15. The method of claim 11, further comprising: Receive information about the first and second space settings from higher up; as well as The first space setting is used to receive the Physical Downlink Control Channel (PDCCH), which provides the downlink control information (DCI) format for scheduling the transmission of PUSCH. The space settings used for sending PUSCH are the second space settings.
