Associating polarization with random access channel transmissions

Abstract

Aspects of the present disclosure relate to methods, devices, and systems that support associating polarization types with random access channel transmissions. For example, a UE and a network entity may share polarization information, such as when the network entity configures the UE to associate a polarization type with RACH resources. The UE may perform a RACH occasion (RO) in the time-frequency domain and / or in the polarization domain during an initial access procedure, thereby enhancing coverage and reliability of a random access channel during uplink synchronization, among other benefits.

Description

[0001] CROSS REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 396,874, filed on August 10, 2022, entitled ASSOCIATING POLARIZATION TO RANDOMACCESS CHANNEL TRANSMISSIONS, the entire text of which is hereby incorporated by reference. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly, to network access procedures for user equipment (UE). Background Art

[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may be further referred to as an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. Each network communication device (e.g., a base station) may support wireless communication of one or more user communication devices, which may be further referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of a wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technologies, fourth generation (4G) radio access technologies, fifth generation (5G) radio access technologies, and other suitable radio access technologies after 5G (e.g., sixth generation (6G)).

[0005] The user communication device performs an initial access procedure, such as a random access channel (RACH) procedure, to acquire uplink synchronization with a network entity (e.g., a gNB of a wireless communication system supporting 5G radio access technology). The RACH procedure includes the UE sending a RACH preamble (e.g., Msg1) to the gNB, and after a random access response from the gNB, sending a connection request or a scheduled transmission (e.g., Msg3) to the gNB. In response to the connection request, the gNB sends back a connection establishment response indicating a successful uplink connection between the UE and the gNB. Summary of the invention

[0006] The present disclosure relates to methods, devices and systems that support associating polarization types with random access channel transmissions. A UE and a network entity share polarization information, such as when the network entity configures the UE to associate polarization types with RACH resources. The UE may perform RACH opportunities (ROs) in the time-frequency domain and / or polarization domain during an initial access procedure, thereby enhancing the coverage and reliability of a random access channel during uplink synchronization.

[0007] Some implementations of the methods and apparatus described herein may further include a UE comprising a processor and a memory coupled to the processor, the processor configured to receive a configuration indicating a polarization type associated with a physical random access channel (PRACH) from a network entity, and transmit a random access message according to the polarization type associated with the PRACH.

[0008] In some implementations of the methods and apparatus described herein, transmitting the random access message includes performing a RO using a Msg1 transmission of the polarization type.

[0009] In some embodiments of the methods and apparatus described herein, the configuration indicates an association of the polarization type with ROs multiplexed in the frequency domain within one PRACH duration.

[0010] In some embodiments of the methods and apparatus described herein, the configuration indicates an association of polarization type with RO at a plurality of PRACH duration instances.

[0011] In some embodiments of the methods and apparatus described herein, the configuration indicates an association of one polarization type with RO at a plurality of PRACH duration instances.

[0012] In some embodiments of the methods and apparatus described herein, the configuration indicates association of different polarization types with RO at a plurality of PRACH duration instances.

[0013] In some implementations of the methods and apparatus described herein, the configuration is received from the network entity via radio resource control (RRC) signaling.

[0014] In some implementations of the methods and apparatus described herein, the identified polarization type is associated with a PRACH configuration index.

[0015] In some embodiments of the methods and apparatus described herein, the configuration indicates an association of a polarization type for each symbol within a RO that is frequency multiplexed in one PRACH duration instance.

[0016] In some implementations of the methods and apparatus described herein, the network entity is part of a non-terrestrial network (NTN).

[0017] In some implementations of the methods and apparatus described herein, the random access message includes a preamble root sequence having the polarization type embedded therein.

[0018] In some implementations of the methods and apparatus described herein, the configuration indicates an association of the identified polarization type with frequency resources configured for one RO.

[0019] In some implementations of the methods and apparatus described herein, the configuration indicates ROs scheduled on resources in the frequency domain or the time domain but associated with different polarization types.

[0020] Some implementations of the methods and apparatus described herein may further include a method performed by a UE, the method comprising: receiving a configuration indicating a polarization type associated with a PRACH from a network entity; and transmitting a random access message according to the polarization type associated with the PRACH.

[0021] In some implementations of the methods and apparatus described herein, the polarization type comprises left-hand circular polarization (LHCP) or right-hand circular polarization (RHCP).

[0022] In some embodiments of the methods and apparatus described herein, the configuration indicates an association of the polarization type with ROs multiplexed in the frequency domain within one PRACH duration.

[0023] In some embodiments of the methods and apparatus described herein, the configuration indicates an association of polarization type with RO at a plurality of PRACH duration instances.

[0024] In some embodiments of the methods and apparatus described herein, the configuration indicates an association of one polarization type with RO at a plurality of PRACH duration instances.

[0025] In some embodiments of the methods and apparatus described herein, the configuration indicates association of different polarization types with RO at a plurality of PRACH duration instances.

[0026] In some implementations of the methods and apparatus described herein, the configuration indicates an association of the polarization type with frequency resources configured for one RO.

[0027] In some implementations of the methods and apparatus described herein, the configuration indicates an indication of a RO scheduled on resources in the frequency domain or the time domain but associated with a polarization type.

[0028] Some implementations of the methods and apparatus described herein may further include a network entity comprising a processor and a memory coupled to the processor, the processor being configured to cause the network entity to transmit a configuration associating a polarization type with a RO to a UE, wherein the polarization type is associated with the RO in a frequency domain, a time domain, or a combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1

[0013] An example of a wireless communication system that supports associating a polarization type with a random access channel transmission in accordance with aspects of the present disclosure is illustrated.

[0030] Figure 2A to 2B An example of a diagram illustrating support for time-based association of RACH occasions (RO) with polarization types in accordance with aspects of the present disclosure.

[0031] Figure 3 An example of a diagram supporting mapping of one polarization type to RO in the time domain is illustrated according to aspects of the present disclosure.

[0032] Figure 4 An example of a diagram illustrating support for mapping of different polarization types to ROs in the time domain according to aspects of the present disclosure.

[0033] Figure 5 An example of a diagram illustrating support for mapping of different polarization types within one physical random access channel (PRACH) duration according to aspects of the present disclosure.

[0034] Figure 6 An example of a diagram supporting frequency-based association of RO to polarization type is illustrated in accordance with aspects of the present disclosure.

[0035] Figure 7 An example of a diagram illustrating a configuration supporting RO in the time-frequency-polarization domain according to aspects of the present disclosure.

[0036] Figure 8 Another example of a diagram illustrating a configuration supporting RO in the time-frequency-polarization domain according to aspects of the present disclosure.

[0037] Fig. 9 An example of a block diagram illustrating a UE that supports associating a polarization type with a random access channel transmission in accordance with aspects of the present disclosure.

[0038] Fig.10 A flow chart illustrating a method of supporting associating a polarization type with a random access channel transmission according to aspects of the present disclosure. DETAILED DESCRIPTION

[0039] In wireless communication systems, such as satellite-based networks or other non-terrestrial networks (NTNs), performance degradation may occur when polarization is unknown or not shared between network entities and user communication devices. For example, due to the low link budget issues of NTNs, polarization mismatches between devices can lead to frequent delays in the connection establishment process. In addition, polarization mismatches in certain messaging (e.g., Msg1 of the RACH procedure) can lead to reduced coverage during initial access procedures, potential beam failures, and other disadvantages.

[0040] To address such issues, the techniques described herein enable sharing of polarization between devices, such as by configuring a UE with polarization type information by a network entity. For example, the network entity may configure the UE to associate polarization with RACH resources, such as by explicitly or implicitly indicating to the UE the polarization type to be transmitted during Msg1 of the RACH procedure. The configuration may associate polarization types supported by NTN or other new radio (NR) networks, such as circular polarization types (e.g., left-hand circular polarization or LHCP, and right-hand circular polarization or RHCP) with RACH resources. In addition, the network entity may configure the UE to perform RO in the time-frequency domain and / or the polarization domain.

[0041] Therefore, sharing polarization information during the initial access procedure can enhance the coverage of the random access channel during uplink synchronization. In addition, using mutually orthogonal circular polarization types provides diversity for message delivery (e.g., when applied to the same message) to enhance coverage, and provides diversity for spatial multiplexing (e.g., when applied to different messages) to avoid collisions, thereby achieving an enhancement of the overall coverage of Msg1 of the RACH process and an enhancement of low coverage channels, as well as other benefits.

[0042] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure will be further illustrated and described with reference to apparatus diagrams and flow charts.

[0043] Figure 1An example of a wireless communication system 100 that supports associating a polarization type with a random access channel transmission according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0044] One or more network entities 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0045] The network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UEs 104 may support wireless communications of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, such as a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0046] One or more UEs 104 may be dispersed throughout a geographical area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be fixed in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0047] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated in FIG. UE 104 may be able to communicate with various types of devices, such as network entity 102, other UE 104, or network equipment (e.g., core network 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network equipment), such as Figure 1 Additionally or alternatively, UE 104 can support communications with other network entities 102 or UE 104 that can act as relays in wireless communication system 100.

