Polarization-based repetition in initial access procedure

By sharing polarization information in wireless communication systems and adopting polarization-based repetition in the initial access program, the problems of connection delay and coverage reduction caused by polarization mismatch in non-terrestrial networks are solved, and a wider access coverage is achieved.

CN119744511APending Publication Date: 2025-04-01LENOVO (SINGAPORE) PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380058233.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-08-10
Filing Date
2023-08-10
Publication Date
2025-04-01

AI Technical Summary

Technical Problem

In wireless communication systems, especially in non-terrestrial networks, polarization is unknown or not shared, which can lead to frequent delays and reduced coverage during connection establishment.

Method used

By sharing polarization information between user equipment (UE) and network entity, the UE is configured to use polarization-based repetitions during the initial access program, using the same time and frequency resources for transmission.

Benefits of technology

This approach enhances the coverage of the random access channel and increases the coverage of the access program without the need for additional time or frequency resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119744511A_ABST
    Figure CN119744511A_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure relate to methods, devices, and systems that support associating a polarization type with a random access channel transmission. For example, when a network entity configures a UE to associate a polarization type with a random access channel (RACH) resource, the UE shares polarization information with the network entity. The UE may employ or utilize polarization-based repetition for Msg1, Msg3, and / or MsgA transmissions during an initial access procedure. In doing so, the UE may utilize the same time and frequency resources when performing polarization-based repetition, thereby enhancing coverage of the access procedure.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 396,889, filed on August 10, 2022, entitled POLARIZATION-BASED REPETITIONS IN INITIAL ACCESS PROCEDURES, the entire contents of which are incorporated herein 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 (such as a base station) may support wireless communication of one or more user communication devices, which may be further referred to as a 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 the 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 (e.g., 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, typically repeatedly sending a connection request or 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. For example, when a network entity configures a UE to associate a polarization type with a RACH resource, the UE shares polarization information with the network entity. The UE may employ or utilize polarization-based repetitions for Msg1, Msg3 and / or MsgA transmissions during an initial access procedure. In doing so, the UE may utilize the same time and frequency resources when performing polarization-based repetitions, thereby enhancing coverage of the access procedure.

[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 repetition of uplink physical channel transmissions during an initial access procedure from a network entity, and to transmit the repeated uplink physical channel based on the indicated polarization type.

[0008] In some embodiments of the methods and apparatus described herein, the configuration indicates a polarization type for performing repetition for Msg1, Msg3, MsgA, or a combination thereof.

[0009] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel includes transmitting multiple uplink physical channels multiple times while applying one or more polarization types.

[0010] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes associating the same frequency and time resources with different polarization types.

[0011] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes configuring multiple repeated physical random access channel (PRACH) preamble code transmissions in the polarization domain for one or more detected signal synchronization blocks (SSBs).

[0012] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes configuring a PRACH transmission for multiple RACH occasions (ROs).

[0013] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes performing Msg3 repetition in the polarization domain.

[0014] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes configuring a plurality of MsgA repetitions in the polarization domain.

[0015] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes transmitting a MsgA preamble and a MsgA PUSCH transmission in parallel simultaneously using two different polarization types.

[0016] In some implementations of the methods and apparatus described herein, a MsgA PUSCH opportunity may overlap in time and frequency with any MsgA PRACH opportunity, but will be different in the polarization domain.

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

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

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

[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 from a network entity indicating a polarization type associated with repetition of uplink physical channel transmissions during an initial access procedure; and transmitting the repeated uplink physical channel based on the indicated polarization type.

[0021] In some embodiments of the methods and apparatus described herein, the configuration indicates a polarization type for performing repetition for Msg1, Msg3, MsgA, or a combination thereof.

[0022] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel includes transmitting multiple uplink physical channels multiple times while applying one or more polarization types.

[0023] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes associating the same frequency and time resources with different polarization types.

[0024] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes configuring multiple repeated physical random access channel (PRACH) preamble code transmissions in the polarization domain for one or more detected signal synchronization blocks (SSBs).

[0025] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes configuring a PRACH transmission for multiple RACH occasions (ROs).

[0026] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes performing Msg3 repetition in the polarization domain.

[0027] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes configuring a plurality of MsgA repetitions in the polarization domain.

[0028] In some implementations of the methods and apparatus described herein, transmitting the repeated uplink physical channel based on the indicated polarization type includes transmitting a MsgA preamble and a MsgA PUSCH transmission in parallel simultaneously using two different polarization types.

[0029] In some implementations of the methods and apparatus described herein, a MsgA PUSCH opportunity may overlap in time and frequency with any MsgA PRACH opportunity, but will be different in the polarization domain.

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

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

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

[0033] 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 configured to cause the network entity to transmit to a UE a configuration indicating a polarization type associated with a repetition of an uplink physical channel transmission during an initial access procedure performed by the UE.

[0034] In some implementations of the methods and apparatus described herein, the configuration is transmitted via RRC signaling. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 An example of a wireless communication system supporting polarization-based repetition in an initial access procedure according to aspects of the present disclosure is described.

[0036] Figure 2 An example of a diagram illustrating support for sharing multiple RACH opportunities (ROs) in the polarization domain for one synchronization signal block (SSB) according to aspects of the present disclosure.

[0037] Figure 3 An example of a diagram illustrating support for triggering Msg3 repetition in the polarization domain according to aspects of the present disclosure.

[0038] Figure 4 An example of a block diagram illustrating a UE supporting polarization-based repetition in an initial access procedure according to aspects of the present disclosure.

[0039] Figure 5 A flow chart illustrating a method of supporting polarization-based repetition in an initial access procedure according to aspects of the present disclosure. DETAILED DESCRIPTION

[0040] 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, polarization mismatches between devices may lead to frequent delays in the connection establishment process due to the low link budget problem of NTNs. In addition, polarization mismatches in specific messaging (e.g., Msg1 or Msg3 of a RACH procedure) may lead to reduced coverage during initial access procedures, potential beam failures, and other disadvantages.

[0041] To address such issues, the techniques described herein enable sharing of polarization between devices, such as by configuring the UE with polarization type information by a network entity. For example, the network entity may configure the UE to employ or utilize polarization-based repetitions for Msg1, Msg3, and / or MsgA transmissions during an initial access procedure. In doing so, the UE may utilize the same time and frequency resources when performing polarization-based repetitions because the repetitions are orthogonal in their polarizations.

[0042] Therefore, sharing polarization information during the initial access procedure can enhance the coverage of the random access channel during uplink synchronization. In addition, among other benefits, the use of the polarization domain orthogonal to the time domain and / or frequency domain also enhances the coverage during the access procedure without utilizing additional time or frequency resources.

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

[0044] Figure 1 An example of a wireless communication system 100 that supports polarization-based repetition in an initial access procedure according to aspects of the present disclosure is described. 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 LTE-Advanced (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 after 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).

[0045] One or more network entities 102 may be dispersed throughout a geographic region 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 communications (e.g., receive signaling, transmit signaling) via a Uu interface.

[0046] The network entity 102 may provide a geographic coverage area 112, wherein 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 UE 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 the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0047] One or more UE 104 may be dispersed throughout the geographic 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, as well as 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, as well as 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.

[0048] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1 1. Some examples of UE 104 are illustrated in FIG. UE 104 may be capable of communicating with various types of devices, such as network entity 102, other UEs 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, which can function as relays in wireless communication system 100.

[0049] The UE 104 may also be capable of supporting wireless communications directly with other UEs 104 via a communication link 114. For example, the UE 104 may support wireless communications directly 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 wireless communications directly with another UE 104 via a PC5 interface.

[0050] 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 embodiments, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other embodiments, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some embodiments, 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).

[0051] In some implementations, the network entity 102 may be configured in a decomposed architecture that may be configured to utilize a protocol stack that is physically or logically distributed between 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 the following: 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.

[0052] 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 embodiments, 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)).

