Random access channel configuration for full-duplex communication

Abstract

Methods, systems, and devices for wireless communication are described that provide random access occasions (ROs) in full-duplex slots in addition to providing ROs in non-full-duplex time division duplex (TDD) slots. Additional ROs can be provided for full-duplex slots based on TDD slots configured in a physical random access channel (PRACH) configuration. A user equipment (UE) can identify a configured TDD PRACH slot within a subset of non-full-duplex slots configured with ROs and identify a full-duplex slot with additional ROs relative to the configured TDD PRACH slot based on a time offset, a frequency offset, or both. The UE can transmit one or more random access messages using one or more of the additional ROs in the full-duplex slot.

Description

Cross-referencing

[0001] This patent application claims priority to U.S. Patent Application No. 19 / 094,644, filed March 28, 2025, entitled “RANDOM ACCESS CHANNEL CONFIGURATION FOR FULL DUPLEX COMMUNICATIONS,” and U.S. Provisional Patent Application No. 63 / 575,226, filed April 5, 2024, entitled “RANDOM ACCESS CHANNEL CONFIGURATION FOR FULL DUPLEX COMMUNICATIONS,” each of which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following text relates to wireless communication, including random access channel configurations for full-duplex communication. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting random access channel configuration for full-duplex communication. For example, the described technology provides ROs in full-duplex time-division duplex (TDD) time slots in addition to providing ROs in non-full-duplex time-division duplex (TDD) time slots. In some aspects, additional ROs can be provided for full-duplex time slots based on TDD time slots configured in a physical random access channel (PRACH) configuration. In some cases, user equipment (UE) can identify configured TDD PRACH time slots within a subset of non-full-duplex time slots with configured ROs, and identify full-duplex time slots with additional ROs relative to the configured TDD PRACH time slots based on time offset, frequency offset, or both. The UE can use one or more additional ROs from the additional ROs in the full-duplex time slots to transmit one or more random access messages.

[0005] A method for wireless communication by a UE is described. The method may include: receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set of non-full-duplex time slots including resources for one or more random access opportunities; receiving a second signal indicating a full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the set of non-full-duplex time slots; and transmitting a random access message in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time resources and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0006] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: receive a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set of non-full-duplex time slots including resources for one or more random access opportunities; receive a second signal indicating a full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the set of full-duplex time slots do not overlap with time slots in the set of non-full-duplex time slots; and transmit a random access message in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time resources and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0007] Another UE for wireless communication is described. The UE may include: means for receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set of non-full-duplex time slots including resources for one or more random access opportunities; means for receiving a second signal indicating a full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the set of non-full-duplex time slots; and means for transmitting a random access message in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set of non-full-duplex time slots including resources for one or more random access opportunities; receive a second signal indicating a full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the set of non-full-duplex time slots; and transmit a random access message in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0009] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, a second full-duplex time slot subset within a full-duplex time slot set is identified based on a time offset from one or more time slots in a first non-full-duplex time slot subset, the second full-duplex time slot subset including one or more random access opportunities that can be used to send random access messages.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the second full-duplex time slot subset is identified based on a mapping from the first non-full-duplex time slot subset, wherein the mapping provides a one-to-one mapping between each time slot in the first non-full-duplex time slot subset and each time slot in the second full-duplex time slot subset, or the mapping provides a one-to-many mapping between a second time slot in the first non-full-duplex time slot subset and two or more time slots in the second full-duplex time slot subset.

[0011] The methods, UEs, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining the location of a first full-duplex time slot based on a time offset from a non-full-duplex time slot in a first subset of non-full-duplex time slots, wherein the time offset includes a non-full-duplex time slot or begins from a subsequent time slot of a non-full-duplex time slot. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the set of full-duplex time slots includes at least two full-duplex time slots mapped to the first non-full-duplex time slot in the first subset of non-full-duplex time slots.

[0012] The methods, UEs, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining the location of a first full-duplex time slot based on a time offset from a non-full-duplex time slot in a first subset of non-full-duplex time slots, wherein the time offset indicates the number of physical time slots relative to the non-full-duplex time slots or the number of available full-duplex time slots relative to a second non-full-duplex time slot. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the time offset indicates the number of positive or negative time slots relative to a second non-full-duplex time slot.

[0013] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for identifying one or more random access opportunities in a first full-duplex time slot based on a time offset from a random access channel opportunity in a first non-full-duplex time slot within a subset of first non-full-duplex time slots, wherein the first full-duplex time slot includes one or more random access opportunities, regardless of whether the first non-full-duplex time slot is a valid uplink time slot.

[0014] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for determining the location of one or more random access opportunities in a first full-duplex time slot based on a time offset from one or more random access opportunities in a first non-full-duplex time slot subset, wherein the time offset indicates the number of time slots or symbols relative to one or more random access opportunities in one or more non-full-duplex symbols in the first non-full-duplex time slot subset.

[0015] The methods, UEs, and some examples of non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying one or more random access opportunities for transmission of a random access channel in a first full-duplex time slot based solely on a time offset from a valid random access opportunity in a first non-full-duplex time slot subset. The methods, UEs, and some examples of non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the location of one or more random access opportunities in a first full-duplex time slot based on a time offset from one or more random access opportunities in a first non-full-duplex time slot subset, wherein the time offset indicates the number of time slots or symbols relative to one or more random access opportunities in one or more non-full-duplex symbols in the first non-full-duplex time slot subset.

[0016] The methods, UEs, and some examples of non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the location of a first full-duplex time slot based on a time offset of a non-full-duplex time slot within a subset of first non-full-duplex time slots, wherein the time offset is a defined offset value or is provided to the UE in a random access channel configuration. The methods, UEs, and some examples of non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the location of frequency resources for random access messages in a first full-duplex time slot based on a frequency offset associated with an uplink subband of the first full-duplex time slot, wherein the frequency offset corresponds to a first physical resource block of the uplink subband of the first full-duplex time slot, or the frequency offset is provided to the UE in a random access channel configuration.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, a first full-duplex time slot includes an uplink subband comprising frequency resources for at least two random access opportunities, wherein random access messages are transmitted using the frequency resources of one of the at least two random access opportunities, and wherein the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with a random access channel configuration associated with a set of non-full-duplex time slots, the at least two random access opportunities being frequency-division multiplexed within the uplink subband based on the bandwidth of the uplink subband, and the at least two random access opportunities being frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with a full-duplex configuration.

[0018] The methods, UEs, and some examples of non-transitory computer-readable media described herein may also include operations, features, components, or instructions for formatting a sequence of random access messages according to the same format indicated in the random access channel configuration or according to the format indicated in the full-duplex configuration. In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the number of full-duplex time slots configured to transmit random access messages in the full-duplex time slot set is signaled to the UE or determined based on the number of non-full-duplex time slots configured to transmit random access messages.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, when the same random access channel sequence is configured for full-duplex and non-full-duplex time slots, a first number of random access opportunities available for transmitting a random access message in a first full-duplex time slot is the same number, a subset thereof, or an integer multiple thereof, as a second number of random access opportunities available for transmitting a random access message in a first non-full-duplex time slot within a subset of the first non-full-duplex time slots.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, when different random access channel sequences are configured for full-duplex and non-full-duplex time slots, a first number of random access opportunities available for transmitting random access messages in a first full-duplex time slot is scaled relative to a second number of random access opportunities available for transmitting random access messages in a first non-full-duplex time slot subset.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, based on whether the same or different random access channel sequences are configured for full-duplex and non-full-duplex time slots, the duration of one or more random access opportunities within a first full-duplex time slot is the same duration or a different duration than the duration of one or more random access opportunities in a subset of first non-full-duplex time slots. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first full-duplex time slot includes time resources for two or more random access opportunities and frequency resources for two or more random access opportunities, wherein the time gap and frequency gap between consecutive random access opportunities are each zero unless configured to non-zero values. Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving mapping information indicating a correspondence between one or more random access opportunities within a first full-duplex time slot and one or more synchronization signal blocks, wherein the mapping information is provided separately from other mapping information associated with non-full-duplex time slots.

[0022] The methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving mapping information indicating a correspondence between one or more random access opportunities and one or more synchronization signal blocks, wherein the mapping information is applied to both full-duplex and non-full-duplex time slots. The methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a UE capability indication regarding the time and frequency resources of a random access message in a first full-duplex time slot based on a random access channel configuration associated with a set of non-full-duplex time slots.

[0023] A method for wireless communication by a network entity is described. The method may include: outputting to a UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set of non-full-duplex time slots including resources for one or more random access opportunities; outputting to the UE a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the set of non-full-duplex time slots; and obtaining a random access message from the UE in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time resources and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0024] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the network entity to: output a first signal to a UE indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set of non-full-duplex time slots including resources for one or more random access opportunities; output a second signal to the UE indicating a full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the set of full-duplex time slots do not overlap with time slots in the set of non-full-duplex time slots; and obtain a random access message from the UE in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time resources and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0025] Another network entity for wireless communication is described. This network entity may include: means for outputting to a UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set including resources for one or more random access opportunities; means for outputting to the UE a second signal indicating a full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set; and means for obtaining a random access message from the UE in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0026] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: output to a UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set of non-full-duplex time slots including resources for one or more random access opportunities; output to the UE a second signal indicating a full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the set of non-full-duplex time slots; and obtain a random access message from the UE in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a second full-duplex time slot subset within the full-duplex time slot set includes one or more random access opportunities that can be used to send random access messages, and wherein the second full-duplex time slot subset is determined based on a time offset from one or more time slots in the first non-full-duplex time slot subset.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second full-duplex time slot subset is identified based on a mapping from the first non-full-duplex time slot subset, wherein the mapping provides a one-to-one mapping between each time slot in the first non-full-duplex time slot subset and each time slot in the second full-duplex time slot subset, or the mapping provides a one-to-many mapping between a second time slot in the first non-full-duplex time slot subset and two or more time slots in the second full-duplex time slot subset.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the location of the first full-duplex time slot is determined based on a time offset from the non-full-duplex time slots in a subset of the first non-full-duplex time slots, wherein the time offset includes the non-full-duplex time slots or begins from a subsequent time slot of the second non-full-duplex time slot. In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the set of full-duplex time slots includes at least two full-duplex time slots mapped to the first non-full-duplex time slots in the subset of the first non-full-duplex time slots.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the location of the first full-duplex time slot is determined based on a time offset from the non-full-duplex time slots in a subset of the first non-full-duplex time slots, wherein the time offset indicates the number of physical time slots relative to the non-full-duplex time slots or the number of available full-duplex time slots relative to the second non-full-duplex time slots. In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the time offset indicates the number of positive or negative time slots relative to the second non-full-duplex time slots.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first full-duplex time slot includes one or more random access opportunities determined based on a time offset from a random access channel opportunity in a first non-full-duplex time slot within a subset of first non-full-duplex time slots, wherein the first full-duplex time slot includes one or more random access opportunities regardless of whether the first non-full-duplex time slot is a valid uplink time slot. In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first full-duplex time slot includes one or more random access opportunities for random access channel transmission, which are based solely on a time offset from a valid random access opportunity within a subset of first non-full-duplex time slots.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the location of one or more random access opportunities in a first full-duplex time slot is based on a time offset from one or more random access opportunities in a first non-full-duplex time slot subset, and wherein the time offset indicates the number of time slots or symbols relative to one or more random access opportunities in one or more non-full-duplex symbols in the first non-full-duplex time slot subset.

[0033] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the location of the first full-duplex time slot is determined based on a time offset from a non-full-duplex time slot within a subset of first non-full-duplex time slots, wherein this time offset is a defined offset value or is provided to the UE in the random access channel configuration. In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the location of the frequency resources for random access messages in the first full-duplex time slot is determined based on a frequency offset associated with an uplink subband of the first full-duplex time slot, wherein this frequency offset corresponds to a first physical resource block of the uplink subband of the first full-duplex time slot, or the frequency offset is provided to the UE in the random access channel configuration.

[0034] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first full-duplex time slot includes an uplink subband comprising frequency resources for at least two random access opportunities, wherein random access messages are transmitted using the frequency resources of one of the at least two random access opportunities, and wherein the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with a random access channel configuration associated with a set of non-full-duplex time slots, the at least two random access opportunities being frequency-division multiplexed within the uplink subband based on the bandwidth of the uplink subband, and the at least two random access opportunities being frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with a full-duplex configuration.