[0048] The UE 104 may also be capable of supporting direct wireless communication with other UEs 104 via a communication link 114. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, the communication link 114 may be referred to as a side link. For example, the UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0049] The network entity 102 may support communication with the core network 106 or with another network entity 102 or both. For example, the network entity 102 may interface with the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2 or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0050] In some implementations, the network entity 102 may be configured as a disaggregated architecture, which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0051] A RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 102 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional division between CU, DU and RU may be flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU or RU. For example, a functional division of a protocol stack may be adopted between the CU and the DU so that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU may be connected to one or more DUs or RUs, and one or more DUs or RUs may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and each may be at least partially controlled by the CU 160.

[0053] In addition or alternatively, a functional division of the protocol stack may be employed between the DU and the RU, such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some embodiments, the functional division between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different ones of the CU, DU, or RU).

[0054] The CU may be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DU may be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul communication links or fronthaul communication links may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by the respective network entities 102 communicating via such communication links.

[0055] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)) and user plane entities that route packets to external networks or interconnect to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signal bearer, etc.) of one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0056] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session or the like) with the core network 106 via the network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0057] In the wireless communication system 100, the network entity 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more parameter sets.

[0058] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, a first parameter set (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0059] The time intervals of resources (e.g., communication resources) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some embodiments, each frame may include a plurality of subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0060] In addition or alternatively, the time intervals of resources (e.g., communication resources) may be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots of a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for the normal cyclic prefix and the extended cyclic prefix may depend on the parameter set. It should be understood that references to a first parameter set (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0061] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. By way of example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, the network entity 102 and the UE 104 may perform wireless communications over one or more of the operating frequency bands. In some embodiments, FR1 may be used by the network entity 102 and the UE 104 as well as other equipment or devices for cellular communication services (e.g., control information, data). In some implementations, FR2 may be used by the network entity 102 and the UE 104 and other equipment or devices for short-range, high data rate capabilities.

