Patent Description:
Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, and orthogonal frequency-division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.

For example, a fifth generation (<NUM>) wireless communications technology (which can be referred to as <NUM> new radio (<NUM> NR)) is envisaged to expand and support diverse usage scenarios and applications with respect to current mobile network generations. In an aspect, <NUM> communications technology can include: enhanced mobile broadband addressing human-centric use cases for access to multimedia content, services and data; ultra-reliable low-latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which can allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information.

In some wireless communication technologies, user equipment (UE) can perform a random access procedure to initiate establishing a connection with an access point for receiving access to a wireless network. The UE can communicate one or more random access messages, such as a random access preamble and/or a random access payload, over time and/or frequency resources that are configured for random access. The UE can receive a response to the random access request and/or contention resolution information from the access point. In addition, in some wireless communication technologies, a UE and/or an access point can be configured for full duplex (FD) communications where the UE and/or access point can concurrently transmit and receive over wireless communication resources within the same frequency band or within the same component carrier.

Patent application publication <CIT> is a document of the prior art in the technical field in question.

According to an aspect, a method of wireless communication is provided. The method includes determining whether full duplex (FD) communications are configured during resources for communicating one or more messages of a random access procedure, the FD communications comprising uplink communications and downlink communications occurring in a same frequency band or in a same component carrier, and responsive to the determining whether the FD communications are configured during the resources, transmitting the one or more messages of the random access procedure using the resources.

In another aspect, a method of wireless communication is provided that includes determining whether to configure FD communications during resources for communicating, with a user equipment (UE), one or more messages of a random access procedure, the FD communications comprising uplink communications and downlink communications occurring in a same frequency band or in a same component carrier, and responsive to the determining whether to configure the FD communications during the resources, communicating at least one of one or more messages of the random access procedure.

In a further aspect, an apparatus for wireless communication is provided that includes a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of methods and examples described above and further herein. In another aspect, an apparatus for wireless communication is provided that includes means for performing the operations of methods and examples described above and further herein. In yet another aspect, a computer-readable medium is provided including code executable by one or more processors to perform the operations of methods and examples described above and further herein.

The described features generally relate to performing a random access procedure based on determining whether full duplex (FD) communications are configured. For example, a device that determines to transmit a random access preamble can determine whether FD communications are configured over the resources defined for transmitting the random access preamble. If so, the device can determine to use one or more different parameter values for transmitting the random access preamble where FD communications are configured than if FD communications are not configured. For example, the different parameter value(s) may include values for an initial transmit power for the random access preamble, a power ramping step for retransmitting the random access preamble, etc. In another example, the device can determine the different parameter value(s) of or relating to a random access format or configuration (e.g., for transmitting the random access preamble) based on whether FD communications are configured over the resources. In another example, the device can determine whether FD communications are configured over resources defined for transmitting and/or retransmitting a payload in the random access procedure. In either case, for example, the device can determine whether FD communications are configured over the resources (and/or can determine the different parameter value(s) and/or whether to use the different parameter values) based on at least one of a received configuration, a determined radio resource control (RRC) state, a determined service type, a signal measurement of signals received from an access point, and/or the like. Moreover, the device can determine whether a response message in the random access procedure is to be received over resources configured for FD communications, and if so, can refrain from transmitting or reduce transmit power over the resources.

Similarly, for example, an access point that configures random access opportunities or related resources for devices can expect to receive messages in the random access procedure based on whether the access point configures FD communications over the resources or not. For example, the access point may determine a random access format or configuration based on whether the access point configured FD communications over the resources. In addition, for example, the access point can configure the device with an indication of whether FD communications are configured over the resources or parameters for determining such. In one example, the access point can determine to not configure FD communications over resources including or at least overlapping resources defined for random access communications. In another example, the access point can determine to configure (and/or indicate configuration of) FD communications over resources including or at least overlapping resources defined for random access communication.

FD communications, as referred to herein, can include a single node (e.g., a user equipment (UE) or access point) transmitting and receiving (e.g., concurrently) over communication resources in the same frequency band and/or over communication resources in the same component carrier (CC). In one example, FD communications can include in-band full duplex (IBFD) where the single node can transmit and receive on the same time and frequency resource, and the downlink and uplink can share the same IBFD time/frequency resources (e.g., full and/or partial overlap). In another example, FD communications can include sub-band FD (also referred to as "flexible duplex") where the single node can transmit and receive at the same time but on different frequency resources within the same frequency band (or over communication resources in the same CC), where the downlink resource and the uplink resources can be separated in the frequency domain (e.g., by a guard band). For example, the guard band in sub-band FD can be on the order of resource block (RB) widths (e.g., <NUM> kilohertz (KHz) for third generation partnership project (3GPP) long term evolution (LTE) and fifth generation (<NUM>) new radio (NR), <NUM> and <NUM> for NR, etc.). This can be distinguished from a guard band in frequency division duplexing (FDD) communications defined in LTE and NR, which can be <NUM> megahertz (MHz) or more, and the associated resources in FDD are defined between frequency bands, but not within the same frequency band (or resources in the same CC) as is the case in sub-band FD communications.