[0035] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the sequence of random access messages is formatted according to either the same format indicated in the random access channel configuration or the format indicated in the full-duplex configuration. In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the number of full-duplex time slots configured to transmit random access messages in the full-duplex time slot set is signaled to the UE or determined based on the number of non-full-duplex time slots configured to transmit random access messages.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, when the same random access channel sequence is configured for full-duplex and non-full-duplex time slots, a first number of random access opportunities available for transmitting a random access message in a first full-duplex time slot is the same number, a subset thereof, or an integer multiple thereof, as a second number of random access opportunities available for transmitting a random access message in a first non-full-duplex time slot within a subset of the first non-full-duplex time slots.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, when different random access channel sequences are configured for full-duplex and non-full-duplex time slots, a first number of random access opportunities available for transmitting random access messages in a first full-duplex time slot is scaled relative to a second number of random access opportunities available for transmitting random access messages in a first non-full-duplex time slot subset.

[0038] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the duration of one or more random access opportunities within a first full-duplex time slot is either the same duration or a different duration than the duration of one or more random access opportunities in a first subset of non-full-duplex time slots, depending on whether the same or different random access channel sequences are configured for full-duplex and non-full-duplex time slots.

[0039] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first full-duplex time slot includes time resources for two or more random access opportunities and frequency resources for two or more random access opportunities, wherein the time gap and frequency gap between consecutive random access opportunities are each zero unless configured to a non-zero value. Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: outputting mapping information indicating a correspondence between one or more random access opportunities and one or more synchronization blocks within the first full-duplex time slot, wherein this mapping information is provided separately from other mapping information associated with non-full-duplex time slots. Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: outputting mapping information indicating a correspondence between one or more random access opportunities and one or more synchronization blocks, wherein this mapping information is applied to both full-duplex and non-full-duplex time slots. Attached Figure Description

[0040] Figure 1 An example of a wireless communication system that supports random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown.

[0041] Figure 2 An example of a wireless communication system that supports random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown.

[0042] Figures 3 to 11 An example of a random access resource supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown.

[0043] Figure 12 An example of a process flow for configuring a random access channel for full-duplex communication, according to one or more aspects of this disclosure, is shown.

[0044] Figure 13 and Figure 14 A block diagram of an apparatus for supporting random access channel configuration for full-duplex communication is shown, according to one or more aspects of this disclosure.

[0045] Figure 15 A block diagram of a communication manager supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown.

[0046] Figure 16 A diagram is shown of a system including a device that supports random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure.

[0047] Figure 17 and Figure 18 A block diagram of an apparatus for supporting random access channel configuration for full-duplex communication is shown, according to one or more aspects of this disclosure.

[0048] Figure 19 A block diagram of a communication manager supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown.

[0049] Figure 20 A diagram is shown of a system including a device that supports random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure.

[0050] Figures 21 to 25 A flowchart illustrating a method for configuring a random access channel for full-duplex communication according to one or more aspects of this disclosure is shown. Detailed Implementation

[0051] In some wireless communication systems, full-duplex communication techniques can be implemented, where the same set of radio resources within a Time Division Duplex (TDD) radio frame is used for both uplink communication from a User Equipment (UE) to a network entity and downlink communication from a network entity to one or more UEs. In some deployments, Subband Full-Duplex (SBFD) can be used, where the set of frequency resources may include one or more non-overlapping uplink subbands and one or more downlink subbands. In other deployments, full-duplex communication techniques may include overlapping uplink and downlink frequency resources. Although the various examples discussed herein exemplify SBFD resources, the techniques provided herein can also be used for full-duplex communication where uplink and downlink communication use overlapping frequency resources in the same time period. In some cases, an SBFD configuration can provide a set of SBFD time slots within a TDD configuration, such that some time slots within a TDD radio frame are SBFD time slots, and the remaining time slots within the TDD radio frame are non-full-duplex time slots. In some cases, non-full-duplex time slots may also be referred to as legacy time slots.

[0052] To initiate communication between a UE and a network entity, the UE can use random access resources configured in one or more uplink slots to send random access messages. In some cases, a Physical Random Access Channel (PRACH) configuration (e.g., via Radio Resource Control (RRC) signaling) can be provided to the UE, identifying one or more uplink slots in a TDD radio frame that include one or more Random Access Opportunities (ROs). ROs may include time and frequency resources, where network entities can monitor random access messages from the UE. Existing techniques for PRACH configuration allow ROs to be configured only in non-full-duplex TDD slots. Depending on the various aspects discussed herein, ROs can also be provided in full-duplex slots, which can be used by full-duplex aware UEs (e.g., UEs supporting full-duplex signaling) to send random access messages. Compared to non-full-duplex ROs provided in PRACH configurations, such techniques can help improve the efficiency of wireless communication and reduce latency by allowing additional ROs in additional slots.

[0053] In some aspects, additional Returns of Interest (ROs) can be provided for full-duplex time slots, where the location of the additional ROs can be based on the TDD time slots configured in the PRACH configuration. In some cases, the UE can identify the configured TDD PRACH time slots within a subset of non-full-duplex time slots configured with ROs, and identify full-duplex time slots with additional ROs relative to the configured TDD PRACH time slots based on time offsets. In some cases, the association or mapping between ROs in TDD PRACH time slots and ROs in full-duplex time slots can be one-to-one or one-to-many, such that a TDD PRACH time slot can be associated with one or more full-duplex time slots with ROs. The time offset can be a default offset or can be configured (e.g., via RRC signaling). In some aspects, the time offset can be based on the configured TDD PRACH time slots, regardless of whether the time slot is a valid uplink time slot (e.g., when the PRACH is configured to provide ROs in a time slot, but that time slot is a downlink time slot in the current TDD configuration, such a time slot is a configured time slot, but not a valid time slot). Within each full-duplex time slot with a RO, one or more ROs may exist. The time offset may be symbol-based or time slot-based, and may begin from the TDD PRACH time slot or the next time slot following the TDD PRACH time slot. Additionally, in some aspects, the time offset may be positive or negative. The frequency offset of the RO frequency resources in the full-duplex subband may be implicit or configurable (e.g., via RRC signaling). Additionally or alternatively, the PRACH format and / or sequence for the full-duplex RO may be the same as or different from the TDD PRACH format and / or sequence.

[0054] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described by way of random access resource diagrams, process flow diagrams, apparatus diagrams, system diagrams, and flowcharts relating to random access channel configuration for full-duplex communication.

[0055] Figure 1 An example of a wireless communication system 100 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0056] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0057] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0058] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0059] In some examples, network entity 105 may communicate with core network 130, or with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0060] One or more of the network entities 105 or network equipment described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0061] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0062] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., RRC, Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both may host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0063] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include IAB mobile terminals (IAB-MTs) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. IAB-MTs may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0064] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0065] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or meters.

[0066] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0067] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a collection of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) and TDD component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0068] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of a modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., over the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0069] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0070] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0071] A subframe, time slot, micro-time slot, or symbol may be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and may be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0072] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a public search space set configured to transmit control information to UE115 (e.g., one or more UEs) or a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0073] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas such as coverage area 110. In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas such as coverage area 110 associated with different technologies may be supported by different network entities (e.g., network entity 105). Wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different RATs to support communication for coverage areas 110 (e.g., different coverage areas).

[0074] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0075] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0076] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0077] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0078] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0079] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0080] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or for some other orientation).

[0081] In some cases, UE 115 and network entity 105 can communicate using full-duplex communication, where the same set of radio resources can be used for both uplink and downlink communication. For example, a subset of subframes of a TDD frame can be configured as full-duplex subframes, such that the TDD frame includes both full-duplex and non-full-duplex time slots. In some cases, ROs can be configured in full-duplex time slots in addition to ROs in non-full-duplex time slots. In some cases, additional ROs can be provided for full-duplex time slots based on the TDD time slots configured in the PRACH configuration. In some cases, UE 115 can identify configured TDD PRACH time slots within a subset of non-full-duplex time slots with configured ROs, and identify full-duplex time slots with additional ROs relative to the configured TDD PRACH time slots based on time offset, frequency offset, or both. UE 115 can use one or more additional ROs in the full-duplex time slots to send one or more random access messages to network entity 105.

[0082] Figure 2 An example of a wireless communication system 200 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 can implement as referenced herein. Figure 1 The described wireless communication system 100 is implemented in or through these aspects. For example, the wireless communication system 200 may include a UE 115-a and a network entity 105-a, which may be as referenced herein. Figure 1 Examples of UE 115 and network entity 105 described. Wireless communication system 200 may support 3G, 4G, 5G or higher radio access technologies.

[0083] UE 115-a and network entity 105-a may perform wireless communication (e.g., receiving, acquiring, transmitting, or outputting one or more of control information, configuration information, or data) via communication link 205 (including uplink communication link 205-a and downlink communication link 205-b), which may be as referenced herein. Figure 1 An example of the described communication link 125. In some cases, the communication link 205 may include multiple component carriers. Figure 2 In the example, UE 115-a may be able to know the full-duplex operation of network entity 105-a. In such an example, UE 115-a may send a capability indication 210 to network entity 105-a indicating full-duplex capability. For example, capability indication 210 may indicate that UE 115-a can identify the time and frequency resources of random access messages in a full-duplex time slot based on the PRACH configuration associated with a non-full-duplex time slot.

[0084] In some respects, network entity 105-a may send PRACH configuration 215 to UE 115-a, wherein PRACH configuration 215 indicates a TDD subframe including RO. Figure 2 In the example, network entity 105-a may send SBFD configuration 220 to UE 115-a, which may identify a TDD subframe configured as an SBFD subframe. In some aspects, additional ROs may be provided for full-duplex slots configured in SBFD configuration 220, wherein the location of the additional ROs may be based on TDD slots configured in PRACH configuration 215. UE 115-a may use one or more additional ROs from the additional ROs to send RACH message 225. In some cases, UE 115-a may identify configured TDD PRACH slots within a subset of non-full-duplex slots configured with ROs, and identify full-duplex slots with additional ROs relative to the configured TDD PRACH slots based on time offsets. In some cases, the association or mapping between ROs in TDD PRACH slots and ROs in full-duplex slots may be one-to-one or one-to-many, such that a TDD PRACH slot may be associated with one or more full-duplex slots with ROs. The time offset can be a default offset or can be configured (e.g., via RRC signaling). In some respects, the time offset can be based on the configured TDD PRACH slot, regardless of whether the slot is a valid uplink slot (e.g., when PRACH is configured to provide RO in a slot, but that slot is a downlink slot in the current TDD configuration, such a slot is a configured slot, but not a valid slot). Within each full-duplex slot with RO, one or more ROs may exist. The time offset can be based on a symbol or slot and can begin from the next slot following the TDD PRACH slot or the TDD PRACH slot. Additionally, in some respects, the time offset can be a positive or negative offset. The frequency offset of the RO frequency resources in the full-duplex subband can be implicit (e.g., interpreted based on one or more other parameters) or can be configured (e.g., via RRC signaling). Additionally or alternatively, the PRACH format and / or sequence for full-duplex ROs can be the same as or different from the TDD PRACH format and / or sequence. In some cases, random access message duplication can be enabled across multiple ROs in a full-duplex time slot. Figures 3 to 11 Examples of full-duplex RO and RO locations based on TDPRACH configurations are provided according to various aspects of this disclosure.

[0085] Figure 3 An example of a random access resource 300 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the random access resource 300 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 300 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0086] In this example, TDD frame 305 may be configured with TDD settings. The TDD configuration may be indicated, for example, in system information broadcast by a network entity. TDD frame 305 comprises 10 subframes, each with two TDD slots, in this example (and in...). Figures 4 to 11 In other examples (in which case), a 30 kHz parameter set is assumed. The time slot may have a TDD time slot configuration 315, which indicates the time slot as downlink time slot 320, SBFD time slot 325, or uplink time slot 330. In this example, SBFD time slot 325 (e.g., the first SBFD time slot 325-a) is... Figure 3 The symbol “X” indicates this. In cases where a time slot is configured with both SBFD symbols and non-SBFD symbols, such an SBFD time slot 325 is indicated by “X’”. Within a TDD time slot configuration 315, one or more uplink PRACH time slots 330 may be configured with PRACH resources for one or more legacy UE ROs 340 according to the PRACH configuration. In this example, each legacy UE RO 340 may include four OFDM symbols 335, such that each configured uplink time slot 330 includes three ROs 340. Figure 3 In the example, the PRACH configuration allows the first uplink PRACH slot 330-a and the second uplink PRACH slot 330-b to be configured with corresponding ROs 340-a and 340-b. In some aspects, the PRACH configuration can be indicated to the UE via a PRACH configuration index value that indicates a resource configured with an RO within the TDD slot configuration 315. For example, the UE can be provided with an indication of PRACH configuration index 102 for TDD communication in FR1 with a 30kHz subcarrier spacing (SCS) for the initial random access message (e.g., MSG1). Table 1 provides an example of information regarding the indication of PRACH configuration index 102:

[0087] Table 1 As can be observed from this example PRACH configuration, subframes 2 310-a and 7 310-b are configured with legacy UE ROs 340, where the RO begins at the initial OFDM symbol 335 (e.g., OFDM symbol number 0) in the slot, there is one PRACH uplink slot 330 within the subframe, three time-domain legacy UE ROs 340 within each PRACH slot, and each RO has a duration of four OFDM symbols. It should be understood that this example of PRACH configuration index 102 is provided for discussion and illustrative purposes, and many different PRACH configurations may be used according to the techniques discussed herein.

[0088] It should be noted that PRACH configuration can be provided independently of TDD slot configuration, and in some cases, the PRACH configuration index can indicate the PRACH slot corresponding to the downlink slot based on the TDD slot configuration. In such cases, the PRACH configuration indicates the configured RO in the slot, but since the associated slot is not an uplink slot, this RO is invalid. A valid RO is the RO of the uplink slot for which TDD slot configuration 315 indicates the RO used for configuration, and an invalid RO is the RO of the downlink slot for which TDD slot configuration 315 indicates the RO used for configuration.

[0089] exist Figure 3 In the example, the SBFD configuration may instruct a subset of slots in the TDD slot configuration 315 to be configured as SBFD slots. In this example, the SBFD slot 325 configured by the SBFD configuration may include a second SBFD slot 325-b and a third SBFD slot 325-c. According to various aspects discussed herein, such SBFD slots 325 may include additional ROs 360 that can be used for random access message transmission by an SBFD-aware UE (e.g., a UE supporting SBFD signaling). For example, SBFD slot 325 may be configured with a downlink subband 350 and an uplink subband 355, wherein the uplink subband 355 may include three valid ROs 360, such that the second SBFD slot 325-b includes a first set of three valid ROs 360-a, and the third SBFD slot 325-c includes a second set of three valid ROs 360-b. The SBFD-aware UE can then use the valid ROs 360 to transmit random access messages. The time resource and frequency location of the SBFD effective RO 360 can be determined based on one or more time offsets, frequency offsets, or both. Figures 4 to 12Various examples of RO locations based on time offset, frequency offset, or both are illustrated according to the various aspects provided herein. One or more time offsets and / or frequency offsets may be indicated to the UE, for example, through RRC signaling of the UE in RRC connected state or in a broadcast message (e.g., SIB1), to enable SBFD random access for RRC idle / inactive UEs.

[0090] Figure 4 An example of a random access resource 400 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the random access resource 400 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 400 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0091] In this example, TDD frame 405 may be configured with a TDD configuration. The TDD configuration may be indicated, for example, in system information broadcast by a network entity. TDD frame 405 comprises 10 subframes, each with two time slots, including a first subframe 410-a and a second subframe 410-b configured with PRACH RO. The time slots may have a TDD time slot configuration 415, which indicates the time slot as either downlink time slot 420 or uplink time slot 430. In this example, one or more SBFD time slots 425 are configured, as shown in the reference. Figure 3 The terms under discussion are indicated by “X” or “X’”. Within TDD slot configuration 415, the first uplink slot 430-a and the second uplink slot 430-b may (e.g., according to PRACH configuration index 102) be configured with PRACH resources for one or more legacy UEROs.

[0092] In this example, the SBFD configuration may indicate that slot 425 is configured as an SBFD slot, and additional ROs within the SBFD slot may be identified based on a time offset 440 relative to the configured PRACH slot. For example, a first time offset 440-a may indicate a first SBFD PRACH slot set 435-a based on a first PRACH uplink slot 430-a configured by the PRACH configuration, and a second time offset 440-b may indicate a second SBFD PRACH slot set 435-b based on a second PRACH uplink slot 430-b configured by the PRACH configuration. Thus, in some aspects, one or more additional SBFD PRACH slots 435 are associated with a TDD PRACH slot 430 configured in the PRACH configuration. The UE may first identify the configured PRACH slot in a non-full-duplex symbol, and then may identify the SBFD PRACH slot 435 relative to the TDD PRACH slot 430 based on the time offset 440. The association or mapping between TDD PRACH slot 430 and SBFD PRACH slot 435 can be a one-to-one mapping or a one-to-many mapping, such that each TDD PRACH slot 430 can be associated with one or more SBFD PRACH slots 435.

[0093] Figure 5 An example of a random access resource 500 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the random access resource 500 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 500 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0094] exist Figure 5In this example, the TDD slot configuration 505 may include downlink slots and uplink slots. Additionally, some downlink slots or flexible slots may be configured as SBFD slots. In this example, the PRACH configuration may configure two TDD PRACH slots 510, and the SBFD PRACH slot 515 may be determined based on a time offset 520 from the TDD PRACH slot 510. In this example, a first instance of time offset 520-a may indicate a first SBFD PRACH slot 515-a, and a second instance of time offset 520-b may indicate a second SBFD PRACH slot 515-b. Each SBFD PRACH slot 515 may include a downlink subband 525 and an uplink subband 530 including two ROs (but more or fewer ROs may also exist). Therefore, in this example, based on time offset 520, an additional SBFD PRACH slot 515 is associated with the TDD PRACH slot 510. In some respects, time offset 520 may begin from the first symbol in TDD PRACH slot 510 (counting PRACH slots), or it may begin from the next symbol after the TDD PRACH slot (not counting PRACH slots).

[0095] Figure 6 An example of a random access resource 600 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the random access resource 600 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 600 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0096] exist Figure 6In this example, the TDD timeslot configuration 605 may include downlink timeslots, flexible timeslots, and uplink timeslots, wherein flexible timeslots and / or downlink timeslots may be configured as SBFD timeslots. In this example, the PRACH configuration may configure a TDD PRACH timeslot 610, and the SBFD PRACH timeslot 615 may be determined based on a time offset 620 from the TDD PRACH timeslot 610. In this example, the two-to-one mapping between the TDD PRACH timeslot 610 and the SBFD PRACH timeslot 615 may indicate a first SBFD PRACH timeslot 615-a and a second SBFD PRACH timeslot 615-b. Each SBFD PRACH timeslot 615 may include a downlink subband 625 and an uplink subband 630 including two ROs (but more or fewer ROs may also exist).

[0097] Figure 7 An example of a random access resource 700 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the random access resource 700 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 700 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0098] exist Figure 7In this example, the TDD slot configuration 705 may include downlink slots, flexible slots, and uplink slots, wherein the downlink slots and / or flexible slots may be configured as SBFD slots, as discussed herein. In this example, the PRACH configuration may configure the TDD PRACH slot 710 to include ROs, including a first PRACH slot 715 and a second PRACH slot 720. However, in this example, the second PRACH slot 720 is configured as a downlink slot. Therefore, in this example, the ROs in the first PRACH slot 715 (i.e., RO #0 and RO #1) are valid, and the ROs in the second PRACH slot 720 (i.e., RO #2 and RO #3) are invalid. In some aspects, the SBFD ROs in the first SBFD slot 725 and the second SBFD slot 730 are determined based on the configured TDD ROs, regardless of whether the associated ROs are valid. Therefore, in this example, a first time offset 735 with respect to the first RO in the first PRACH slot 715 can be used to identify the RO in the first SBFD slot 725 (i.e., SBFD RO #0 and #1), and a second time offset 740 with respect to the RO in the second PRACH slot 720 can be used to identify the RO in the second SBFD slot 730 (i.e., SBFD RO #2 and #3).

[0099] Figure 8 An example of a random access resource 800 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the random access resource 800 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 800 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0100] exist Figure 8 In this example, the TDD slot configuration 805 may include downlink slots, flexible slots, and uplink slots, wherein the downlink slots or flexible slots may be configured as SBFD slots, as discussed herein. In this example, the PRACH configuration may configure the TDD PRACH slot 810 to include ROs, including a first PRACH slot 815 and a second PRACH slot 820. In this example, similar to the reference... Figure 7The second PRACH slot 820 is configured in the downlink slots. Therefore, in this example, the ROs (i.e., RO #0 and RO #1) in the first PRACH slot 815 are valid, and the ROs (i.e., RO #2 and RO #3) in the second PRACH slot 820 are invalid. In some respects, the SBFD ROs in the first SBFD slot 825 and the second SBFD slot 830 are determined based on the valid TDD ROs in PRACH slot 810. Therefore, in this example, the time offset 835 from the valid ROs in the first PRACH slot 815 can be used to identify the ROs (i.e., SBFD RO #0 and #1) in the first SBFD slot 825, and the second SBFD slot 830 may not include any ROs due to the invalid ROs in the second PRACH slot 820.

[0101] Figure 9 An example of a random access resource 900 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the random access resource 900 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 900 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0102] exist Figure 9 In this example, the TDD slot configuration 905 may include downlink slots, flexible slots, and uplink slots, wherein a downlink slot or flexible slot may be configured as an SBFD slot, as discussed herein. In this example, the PRACH configuration may configure the TDD PRACH slot 910 to include an RO. In this example, the RO of the SBFD PRACH slot 915 may be determined based on a time offset 920 from the TDD PRACH slot 910, where the time offset 920 may be positive or negative. For example, a positive offset value 930 may be provided by a first time offset 920-a or a second time offset 920-b. Similarly, a negative offset value 925 may be provided by a third time offset 920-c or a fourth time offset 920-d.

[0103] In some aspects, time offset 920 may be based on physical time slot counts. In other aspects, time offset 920 may be based on available SBFD PRACH time slots 915. For example, a first time offset 920-a may have time slot offset values ​​for two time slots using physical time slot counts, and a second time offset 920-b may have time slot offset values ​​for two time slots using available SBFD PRACH time slot counts, and thus these two time offsets 920-a and 920-b result in the selection of different SBFD PRACH time slots 915. In these examples, available SBFD time slot counts refer to counting only SBFD time slots from the reference PRACH time slot or RO. In some aspects, time offset 920 may have time slot or symbol granularity, wherein, for time slot granularity, TDD-RO and SBFD-RO are separated in different time slots, and, for symbol granularity, TDD-RO and SBFD-RO may be in the same or different time slots. In some aspects, the value of time offset 920 may be implicit or explicit. For implicit values, the time offset 920 can be based on the first available SBFD slot (e.g., slot offset = 1). For explicit values, the time offset 920 can be based on the RRC configuration.