[0062] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with the following parameter sets: a first parameter set (e.g., μ=0) including a 15 kHz subcarrier spacing; a second parameter set (e.g., μ=1) including a 30 kHz subcarrier spacing; and a third parameter set (e.g., μ=2) including a 60 kHz subcarrier spacing. FR2 may be associated with one or more parameter sets (e.g., at least 2 parameter sets). For example, FR2 may be associated with the following parameter sets: a third parameter set (e.g., μ=2) including a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ=3) including a 120 kHz subcarrier spacing.

[0063] As described herein, in some embodiments, a network entity may configure a UE via implicit or explicit communication to associate a polarization type with a RACH transmission during an access procedure (e.g., an initial access procedure performed by the UE). For example, the configuration may associate an RO with a polarization type (e.g., LHCP, RHCP, or linear), where the association is in the frequency domain, the time domain (e.g., symbol-based within an RO or per RO duration, or slot-based), or a combination thereof.

[0064] For example, the configuration will be a RO time instance (PRACH duration ) is associated with one polarization type, where the UE transmits all ROs indicated by "msg1-FDM" at one PRACH duration instance. Figure 2A to 2BAn example of a diagram supporting time-based association of RO with polarization type is illustrated in accordance with aspects of the present disclosure.

[0065] As depicted, the configuration can be for different PRACH durations The same or different polarization types are associated, whereas the same polarization may be used for all ROs indicated by "msg1-FDM" at one PRACH duration instance. Figure 2A FIG2B illustrates an example of a diagram supporting time-based association of RACH occasions (RO) with polarization types according to aspects of the present disclosure.

