RACH type selection and different RACH parameter sets

Abstract

The UE can receive configuration from the base station for multiple parameter sets, each parameter set including one or more parameters for RACH messages, and each parameter set associated with one of TDM, FDM, or SDM. The UE can determine the transport type of the RACH message corresponding to one or more of TDM, FDM, or SDM, and send the RACH message to the base station based on at least one parameter set and the determined transport type of the RACH message. In various aspects, the configuration received by the UE can be a configuration for sending RACH messages based on a RACH determination protocol. The UE can send the RACH message to the base station based on the received configuration associated with the RACH determination protocol and at least one transport type of the determined RACH message.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of U.S. Patent Application No. 17 / 115,691, filed December 8, 2020, entitled “RACH TYPE SELECTION AND DIFFERENT SETS OF RACH PARAMETERS,” which is a continuation of U.S. Nonprovisional Application Serial No. 17 / 102,261, filed November 23, 2020, entitled “RACH TYPE SELECTION AND DIFFERENT SETS OF RACH PARAMETERS,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] In summary, this disclosure relates to communication systems, and more specifically, to the selection of random access channel (RACH) type and different sets of RACH parameters. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects, and is neither intended to identify key or important elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may include a memory and at least one processor coupled to the memory and configured to: receive configuration for a plurality of parameter sets, each parameter set including one or more parameters for a Random Access Channel (RACH) message and associated with one of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or Space Division Multiplexing (SDM); determine a transmission type for the RACH message corresponding to one or more of TDM, FDM, or SDM; and transmit the RACH message based on at least one parameter set from the plurality of parameter sets, the at least one parameter set being associated with the determined transmission type of the RACH message.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may include a memory and at least one processor coupled to the memory and configured to: transmit configuration for a plurality of parameter sets, each parameter set including one or more parameters for a RACH message and associated with one of TDM, FDM, or SDM; and receive a RACH message based on at least one parameter set from the plurality of parameter sets, the at least one parameter set being associated with a transmission type of the RACH message corresponding to one or more of TDM, FDM, or SDM.

[0009] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may include a memory and at least one processor coupled to the memory and configured to: receive a configuration for transmitting a RACH message, the configuration being associated with a plurality of transport types including TDM, FDM, and SDM; determine at least one transport type among the plurality of transport types for the RACH message, the at least one transport type corresponding to one or more of TDM, FDM, or SDM; and transmit the RACH message based on the received configuration for the RACH message and the determined at least one transport type of the RACH message.

[0010] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may include a memory and at least one processor coupled to the memory and configured to: transmit a configuration for a RACH message, the configuration being associated with a plurality of transport types including TDM, FDM, and SDM; and receive the RACH message based on the transmitted configuration for the RACH message and at least one of the plurality of transport types for the RACH message, the at least one transport type corresponding to one or more of TDM, FDM, or SDM.

[0011] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and particularly pointed out in the claims. Certain illustrative features of one or more aspects are set forth in detail in the following description and drawings. However, these features indicate only a few of the various ways in which the principles of each aspect may be employed, and this specification is intended to include all such aspects and their equivalents. Attached Figure Description

[0012] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.

[0013] Figure 2A This is a diagram illustrating an example of the first frame of various aspects according to this disclosure.

[0014] Figure 2B This is a diagram illustrating an example of a downlink (DL) channel within a subframe according to various aspects of this disclosure.

[0015] Figure 2C This is a diagram illustrating an example of the second frame according to various aspects of this disclosure.

[0016] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0017] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0018] Figure 4 This is a call flow diagram illustrating the communication between the UE and the base station.

[0019] Figure 5 This is a call flow diagram illustrating the communication between the UE and the base station.

[0020] Figures 6A-6C A diagram is shown for full-duplex (FD) operation for the UE and the base station.

[0021] Figure 7This is a flowchart of the UE's wireless communication method.

[0022] Figure 8 This is a flowchart of the wireless communication method of a base station.

[0023] Figure 9 This is a flowchart of the UE's wireless communication method.

[0024] Figure 10 This is a flowchart of the wireless communication method of a base station.

[0025] Figure 11 This is a diagram illustrating an example of the hardware implementation used for the example device.

[0026] Figure 12 This is a diagram illustrating an example of the hardware implementation used for the example device.

[0027] Figure 13 This is a diagram illustrating an example of the hardware implementation used for the example device.

[0028] Figure 14 This is a diagram illustrating an example of the hardware implementation used for the example device. Detailed Implementation

[0029] The detailed description below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing only the configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in the form of block diagrams in order to avoid obscuring such concepts.

[0030] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by way of various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0031] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0032] Accordingly, in one or more example embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium accessible by a computer. By way of example, and not limitation, such a computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code accessible by a computer in the form of instructions or data structures.

[0033] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0034] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or core network 190) via third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0035] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB), which can provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use spectrum allocated in carrier aggregation for a total of up to Y x MHz (x component carriers) for transmission in each direction, with a bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0036] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0037] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0038] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as the unlicensed spectrum used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0039] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "sub-6GHz" band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although FR2 differs from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), it is often (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0040] In light of the foregoing, unless otherwise specifically stated, it should be understood that the terms "sub-6GHz" and the like (if used herein) can broadly refer to frequencies that are less than 6GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0041] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0042] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0043] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for MBMS transmissions to content providers, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to areas of a Multicast-Broadcast Single Frequency Network (MBSFN) that broadcasts specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0044] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that processes signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS streaming and session management. All user Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) services, and / or other IP services.

[0045] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides access to EPC 160 or core network 190 for UE 104. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UE 104 devices may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.

[0046] Refer again Figure 1In some aspects, UE 104 may include a parameter-based transmission component 198a configured to: receive configuration for a plurality of parameter sets, each parameter set including one or more parameters for a Random Access Channel (RACH) message and associated with one of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or Space Division Multiplexing (SDM); determine a transmission type for the RACH message corresponding to one or more of TDM, FDM, or SDM; and transmit the RACH message based on at least one parameter set from the plurality of parameter sets, the at least one parameter set being associated with the determined transmission type of the RACH message. In some aspects, base station 180 may include a parameter configuration component 199a configured to: transmit configuration for a plurality of parameter sets, each parameter set including one or more parameters for a RACH message and associated with one of TDM, FDM, or SDM; and receive the RACH message based on at least one parameter set from the plurality of parameter sets, the at least one parameter set being associated with a transmission type for the RACH message corresponding to one or more of TDM, FDM, or SDM. In some aspects, UE 104 may include a RACH protocol determination component 198b configured to: receive a configuration for transmitting a RACH message, the configuration being associated with multiple transport types including TDM, FDM, and SDM; determine at least one transport type among the multiple transport types for the RACH message, the at least one transport type corresponding to one or more of TDM, FDM, or SDM; and transmit the RACH message based on the received configuration for the RACH message and the determined at least one transport type of the RACH message. In some aspects, base station 180 may include a RACH protocol configuration component 199b configured to: transmit a configuration for the RACH message, the configuration being associated with multiple transport types including TDM, FDM, and SDM; and receive the RACH message based on the transmitted configuration for the RACH message and at least one transport type among the multiple transport types of the RACH message, the at least one transport type corresponding to one or more of TDM, FDM, or SDM. Although the following description may focus on 5G NR, the concepts described herein can be applied to other similar areas such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0047] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2DFigure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL), or Time Division Duplex (TDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL). In the process of... Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0048] Other wireless communication technologies may have different frame structures or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may contain 7, 4, or 2 symbols. Each time slot may contain 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may contain 14 symbols, while for time slot configuration 1, each time slot may contain 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread Spectrum OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe can be based on the time slot configuration and the numbering scheme. For slot configuration 0, different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2... μEach time slot / subframe. Subcarrier spacing and symbol length / duration are functions of the digital scheme. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 4. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15kHz, and digital scheme μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 2A-2D Examples are provided for slot configuration 0 (14 symbols per slot) and digital scheme μ=2 (4 slots per subframe). The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, one or more distinct bandwidth portions (BWPs) of frequency division multiplexing can exist (see [link to relevant documentation]). Figure 2B Each BWP can have a specific digital scheme.

[0049] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)), which is extended by 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0050] like Figure 2A As shown, some REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS). RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0051] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs within an OFDM symbol of an RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring on a CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can span the channel bandwidth at larger and / or lower frequencies. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can logically be grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0052] like Figure 2C As shown, some REs in the REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols before the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0053] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / NACK (NACK)) feedback. The PUCCH carries data and may also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0054] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0055] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine decoding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0056] At UE 350, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0057] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0058] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection and measurement reporting; PDCP layer functions associated with: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0059] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate decoding and modulation scheme, as well as to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0060] UL transmission at base station 310 is handled in a manner similar to that described for the receiver functions integrated at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0061] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0062] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to combine Figure 1 198a-198b are used to implement various aspects.

[0063] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to combine Figure 1 199a-199b are used to implement various aspects.

[0064] Wireless communication systems can be configured to share available system resources and provide various telecommunications services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple users (such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and TD-SCDMA systems). In many cases, common protocols that facilitate communication with wireless devices are adopted across various telecommunications standards. For example, communication methods associated with eMBB, mMTC, and URLLC can be incorporated into the 5G NR telecommunications standard, while others can be incorporated into the 4G LTE standard. As mobile broadband technology is part of continuous evolution, further improvements to mobile broadband remain useful for the continued development of such technologies.