In some examples of FD communications, various antenna configurations can be used within a device (e.g., an access point or UE) to facilitate FD communications. In one configuration, a transmit antenna array can be spatially separated from a receive antenna array within the device to reduce leakage (e.g., self-interference) from the transmit antenna array into the receive antenna array. In another example, the antenna array configuration of non-FD communications can use the same antenna array(s) for transmitting or receiving (but not both).

Moreover, a random access procedure can refer to a random access channel (RACH) procedure as defined in LTE and/or NR, such as a four-step RACH procedure, a two-step RACH procedure, etc. For example, a four-step RACH procedure can include a UE transmitting a first message (MSG1) over a physical RACH (PRACH) physical layer (PHY) channel, where the first message can include a PRACH preamble transmitted in a configured RACH occasion. The four-step RACH procedure can include an access point transmitting a second message (MSG2), in response to MSG1, over a physical downlink control channel (PDCCH) or physical downlink shared channel (PDSCH) as a random access response (RAR) including a timing advance, an uplink grant for a third message (MSG3), a temporary cell radio network temporary identifier (TC-RNTI), etc. The four-step RACH procedure can include the UE transmitting MSG3, in response to MSG2, over a physical uplink shared channel (PUSCH) including a radio resource control (RRC) connection request, a scheduling request, a buffer status, etc. The four-step RACH procedure can include the access point transmitting a fourth message (MSG4), in response to MSG3, over PDCCH or PDSCH including a contention resolution message. In another example, a two-step RACH procedure can include the UE transmitting a first message (MSG-A) that can include a RACH preamble and PUSCH payload, and the access point transmitting a second message (MSG-B), in response to MSG-A, including RAR and/or contention resolution message.

In addition, for example, the UE can be configured to use RACH in various cases, such as in requesting initial access with the access point, transitioning from one RRC state to another with the access point (e.g., from RRC IDLE/INACTIVE to RRC CONNECTED), performing RACH to a target cell during handover, transmitting small uplink data in RRC IDLE/INACTIVE without necessarily transitioning to RRC CONNECTED, performing beam failure recovery, etc..

In any case, in these or other examples, random access procedures can be improved based on the device and/or access point being able to determine whether FD communications are configured over random access resources and accordingly taking actions based on this determination. For example, the device and/or access point can determine to not use random access resources that overlap with those configured for FD communications, improve signal quality and/or hearability for random access communications over resources configured for FD communications, use different formats or configurations for random access communications over resources configured for FD communications, etc., as described further herein.

As used in this application, the terms "component," "module," "system" and the like are intended to include a computer-related entity, such as but not limited to hardware, software, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.

Techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" may often be used interchangeably. IS-<NUM> Releases <NUM> and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-<NUM> (TIA-<NUM>) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band. The description below, however, describes an LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to fifth generation (<NUM>) new radio (NR) networks or other next generation communication systems).

The wireless communications system (also referred to as a wireless wide area network (WWAN)) can include base stations <NUM>, UEs <NUM>, an Evolved Packet Core (EPC) <NUM>, and/or a <NUM> Core (5GC) <NUM>. The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells. In an example, the base stations <NUM> may also include gNBs <NUM>, as described further herein. In one example, some nodes of the wireless communication system may have a modem <NUM> and communicating component <NUM> for performing random access procedures based on determining whether corresponding resources are also configured for FD communications. In addition, some nodes may have a modem <NUM> and scheduling component <NUM> for configuring resources for random access procedures and/or for FD communications, as described herein. Though a UE <NUM> is shown as having the modem <NUM> and communicating component <NUM> and a base station <NUM> is shown as having the modem <NUM> and scheduling component <NUM>, this is one illustrative example, and substantially any node or type of node may include a modem <NUM> and communicating component <NUM> and/or a modem <NUM> and scheduling component <NUM> for providing corresponding functionalities described herein.

The base stations <NUM> configured for <NUM> LTE (which can collectively be referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through backhaul links <NUM> (e.g., using an S1 interface). The base stations <NUM> configured for 5GNR (which can collectively be referred to as Next Generation RAN (NG-RAN)) may interface with 5GC <NUM> through backhaul links <NUM>. The base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or 5GC <NUM>) with each other over backhaul links <NUM> (e.g., using an X2 interface).