[0066] Figure 2A 200 illustrates the association of one synchronization signal block (SSB) with one RO across the time domain 205 and the frequency domain 210. For example, a first polarization type x (e.g., RHCP) is associated with a first PRACH duration 215, and a second, different polarization type y (e.g., LHCP) is associated with a second PRACH duration 220. Figure 2B Figure 250 illustrates a similar association of one SSB with two ROs.

[0067] The network entity may communicate the association of polarization type with PRACH duration explicitly or implicitly. For example, the network entity may indicate a new parameter (e.g., "msg1-Pol") during RACH RRC signaling to indicate the polarization type associated with different time instances. In some cases, the network entity may add a parameter in the IE "RACH-ConfigGeneric" regardless of whether the random access procedure is contention-free or contention-based.

[0068] In some cases, the network entity may indicate parameters for contention-free and contention-based random access procedures through separate RRCIEs. For example, with respect to contention-based random access procedures, the parameters may be common to all UEs in a cell and may be included in the IE "RACH-ConfigCommon". For contention-free random access procedures, the parameters may be indicated in the IE "RACH-ConfigDedicated".

[0069] The following is an example of a RACH-ConfigGeneric information element modified with the new parameters:

[0070]

[0071] In some embodiments, the RO at multiple PRACH duration instances in a frame may use the same polarization type. For example, when the UE receives a RACH RRC configuration of TDD FR2, where msg1-Pol is LHCP and prach-ConfigurationIndex is 12, the UE searches for the corresponding RACH transmission symbol, preamble format, and RACH opportunity in the time domain by using the information in Table 6.3.3.2-4 of TS 38.211. Table 1 depicted below presents information similar to the information in Table 6.3.3.2-4:

[0072]

[0073] Table 1: Information of PRACH configuration index 12 & 74

[0074] The UE may calculate or otherwise determine the starting symbol of the RO in the time domain via the information in Table 1. For example, based on the information in Table 1, the PRACH duration is two time domain symbols, there are three ROs in one slot, and all ROs will adopt LHCP. Figure 3 An example of a diagram 300 is illustrated that supports mapping of one polarization type to RO in the time domain according to aspects of the present disclosure.

[0075] Diagram 300 includes a slot (e.g., slot 19) in a 60 kHz reference grid 305 and two slots (e.g., slot 38 and slot 39) in a 120 kHz reference grid 310. According to the information in Table 1, the two ROs 315 and 320 start with start symbol 7 and the PRACH duration is 2.

[0076] In some embodiments, for example, to enhance flexibility and coverage during access procedures, the configuration may indicate that different ROs at different PRACH duration instances are associated with different polarization types. For example, when the wireless communication system is an NTN, the cell size is very large and many users may perform RACH procedures at the same time. Therefore, using different polarizations at different time instances may reduce the probability of preamble collisions for different users.