[0104] Figure 10 An example of a random access resource 1000 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. In some cases, aspects of the random access resource 1000 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 1000 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0105] exist Figure 10 In this example, TDD slot configuration 1005 may include downlink slots, flexible slots, and uplink slots, wherein flexible slots can be configured as SBFD slots, as discussed herein. In this example, PRACH configuration may configure TDDPRACH slot 1010 to include RO, including the first PRACH slot 1015. In this example, similar to the reference... Figure 7 and Figure 8In the discussion, the second PRACH slot 1020 is configured as a downlink slot. Therefore, in this example, the ROs (i.e., RO #0 and RO #1) in the first PRACH slot 1015 are valid. In some aspects, the SBFD ROs in the first SBFD slot 1025 are determined based on the valid first ROs in PRACH slot 1015. Therefore, in this example, the time offset 1035 with respect to the first valid RO in PRACH slot 1015 can be used to identify the ROs in the first SBFD slot 1025 (i.e., SBFD RO #0 and #1), while there are no ROs in the second SBFD slot 1030. In some cases, the time offset 1035 can be based on a physical symbol or slot count, or the time offset 1035 can be based on an available SBFD symbol or slot count. Therefore, for slot-based offsets, TDD-RO and SBFD-RO can be separated in different slots, and for symbol-based offsets, TDD-RO and SBFD-RO can be in the same or different slots.

[0106] Figure 11 An example of a random access resource 1100 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. In some cases, aspects of the random access resource 1100 may be implemented as described in the reference. Figure 1 and Figure 2 The described wireless communication system 100 or 200 is implemented in or through these aspects. For example, random access resources 1100 may be configured at network entity 105 and UE 115, which may be as described in reference... Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described.

[0107] exist Figure 11 In this configuration, frequency resources for SBFD ROs can be identified based on configuration or based on the RO frequency offset provided in the PRACH configuration. In a first example, the first time slot 1110 can be a TDD uplink time slot, the second time slot 1115 can be a downlink time slot, and the third time slot 1120 and the fourth time slot 1125 can be SBFD time slots. In some aspects, an explicitly configured frequency offset 1105 can allow SBFD RO resources to be identified based on time offset 1130 and frequency offset 1135 relative to the TDD RO. In this example, the first TDD time slot 1110 can include two TDD ROs that are frequency-division multiplexed, and the location of the SBFD RO in the third time slot 1120 can be determined based on time offset 1130 and frequency offset 1135.

[0108] In the second example, the first time slot 1155 can be a TDD uplink time slot, the second time slot 1160 can be a downlink time slot, and the third time slot 1165 and the fourth time slot 1170 can be SBFD time slots. In some aspects, the implicit frequency offset 1150 may allow the SBFD RO resource to be identified based on a time offset 1175 and a frequency offset 1180 relative to the TDD RO. In this example, the first TDD time slot 1110 may include two TDD ROs that are frequency-division multiplexed, and the location of the SBFD RO in the third time slot 1165 may be determined based on a time offset 1130 and an implicit frequency offset 1180 relative to the start of the uplink subband of the SBFD third time slot 1165. In some cases, for implicit indications, the starting resource block (RB) for the SBFD RO (e.g., the lowest RO in the frequency domain) can be interpreted relative to the first physical resource block (PRB) in the uplink subband (e.g., the lowest PRB in the frequency domain) (or the available PRB in the uplink subband) and using modulo operations based on the size of the uplink subband or the number of PRBs in the uplink subband. In cases with explicit indications of frequency offset, the RB offset can be configured using RRC. Additionally, in some aspects, the UE can determine whether the RO is frequency-division multiplexed in the SBFD slot, and this determination can be based on the same number of frequency-division multiplexed ROs as in the TDD PRACH slot, on fewer frequency-division multiplexed ROs than in the TDD PRACH slots on one side of the uplink subband, or based on an explicit configuration that may differ from the PRACH configuration used for TDD communication.

[0109] Additionally or alternatively, the PRACH format in an SBFD-PRACH RO can be the same as the PRACH format in a TDD-PRACH RO, or it can be a different PRACH format. The PRACH format can be explicitly configured by the RRC, or implicitly determined based on rules or association with the TDD PRACH format. For example, SBFD PRACH formats A1 / A2 can be associated with long format sequence 0, and SBFD PRACH formats B1 / B2 can be associated with format sequence 1. In some aspects, the number of SBFD-PRACH slots can also be explicitly configured or implicitly determined (e.g., the same as TDD PRACH slots or an integer number of slots). In some aspects, the number of ROs per SBFD PRACH slot can be based on the PRACH sequence used for random access messages. For example, if the same PRACH sequence is used, the same number of ROs can be used, or a subset of ROs or even an integer multiple of ROs can be used. If different PRACH sequences are used for SBFD ROs, the number of SBFD ROs can be scaled by a factor based on the sequence length. In some aspects, when using the same PRACH sequence, the length of the SBFD ROs at the TDD ROs can be the same in terms of symbol count; otherwise, scaling can be based on different sequence lengths. In some aspects, the time gap between consecutive SBFD ROs and the frequency gap between frequency-division multiplexed SBFD ROs can be configured, or a default behavior with no gaps can be used. Additionally or alternatively, a mapping between ROs and synchronization signal blocks (SSBs) can be provided. In some aspects, a separate SSB-RO mapping for additional SBFD ROs can be provided in addition to the SSB-RO mapping for TDD-ROs. In other aspects, a single SBFD mapping can be used across both TDD-ROs and SBFD-ROs.

[0110] Figure 12 An example of a process flow 1200 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. In some cases, aspects of process flow 1200 may be implemented as described in the reference. Figures 1 to 11 The described wireless communication system 100 or 200 or aspects of random access resources or implemented through these aspects. For example, process flow 1200 may include UE 115-b, which may be as referenced Figures 1 to 11 The example of UE 115 described herein. Additionally, process flow 1200 may include network entity 105-b, which may be as described in reference [reference needed]. Figures 1 to 11 An example of the described network entity 105.

[0111] In the following description of process flow 1200, operations may be performed in a different order than those shown. Additionally or alternatively, other operations may be added to or removed from process flow 1200. Although UE 115-b and network entity 105-b are shown as performing operations of process flow 1200, some aspects of some operations may also be performed by one or more other devices (e.g., other UE 115, other network entity 105, or other entities outside the network).

[0112] At 1205, optionally, UE 115-b may send a UE capability indication, and network entity 105-b may receive the UE capability indication. In some cases, the UE capability indication may be provided via RRC signaling having other UE 115-b capabilities. In some cases, the UE capability indication may be provided in response to a query from network entity 105-b. In some cases, the UE capability indication may indicate that UE 115-b can identify the time and frequency resources of random access messages in a full-duplex time slot, at least in part, based on the random access channel configuration associated with the non-full-duplex time slot.

[0113] At 1210, network entity 105-b can send PRACH configuration, and UE 115-b can receive this PRACH configuration. In some cases, PRACH configuration can be provided for non-SBFD time slots in TDD time slot configuration. In some cases, the PRACH configuration can indicate the PRACH configuration index value of a parameter mapped to the location defining the RO.

[0114] At 1215, network entity 105-b can send an SBFD configuration, and UE 115-b can receive the SBFD configuration. In some cases, the SBFD configuration can indicate that one or more TDD slots in the TDD configuration are SBFD slots, where network entity 105-b can use one or more downlink subbands to send downlink communication to the UE, while using uplink subbands to receive uplink communication from the same or different UEs.

[0115] At 1220, UE 115-b can determine resources for one or more ROs in one or more SBFD slots based on PRACH configuration and SBFD configuration. UE 115-b can determine the RO locations in SBFD slots according to various techniques as discussed herein, including determining time and frequency resources for one or more ROs. At 1225, network entity 105-b can monitor RACH messages in one or more SBFD slot ROs.

[0116] At 1230, UE 115-b can send a RACH message (e.g., MSG1) in the RO of the SBFD time slot, and network entity 105-b can receive the RACH message. At 1235, UE 115-b and network entity 105-b can communicate using the established communication procedure triggered by the RACH message.

[0117] Figure 13 A block diagram 1300 of a device 1305 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. Device 1305 may be an example of various aspects of UE 115 as described herein. Device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. Device 1305, or one or more components of device 1305 (e.g., receiver 1310, transmitter 1315, communication manager 1320), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0118] Receiver 1310 may provide components for receiving information, such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels associated with random access channel configurations for full-duplex communication). The information may be passed to other components of device 1305. Receiver 1310 may utilize a single antenna or a collection of antennas.

[0119] Transmitter 1315 may provide components for transmitting signals generated by other components of device 1305. For example, transmitter 1315 may transmit information associated with various information channels, such as control channels, data channels, and information channels associated with random access channel configurations for full-duplex communication, including packets, user data, control information, or any combination thereof. In some examples, transmitter 1315 may be co-located with receiver 1310 in a transceiver module. Transmitter 1315 may utilize a single antenna or a collection of multiple antennas.

[0120] The communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be examples of components used to perform various aspects of random access channel configuration for full-duplex communication as described herein. For example, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0121] In some examples, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0122] Additionally or alternatively, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor (e.g., referred to as processor executable code). If implemented in code executed by at least one processor, the functionality of the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0123] In some examples, the communication manager 1320 may be configured to use a receiver 1310, a transmitter 1315, or both, or otherwise cooperate with the receiver, transmitter, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1320 may receive information from the receiver 1310, transmit information to the transmitter 1315, or integrate with the receiver 1310, transmitter 1315, or a combination of both to acquire information, output information, or perform various other operations as described herein.

[0124] According to the examples disclosed herein, the communication manager 1320 may support wireless communication. For example, the communication manager 1320 is capable of, configured to, or operable to support components for receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes resources for one or more random access opportunities. The communication manager 1320 is capable of, configured to, or operable to support components for receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set. The communication manager 1320 is capable of, configured to, or operable to support components for transmitting random access messages in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access messages in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0125] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 (e.g., controlling receiver 1310, transmitter 1315, communication manager 1320, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for providing RO in full-duplex time slots in addition to RO provided in non-full-duplex time slots, which can allow for reduced latency, increased throughput, more efficient use of communication resources, improved communication reliability, and enhanced user experience.

[0126] Figure 14 A block diagram 1400 of a device 1405 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. Device 1405 may be an example of aspects of device 1305 or UE 115 as described herein. Device 1405 may include receiver 1410, transmitter 1415, and communication manager 1420. Device 1405, or one or more components of device 1405 (e.g., receiver 1410, transmitter 1415, communication manager 1420), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0127] Receiver 1410 may provide components for receiving information, such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels associated with random access channel configurations for full-duplex communication). Information may be passed to other components of device 1405. Receiver 1410 may utilize a single antenna or a collection of antennas.

[0128] Transmitter 1415 may provide components for transmitting signals generated by other components of device 1405. For example, transmitter 1415 may transmit information associated with various information channels, such as control channels, data channels, and information channels associated with random access channel configurations for full-duplex communication, including packets, user data, control information, or any combination thereof. In some examples, transmitter 1415 may be co-located with receiver 1410 in a transceiver module. Transmitter 1415 may utilize a single antenna or a collection of multiple antennas.

[0129] Device 1405 or its various components may be examples of parts for performing various aspects of random access channel configuration for full-duplex communication as described herein. For example, communication manager 1420 may include RACH configuration manager 1425, full-duplex configuration manager 1430, RACH transmission component 1435, or any combination thereof. Communication manager 1420 may be examples of aspects of communication manager 1320 as described herein. In some examples, communication manager 1420 or its various components may be configured to use receiver 1410, transmitter 1415, or both, or otherwise cooperate with the receiver, transmitter, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or be integrated with receiver 1410, transmitter 1415, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0130] According to the examples disclosed herein, the communication manager 1420 may support wireless communication. The RACH configuration manager 1425 is capable of, configured to, or operable to support components for receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set including resources for one or more random access opportunities. The full-duplex configuration manager 1430 is capable of, configured to, or operable to support components for receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set. The RACH transmission component 1435 is capable of, configured to, or operable to support components for transmitting random access messages in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access messages in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0131] Figure 15A block diagram 1500 is shown of a communication manager 1520 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure. The communication manager 1520 may be an example of a communication manager 1320, a communication manager 1420, or aspects thereof as described herein. The communication manager 1520 or its various components may be examples of parts for performing various aspects of random access channel configuration for full-duplex communication as described herein. For example, the communication manager 1520 may include a RACH configuration manager 1525, a full-duplex configuration manager 1530, a RACH transmission component 1535, an RO identification component 1540, a capability manager 1545, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0132] According to the examples disclosed herein, the communication manager 1520 may support wireless communication. The RACH configuration manager 1525 is capable of, configured to, or operable to support components for receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set including resources for one or more random access opportunities. The full-duplex configuration manager 1530 is capable of, configured to, or operable to support components for receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set. The RACH transmission component 1535 is capable of, configured to, or operable to support components for transmitting random access messages in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access messages in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0133] In some examples, the RO identification component 1540 is capable of, configured to, or operable to support components for identifying a second full-duplex time slot subset within a full-duplex time slot set based on a time offset from one or more time slots in a first non-full-duplex time slot subset, the second full-duplex time slot subset including one or more random access opportunities that can be used to send random access messages.

[0134] In some examples, the second full-duplex time slot subset is identified based on a mapping from the first non-full-duplex time slot subset, wherein the mapping provides a one-to-one mapping between each time slot in the first non-full-duplex time slot subset and each time slot in the second full-duplex time slot subset, or the mapping provides a one-to-many mapping between a second time slot in the first non-full-duplex time slot subset and two or more time slots in the second full-duplex time slot subset.

[0135] In some examples, the RACH configuration manager 1525 is capable of, configured to, or operable to support components for determining the location of a first full-duplex time slot based on a time offset from a non-full-duplex time slot in a first non-full-duplex time slot subset, wherein the time offset includes the non-full-duplex time slot or begins from a subsequent time slot of a second non-full-duplex time slot. In some examples, the full-duplex time slot set includes at least two full-duplex time slots mapped to the first non-full-duplex time slot in the first non-full-duplex time slot subset.

[0136] In some examples, the RACH configuration manager 1525 is capable of, configured to, or operable to support components for determining the location of a first full-duplex time slot based on a time offset from a non-full-duplex time slot in a subset of first non-full-duplex time slots, wherein the time offset indicates the number of physical time slots relative to the non-full-duplex time slots or the number of available full-duplex time slots relative to the second non-full-duplex time slots. In some examples, the time offset indicates the number of positive or negative time slots relative to the second non-full-duplex time slots.