[0065] Figure 4This is a call flow diagram 400 illustrating communication between UE 402 and base station 404. At 406a, base station 404 may send a RACH parameter set configuration 406b to UE 402. Parameter set configuration 406b may include all different parameter sets for TDM / FDM / SDM; or parameter set configuration 406b may include at least one common parameter set for TDM / FDM / SDM and different subsets of parameters for each of TDM / FDM / SDM. In various aspects, the parameter set configuration may include three parameter sets for a 2-step RACH procedure and three additional parameter sets for a 4-step RACH procedure. Base station 404 may send the RACH parameter set configuration to UE 402 via RRC signaling in connected mode; or base station 404 may send the RACH parameter set configuration to UE 402 via RMSI in broadcast mode.

[0066] At 408, UE 408 can determine the RACH transmission type for the RACH message. The RACH transmission type can correspond to one or more of TDM, FDM, or SDM. At 410, UE 402 can send the RACH message to base station 404 based on the parameter set and the determined RACH transmission type.

[0067] Figure 5 This is a call flow diagram 500 illustrating communication between UE 502 and base station 504. At 506, the base station may send a RACH message configuration to UE 502. In various aspects, the RACH message configuration may indicate FD activation / deactivation based on DL transmission priority. At 508a, UE 502 may determine the RACH transmission type (e.g., corresponding to any of TDM / FDM / SDM). At 508a, the determination made by UE 502 may be based on determination protocol 508b. For example, a first protocol in determination protocol 508b may correspond to the RACH transmission type determined by the UE. A second protocol in determination protocol 508b may correspond to a determination of the RACH transmission type based on Reference Signal Received Power (RSRP) or Signal-to-Interference-plus-Noise Ratio (SINR). A third protocol in determination protocol 508b may correspond to a priority-based determination of the RACH transmission type. A fourth protocol in determination protocol 508b may correspond to a destination-based determination of the RACH transmission type. The fifth protocol in protocol 508b can correspond to the determination of the RACH transport type based on multiple attempts.

[0068] At 510, UE 502 can activate / deactivate the FD transmission mode. For example, FD RACH can be deactivated to increase the likelihood of UE 502 successfully receiving high-priority DL transmissions from base station 504 without self-interference. Therefore, at 512, UE 502 can switch the transmission type from FDM or SDM (e.g., which may be associated with FD transmission mode) to TDM (e.g., which may be associated with HD transmission mode). At 510, UE 502 can activate the FD transmission mode in association with low-priority DL transmissions from base station 504. At 514, UE 502 can send a RACH message to base station 504 based on the received configuration and the determined transmission type.

[0069] Figures 6A-6C Figures 600-620 illustrate FD operation for UEs 604b-604c and base stations 602a-602b. FD operation can be based on simultaneous UL and DL transmissions at UEs 604b-604c and / or base stations 602a-602b. In some configurations, simultaneous UL and DL transmissions can occur in frequency range 2 (FR2). However, in other configurations, simultaneous UL and DL transmissions can occur at lower frequencies (such as frequency range 1 (FR1) or another lower frequency), or simultaneously UL and DL transmissions can occur at higher frequencies (such as frequency range 4 (FR4)). Either or both of UEs 604a-604c and base stations 602a-602c can be configured with FD capability. For example, in Figure 600, base station 602a can transmit to UE1 604a and receive from UE2 606 simultaneously; or, in Figure 620, UE 604c can receive from a first base station 602c / first transmit / receive point (TRP1) and transmit to a second base station 608 / second transmit / receive point (TRP2), where TRP1 and TRP2 can be associated with the same serving cell. In another example associated with Figure 610, UE 604b and base station 602b / TRP can transmit and receive from each other simultaneously.

[0070] UL signals can be associated with a first panel of UE 604b-604c and base stations 602a-602b, and DL signals can be associated with a second panel of UE 604b-604c and base stations 602a-602b. For example, UE 604b-604c may include two separate panels, such as a panel for UL transmission on the first side of UE 604b-604c and a panel for DL ​​transmission on the second side of UE 604b-604c. Each panel may have an independent baseband digital radio frequency (RF) chain for forming a beam at the panel's time. Based on the independent baseband digital RF chain, the separate panels can form separate beams for simultaneous transmission and reception at UE 604b-604c. In various aspects, whether the UE or base station can support simultaneous transmission and reception via separate beams from two different panels may depend on beam separation and / or other parameters. If UEs 604b-604c are transmitting to base stations 602b / 608 via the transmission panel, but the transmitted signal strength causes leakage to the receiving panel, self-interference from UL to DL may occur at UEs 604b-604c. If the self-interference is too large, DL transmission failure may occur, and UEs 604b-604c may not be able to perform FD operation correctly. Self-interference caused by leakage from DL to UL may similarly occur at base station 602a, which may cause UL transmission failure at base station 602a. Self-interference can be sufficiently reduced to perform FD operation by implementing beam splitting and / or beam selection techniques for one or more beam pair candidates associated with reduced self-interference (e.g., based on measurements).

[0071] FD operation can provide latency reduction because UEs 604b-604c and base stations 602a-602b may not have to wait for specific UL and DL time slots / symbols to perform the corresponding transmission. For example, UEs 604b-604c can receive DL signals in FD time slots / symbols, or base stations 602a-602b can receive UL signals in FD time slots / symbols, thus providing latency reduction. Therefore, since transmission and reception can occur at the same time and / or in the same frequency band, spectral efficiency per cell and per UE can be improved. For subband FD transmission, the simultaneously transmitted UL and DL signals can correspond to different frequency bands (e.g., separated by guard bands), partially overlapping frequency bands, or completely overlapping frequency bands. FD operation can be performed with reduced self-interference / leakage, thus providing more efficient use of resources and higher data rates.