[0077] The network entity may explicitly indicate the mapping of RO time instances to polarization types using RRC signaling. For example, the network entity may use a separate field in the RRC signaling to indicate whether a polarization is to be applied for all time instances, or whether different polarizations are to be applied for different time instances. When the RRC signaling does not contain this information, the UE may assume that the indicated polarization is valid for all time instances in the frame.

[0078] In some embodiments, alternate RO duration instances may employ different polarization types, wherein the configuration received by the UE may only indicate the polarization for the first time instance.

[0079] In some embodiments, groups of RO durations in consecutive time instances may use the same polarization type. The network entity may indicate this association to the UE using a value in RRC signaling that identifies how many consecutive time instances will use the same polarization type (e.g., a parameter "Pol duration" that configures the polarization duration). For example, a "Pol duration" of value 0 (or another reserved value) indicates that all RO durations use the same polarization, while a "Pol duration" of value 1 indicates that consecutive RO durations will use alternating polarization types, and so on.

[0080] Figure 4 An example of a diagram 400 illustrating support for mapping of different polarization types to RO in the time domain according to aspects of the present disclosure. As depicted, when the UE receives prach-ConfigurationIndex 12 and msg1-Pol is LHCP and Polduration is 1, 315 and 320 uses LHCP, while RO 410 adopts RHCP.

[0081] In some embodiments, the polarization duration and / or polarization type is fixed for the PRACH configuration index, fixed into the specification via a mapping table. Table 2 depicts this mapping table:

[0082]

[0083] Table 2: Polarization mapped to PRACH configuration index

[0084] As illustrated in Table 2, PRACH configuration index 12 employs LHCP for all PRACH durations, while PRACH configuration index 74 employs an alternate polarization type for each PRACH duration instance (where the first polarization of RO in slot 9 is RHCP).

[0085] In some embodiments, the configuration indicates an association of a polarization type with each of the symbols in the RO duration in the time domain, while the same polarization type or different polarization types are associated with symbols in one PRACH duration. The network entity may configure the association of polarization types with symbols in one PRACH duration via RRC parameters or via a mapping table. For example, the indication may be a default mode, where alternative symbols use different polarization types. As another example, the configured parameters may indicate a group of symbols using the same polarization type.

[0086] Figure 5An example of a diagram 500 is illustrated that supports mapping of different polarization types within one PRACH duration in accordance with aspects of the present disclosure. Diagram 500 depicts the use of different polarization types for each RO 510, 520 based on the parameters of the PRACH configuration index 74 defined in Table 1. As shown, one PRACH duration includes 6 OFDM symbols, with alternating or different polarization types (e.g., alternating between LHCP and RHCP) used for consecutive OFDM symbols within one PRACH duration.

[0087] In some embodiments, the association of polarization to RO is mapped by slot number and / or subframe number. Thus, a configuration may associate a polarization or polarization type with a slot number / subframe number (eg, all PRACH symbols in that slot or subframe number use one polarization type).

[0088] In some embodiments, the configuration does not explicitly indicate the association of polarization with PRACH duration instances. Instead, the UE may utilize the same polarization as indicated and / or detected for SSBs mapped to the RO. For example, referring back to Figure 2B When SSB 1 uses RHCP and there is no explicit indication of polarization during the RACH process, the UE also uses RHCP for PRACH duration time 2.

[0089] In some embodiments, the UE may embed information about the polarization association with the RO in the preamble root sequence and / or the preamble type / length. For example, a preamble format of a certain type may always indicate or be associated with a certain polarization (e.g., preamble format A1 uses LHCP, and preamble format A3 uses RHCP). Thus, in some cases, the preamble format may indicate the polarization type that the RO will adopt.

[0090] In some embodiments, the configuration may associate the polarization type with a frequency resource (e.g., a frequency resource configured for one RO). The UE may receive the configuration via RRC, as described herein. The configuration may associate the polarization type with one of the frequency RACH opportunities configured with "msg1-FDM".