The base stations <NUM> may wirelessly communicate with one or more UEs <NUM>. A network that includes both small cell and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group, which can be referred to as a closed subscriber group (CSG). The base stations <NUM> / UEs <NUM> may use spectrum up to Y MHz (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (e.g., for x component carriers) used for transmission in the DL and/or the UL direction. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

In another example, certain UEs <NUM> may communicate with each other using device-to-device (D2D) communication link <NUM>.

A base station <NUM>, whether a small cell <NUM>' or a large cell (e.g., macro base station), may include an eNB, gNodeB (gNB), or other type of base station. A base station <NUM> referred to herein can include a gNB <NUM>.

The 5GC <NUM> may include an Access and Mobility Management Function (AMF) <NUM>, other AMFs <NUM>, a Session Management Function (SMF) <NUM>, and a User Plane Function (UPF) <NUM>. The AMF <NUM> can be a control node that processes the signaling between the UEs <NUM> and the 5GC <NUM>. Generally, the AMF <NUM> can provide QoS flow and session management. User Internet protocol (IP) packets (e.g., from one or more UEs <NUM>) can be transferred through the UPF <NUM>. The UPF <NUM> can provide UE IP address allocation for one or more UEs, as well as other functions.

The base station <NUM> provides an access point to the EPC <NUM> or 5GC <NUM> for a UE <NUM>. Examples of UEs <NUM> include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a positioning system (e.g., satellite, terrestrial), a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, robots, drones, an industrial/manufacturing device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a vehicle/a vehicular device, a meter (e.g., parking meter, electric meter, gas meter, water meter, flow meter), a gas pump, a large or small kitchen appliance, a medical/healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs <NUM> may be referred to as IoT devices (e.g., meters, pumps, monitors, cameras, industrial/manufacturing devices, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC/enhanced MTC (eMTC, also referred to as CAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. The UE <NUM> may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

In an example, scheduling component <NUM> can configure resources for performing random access procedure with a base station <NUM> and/or performing FD communications by the base station <NUM> and/or one or more UEs <NUM>. Scheduling component <NUM> may configure one or more parameters for determining whether FD communications are scheduled during random access resources. In an example, communicating component <NUM> can perform a random access procedure based on a determination of whether resources for the random access procedure are configured for FD communications. Communicating component <NUM> can determine whether the resources are configured for FD communications based on at least one of receiving a configuration indicating such, a RRC state, a service type of communications with a base station <NUM>, a signal quality or power received from the base station <NUM>, and/or the like. Communicating component <NUM> may accordingly modify a random access message based on the determination (e.g., modify one or more parameters, such as a transmit power, power ramping step, random access format or configuration, etc.).

Turning now to <FIG>, aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional. Although the operations described below in <FIG> are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation. Moreover, it should be understood that the following actions, functions, and/or described components may be performed by a specially-programmed processor, a processor executing specially-programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions.

Referring to <FIG>, one example of an implementation of UE <NUM> may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and/or communicating component <NUM> for performing random access procedures based on a determination of whether FD communications are configured over random access resources, as described herein.

In an aspect, the one or more processors <NUM> can include a modem <NUM> and/or can be part of the modem <NUM> that uses one or more modem processors. Thus, the various functions related to communicating component <NUM> may be included in modem <NUM> and/or processors <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver <NUM>. In other aspects, some of the features of the one or more processors <NUM> and/or modem <NUM> associated with communicating component <NUM> may be performed by transceiver <NUM>.

Also, memory <NUM> may be configured to store data used herein and/or local versions of applications <NUM> or communicating component <NUM> and/or one or more of its subcomponents being executed by at least one processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or at least one processor <NUM>, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining communicating component <NUM> and/or one or more of its subcomponents, and/or data associated therewith, when UE <NUM> is operating at least one processor <NUM> to execute communicating component <NUM> and/or one or more of its subcomponents.

In an aspect, communicating component <NUM> can optionally include a FD determining component <NUM> for determining whether FD communications are configured over a set of resources related to a random access procedure, and/or a random access initiating component <NUM> for communicating one or more messages of a random access procedure (or other messages) based on whether FD communications are configured over the set of resources, as described herein.

Referring to <FIG>, one example of an implementation of base station <NUM> (e.g., a base station <NUM> and/or gNB <NUM>, as described above) may include a variety of components, some of which have already been described above, but including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and scheduling component <NUM> for configuring FD communications and/or resources for performing random access procedures, as described herein.

In an aspect, scheduling component <NUM> can optionally include a FD configuring component <NUM> for configuring FD communications by the base station <NUM> or one or more UEs <NUM> over certain resources, and/or a random access communicating component <NUM> for communicating one or more messages in a random access procedure based on whether FD communications are configured over the random access resources.

<FIG> illustrates a flow chart of an example of a method <NUM> for performing a random access procedure based on determining whether resources are configured for FD communications. In an example, a UE <NUM> can perform the functions described in method <NUM> using one or more of the components described in <FIG> and <FIG>.

In method <NUM>, optionally at Block <NUM>, it can be determined to perform a random access procedure with an access point. In an aspect, random access initiating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine to perform a random access procedure with an access point (e.g., base station <NUM>). For example, random access initiating component <NUM> can determine to perform the random access procedure based on determining one or more scenarios configured to trigger the random access procedure. For example, as described, random access initiating component <NUM> can determine to perform the random access procedure based on determining to establish a connection with the access point as an initial access attempt, based on determining to transition from one RRC state to another (e.g., from RRC IDLE or RRC INACTIVE to RRC CONNECTED) with the access point, based on determining to handover to a target cell and accordingly perform the random access procedure with the target cell, based on determining to transmit small uplink data to the access point via a random access procedure (e.g., via the PUSCH payload of the random access procedure) without necessarily switching RRC state, based on determining to perform beam failure recovery after detecting failure to receive one or more beams from the access point, etc..

In addition, for example, in determining to perform the random access procedure, random access initiating component <NUM> can determine resources over which to communicate (e.g., transmit or receive) one or more messages of the random access procedure. For example, random access initiating component <NUM> can determine a random access occasion configured (e.g., by the access point) for transmitting a random access preamble to initiate the random access procedure, and can determine the time and frequency resources corresponding to the random access occasion. The resources can include time and frequency resources, such as a symbol (e.g., orthogonal frequency division multiplexing (OFDM) symbol) to use to transmit the random access preamble, a component carrier (CC) or frequency band to use to transmit the random access preamble, etc. In an example, a configuration received from the access point may indicate one or more of the time resources (e.g., the symbol) or the frequency resources (e.g., the CC) for the random access occasion and/or one or more of the time resources or frequency resources may be determined from other configurations. In addition, determining to perform the random access procedure may also include determining resources over which to possibly retransmit the random access preamble, resources over which to transmit another random access message, such as a payload message, resources over which to receive one or more random access messages, such as a RAR, contention resolution message, etc., and/or the like, as described further herein.

In method <NUM>, at Block <NUM>, it can be determined whether FD communications are configured during resources for communicating one or more messages of the random access procedure. In an aspect, FD determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine whether FD communications are configured during resources for communicating the one or more messages of the random access procedure. For example, FD determining component <NUM> can determine whether FD communications are configured for the UE <NUM> or the access point (e.g., base station <NUM>) during resources for the random access procedure, which can include a determination of whether IBFD or sub-band FD communications are configured with full or partial overlap of the random access resources. In addition, for example, FD determining component <NUM> can determine whether FD communications are configured during one or more of resources for transmitting a random access preamble, resources for receiving a RAR, resources for transmitting a payload, etc. during the random access procedure.

For example, it may be possible that the access point configures FD communications during resources for random access procedures or the access point may avoid configuring FD communications during resources for random access procedures. In another example, whether FD communications are or can be configured during resources for random access procedure may depend on an RRC state of the UE <NUM>, a service type of communications between the UE <NUM> and the access point, and/or the like, as described further herein.

In method <NUM>, at Block <NUM>, responsive to the determining whether the FD communications are configured during the resources, the one or more messages can be transmitted using/over the resources. In an aspect, random access initiating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can transmit, over the resources and responsive to the determining whether the FD communications are configured during the resources, the one or more messages. In one example, if FD communications are configured during the resources, the one or more messages are transmitted using the resources, and the transmission of the one or more messages can be modified as described further herein to account for possible self-interference (at the UE <NUM> or the base station <NUM>) that may be caused due to the FD communications. The transmissions can further be based on determining to perform the random access procedure. This can include determining an initial transmit power, a power-ramping step, a random access format or configuration, or other parameters based on whether FD communications are configured over the random access resources.

In method <NUM>, optionally at Block <NUM>, one or more parameters for transmitting the one or more messages can be determined based on determining whether FD communications are configured during the resources. In an aspect, random access initiating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine, determine, based on determining whether FD communications are configured during the resources, one or more parameters (or parameter values) for transmitting the one or more messages. For example, the parameter(s) and/or related values can be different based on whether the one or more messages are to be transmitted in resources over which FD communications are configured or resources over which FD communications are not configured. Moreover, in an example, the parameter(s) and/or related values can be different based on a RRC state, a service type, or the scenario causing the RACH procedure (e.g., whether the RACH procedure is for initial access, RRC state transition, handover to a target cell, small uplink data transmission in RRC IDLE/INACTIVE, beam failure recovery, etc. Thus, in an example, random access initiating component <NUM> can determine the different parameter(s) and/or related values based on determining the scenario causing the RACH procedure. The one or more parameters or values may relate to transmit power for transmitting the one or more messages, a format or configuration for transmitting the one or more messages, etc., as described herein.

In determining the one or more parameters at Block <NUM>, optionally at Block <NUM>, an initial transmit power or a power ramping step for the one or more messages can be determined based on determining whether FD communications are configured during the resources. In an aspect, random access initiating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine, based on determining whether FD communications are configured during the resources, the initial transmit power or the power ramping step for the one or more messages. For example, where it is determined the FD communications are configured during the resources, random access initiating component <NUM> can adjust an initial transmit power and/or a power ramping step for a random access preamble (e.g., also referred to as a PRACH). For example, the power ramping step can refer to an increase in transmit power between consecutively transmitted random access preambles where multiple random access preambles are transmitted, each with an increased transmit power. For example, the initial power and/or power ramping step can be initially configured at the UE <NUM> by a configuration received from the access point or parameters otherwise stored in memory <NUM> of the UE <NUM>. In a specific example, where it is determined the FD communications are configured during the resources, random access initiating component <NUM> can increase the initial transmit power and/or power ramping step to compensate for possible self-interference cancellation efficiency than where it is determined that FD communications are not configured during the resources. In an example, UE <NUM> can receive a configuration from the access point that indicates an amount to increase the initial transmit power or the power ramping step in either case (and/or based on the scenario causing the RACH procedure) and/or parameters for determining an amount to increase the initial transmit power or the power ramping step in either case (and/or based on the scenario causing the RACH procedure).

In another example, in determining the one or more parameters at Block <NUM>, optionally at Block <NUM>, a random access format or a random access configuration for transmitting the one or more messages can be determined. In an aspect, random access initiating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine a random access format or random access configuration for transmitting the one or more messages. As described, for example, random access initiating component <NUM> can determine the random access format or configuration based on determining whether FD communications are configured during the resources. For example, to support FD in OFDM symbols overlapping with ROs, a different PRACH format and/or configuration (e.g., a newly defined PRACH format and/or configuration) can be used when FD communications are configured to fit new uplink and/or downlink configurations in FD. RO configuration (e.g., as received from the access point) for FD case may be different from RO configuration for non-FD case. ROs for FD can be a subset of ROs currently defined in LTE and/or NR. PRACH parameter (e.g., PRACH format, PRACH configuration) for FD can be different from PRACH parameter for non-FD.

For example, a first PRACH format can be used where FD communications are configured, while a second PRACH format can be used where FD communications are not configured during random access resources. The first and second PRACH formats can be different. For example, in one PRACH format (e.g., a "long PRACH format"), more symbols can be used to transmit PRACH (e.g., where FD communications are configured), whereas in another PRACH format (e.g., a "short PRACH format"), less symbols can be used to transmit PRACH (e.g., where FD communications are not configured). In any case, for example, random access initiating component <NUM> can determine the random access configuration and/or format to use based on determining whether FD communications are configured during the random access resources. In an example, UE <NUM> can receive a configuration from the access point that indicates the random access configuration and/or format to use in either case (and/or based on the scenario causing the RACH procedure) and/or parameters for determining the random access configuration and/or format to use in either case (and/or based on the scenario causing the RACH procedure).

In method <NUM>, optionally at Block <NUM>, a configuration indicating whether FD communications are configured during the random access procedure can be received. In an aspect, FD determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can receive the configuration indicating whether FD communications are configured during the random access procedure. For example, FD determining component <NUM> can receive the configuration from the access point (e.g., base station <NUM>) in system information (SI) or other broadcast signaling, RRC signaling, etc. For example, the configuration can indicate whether FD is configured at the access point in OFDM symbols overlapping random access occasions (ROs) or not. As such, for example, random access initiating component <NUM> can determine whether to adjust an initial transmit power or power ramping step, use a different random access format or configuration, etc. or take additional action based on whether the configuration indicates FD communications are configured during the random access resources.

In method <NUM>, in determining whether FD communications are configured during the resources at Block <NUM>, optionally at Block <NUM>, a RRC state or service type of communications with the access point can be determined. In an aspect, FD determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine the RRC state or service type of communications with the access point, and/or can determine whether FD communications are configured based at least in part on the RRC state or service type. In this example, whether FD is configured at the access point in OFDM symbols overlapping with ROs or not can depend on the RRC states or service types. In one example, service types can include a first service type, such as enhanced mobile broadband (eMBB), a second service type that may have additional or more restrictive latency or reliability requirements (e.g., lower latency and/or higher reliability) than the first service type, such as ultra-reliable low latency communications (URLLC), etc. In an example, each of one or more service types may or may not allow FD communications to be configured in random access resources.

For example, FD determining component <NUM> can determine whether an RRC state is RRC IDLE or INACTIVE, RRC CONNECTED, etc., and can determine whether FD communications are configured based on the RRC state. In a specific example, FD determining component <NUM> can determine that FD may be configured for initial access RACH (e.g., for transitioning from RRC IDLE or INACTIVE to RRC CONNECTED), or not configured for RACH when in an RRC CONNECTED state (e.g., for handover or out-of-sync recovery due to uplink timing loss). More generally, in an example, FD determining component <NUM> can determine that FD communications may be configured during random access resources where the UE <NUM> is operating in a RRC IDLE or INACTIVE state and/or can determine that FD communications are not configured during random access resources where the UE <NUM> is operating in an RRC CONNECTED state. In another example, FD determining component <NUM> can determine whether a service type is eMBB or URLLC (or other service types) and can determine whether FD communications are configured based on the service type. For example, for RACH to a target cell during handover, FD determining component <NUM> can determine that FD may be configured for eMBB, or not configured for URLLC.

In method <NUM>, in determining whether FD communications are configured during the resources at Block <NUM>, optionally at Block <NUM>, a signal measurement of one or more signals received from the access point can be determined. In an aspect, FD determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine a signal measurement of one or more signals received from the access point. For example, FD determining component <NUM> can determine the signal measurement, such as a reference signal received power (RSRP), path loss measurement, etc. of a signal from the access point, and can determine whether FD communications are configured during random access resources based on comparing the signal measurement to one or more thresholds. This may be useful for transmit power prioritization with respect to FD versus non-FD. This may also be applicable to RACH or other channels. In addition, in an example, the access point may configure parameters (e.g., in the configuration received from the access point described in Block <NUM>) indicating a relationship between the signal measurement and an assumption that FD is configured over resources.

In method <NUM>, in determining whether FD communications are configured during the resources at Block <NUM>, optionally at Block <NUM>, it can be determined whether FD communications are configured during shared channel resources for at least one of transmitting or retransmitting a shared channel. In an aspect, FD determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine whether FD communications are configured during shared channel resources for at least one of transmitting or retransmitting the shared channel. For example, in a four-step random access procedure, this determination and/or the shared channel resources can correspond to MSG3 transmitted after the random access preamble (e.g., MSG1). In a two-step random access procedure, this determination can correspond to transmitting at least a payload portion of MSG-A.

For example, it may be possible that the access point does not configure FD communications during resources for an initial shared channel (e.g., PUSCH) transmission or for shared channel retransmission. For example, the resources for initial shared channel transmission may be specified in the RAR and resources for shared channel retransmission may be specified in downlink control information (DCI) (e.g., DCI format 0_0 scrambled by TC-RNTI). In another example, it may be possible that the access point configures FD communications during resources for an initial shared channel (e.g., PUSCH) transmission but does not configure FD communications during resources for shared channel retransmission to provide higher protection for retransmission. Thus, in an example, FD determining component <NUM> can determine whether FD communications are configured based on determining whether the resources correspond to an initial shared channel transmission or a retransmission.

In yet another example, as described above, whether FD is configured for shared channel transmission in the random access procedure may also be based on RRC state and/or service type. Thus, in a specific example, FD may be configured for initial access RACH (e.g., RRC IDLE or INACTIVE to RRC CONNECTED), but not configured for RACH in RRC CONNECTED, and FD determining component <NUM> can determine whether FD communications are configured in the resources based on such. In addition, in a specific example, for RACH to target cell during handover, FD maybe configured for one service type (e.g., eMBB) but not configured for another service type (e.g., URLLC), and FD determining component <NUM> can determine whether FD communications are configured in the resources based on the service type.

In method <NUM>, optionally at Block <NUM>, response resources during which a response to the one or more messages is received from the access point can be determined. In an aspect, random access initiating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine the response resources during which a response to the one or more messages is received from the access point. For example, random access initiating component <NUM> can determine the response resources based on the random access configuration or indication of ROs, a determined period of time after which the random access preamble is transmitted, resources after transmitting the random access preamble until the response is received, etc. The response may include the RAR (e.g., MSG2), contention resolution message (e.g., MSG4), MSG-B in a two-step random access procedure, etc..

For example, for handover scenario in which UE can perform a RACH procedure to a target cell while sending PUCCH/PUSCH to source cell, if UE receives MSG2 or MSG4 (e.g., MSG-B) PDCCH/PDSCH from target cell, PUCCH/PUSCH transmission in FD during MSG2 or MSG4 (e.g., MSG-B) reception might have impact on PDCCH/PDSCH performance. Furthermore, coverage of broadcast channels may be limited due to wide beam (compared to narrow beam for unicast channels).

In method <NUM>, optionally at Block <NUM>, transmitting can be refrained from or can occur with reduced transmit power over the response resources. In an aspect, random access initiating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can refrain from transmitting or transmit with reduced transmit power (e.g., to the access point or other devices) over the response resources, such to mitigate interference to the response where FD communications are configured at the UE <NUM>. In one example, for symbols in which FD UE receives MSG2 or MSG4 (e.g., MSG-B) PDCCH/PDSCH in RRC CONNECTED, UE may not expect to be configured with uplink transmission. As such, for example, if uplink transmission is scheduled, random access initiating component <NUM> can refrain from transmitting uplink communications over the scheduled resources. In another example, the UE may transmit configured uplink communications at reduced transmission power, as described. In one example, the transmit power reduction can be configured to UE (e.g., by the access point) or determined by the UE in a configuration or hardcoded in memory (e.g., memory <NUM>) based on a radio access technology specification or standard, etc..

<FIG> illustrates a flow chart of an example of a method <NUM> for configuring or refraining from configuring FD communications over random access resources. In an example, a base station <NUM> can perform the functions described in method <NUM> using one or more of the components described in <FIG> and <FIG>.

In method <NUM>, at Block <NUM>, it can be determined whether to configure FD communications during resources for communicating one or more messages of a random access procedure. In an aspect, FD configuring component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, scheduling component <NUM>, etc., can determine whether to configure FD communications during resources for communicating one or more messages or the random access procedure, For example, scheduling component <NUM> can configure resources for UEs to use in performing a random access procedure with base station <NUM>. The configured random access resources can indicate ROs, random access preambles, etc. for the UEs to use in performing the random access procedure. Allowing FD communications during random access resources may have an impact on random access communications from UEs, and thus the base station <NUM> can determine whether to configure FD communications or not, and/or can indicate whether FD communications are configured during random access resources (e.g., where the FD communications may fully or partially overlap the random access resources in time as IBFD, sub-band FD, etc.).

For example, FD configuring component <NUM> can determine to not configure FD in OFDM symbols overlapping with ROs configured for one or more UEs, which can at least improve communications for cell-edge UEs. In another example, FD configuring component <NUM> can determine to configure FD in OFDM symbols overlapping with ROs configured for one or more UEs. In an example, whether to configure FD in OFDM symbols overlapping with ROs may be dependent on a network implementation.

In another example, in method <NUM>, optionally at Block <NUM>, a configuration indicating whether FD communications are configured during the random access procedure can be transmitted. In an aspect, FD configuring component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, scheduling component <NUM>, etc., can transmit the configuration (e.g., to one or more UEs, as described) indicating whether FD communications are configured during the random access procedure. In an example, FD configuring component <NUM> can transmit the configuration in SI broadcast signaling, RRC signaling, etc. In this example, as described, a UE <NUM> can receive the configuration and can adjust random access communication parameters (e.g., initial transmit power or power ramping step, random access format or configuration, etc.) based on an indication in the configuration as to whether FD communications are configured over the random access resources. According to the claimed invention, a method for wireless communication, comprises: receiving an indication indicating whether FD communications are configured during resources for communicating one or more messages of a random access procedure, the FD communications comprising uplink communications and downlink communications occurring in a same frequency band or in a same component carrier; and where the indication indicates that the FD communications are configured during the resources, transmitting the one or more messages of the random access procedure, including a random access preamble, using the resources and using at least one of an initial transmit power and a power ramping step that is, in each case, based on the indication. In another example, the configuration may include parameters for determining whether FD communications are configured over random access resources, such as a threshold of a signal measurement of signals received from an access point (e.g., RSRP, path loss measurement, etc.) that can indicate FD communications are configured in the random access resources. In another example, the configuration may include the random access communication parameter values, parameters for determining the values, and/or the like.

In yet another example, in determining whether the configure FD communications during the resources at Block <NUM>, optionally at Block <NUM>, an RRC state or service type of communications with the UE can be determined. In an aspect, FD configuring component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, scheduling component <NUM>, etc., can determine the RRC state or service type of the communications with the UE (e.g., UE <NUM>). , and can determine whether to configure the FD communications in the resources based on the RRC state or service type. As described, in a specific example, FD may be configured for initial access RACH (e.g., RRC IDLE or INACTIVE to RRC CONNECTED), but not configured for RACH in RRC CONNECTED, and FD configuring component <NUM> can configure FD communications, or not, in the resources based on such. More generally, in an example, FD configuring component <NUM> can configure FD communications during random access resources where the UE <NUM> is operating in a RRC IDLE or INACTIVE state and/or can refrain from configuring FD communications during random access resources where the UE <NUM> is operating in an RRC CONNECTED state. In addition, in a specific example, for RACH to target cell during handover, FD maybe configured for a first service type (e.g., eMBB) but not configured for another service type (e.g., URLLC or other service type with more restrictive latency and/or reliability requirements), and FD configuring component <NUM> can determine to configure FD communications, or not, in the resources based on the service type.

In yet another example, in determining whether to configure FD communications during the resources at Block <NUM>, optionally at Block <NUM>, it can be determined whether to configure FD communications during shared channel resources for at least one of transmitting or retransmitting a shared channel. In an aspect, FD configuring component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, scheduling component <NUM>, etc., can determine whether to configure FD communications during shared channel resources for at least one of transmitting or retransmitting the shared channel. For example, as described, FD configuring component <NUM> can determine not to configure FD communications for initial transmission and retransmissions of the shared channel (e.g., PUSCH). In another example, as described, FD configuring component <NUM> can determine not to configure FD communications for retransmissions of the shared channel but may configure FD communications over resources for initial transmission of the shared channel. In yet another example, as described, whether or not to configure FD communications over the resources for shared channel transmission/retransmission may be based on an RRC state or service type of communications with the UE.

In method <NUM>, optionally at Block <NUM>, a random access format or a random access configuration for communicating the one or more messages can be determined. In an aspect, random access communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, scheduling component <NUM>, etc., can determine the random access format or the random access configuration for communicating the one or more messages. In an example, as described above, the determination of the random access format or configuration can also be based on whether FD communications are configured during the random access resources. In addition, as described above, the PRACH format/configuration may include a new format/configuration to fit new uplink/downlink configuration in FD. In addition, for example, the RO configuration for FD can be different than for non-FD and/or a PRACH parameter can be different FD than for non-FD (e.g., long PRACH format or more symbols for PRACH in FD than for PRACH in non-FD).

In method <NUM>, at Block <NUM>, at least one of the one or more messages can be communicated over the resources and responsive to the determining whether to configure FD communications during the resources. In an aspect, random access communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, scheduling component <NUM>, etc., can communicate, over the resources and responsive to the determining whether to configure FD communications during the resources, at least one of the one or more messages. For example, random access communicating component <NUM> can communicate the one or more messages, which can include receiving a random access preamble transmitted based on whether FD communications are configured during the resources, as described, receiving a shared channel transmission and/or retransmission based on whether FD communications are configured during the resources, transmitting a RAR and/or contention resolution message based on whether FD communications are configured during the resources, and/or the like. In one example, communicating the one or more messages can be based on the determined random access format and/or configuration determined in Block <NUM>. In another example, communicating the one or more messages can be with a selected transmit power or power ramping step, etc..

In yet another example, for initial access UEs, based on PRACH reception, random access communicating component <NUM> can determine to group UEs for interference mitigation. For example, random access communicating component <NUM> can adjust synchronization signal block (SSB) transmission so that the intended UE gets better SSB to PRACH association for communicating the one or more signals (e.g., PRACH preamble transmission, PUSCH transmission, MSG2 or MSG4 reception, etc.), at least where FD communications are configured during the random access resources.

<FIG> is a block diagram of a MIMO communication system <NUM> including a base station <NUM> and a UE <NUM>, in accordance with various aspects of the present disclosure. The MIMO communication system <NUM> may illustrate aspects of the wireless communication access network <NUM> described with reference to <FIG>. The base station <NUM> may be an example of aspects of the base station <NUM> described with reference to <FIG>. The base station <NUM> may be equipped with antennas <NUM> and <NUM>, and the UE <NUM> may be equipped with antennas <NUM> and <NUM>. In the MIMO communication system <NUM>, the base station <NUM> may be able to send data over multiple communication links at the same time. Each communication link may be called a "layer" and the "rank" of the communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station <NUM> transmits two "layers," the rank of the communication link between the base station <NUM> and the UE <NUM> is two.

The UE <NUM> may be an example of aspects of the UEs <NUM> described with reference to <FIG>. At the UE <NUM>, the UE antennas <NUM> and <NUM> may receive the DL signals from the base station <NUM> and may provide the received signals to the modulator/demodulators <NUM> and <NUM>, respectively. Each modulator/demodulator <NUM> through <NUM> may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator/demodulator <NUM> through <NUM> may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector <NUM> may obtain received symbols from the modulator/demodulators <NUM> and <NUM>, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive (Rx) processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE <NUM> to a data output, and provide decoded control information to a processor <NUM>, or memory <NUM>.

The processor <NUM> may in some cases execute stored instructions to instantiate a communicating component <NUM> (see e.g., <FIG> and <FIG>).

The processor <NUM> may in some cases execute stored instructions to instantiate a scheduling component <NUM> (see e.g., <FIG> and <FIG>).

The functions described herein may be implemented in hardware, software, or any combination thereof. For example, due to the nature of software, functions described above can be implemented using software executed by a specially programmed processor, hardware, hardwiring, or combinations of any of these. " That is, unless specified otherwise, or clear from the context, the phrase, for example, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, for example the phrase "X employs A or B" is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B. Also, as used herein, including in the claims, "or" as used in a list of items prefaced by "at least one of" indicates a disjunctive list such that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (A and B and C).

Claim 1:
A method for wireless communication, comprising:
receiving (<NUM>, <NUM>) an indication indicating whether full duplex, FD, communications are configured during resources for communicating one or more messages of a random access procedure, the FD communications comprising uplink communications and downlink communications occurring in a same frequency band or in a same component carrier; and
where the indication indicates that the FD communications are configured during the resources, transmitting (<NUM>, <NUM>) the one or more messages of the random access procedure, including a random access preamble, using the resources and using at least one of an initial transmit power and a power ramping step that is, in each case, based on the indication.