[0072] The RACH process can be performed in conjunction with FD mode (e.g., FDM-based and / or SDM-based) or half-duplex (HD) mode (e.g., TDM-based). In an HD RACH-based configuration, RACH message transmissions (such as message (Msg)1 (e.g., preamble) or Msg 3 (e.g., UL payload) in a four-step RACH process or Msg A (e.g., preamble and UL payload) in a two-step RACH process can be time-independent and do not overlap with DL transmissions, where the DL transmissions can be SSB, PDCCH, PDSCH, or CSI-RS. RACH message receptions (such as Msg2 (e.g., control information) or Msg 4 (e.g., DL payload) in a four-step RACH process or Msg A in a two-step RACH process) can also be performed in conjunction with DL transmissions. B (e.g., control information and DL payload) can be time-independent and not overlap with UL transmissions, where UL transmissions can be PUCCH, PUSCH, or SRS. For example, the RACH process can be TDM-based based on HD mode, where a RACH preamble or another RACH message can be sent at once, so that the RACH process does not overlap with DL transmissions such as SSB, PDCCH, PDSCH, and CSI-RS in time. Therefore, when a RACH preamble is sent to the base station, no transmission needs to be received in the DL, because the transmission can be per-direction and per-time.

[0073] A two-step RACH process can be based on the preamble and payload portions of Msg A or the control and payload portions of Msg B. Msg A can be associated with the UL signal, while Msg B can be associated with the DL signal. For Msg A, the preamble portion can correspond to Msg 1, and the payload portion can correspond to Msg 3. For Msg B, the control portion can correspond to Msg 2, and the payload portion can correspond to Msg 4. That is, Msg 1 and Msg 3 can be associated with the UL signal, and Msg 2 and Msg 4 can be associated with the DL signal. A four-step RACH process can be based on a combination of Msg 1, Msg 2, Msg 3, and Msg 4. Although some aspects described herein for illustrative purposes can be associated with Msg 1, such aspects can also be associated with Msg 3, alternatively or otherwise. Furthermore, aspects described herein can be associated with Msg 2 and / or Msg 4. For example, Msg 2 and / or Msg 4 may overlap temporally with UL signals (such as PUCCH, PUSCH, SRS, etc.) and may be FDM or SDM. Although other aspects described herein for illustrative purposes may be associated with Msg A, such aspects may also be associated with Msg B, either alternatively or otherwise. For example, Msg B may overlap temporally with UL signals (such as PUCCH, PUSCH, SRS, etc.) and may be FDM or SDM.

[0074] For FD mode, RACH messages can overlap temporally with DL transmissions (such as SSB, PDCCH, PDSCH, CSI-RS, etc.) to improve system efficiency and reduce latency. For example, an SSB associated with a fixed resource allocation can overlap temporally with a pre-allocation used for RACH messages. FD RACH types can include FDM-based RACH, SDM-based RACH, or a combination of FDM-based and SDM-based RACH. FDM-based RACH (which can be associated with UL transmissions) can share the same time resources as DL transmissions but can correspond to different frequency resources (e.g., separated by guard bands) or different frequency resources than DL transmissions. For example, DL transmissions can utilize bands 1, 2, and 3, and UL transmissions used for RACH can utilize bands 2, 3, and 4. SDM-based RACH (which can also be associated with UL transmissions) can share the same time and frequency resources as DL transmissions. Therefore, UL and DL transmissions can overlap temporally and frequency-wise, and can be separated based on spatial dimensions. This separation can be based on the physical separation and / or orientation of the UL and DL beams. Since DL transmissions can be received by UE 604b-604c and / or sent by base stations 602a-602b simultaneously with RACH messages, both FDM-based RACH and SDM-based RACH can be associated with FD operations.

[0075] For the RACH procedure, different RACH parameters can be configured via RRC signaling from base stations 602a-602c to UEs 604a-604c. Different RACH parameters may include one or more of the following: prach-ConfigurationIndex, preambleReceivedTargetPower, rsrp-ThresholdSSB, rsrp-ThresholdCSI-RS, rsrp-ThresholdSSB-SUL, candidateBeamRSList, recoverySearchSpaceId, powerRampingStep, powerRampingStepHighPriority, scalingFactorBI, ra-PreambleIndex, ra-ssb-OccasionMaskIndex, ra-OccasionList, ra-PreambleStartIndex, preambleTransMax, ssb-perRACH-OccasionAndCB-PreamblesPerSSB, and other parameters.

[0076] The `prach-ConfigurationIndex` parameter corresponds to the index of the available physical RACH (PRACH) timing for transmitting the random access preamble. The `preambleReceivedTargetPower` parameter corresponds to the initial random access preamble power. The `rsrp-ThresholdSSB` parameter corresponds to the RSRP threshold used to select the SSB. If a random access procedure is initiated for Beam Failure Recovery (BFR), the `rsrp-ThresholdSSB` parameter can be used to select an SSB from the `candidateBeamRSList`, which corresponds to the `rsrp-ThresholdSSB` of the BeamFailureRecoveryConfig information element (IE). That is, the SSB received by UE 604b-604c can be used to transmit the RACH preamble. The `rsrp-ThresholdCSI-RS` parameter corresponds to the RSRP threshold used to select the CSI-RS. If a random access procedure is initiated for a BFR, the rsrp-ThresholdCSI-RS parameter can be equal to the rsrp-ThresholdSSB parameter of the BeamFailureRecoveryConfig IE. The rsrp-ThresholdSSB-SUL parameter can correspond to the RSRP threshold used to select the Normal Uplink (NUL) carrier or the Supplemental Uplink (SUL) carrier. The candidateBeamRSList parameter can correspond to a list of reference signals (e.g., CSI-RS and / or SSB) used to identify candidate beams for recovery and associated random access parameters. The recoverySearchSpaceId parameter can correspond to the search space identifier used to monitor the response to a Beam Failure Recovery (BFR) request. The powerRampingStep parameter can correspond to the power ramp factor. The powerRampingStepHighPriority parameter can correspond to the power ramp factor in an instance of a prioritized random access procedure. The scalingFactorBI parameter can correspond to the scaling factor of a prioritized random access procedure. The ra-PreambleIndex parameter can correspond to the random access preamble. The `ra-ssb-OccasionMaskIndex` parameter can define one or more PRACH opportunities associated with the SSB, where the MAC can send a random access preamble. The `ra-OccasionList` parameter can define one or more PRACH opportunities associated with the CSI-RS, where the MAC can send a random access preamble.The `ra-PreambleStartIndex` parameter can correspond to the starting index of one or more random access preambles used for on-demand System Information (SI) requests. The `preambleTransMax` parameter can correspond to the maximum number of random access preambles transmitted. The `ssb-perRACH-OccasionAndCB-PreamblesPerSSB` parameter can define the number of SSBs mapped to each PRACH timing and the number of contention-based random access preambles mapped to each SSB. One or more of the above parameters and / or other parameters can be signaled from base stations 602a-602c to UEs 604a-604c.

[0077] In the first aspect, base stations 602a-602c can configure different RACH parameter sets (e.g., three different parameter sets instead of one) for UEs 604a-604c based on RRC signaling. UEs 604a-604c can use some or all of the parameters for RACH transmission in HD mode and some or all of the parameters for RACH transmission in FD mode, and these parameters can be different. The parameter sets can be different for two-step RACH procedures and four-step RACH procedures. For example, three parameter sets can correspond to a two-step RACH procedure, and three parameter sets can correspond to a four-step RACH procedure, which can correspond to a total of six parameter sets. The three parameter sets can include parameters for each of the TDM-based RACH procedure (e.g., HD RACH), the FDM-based RACH procedure (e.g., FD RACH), and the SDM-based RACH procedure (e.g., FD RACH). The parameters configured for each parameter set in different parameter sets may include different values ​​for initial random access preamble power, power ramp process, maximum number of preamble transmissions, RSRP SSB threshold, RSRP CSI-RS threshold, etc.

[0078] For the HD RACH procedure of UE 606, the RACH preamble can be transmitted by UE 606 at full power. However, for the FD RACH procedure of UE 604b-604c (where UE 604b-604c is operating in FD mode), the transmission power at the UE transmitter can be reduced to limit self-interference to the UE receiver. In another example, to receive the RACH preamble at base stations 602a-602b (where the base stations are operating in FD mode), UE 604b / 606 can increase the transmission power to enhance the UL transmission being received by base stations 602a-602b, because the receiving panel of base stations 602a-602b can receive a certain level of self-interference from the transmitting panel of base stations 602a-602b via simultaneous DL transmission. Therefore, the transmission power used for the RACH preamble may differ for different configurations of UE 604a-604c and base stations 602a-602c. Therefore, in addition to the transmission type of RACH, the parameter set can also depend on whether the UE or the base station, or both, are operating in FD mode. In this case, for example, more than three parameter sets can correspond to a two-step RACH procedure, and more than three parameter sets can correspond to a four-step RACH procedure.

[0079] The power ramping process may differ for different transmissions, as it can correspond to an increase in power during RACH preamble transmission. The maximum number of preamble transmissions / retransmissions can be based on whether UE 604a-604c and / or base station 602a-602c are operating in HD mode or FD mode. For HD RACH procedures, UE 606 can be configured to perform a lower number of retransmissions, and for FD RACH procedures, UE 604b-604c can be configured to perform a higher number of retransmissions.

[0080] In the second aspect, base stations 602a-602c can be configured with a common RACH parameter set (where the same parameters are used for different RACH transmission types (e.g., TDM, FDM, SDM)) and different subsets of RACH parameters (e.g., three different subsets) (where the parameter set used for each subset of the different subsets is different (e.g., three parameter sets for two-step RACH and three sets for four-step RACH)). For example, each two-step RACH process can be associated with the common RACH parameter set and three different subsets of RACH parameters, and each four-step RACH process can be associated with an additional common RACH parameter set and three different subsets of RACH parameters.

[0081] At least one parameter in each parameter set of different parameter sets may differ from parameters in other parameter sets of different parameter sets. In the example where UE 604b-604c is operating in FD mode, low transmission power can be used to transmit the RACH preamble associated with the SDM-based RACH procedure. Since UE 604b-604c is operating in FD mode and can receive DL reception from base station 602b-602c, using high transmission power for the RACH preamble may generate too much self-interference at UE 604b-604c, making it impossible to successfully receive DL reception. Therefore, base station 602b-602c may configure UE 604b-604c based on low transmission power. For the FDM-based RACH procedure, the preamble transmission power can be higher than that used in the SDM-based RACH procedure because the FDM-based RACH procedure may include frequency separation (e.g., based on a guard band located between the UL and DL bands). For example, self-interference caused by a RACH procedure via FDM can be less than that caused by a RACH procedure via SDM, thus allowing UE 604b-604c to use higher transmission power for the RACH preamble. For a RACH procedure via TDM, the preamble transmission power can be further increased (e.g., increased to the maximum / full power of UE 606) because self-interference may not occur since UE 606 is operating in HD mode. When operating in HD mode, interference to UE 606 can be limited to background noise and / or other external forms of interference.

[0082] In the example where base stations 602a-602b are operating in FD mode, UE 604b / 606 may use high transmission power in association with the SDM-based RACH procedure for base stations 602a-602b to receive the RACH preamble from UE 604b / 606. Since base stations 602a-602b are operating in FD mode and may send DL transmissions to UE 604a-604b while base stations 602a-602b are receiving the RACH preamble, the UL signal strength corresponding to the RACH preamble may need to overcome leakage caused by the DL transmission, which may cause self-interference with the reception of the RACH preamble. Therefore, the transmission power of the RACH preamble can correspond to high transmission power. For the FDM-based RACH procedure, the preamble transmission power can be lower than the transmission used in association with the SDM-based RACH procedure because the FDM-based RACH procedure may include frequency separation (e.g., based on a guard band located between the UL and DL bands). Frequency separation can induce lower self-interference at base stations 602a-602b, allowing RACH preambles to be transmitted at lower power levels. For TDM-based RACH procedures, UE 604c can further reduce preamble transmission power because self-interference may not occur at base station 608, which is operating in HD mode. Therefore, the configuration of different RACH parameter sets can depend on the type of RACH transmission being implemented (e.g., TDM, FDM, SDM) and whether UE 604a-604c and / or base stations 602a-602c are operating in FD mode.

[0083] While the above examples illustrate different configurations for RACH preamble transmission power, other parameters for different RACH parameters can be adjusted based on similar considerations. For instance, each parameter set could include different power ramp parameters, or different rsrp-ThresholdSSB / CSI-RS parameters, where different thresholds can be used to receive SSB or CSI-RS depending on whether UE 604a-604c and / or base station 602a-602c are operating in FD or HD mode. Instead of configuring UE 604a-604c based on the rsrp-ThresholdSSB / CSI-RS parameters, this configuration could be based on new sinr-ThresholdSSB / CSI-RS parameters or other parameters. In FD mode, the SSB power can be measured against self-interference to determine if the beam can be used for FD RACH or if the beam might fail due to self-interference. SINR can be a parameter used to measure SSB / CSI-RS instead of performing the measurement based on RSRP.

[0084] After determining the different RACH parameter sets, base stations 602a-602c can signal to UEs 604a-604c the configuration for the different RACH parameter sets. This signaling can be based on RRC messages used for connection operation modes. For example, RRC signaling can be used to send three different RACH parameter configuration sets to UEs 604a-604c. This signaling can also be based on Residual Minimum System Information (RMSI) used for broadcast operation modes.

[0085] UE 604b-604c / 606 can determine the type of RACH transmission (e.g., TDM, FDM, SDM) in association with HD mode and FD mode. In a first aspect, UE 604b-604c / 606 can independently determine the type of RACH transmission. For example, UE 604b-604c / 606 can determine to use the latest RACH timing to transmit the RACH preamble, which can be TDM, FDM, or SDM.

[0086] In the second aspect, UEs 604b-604c / 606 can determine the type of RACH transmission based on SINR or RSRP based on SSB or CSI-RS. Base stations 602a-602c can configure different SSB or CSI-RS thresholds for each RACH type based on different parameters used for different RACH types. For example, UE 606 with a low measured DL RSRP can utilize TDM-based HD RACH. UE 604b-604c with a high measured DL RSRP can utilize FDM-based FD RACH, or for even higher DL RSRPs, UE 604b-604c can utilize SDM-based FD RACH. More specifically, power-constrained UEs such as those using URLLC (e.g., those that may be farther from base stations 602a-602c) can utilize HD RACH via TDM to increase the likelihood of UL transmissions being received by base stations 602a-602c, while non-power-constrained UEs (e.g., those that may be closer to base stations 602a-602c) can utilize FD RACH via FDM or SDM.

[0087] In the third aspect, UEs 604b-604c / 606 can determine the type of RACH transmission based on a priority indication. For example, after UEs 604b-604c / 606 connect to the network, base stations 602a-602c can include a priority field in the RACH configuration. The priority field can indicate the service type of the RACH transmission, which can correspond to the BFR and / or timing advance (TA) of the RACH transmission. A higher-priority UE 606 can utilize HD RACH transmission over TDM to provide base station 602a with an increased probability of successful transmission. A lower-priority UE 604b-604c can utilize FD RACH over FDM or FDRACH over SDM. Therefore, for non-initial access (e.g., where UEs 604b-604c / 606 are operating in connected mode), UEs 604b-604c / 606 can determine the type of RACH based on the indication of the PHY priority field from base stations 602a-602c.

[0088] For initial access, UEs 604b-604b / 606 can determine the priority of RACH transmission based on the priority of the subscript service class of UE 604b-604b / 606. This priority can be determined via the UE profile (e.g., included on the Subscriber Identity Module (SIM) card). The determination of the subscript service class priority can be based on a predefined protocol. Higher-priority UE 606 can utilize HD RACH transmission over TDM to increase the likelihood of a successful initial access transmission to base station 602a. Lower-priority UEs 604b-604c can utilize FD RACH over FDM or FD RACH over SDM.

[0089] In the fourth aspect, UEs 604b-604b / 606 can determine the priority of RACH transmissions based on the purpose of the RACH procedure. For example, if the purpose of the RACH transmission is for initial access that can have a higher priority, UE 606 can utilize HD RACH via TDM to increase the likelihood of a successful connection with the cell. If the purpose of the RACH transmission is for BFR or a new TA request, UEs 604b-604c can utilize FD RACH via SDM or FD RACH via FDM, since BFR and TA can have a lower priority compared to initial access. The determination of the priority of the purpose of the RACH transmission can be based on a predefined protocol or indicated by base stations 602a-602c via RMSI or SIB messages sent to UEs 604b-604b / 606.

[0090] In the fifth aspect, UEs 604b-604b / 606 can determine the priority of RACH transmissions based on the number of RACH transmission retransmission attempts. For example, the initial RACH transmission can be based on SDM-based FD RACH or FDM-based FD RACH. If, after N retransmissions, base station 602b / 608 still fails to successfully receive the RACH, UEs 604b-604c can switch the type of RACH transmission from SDM / FDM-based FD RACH to TDM-based HD RACH. The determination of the RACH transmission type can be based on a predefined protocol or indicated by base station 602b-602c via RMSI messages, SIB messages, or other DL signals sent to UEs 604b-604c.

[0091] Base stations 602a-602c can provide activation / deactivation configurations for RACH transmissions based on lower-layer signaling. For example, base stations 602a-602c can configure RACH transmission activation / deactivation via a MAC-Control Element (MAC-CE) or DCI. UEs 604b-604c / 606 can receive this configuration when they are in connected mode. Base stations 602a-602c can determine to deactivate RACH transmissions to increase the likelihood of successfully receiving DL transmissions from base stations 602a-602c (e.g., DL transmissions have a higher priority than RACH transmissions). RACH can be pre-allocated / pre-configured based on certain symbols. Therefore, scheduling flexibility can be provided to base stations 602a-602c via the RACH activation / deactivation mechanism, as FDRACH transmissions may lead to DL transmission failures. If RACH transmission is deactivated during such a symbol period, UE 604a-604c can receive DL transmissions without self-interference from RACH transmissions in the UL. For example, URLLC transmissions in the DL can be associated with higher reliability and lower latency than RACH transmissions in UE 604a-604b / 606. Therefore, RACH transmission can be deactivated / disabled during such DL transmission symbols to increase the likelihood of UE 604a-604c receiving URLLC transmissions.

[0092] Figure 7This is a flowchart 700 of a wireless communication method. The method can be executed by a UE (e.g., UE 104, 402, 502, 604a-604c, 606; device 1102; etc.), which may include a memory 360 and may be the entire UE 104, 402, 502, 604a-604c, 606 or components of UE 104, 402, 502, 604a-604c, 606, such as a TX processor 368, an RX processor 356, and / or a controller / processor 359.

[0093] At 702, the UE can receive configuration for multiple parameter sets, each of which includes one or more parameters for RACH messages and is associated with one of TDM, FDM, or SDM. For example, refer to Figure 4 and Figures 6A-6C At 406a, UE 402 can receive RACH parameter configuration for TDM / FDM / SDM RACH message transmission from base station 404. Similarly, UEs 604b-604c / 606 can receive RACH configuration for parameter sets from base stations 602a-602c. Configurations for multiple parameter sets (e.g., parameter set configuration 406b) can correspond to different parameter sets within multiple parameter sets for each of TDM, FDM, and SDM; or configurations for multiple parameter sets (e.g., parameter set configuration 406b) can correspond to a common parameter set within multiple parameter sets for TDM, FDM, and SDM, and different parameter sets within multiple parameter sets for each of TDM, FDM, and SDM. In either case, the different parameter sets may include a first set of parameter sets associated with a two-step RACH procedure and a second set of parameter sets associated with a four-step RACH procedure. For example, parameter set configuration 406b may include three parameter sets for two-step RACH and three parameter sets for four-step RACH. Different parameter sets (e.g., parameter set configuration 406b) can be based on different values ​​of one or more parameters for each of TDM, FDM, and SDM. In various aspects, one or more parameters (e.g., parameter set configuration 406b) may include an SINR threshold for at least one of SSB or CSI-RS. The configuration of multiple parameter sets for RACH messages can be received by UE 402 in connected mode via RRC signaling at 406a, or the configuration of multiple parameter sets for RACH messages can be received by UE 402 in broadcast mode via RMSI at 406a.

[0094] At 704, the UE can determine the transmission type of the RACH message, which corresponds to one or more of TDM, FDM, or SDM. For example, refer to... Figure 4At 408, UE 402 can determine the RACH transmission type (e.g., TDM / FDM / SDM).

[0095] At point 706, the UE can send a RACH message based on at least one parameter set from a plurality of parameter sets, wherein the at least one parameter set is associated with the determined transmission type of the RACH message. For example, refer to Figure 4 and Figures 6A-6C At 410, UE 402 can send a RACH message based on the parameter set and the determined transmission type. Similarly, UEs 604b-604c / 606 can send a UL RACH message to base stations 602a-602b / 608 via TDM / FDM / SDM based on the RACH configuration received from base stations 602a-602c.

[0096] Figure 8 This is a flowchart 800 of a wireless communication method. The method can be executed by a base station (e.g., base station 102, 404, 504, 602a-602c, 608; device 1202; etc.), which may include a memory 376 and may be the entire base station 102, 404, 504, 602a-602c, 608 or components of base station 102, 404, 504, 602a-602c, 608, such as a TX processor 316, an RX processor 370, and / or a controller / processor 375.

[0097] At point 802, the base station can configure multiple parameter sets based on different parameter sets from multiple parameter sets used for each of TDM, FDM, and SDM. For example, refer to Figure 4 Base station 404 can configure all different parameter sets for TDM / FDM / SDM via parameter set configuration 406b. (For example,) the different parameter sets of parameter set configuration 406b can include a first set of parameter sets associated with a two-step RACH process and a second set of parameter sets associated with a four-step RACH process. For example, parameter set configuration 406b can include three parameter sets for two-step RACH and three parameter sets for four-step RACH. (For example,) the different parameter sets of parameter set configuration 406b can be based on different values ​​of one or more parameters for each of TDM, FDM, and SDM.

[0098] At 804, the base station can alternatively configure multiple parameter sets based on a common parameter set among multiple parameter sets for TDM, FDM, and SDM, and different parameter sets among multiple parameter sets for each of TDM, FDM, and SDM. For example, refer to Figure 4Base station 404 can configure at least one common parameter set for TDM / FDM / SDM and different subsets of parameters for each of TDM / FDM / SDM via parameter set configuration 406b. (For example, the different parameter sets of parameter set configuration 406b) may include a first set of parameter sets associated with a two-step RACH process and a second set of parameter sets associated with a four-step RACH process. For example, parameter set configuration 406b may include three parameter sets for two-step RACH and three parameter sets for four-step RACH.

[0099] At 806, base stations 404 / 602a-602c can determine whether the transmission mode for a configuration of multiple parameter sets (e.g., parameter set configuration 406b) corresponds to a connection mode or a broadcast mode.

[0100] At 808, if the transport mode corresponds to the connected mode, the base station can configure multiple parameter sets for RACH messages in connected mode based on RRC signaling. For example, refer to Figure 4 Base station 404 can use RRC signaling to configure RACH parameters in connection mode.

[0101] At 810, if the transmission mode corresponds to broadcast mode, the base station can configure multiple parameter sets for RACH messages in broadcast mode based on RMSI. For example, refer to Figure 4 Base station 404 can use RMSI to configure RACH parameters in broadcast mode.

[0102] At point 812, based on either connection mode or broadcast mode, the base station can send configurations for multiple parameter sets, each of which includes one or more parameters for the RACH message and is associated with one of TDM, FDM, or SDM. For example, refer to... Figure 4 and Figures 6A-6C Base station 404 can send RACH parameter set configuration to UE 402 at 406a. Base stations 602a-602c can similarly send RACH configuration to UEs 604b-604c / 606. One or more parameters (e.g., included in parameter set configuration 406b / RACH configuration) may include SINR thresholds for at least one of SSB or CSI-RS.

[0103] At point 814, the base station can receive RACH messages based on at least one parameter set from a plurality of parameter sets, which is associated with the transmission type of the RACH message, corresponding to one or more of TDM, FDM, or SDM. For example, refer to Figure 4 and Figures 6A-6CAt 410, base station 404 can receive RACH messages based on a parameter set and a determined transmission type (e.g., TDM / FDM / SDM). Similarly, base stations 602a-602b / 608 can receive UL RACH messages from UEs 604b-604c / 606 via TDM / FDM / SDM based on the parameter set configured for RACH.

[0104] Figure 9 This is a flowchart 900 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, 402, 502, 604a-604c, 606; device 1302; etc.), which may include a memory 360 and may be the entire UE 104, 402, 502, 604a-604c, 606 or components of UE 104, 402, 502, 604a-604c, 606, such as a TX processor 368, an RX processor 356, and / or a controller / processor 359.