[0137] In some examples, the RO identification component 1540 is capable of, configured to, or operable to support components for identifying one or more random access opportunities in a first full-duplex time slot based on a time offset from the random access channel opportunity in the first non-full-duplex time slot within a subset of the first non-full-duplex time slots, wherein the first full-duplex time slot includes one or more random access opportunities, regardless of whether the first non-full-duplex time slot is a valid uplink time slot.

[0138] In some examples, the RO identification component 1540 is capable of, configured to, or operable to support components for determining the location of one or more random access opportunities in a first full-duplex time slot based on a time offset relative to one or more random access opportunities in a first non-full-duplex time slot subset, wherein the time offset indicates the number of time slots or symbols relative to one or more random access opportunities in one or more non-full-duplex symbols in the first non-full-duplex time slot subset.

[0139] In some examples, the RO identification component 1540 is capable of, configured to, or operable to support a component for identifying one or more random access opportunities for transmission of the random access channel in the first full-duplex time slot based solely on the time offset from the valid random access opportunities in the first non-full-duplex time slot subset.

[0140] In some examples, the RO identification component 1540 is capable of, configured to, or operable to support components for determining the location of one or more random access opportunities in a first full-duplex time slot based on a time offset relative to one or more random access opportunities in a first non-full-duplex time slot subset, wherein the time offset indicates the number of time slots or symbols relative to one or more random access opportunities in one or more non-full-duplex symbols in the first non-full-duplex time slot subset.

[0141] In some examples, the RACH configuration manager 1525 is capable of, can be configured to, or is operable to support components for determining the location of a first full-duplex time slot based on a time offset from a non-full-duplex time slot in a subset of first non-full-duplex time slots, wherein the time offset is a defined offset value or is provided to the UE in the random access channel configuration.

[0142] In some examples, the RACH configuration manager 1525 is capable of, configured to, or able to operate to support components for determining the location of frequency resources for random access messages in a first full-duplex time slot based on a frequency offset associated with an uplink subband of the first full-duplex time slot, wherein the frequency offset corresponds to a first physical resource block of the uplink subband of the first full-duplex time slot, or the frequency offset is provided to the UE in a random access channel configuration.

[0143] In some examples, the first full-duplex timeslot includes an uplink subband that includes frequency resources for at least two random access opportunities, with random access messages being transmitted using the frequency resources of one of the at least two random access opportunities. In some examples, the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with a random access channel configuration associated with a set of non-full-duplex timeslots. In some examples, the at least two random access opportunities are frequency-division multiplexed within the uplink subband based on the bandwidth of the uplink subband. In some examples, the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with a full-duplex configuration.

[0144] In some examples, the RACH transmission component 1535 is capable of, configured to, or able to operate to support components for formatting sequences of random access messages according to the same format indicated in the random access channel configuration or according to the format indicated in the full-duplex configuration. In some examples, the number of full-duplex time slots in the full-duplex time slot set configured for transmitting random access messages is signaled to the UE or determined based on the number of non-full-duplex time slots configured for transmitting random access messages.

[0145] In some examples, when the same random access channel sequence is configured for both full-duplex and non-full-duplex time slots, the first number of random access opportunities available for transmitting a random access message in the first full-duplex time slot is the same number, a subset thereof, or an integer multiple thereof, as the second number of random access opportunities available for transmitting a random access message in a subset of the first non-full-duplex time slots. In some examples, when different random access channel sequences are configured for both full-duplex and non-full-duplex time slots, the first number of random access opportunities available for transmitting a random access message in the first full-duplex time slot is scaled relative to the second number of random access opportunities available for transmitting a random access message in a subset of the first non-full-duplex time slots.

[0146] In some examples, based on whether the same or different random access channel sequences are configured for full-duplex and non-full-duplex time slots, the duration of one or more random access opportunities within a first full-duplex time slot is the same duration or a different duration than the duration of one or more random access opportunities in a subset of first non-full-duplex time slots. In some examples, the first full-duplex time slot includes time resources for two or more random access opportunities and frequency resources for two or more random access opportunities, and wherein the time gap and frequency gap between consecutive random access opportunities are each zero unless configured to non-zero values.

[0147] In some examples, the RO identification component 1540 is capable of, configured to, or operable to support components for receiving mapping information indicating the correspondence between one or more random access opportunities and one or more synchronization blocks within a first full-duplex time slot, wherein this mapping information is provided separately from other mapping information associated with non-full-duplex time slots. In some examples, the RACH configuration manager 1525 is capable of, configured to, or operable to support components for receiving mapping information indicating the correspondence between one or more random access opportunities and one or more synchronization blocks, wherein this mapping information applies to both full-duplex and non-full-duplex time slots.

[0148] In some examples, the capability manager 1545 is capable of, configured to, or able to operate to support components for sending UE capability indications regarding the time and frequency resources of a UE's ability to identify a random access message in a first full-duplex time slot based on the random access channel configuration associated with the non-full-duplex time slot set.

[0149] Figure 16 A diagram of a system 1600 including device 1605 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. Device 1605 may be an example of device 1305, device 1405, or UE 115 as described herein, or may include components thereof. Device 1605 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 1605 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1620, an input / output (I / O) controller (e.g., I / O controller 1610), a transceiver 1615, one or more antennas 1625, at least one memory 1630, code 1635, and at least one processor 1640. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1645).

[0150] I / O controller 1610 manages the input and output signals of device 1605. I / O controller 1610 can also manage peripheral devices not integrated into device 1605. In some cases, I / O controller 1610 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1610 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, it may be another known operating system. Additionally or alternatively, the I / O controller 1610 may represent, or interact with, a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1610 may be implemented as part of one or more processors, such as at least one processor 1640. In some cases, a user may interact with the device 1605 via the I / O controller 1610 or via hardware components controlled by the I / O controller 1610.

[0151] In some cases, device 1605 may include a single antenna. However, in other cases, device 1605 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1615 may communicate bidirectionally via one or more antennas 1625 using a wired or wireless link as described herein. For example, transceiver 1615 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1615 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1625 for transmission; and demodulating packets received from one or more antennas 1625. Transceiver 1615, or transceiver 1615 and one or more antennas 1625, may be an example of transmitter 1315, transmitter 1415, receiver 1310, receiver 1410, or any combination thereof or components thereof as described herein.

[0152] At least one memory 1630 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1630 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1635. Code 1635 may include instructions that, when executed by at least one processor 1640, cause device 1605 to perform the various functions described herein. Code 1635 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1635 may not be directly executable by at least one processor 1640, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1630 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0153] At least one processor 1640 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1640 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 1640. At least one processor 1640 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1630) to cause device 1605 to perform various functions (e.g., functions or tasks supporting random access channel configuration for full-duplex communication). For example, device 1605 or components thereof may include at least one processor 1640 and at least one memory 1630 coupled to or coupled to the at least one processor 1640, wherein the at least one processor 1640 and the at least one memory 1630 are configured to perform the various functions described herein.

[0154] In some examples, at least one processor 1640 may include multiple processors, and at least one memory 1630 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1640 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1640) and memory circuitry (which may include at least one memory 1630)) or components that receive or receive input and process the input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1640 or a processing system including at least one processor 1640 may be configured, capable of being configured, or operable to cause device 1605 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 1635 (e.g., processor-executable code) stored in at least one memory 1630 or otherwise executing the code.

[0155] According to the examples disclosed herein, the communication manager 1620 may support wireless communication. For example, the communication manager 1620 may be capable of, configured to, or operable to support components for receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes resources for one or more random access opportunities. The communication manager 1620 may be capable of, configured to, or operable to support components for receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set. The communication manager 1620 may be capable of, configured to, or operable to support components for transmitting random access messages in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access messages in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0156] By including or configuring a communication manager 1620 according to an example as described herein, device 1605 can support techniques for providing ROs in full-duplex time slots in addition to those provided in non-full-duplex time slots, which can allow for reduced latency, increased throughput, more efficient use of communication resources, improved communication reliability, and enhanced user experience.

[0157] In some examples, the communication manager 1620 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1615, one or more antennas 1625, or any combination thereof, or otherwise cooperating with such transceiver, one or more antennas, or any combination thereof. Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 may be supported or executed by at least one processor 1640, at least one memory 1630, code 1635, or any combination thereof. For example, code 1635 may include instructions that can be executed by at least one processor 1640 to cause the device 1605 to perform various aspects of the random access channel configuration for full-duplex communication as described herein, or at least one processor 1640 and at least one memory 1630 may be otherwise configured to perform or support such operations individually or jointly.

[0158] Figure 17A block diagram 1700 of a device 1705 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. Device 1705 may be an example of aspects of network entity 105 as described herein. Device 1705 may include a receiver 1710, a transmitter 1715, and a communication manager 1720. Device 1705, or one or more components of device 1705 (e.g., receiver 1710, transmitter 1715, communication manager 1720), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0159] Receiver 1710 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1705. In some examples, receiver 1710 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1710 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0160] Transmitter 1715 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1705. For example, transmitter 1715 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1715 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1715 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1715 and receiver 1710 may be co-located in a transceiver, which may include or be coupled to a modem.

[0161] The communication manager 1720, receiver 1710, transmitter 1715, or various combinations or components thereof may be examples of components used to perform various aspects of random access channel configuration for full-duplex communication as described herein. For example, the communication manager 1720, receiver 1710, transmitter 1715, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0162] In some examples, the communication manager 1720, receiver 1710, transmitter 1715, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0163] Additionally or alternatively, the communication manager 1720, receiver 1710, transmitter 1715, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor (e.g., referred to as processor executable code). If implemented in code executed by at least one processor, the functionality of the communication manager 1720, receiver 1710, transmitter 1715, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0164] In some examples, the communication manager 1720 may be configured to use a receiver 1710, a transmitter 1715, or both, or otherwise cooperate with the receiver, transmitter, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1720 may receive information from the receiver 1710, transmit information to the transmitter 1715, or integrate with the receiver 1710, transmitter 1715, or a combination of both to acquire information, output information, or perform various other operations as described herein.

[0165] According to the examples disclosed herein, the communication manager 1720 may support wireless communication. For example, the communication manager 1720 may be capable of, configured to, or operable to support components for outputting to the UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set including resources for one or more random access opportunities. The communication manager 1720 may be capable of, configured to, or operable to support components for outputting to the UE a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set. The communication manager 1720 may be capable of, configured to, or operable to support components for obtaining a random access message from the UE in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0166] By including or configuring a communication manager 1720 according to an example as described herein, device 1705 (e.g., controlling receiver 1710, transmitter 1715, communication manager 1720, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for providing RO in full-duplex time slots in addition to RO provided in non-full-duplex time slots, which can allow for reduced latency, increased throughput, more efficient use of communication resources, improved communication reliability, and enhanced user experience.

[0167] Figure 18 A block diagram 1800 of a device 1805 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. Device 1805 may be an example of aspects of device 1705 or network entity 105 as described herein. Device 1805 may include a receiver 1810, a transmitter 1815, and a communication manager 1820. Device 1805, or one or more components of device 1805 (e.g., receiver 1810, transmitter 1815, communication manager 1820), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0168] Receiver 1810 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1805. In some examples, receiver 1810 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1810 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0169] Transmitter 1815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1805. For example, transmitter 1815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1815 and receiver 1810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0170] Device 1805 or its various components may be examples of parts for performing various aspects of random access channel configuration for full-duplex communication as described herein. For example, communication manager 1820 may include RACH configuration manager 1825, full-duplex configuration manager 1830, RACH receiver component 1835, or any combination thereof. Communication manager 1820 may be examples of aspects of communication manager 1720 as described herein. In some examples, communication manager 1820 or its various components may be configured to use receiver 1810, transmitter 1815, or both, or otherwise cooperate with such receiver, transmitter, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1820 may receive information from receiver 1810, transmit information to transmitter 1815, or be integrated with receiver 1810, transmitter 1815, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0171] According to the examples disclosed herein, the communication manager 1820 may support wireless communication. The RACH configuration manager 1825 is capable of, configured to, or operable to support components for outputting to the UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set including resources for one or more random access opportunities. The full-duplex configuration manager 1830 is capable of, configured to, or operable to support components for outputting to the UE a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set. The RACH receiving component 1835 is capable of, configured to, or operable to support components for obtaining a random access message from the UE in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0172] Figure 19 A block diagram 1900 is shown of a communication manager 1920 supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure. The communication manager 1920 may be an example of a communication manager 1720, a communication manager 1820, or aspects thereof as described herein. The communication manager 1920 or its various components may be examples of parts for performing various aspects of random access channel configuration for full-duplex communication as described herein. For example, the communication manager 1920 may include a RACH configuration manager 1925, a full-duplex configuration manager 1930, a RACH receiving component 1935, an RO identification component 1940, a capability manager 1945, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). The communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0173] According to the examples disclosed herein, the communication manager 1920 may support wireless communication. The RACH configuration manager 1925 is capable of, configured to, or operable to support components for outputting to the UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set including resources for one or more random access opportunities. The full-duplex configuration manager 1930 is capable of, configured to, or operable to support components for outputting to the UE a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set. The RACH receiving component 1935 is capable of, configured to, or operable to support components for obtaining a random access message from the UE in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0174] In some examples, a second full-duplex time slot subset within the full-duplex time slot set includes one or more random access opportunities that can be used to send random access messages, and wherein the second full-duplex time slot subset is determined based on the time offset from one or more time slots in the first non-full-duplex time slot subset.