[0053] The functional division between the CU, DU and RU may be flexible and may support different functions 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 the 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)) functions 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) functions and signaling, and each may be at least partially controlled by the CU 160.

[0054] Additionally 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 implementations, 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).

[0055] 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 a respective network entity 102 communicating via such communication links.

[0056] The core network 106 may support user authentication, access authorization, tracking, connection, 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 or interconnections 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 of one or more UEs 104 served by one or more network entities 102 associated with the core network 106, such as mobility, authentication, and bearer management (e.g., data bearer, signal bearer, etc.).

[0057] 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).

[0058] 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 communications). 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 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.

[0059] 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.

[0060] 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, such as a duration of 10 milliseconds (ms). In some embodiments, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, such as a duration of 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0061] Additionally 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., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. For a normal cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame may depend on a 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.

[0062] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various categories, bands, 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 the frequency range designations 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 implementations, the network entity 102 and the UE 104 may perform wireless communications on the one or more operating frequency bands. In some implementations, FR1 may be used by the network entity 102 and the UE 104 as well as other equipment or devices for cellular communication traffic (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.

[0063] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with 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 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.

[0064] As described herein, in some embodiments, a network entity may configure a UE via implicit or explicit communication to utilize polarization-based repetitions during Msg1, Msg3, and / or MsgA transmissions. In some embodiments, a UE (e.g., UE 104) performs multiple / repeated PRACH preamble transmissions in the polarization domain for one or more detected SSBs. For both contention-based and contention-free random channel access methods, the number or amount of repetitions in the polarization domain may be explicitly configured by RRC via RACH RRC information elements.

[0065] In some cases, the number of repetitions is based on two circular polarization types (e.g., left-hand circular polarization or LHCP and right-hand circular polarization or RHCP). For example, the RACH information element may include a parameter field "PolRep" with values ​​{0,1} to indicate a default repetition method based on LHCP and RHCP. Thus, a parameter field false indicates no repetition in the polarization domain, and a field true indicates that the UE will employ repetition in the polarization domain by transmitting the PRACH preamble in both LHCP and RHCP.

[0066] In some cases, the number of polarization types to be used for repetition may be greater than two and may be predefined in the specification (e.g., via a mapping table defining an index corresponding to the polarization types to be used for repetition). For example, the mapping table may define "0" to represent LHCP and linear, "1" to represent RHCP and LHCP, and "2" to represent RHCP, LHCP, and linear. As described herein, when the UE performs repetition, RRC signaling may also indicate the number of polarization types (e.g., 1, 2, or 3).

[0067] In some embodiments, the UE may perform RO configuration in the polarization domain, where multiple ROs are configured for SSB using time, frequency, and polarization resources. Figure 2An example of a diagram 200 illustrating support for sharing multiple RACH opportunities (RO) in the polarization domain for one synchronization signal block (SSB) according to aspects of the present disclosure. Diagram 200 illustrates using resources in the time domain 205, frequency domain 210, and polarization domain 215

[0068] As depicted, if the higher layer parameters are msg1-FDM=2, msg1-FDM=2, and ssb-perRACH-OccasionAndCB-PreamblesPerSSB=1 / 4, then a single SSB is associated with 4 ROs 220. The UE may perform repetition as follows: The UE utilizes the first two frequency resources with one polarization on a single resource instance in the time domain 205, and then moves to the next polarization using the same two time and frequency resources. Then, the UE moves along the time domain 205 to the next time RO instance.

[0069] In some embodiments, when there is no RO configuration in the polarization domain, the repetition in the polarization domain includes repeating the configured RO for the SSB candidate in the polarization domain using the time-frequency resources.

[0070] In some embodiments, the UE is configured to perform PRACH repetitions for a single detected SSB in the polarization domain using the same PRACH preamble (e.g., to exploit polarization diversity). In some cases, the UE is configured with one RO for an SSB candidate and is configured (e.g., by default) to perform circular polarization-based repetitions using a polarization diversity approach. After detecting an SSB, the UE may first transmit a preamble on the configured RO with one circular polarization type (e.g., LHCP), and then transmit the same preamble on the same time-frequency resources with a second circular polarization type (e.g., RHCP).

[0071] In some cases, the UE is configured with multiple beams and / or multiple ROs for SSB candidates and is configured to perform polarization diversity based repetition. Based on such configuration, the UE may perform multiple PRACH preamble transmissions in the time-frequency domain and the polarization domain. For example, the UE may repeat the preamble for each configured RO of the SSB in the polarization domain (e.g., repeat the same preamble for ROs with multiple different configured polarizations).

[0072] In some embodiments, the UE is configured to perform PRACH repetitions for a single detected SSB in the polarization domain using different PRACH preambles (e.g., exhibiting polarization multiplexing). Utilizing polarization multiplexing can reduce the probability of preamble collisions between UEs in cells, such as in an NTN, which can have a large cell size with a large number of attempted initial accesses to the network.

[0073] In some cases, the UE is configured with one RO for SSB candidates and is configured (e.g., as a default configuration) to perform circular polarization-based repetition using polarization multiplexing. After detecting an SSB, the UE first transmits a preamble on the configured RO with one circular polarization type (e.g., LHCP), and then transmits a second preamble on the same time-frequency resources using a second circular polarization type (e.g., RHCP).

[0074] In some cases, the configuration instructs the UE to randomly select preambles from a set of preambles for use with different polarizations of one RO. In other cases, each polarization repetition is configured with or associated with a set of preambles (e.g., preambles 0 to 31 are associated with LHCP, and preambles 32 to 63 are associated with RHCP).

[0075] In some cases, the UE is configured with multiple beams and / or multiple ROs for SSB candidates and is configured to perform polarization multiplexing based repetitions. For example, for each of the beams / ROs, the UE may employ a different preamble for repetitions in the polarization domain.

[0076] In some embodiments, when multiple beams and / or multiple ROs are configured for SSB, the configuration may indicate a combination or hybrid of polarization diversity based repetition and spatial multiplexing based repetition. For example, for SSB candidates, some beams / ROs may use polarization diversity based repetition, while some other beams / ROs may use polarization multiplexing based repetition.

[0077] In some embodiments, the UE is configured to transmit PRACH preambles associated with multiple SSBs while multiplexing multiple SSBs in the polarization domain. For example, the UE detects multiple SSBs and transmits PRACH preambles associated with the best detected SSB at different polarizations at the same time. In some cases, the number of polarization domain transmissions is based on the UE polarization capability and the number of best detected SSBs.

[0078] In some cases, a separate RO is defined for each SSB in the polarization domain, there is only one valid RO configured for one SSB in the polarization domain, or there is only one valid RO and the UE transmits preambles for multiple SSBs in the polarization domain. The configuration may include a list of valid preambles associated with all SSBs to be used for the second polarization type, so the network is aware of the second SSB.

[0079] For example, if the UE has the capability to transmit LHCP and RHCP polarizations, the UE identifies the best two SSBs (e.g., the SSB with the highest reference signal received power (RSRP) value within a predefined threshold) and searches for a valid RO for the first SSB. The UE may then transmit a PRACH preamble associated with the first SSB on a corresponding valid RO using a first polarization type (e.g., LHCP), and then search for a PRACH preamble associated with the second SSB on the same RO using a second polarization type (e.g., RHCP).

[0080] In some embodiments, the network does not explicitly indicate the use of polarization-based repetition. Instead, the UE may perform repetition based on the RSRP of the detected SSB. For example, if the RSRP level of the SSB is below a certain threshold, the UE will adopt polarization-based repetition for the RO of the SSB, where the repetition type (e.g., diversity or multiplexing) and the polarization type (e.g., LHCP, RHCP, linear, etc.) are separately configured, predefined, or selected autonomously by the UE. The threshold of the RSRP level may also be predefined, configured through RRC signaling, or selected autonomously by the UE, and may depend on various factors, such as cell layout, frequency reuse facts, and / or the location of the UE (e.g., for contention-free random access procedures).

[0081] In some embodiments, in addition to time domain repetition, the UE also performs or applies Msg3 repetition in the polarization domain, where multiple polarization-based repetitions may utilize the same time and frequency resources. The configuration of polarization-based repetitions may depend on the polarization capability of the UE.

[0082] In some cases, the network is aware of the polarization capabilities of the UE (e.g., what polarization types the UE can adopt) and configures polarization-based repetitions based on the indicated UE capabilities. The UE may indicate the polarization capabilities to the network explicitly or implicitly during or within a Msg1 transmission of an initial access procedure.

[0083] For example, the UE may be configured to use multiple polarization-based PRACH repetitions (e.g., configured with LHCP, RHCP, and linear polarization types). However, the UE may only have LHCP and RHCP capabilities, and the PRACH repetitions are applied based on their capabilities. In response to the received PRACH repetitions, the network determines the UE capabilities of only LHCP and RHCP, and then configures polarization-based Msg3 repetitions in the random access response (RAR) message using only LHCP and RHCP.

[0084] In some cases, the UE may configure polarization-based Msg3 repetitions without receiving network configuration, where repetitions on multiple polarizations are configured with a specified pattern. The UE applies repetitions based on its known capabilities, utilizing all or one polarization-based repetition in the specified pattern.

[0085] In some embodiments, the configuration of Msg3 repetitions in the time domain is indicated by a higher layer parameter "numberOfMsg3Repetitions", which is configured / associated with the polarization type to avoid polarization loss. Msg3 repetitions may also be configured by RRC parameters or by a field in the downlink control information (DCI), where the same or different polarization types may be configured with the repetitions.

[0086] For example, if numberOfMsg3Repetitions=4 and the polarization-related parameters are the same, then all configured time domain repetitions utilize the same polarization type. In some cases, the configuration may define different polarization pattern combinations associated with each repetition number, and the indexes for these patterns may be configured via DCI or RRC (e.g., in a physical uplink shared channel (PUSCH) scheduled by an RAR UL grant). The following table (Table 1) illustrates different polarization mapping combinations for Msg3 repetition number 4.

[0087]

[0088]

[0089] Table 1

[0090] In some cases, all configured Msg3s reuse the same polarization type configured for the PRACH preamble, where one polarization type is configured.

[0091] In some embodiments, the number of Msg3 repetitions can be increased by associating two circular polarization types with each of the repetitions. For example, by using two orthogonal polarizations LHCP and RHCP for each repetition (and without using additional time and frequency resources), Msg3 repetitions can be increased from 16 to 32. This configuration can utilize resources in an efficient manner while increasing the repetition factor that is typically useful in NTNs due to higher path losses in the network.

[0092] In some cases, the number of Msg3 repetitions can be increased by predefining each repetition for the polarization type. For example, repetitions 1 to 16 are associated with LHCP, and repetitions 17 to 32 are associated with RHCP. Given the association, the repetitions will follow a similar sequence. According to an example, when configured with a repetition of 16, all repetitions will use LHCP, however, when configured with a repetition of 20, the first 4 repetitions will use LHCP and RHCP, and the remaining repetitions will use LHCP.

[0093] In some cases, each odd and even repetition number may be associated with a polarization type (e.g., odd numbers are associated with LHCP, and even numbers are associated with RHCP), where even repetition numbers utilize one time resource and are repeated using both polarizations on the same time resource. For example, an even repetition number of 8 indicates 4 time domain occurrences (resources) by repeating Msg 3 using both circular polarization types at each occurrence. An odd repetition number such as 7 would indicate 4 time domain occurrences (resources), but Msg 3 is repeated using both circular polarization types at the first 3 occurrences and only with LHCP at the last occurrence.

[0094] In some embodiments, the network may use separate signaling to indicate whether the number of configured Msg3 repetitions includes or does not include polarization-based repetitions. The signaling may include a RAR UL grant or Msg1 configuration using parameters in DCI or RRC. In some cases, the configuration may include a new higher layer parameter (e.g., "Polbasedrepetitions") as well as a higher layer parameter numberOfMsg3Repetitions to indicate whether the time-based repetitions will include additional polarization-based repetitions.

[0095] In some embodiments, the UE performs or applies polarization-based repetition for Msg3 by default, such as when the UE is configured to perform multiple / repeated PRACH preamble transmissions for one or more detected SSBs. The UE may adopt the same polarization mode indicated for the Msg3 time domain repetition as for the PRACH preamble transmission. For example, when the repeated PRACH preamble uses LHCP and RHCP, the Msg3 time domain repetition also adopts polarization-based repetition, such as LHCP and RHCP-based repetition.

[0096] In some embodiments, the configuration may include one higher layer parameter (eg, only one parameter) to indicate that polarization based repetition is utilized for both Msg1 and Msg3 transmissions. Similarly, the configuration may include only one higher layer parameter to indicate the polarization type to be used for repetition of Msg1 and Msg3.

[0097] In some embodiments, when the SSB or Msg2 RSRP drops below a configured RSRP threshold (e.g., when RSRP < RSRP threshold), the UE activates or requests polarization-based Msg3 repetition. In such a case, the UE repeats Msg3 via the configured polarization type for repetition using the polarization type configured for PRACH repetition or specifically configured for Msg3 repetition. When there is no polarization type configured for repetition, the UE may use its polarization type capabilities to repeat Msg3.

[0098] In some cases, the parameter field “rsrp-ThresholdSSB” in the RACH configuration IE can be used for polarization-based repetition. When the synchronization signal RSRP of the SSB (SS-RSRP) is much higher than the rsrp-ThresholdSSB value, the UE may not apply repetition to Msg3. However, when the value approaches the threshold, the UE will apply polarization-based repetition.

[0099] In some embodiments, the configuration may include or introduce a new RSRP threshold field for a four-step RACH procedure that defines the use / activation / request for polarization-based repetition. Figure 3 Illustrate an example of FIG. 300 that supports triggering Msg3 repetition in the polarization domain according to aspects of the present disclosure. As depicted, the threshold of the field “rsrp-ThresholdPol” 305 is set lower than the threshold of the field “rsrp-ThresholdSSB” 310. When the value drops below the field “rsrp-ThresholdPol” 305 and is higher than the field “rsrp-ThresholdSSB” 310, the UE triggers Msg3 repetition in the polarization domain. In some cases, the new field value is set higher than the value of the field “rsrp-ThresholdSSB” 310 to trigger Msg3 repetition.

[0100] In some embodiments, the UE may be configured to perform multiple / repeated MsgA preamble transmissions on one or more ROs for one or more detected SSBs by employing multiple polarizations. However, in such a case, the UE may not be configured with a single or multiple resources to perform MsgA PUSCH repetition in the polarization domain.

[0101] The UE may receive configuration via RRC signaling, such as a configuration indicating the polarization type to be used for MsgA transmission. The UE may apply the indicated polarization type to both MsgA PRACH preamble transmission and MsgA PUSCH transmission. In some cases, the configuration may indicate multiple polarization types instead of indicating a single polarization type. The UE may use the configured time and frequency resources to determine MsgA to be repeated in the polarization domain.

[0102] For example, the indication of repeating MsgA PRACH and MsgAPUSCH can be configured by a field alone (e.g., indicating that repetition in the polarization domain will or will not be performed), and multiple polarization types can indicate that the UE can select a single polarization (from multiple polarizations) for MsgA transmission based on the UE's capabilities. When the UE has more than one polarization type capability (from the configured polarization type), the UE can use the same time and frequency resources to repeat MsgA with polarization.

[0103] In some embodiments, the UE transmits the MsgA preamble and MsgAPUSCH transmissions in parallel using two different polarization types at the same time (e.g., performing MsgA preamble transmissions with LHCP and MsgA PUSCH transmissions with RHCP). Thus, the PUSCH opportunity may overlap with any PRACH opportunity in time and frequency, but will be different in the polarization domain.

[0104] In some embodiments, MsgAPUSCH opportunities are configured in the polarization domain, where a parameter may be used to indicate the number of PUSCH opportunities available in the polarization domain. For example, for each configured time instance, the number of PUSCH opportunities available in the frequency domain configured by the nrMsgA-PO-FDM parameter is repeated in the polarization domain.

[0105] Thus, as described herein, a UE (e.g., UE 104) may perform a random access procedure with polarization-based repetition for Msg1, Msg3, and / or MsgA transmissions.

[0106] Figure 4 An example of a block diagram 400 illustrating a device 402 that supports polarization-based repetition in an initial access procedure according to aspects of the present disclosure. The device 402 may be an example of a UE 104 as described herein. The device 402 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 402 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 404, a memory 406, a transceiver 408, and an I / O controller 410. 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).

