Rapid mismatch based message 1 cfo compensation method
By monitoring coherent RAR attempts and compensating for carrier frequency offsets in high-speed train deployments, the problem of random access failures caused by RAPID mismatch was solved, and the communication success rate was improved.
Patent Information
- Application Number
- CN202180098519.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-05-29
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2041-05-29
AI Technical Summary
In high-speed train deployments, random access failures between user equipment (UE) and base stations occur frequently, mainly due to uplink Doppler shift causing mismatch in the random access preamble identifier (RAPID). Existing technologies struggle to effectively address this issue.
User equipment (UE) identifies mismatch RAPID by monitoring coherent random access response (RAR) attempts and compensates for carrier frequency offset in subsequent random access messages to overcome Doppler shift, thereby improving the success rate of random access.
Carrier frequency compensation significantly improves the success rate of random access for user equipment in high-speed train deployments and enhances communication reliability.
Smart Images

Figure CN117378274B_ABST
Abstract
Description
Background Technology Technical Field
[0002] This disclosure generally relates to communication systems, and more specifically to wireless communication systems between user equipment (UE) and base stations.
[0003] introduction
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.
[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband, promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them.
[0006] Overview
[0007] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not an exhaustive summary of all conceived aspects, nor is it intended to identify the key or decisive elements of all aspects, nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as an introduction to the more detailed description that follows.
[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a UE (User Equipment). The UE receives one or more Random Access Responses (RARs). Each of the one or more RARs includes a Random Access Prefix Identifier (RAPID), and each of the one or more RARs responds to a random access message including a prefix. The UE determines, in each of the one or more RARs a threshold number of times, that the RAPID of the corresponding RAR differs from the prefix of the corresponding random access message. In response to this determination, the UE offsets the carrier frequency used for each of the one or more subsequent random access messages.
[0009] To achieve the foregoing and related objectives, these one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of these one or more aspects are set forth in detail in the following description and drawings. However, these features merely indicate a few of the various ways in which the principles of these various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. Brief description of the attached diagram
[0011] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.
[0012] Figure 2A This is an example illustration of the first frame explaining various aspects of this disclosure.
[0013] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.
[0014] Figure 2C This is an example illustration of the second frame explaining various aspects of this disclosure.
[0015] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.
[0016] Figure 3 This is a diagram illustrating an example of a base station and user equipment (UE) in an access network.
[0017] Figure 4 This is a diagram illustrating an example of high-speed train deployment.
[0018] Figure 5 This is a diagram illustrating an example of a UE compensating for uplink Doppler shift when performing the Random Access Channel (RACH) procedure with the base station.
[0019] Figure 6This is a diagram illustrating an example of a UE transmitting a RACH preamble that undergoes uplink Doppler shift in either the positive or negative frequency direction.
[0020] Figure 7 This is a diagram illustrating an example of a UE that uses a carrier frequency offset for different RACH preambles to compensate for uplink Doppler shift.
[0021] Figure 8 This is a diagram illustrating the call flow between the UE and the base station.
[0022] Figure 9 This is a flowchart of a wireless communication method.
[0023] Figure 10 This is a diagram illustrating an example of the hardware implementation of the example device.
[0024] Detailed description
[0025] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent only the configurations in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.
[0026] In a contention-based four-step RACH procedure, four messages can be provided between the UE and the base station. For example, during the initial attachment procedure, the UE may send a preamble to the base station (e.g., message 1), receive a Random Access Response (RAR) from the base station (e.g., message 2), send an RRC connection request message or other payload to the base station (e.g., message 3), and receive an RRC connection establishment message or other contention-resolved transmission from the base station (e.g., message 4). This four-step RACH procedure can be simplified to a two-step RACH procedure, in which the UE sends the preamble and payload in the first message. For example, message A (“msgA”) in the two-step RACH procedure may correspond to messages 1 and 3 in the four-step RACH procedure, and message B (“msgB”) may correspond to messages 2 and 4 in the four-step RACH procedure. Thus, in the two-step RACH procedure, the UE may send the preamble followed by the payload in the msgA transmission to the base station, while the base station may send the RAR and RRC response messages in the msgB transmission to the UE.
[0027] The UE can select a preamble for message 1 or msgA from a set of random access preambles generated by the UE. The set of random access preambles can be a function of various configured RACH parameters, including the Physical Random Access Channel (PRACH) preamble format. The preamble format can then be associated with the PRACH preamble subcarrier spacing. After the UE selects a preamble from the generated set, the UE can transmit the preamble to the base station in configured time and frequency resources. Time and frequency resources can be functions of various configured RACH parameters. For example, the time slot or symbol in which the preamble is transmitted can depend on the PRACH configuration index, and the subcarrier in which the preamble is transmitted can depend on the PRACH preamble subcarrier spacing.
[0028] After the UE transmits the selected preamble to the base station in a PRACH subcarrier (in message 1 or msgA), the base station can decode the message and identify the preamble transmitted by the UE. For example, the base station can receive and demodulate data in the PRACH subcarrier and determine the UE's selected preamble sequence based on the subcarrier in which the PRACH data was received. In response to identifying the preamble, the base station can configure a RAR including a Random Access Preamble Identifier (RAPID). The base station can configure the RAPID using an identifier associated with the decoded preamble sequence (e.g., determining the preamble sequence already transmitted by the UE). The base station can then transmit the RAR to the UE in message 2 or msgB.
[0029] Once the UE receives and decodes the RAR, it can determine whether the RAPID in the RAR is the same as the identifier associated with the preamble sequence selected by the UE. If the RAPID matches the preamble, the UE can determine that the preamble has been successfully received or the RACH procedure has been successfully executed, and the UE can communicate with the base station accordingly. Otherwise, if the RAPID does not match the preamble (e.g., the RAPID is a mismatched RAPID), the UE can determine that the RACH procedure has failed, and the UE can restart the RACH procedure from message 1 or msgA.
[0030] One scenario where mismatched RAPIDs might be observed is in high-speed train (HST) deployments. HSTs have recently evolved into fast, convenient, environmentally friendly, and flexible transportation devices. As more passengers carrying UEs tend to travel on HSTs, new challenges arise in providing reliable communication services to accommodate the increasing communication demands. For example, a typical HST may travel at speeds exceeding 200 km / h or even 350 km / h, leading to frequent and rapid handovers, Doppler spread, and other effects. To overcome these challenges, millimeter-wave (mmW) and massive MIMO technologies, as well as Coordinated Multipoint (CoMP) and mobile relay station architectures, have been considered for HST deployments.
[0031] However, despite such techniques, conventional HST deployments may still be insufficient to cover all possible scenarios that can occur in an HST, including the aforementioned mismatch RAPID. For example, UEs located in or on an HST (referred to herein as HST UEs) typically camp on non-HST cells (e.g., cells served by base stations located outside or far from the HST). Since these non-HST cells were originally designed to support UEs located outside or far from the HST (referred to herein as non-HST UEs), base stations serving these non-HST cells can configure HST UEs and non-HST UEs with similar RACH configurations. For example, a base station in a non-HST cell can provide both HST UEs and non-HST UEs with a RACH configuration indicating PRACH preamble format 0 and employing an unconstrained set of preamble sequences. As a result, HST UEs camped on non-HST cells tend to experience frequent RACH failures due to the mismatch between the RAPID in the RAR and the UE's selected preamble. These RAPID mismatches are typically due to the relatively small PRACH preamble subcarrier spacing (e.g., Δf) associated with the previously coded format. RA =1.25kHz) and the relatively large uplink Doppler shift that the HST UE may experience when transmitting message 1 or msgA. Therefore, compensating for this uplink Doppler shift would be helpful in improving the RACH success rate of the HST UE.
[0032] Various aspects of this disclosure allow the UE to compensate for uplink Doppler shift during (e.g., in HST) transmission of RACH preambles. In one example, the UE can monitor a number of N consecutive RACH attempts (e.g., the first to the Nth RACH attempts) to find mismatched RAPIDs. For example, the UE can obtain N consecutive RARs, each RAR responding to the transmitted preamble, and the UE can determine whether any of these RARs includes a RAPID whose identifier does not match the corresponding preamble sequence transmitted by the UE. If the UE determines that a threshold number K of these RACH attempts have failed due to mismatched RAPIDs in response to the aforementioned Doppler shift effect, the UE can compensate for the frequency shift in subsequent RACH attempts. For example, if a UE determines that K out of N consecutive RARs include RAPIDs that do not match the identifiers of the corresponding preamble sequence due to positive or negative Doppler shift, the UE can offset the carrier frequency used for subsequent messages 1 or msgA (e.g., in RACH attempt N+1 and beyond) positively or negatively to compensate for the Doppler shift. For example, if the UE has already transmitted the preamble at a carrier frequency of 3.8 GHz in RACH attempts 1 through N, the UE can transmit the preamble at a carrier frequency offset of 600 Hz (3.8000006 GHz) or -600 Hz (3.7999994 GHz) in subsequent RACH attempts N+1. The UE can similarly transmit subsequent RACH preambles with a carrier frequency offset (positive or negative) until the base station successfully decodes the transmitted preamble and the UE receives a RAR with a RAPID that matches the transmitted preamble. As a result, the RACH success rate can be increased for HST UEs.
[0033] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and explained in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0034] As an example, an element, or any part of an element, or any combination of elements, may be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.
[0035] Accordingly, in one or more example embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of being used to store computer-executable code in the form of instructions or data structures accessible to a computer.
[0036] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.
[0037] Base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: user data delivery, radio channel cryptography and cryptography decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of alarm messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) on third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.
[0038] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved B Node (eNB) (HeNB) that can provide services to a restricted group called a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may use one or more carriers. For each carrier allocated in a carrier aggregation totaling up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). These carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).
[0039] Some UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
[0040] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 via a communication link 154, for example, in an unlicensed spectrum of 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.
[0041] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can enhance access network coverage and / or increase access network capacity.
[0042] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although different from the Very High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles.
[0043] In light of the foregoing, unless otherwise stated, it should be understood that, as used herein, the term "sub-6GHz" and the like can broadly refer to frequencies less than 6GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.
[0044] Whether it is a small cell 102' or a large cell (e.g., a macro base station), base station 102 may include and / or be referred to as an eNB, gB node (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave frequencies or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.
[0045] Base station 180 may transmit beamformed signals to UE 104 in one or more transmission directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more reception directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmission directions. Base station 180 may receive beamformed signals from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 180 / UE 104. The transmission and reception directions of base station 180 may be the same or different. The transmission and reception directions of UE 104 may be the same or different.
[0046] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, MBMS Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.
[0047] Core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and core network 190. Generally, AMF 192 provides Quality of Service (QoS) streaming and session management. All user IP packets are delivered via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IMS, packet-switched (PS) streaming service, and / or other IP services.
[0048] Base stations may include and / or be referred to as gNB, B-node, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop devices, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking timers, oil pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.
[0049] While this disclosure may focus on 5G NR, the concepts and aspects described herein are applicable to other similar fields, such as LTE, LTE-A Advanced, Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), or other wireless / radio access technologies.
[0050] Refer again Figure 1 In some aspects, UE 104 may include a carrier frequency offset (CFO) compensation component 198 configured to obtain one or more RARs, wherein each of the one or more RARs includes a RAPID, and wherein each of the one or more RARs responds to a random access message including a preamble. The CFO compensation component 198 is also configured to determine, in each of a threshold number of RARs in the one or more RARs, that the RAPID of the corresponding RAR differs from the preamble of the corresponding random access message. The CFO compensation component 198 is also configured to offset the carrier frequency used for each of one or more subsequent random access messages in response to this determination.
[0051] Figure 2A This is a diagram 200 illustrating an example of the first subframe within the 5G NR frame structure. Figure 2B Figure 230 is an example illustrating the DL channel within a 5G NR subframe. Figure 2CThis is a diagram 250 illustrating an example of the second subframe within the 5G NR frame structure. Figure 2D Figure 280 illustrates an example of the UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL; or it can be Time Division Duplex (TDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , 2C In the provided example, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is for flexible use between DL / UL, and subframe 3 is configured with slot format 34 (mostly UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G NR frame structures for TDD.
[0052] Other wireless communication technologies may have different frame structures and / or different channels. A frame (e.g., a 10-millisecond (ms) frame) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL may be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 symbols per subframe. μEach time slot. The subcarrier spacing and symbol length / duration vary depending on the design parameters. The subcarrier spacing can be equal to 2. μ *15 kHz, where μ is the parameter design from 0 to 4. Thus, parameter design μ = 0 has a subcarrier spacing of 15 kHz, while parameter design μ = 4 has a subcarrier spacing of 240 kHz. Symbol length / duration is inversely correlated with subcarrier spacing. Figure 2A-2D An example is provided with a slot configuration of 0 (14 symbols per slot) and a parameter design of μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth portions (BWPs) that are frequency-division multiplexed (see [link to relevant documentation]). Figure 2B Each BWP can have specific parameter designs.
[0053] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) extending 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0054] like Figure 2A As explained in the text, some REs carry reference (pilot) signals (RS) for the UE. RS may include demodulated RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x (where 100x is the port number, but other DM-RS configurations are possible) and Channel State Information Reference Signal (CSI-RS). RS may also include Beam Measurement RS (BRS), Beam Refinement RS (BRRS), and Phase Tracking RS (PT-RS).
[0055] Figure 2BExamples of various DL channels within a subframe of a frame are explained. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising 9 RE Groups (REGs), each REG comprising 4 consecutive REs in OFDM symbols. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). Additional BWPs can be located at higher and / or lower frequencies spanning the channel bandwidth. The Primary Synchronization Signal (PSS) is located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) is located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identity Group Number and radio frame timing. Based on the Physical Layer Identity and Physical Layer Cell Identity Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can logically group with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as the System Information Block (SIB)), and paging messages.
[0056] like Figure 2C As explained, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and on the specific PUCCH format used. The UE can transmit a probe reference signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
[0057] Figure 2DExamples of various UL channels within a subframe of a frame are explained. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) / negative acknowledgment (NACK) feedback. The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.
[0058] Figure 3 This is a block diagram showing the communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (cryptography, cryptographic decoding, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer packet data unit (PDU) delivery, error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.
[0059] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be derived from reference signals and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.
[0060] At UE 350, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If there are multiple spatial streams destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by base station 310 over the physical channel. This data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.
[0061] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, cipher decoding, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.
[0062] Similar to the functionality described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (cryptography, cryptographic decoding, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.
[0063] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.
[0064] UL transmissions are processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.
[0065] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, cipher decoding, header decompression, and control signal processing to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.
[0066] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 The CFO compensation component 198 combines various aspects.
[0067] In a contention-based four-step RACH procedure, four messages can be provided between the UE and the base station. For example, during the initial attachment procedure, the UE may send a preamble to the base station (e.g., message 1), receive a RAR from the base station (e.g., message 2), send an RRC connection request message or other payload to the base station (e.g., message 3), and receive an RRC connection establishment message or other contention-resolved transmission from the base station (e.g., message 4). This four-step RACH procedure can be simplified to a two-step RACH procedure, in which the UE sends the preamble and payload in the first message. For example, message A (“msgA”) in the two-step RACH procedure may correspond to messages 1 and 3 in the four-step RACH procedure, and message B (“msgB”) may correspond to messages 2 and 4 in the four-step RACH procedure. Thus, in the two-step RACH procedure, the UE may send a preamble followed by a payload in the msgA transmission to the base station, while the base station may send the RAR and RRC response messages in the msgB transmission to the UE.
[0068] The UE can select from the set of random access preambles (x) generated by the UE. u,v The preamble for either message 1 or msgA is selected from (n). The set of random access preambles can be a function of various configured RACH parameters. For example, the random access preamble can depend at least on the preamble sequence number (u) obtained from the logical root sequence index and the length (L) associated with the physical random access channel (PRACH) preamble format. RA ) and the cyclic shift of the logical root sequence (C v The preamble format can then be related to the PRACH preamble subcarrier spacing (Δf). RA ), Prefix length (N) u ), Prefix cyclic prefix length This is associated with support for constrained sets of preamble sequences, as illustrated in the examples in Table 1 below. Furthermore, for unconstrained sets of preamble sequences, cyclic shift (C... v ) can be a cyclic shift parameter (N) CS The function is N, and for a constrained set of preamble sequences, the cyclic shift can be N. CS and Doppler shift parameter (d u The function of ).
[0069]
[0070] Table 1 (Assuming L) RA =839 and Δf RA (∈{1.25,5}kHz)
[0071] After the UE selects a preamble from the generated preamble set, the UE can transmit the preamble to the base station in configured time and frequency resources. The time and frequency resources can be functions of various configured RACH parameters. For example, the time slot or symbol in which the preamble is transmitted can depend on the PRACH configuration index, and the subcarrier in which the preamble is transmitted can depend on the length (L). RA ) and PRACH preamble subcarrier spacing (Δf RA The subcarrier can be represented in the frequency domain (y) based on the generated preamble sequence set. u,v (n)) cross-frequency domain extension, and further, cyclic shift (C v The function of ). Therefore, each preamble sequence in this set can be configured in the frequency domain in different combinations across PRACH subcarriers based on a corresponding cyclic shift, wherein each PRACH subcarrier is frequency-spaced apart from each other according to the PRACH preamble subcarrier spacing. As a result, adjacent PRACH subcarriers (by Δf RA (Separated) can be configured for different preamble sequences, and the UE can transmit the selected preamble in the corresponding PRACH subcarrier used for that preamble sequence.
[0072] After the UE transmits the selected preamble to the base station in a PRACH subcarrier (in message 1 or msgA), the base station can decode the message and identify the preamble transmitted by the UE. For example, the base station can receive and demodulate data in the PRACH subcarrier and determine the UE's selected preamble sequence based on the subcarrier in which the PRACH data was received. In response to identifying the preamble, the base station can configure a RAR including a Random Access Preamble Identifier (RAPID). The base station can configure the identifier associated with the decoded preamble sequence (e.g., determining the preamble sequence already transmitted by the UE) to have a RAPID. The base station can then transmit the RAR to the UE in message 2 or msgB.
[0073] Once the UE receives and decodes the RAR, it can determine whether the RAPID in the RAR is the same as the identifier associated with the preamble sequence selected by the UE. If the RAPID matches the preamble, the UE can determine that the preamble has been successfully received or the RACH procedure has been successfully executed, and the UE can communicate with the base station accordingly. Otherwise, if the RAPID does not match the preamble (e.g., the RAPID is a mismatched RAPID), the UE can determine that the RACH procedure has failed, and the UE can restart the RACH procedure from message 1 or msgA.
[0074] One scenario where mismatched RAPID can be observed is in HST deployments. HSTs have recently evolved into fast, convenient, environmentally friendly, and flexible transport devices. As more passengers carrying UEs tend to travel on HSTs, new challenges arise in providing reliable communication services to accommodate the increasing communication demands. For example, a typical HST may travel at speeds exceeding 200 km / h or even 350 km / h, leading to frequent and rapid handovers, Doppler spread, and other effects. To overcome these challenges, mmW and massive MIMO technologies, as well as CoMP and mobile relay station architectures, have been considered for HST deployments.
[0075] However, despite such techniques, conventional HST deployments may still be insufficient to cover all possible scenarios that can occur in an HST, including the aforementioned mismatch RAPID. For example, UEs located in or on an HST (referred to herein as HST UEs) are typically camped on non-HST cells (e.g., cells served by base stations located outside or far from the HST). Since these non-HST cells were originally designed to support UEs located outside or far from the HST (referred to herein as non-HST UEs), base stations serving these non-HST cells can configure both HST and non-HST UEs with similar RACH configurations. For example, a base station in a non-HST cell can provide both the HST and non-HST UEs with a RACH configuration indicating PRACH preamble format 0 (see Table 1 above) and employing an unconstrained set of preamble sequences. As a result, HST UEs camped on non-HST cells tend to experience frequent RACH failures due to the mismatch between the RAPID in the RAR and the UE's selected preamble. These RAPID mismatches are typically due to the relatively small PRACH preamble subcarrier spacing (e.g., Δf) associated with the previously coded format. RA =1.25kHz) and the relatively large uplink Doppler shift that the HST UE may experience when transmitting message 1 or msgA.
[0076] Here, uplink Doppler shift refers to the frequency shift of the radio signal received by the base station relative to the movement of the transmitting UE. For example, if a stationary base station receives a RACH message on a 3.5 GHz carrier frequency from an HST UE traveling at 200 km / h in an HST, the RACH message may experience a Doppler shift or frequency offset varying between ±600 Hz. Furthermore, if a stationary base station receives a RACH message on a 3.8 GHz carrier frequency from an HST UE traveling at 350 km / h in an HST, the RACH message may experience a Doppler shift or frequency offset varying between ±1230 Hz. This Doppler shift can be relatively large compared to the small preamble subcarrier spacing typically associated with the common preamble format used for both HST and non-HST UEs. For example, if Δf RA If the frequency is 1.25 kHz, the base station can receive message 1 or msgA from an HST UE traveling at 350 km / h on the HST, and the frequency offset is close to one PRACH subcarrier. In some cases, the frequency offset may be even larger, typically up to two PRACH subcarriers. As a result of this frequency offset applied to the received signal, the base station may misidentify the transmitted preamble as a different preamble, causing the base station to identify a different RAPID and ultimately leading to RACH failure. This misidentification may be caused by positive Doppler shift (e.g., where the preamble is received at a frequency higher than its transmitted frequency) or negative Doppler shift (e.g., where the preamble is received at a frequency lower than its transmitted frequency). Therefore, compensating for these carrier frequency offsets will be helpful in improving the RACH success rate of HST UEs.
[0077] For example, Figure 4 Example 400 of an HST deployment in which a UE on the HST (HST UE 402) can communicate with a base station 404 in a non-HST cell is described. Base station 404 can also communicate with UEs outside the HST (non-HST UE 406). During the RACH procedure, HST UE 402 can transmit a RACH message 408 (e.g., message 1 or msgA) including a preamble to base station 404 at a given frequency A. However, due to the high speed of the HST UE relative to the base station, a Doppler shift 410 or frequency offset can be applied, causing the base station to receive the RACH message at a different frequency B. As a result of this frequency offset, base station 404 can identify an incorrect preamble and accordingly transmit a RAR 412 (e.g., message 2 or msgB) including an incorrect RAPID to the HST UE. The RACH procedure may fail due to a mismatch between the preamble in RACH message 408 and the RAPID in RAR 412, and the procedure may be inefficiently repeated for subsequent RACH attempts.
[0078] To address this issue, aspects of this disclosure allow for compensation of uplink Doppler shift when the UE transmits a RACH preamble (e.g., in an HST). In one example, the UE can monitor a number of N consecutive RACH attempts (e.g., the first to the Nth RACH attempts) to find mismatched RAPIDs. For example, the UE can obtain N consecutive RARs, each RAR responding to the transmitted preamble, and the UE can determine whether any of these RARs includes a RAPID whose identifier does not match the corresponding preamble sequence transmitted by the UE. If the UE determines that a threshold number K of these RACH attempts have failed due to mismatched RAPIDs in response to the aforementioned Doppler shift effect, the UE can compensate for the frequency shift in subsequent RACH attempts. For example, if a UE determines that K out of N consecutive RARs include RAPIDs that do not match the identifiers of the corresponding preamble sequence due to positive or negative Doppler shift, the UE can offset the carrier frequency used for subsequent messages 1 or msgA (e.g., in RACH attempt N+1 and beyond) positively or negatively to compensate for the Doppler shift. For instance, if the UE has already transmitted the preamble at a carrier frequency of 3.8 GHz in RACH attempts 1 through N, the UE can transmit the preamble at a carrier frequency offset of 600 Hz (3.8000006 GHz) or -600 Hz (3.7999994 GHz) in subsequent RACH attempts N+1. The UE can similarly transmit subsequent RACH preambles with different carrier frequency offsets (positive or negative) until the base station successfully decodes the transmitted preamble and the UE receives a RAR with a RAPID that matches the transmitted preamble. As a result, the RACH success rate can be increased for HST UEs.
[0079] Figure 5 Example 500 of UE 502 is explained when the RACH procedure with base station 504 is executed to compensate for uplink Doppler shift. UE 502 may correspond to Figure 4 HST UE 402, and base station 504 can correspond to Figure 4Base station 404. Initially, UE 502 can monitor up to N consecutive RACH attempts, wherein in each RACH attempt 506, the UE transmits a RACH message 508 (e.g., message 1 or msgA) to base station 504 and receives a RAR 510 (e.g., message 2 or msgB) from the base station. Each RACH message 508 may include a preamble selected by UE 502, and each RAR 510 may include a RAPID configured by base station 504. The number N can be a configurable value, which is a function of the maximum number of preamble transmissions configured for the UE. The maximum number of preamble transmissions can be configured via the parameter preambleTransMax (maximum preamble transmissions), which the base station can notify the UE of in an RRC message signaling. For example, the base station can configure N = minimum value (preambleTransMax, 10).
[0080] For each RACH attempt 506 in which UE 502 receives a RAPID in RAR 510, the UE checks whether the RAPID matches the preamble in the corresponding RACH message 508. If UE 502 determines that a threshold number 512 of RACH attempts 506 (e.g., K RACH attempts out of N consecutive RACH attempts) failed due to a mismatched RAPID (e.g., the RAPID does not match the preamble in each of the K attempts), the UE may determine whether each of these failed attempts was due to an uplink Doppler shift or offset in the carrier frequency 514 used for each RACH message 508. The threshold number K may include any combination of consecutive or inconsequential RACH attempts out of N consecutive RACH attempts. For example, if N=10 and K=5, the threshold number of RACH attempts can include five different RACH attempts 1-5; RACH attempts 3-7; RACH attempts 6-10; RACH attempts 1, 3, 5, 7, 9; RACH attempts 2, 4, 6, 8, 10; RACH attempts 3, 4, 7, 9, 10 or any other combination of K different RACH attempts within N consecutive RACH attempts.
[0081] The UE can also determine how many of these K RACH attempts (if any) include a positive Doppler shift (denoted by the number K1), and how many of these K RACH attempts (if any) include a negative Doppler shift (denoted by the number K2), where K = K1 + K2. For example, Figure 6 Example 600 of UE 602 attempting to use a RACH preamble to base station 604 is described, wherein the RACH preamble carried in PRACH 606 undergoes uplink Doppler shift in either the positive (K1) or negative (K2) direction. UE 602 may correspond to Figure 4 and 5 HST UE 402 and UE502, and base station 604 can correspond to Figure 4 and 5 Base stations 404 and 504. In this example, when UE 602 transmits the RACH preamble for RACH attempt 1 in PRACH 1, PRACH 1 may undergo a positive Doppler shift, causing base station 604 to receive PRACH 1 at a higher frequency than the transmitted frequency. As a result, the base station may misidentify PRACH 1 as including a different preamble and configure an incorrect RAPID accordingly. Therefore, PRACH 1 may be included in the total K1. Similarly, when UE 602 transmits the RACH preamble for RACH attempt 2 in PRACH 2, PRACH 2 may undergo a negative Doppler shift, causing base station 604 to receive PRACH 2 at a lower frequency than the transmitted frequency. As a result, the base station may similarly misidentify PRACH 2 as including a different preamble and configure an incorrect RAPID accordingly. Therefore, PRACH 2 may be included in the total K2. For other RACH attempts, the UE can continue to transmit RACH preambles in PRACH, where each PRACH can be subjected to positive or negative Doppler shift.
[0082] In one example, the UE can determine whether the RAPID mismatch is caused by uplink Doppler shift effects and the direction (positive or negative) of the Doppler shift based on the expected RAPID at the base station. For example, the UE can apply the following formula to determine the presence and direction of Doppler shift or carrier frequency offset (CFO):
[0083]
[0084] Where RAPID0 indicates a cyclic shift C v RAPID of the root u = 0;
[0085]
[0086] Where v UE Indicates RAPID UE Circular shift index;
[0087]
[0088] in This indicates a shift relative to RAPID0 for CFO>0 (positive Doppler shift);
[0089]
[0090] in This indicates a shift relative to RAPID0 for CFO < 0 (negative Doppler shift);
[0091] For l∈{0,1,...,L} RA -1}, definition:
[0092]
[0093] Where g represents the mapping to RAPID;
[0094] For delay d D The expected RAPID at the receiver is
[0095]
[0096]
[0097] in or This indicates the total shift relative to RAPID0; and
[0098]
[0099]
[0100] RAPID pos and RAPID neg This indicates that for positive and negative frequency shifts, respectively, for 0 ≤ d D ≤N CS -1 may be the RAPID received.
[0101] In determining the expected RAPID (RAPID) pos and RAPID neg ) and the actual RAPID in the RAR received from the base station (RAPID gNB When a RAPID mismatch occurs, the UE can apply the following decision rules to determine whether it is due to the CFO; if so, the direction of the CFO should be determined:
[0102]
[0103] In Equation 8, "non-Doppler" indicates that the mismatch RAPID is not determined by the Doppler effect (no frequency shift), and "positive Doppler" indicates that the mismatch RAPID is determined by a positive frequency shift (e.g., Figure 6 The determination caused by PRACH 1) in the text, "negative Doppler" indicates that the mismatch RAPID is caused by a negative frequency shift (e.g., Figure 6The determination is caused by PRACH 2), and "fuzziness" indicates that the mismatch RAPID may be caused by a positive or negative frequency offset.
[0104] In another example, the UE can determine whether the RAPID mismatch is caused by an uplink Doppler shift effect and the direction (positive or negative) of the Doppler shift based on the expected RAPID at the base station and the timing advance received from the base station in the RAR. For example, the UE can apply the following formula to determine the presence and direction of the Doppler shift or CFO:
[0105]
[0106] Where RAPID0 indicates a cyclic shift C v RAPID of the root u = 0;
[0107]
[0108] Where v UE Indicates RAPID UE Circular shift index;
[0109]
[0110] in This indicates the frequency shift relative to RAPID0 for CFO>0 (positive Doppler shift);
[0111]
[0112] in This represents the frequency shift relative to RAPID0 for CFO < 0 (negative Doppler shift);
[0113]
[0114] Where v gNB Indicates RAPID gNB Circular shift index;
[0115]
[0116] Where T NW This indicates a timing advance reported by the network in seconds, and T RA This indicates the RACH sampling period.
[0117]
[0118]
[0119] Equation 15 defines the lower bound LB and upper bound UB associated with the cyclic shift used for the expected RAPID, and π represents the coverage T. NW Error margin in the process;
[0120]
[0121] Where I D This indicates the possible cyclic shift that is expected to be received for the RAPID.
[0122] In determining the expected RAPID(I) D During the cyclic shift of ), the UE can apply the following decision rule to determine whether the RAPID mismatch is due to the CFO, and if so, determine the direction of the CFO:
[0123]
[0124] In Equation 17, "non-Doppler" indicates that the mismatch RAPID is not determined by the Doppler effect (no frequency shift), and "positive Doppler" indicates that the mismatch RAPID is determined by a positive frequency shift (e.g., Figure 6 The determination caused by PRACH 1) in the text, "negative Doppler" indicates that the mismatch RAPID is caused by a negative frequency shift (e.g., Figure 6 The determination is caused by PRACH 2), and "fuzziness" indicates that the mismatch RAPID may be caused by a positive or negative frequency offset.
[0125] While the two examples above illustrate the specific parameters and equations that a UE can apply to determine the CFO and direction, other parameters or equations can be applied to make that determination. Therefore, the examples above are illustrative in nature, and the determination of the CFO and direction is not limited to the parameters and equations shown in these examples.
[0126] For example, as described in the example above, the UE can be based on the Doppler frequency shift parameter d. u (See, for example, equations 3, 4, 11, and 12) to determine the presence and direction of the Doppler shift. Typically, the maximum uplink CFO observed in the HST can be twice the maximum Doppler shift (e.g., for an HST of 350 km / h, 2 x 1230 Hz = 2460 Hz, or assuming Δf...). RA = Approximately two PRACH subcarriers at 1.25 kHz). Therefore, d u It can be represented as d (1) u or d (2) uThese can represent the cyclic shift location of false alarm peaks caused by frequency offsets of up to one or two PRACH subcarriers. For example, the cyclic shift d on sequence u. (1) u This can be caused by a frequency offset of up to one PRACH subcarrier, or a cyclic shift d on sequence u. (2) u This can be caused by a frequency shift of up to two PRACH subcarriers. Therefore, in equations 3, 4, 11, and 12 above, d u Can be replaced with d (1) u (for at most one PRACH subcarrier offset) or d (2) u (For at most two PRACH subcarrier offsets), where d (1) u It satisfies u*d(1) u mod L RA = the smallest positive integer or the largest negative integer equal to + / - 1, where d (2) u Is it satisfying u*d (2) u modL RA = the smallest positive integer or the largest negative integer equal to + / - 2.
[0127] Refer back Figure 5 If UE 502 determines that RACH attempts of threshold number 512 (K in N) each fail due to uplink Doppler shift (e.g., in response to determining positive Doppler, negative Doppler, or ambiguity in Equation 8 or 17 above), the UE can compensate for the Doppler shift in subsequent RACH attempts 516 by offsetting the carrier frequency 514 used for each subsequent RACH message 518 (starting from RACH attempt N+1). For example, the UE can apply an offset 520 to the carrier frequency 514 used for subsequent RACH messages 518 in RACH attempt N+1 by transmitting a preamble in the subsequent RACH message at the offset carrier frequency. For example, if the UE transmits RACH attempts 1 to N at a frequency of 3.8 GHz, the UE can apply an offset of 600 Hz or -600 Hz to RACH attempt N+1 by transmitting a preamble at the offset carrier frequency (e.g., 3.8000006 GHz or 3.7999994 GHz, respectively) during the RACH attempts. The UE may apply a different offset (or the same offset) in each subsequent RACH attempt (e.g., N+2, etc.), and the UE may continue to apply the offset to subsequent RACH messages accordingly until the UE receives a subsequent RAPID 522 that matches the transmitted preamble.
[0128] For example, Figure 7 Example 700 of UE 702 describes how, after determining K mismatched RAPIDs in N initial RACH attempts, the carrier frequency for different RACH preambles is offset. UE 702 can correspond to... Figure 4-6 HST UEs 402 and 502, 602. For example, a UE can offset the carrier frequency used for each RACH preamble by transmitting each preamble in PRACH 704 with different frequency offsets (positive or negative) to compensate for the Doppler shift effect. For example, UE 702 can transmit the RACH preamble for RACH attempt N+1 in PRACH N+1 according to a first carrier frequency offset in either the positive or negative direction. For example, if a previous PRACH (in RACH attempt N or a previous attempt) experienced a positive Doppler shift, the UE can transmit PRACH N+1 at a lower frequency (negative frequency offset) to attempt to compensate for the positive Doppler shift, while if a previous PRACH experienced a negative Doppler shift, the UE can transmit PRACH N+1 at a higher frequency (positive frequency offset) to attempt to compensate for the negative Doppler shift. If the value of the first carrier frequency offset is insufficient to compensate for the Doppler shift, the base station may still misidentify PRACH N+1 as including a different preamble and configure an incorrect RAPID accordingly. Therefore, the UE can attempt to apply more compensation (different offsets) in the next RACH attempt. For example, UE 702 can transmit the RACH preamble for RACH attempt N+2 based on a second carrier frequency offset in either the positive or negative direction, where the second carrier frequency offset differs from the first carrier frequency offset. For instance, the UE can transmit PRACH N+2 at a frequency lower than PRACH N+1 to increase compensation for the positive Doppler shift, or transmit PRACH N+2 at a frequency higher than PRACH N+1 to increase compensation for the negative Doppler shift. Alternatively, the second carrier frequency offset can be the same as the first carrier frequency offset. The UE can continue to offset the PRACH for subsequent RACH attempts until the Doppler shift is adequately compensated and the base station 704 correctly identifies the preamble in the PRACH. As a result, the base station can configure the correct RAPID, and the probability of a successful RACH can be increased.
[0129] Refer again Figure 5 In one example, the value of each offset of 520 can be limited to the base station's ability to base on the preamble subcarrier spacing Δf. RA Within the configurable range. For example, a base station can configure the following range for CFO compensation:
[0130] [-(1.5+L)*RA_SCS,-(0.5+L)*RA_SCS](18)
[0131] or;
[0132] [(0.5+L)*RA_SCS,(1.5+L)*RA_SCS](19)
[0133] Wherein, the first range (18) represents an example of a negative range that the UE can apply in response to determining a negative (or ambiguous) frequency offset in Equation 8 or 17, the second range (19) represents an example of a positive range that the UE can apply in response to determining a positive (or ambiguous) frequency offset in Equation 8 or 17, and RA_SCS refers to the preamble subcarrier spacing Δf RA Furthermore, the value of L can depend on whether the frequency offset causing the RAPID mismatch is as large as one PRACH subcarrier (in which case the UE can apply d in equations 3, 4, 11, or 12 above). (1) u Or, at most two PRACH subcarriers (in this case, the UE can apply d in equations 3, 4, 11, or 12 above). (2) u For example, if the frequency offset is one PRACH subcarrier, then L = 0; if the frequency offset is two PRACH subcarriers, then L = 1.
[0134] Additionally, in another example, the aforementioned ranges (e.g., negative range (18) or positive range (19)) can be further optimized by the maximum uplink carrier frequency offset. In the example ranges (18) and (19) above, for L = 1 (i.e., -(1.5 + [L = 1]) * RA_SCS and (1.5 + [L = 1]) * RA_SCS), the minimum and maximum limits can be -2.5 * RA_SCS and 2.5 * RA_SCS, respectively. However, these ranges can be optimized (narrowed) to account for the maximum uplink CFO observable in an HST deployment. For example, as mentioned above, the maximum uplink CFO observed in an HST can be twice the maximum Doppler shift (e.g., 2 x 1230 Hz = 2460 Hz for an HST of 350 km / h, or assuming Δf RA = Approximately two PRACH subcarriers at 1.25 kHz). Since 2460 Hz < 2.5 kHz = 2 * (Δf) RA =1.25kHz), the UE can apply a positive CFO compensation of up to 2*RA_SCS to L=1 (two PRACH subcarriers), instead of 2.5*RA_SCS as in the previous example range (19). Similarly, for L=1, the UE can apply a negative CFO compensation as low as -2*RA_SCS, instead of -2.5*RA_SCS as in the previous example range (18). Therefore, the aforementioned ranges (18) and (19) can be modified to replace (1.5+L)*RA_SCS with 2*RA_SCS, thereby narrowing the range and allowing for more optimized offset determination.
[0135] The UE can determine the value of each offset 520 to be applied to each subsequent RACH attempt 516 (within the limits of the aforementioned range) based on one or more configured or pre-configured tables or other data structures. For example, the base station can configure the UE to apply the offsets identified in Table 2 below to positive frequency offsets, or the offsets identified in Table 3 below to negative frequency offsets:
[0136]
[0137]
[0138] Table 2. RAPID mismatch caused by positive CFO.
[0139] RACH attempt Offset (CFO compensation) N+1 O*M N+2 (O+1)*M N+3 (O+2)*M … … N+X-2 (O+X–3)*M N+X-1 (O+X–2)*M N+X (O+X–1)*M
[0140] Table 3. RAPID mismatch caused by negative CFO.
[0141] Where M represents the configurable CFO compensation step size attempted per RACH (e.g., M = 200Hz or some other configured or pre-configured value), and O represents the configurable start frequency used for CFO compensation (e.g., ...). (or some other function), and X represents the maximum number of RACH attempts to which CFO compensation can be applied. The value of X can depend on the values of O and M. For example, X could be equal to Or some other value.
[0142] While Tables 2 and 3 above refer to example configurations where the UE applies different positive offsets or different negative offsets to each subsequent RACH attempt, these configurations are not limited to this. For example, different values or functions of M, O, and X, or parameters different from M, O, or X, can be applied to RACH attempts in either table. In another example, Tables 2 and 3 can be combined into a single table indicating alternating positive and negative offsets (or some other combination of positive and negative offsets) across RACH attempts, and the UE can accordingly apply positive or negative offsets to different attempts in subsequent RACH attempts. In a further example, multiple RACH attempts can be associated with the same offset instead of the different offsets as in Tables 2 and 3. For example, RACH attempts N+1 and N+2 can both be associated with offset O*M, instead of offsets O*M and (O+1)*M respectively. For example, when M is a large value (e.g., M = 600Hz), the UE can apply the same offset to multiple RACH attempts.
[0143] Still referring to another example Figure 5If a consecutive number (Y) RAPID mismatches are caused by frequency offsets in the same direction (e.g., all positive Doppler shifts or all negative Doppler shifts), the UE may apply CFO compensation. If the UE determines that a consecutive number (Y) RAPID mismatches are all caused by positive CFOs, the UE may apply a negative frequency offset to each subsequent RACH attempt 516, as explained in Table 2 above. Alternatively, if the UE determines that a consecutive number Y RAPID mismatches are all caused by negative CFOs, the UE may apply a positive frequency offset 516 to each subsequent RACH attempt, as explained in Table 3 above. The value of Y may be configured by the base station or pre-configured for the UE (e.g., Y = 3 or some other value). Consecutive RAPID mismatches may include the last (Kth) RAPID mismatch identified by the UE in RAPID attempts 1 to N.
[0144] For example, assuming K=5 and Y=3, the UE determines the RAPID mismatch due to CFO in RACH attempts 1-5 in the following directions: RACH attempts 1 and 2 – negative (K2=2), RACH attempts 3, 4, and 5 – positive (K1=3). In this case, three consecutive RACH attempts (including the last or Kth RACH attempt) are associated with a positive Doppler shift direction, so the UE can determine that there is a high probability that subsequent RACH attempt 516 will also include the same positive Doppler shift direction. As a result, the UE can apply a negative frequency offset to subsequent RACH attempt 516 according to Table 2 above.
[0145] On the other hand, if the consecutive number Y RAPID mismatches caused by frequency offsets in the same direction cannot be determined, the UE can determine which frequency offset direction is associated with more RAPID mismatches (e.g., whether K1>K2 or K2>K1). After this determination, the UE can apply an offset accordingly to subsequent RACH attempts 516 to compensate for that direction. For example, if K1>K2, the UE can apply a negative frequency offset to each subsequent RACH attempt 516 (as explained in Table 2 above), while if K2>K1, the UE can apply a positive frequency offset to each subsequent RACH attempt 516 (as explained in Table 3 above).
[0146] For example, assuming K = 5 and Y = 3, the UE determines the RAPID mismatch due to CFO in RACH attempts 1-5 in the following directions: RACH attempts 1, 2, and 5 - positive (K1 = 3), and RACH attempts 3 and 4 - negative (K2 = 2). In this case, the UE can determine that there are no consecutive number Y RAPID mismatches associated with the same Doppler shift direction (since there are only two consecutive RACH attempts in the same direction in this example). Therefore, the UE can determine that since K1 > K2 (there is more positive Doppler shift), the subsequent RACH attempt 516 is highly likely to also include a positive Doppler shift direction. As a result, the UE can apply the negative frequency offset to the subsequent RACH attempt 516 according to Table 2 above.
[0147] As a result, if the UE cannot determine the consecutive number Y RAPID mismatches caused by frequency offsets in the same direction, the UE can determine which frequency offset direction is associated with more RAPID mismatches (i.e., the majority of directions) and which frequency offset direction is associated with fewer RAPID mismatches (i.e., the minority of directions), and then the UE can apply CFO compensation accordingly. For example, if K1 > K2, the UE can determine that the majority of directions are positive and the minority of directions are negative, while if K2 > K1, the UE can determine that the majority of directions are negative and the minority of directions are positive. However, in some cases, the UE can also determine that the majority of directions do not apply to the last RAPID mismatch (e.g., the Kth RACH attempt). For example, if K1 > K2, the UE can determine in some cases that K1 does not include the last RAPID mismatch, or if K2 > K1, the UE can determine in some cases that K2 does not include the last RAPID mismatch. As a result, the UE may not be able to determine with a high probability whether subsequent RACH attempts 516 will also be associated with the majority of directions (whether K1 or K2).
[0148] For example, suppose N=10 and K=5, RACH attempts 2 and 5 are positive (K1=2), and RACH attempts 1, 3, and 4 are negative (K2=3). Here, since K2>K1, the UE will initially apply a positive frequency offset to subsequent RACH attempts 516 according to Table 3 above. However, in this example, although most directions are negative (K2>K1), the last Kth RAPID in RACH attempt 5 mismatches in a few directions (positive or K1). Therefore, the UE may not be able to determine with a high probability that subsequent RACH attempts 516 will also include negative directions (e.g., they could be changed to positive directions).
[0149] Therefore, when the UE applies CFO compensation to subsequent RACH attempts 516 in most directions, the UE can also monitor these subsequent RACH attempts to determine whether the offset direction should be switched (e.g., from the offset in Table 2 to Table 3, or vice versa). For example, the UE can determine whether a consecutive number of Y RAPID mismatches have occurred due to CFO in a minority direction (K2 if K1>K2, or K1 if K2>K1), including RAPID mismatches associated with the last monitored subsequent RACH attempt. If the UE determines that there are consecutive number Y RAPID mismatches in a minority direction in subsequent RACH attempts, the UE can determine that applying the offset in most directions is inaccurate, and therefore the UE can switch to the offset in the minority direction accordingly. For example, if K1>K2, the UE can switch from applying the offset in Table 2 to the offset in Table 3, and if K2>K1, the UE can switch from applying the offset in Table 3 to the offset in Table 2. The UE can also stop monitoring subsequent RACH attempts at this time.
[0150] For example, suppose the UE starts applying CFO compensation according to Table 3, beginning with subsequent RACH attempt 6. Furthermore, suppose Y = 3, where after performing RACH attempts 1-5 in the example above, the UE determines a RAPID mismatch, despite CFO compensation in the following directions in subsequent RACH attempts 6-10: subsequent RACH attempts 6 and 7 - negative, and subsequent RACH attempts 8 to 10 - positive. In this case, the three consecutive RACH attempts (including the last RACH attempt 10) are associated with a positive Doppler shift direction, and therefore the UE can determine that there is a high probability that additional RACH attempts (e.g., RACH attempts 11 and later) will also include the same Doppler shift direction (positive). As a result, during additional RACH attempts (e.g., 11 and later), the UE can switch from applying a positive frequency offset according to Table 3 to applying a negative frequency offset according to Table 2.
[0151] Therefore, in any of the foregoing examples, the UE may use the applied carrier frequency offset to perform multiple subsequent RACH attempts in an attempt to compensate for uplink Doppler shift effects on message 1 or msgA. However, in some cases where the UE's radio conditions are poor, the UE may not be able to perform subsequent RACH attempts. For example, if the Reference Signal Received Power (RSRP) of the non-HST cell serving the HST UE is below a configured RSRP threshold (e.g., -120 dBM by default, or some other value), the UE may not perform more than N RACH attempts. Therefore, in one example, the UE may perform the CFO compensation / offset, calculation, or determination described in any of the above examples in response to determining that the RSRP of the serving cell is greater than or equal to the RSRP threshold.
[0152] Figure 8Example 800 illustrates the call flow between UE 802 and base station 804. UE 802 may correspond to... Figure 4-7 HST UE 402 or UE 502, 602, 702, and base station 804 can correspond to Figure 4-6 Base stations 404, 504, and 604. Initially, the UE may receive RACH configuration 806 from the base station. The RACH configuration may include the maximum number of preamble transmissions 807 (e.g., the parameter maxPreambleTrans or another name). After receiving the RACH configuration, the UE may attempt one or more random access messages 808. Random access message 808 may correspond to... Figure 4 and 5 The RACH messages 408 and 508 (e.g., in RACH attempts 1 to N) may each include a preamble 809 selected by the UE. In response to transmitting a random access message 808, the UE may receive one or more RARs 810 from the base station, each RAR responding to a random access message. RARs 810 may correspond to RARs 412 and 510 (e.g., in RACH attempts 1 to N), and each may include a RAPID 811 configured by the base station. The number of RARs (e.g., the number N) may be a function of the maximum number of preamble transmissions 807.
[0153] At 812, UE 802 can determine whether the threshold number 813 of (a few) RARs 810 includes mismatched RAPIDs. For example, the UE can determine whether K out of N RARs include RAPIDs that are different from their corresponding preambles. Furthermore, the UE can determine whether each mismatched RAPID in the K RARs is caused by an uplink Doppler shift effect. For example, at 814, the UE can determine whether a frequency offset 816 (or Doppler shift) affects each RAR, and determine the direction of the frequency offset. In one example, at 814, the UE can perform the determination based on the expected RAPID 818, as described above with respect to Equations 1-8. In another example, the UE can perform the determination at 814 based on the expected RAPID 818 and a timing advance 820, as described above with respect to Equations 9-17.
[0154] If UE 802 determines the threshold number of RARs 810 based on frequency offset 816 in 812, which includes a mismatch RAPID, then in 822, the UE may offset the carrier frequency of subsequent random access messages 824 (e.g., in RACH attempt N+1 and beyond). For example, the UE may offset the carrier frequency(s) by transmitting a preamble 825 in each subsequent random access message 824 at a frequency offset relative to the carrier frequency used for random access messages(s) 808. The UE may apply the carrier frequency offset in 822 in response to determining in 826 that the RSRP of the serving cell of the base station 804 serving the UE is greater than or equal to the RSRP threshold.
[0155] The carrier frequency offset that the UE can apply to subsequent random access messages can be within a configured positive or negative offset range 828. For example, UE 802 can offset the carrier frequency for each subsequent random access message to a positive value as described in Table 3 above, or to a negative value as explained in Table 2 above. In one example, range 828 can be a function of the random access preamble subcarrier spacing 830. In another example, range 828 can be a function of the frequency offset 816 determined at 814. In a further example, range 828 can be a function of the maximum Doppler shift 832 in the HST.
[0156] UE 802 may determine the direction (e.g., positive or negative) to apply a frequency offset in 822 in response to a consecutive number of RAPID mismatches in RAR 810, which identifies a threshold number in 834. For example, the UE may identify whether Y consecutive RARs include RAPID mismatches due to CFO. If Y consecutive mismatches are identified, the UE may offset the carrier frequency of each subsequent random access message 824 based on the direction of the frequency offset associated with each consecutive mismatch. For example, if the mismatch is based on a positive CFO, the UE may apply a negative frequency offset in 822, and if the mismatch is based on a negative CFO, the UE may apply a positive frequency offset in 822.
[0157] Otherwise, if UE 802 receives (e.g.) additional RARs 836 in response to (e.g.) subsequent random access messages 824, where each additional RAR includes a RAPID 837 that mismatches with a corresponding one in the subsequent preamble 825 (e.g., due to an incorrect frequency offset direction applied in 822), then at 838, the UE may determine whether Y consecutive mismatches are identified in the RAPIDs of these (e.g.) additional RARs 836. If the UE determines that Y consecutive mismatches are identified in these additional RAPIDs, then at 840, the UE may offset (e.g.) the carrier frequencies used for (e.g.) additional random access messages 842, and the UE transmits the additional random access message 842 to the base station in the opposite direction to that applied in 822. For example, if the UE applies a positive frequency offset to the subsequent random access message 824 in 822 (e.g., according to Table 3), then at 840, the UE may apply a negative frequency offset to the additional random access message 842 (e.g., according to Table 2). Similarly, if the UE applies a negative frequency offset to the subsequent random access message 824 at 822 (e.g., according to Table 2), then at 840, the UE can apply a positive frequency offset to the additional random access message 842 (e.g., according to Table 3). In this way, the likelihood of a successful RACH attempt can be further increased.
[0158] Figure 9 This is a flowchart 900 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, 350, 402, 502, 602, 702, 802; device 1002). Optional aspects are illustrated with dashed lines. This method allows the UE to apply CFO compensation to improve RACH success rate in response to determining a mismatch RAPID in previous RACH attempts caused by uplink Doppler frequency shift effects (e.g., in HST).
[0159] In 902, the UE obtains one or more RARs, each of which includes a RAPID, and each of which is in response to a random access message including a preamble. For example, refer to Figure 8 UE 802 can obtain each of the following RARs 810, each including a RAPID 811. The RAR can be obtained in response to a random access message 808 including a preamble 809 transmitted by the UE to base station 804. The UE (or a component of the UE) can obtain the RAR, for example, by receiving the RAR from base stations 310, 404, 504, 604, and 804 and demodulating the received RAR data. For example, the RX processor 356 of UE 350 can receive the RAR from a base station via one or more antennas 352, and the controller / processor 359 of UE 350 can demodulate the received RAR data and identify the RAPID.
[0160] In one example, the number of one or more RARs can be based on the maximum number of preamble transmissions. For example, refer to Figure 8 UE 802 may obtain a number N (e.g.) RARs 810, where the number N is a function configured for the maximum number of preamble transmissions 807 for the UE. For example, N may be the minimum between the maximum number of preamble transmissions 807 and a pre-configured or configured value (e.g., 10), such as represented by the equation N = minimum value(preambleTransMax, 10).
[0161] In 904, the UE determines the RAPID of the corresponding RAR, which differs from the preamble of the corresponding random access message, in each of the threshold number of RARs in the one or more RARs. For example, refer to Figure 8 In step 812, UE 802 can determine that each of the threshold numbers 813 of RARs 810 includes a preamble different from the corresponding one in the random access messages 808. For example, referring to... Figure 5 UE 502 can determine that K out of N consecutive RACH attempts each include a mismatched RAPID. The UE (or a component of the UE) can perform this determination, for example, by identifying the RAPID in one of the N RARs (e.g., message 2 or msgB), comparing the RAPID with the corresponding preamble in one of the N random access messages (e.g., message 1 or msgA), identifying a mismatch between the RAPID and the preamble, and repeating the identification and comparison for different RAPIDs until K mismatches are identified. For example, after receiving RAR 510 from RX processor 356 in RACH attempt 1, the controller / processor 359 of UE 350 can identify the RAPID in the RAR, compare the RAPID with the preamble in the previously transmitted RACH message 508 during RACH attempt 1, and identify that the RAPID and the preamble are different (for example, the RAPID configured in RAR 510 may indicate preamble 21 or some other value, while the selected preamble included in RACH message 508 is actually preamble 9 or some other different value). The controller / processor 359 can similarly repeat the above process of identifying RAPID mismatches in RACH attempts 2, 3, etc., until K RAPID mismatches are identified.
[0162] In one example, each of the threshold number of RARs in the one or more RARs may include a mismatch RAPID based on the frequency offset of the PRACH received at the base station. For example, refer to Figure 8In 814, UE 802 can determine that the frequency offset 816 (e.g., positive or negative Doppler shift) affects each of the RARs 810, whereby the UE determines the mismatch RAPID in 812. For example, refer to Figure 6 UE 602 can determine that each RACH preamble is carried (e.g., in...). Figure 8 In the random access message 808, PRACH 606 is in the positive direction (at a frequency higher than that of transmission, such as...) Figure 6 PRACH 1) or negative direction (at a frequency lower than that of transmission, such as Figure 6 The uplink Doppler shift on PRACH 2) is received by base station 604. As a result of this frequency offset or uplink Doppler shift in PRACH 606, the UE can determine that the base station has misidentified each PRACH as including a preamble different from the preamble actually transmitted by the UE.
[0163] In one example, the frequency offset can be determined based on the expected RAPID received at the base station. For example, refer to Figure 8 In step 814, UE 802 can determine the existence of a frequency offset 816 causing the mismatch RAPID based on the expected RAPID 818 already received by UE from base station 804 as a result of uplink Doppler frequency shift, and determine the direction (positive or negative) of the frequency offset 816. For example, UE can apply the aforementioned equations 1-7 to identify the expected RAPID (e.g., RAPID in one example). pos or RAPID neg ), and in response to the expected RAPID, the aforementioned equation 8 is applied to determine the presence and direction of the frequency offset 816.
[0164] In one example, the frequency offset can be further determined based on timing advance. For example, refer to Figure 8 In step 814, UE 802 can determine the presence of a frequency offset 816 causing the mismatch RAPID based on the timing advance 820 reported by base station 804 and the expected RAPID 818, and determine the direction of the frequency offset 816. For example, in one example, the UE can apply the aforementioned equations 9-16 to identify the timing advance (e.g., T in one example). NW ), expected RAPID (e.g., in one example) or ) and for the intended RAPID (e.g., I D The cyclic shift of the frequency offset 816 is performed, and in response to these parameters, the aforementioned Equation 17 is applied to determine the presence and direction of the frequency offset 816.
[0165] In 906, the UE responds to this determination by offsetting the carrier frequency used for each of one or more subsequent random access messages. For example, refer to Figure 8 In response to determining the mismatch RAPID of the threshold number 813 due to frequency offset 816 at 812, at 822, the UE may offset the carrier frequencies(s) used for subsequent random access messages 824 to compensate for frequency offset 816. For example, refer to Figure 7 UE 702 can, for example, offset the carrier frequency used for each RACH preamble by transmitting each preamble in PRACH 704 with different frequency offsets (positive or negative) to compensate for the Doppler shift effect. (See reference...) Figure 5 UE 502 may apply an offset 520 to the carrier frequency 514 used for each subsequent RACH message 518. As an example, if the UE transmits random access messages 808 at a carrier frequency of 3.8 GHz, when transmitting subsequent random access messages 824, the UE may apply an offset of 600 Hz or -600 Hz (or some other positive or negative value) to the 3.8 GHz frequency (e.g., in one example, causing the messages to be transmitted at offset carrier frequencies of 3.8000006 GHz or 3.7999994 GHz, respectively). The offset may be one of the CFO compensation values identified, for example, in Table 2 or Table 3 above. The UE (or a component of the UE) may perform the offset, for example, by identifying the offset to be applied to the carrier frequency used for each subsequent random access message and transmitting each subsequent random access message at the offset carrier frequency. For example, in response to determining the threshold number of mismatch RAPIDs due to frequency offset, the controller / processor 359 of the UE 350 may identify the offset for each subsequent random access message from Table 2 or Table 3 (e.g., depending on the direction of the frequency offset), and the TX processor 368 may transmit the subsequent random access message to the base station 310 via one or more antennas 352 at the offset carrier frequency identified by the controller / processor 359 for each subsequent random access message.
[0166] In one example, each of the carrier frequencies can be offset based on a value within a range of random access precode subcarrier intervals. For example, refer to Figure 8 The offset can be within a configured positive or negative range of 828. Range 828 can be a function of the random access preamble subcarrier spacing 830. For example, refer to... Figure 5 Each offset of 520 (e.g., corresponding to one of the values in Table 2 or Table 3 above) can be limited based on the preamble subcarrier spacing Δf RA Within the configured range. For example, this range could be one of the aforementioned ranges (18) or (19), which is RA_SCS(Δf RA The function of ).
[0167] In one example, this range could be a function of the frequency offset of the PRACH received at the base station. For example, refer to Figure 6 and 8 Range 828 may be based on a frequency offset 816 affecting PRACH 606 carrying the RACH preamble received by base stations 604 and 804, the frequency offset 816 being determined by UE 802 at 814. For example, refer to Figure 5 Either of the ranges (18) or (19) above can be a function of L, the value of which can depend on whether the frequency offset 816 is up to one PRACH subcarrier (e.g., L = 0) or up to two PRACH subcarriers (e.g., L = 1).
[0168] In one example, the range can be further based on the maximum Doppler shift in the HST deployment. For example, refer to Figure 8 The range 828 may be based on the maximum Doppler frequency shift 832 in the HST (e.g., the range 828 may be...). Figure 8 (A function of the maximum value of the mid-frequency offset of 816). For example, refer to... Figure 5 Either of the ranges (18) or (19) above can be a function of L or RA_SCS, where either value can be further optimized to depend on the maximum uplink Doppler shift observed in the HST. For example, the maximum uplink Doppler shift can be twice the maximum Doppler shift typically observed in the HST (e.g., 2 × 1230 Hz = 2460 Hz for HSTs at 350 km / h, or assuming Δf RA = Approximately two PRACH subcarriers at 1.25 kHz). Figure 4 An example of an HST deployment is shown in the figure.
[0169] In one example, each of the carrier frequencies may shift in response to the RSRP associated with the serving cell exceeding a threshold. For example, refer to Figure 8 UE 802 may offset the carrier frequency at 822 in response to determining at 826 that the RSRP of the serving cell of base station 804 serving the UE is greater than or equal to the RSRP threshold. For example, refer to Figure 4 and 5 If the RSRP of a non-HST cell serving an HST UE (e.g., where base station 404 serves a cell serving HST UE 402) is greater than or equal to a configured RSRP threshold (e.g., -120 dBM or some other value), then UEs 402 and 502 may apply an offset 520 to the carrier frequency 514 used for each subsequent RACH message 518.
[0170] In one example, each of the carrier frequencies can be offset by a different value. For example, refer to Figure 5 , 7 UEs 502, 702, and 802 may apply an offset 520 (e.g., in 822) to the carrier frequency 514 used for subsequent RACH messages 518 according to any one (or both) of the aforementioned Tables 2 and 3, where each offset is different for each subsequent RACH message, such as... Figure 7 As explained in the text. For example, a subsequent RACH message in RACH attempt N+1 can be offset by a value -O*M (or its positive version in another table), the next subsequent RACH message in RACH attempt N+2 can be offset by a different value -(O+1)*M (or its positive version), and so on, where M represents the configurable offset for each RACH attempt, such as M = 200Hz or some other value, and O represents the configurable start frequency used for the offset, such as... Or some other function. Furthermore, at least one of the different values can be a function of the maximum number (X) of the one or more subsequent random access messages. For example, a subsequent RACH message in RACH attempt N+X-2 can be offset to another different value -(O+X-3)*M (or its positive version), the next subsequent RACH message in RACH attempt N+X-1 can be offset to a further different value -(O+X-2)*M (or its positive version), and so on, where X represents the maximum number of RACH attempts to which CFO compensation can be applied. The value of X can depend on the values of O and M. For example, X can be equal to Or some other value.
[0171] In one example, one or more of the carrier frequencies can be offset by the same value. For example, refer to Figure 5 and 8 UEs 502 and 802 can apply an offset 520 (e.g., in 822) to the carrier frequency 514 used for subsequent RACH messages 518 according to any one (or both) of the aforementioned Tables 2 and 3, where one or more of the offsets are the same for subsequent RACH messages. For example, RACH attempts N+1 and N+2 can both be associated with the same offset O*M (or its negative version in another table), instead of being associated with different offsets O*M and (O+1)*M (or their negative versions in another table), respectively. For example, when M is a large value (e.g., M = 600 Hz), the UE can apply the same offset to multiple RACH attempts. Similarly, the same value can be a function of the maximum number (X) of one or more subsequent random access messages. For example, RACH attempts N+X–2 and N+X–1 can both be associated with the same offset -(O+X–3)*M, instead of being associated with different offsets -(O+X–3)*M and -(O+X–2)*M, respectively.
[0172] In 908, the UE can identify a coherent mismatch in threshold amounts between the RAPID and the preamble, wherein the carrier frequency is offset by either a positive or negative value in response to this identification. For example, refer to Figure 8 In 834, the UE can identify consecutive RAPID mismatches of a threshold amount Y between RAPID 811 and preamble 809. In 834, if Y consecutive mismatches are identified, then in 822, the UE can offset the carrier frequency of each subsequent random access message 824 based on whether the frequency offset 816 determined in 814 is positive or negative. For example, refer to... Figure 5 If UE 502 determines that Y consecutive RAPID mismatches within RACH attempts 1 to K are all due to positive frequency offsets (e.g., Figure 8 The frequency offset of 816 is positive, such as relative to Figure 6 If the UE determines that Y consecutive RAPID mismatches within RACH attempts 1 to K are due to negative frequency offsets (e.g., PRACH 1), then the UE can apply the negative frequency offsets from Table 2 to each subsequent RACH attempt 516. Alternatively, if the UE determines that Y consecutive RAPID mismatches within RACH attempts 1 to K are due to negative frequency offsets (e.g., PRACH 1), then the UE can apply the negative frequency offsets from Table 2 to each subsequent RACH attempt 516. Figure 8 The frequency offset of 816 is negative, such as relative to Figure 6 If PRACH 2 is specified, the UE can apply the positive frequency offset from Table 3 to each subsequent RACH attempt 516. The value of Y can be configured by the base station or pre-configured for the UE (e.g., Y = 3 or some other value). The UE (or a component of the UE) can, for example, identify a coherent mismatch between the RAPID and the preamble by counting each instance where RAPID 811 differs from the preamble 809 in RACH attempts 1 through K, determining that the count at least totals the threshold amount (Y) in the coherent RACH attempts, and that all counted instances for which the threshold amount is determined have experienced the same directional frequency offset. For example, the controller / processor 359 of UE 350 can identify three coherent RACH attempts 3, 4, and 5 as including mismatched RAPIDs due to positive frequency offsets (assuming K = 5 and Y = 3).
[0173] In 910, the UE may obtain additional RARs, each of which includes an additional RAPID, and in response to one of the subsequent random access messages including a subsequent preamble. For example, refer to Figure 8UE 802 may obtain (a number of) additional RARs 836 from base station 804 in response to subsequent random access messages 824 transmitted by the UE along with subsequent preamble 825. Each of the additional RARs may include an additional RAPID 837 configured by the base station. The UE (or a component of the UE) may obtain these additional RARs, for example, by receiving the additional RARs and demodulating the data in these additional RARs. For example, RX processor 356 may receive the additional RARs via one or more antennas 352, and controller / processor 359 may demodulate the data received from RX processor 356.
[0174] In 912, the UE can further determine a coherent mismatch in the threshold amount between the additional RAPID and the subsequent preamble. For example, refer to Figure 8 In step 838, the UE can determine a coherent RAPID mismatch between the additional RAPID 837 and the subsequent preamble 825. The threshold amount Y can be compared with the above 908 (and Figure 8 The threshold values Y in 834 are the same or different. The UE (or a component of the UE) may perform further determination, for example, according to the following procedure. First, if the controller / processor 359 of the UE 350 cannot determine in 834 that the Y consecutive RAPID mismatches are all due to frequency offsets in the same direction, the controller / processor 359 may determine the majority direction and the minority direction of the frequency offset. Next, the controller / processor 359 may receive (a few) additional RARs 836 including additional RAPIDs 837, and the controller / processor 359 may compare the Y consecutive additional RAPIDs with the subsequent preamble 825 of the corresponding subsequent random access message 824. The controller / processor 359 may then determine whether these additional RAPID mismatches are caused by frequency offsets in the minority direction.
[0175] Finally, at 914, the UE may, in response to this further determination, offset the carrier frequency used for each of one or more additional random access messages by one of a positive or negative value, wherein the carrier frequencies used for the one or more subsequent random access messages are offset by the other of the positive or negative value. For example, refer to Figure 8At 838, if the UE determines that Y consecutive mismatches are identified in the additional RAPID 837 of the additional RAR 836, then at 840, the UE may offset the carrier frequency for the additional random access message 842 that the UE can transmit to the base station 804. The UE may offset these carrier frequencies in the opposite direction to the direction applied at 822. For example, if the UE applies a positive frequency offset to the subsequent random access message 824 at 822 (e.g., according to Table 3), then at 840 the UE may apply a negative frequency offset to the additional random access message 842 (e.g., according to Table 2). Similarly, if the UE applies a negative frequency offset to the subsequent random access message 824 at 822 (e.g., according to Table 2), then at 840 the UE may apply a positive frequency offset to the additional random access message 842 (e.g., according to Table 3). The UE (or a component of the UE) may perform a carrier frequency offset for each additional random access message, for example, by identifying the carrier frequency offset to be applied for each additional random access message and transmitting each additional random access message at the offset carrier frequency. For example, in response to further determining a number of mismatch additional RAPIDs due to a threshold number of frequency offsets in a few directions, the controller / processor 359 of the UE 350 may identify the offset for each additional random access message from Table 2 or Table 3 (e.g., in the opposite direction applied to subsequent random access messages), and the TX processor 368 may transmit these additional random access messages to the base station 310 via one or more antennas 352 at the offset carrier frequency identified by the controller / processor 359 for each additional random access message.
[0176] Figure 10Figure 1002 illustrates an example of the hardware implementation of device 1000. Device 1002 is a UE and includes a cellular baseband processor 1004 (also referred to as a modem) coupled to a cellular RF transceiver 1022 and one or more Subscriber Identity Module (SIM) cards 1020, an application processor 1006 coupled to a Secure Digital Card (SD) card 1008 and a screen 1010, a Bluetooth module 1012, a Wireless Local Area Network (WLAN) module 1014, a Global Positioning System (GPS) module 1016, and a power supply 1018. The cellular baseband processor 1004 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1022. The cellular baseband processor 1004 may include computer-readable media / memory. The computer-readable media / memory may be non-transient. The cellular baseband processor 1004 is responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1004, the software causes the cellular baseband processor 1004 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1004 during software execution. The cellular baseband processor 1004 further includes a receiving component 1030, a communication manager 1032, and a transmission component 1034. The communication manager 1032 includes the one or more of the described components. The components within the communication manager 1032 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1004. The cellular baseband processor 1004 can be a component of the UE 350 and may include a memory 360 and / or at least one of the following: a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1002 may be a modem chip and include only the baseband processor 1004, and in another configuration, the device 1002 may be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional modules of device 1002.
[0177] The communication manager 1032 includes a RAR component 1040 configured to acquire one or more RARs, each of the one or more RARs including a RAPID, and each of the one or more RARs responding to a random access message including a preamble, for example, as described in conjunction with 902. The communication manager 1032 further includes a determining component 1042 that receives input from the RAR component 1040 in the form of one or more RARs, and is configured to determine, in each of a threshold number of RARs in the one or more RARs, that the RAPID of the corresponding RAR differs from the preamble of the corresponding random access message, for example, as described in conjunction with 904. The communication manager 1032 further includes an offsetting component 1044 that receives input in the form of the determining component 1042, and is configured to offset the carrier frequency of each of one or more subsequent random access messages in response to the determining, for example, as described in conjunction with 906.
[0178] The communication manager 1032 may further include an identification component 1046 that receives input from the RAR component 1040 in the form of a RAPID and a preamble, and is configured to identify a coherent mismatch of a threshold amount between the RAPID and the preamble, for example, as described in conjunction with 908. The carrier frequency may be offset (by the offset component 1044) by either a positive or negative value in response to the identification by the identification component 1046.
[0179] RAR component 1040 may be further configured to obtain additional RARs, each of which includes an additional RAPID, and in response to one of the subsequent random access messages including a subsequent preamble, for example, as described in conjunction with 910. Determining component 1042 may receive input in the form of additional RARs from RAR component 1040, and may be further configured to further determine a coherent mismatch of a threshold amount between the additional RAPID and the subsequent preamble, for example, as described in conjunction with 912. Offset component 1044 may receive input in the form of this further determination from determining component 1042, and may be further configured to, in response to this further determination, offset the carrier frequency used for each of one or more additional random access messages by one of a positive or negative value, wherein the carrier frequency used for one or more subsequent random access messages is offset by the other of a positive or negative value, for example, as described in conjunction with 914.
[0180] The device may include execution Figure 8 and Figure 9 The additional components of each block of the algorithm in the aforementioned flowchart. Therefore, Figure 8 and Figure 9Each block in the aforementioned flowchart can be executed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.
[0181] In one configuration, device 1002 (and specifically cellular baseband processor 1004) includes: means for obtaining one or more random access commands (RARs), wherein each of the one or more RARs includes a RAPID, and wherein each of the one or more RARs is in response to a random access message including a preamble. Device 1002, and particularly cellular baseband processor 1004, further includes means for determining, in each of the one or more RARs, a threshold number of RARs, that the RAPID of the corresponding RAR differs from the preamble of the corresponding random access message. Device 1002, and particularly cellular baseband processor 1004, further includes means for offsetting the carrier frequency for each of the one or more subsequent random access messages in response to this determination.
[0182] In one configuration, device 1002 (and in particular cellular baseband processor 1004) may include means for identifying a coherent mismatch of a threshold amount between RAPID and preamble, wherein the carrier frequency is offset by either a positive or negative value in response to the identification.
[0183] In one configuration, the means for obtaining may be further configured to obtain additional RARs, each of which includes an additional RAPID, and in response to one of the subsequent random access messages including a subsequent preamble. The means for determining may be further configured to further determine a coherent mismatch of a threshold amount between the additional RAPID and the subsequent preamble. The means for offsetting may be further configured to, in response to this further determination, offset the carrier frequencies used for each of the one or more additional random access messages by one of a positive or negative value, wherein the carrier frequencies used for the one or more subsequent random access messages are offset by the other of the positive or negative value.
[0184] The aforementioned apparatus may be one or more of the aforementioned components in device 1002 configured to perform the functions described by the aforementioned apparatus. As described above, device 1002 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the aforementioned apparatus may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described by the aforementioned apparatus.
[0185] Therefore, aspects of this disclosure allow a UE to apply CFO compensation to improve RACH success rate in response to determining a mismatch RAPID in a previous RACH attempt, typically caused by uplink Doppler shift effects in the HST. When attempting to perform RACH with a base station, the UE may obtain one or more RARs, each including a RAPID, in response to transmitting a random access message, each including a preamble. If the UE determines a RAPID mismatch in each of these RARs within a threshold number of RARs, where such a mismatch is caused by a frequency offset (uplink Doppler shift) in the PRACH received by the base station, the UE may offset the carrier frequency used for each subsequent random access message transmitted by the UE. When the mismatch RAPID is caused by such uplink Doppler shift, offsetting the carrier frequency can resolve the RAPID mismatch and thus allow for improved RACH success rate. Furthermore, to determine the frequency direction applied in the offset to resolve the RAPID mismatch, the UE may identify whether there is a coherent mismatch of a threshold amount between the RAPID and the preamble, and the UE may offset the carrier frequency used for subsequent random access messages by a positive or negative value in response to this identification. If a coherent RAPID mismatch of the threshold amount does not exist, then if a subsequent random access message includes a coherent additional RAPID mismatch of the threshold amount caused by a frequency offset in the opposite direction, the UE can determine to change the offset direction in the additional random access message (e.g., from positive to negative, or vice versa). As a result, the RACH success rate can be further improved.
[0186] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is an explanation of exemplary methods. It should be understood that the specific order or hierarchy of the boxes in these process / flowcharts can be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the various boxes in an exemplary order and are not intended to be limited to the specific order or hierarchy presented.
[0187] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element, unless specifically stated otherwise, are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the time of” should be interpreted as meaning “under this condition,” rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only imply that an action will occur when a condition is met, without requiring a specific or immediate temporal constraint for the action to occur. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to or overriding other aspects. Unless specifically stated otherwise, the term “some / a” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. Elements of all aspects described throughout this disclosure that are structural and functional equivalents known now or hereafter to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended as a donation to the public, whether or not such disclosure is expressly stated in the claims. The terms “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “apparatus.” Thus, no claim element should be interpreted as an apparatus plus a function unless the element is explicitly stated using the phrase “apparatus for…”.
[0188] The following examples are merely illustrative and can be combined with other embodiments or aspects of the teachings described herein without limitation.
[0189] Example 1 is a method for wireless communication at a user equipment (UE), comprising: obtaining one or more random access responses (RARs), wherein each of the one or more RARs includes a random access preamble identifier (RAPID), and wherein each of the one or more RARs is responsive to a random access message including a preamble; determining, in each of the one or more RARs a threshold number of RARs, that the RAPID of the corresponding RAR is different from the preamble of the corresponding random access message; and offsetting, in response to the determination, a carrier frequency for each of the one or more subsequent random access messages.
[0190] Example 2 is the method of Example 1, wherein the number of the one or more RARs can be based on the maximum number of preamble transmissions.
[0191] Example 3 is a method of either Example 1 or 2, wherein each of the threshold number of RARs in the one or more RARs includes a mismatch RAPID based on the frequency offset of the Physical Random Access Channel (PRACH) received at the base station.
[0192] Example 4 is the method of Example 3, where the frequency offset is determined based on the expected RAPID received at the base station.
[0193] Example 5 is the method of Example 4, where the frequency offset is further determined based on timing advance.
[0194] Example 6 is a method of any of Examples 1 to 5, wherein each of the carrier frequencies can be offset by a value within a range based on the random access preamble subcarrier spacing.
[0195] Example 7 is the method of Example 6, where the range is a function of the frequency offset of the Physical Random Access Channel (PRACH) received at the base station.
[0196] Example 8 is a method of either Example 6 or 7, where the range is further based on the maximum Doppler shift in a high-speed train (HST) deployment.
[0197] Example 9 is a method of any of Examples 1 to 8, wherein each of the carrier frequencies is offset in response to the reference signal received power (RSRP) associated with the serving cell exceeding a threshold.
[0198] Example 10 is a method of any of Examples 1 through 9, where each of the carrier frequencies is offset by a different value.
[0199] Example 11 is a method of Example 10, wherein at least one of the distinct values is a function of the maximum number of one or more subsequent random access messages.
[0200] Example 12 is a method of any of Examples 1 through 9, wherein one or more of the carrier frequencies are offset by the same value.
[0201] Example 13 is a method of any of Examples 1 to 12, further comprising: identifying a coherent mismatch of a threshold amount between the RAPID and the preamble, wherein the carrier frequency is offset by either a positive or negative value in response to the identification.
[0202] Example 14 is a method of any of Examples 1 to 12, further comprising: obtaining additional RARs, wherein each of these additional RARs includes an additional RAPID, and in response to one of subsequent random access messages including a subsequent preamble; further determining a coherent mismatch of a threshold amount between the additional RAPID and the subsequent preamble; and in response to the further determination, offsetting the carrier frequencies used for each of the one or more additional random access messages by one of a positive or a negative value, wherein the carrier frequencies used for the one or more subsequent random access messages are offset by the other of the positive or negative value.
[0203] Example 15 is an apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable, when executed by the processor, to cause the apparatus to: obtain one or more random access responses (RARs), wherein each of the one or more RARs includes a random access preamble identifier (RAPID), and wherein each of the one or more RARs responds to a random access message including a preamble; determines, in each of a threshold number of RARs among the one or more RARs, that the RAPID of the corresponding RAR is different from the preamble of the corresponding random access message; and, in response to the determination, offset the carrier frequency for each of the one or more subsequent random access messages.
[0204] Example 16 is an apparatus of Example 15, wherein each of the threshold number of RARs in the one or more RARs includes a mismatch RAPID based on the frequency offset of the Physical Random Access Channel (PRACH) received at the base station.
[0205] Example 17 is an apparatus of Example 16, wherein the frequency offset is determined based on the expected RAPID received at the base station.
[0206] Example 18 is a device of Example 17, wherein the frequency offset is further determined based on timing advance.
[0207] Example 19 is an apparatus of any of Examples 15 to 18, wherein each of the carrier frequencies can be offset by a value within a range based on the random access preamble subcarrier spacing.
[0208] Example 20 is an apparatus of Example 19, wherein the range is a function of the frequency offset of the Physical Random Access Channel (PRACH) received at the base station.
[0209] Example 21 is a device of either Example 19 or 20, wherein the range is further based on the maximum Doppler shift in a high-speed train (HST) deployment.
[0210] Example 22 is an apparatus of any of Examples 15 to 21, wherein each of the carrier frequencies is offset in response to the reference signal received power (RSRP) associated with the serving cell exceeding a threshold.
[0211] Example 23 is an apparatus of any of Examples 15 to 22, wherein each of the carrier frequencies is offset by a different value, wherein at least one of these different values is a function of the maximum number of one or more subsequent random access messages.
[0212] Example 24 is an apparatus of any of Examples 15 to 22, wherein one or more of the carrier frequencies are offset by the same value.
[0213] Example 25 is an apparatus of any of Examples 15 to 24, wherein, when executed by the processor, the apparatus further causes the apparatus to: identify a coherent mismatch of a threshold amount between the RAPID and the preamble, wherein the carrier frequency is offset by either a positive or negative value in response to the identification.
[0214] Example 26 is an apparatus of any of Examples 15 to 24, wherein, when executed by the processor, the apparatus further causes to: obtain an additional RAR, wherein each of the additional RARs includes an additional RAPID, and in response to one of the subsequent random access messages including a subsequent preamble; further determine a coherent mismatch of a threshold amount between the additional RAPID and the subsequent preamble; and in response to the further determination, offset the carrier frequency used for each of the one or more additional random access messages by one of a positive or negative value; wherein the carrier frequencies used for the one or more subsequent random access messages are offset by the other of the positive or negative value.
[0215] Example 27 is an apparatus for wireless communication, comprising: means for obtaining one or more random access responses (RARs), wherein each of the one or more RARs includes a random access preamble identifier (RAPID), and wherein each of the one or more RARs is responsive to a random access message including a preamble; means for determining, in each of the one or more RARs, a threshold number of RARs, that the RAPID of a corresponding RAR is different from the preamble of a corresponding random access message; and means for offsetting a carrier frequency for each of the one or more subsequent random access messages in response to the determination.
[0216] Example 28 is an apparatus of Example 27, further comprising: means for identifying a coherent mismatch of a threshold amount between the RAPID and the preamble, wherein the carrier frequencies are offset by either a positive or negative value in response to the identification.
[0217] Example 29 is an apparatus of Example 27, wherein the means for obtaining is further configured to obtain additional RARs, each of which includes an additional RAPID and is in response to one of subsequent random access messages including a subsequent preamble; wherein the means for determining is configured to further determine a coherent mismatch of a threshold amount between the additional RAPID and the subsequent preamble; and wherein the means for offsetting is further configured to offset the carrier frequency used for each of the one or more additional random access messages by one of a positive or negative value in response to the further determination; wherein the carrier frequencies used for the one or more subsequent random access messages are offset by the other of the positive or negative value.
[0218] Example 30 is a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to: obtain one or more random access responses (RARs), wherein each of the one or more RARs includes a random access preamble identifier (RAPID), and wherein each of the one or more RARs responds to a random access message including a preamble; determine, in each of the one or more RARs a threshold number of RARs, that the RAPID of the corresponding RAR is different from the preamble of the corresponding random access message; and, in response to the determination, offset the carrier frequency for each of the one or more subsequent random access messages.
Claims
1. A method for performing wireless communication at a user equipment (UE), comprising: Obtain one or more Random Access Responses (RARs), each of the one or more RARs including a Random Access Prefix Identifier (RAPID), and each of the one or more RARs responding to a random access message including a prefix; In each of the threshold number of RARs in the one or more RARs, determine an identifier for the corresponding RAR whose RAPID is different from the preamble of the corresponding random access message; as well as In response to the determination, the carrier frequency is offset for each of one or more subsequent random access messages.
2. The method of claim 1, wherein the number of said one or more RARs is based on the maximum number of preamble transmissions.
3. The method of claim 1, wherein each of the threshold number of RARs in the one or more RARs includes a mismatch RAPID based on the frequency offset of the Physical Random Access Channel (PRACH) received at the base station.
4. The method of claim 3, wherein the frequency offset is determined based on the expected RAPID received at the base station.
5. The method of claim 4, wherein the frequency offset is further determined based on timing advance.
6. The method of claim 1, wherein each of the carrier frequencies is offset by a value within a range based on the random access preamble subcarrier interval.
7. The method of claim 6, wherein the range is a function of the frequency offset of the Physical Random Access Channel (PRACH) received at the base station.
8. The method of claim 6, wherein the range is further based on the maximum Doppler shift in the high-speed train HST deployment.
9. The method of claim 1, wherein each of the carrier frequencies is offset in response to a reference signal received power RSRP associated with the serving cell exceeding a threshold.
10. The method of claim 1, wherein each of the carrier frequencies is offset by a different value.
11. The method of claim 10, wherein at least one of the different values is a function of the maximum number of the one or more subsequent random access messages.
12. The method of claim 1, wherein one or more of the carrier frequencies are offset by the same value.
13. The method of claim 1, further comprising: A coherent mismatch of a threshold amount is identified between the RAPID and the preamble, wherein the carrier frequency is offset by either a positive or negative value in response to the identifier.
14. The method of claim 1, further comprising: Obtain additional RARs, each of which includes an additional RAPID, and respond to one of the subsequent random access messages including a subsequent preamble; Further determine the coherence mismatch of the threshold amount between the additional RAPID and the subsequent preamble; and In response to the further determination, the carrier frequency offset for each of one or more additional random access messages will be either positive or negative; The carrier frequency used for the one or more subsequent random access messages is offset by either the positive value or the negative value.
15. An apparatus for wireless communication, comprising: processor; Memory coupled to the processor; as well as Instructions, which are stored in the memory and, when executed by the processor, are operable to cause the device to: Obtain one or more Random Access Responses (RARs), each of the one or more RARs including a Random Access Prefix Identifier (RAPID), and each of the one or more RARs responding to a random access message including a prefix; In each of the threshold number of RARs in the one or more RARs, determine an identifier for the corresponding RAR whose RAPID is different from the preamble of the corresponding random access message; as well as In response to the determination, the carrier frequency is offset for each of one or more subsequent random access messages.
16. The apparatus of claim 15, wherein each of the threshold number of RARs in the one or more RARs includes a mismatch RAPID based on the frequency offset of the Physical Random Access Channel (PRACH) received at the base station.
17. The apparatus of claim 16, wherein the frequency offset is determined based on an expected RAPID received at the base station.
18. The apparatus of claim 17, wherein the frequency offset is further determined based on timing advance.
19. The apparatus of claim 15, wherein each of the carrier frequencies is offset by a value within a range based on the random access preamble subcarrier interval.
20. The apparatus of claim 19, wherein the range is a function of the frequency offset of the Physical Random Access Channel (PRACH) received at the base station.
21. The apparatus of claim 19, wherein the range is further based on the maximum Doppler shift in a high-speed train HST deployment.
22. The apparatus of claim 15, wherein each of the carrier frequencies is offset in response to a reference signal received power RSRP associated with the serving cell exceeding a threshold.
23. The apparatus of claim 15, wherein each of the carrier frequencies is offset by a different value, wherein at least one of the different values is a function of the maximum number of the one or more subsequent random access messages.
24. The apparatus of claim 15, wherein one or more of the carrier frequencies are offset by the same value.
25. The apparatus of claim 15, wherein the instructions, when executed by the processor, further cause the apparatus to: A coherent mismatch of a threshold amount is identified between the RAPID and the preamble, wherein the carrier frequency is offset by either a positive or negative value in response to the identifier.
26. The apparatus of claim 15, wherein the instructions, when executed by the processor, further cause the apparatus to: Obtain additional RARs, each of which includes an additional RAPID, and respond to one of the subsequent random access messages including a subsequent preamble; Further determine the coherence mismatch of the threshold amount between the additional RAPID and the subsequent preamble; and In response to the further determination, the carrier frequency offset for each of one or more additional random access messages will be either positive or negative; The carrier frequency used for the one or more subsequent random access messages is offset by either the positive value or the negative value.
27. The apparatus of claim 15, wherein the number of said one or more RARs is based on the maximum number of preamble transmissions.
28. A device for wireless communication, comprising: A means for obtaining one or more random access response RARs, each of the one or more RARs including a random access preamble identifier RAPID, and each of the one or more RARs responding to a random access message including a preamble. A means for determining, in each of the threshold number of RARs in the one or more RARs, the identifier of the RAPID of the corresponding RAR that is different from the preamble of the corresponding random access message. as well as A means for offsetting the carrier frequency for each of one or more subsequent random access messages in response to the determination.
29. The apparatus of claim 28, further comprising: A means for identifying a coherent mismatch of a threshold amount between the RAPID and the preamble, wherein the carrier frequencies are offset by either a positive or a negative value in response to the identification.
30. The device as claimed in claim 28, The means for obtaining is further configured to obtain additional RARs, each of which includes an additional RAPID and is in response to one of the subsequent random access messages including a subsequent preamble. The means for determining this is configured to further determine a coherent mismatch in the threshold amount between the additional RAPID and the subsequent preamble; and The means for offsetting is further configured to offset the carrier frequency used for each of one or more additional random access messages by a positive or negative value in response to the further determination. The carrier frequency used for the one or more subsequent random access messages is offset by either the positive value or the negative value.
31. A computer-readable medium storing computer-executable code, said code, when executed by a processor, causing the processor to: Obtain one or more Random Access Responses (RARs), each of the one or more RARs including a Random Access Prefix Identifier (RAPID), and each of the one or more RARs responding to a random access message including a prefix; In each of the threshold number of RARs in the one or more RARs, determine an identifier for the corresponding RAR whose RAPID differs from the preamble of the corresponding random access message; and In response to the determination, the carrier frequency is offset for each of one or more subsequent random access messages.
Citation Information
Patent Citations
Signal transmission method, UE, base station and computer readable medium
CN111385909A
Random access handling in single frequency network with unidirectional antenna node arrangement
US20170289834A1