[0105] At position 902, the UE can receive configuration for sending RACH messages, which is associated with multiple transport types including TDM, FDM, and SDM. For example, refer to... Figure 5-6C At 506, UE 502 can receive RACH message configuration from base station 504. Similarly, UEs 604b-604c / 606 can receive RACH configuration for transport type selection (e.g., TDM / FDM / SDM) from base stations 602a-602c.

[0106] At 904, the UE can determine at least one of a plurality of transport types for the RACH message, which corresponds to one or more of TDM, FDM, or SDM. For example, refer to Figure 5At 508a, UE 502 can determine the RACH transmission type (e.g., TDM / FDM / SDM) based on determination protocol 508b. In a first aspect, at 508a, at least one transmission type in the RACH message can be determined based on the latest timing of the transmission type for the RACH message (e.g., determined by the UE according to determination protocol 508b). In a second aspect, at 508a, at least one transmission type can be determined based on at least one of the measured RSRP of the SSB or CSI-RS, or the SINR of the SSB or CSI-RS (e.g., RSRP-based / SINR-based according to determination protocol 508b). In a third aspect, the configuration (e.g., received at 506) can include a priority indication for the RACH message, wherein at 508a, at least one transmission type can be determined based on the priority indication (e.g., priority-based according to determination protocol 508b). The priority indication may correspond to the priority of the service category subscribed by UE 502. In the fourth aspect, at 508a, at least one transport type can be determined based on the purpose of the RACH message (e.g., according to the purpose-based determination protocol 508b), wherein the purpose can correspond to at least one of initial access, BFR, or TA command. Initial access can be associated with TDM, and each of the BFR and TA commands can be associated with at least one of FDM or SDM. In the fifth aspect, at 508a, at least one transport type can be determined based on the number of retransmission attempts for the RACH message (e.g., according to the multiple attempts determination protocol 508b).