[0107] The processor 404, memory 406, transceiver 408, 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 404, memory 406, transceiver 408, or various combinations thereof, or components thereof may support a method for performing one or more of the operations described herein.

[0108] In some implementations, the processor 404, memory 406, transceiver 408, 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, configured as or otherwise supporting means for performing the functions described in the present disclosure. In some implementations, the processor 404 and the memory 406 coupled to the memory 404 may be configured to perform one or more of the functions described herein (e.g., execution of instructions stored in the memory 406 by the processor 404).

[0109] For example, the processor 404 may support wireless communications at the device 402 according to examples as disclosed herein. The processor 404 may be configured to or otherwise support means for receiving a configuration indicating a polarization type associated with a physical random access channel (PRACH) from a network entity and performing PRACH repetition in a polarization domain associated with the indicated polarization type.

[0110] Furthermore, processor 400 may be configured to or otherwise support means for receiving a configuration from a network entity indicating a polarization type associated with repetition of uplink physical channel transmissions during an initial access procedure and transmitting a repeated uplink physical channel based on the indicated polarization type.

[0111] The processor 404 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 implementations, the processor 404 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 404. The processor 404 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 406) to cause the device 402 to perform various functions of the present disclosure.

[0112] The memory 406 may include random access memory (RAM) and read-only memory (ROM). The memory 406 may store computer-readable, computer-executable code including instructions that, when executed by the processor 404, cause the device 402 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 404, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some embodiments, the memory 406 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.

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