[0091] Figure 6 An example of a diagram 600 illustrating frequency-based association of ROs with polarization types in accordance with aspects of the present disclosure is illustrated. Diagram 600, depicting time domain 605 and frequency domain 610, illustrates that a first RO 615 employs a first polarization type (e.g., "polarization type x") and a second RO 620 employs a second polarization type (e.g., "polarization type y").

[0092] In some embodiments, the network entity explicitly configures the UE with the polarization type via RRC parameters indicating the RO in the frequency domain and its associated polarization type.

[0093] In some embodiments, other RRC parameters (e.g., msg1-FDM and ssb-perRACH-OccasionAndCB-PreamblesPerSSB) may indicate the polarization type. Thus, when one SSB is FDMed with multiple ROs in the frequency domain, the polarization association with multiple FDMed ROs is defined and utilized by the RO. For example, if the number of SSBs is 4, msg1-FDM=4 and ssb-perRACH-OccasionAndCB-PreamblesPerSSB is half, then two SSBs are configured with 4 frequency ROs, with one SSB using two frequency ROs. Based on the defined association of polarization with frequency ROs, the frequency ROs employ the same or different polarizations for one SSB. According to diagram 600, RO#0 for SSB#0 employs LHCP (as indicated by RRC), and RO#1 for SSB#0 employs RHCP.

[0094] In some embodiments, the mapping table may illustrate the association of frequency RO with polarization type.Similar to Table 2, the mapping table may define the association of frequency RO with polarization type for PRACH configuration index.

[0095] In some embodiments, ROs may be defined in the polarization domain in addition to or separately from the time and / or frequency domains. Thus, ROs may utilize polarization as an additional orthogonal dimension. For example, during an access procedure, multiple ROs use the same time-frequency resources, but differ in the polarization domain. As described herein, a configuration may map an SSB index to a valid PRACH opportunity in the time and frequency resources. Similarly, a configuration may map ROs in the circular polarization domain.

[0096] In some embodiments, the configuration may utilize various mapping orders, such as (1) in increasing order of preamble code index within a single PRACH opportunity, (2) in increasing order of frequency resource index of PRACH opportunities using frequency multiplexing of a first polarization type, (3) in increasing order of a second polarization type by adopting the same time-frequency resources as in the previous type (for example, when there are more polarization types), (4) in increasing order of time resource index of PRACH opportunities time multiplexed within a PRACH slot and / or (5) in increasing order of index of PRACH slots.

[0097] The network entity may utilize a parameter to indicate that the RO is also polarization multiplexed (e.g., "msg1-PDM"), as shown in the following information element RACH-ConfigGeneric IE:

[0098]

[0099] Depending on the number of specified polarization types, different values ​​may be specified in the parameter field. For example, "msg1-PDM=1" may indicate that there is no polarization-multiplexed RO, while "msg1-PDM=2" may indicate that the PRACH opportunities are polarization-multiplexed by both LHCP and RHCP in the specified mapping order.

[0100] Figure 7 An example of a diagram 700 illustrating a configuration supporting RO in the time-frequency-polarization domain according to aspects of the present disclosure. Diagram 700 provides a 3D illustration of a PRACH opportunity configuration that maps RO 720 to all three domains (time 705, frequency 710, and polarization 715).

[0101] For example, the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB is read consistently with the parameter field "msg1-FDM", where one SSB shares the same time, frequency and polarization resources.

[0102] Figure 8 Another example of a diagram 800 illustrating a configuration supporting RO in the time-frequency-polarization domain according to aspects of the present disclosure. As depicted, when msg1-FDM=2, msg1-PDM=2, and ssb-perRACH-OccasionAndCB-PreamblesPerSSB is one quarter, a single SSB is associated with four ROs 810, where the UE utilizes two first frequency resources on a single time resource instance with one polarization. The UE then utilizes the next polarization using the same two time and frequency resources (but different polarizations), and then moves to the next RO time instance 810, as shown.