[0107] At 906, the UE can deactivate or activate the FD transmission mode for RACH messages, which corresponds to at least one of FDM or SDM, indicated by the received configuration and based on the priority of DL transmission. For example, refer to Figure 5-6C At 510, UE 502 can activate / deactivate its FD mode. For example, FD activation / deactivation can be indicated in the RACH message configuration based on DL transmission priority received at 506. UEs 604b-604c can be configured in FD mode to send UL RACH messages to base stations 602b / 608 based on FDM / SDM. UE 606 can be configured in HD mode to send UL RACH messages to base station 602a based on TDM.

[0108] In 908, the UE can switch at least one transport type for a RACH message from a first transport type to a second transport type among a plurality of transport types based on the number of retransmission attempts for the RACH message. For example, refer to Figure 5At 512, UE 502 can switch from FDM / SDM to TDM via a multi-trial protocol of determination protocol 508b.

[0109] At 910, the UE can send a RACH message based on the received configuration for the RACH message and at least one transport type of the determined RACH message. For example, refer to Figure 5 At point 514, UE 502 can send a RACH message based on the received configuration and the determined transmission type. Similarly, UEs 604b-604c / 606 can send a UL RACH message to base stations 602a-602b / 608 via TDM / FDM / SDM based on the RACH configuration received from base stations 602a-602c / 608.

[0110] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be executed by a base station (e.g., base station 102, 404, 504, 602a-602c, 608; device 1402; etc.), which may include a memory 376 and may be the entire base station 102, 404, 504, 602a-602c, 608 or components of base station 102, 404, 504, 602a-602c, 608, such as a TX processor 316, an RX processor 370, and / or a controller / processor 375.

[0111] At point 1002, the base station can configure the deactivation or activation of the FD transmission mode for RACH messages based on the priority of DL transmission. The FD transmission mode corresponds to at least one of FDM or SDM. For example, refer to Figure 5-6C Base station 504 can configure FD activation / deactivation of UE 502 based on DL transmission priority. UEs 604b-604c can send UL RACH messages to base stations 602b / 608 in FD mode via FDM / SDM. UE 606 can send UL RACH messages to base station 602a in HD mode via TDM.

[0112] At position 1004, the base station can send a configuration for the RACH message, which is associated with multiple transport types, including TDM, FDM, and SDM. For example, refer to... Figure 5-6C At point 506, base station 504 can send a RACH message configuration to UE 502 to trigger UL RACH transmission based on TDM / FDM / SDM. Similarly, base stations 602a-602c / 608 can send RACH configuration to UEs 604a-604c / 606.

[0113] At point 1006, the base station can receive RACH messages based on the configuration sent for the RACH messages and at least one of several transport types for the RACH messages, wherein the at least one transport type corresponds to one or more of TDM, FDM, or SDM. For example, refer to Figure 5-6C At point 514, base station 504 can receive RACH messages from UE 502 based on the transmitted configuration and the corresponding transmission type (e.g., TDM / FDM / SDM). Similarly, base stations 602a-602b / 608 can receive UL RACH messages from UEs 604b-604c / 606 via TDM / FDM / SDM. In the first aspect, at least one transmission type for the RACH message can be based on the latest timing of the transmission type for the RACH message (e.g., determined by the UE according to determination protocol 508b). In the second aspect, at least one transmission type can be based on at least one of the following: a measurement of RSRP of SSB or CSI-RS, or a measurement of SINR of SSB or CSI-RS (e.g., RSRP-based / SINR-based according to determination protocol 508b). In the third aspect, the configuration (e.g., sent at 506) may include a priority indication for the RACH message, wherein at least one transport type may be based on the priority indication (e.g., priority-based according to determination protocol 508b). The priority indication may correspond to the priority of the subscribed service category configured to be sent to UE 502 at 506. In the fourth aspect, at least one transport type may be based on the purpose of the RACH message (e.g., purpose-based according to determination protocol 508b), wherein the purpose may correspond to at least one of initial access, BFR, or TA command. Initial access may be associated with TDM, and each of the BFR and TA commands may be associated with at least one of FDM or SDM. In the fifth aspect, at 514, a RACH message can be received based on a second transport type (e.g., at least one of FDM or SDM) among a plurality of transport types, wherein at least one transport type can be switched from a first transport type (e.g., TDM) among a plurality of transport types (e.g., TDM) based on the number of retransmission attempts for the RACH message (e.g., based on multiple attempts according to determination protocol 508b).