[0114] In some implementations, the device 402 may include a single antenna 412. However, in some other implementations, the device 402 may have more than one antenna 412 (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 408 may communicate bidirectionally via one or more antennas 412, wired or wireless links as described herein. For example, the transceiver 408 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 408 may also include a modem to modulate packets, provide the modulated packets to one or more antennas 412 for transmission, and demodulate packets received from the one or more antennas 412.

[0115] Figure 5 Flowchart illustrating a method 500 for supporting polarization-based repetition in an initial access procedure according to aspects of the present disclosure. The operations of the method 500 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 500 may be implemented by a device or component thereof as described in reference to Figures 1 to 4 The described UE 104 may be used to perform. In some embodiments, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0116] At 510, the method may include receiving, from a network entity, a configuration indicating a polarization type associated with repetitions of uplink physical channel transmissions during an initial access procedure. Operation 510 may be performed according to examples as described herein. In some embodiments, aspects of operation 510 may be implemented as described in reference to Figure 1 The described device is implemented.

[0117] At 520, the method may include transmitting the repeated uplink physical channel based on the indicated polarization type. Operation 520 may be performed according to examples as described herein. In some embodiments, aspects of operation 520 may be performed as described in reference to Figure 1 The described device is implemented.

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

[0119] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using 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. A 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).