[0175] In some examples, the second full-duplex time slot subset is identified based on a mapping from the first non-full-duplex time slot subset, wherein the mapping provides a one-to-one mapping between each time slot in the first non-full-duplex time slot subset and each time slot in the second full-duplex time slot subset, or the mapping provides a one-to-many mapping between a second time slot in the first non-full-duplex time slot subset and two or more time slots in the second full-duplex time slot subset. In some examples, the location of the first full-duplex time slot is determined based on a time offset from a non-full-duplex time slot in the first non-full-duplex time slot subset, wherein the time offset includes the non-full-duplex time slot or begins from a subsequent time slot of the second non-full-duplex time slot. In some examples, the full-duplex time slot set includes at least two full-duplex time slots mapped to a first non-full-duplex time slot in the first non-full-duplex time slot subset.

[0176] In some examples, the location of the first full-duplex time slot is determined based on the time offset from non-full-duplex time slots in a subset of first non-full-duplex time slots, and wherein the time offset indicates the number of physical time slots relative to the non-full-duplex time slots or the number of available full-duplex time slots relative to the second non-full-duplex time slots. In some examples, the time offset indicates the number of positive or negative time slots relative to the second non-full-duplex time slots. In some examples, the first full-duplex time slot includes one or more random access opportunities determined based on the time offset from random access channel opportunities in the first non-full-duplex time slots in a subset of first non-full-duplex time slots, wherein the first full-duplex time slot includes one or more random access opportunities regardless of whether the first non-full-duplex time slot is a valid uplink time slot.

[0177] In some examples, the first full-duplex time slot includes one or more random access opportunities for random access channel transmission, the one or more random access opportunities being based solely on time offsets from valid random access opportunities in a first non-full-duplex time slot subset. In some examples, the location of one or more random access opportunities in the first full-duplex time slot is based on time offsets from one or more random access opportunities in a first non-full-duplex time slot subset, and wherein the time offset indicates the number of time slots or symbols relative to one or more random access opportunities in one or more non-full-duplex symbols in the first non-full-duplex time slot subset. In some examples, the location of the first full-duplex time slot is determined based on time offsets from non-full-duplex time slots in the first non-full-duplex time slot subset, and wherein the time offset is a defined offset value or is provided to the UE in the random access channel configuration. In some examples, the location of the frequency resources for random access messages in the first full-duplex time slot is determined based on a frequency offset associated with an uplink subband of the first full-duplex time slot, and wherein the frequency offset corresponds to a first physical resource block of the uplink subband of the first full-duplex time slot, or the frequency offset is provided to the UE in the random access channel configuration.

[0178] In some examples, the first full-duplex timeslot includes an uplink subband that includes frequency resources for at least two random access opportunities, with random access messages being transmitted using the frequency resources of one of the at least two random access opportunities. In some examples, the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with a random access channel configuration associated with a set of non-full-duplex timeslots. In some examples, the at least two random access opportunities are frequency-division multiplexed within the uplink subband based on the bandwidth of the uplink subband. In some examples, the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with a full-duplex configuration.

[0179] In some examples, the sequence of random access messages is formatted according to the same format indicated in the random access channel configuration or according to the format indicated in the full-duplex configuration. In some examples, the number of full-duplex time slots configured to send random access messages in the full-duplex time slot set is signaled to the UE or determined based on the number of non-full-duplex time slots configured to send random access messages.

[0180] In some examples, when the same random access channel sequence is configured for both full-duplex and non-full-duplex time slots, the first number of random access opportunities available for transmitting a random access message in the first full-duplex time slot is the same number, a subset thereof, or an integer multiple thereof, as the second number of random access opportunities available for transmitting a random access message in a subset of the first non-full-duplex time slots. In some examples, when different random access channel sequences are configured for both full-duplex and non-full-duplex time slots, the first number of random access opportunities available for transmitting a random access message in the first full-duplex time slot is scaled relative to the second number of random access opportunities available for transmitting a random access message in a subset of the first non-full-duplex time slots.

[0181] In some examples, based on whether the same or different random access channel sequences are configured for full-duplex and non-full-duplex time slots, the duration of one or more random access opportunities within a first full-duplex time slot is the same duration or a different duration than the duration of one or more random access opportunities in a subset of first non-full-duplex time slots. In some examples, the first full-duplex time slot includes time resources for two or more random access opportunities and frequency resources for two or more random access opportunities, and wherein the time gap and frequency gap between consecutive random access opportunities are each zero unless configured to non-zero values.

[0182] In some examples, the RACH configuration manager 1925 is capable of, configured to, or operable to support components for outputting mapping information indicating the correspondence between one or more random access opportunities and one or more synchronization blocks within a first full-duplex time slot, wherein this mapping information is provided separately from other mapping information associated with non-full-duplex time slots. In some examples, the capability manager 1945 is capable of, configured to, or operable to support components for outputting mapping information indicating the correspondence between one or more random access opportunities and one or more synchronization blocks, wherein this mapping information applies to both full-duplex and non-full-duplex time slots.

[0183] Figure 20A diagram of a system 2000 including a device 2005 supporting random access channel configuration for full-duplex communication, according to one or more aspects of this disclosure, is shown. Device 2005 may be an example of device 1705, device 1805, or network entity 105 as described herein, or may include components thereof. Device 2005 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. This communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 2005 may include components supporting output and acquisition of communication, such as a communication manager 2020, a transceiver 2010, one or more antennas 2015, at least one memory 2025, code 2030, and at least one processor 2035. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 2040).

[0184] Transceiver 2010 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 2010 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 2010 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 2005 may include one or more antennas 2015 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 2010 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 2015, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 2015, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 2010 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 2015 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 2015 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 2010 may include one or more processors or one or more memory components, or be configured to couple to one or more processors or one or more memory components capable of operating to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 2010, or transceiver 2010 and one or more antennas 2015, or transceiver 2010 and one or more antennas 2015, and one or more processors or one or more memory components (e.g., at least one processor 2035, at least one memory 2025, or both), may be included in a chip or chip assembly mounted in device 2005. In some examples, transceiver 2010 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0185] At least one memory 2025 may include RAM, ROM, or any combination thereof. At least one memory 2025 may store computer-readable code, computer-executable code, or processor-executable code, such as code 2030. Code 2030 may include instructions that, when executed by one or more processors in at least one processor 2035, cause device 2005 to perform the various functions described herein. Code 2030 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 2030 may not be directly executable by a processor in at least one processor 2035, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 2025 may include a BIOS, etc., which controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 2035 may include multiple processors, and at least one memory 2025 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0186] At least one processor 2035 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 2035 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 2035. At least one processor 2035 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 2025) to cause device 2005 to perform various functions (e.g., functions or tasks supporting random access channel configuration for full-duplex communication). For example, device 2005 or components thereof may include at least one processor 2035 and at least one memory 2025 coupled to one or more processors in the at least one processor 2035, the at least one processor 2035 and the at least one memory 2025 being configured to perform the various functions described herein. The at least one processor 2035 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may (e.g., by executing code 2030) host functions for performing the functions of device 2005. The at least one processor 2035 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 2005 (such as within one or more memories of the at least one memory 2025).

[0187] In some examples, at least one processor 2035 may include multiple processors, and at least one memory 2025 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 2035 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 2035) and memory circuitry (which may include at least one memory 2025)) or components that receive or obtain input and process the input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 2035 or a processing system including at least one processor 2035 may be configured, capable of being configured, or operable to cause device 2005 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 2025 or otherwise.

[0188] In some examples, bus 2040 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 2040 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 2005, or communication performed between different components of device 2005 that are co-addressable or may be located in different locations (e.g., where device 2005 may refer to a system in which one or more of communication manager 2020, transceiver 2010, at least one memory 2025, code 2030 and at least one processor 2035 may be located in one component of different components or partitioned between different components).

[0189] In some examples, the communication manager 2020 can manage various aspects of communication with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 2020 can manage the transfer of data communication with client devices (such as one or more UEs 115). In some examples, the communication manager 2020 can manage communication with one or more other network entities 105 and may include a controller or scheduler for controlling communication with UE 115 (in cooperation with one or more other network devices). In some examples, the communication manager 2020 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0190] According to the examples disclosed herein, the communication manager 2020 may support wireless communication. For example, the communication manager 2020 may be capable of, configured to, or operable to support components for outputting to the UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set including resources for one or more random access opportunities. The communication manager 2020 may be capable of, configured to, or operable to support components for outputting to the UE a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the non-full-duplex time slot set. The communication manager 2020 may be capable of, configured to, or operable to support components for obtaining a random access message from the UE in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0191] By including or configuring a communication manager 2020 according to an example as described herein, device 2005 can support a technology for providing RO in full-duplex time slots in addition to RO provided in non-full-duplex time slots, which can allow for reduced latency, increased throughput, more efficient use of communication resources, improved communication reliability, and enhanced user experience.

[0192] In some examples, the communication manager 2020 may be configured to use or otherwise coordinate with the transceiver 2010, one or more antennas 2015 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 2020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 2020 may be supported or performed by the transceiver 2010, one or more processors in at least one processor 2035, one or more memories in at least one memory 2025, code 2030, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 2035, at least one memory 2025, code 2030, or any combination thereof). For example, code 2030 may include instructions that can be executed by one or more processors in at least one processor 2035 to cause the device 2005 to perform various aspects of the random access channel configuration for full-duplex communication as described herein, or at least one processor 2035 and at least one memory 2025 may be otherwise configured to perform or support such operations individually or jointly.

[0193] Figure 21A flowchart illustrating a method 2100 for supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. Operation of method 2100 may be implemented by a UE or its components as described herein. For example, operation of method 2100 may be performed by, as referenced... Figures 1 to 16 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0194] In some examples, at 2105, the method may include: transmitting a UE capability indication regarding time and frequency resources of the UE capable of identifying one or more random access messages in a first full-duplex time slot based on a random access channel configuration associated with a set of non-full-duplex time slots. Operation of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2105 may be provided by reference to [reference needed]. Figure 15 The described capability manager 1545 is executed.

[0195] At 2110, the method may include: receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots for resources for one or more random access opportunities. Operation of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2110 may be derived from references... Figure 15 The RACH Configuration Manager 1525 described is executed.

[0196] At 2115, the method may include: receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in a set of non-full-duplex time slots. The operation of 2115 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2115 may be derived from references... Figure 15 The described full-duplex configuration manager 1530 is executed.

[0197] At 2120, the method may include: transmitting a random access message in at least a first full-duplex time slot of a set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on a random access channel configuration associated with a set of non-full-duplex time slots. The operation of 2120 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2120 may be provided by reference to [reference needed]. Figure 15 The RACH sending component 1535 is described and is used to perform this action.

[0198] Figure 22A flowchart illustrating a method 2200 for supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. Operation of method 2200 may be implemented by a UE or its components as described herein. For example, operation of method 2200 may be performed by, as referenced... Figures 1 to 16 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0199] At 2205, the method may include: receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots for resources for one or more random access opportunities. Operation of 2205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2205 may be derived from references... Figure 15 The RACH Configuration Manager 1525 described is executed.

[0200] At 2210, the method may include: receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in a set of non-full-duplex time slots. The operation of 2210 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2210 may be derived from references... Figure 15 The described full-duplex configuration manager 1530 is executed.

[0201] In some examples, at 2215, the method may include: determining the location of a first full-duplex time slot based on a time offset from a non-full-duplex time slot in a subset of first non-full-duplex time slots, wherein the time offset includes the non-full-duplex time slot or begins from a subsequent time slot of the non-full-duplex time slot. The operation of 2215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2215 may be derived from references... Figure 15 The RACH Configuration Manager 1525 described is executed.