[0114] Figure 11Figure 1100 illustrates an example of a hardware implementation for device 1102. Device 1102 is a UE and includes: a cellular baseband processor 1104 (also referred to as a modem) coupled to a cellular RF transceiver 1122 and one or more SIM cards 1120; an application processor 1106 coupled to a secure digital card (SD) 1108 and a screen 1110; a Bluetooth module 1112; a wireless local area network (WLAN) module 1114; a global positioning system (GPS) module 1116; and a power supply 1118. The cellular baseband processor 1104 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1122. The cellular baseband processor 1104 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1104 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1104, the software causes the cellular baseband processor 1104 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1104 during software execution. The cellular baseband processor 1104 also includes a receiving component 1130, a communication manager 1132, and a transmitting component 1134. The communication manager 1132 includes one or more of the components shown. The components within the communication manager 1132 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1104. The cellular baseband processor 1104 can be a component of the UE 350 and can include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or memory 360. In one configuration, the device 1102 can be a modem chip and only include the baseband processor 1104, and in another configuration, the device 1102 can be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional module of device 1102.

[0115] The receiving component 1130 is configured to receive configurations for multiple parameter sets, each parameter set including one or more parameters for a RACH message and associated with one of TDM, FDM, or SDM, for example, as described in conjunction with 702. The communication manager 1132 includes a determining component 1140 configured to determine the transmission type of a RACH message, which corresponds to one or more of TDM, FDM, or SDM, for example, as described in conjunction with 704. The sending component 1134 is configured to send a RACH message based on at least one parameter set from the multiple parameter sets, the at least one parameter set being associated with the determined transmission type of the RACH message, for example, as described in conjunction with 706.

[0116] The device may include the ability to perform the above-described actions. Figure 7 The flowchart shows the algorithm's additional components in each box. Therefore, the above... Figure 7 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0117] In one configuration, apparatus 1102 (and specifically, cellular baseband processor 1104) includes: a unit for receiving configurations for a plurality of parameter sets, each parameter set including one or more parameters for a Random Access Channel (RACH) message and associated with one of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or Space Division Multiplexing (SDM); a unit for determining a transmission type of the RACH message, the transmission type corresponding to one or more of TDM, FDM, or SDM; and a unit for transmitting the RACH message based on at least one parameter set from the plurality of parameter sets, the at least one parameter set being associated with the determined transmission type of the RACH message. The aforementioned unit may be one or more of the components of apparatus 1102 configured to perform the functions described therein. As described above, apparatus 1102 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned unit may be the TX processor 368, the RX processor 356, and the controller / processor 359, configured to perform the functions described therein.

[0118] Figure 12Figure 1200 illustrates an example of a hardware implementation for device 1202. Device 1202 is a BS and includes a baseband unit 1204. Baseband unit 1204 can communicate with UE 104 via cellular RF transceiver 1222. Baseband unit 1204 may include computer-readable medium / memory. Baseband unit 1204 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by baseband unit 1204, the software causes baseband unit 1204 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by baseband unit 1204 when executing the software. Baseband unit 1204 also includes a receiving component 1230, a communication manager 1232, and a transmitting component 1234. Communication manager 1232 includes one or more of the components shown. Components within communication manager 1232 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 1204. The baseband unit 1204 may be a component of the BS 310 and may include at least one of the TX processor 316, the RX processor 370 and the controller / processor 375 and / or the memory 376.

[0119] The receiving component 1230 is configured to receive RACH messages based on at least one parameter set from a plurality of parameter sets, the at least one parameter set being associated with the transmission type of the RACH message, the transmission type corresponding to one or more of TDM, FDM, or SDM, for example, as described in conjunction with 814. The communication manager 1232 includes a configuration component 1240 configured to: configure multiple parameter sets based on different parameter sets from the plurality of parameter sets for each of TDM, FDM, and SDM; configure multiple parameter sets based on a common parameter set from the plurality of parameter sets for TDM, FDM, and SDM, and different parameter sets from the plurality of parameter sets for each of TDM, FDM, and SDM; configure multiple parameter sets for RACH messages in connection mode based on RRC signaling; and configure multiple parameter sets for RACH messages in broadcast mode based on RMSI, for example, as described in conjunction with 802, 804, 808, and 810. The sending component 1234 is configured to send configurations for multiple parameter sets, each of which includes one or more parameters for RACH messages and is associated with one of TDM, FDM, or SDM, for example, as described in conjunction with 812.

[0120] The device may include the ability to perform the above-described actions. Figure 8 The flowchart shows the algorithm's additional components in each box. Therefore, the above... Figure 8Each box in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0121] In one configuration, apparatus 1202 (and specifically, baseband unit 1204) includes: a unit for transmitting configurations for multiple parameter sets, each parameter set including one or more parameters for RACH messages and associated with one of TDM, FDM, or SDM; and a unit for receiving RACH messages based on at least one parameter set of the multiple parameter sets, the at least one parameter set being associated with a transmission type of the RACH message, the transmission type corresponding to one or more of TDM, FDM, or SDM. Apparatus 1202 further includes: a unit for configuring the multiple parameter sets based on different parameter sets in the multiple parameter sets for each of TDM, FDM, and SDM. Apparatus 1202 further includes: a unit for configuring the multiple parameter sets based on a common parameter set in the multiple parameter sets for TDM, FDM, and SDM, and different parameter sets in the multiple parameter sets for each of TDM, FDM, and SDM. Apparatus 1202 further includes: a unit for configuring the multiple parameter sets for RACH messages in connection mode based on RRC signaling. The apparatus 1202 further includes a unit for configuring multiple parameter sets for RACH messages in broadcast mode based on RMSI. This unit may be one or more of the components of the apparatus 1202 configured to perform the functions described therein. As described above, the apparatus 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the unit may be the TX processor 316, the RX processor 370, and the controller / processor 375, configured to perform the functions described therein.

[0122] Figure 13Figure 1300 illustrates an example of a hardware implementation for device 1302. Device 1302 is a UE and includes: a cellular baseband processor 1304 (also referred to as a modem) coupled to a cellular RF transceiver 1322 and one or more SIM cards 1320; an application processor 1306 coupled to a secure digital card (SD) 1308 and a screen 1310; a Bluetooth module 1312; a wireless local area network (WLAN) module 1314; a global positioning system (GPS) module 1316; and a power supply 1318. The cellular baseband processor 1304 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1322. The cellular baseband processor 1304 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1304 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1304, the software causes the cellular baseband processor 1304 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1304 during software execution. The cellular baseband processor 1304 also includes a receiving component 1330, a communication manager 1332, and a transmitting component 1334. The communication manager 1332 includes one or more of the components shown. The components within the communication manager 1332 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1304. The cellular baseband processor 1304 can be a component of the UE 350 and can include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or memory 360. In one configuration, the device 1302 can be a modem chip and only include the baseband processor 1304; in another configuration, the device 1302 can be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional module of device 1302.

[0123] The receiving component 1330 is configured to receive a configuration for transmitting a RACH message, which is associated with multiple transport types including TDM, FDM, and SDM, for example, as described in conjunction with 902. The communication manager 1332 includes a determining component 1340 configured to determine at least one transport type among multiple transport types for the RACH message, the at least one transport type corresponding to one or more of TDM, FDM, or SDM, for example, as described in conjunction with 904. The communication manager 1332 also includes an activation-deactivation component 1342 configured to deactivate or activate an FD transport mode for the RACH message, the FD transport mode corresponding to at least one of FDM or SDM, deactivating or activating the mode indicated by the received configuration and based on the priority of DL transport, for example, as described in conjunction with 906. The communication manager 1332 also includes a switcher component 1344 configured to switch at least one transport type for a RACH message from a first transport type among a plurality of transport types to a second transport type among a plurality of transport types based on the number of retransmission attempts for the RACH message, for example, as described in conjunction with 908.

[0124] The device may include the ability to perform the above-described actions. Figure 9 The flowchart shows the algorithm's additional components in each box. Therefore, the above... Figure 9 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0125] In one configuration, apparatus 1302 (and specifically, cellular baseband processor 1304) includes: unit for receiving a configuration for transmitting RACH messages, the configuration being associated with a plurality of transmission types including TDM, FDM, and SDM; unit for determining at least one transmission type among the plurality of transmission types for RACH messages, the at least one transmission type corresponding to one or more of TDM, FDM, or SDM; and unit for transmitting RACH messages based on the received configuration for RACH messages and the determined at least one transmission type of RACH messages. Apparatus 1302 further includes: unit for switching at least one transmission type for RACH messages from a first transmission type among the plurality of transmission types to a second transmission type among the plurality of transmission types based on the number of retransmission attempts for the RACH messages. Apparatus 1302 further includes: unit for deactivating an FD transmission mode for RACH messages or unit for activating an FD transmission mode for RACH messages, the FD transmission mode corresponding to at least one of FDM or SDM, deactivating or activating a priority indicated via the received configuration and based on downlink (DL) transmission. The aforementioned unit may be one or more of the components of the device 1302 configured to perform the functions described therein. As described above, the device 1302 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned unit may be the TX processor 368, the RX processor 356, and the controller / processor 359, configured to perform the functions described therein.