[0120] 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 on or transmitted by a computer-readable medium as one or more instructions or codes. 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, hardwiring, or a combination of any of these. Features implementing the functions may also be physically located at different locations, including being distributed so that portions of the functions are implemented at different physical locations.

[0121] Computer-readable media include both non-transitory computer storage media and communication media, including any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media can 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 can 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 the desired program code components 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.

[0122] 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, DSL, or wireless technology (such as infrared, radio and microwave) is included in the definition of computer-readable media. As used herein, magnetic disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where magnetic disks usually reproduce data magnetically, while optical disks reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0123] 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" or "one or more" or "one or two") represents an inclusive list, so that, for example, a list of at least one of A, B, or C represents 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, including in the claims, the phrase "based on" should not be interpreted as a reference 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.

[0124] The terms "transmit," "receive," or "communicate," when referring to a network entity, 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).

[0125] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "as an example, instance, or illustration" and is not "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.

[0126] The description herein is provided to enable one skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled 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 in 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 repetitions of uplink physical channel transmissions during an initial access procedure; and The repeated uplink physical channel is transmitted based on the indicated polarization type. 2 . The UE according to claim 1 , wherein the configuration indicates a polarization type for performing repetition for Msg1, Msg3, MsgA, or a combination thereof.

3. The UE of claim 1, wherein transmitting the repeated uplink physical channel comprises transmitting a plurality of uplink physical channels a plurality of times while applying one or more polarization types.