[0202] At 2220, the method may include: transmitting a random access message in at least a first full-duplex time slot of a set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on a random access channel configuration associated with a set of non-full-duplex time slots. The operation of 2220 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2220 may be provided by reference to [reference]. Figure 15 The RACH sending component 1535 is described and is used to perform this action.

[0203] Figure 23A flowchart illustrating a method 2300 for supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. Operation of method 2300 may be implemented by a UE or its components as described herein. For example, operation of method 2300 may be performed by, as referenced... Figures 1 to 16 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0204] At 2305, the method may include: receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots for resources for one or more random access opportunities. Operation of 2305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2305 may be provided by reference to [reference needed]. Figure 15 The RACH Configuration Manager 1525 described is executed.

[0205] At 2310, the method may include: receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in a set of non-full-duplex time slots. The operation of 2310 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2310 may be derived from references... Figure 15 The described full-duplex configuration manager 1530 is executed.

[0206] In some examples, at 2315, the method may include: determining the location of a first full-duplex time slot based on a time offset from a non-full-duplex time slot in a first subset of non-full-duplex time slots, wherein the time offset indicates the number of physical time slots relative to the non-full-duplex time slots or the number of available full-duplex time slots relative to the non-full-duplex time slots. The operation of 2315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2315 may be derived from references... Figure 15 The RACH Configuration Manager 1525 described is executed.

[0207] At 2320, the method may include: transmitting a random access message in at least a first full-duplex time slot of a set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on a random access channel configuration associated with a set of non-full-duplex time slots. The operation of 2320 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2320 may be provided by reference to [reference needed]. Figure 15 The RACH sending component 1535 is described and is used to perform this action.

[0208] Figure 24 A flowchart illustrating a method 2400 for supporting random access channel configuration for full-duplex communication according to one or more aspects of this disclosure is shown. Operation of method 2400 may be implemented by a UE or its components as described herein. For example, operation of method 2400 may be performed by, as referenced... Figures 1 to 16 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0209] At 2405, the method may include: receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots for resources for one or more random access opportunities. Operation of 2405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2405 may be provided by reference to... Figure 15 The RACH Configuration Manager 1525 described is executed.

[0210] At 2410, the method may include: receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in a set of non-full-duplex time slots. The operation of 2410 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2410 may be derived from references... Figure 15 The described full-duplex configuration manager 1530 is executed.

[0211] In some examples, at 2415, the method may include: determining the location of frequency resources for random access messages in the first full-duplex time slot based on a frequency offset associated with an uplink subband of the first full-duplex time slot, wherein the frequency offset corresponds to a first physical resource block of the uplink subband of the first full-duplex time slot, or the frequency offset is provided to the UE in a random access channel configuration. Operation of 2415 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2415 may be provided by reference to [reference needed]. Figure 15 The RACH Configuration Manager 1525 described is executed.

[0212] At 2420, the method may include: transmitting a random access message in at least a first full-duplex time slot of a full-duplex time slot set, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified based on a random access channel configuration associated with a non-full-duplex time slot set. The operation of 2420 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2420 may be provided by reference to [reference needed]. Figure 15 The RACH sending component 1535 is described and is used to perform this action.

[0213] Figure 25 A flowchart illustrating a method 2500 for configuring a random access channel for full-duplex communication, according to one or more aspects of this disclosure, is shown. Operation of method 2500 may be implemented by a network entity or its components as described herein. For example, operation of method 2500 may be implemented by, as referenced... Figures 1 to 12 as well as Figures 17 to 20 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0214] At 2505, the method may include: outputting to the UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots for resources for one or more random access opportunities. Operation of 2505 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2505 may be provided by reference to [reference needed]. Figure 19 The RACH Configuration Manager 1925 described is executed.

[0215] At 2510, the method may include: outputting a second signal to the UE indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in a non-full-duplex time slot set. Operation of 2510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2510 may be derived from references... Figure 19 The described full-duplex configuration manager 1930 is executed.

[0216] At 2515, the method may include: obtaining a random access message from the UE in at least a first full-duplex time slot of a full-duplex time slot set, wherein the time resources and frequency resources of the random access message in the first full-duplex time slot are identified based on a random access channel configuration associated with a non-full-duplex time slot set. The operation of 2515 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2515 may be provided by reference to [reference needed]. Figure 19 The RACH receiving component 1935 described herein is used to perform this action.

[0217] The following provides an overview of the various aspects of this disclosure.

[0218] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots with resources for one or more random access opportunities; receiving a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the full-duplex time slot set do not overlap with time slots in the set of non-full-duplex time slots; and transmitting a random access message in at least a first full-duplex time slot in the set of full-duplex time slots, wherein time resources and frequency resources of the random access message in the first full-duplex time slot are identified at least in part based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0219] Aspect 2: According to the method of aspect 1, the method further includes: identifying a second full-duplex time slot subset within the full-duplex time slot set based at least in part on a time offset from one or more time slots in the first non-full-duplex time slot subset, the second full-duplex time slot subset including one or more random access opportunities available for sending the random access message.

[0220] Aspect 3: According to the method of aspect 2, wherein the second full-duplex time slot subset is identified at least in part based on a mapping from the first non-full-duplex time slot subset, and wherein the mapping provides a one-to-one mapping between each time slot in the first non-full-duplex time slot subset and each time slot in the second full-duplex time slot subset, or the mapping provides a one-to-many mapping between a second time slot in the first non-full-duplex time slot subset and two or more time slots in the second full-duplex time slot subset.

[0221] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: determining the position of the first full-duplex time slot based at least in part on a time offset from a non-full-duplex time slot in the first non-full-duplex time slot subset, wherein the time offset includes the non-full-duplex time slot or begins from a subsequent time slot of the non-full-duplex time slot.

[0222] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the full-duplex time slot set includes at least two full-duplex time slots of a first non-full-duplex time slot mapped to the first non-full-duplex time slot subset.

[0223] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: determining the location of the first full-duplex time slot based at least in part on a time offset from a non-full-duplex time slot in the first non-full-duplex time slot subset, wherein the time offset indicates the number of physical time slots relative to the non-full-duplex time slot or the number of available full-duplex time slots relative to the second non-full-duplex time slot.

[0224] Aspect 7: According to the method of aspect 6, wherein the time offset indicates the number of positive or negative time slots relative to the second non-full-duplex time slot.

[0225] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: identifying one or more random access opportunities in the first full-duplex time slot based at least in part on a time offset from a random access channel opportunity in the first non-full-duplex time slot within the first non-full-duplex time slot subset, wherein the first full-duplex time slot includes the one or more random access opportunities, regardless of whether the first non-full-duplex time slot is a valid uplink time slot.

[0226] Aspect 9: The method according to aspect 8, the method further comprising: determining the location of the one or more random access opportunities in the first full-duplex time slot based at least in part on a time offset relative to one or more random access opportunities in the first non-full-duplex time slot subset, and wherein the time offset indicates the number of time slots or symbols of the one or more random access opportunities relative to one or more non-full-duplex symbols in the first non-full-duplex time slot subset.

[0227] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: identifying one or more random access opportunities for transmission of the random access channel in the first full-duplex time slot based at least in part solely on the time offset from the valid random access opportunities in the first non-full-duplex time slot subset.

[0228] Aspect 11: The method according to aspect 10, the method further comprising: determining the location of the one or more random access opportunities in the first full-duplex time slot based at least in part on a time offset relative to one or more random access opportunities in the first non-full-duplex time slot subset, and wherein the time offset indicates the number of time slots or symbols of the one or more random access opportunities relative to one or more non-full-duplex symbols in the first non-full-duplex time slot subset.

[0229] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: determining the location of the first full-duplex time slot based at least in part on a time offset from a non-full-duplex time slot in the first non-full-duplex time slot subset, wherein the time offset is a defined offset value or is provided to the UE in the random access channel configuration.

[0230] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: determining, at least in part, the location of the frequency resource of the random access message in the first full-duplex time slot based on a frequency offset associated with an uplink subband of the first full-duplex time slot, and wherein the frequency offset corresponds to a first physical resource block of the uplink subband of the first full-duplex time slot, or the frequency offset is provided to the UE in the random access channel configuration.

[0231] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the first full-duplex time slot includes an uplink subband, the uplink subband including frequency resources for at least two random access opportunities, the random access message being transmitted using the frequency resources of one of the at least two random access opportunities, and wherein: the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with the random access channel configuration associated with a set of non-full-duplex time slots, the at least two random access opportunities are frequency-division multiplexed within the uplink subband at least in part based on the bandwidth of the uplink subband, or the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with the full-duplex configuration.

[0232] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: formatting the sequence of random access messages according to the same format indicated in the random access channel configuration or according to the format indicated in the full-duplex configuration.

[0233] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the number of full-duplex time slots in the full-duplex time slot set configured for transmitting the random access message is signaled to the UE, or is determined at least in part based on the number of non-full-duplex time slots configured for transmitting the random access message.

[0234] Aspect 17: The method according to any one of Aspects 1 to 16, wherein when the same random access channel sequence is configured for full-duplex time slots and non-full-duplex time slots, a first number of random access opportunities available for transmitting the random access message in the first full-duplex time slot is the same number, a subset thereof, or an integer multiple thereof, as well as a second number of random access opportunities available for transmitting the random access message in a first non-full-duplex time slot within a subset of the first non-full-duplex time slots.

[0235] Aspect 18: The method according to any one of Aspects 1 to 17, wherein when different random access channel sequences are configured for full-duplex time slots and non-full-duplex time slots, a first number of random access opportunities available for transmitting the random access message in the first full-duplex time slot is scaled relative to a second number of random access opportunities available for transmitting the random access message in the first non-full-duplex time slot subset.

[0236] Aspect 19: The method according to any one of Aspects 1 to 18, wherein at least in part based on whether the same or different random access channel sequences are configured for full-duplex and non-full-duplex time slots, the duration of one or more random access opportunities within the first full-duplex time slot is the same duration or a different duration than the duration of the one or more random access opportunities in the first non-full-duplex time slot subset.

[0237] Aspect 20: The method according to any one of Aspects 1 to 19, wherein the first full-duplex time slot includes time resources for two or more random access opportunities and frequency resources for the two or more random access opportunities, and wherein the time gap and frequency gap between consecutive random access opportunities are each zero unless configured to a non-zero value.

[0238] Aspect 21: The method according to any one of Aspects 1 to 20, the method further comprising: receiving mapping information, the mapping information indicating a correspondence between one or more random access opportunities and one or more synchronization signal blocks within the first full-duplex time slot, and wherein the mapping information is provided separately from other mapping information associated with non-full-duplex time slots.

[0239] Aspect 22: The method according to any one of aspects 1 to 21, the method further comprising: receiving mapping information, the mapping information indicating a correspondence between one or more random access opportunities and one or more synchronization signal blocks, and wherein the mapping information is applied to both full-duplex time slots and non-full-duplex time slots.

[0240] Aspect 23: The method according to any one of Aspects 1 to 22, the method further comprising: transmitting a UE capability indication regarding the time resources and frequency resources of the UE being able to identify the random access message in the first full-duplex time slot based at least in part on the random access channel configuration associated with the non-full-duplex time slot set.

[0241] Aspect 24: A method for wireless communication at a network entity, the method comprising: outputting to a UE a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating a first subset of non-full-duplex time slots in the set of non-full-duplex time slots including resources for one or more random access opportunities; outputting to the UE a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein time slots in the set of full-duplex time slots do not overlap with time slots in the set of non-full-duplex time slots; and obtaining from the UE a random access message in at least a first full-duplex time slot in the set of full-duplex time slots, wherein time resources and frequency resources of the random access message in the first full-duplex time slot are identified at least in part based on the random access channel configuration associated with the set of non-full-duplex time slots.

[0242] Aspect 25: According to the method of aspect 24, the second full-duplex time slot subset within the full-duplex time slot set includes one or more random access opportunities available for transmitting the random access message, and the second full-duplex time slot subset is determined at least in part based on the time offset from one or more time slots in the first non-full-duplex time slot subset.

[0243] Aspect 26: According to the method of aspect 25, wherein the second full-duplex time slot subset is identified at least in part based on a mapping from the first non-full-duplex time slot subset, and wherein the mapping provides a one-to-one mapping between each time slot in the first non-full-duplex time slot subset and each time slot in the second full-duplex time slot subset, or the mapping provides a one-to-many mapping between a second time slot in the first non-full-duplex time slot subset and two or more time slots in the second full-duplex time slot subset.