[0126] Figure 14Figure 1400 illustrates an example of a hardware implementation for device 1402. Device 1402 is a BS and includes a baseband unit 1404. Baseband unit 1404 can communicate with UE 104 via cellular RF transceiver 1422. Baseband unit 1404 may include computer-readable medium / memory. Baseband unit 1404 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by baseband unit 1404, the software causes baseband unit 1404 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by baseband unit 1404 when executing the software. Baseband unit 1404 also includes a receiving component 1430, a communication manager 1432, and a transmitting component 1434. Communication manager 1432 includes one or more of the components shown. Components within communication manager 1432 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 1404. The baseband unit 1404 may be a component of the BS 310 and may include at least one of the TX processor 316, the RX processor 370 and the controller / processor 375 and / or the memory 376.

[0127] The receiving component 1430 is configured to receive RACH messages based on a configuration for the transmitted RACH message and at least one of a plurality of transport types for the RACH message, the at least one transport type corresponding to one or more of TDM, FDM, or SDM, for example, as described in conjunction with 1006. The communication manager 1432 includes a configuration component 1440 configured to configure the deactivation or activation of an FD transport mode for the RACH message based on the priority of DL transport, the FD transport mode corresponding to at least one of FDM or SDM, for example, as described in conjunction with 1002. The transmitting component 1434 is configured to transmit a configuration for the RACH message, the configuration being associated with a plurality of transport types including TDM, FDM, and SDM, for example, as described in conjunction with 1004.

[0128] The device may include the functions described above. Figure 10 The flowchart shows the algorithm's additional components in each box. Therefore, in the above... Figure 10 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0129] In one configuration, device 1402 (and specifically, baseband unit 1404) includes: a unit for transmitting a configuration for RACH messages, the configuration being associated with multiple transmission types including TDM, FDM, and SDM; and a unit for receiving RACH messages based on the transmitted configuration for RACH messages and at least one of the multiple transmission types of RACH messages, the at least one transmission type corresponding to one or more of TDM, FDM, or SDM. Device 1402 further includes: a unit for configuring the deactivation or activation of an FD transmission mode for RACH messages based on the priority of DL transmissions, the FD transmission mode corresponding to at least one of FDM or SDM. The aforementioned units may be one or more of the components of device 1402 configured to perform the functions described therein. As described above, device 1402 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned units may be the TX processor 316, the RX processor 370, and the controller / processor 375, configured to perform the functions described therein.

[0130] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the example method. It should be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims give the elements of each box in the example order, but are not intended to limit one to the given specific order or hierarchy.

[0131] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the language of the claims, wherein, unless expressly stated otherwise, references to the singular element are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the same time as” should be interpreted as “under the condition of,” rather than implying an immediate temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only that an action will occur if the condition is met, but do not require a specific or immediate temporal constraint on the occurrence of the action. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred over or superior to other aspects. Unless expressly stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements described throughout the various aspects of this disclosure that are known to or will be known later by one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. Furthermore, the disclosure herein is not intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. Terms such as “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “unit.” Therefore, no claim can be made that an element should be interpreted as a functional unit unless the element is explicitly described using the phrase “unit for…”.

[0132] The following aspects are illustrative only and may be combined with other aspects or teachings described herein without limitation.

[0133] Aspect 1 is a method for wireless communication of a UE, characterized by: receiving configuration for a plurality of parameter sets, each of the plurality of parameter sets including one or more parameters for a RACH message and associated with one of TDM, FDM or SDM; determining a transmission type of the RACH message, the transmission type corresponding to one or more of the TDM, the FDM or SDM; and transmitting the RACH message based on at least one parameter set of the plurality of parameter sets, the at least one parameter set being associated with the determined transmission type of the RACH message.

[0134] Aspect 2 can be combined with aspect 1, and is characterized in that: the configuration for the plurality of parameter sets corresponds to different parameter sets in the plurality of parameter sets for each of the TDM, the FDM and the SDM.

[0135] Aspect 3 can be combined with any of Aspects 1-2, and is characterized in that: the different parameter sets include a first set of parameter sets associated with a two-step RACH process and a second set of parameter sets associated with a four-step RACH process.

[0136] Aspect 4 can be combined with any of aspects 1-3, and is characterized in that: the different parameter sets are based on different values ​​of one or more parameters for each of the TDM, the FDM and the SDM.

[0137] Aspect 5 may be combined with either aspect 1 or 4, and is characterized in that: the configuration for the plurality of parameter sets corresponds to a common parameter set in the plurality of parameter sets for the TDM, the FDM and the SDM, and a different parameter set in the plurality of parameter sets for each of the TDM, the FDM and the SDM.

[0138] Aspect 6 may be combined with aspect 1 or any of aspects 4-5, and is characterized in that: the different parameter sets include a first set of parameter sets associated with a two-step RACH process and a second set of parameter sets associated with a four-step RACH process.

[0139] Aspect 7 may be combined with any of aspects 1-6, and is characterized in that the configuration of the plurality of parameter sets for the RACH message is received via RRC signaling in connection mode.

[0140] Aspect 8 may be combined with any of aspects 1-6, and is characterized in that the configuration of the plurality of parameter sets for the RACH message is received via RMSI in broadcast mode.

[0141] Aspect 9 may be combined with any of aspects 1-8, and is characterized in that: the one or more parameters include a SINR threshold for at least one of SSB or CSI-RS.

[0142] Aspect 10 is a method for wireless communication of a base station, characterized by: transmitting configuration for a plurality of parameter sets, each of the plurality of parameter sets including one or more parameters for a RACH message and associated with one of TDM, FDM or SDM; and receiving the RACH message based on at least one parameter set of the plurality of parameter sets, the at least one parameter set being associated with a transmission type of the RACH message, the transmission type corresponding to one or more of the TDM, the FDM or the SDM.

[0143] Aspect 11 can be combined with aspect 10, and is further characterized in that the plurality of parameter sets are configured based on different parameter sets in the plurality of parameter sets for each of the TDM, the FDM and the SDM.

[0144] Aspect 12 may be combined with any of aspects 10-11, and is characterized in that: the different parameter sets include a first set of parameter sets associated with a two-step RACH process and a second set of parameter sets associated with a four-step RACH process.

[0145] Aspect 13 may be combined with any of aspects 10-12, and is characterized in that: the different sets of parameters are based on different values ​​of one or more parameters for each of the TDM, the FDM and the SDM.

[0146] Aspect 14 may be combined with any one of aspects 10 or 13, and is further characterized in that the plurality of parameter sets are configured based on a common parameter set in the plurality of parameter sets for the TDM, the FDM and the SDM and different parameter sets in the plurality of parameter sets for each of the TDM, the FDM and the SDM.

[0147] Aspect 15 may be combined with any one of Aspects 10 or 13-14, and is characterized in that: the different parameter sets include a first set of parameter sets associated with a two-step RACH process and a second set of parameter sets associated with a four-step RACH process.

[0148] Aspect 16 may be combined with any one of aspects 10-15, and is further characterized by configuring the plurality of parameter sets for the RACH message in connection mode based on RRC signaling.

[0149] Aspect 17 may be combined with any of aspects 10-15, and is further characterized in that: the plurality of parameter sets for the RACH message in broadcast mode are configured based on RMSI.

[0150] Aspect 18 may be combined with any of aspects 10-17, and is characterized in that the one or more parameters include a SINR threshold for at least one of SSB or CSI-RS.

[0151] Aspect 19 is a method for wireless communication of a UE, characterized by: receiving a configuration for transmitting a RACH message, the configuration being associated with a plurality of transmission types including TDM, FDM, and SDM; determining at least one transmission type among the plurality of transmission types for the RACH message, the at least one transmission type corresponding to one or more of the TDM, the FDM, or the SDM; and transmitting the RACH message based on the received configuration for the RACH message and the determined at least one transmission type of the RACH message.

[0152] Aspect 20 may be combined with aspect 19, and is characterized in that: the at least one transmission type for the RACH message is determined based on the latest timing of the transmission type for the RACH message.

[0153] Aspect 21 may be combined with aspect 19, and is characterized in that: the at least one transmission type is determined based on at least one of the measured values ​​of RSRP of SSB or CSI-RS or SINR of SSB or CSI-RS.

[0154] Aspect 22 may be combined with aspect 19, and is characterized in that: the configuration includes a priority indication for the RACH message, the at least one transport type being determined based on the priority indication.

[0155] Aspect 23 may be combined with any one of aspects 19 or 22, and is characterized in that: the priority indicates the priority corresponding to the ordering service category of the UE.

[0156] Aspect 24 may be combined with aspect 19, and is characterized in that: the at least one transmission type is determined based on the purpose of the RACH message, the purpose corresponding to at least one of initial access, BFR or TA command.

[0157] Aspect 25 may be combined with any one of Aspects 19 or 24, and is characterized in that: the initial access is associated with the TDM, and each of the BFR and the TA command is associated with at least one of the FDM or the SDM.

[0158] Aspect 26 may be combined with aspect 19, and is further characterized in that: the at least one transport type for the RACH message is switched from a first transport type among the plurality of transport types to a second transport type among the plurality of transport types based on the number of retransmission attempts for the RACH message.