4. The UE of claim 1 , wherein transmitting the repeated uplink physical channel based on the indicated polarization type comprises associating same frequency and time resources with different polarization types.

5. The UE of claim 1 , wherein transmitting the repeated uplink physical channel based on the indicated polarization type comprises configuring multiple repeated physical random access channel (PRACH) preamble transmissions for one or more detected signal synchronization blocks (SSBs) in the polarization domain.

6. The UE of claim 1, wherein transmitting the repeated uplink physical channel based on the indicated polarization type comprises configuring PRACH transmissions for multiple RACH occasions (ROs).

7. The UE of claim 1, wherein transmitting the repeated uplink physical channel based on the indicated polarization type comprises performing Msg3 repetition in a polarization domain.

8. The UE of claim 1, wherein transmitting the repeated uplink physical channel based on the indicated polarization type comprises configuring a plurality of MsgA repetitions in a polarization domain.

9. The UE of claim 1, wherein transmitting the repeated uplink physical channel based on the indicated polarization type comprises transmitting a MsgA preamble and a MsgAPUSCH transmission in parallel using two different polarization types simultaneously.

10. The UE of claim 1, wherein a MsgA PUSCH opportunity may overlap with any MsgAPRACH opportunity in time and frequency, but will be different in the polarization domain. 11 . The UE according to claim 1 , wherein the polarization type comprises left-hand circular polarization (LHCP) or right-hand circular polarization (RHCP).

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

13. The UE of claim 1, wherein the configuration is received from the network entity of a non-terrestrial network (NTN).

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 repetitions of uplink physical channel transmissions during an initial access procedure; and The repeated uplink physical channel is transmitted based on the indicated polarization type.

15. The method of claim 14, wherein the configuration indicates a polarization type for performing repetition for Msg1, Msg3, MsgA, or a combination thereof.

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

17. The method of claim 14, wherein the configuration is received from the network entity via Radio Resource Control (RRC) signaling.

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 repetitions of uplink physical channel transmissions during an initial access procedure; and The repeated uplink physical channel is transmitted based on the indicated polarization type.

19. A network entity, comprising: processor; and a memory coupled to the processor, the processor being configured to cause the network entity to: A configuration indicative of a polarization type associated with repetitions of uplink physical channel transmissions during an initial access procedure performed by a user equipment UE is transmitted to the UE.

20. The network entity of claim 19, wherein the configuration is transmitted via Radio Resource Control (RRC) signaling.