[0244] Aspect 27: The method according to any one of Aspects 24 to 26, wherein the position of the first full-duplex time slot is determined at least in part based on the time offset of non-full-duplex time slots in the subset of the first non-full-duplex time slots, and wherein the time offset includes the non-full-duplex time slot or begins from a subsequent time slot of the second non-full-duplex time slot.

[0245] Aspect 28: The method according to any one of Aspects 24 to 27, wherein the full-duplex time slot set includes at least two full-duplex time slots of a first non-full-duplex time slot mapped to the first non-full-duplex time slot subset.

[0246] Aspect 29: The method according to any one of Aspects 24 to 28, wherein the location of the first full-duplex time slot is determined at least in part based on the time offset of non-full-duplex time slots in the first non-full-duplex time slot subset, and wherein the time offset indicates the number of physical time slots relative to the non-full-duplex time slots or the number of available full-duplex time slots relative to the second non-full-duplex time slots.

[0247] Aspect 30: The method according to aspect 29, wherein the time offset indicates the number of positive or negative time slots relative to the second non-full-duplex time slot.

[0248] Aspect 31: The method according to any one of Aspects 24 to 30, wherein the first full-duplex time slot includes one or more random access opportunities, the one or more random access opportunities being determined at least in part based on a time offset from a random access channel opportunity in a first non-full-duplex time slot within a subset of the first non-full-duplex time slots, wherein the first full-duplex time slot includes the one or more random access opportunities, regardless of whether the first non-full-duplex time slot is a valid uplink time slot.

[0249] Aspect 32: The method according to any one of Aspects 24 to 31, wherein the first full-duplex time slot includes one or more random access opportunities for random access channel transmission, the one or more random access opportunities being based at least in part solely on time offsets from valid random access opportunities in the first non-full-duplex time slot subset.

[0250] Aspect 33: According to the method of aspect 32, the position of the one or more random access opportunities in the first full-duplex time slot is based at least in part on a time offset from one or more random access opportunities in the first non-full-duplex time slot subset, and the time offset indicates the number of time slots or symbols of the one or more random access opportunities relative to one or more non-full-duplex symbols in the first non-full-duplex time slot subset.

[0251] Aspect 34: The method according to any one of Aspects 24 to 33, wherein the position of the first full-duplex time slot is determined at least in part based on the time offset of the non-full-duplex time slots in the first non-full-duplex time slot subset, and wherein the time offset is a defined offset value or is provided to the UE in the random access channel configuration.

[0252] Aspect 35: The method according to any one of Aspects 24 to 34, wherein the location of the frequency resource of the random access message in the first full-duplex time slot is determined at least in part based on a frequency offset associated with an uplink subband of the first full-duplex time slot, and wherein the frequency offset corresponds to a first physical resource block of the uplink subband of the first full-duplex time slot, or the frequency offset is provided to the UE in the random access channel configuration.

[0253] Aspect 36: The method according to any one of Aspects 24 to 35, wherein the first full-duplex time slot includes an uplink subband, the uplink subband including frequency resources for at least two random access opportunities, the random access message being transmitted using the frequency resources of one of the at least two random access opportunities, and wherein: the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with the random access channel configuration associated with a set of non-full-duplex time slots, the at least two random access opportunities are frequency-division multiplexed within the uplink subband at least in part based on the bandwidth of the uplink subband, or the at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with the full-duplex configuration.

[0254] Aspect 37: The method according to any one of Aspects 24 to 36, wherein the sequence of random access messages is formatted according to the same format indicated in the random access channel configuration or according to the format indicated in the full-duplex configuration.

[0255] Aspect 38: The method according to any one of Aspects 24 to 37, wherein the number of full-duplex time slots in the full-duplex time slot set configured to transmit the random access message is signaled to the UE, or determined at least in part based on the number of non-full-duplex time slots configured to transmit the random access message.

[0256] Aspect 39: The method according to any one of Aspects 24 to 38, wherein when the same random access channel sequence is configured for full-duplex and non-full-duplex time slots, a first number of random access opportunities available for transmitting the random access message in the first full-duplex time slot is the same number, a subset thereof, or an integer multiple thereof, as well as a second number of random access opportunities available for transmitting the random access message in a first non-full-duplex time slot within a subset of the first non-full-duplex time slots.

[0257] Aspect 40: The method according to any one of Aspects 24 to 39, wherein when different random access channel sequences are configured for full-duplex time slots and non-full-duplex time slots, a first number of random access opportunities available for transmitting the random access message in the first full-duplex time slot is scaled relative to a second number of random access opportunities available for transmitting the random access message in the first non-full-duplex time slot subset.

[0258] Aspect 41: The method according to any one of Aspects 24 to 40, wherein at least in part based on whether the same or different random access channel sequences are configured for full-duplex and non-full-duplex time slots, the duration of one or more random access opportunities within the first full-duplex time slot is the same duration or a different duration than the duration of the one or more random access opportunities in the first non-full-duplex time slot subset.

[0259] Aspect 42: The method according to any one of Aspects 24 to 41, wherein the first full-duplex time slot includes time resources for two or more random access opportunities and frequency resources for the two or more random access opportunities, and wherein the time gap and frequency gap between consecutive random access opportunities are each zero unless configured to a non-zero value.

[0260] Aspect 43: The method according to any one of Aspects 24 to 42, the method further comprising: outputting mapping information, the mapping information indicating a correspondence between one or more random access opportunities and one or more synchronization signal blocks within the first full-duplex time slot, and wherein the mapping information is provided separately from other mapping information associated with non-full-duplex time slots.

[0261] Aspect 44: The method according to any one of Aspects 24 to 43, the method further comprising: outputting mapping information, the mapping information indicating a correspondence between one or more random access opportunities and one or more synchronization signal blocks, and wherein the mapping information is applied to both full-duplex time slots and non-full-duplex time slots.

[0262] Aspect 45: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 23.

[0263] Aspect 46: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 23.

[0264] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 23.

[0265] Aspect 48: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 24 to 44.

[0266] Aspect 49: A network entity for wireless communication, the network entity comprising at least one component for performing a method according to any one of aspects 24 to 44.

[0267] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform a method according to any one of aspects 24 to 44.

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

[0269] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0270] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0271] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), (neural processing unit) NPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0272] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0273] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. A disk can magnetically reproduce data, and an optical disc can optically reproduce data using a laser. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0274] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0275] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” may refer to any or all of those one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0276] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0277] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0278] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0279] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots containing resources for one or more random access opportunities; Receive a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein the time slots in the full-duplex time slot set do not overlap with the time slots in the non-full-duplex time slot set; as well as A random access message is transmitted in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified at least in part based on the random access channel configuration associated with the set of non-full-duplex time slots.

2. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The location of the frequency resource of the random access message in the first full-duplex time slot is determined at least in part based on the frequency offset associated with the uplink subband of the first full-duplex time slot, wherein the frequency offset corresponds to the first physical resource block of the uplink subband of the first full-duplex time slot.

3. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: A second full-duplex time slot subset within the full-duplex time slot set is identified at least in part based on the time offset from one or more time slots in the first non-full-duplex time slot subset, the second full-duplex time slot subset including one or more random access opportunities that can be used to send the random access message.

4. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The location of the first full-duplex time slot is determined at least in part based on the time offset from the non-full-duplex time slots in the first non-full-duplex time slot subset, and wherein the time offset includes the non-full-duplex time slot or begins from a subsequent time slot of the non-full-duplex time slot.

5. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The location of the first full-duplex time slot is determined at least in part based on the time offset from the non-full-duplex time slots in the first non-full-duplex time slot subset, and wherein the time offset indicates the number of physical time slots relative to the non-full-duplex time slots or the number of available full-duplex time slots relative to the non-full-duplex time slots.

6. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: One or more random access opportunities in the first full-duplex time slot are identified at least in part based on the time offset from the random access channel opportunity in the first non-full-duplex time slot within the first non-full-duplex time slot subset, wherein the first full-duplex time slot includes the one or more random access opportunities, regardless of whether the first non-full-duplex time slot is a valid uplink time slot.

7. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The location of the first full-duplex time slot is determined at least in part based on the time offset from the non-full-duplex time slots in the first non-full-duplex time slot subset, and wherein the time offset is a defined offset value or is provided to the UE in the random access channel configuration.

8. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The location of the frequency resource for the random access message in the first full-duplex time slot is determined at least in part based on the frequency offset associated with the uplink subband of the first full-duplex time slot, wherein the frequency offset is provided to the UE in the random access channel configuration.

9. The UE according to claim 1, wherein: The first full-duplex time slot includes an uplink subband, the uplink subband including frequency resources for at least two random access opportunities, the random access message being transmitted using the frequency resources of one of the at least two random access opportunities, and wherein: The at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency-division multiplexing configuration provided together with the random access channel configuration associated with the non-full-duplex time slot set. The at least two random access opportunities are frequency-division multiplexed within the uplink subband, at least in part based on the bandwidth of the uplink subband, or The at least two random access opportunities are frequency-division multiplexed within the uplink subband according to a frequency division multiplexing configuration provided together with the full-duplex configuration.

10. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The sequence of random access messages is formatted according to the same format indicated in the random access channel configuration or according to the format indicated in the full-duplex configuration.

11. The UE of claim 1, wherein the number of full-duplex time slots configured to transmit the random access message in the full-duplex time slot set is signaled to the UE, or determined at least in part based on the number of non-full-duplex time slots configured to transmit the random access message.

12. The UE of claim 1, wherein a first number of random access opportunities may be used to transmit the random access message in the first full-duplex time slot: When the same random access channel sequence is configured for full-duplex and non-full-duplex time slots, it is the same number, a subset of, or an integer multiple of the second number of random access opportunities available for transmitting the random access message in the first non-full-duplex time slot within the first non-full-duplex time slot subset; or When different random access channel sequences are configured for full-duplex and non-full-duplex time slots, the scaling is performed relative to a second number of random access opportunities available for transmitting random access messages in the first non-full-duplex time slot subset.

13. The UE of claim 1, wherein the configuration for full-duplex and non-full-duplex time slots is based at least in part on whether the same or different random access channel sequences are used, and the duration of one or more random access opportunities within the first full-duplex time slot is the same or different from the duration of the one or more random access opportunities in the first non-full-duplex time slot subset.

14. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive mapping information indicating the correspondence between one or more random access opportunities and one or more synchronization signal blocks, wherein: The mapping information is provided separately from other mapping information associated with non-full-duplex time slots; or The mapping information is applied to both full-duplex and non-full-duplex time slots.

15. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Send a UE capability indication regarding the time resources and frequency resources of the random access message in the first full-duplex time slot, based at least in part on the random access channel configuration associated with the non-full-duplex time slot set.

16. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Output a first signal to the user equipment (UE) indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots containing resources for one or more random access opportunities; A second signal indicating full-duplex configuration is output to the UE, the full-duplex configuration indicating a set of full-duplex time slots, wherein the time slots in the set of full-duplex time slots do not overlap with the time slots in the set of non-full-duplex time slots; as well as A random access message is obtained from the UE in at least a first full-duplex time slot in the full-duplex time slot set, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified at least in part based on the random access channel configuration associated with the non-full-duplex time slot set.

17. The network entity of claim 16, wherein the location of the frequency resource of the random access message in the first full-duplex time slot is based at least in part on a frequency offset associated with an uplink subband of the first full-duplex time slot, wherein the frequency offset corresponds to a first physical resource block of the uplink subband of the first full-duplex time slot.

18. The network entity of claim 16, wherein the second full-duplex time slot subset within the full-duplex time slot set includes one or more random access opportunities available for transmitting the random access message, and wherein the second full-duplex time slot subset is determined at least in part based on time offsets from one or more time slots in the first non-full-duplex time slot subset.

19. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive a first signal indicating a random access channel configuration associated with a set of non-full-duplex time slots, the random access channel configuration indicating that the set of non-full-duplex time slots includes a first subset of non-full-duplex time slots containing resources for one or more random access opportunities; Receive a second signal indicating a full-duplex configuration, the full-duplex configuration indicating a set of full-duplex time slots, wherein the time slots in the full-duplex time slot set do not overlap with the time slots in the non-full-duplex time slot set; as well as A random access message is transmitted in at least a first full-duplex time slot in the set of full-duplex time slots, wherein the time and frequency resources of the random access message in the first full-duplex time slot are identified at least in part based on the random access channel configuration associated with the set of non-full-duplex time slots.

20. The method according to claim 19, further comprising: The location of the frequency resource of the random access message in the first full-duplex time slot is determined at least in part based on the frequency offset associated with the uplink subband of the first full-duplex time slot, wherein the frequency offset corresponds to the first physical resource block of the uplink subband of the first full-duplex time slot.

Images