[0103] Of course, in various embodiments, the UE may follow the Figure 7 Or a mapping order different from that depicted in 8. For example, the UE may swap steps 2 and 3, and first increment the preamble index within a single PRACH opportunity, then increment in the polarization domain, and finally increment in the frequency domain, as well as many different sequences of steps.

[0104] Thus, as described herein, a UE (e.g., UE 104) may perform a random access procedure that employs a configured polarization type to enhance coverage during the access procedure and / or prevent or mitigate collisions between other UEs 104 (e.g., within a cell of an NTN), among other benefits. As described herein, a UE may configure a RO in the time domain and / or frequency domain and associate it with an SSB and polarization. Furthermore, a UE may associate PRACH resources in the polarization domain, and in some cases, perform multiple PRACH preamble transmissions in the polarization domain to enhance coverage during the access procedure, among other benefits.

[0105] Fig. 9 An example of a block diagram 900 illustrating a device 902 that supports associating a polarization type with a random access channel transmission in accordance with aspects of the present disclosure. The device 902 may be an example of a UE 104 as described herein. The device 902 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 902 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 904, a memory 906, a transceiver 908, and an I / O controller 910. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0106] The processor 904, memory 906, transceiver 908, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 904, memory 906, transceiver 908, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0107] In some implementations, the processor 904, memory 906, transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some implementations, the processor 904 and the memory 906 coupled to the processor 904 may be configured to perform one or more of the functions described herein (e.g., execution of instructions stored in the memory 906 by the processor 904).

[0108] For example, processor 904 can support wireless communication at device 902 according to examples as disclosed herein. Processor 904 can be configured to or otherwise support means for: receiving a configuration indicating a polarization type associated with a PRACH from a network entity; and transmitting a random access message according to the polarization type associated with the PRACH.

[0109] The processor 904 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some embodiments, the processor 904 may be configured to operate a memory array using a memory controller. In some other embodiments, the memory controller may be integrated into the processor 904. The processor 904 may be configured to execute computer-readable instructions stored in a memory (e.g., 906) to cause the device 902 to perform various functions of the present disclosure.

[0110] The memory 906 may include random access memory (RAM) and read-only memory (ROM). The memory 906 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 904, cause the device 902 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some embodiments, the code may not be directly executable by the processor 904, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some embodiments, the memory 906 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0111] I / O controller 910 can manage input and output signals of device 902. I / O controller 910 can also manage peripheral devices that are not integrated into device 2402. In some embodiments, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some embodiments, I / O controller 910 can utilize an operating system, such as or another known operating system. In some embodiments, I / O controller 910 may be implemented as part of a processor (e.g., processor M06). In some embodiments, a user may interact with device 902 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0112] In some implementations, the device 902 may include a single antenna 912. However, in some other implementations, the device 902 may have more than one antenna 912 (i.e., multiple antennas) including multiple antenna panels or antenna arrays, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously. The transceiver 908 may communicate bidirectionally via one or more antennas 912, wired or wireless links as described herein. For example, the transceiver 908 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 908 may also include a modem to modulate packets, provide the modulated packets to one or more antennas 912 for transmission, and demodulate packets received from the one or more antennas 912.

[0113] Fig.10 Flowchart illustrating a method 1000 for supporting associating a polarization type with a random access channel transmission according to aspects of the present disclosure. The operations of the method 1000 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1000 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 9 The described UE 104 performs. In some embodiments, the device may execute an instruction set to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0114] At 1010, the method may include receiving a configuration indicating a polarization type associated with a PRACH from a network entity. The operations of 1010 may be performed according to examples as described herein. In some embodiments, aspects of the operations of 1010 may be performed as described in reference to Figure 1 The described device performs.

[0115] At 1020, the method may include transmitting a random access message according to a polarization type associated with the PRACH. The operations of 1020 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1020 may be performed as described in reference to Figure 1 The described device performs.