[0159] Aspect 27 may be combined with any one of aspects 19-26, and is further characterized by: deactivating or activating the FD transmission mode for the RACH message, the FD transmission mode corresponding to at least one of the FDM or the SDM, the deactivation or activation being indicated via the received configuration and based on the priority of the DL transmission.

[0160] Aspect 28 is a method for wireless communication of a base station, comprising: transmitting a configuration for a RACH message, the configuration being associated with a plurality of transmission types including TDM, FDM and SDM; and receiving the RACH message based on the transmitted configuration for the RACH message and at least one of the plurality of transmission types of the RACH message, the at least one transmission type corresponding to one or more of the TDM, the FDM or the SDM.

[0161] Aspect 29 may be combined with aspect 28, and is characterized in that: the at least one transport type for the RACH message is based on the latest timing of the transport type for the RACH message.

[0162] Aspect 30 may be combined with aspect 28, and is characterized in that: the at least one transmission type is based on at least one of the measured values ​​of RSRP of SSB or CSI-RS or SINR of SSB or CSI-RS.

[0163] Aspect 31 may be combined with aspect 28, and is characterized in that: the configuration includes a priority indication for the RACH message, the at least one transport type being based on the priority indication.

[0164] Aspect 32 may be combined with any one of aspects 28 or 31, and is characterized in that: the priority indication corresponds to the priority of the subscribed service category of the UE to which the configuration is sent.

[0165] Aspect 33 may be combined with aspect 28, and is characterized in that: the at least one transmission type is based on the purpose of the RACH message, the purpose corresponding to at least one of initial access, BFR or TA command.

[0166] Aspect 34 may be combined with any one of aspects 28 or 33, and is characterized in that: the initial access is associated with the TDM, and each of the BFR and the TA command is associated with at least one of the FDM or the SDM.

[0167] Aspect 35 may be combined with aspect 28, and is characterized in that: the RACH message is received based on a second transport type among the plurality of transport types, and the at least one transport type switches from a first transport type among the plurality of transport types to the second transport type based on a threshold number of retransmission attempts for the RACH message.

[0168] Aspect 36 may be combined with any one of aspects 28-35, and is further characterized in that: the deactivation or activation of the FD transmission mode for the RACH message is configured based on the priority of the DL transmission, the FD transmission mode corresponding to at least one of the FDM or the SDM.

[0169] Aspect 37 is an apparatus for wireless communication, including at least one processor coupled to a memory and configured to implement the methods of any one of aspects 1-36.

[0170] Aspect 38 is an apparatus for wireless communication, including units for implementing the methods of any one of aspects 1-36.

[0171] Aspect 39 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement the methods of any one of aspects 1-36.

Claims

1. A method for wireless communication of a user equipment (UE), comprising: Receive configuration for sending Random Access Channel (RACH) messages, the configuration being associated with multiple transmission types including Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), and Space Division Multiplexing (SDM); Determine at least one of the plurality of transport types for the RACH message, the at least one transport type corresponding to one or more of the TDM, the FDM, or the SDM; The RACH message is sent based on the received configuration for the RACH message and at least one transport type of the RACH message determined. as well as Based on the number of retransmission attempts for the RACH message, the at least one transport type used for the RACH message is switched from a first transport type among the plurality of transport types to a second transport type among the plurality of transport types.

2. The method according to claim 1, wherein, The at least one transport type used for the RACH message is determined based on the latest timing of the transport type used for the RACH message.

3. The method according to claim 1, wherein, The at least one transmission type is determined based on at least one of the following: a measurement of the reference signal received power (RSRP) of the synchronization signal block (SSB) or the channel state information reference signal (CSI-RS), or a measurement of the signal-to-interference-plus-noise ratio (SINR) of the SSB or the CSI-RS.

4. The method according to claim 1, wherein, The configuration includes a priority indication for the RACH message, and the at least one transport type is determined based on the priority indication.

5. The method according to claim 4, wherein, The priority indicator corresponds to the priority of the service category ordered by the UE.

6. The method according to claim 1, wherein, The at least one transmission type is determined based on the purpose of the RACH message, which corresponds to at least one of initial access, beam failure request (BFR), or timing advance (TA) command.

7. The method according to claim 6, wherein, The initial access is associated with the TDM, and each of the BFR and the TA command is associated with at least one of the FDM or the SDM.

8. The method according to claim 1, further comprising: Deactivate or activate the full-duplex (FD) transmission mode for the RACH message, the FD transmission mode corresponding to at least one of the FDM or the SDM, the deactivation or activation being indicated via the received configuration and based on the priority of the downlink (DL) transmission.

9. A method for wireless communication of a base station, comprising: Sending configurations for Random Access Channel (RACH) messages, the configurations being associated with multiple transmission types including Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), and Space Division Multiplexing (SDM); as well as The RACH message is received based on the configuration sent for the RACH message and at least one of the plurality of transport types of the RACH message, the at least one transport type corresponding to one or more of the TDM, the FDM or the SDM, wherein the RACH message is received based on a second transport type of the plurality of transport types, and the at least one transport type switches from a first transport type of the plurality of transport types to the second transport type based on a threshold number of retransmission attempts for the RACH message.

10. The method according to claim 9, wherein, The at least one transport type used for the RACH message is based on the latest timing of the transport type used for the RACH message.

11. The method according to claim 9, wherein, The at least one transmission type is based on at least one of the following: a measurement of the reference signal received power (RSRP) of the synchronization signal block (SSB) or the channel state information reference signal (CSI-RS), or a measurement of the signal-to-interference-plus-noise ratio (SINR) of the SSB or the CSI-RS.

12. The method according to claim 9, wherein, The configuration includes a priority indication for the RACH message, and the at least one transport type is based on the priority indication.

13. The method according to claim 12, wherein, The priority indicator corresponds to the priority of the service category of the user equipment (UE) to which the configuration is sent.

14. The method according to claim 9, wherein, The at least one transmission type is based on the purpose of the RACH message, which corresponds to at least one of initial access, beam failure request (BFR), or timing advance (TA) command.

15. The method according to claim 14, wherein, The initial access is associated with the TDM, and each of the BFR and the TA command is associated with at least one of the FDM or the SDM.

16. The method of claim 9, further comprising: The activation or deactivation of the full-duplex (FD) transmission mode for the RACH message is configured based on the priority of downlink (DL) transmission, the FD transmission mode corresponding to at least one of the FDM or the SDM.

17. An apparatus for wireless communication for a user equipment (UE), comprising: Memory; as well as At least one processor, coupled to the memory, is configured to: Receive configuration for sending Random Access Channel (RACH) messages, the configuration being associated with multiple transmission types including Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), and Space Division Multiplexing (SDM); Determine at least one of the plurality of transport types for the RACH message, the at least one transport type corresponding to one or more of the TDM, the FDM, or the SDM; The RACH message is sent based on the received configuration for the RACH message and at least one transport type of the RACH message determined. as well as Based on the number of retransmission attempts for the RACH message, the at least one transport type used for the RACH message is switched from a first transport type among the plurality of transport types to a second transport type among the plurality of transport types.

18. The apparatus according to claim 17, wherein, In order to determine the at least one transmission type, the at least one processor is configured to determine the at least one transmission type for the RACH message based on the latest timing of the transmission type for the RACH message.

19. The apparatus according to claim 17, wherein, To determine the at least one transmission type, the at least one processor is configured to determine the at least one transmission type based on at least one of the following: a measurement of the reference signal received power (RSRP) of the synchronization signal block (SSB) or the channel state information reference signal (CSI-RS), or a measurement of the signal-to-interference-plus-noise ratio (SINR) of the SSB or the CSI-RS.

20. The apparatus according to claim 17, wherein, The configuration includes a priority indication for the RACH message, and the at least one transport type is determined based on the priority indication.

21. The apparatus according to claim 17, wherein, To determine the at least one transmission type, the at least one processor is configured to determine the at least one transmission type based on the purpose of the RACH message, the purpose corresponding to at least one of initial access, beam failure request (BFR), or timing advance (TA) command.

22. An apparatus for wireless communication for a base station, comprising: Memory; as well as At least one processor, coupled to the memory, is configured to: Sending configurations for Random Access Channel (RACH) messages, the configurations being associated with multiple transmission types including Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), and Space Division Multiplexing (SDM); as well as The RACH message is received based on the configuration sent for the RACH message and at least one of the plurality of transport types of the RACH message, the at least one transport type corresponding to one or more of the TDM, the FDM or the SDM, wherein the RACH message is received based on a second transport type of the plurality of transport types, and the at least one transport type switches from a first transport type of the plurality of transport types to the second transport type based on a threshold number of retransmission attempts for the RACH message.

23. The apparatus according to claim 22, wherein, The at least one transport type used for the RACH message is based on the latest timing of the transport type used for the RACH message.

24. The apparatus according to claim 22, wherein, The at least one transmission type is based on at least one of the following: a measurement of the reference signal received power (RSRP) of the synchronization signal block (SSB) or the channel state information reference signal (CSI-RS), or a measurement of the signal-to-interference-plus-noise ratio (SINR) of the SSB or the CSI-RS.

25. The apparatus according to claim 22, wherein, The configuration includes a priority indication for the RACH message, and the at least one transport type is based on the priority indication.

26. The apparatus according to claim 22, wherein, The at least one transmission type is based on the purpose of the RACH message, which corresponds to at least one of initial access, beam failure request (BFR), or timing advance (TA) command.

Images