[0116] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0117] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0118] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features that implement the functions may also be physically located at various locations, including being distributed so that portions of the functions are implemented at different physical locations.

[0119] Computer-readable media include non-transitory computer storage media and communication media, including any media that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available media that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage, or any other non-transitory media that can be used to carry or store desired program code means in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.

[0120] Any connection may properly be referred to as a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, or DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable media. Disk and optical disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks usually reproduce data magnetically, while optical discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0121] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of..." or "one or more of..." or "one or both of...") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on." In addition, as used herein, including in the claims, a "set" may include one or more elements.

[0122] When referring to a network entity, the terms "transmit," "receive," or "communicate" may refer to any part of a network entity of a RAN (e.g., base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0123] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some examples, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0124] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment UE, comprising: processor; and a memory coupled to the processor, the processor being configured to cause the UE to: receiving, from a network entity, a configuration indicating a polarization type associated with a physical random access channel PRACH; and A random access message is transmitted according to the polarization type associated with the PRACH.

2. The UE of claim 1, wherein transmitting the random access message comprises performing a RACH occasion (RO) of a Msg1 transmission using the polarization type.

3. The UE according to claim 1, wherein the configuration indicates an association of the polarization type with ROs multiplexed in the frequency domain within one PRACH duration.

4. The UE of claim 1, wherein the configuration indicates an association of polarization type with RO at a plurality of PRACH duration instances.

5. The UE of claim 1, wherein the configuration indicates an association of one polarization type with RO at a plurality of PRACH duration instances.

6. The UE of claim 1, wherein the configuration indicates association of different polarization types with RO at multiple PRACH duration instances.

7. The UE of claim 1, wherein the configuration is received from the network entity via Radio Resource Control (RRC) signaling.

8. The UE of claim 1, wherein the identified polarization type is associated with a PRACH configuration index.

9. The UE of claim 1, wherein the configuration indicates an association of a polarization type for each symbol within a RO that is frequency multiplexed in one PRACH duration instance.

10. The UE of claim 1, wherein the network entity is part of a non-terrestrial network (NTN).

11. The UE according to claim 1, wherein the random access message includes a preamble root sequence having the polarization type embedded therein.

12. The UE of claim 1, wherein the configuration indicates an association of the identified polarization type with frequency resources configured for one RO.

13. The UE of claim 1, wherein the configuration indicates ROs scheduled on resources in the frequency domain or the time domain but associated with different polarization types.

14. A method performed by a user equipment UE, the method comprising: receiving, from a network entity, a configuration indicating a polarization type associated with a physical random access channel (PRACH); and A random access message is transmitted according to the polarization type associated with the PRACH.

15. The method of claim 14, wherein the polarization type comprises left-hand circular polarization (LHCP) or right-hand circular polarization (RHCP).

16. The method of claim 14, wherein the configuration indicates an association of the polarization type with RACH occasions (RO) multiplexed in the frequency domain within one PRACH duration.

17. The method of claim 14, wherein the configuration indicates: Association of polarization type with RO at multiple PRACH duration instances; Association of one polarization type with RO at multiple PRACH duration instances; Association of different polarization types with RO at multiple PRACH duration instances; an association of the polarization type with frequency resources configured for one RO; or An indication of a RO scheduled on resources in the frequency domain or time domain but associated with a polarization type.

18. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving, from a network entity, a configuration indicating a polarization type associated with a physical random access channel PRACH; and A random access message is transmitted according to the polarization type associated with the PRACH.

19. The processor of claim 18, wherein the configuration is received from the network entity via Radio Resource Control (RRC) signaling.

20. A network entity, comprising: processor; and a memory coupled to the processor, the processor being configured to cause the network entity to: A configuration associating a polarization type with a random access channel (RACH) opportunity (RO) is transmitted to a user equipment (UE), wherein the polarization type is associated with the RO in the frequency domain, the time domain, or a combination thereof.

Images