Timing considerations for transmission timing in full-duplex mode
By relaxing the timing conditions for transmission in a full-duplex communication system, allowing RO/PO to precede or overlap with SSB, the timing structure of SBFD communication is optimized, improving network resource utilization efficiency and reducing latency.
Patent Information
- Application Number
- CN202580025852.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-03-31
- Filing Date
- 2025-04-01
- Publication Date
- 2026-11-17
AI Technical Summary
In existing full-duplex communication systems, the timing rules for transmission are quite strict, resulting in low network resource utilization efficiency and increased communication latency. In particular, in subband full-duplex (SBFD), the effectiveness of random access timing (RO) and physical uplink shared channel timing (PO) is not fully defined.
The timing conditions for transmission are relaxed, allowing RO/PO to overlap or be adjacent to SSB before the synchronization signal/physical broadcast channel block (SSB), or within a symbol number less than Ng symbols. Flexible link symbol rules are introduced to optimize the communication timing structure through conflict handling rules.
It improves the efficiency of network resource utilization, reduces communication latency, and provides a more flexible timing structure to support SBFD communication.
Smart Images

Figure CN123126012A_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This patent application claims priority to U.S. Patent Application No. 19 / 095,687, filed March 31, 2025, entitled “TIMING CONSIDERATIONS FOR TRANSMISSION OCCASIONS IN FULL DUPLEX”, and U.S. Patent Application No. 63 / 573,881, filed April 3, 2024, entitled “TIMING CONSIDERATIONS FOR TRANSMISSION OCCASIONS IN FULL DUPLEX”, each of which is assigned to the assignee of this application, and each of which is expressly incorporated herein by reference. Technical Field
[0003] The following discussion concerns wireless communication, including timing considerations for transmission in full-duplex environments. Background Technology
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. 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 for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention
[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting timing considerations for transmission timing in full-duplex communication. For example, the described techniques provide different definitions for valid transmission timing (such as for random access timing (RO) or physical uplink shared channel (PUSCH) timing (PO)), and timing considerations in full-duplex communication (including sub-band full-duplex (SBFD)). For example, the network may allow transmission timing before one or more synchronization messages (e.g., synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB)), or for non-SSB-aware user equipment (UE), may allow transmission timing and synchronization messages to be within a time frame less than a symbol-based time frame. N g Within the number of symbols in the gap, or allowing timing and synchronization messages to be sent even adjacently or overlapping. In some examples, timing and synchronization messages may involve various combinations of spacing and arrangement (e.g., front-of-line) rules in SBFD-DL symbols and Flexible Link (FL) symbols. When overlap exists, timing and synchronization messages may also involve collision handling rules and additional rules.
[0006] A method for wireless communication by a UE is described. The method may include: receiving a control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure; receiving a synchronization message during a first duration; and transmitting the random access message associated with the random access procedure during a second duration based on the validity of a transmission time corresponding to a second duration different from the first duration among the one or more transmission times, wherein the validity of the transmission time is based on the relationship between the first duration and the second duration.
[0007] 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 control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure; receive a synchronization message during a first duration; and transmit the random access message associated with the random access procedure during a second duration based on the validity of a transmission time corresponding to a second duration different from the first duration, wherein the validity of the transmission time is based on the relationship between the first duration and the second duration.
[0008] Another UE for wireless communication is described. The UE may include: components for: receiving a control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure; components for: receiving a synchronization message during a first duration; and components for: transmitting the random access message associated with the random access procedure during a second duration based on the validity of a transmission time corresponding to a second duration different from the first duration, wherein the validity of the transmission time is based on the relationship between the first duration and the second duration.
[0009] 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 control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure; receive a synchronization message during a first duration; and transmit the random access message associated with the random access procedure during a second duration based on the validity of a transmission time corresponding to a second duration different from the first duration, wherein the validity of the transmission time is based on the relationship between the first duration and the second duration.
[0010] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for performing a verification process to determine the timing of transmission based on one or more symbols of a second duration preceding one or more symbols of a first duration.
[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more symbols of a second duration are in the same time slot in the time domain as one or more symbols of a first duration.
[0012] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for performing a verification process to determine the timing of transmission based on a first threshold time gap satisfied between a first duration and a second duration.
[0013] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for performing a verification process to determine the timing of transmission based on a threshold time gap associated with a second random access procedure, which is satisfied before one or more symbols of a first duration and before one or more symbols of a second duration, and between the first and second durations.
[0014] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for: receiving a second synchronization message during the third duration based on the overlap of one or more symbols of a third duration different from the fourth duration corresponding to the second transmission timing with one or more symbols of the fourth duration; and transmitting a second random access message associated with a second random access procedure during the fourth duration corresponding to the second transmission timing based on the overlap.
[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving a second synchronization message or sending a second random access message may include operations, features, components, or instructions for: receiving the second synchronization message based on the second synchronization message having a higher priority than a second transmission timing, based on performing one or more measurements on the second synchronization message, or based on an index associated with the second synchronization message having a higher priority than one or more additional indices; and sending the second random access message based on the second random access message and the second transmission timing having a higher priority than the second synchronization message, based on the occurrence of a random access triggering event, based on the random access triggering event having a higher priority than one or more additional random access triggering events, or based on an index associated with the second synchronization message having a lower priority than the one or more additional indices.
[0016] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the following operations, features, components, or instructions may also be included: Performing a verification process to determine that the timing of transmission is valid based on the fact that one or more symbols of a first duration do not overlap with one or more symbols of a second duration. In some examples of the methods, UEs, and non-transitory computer-readable media described herein, one or more symbols of the first duration overlap with one or more symbols of the second duration.
[0017] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, synchronization messages, random access messages, and transmission timing may be associated with threshold frequency gaps, two or more different beams, threshold time gaps for messages with the same index, and minimum transmission power for random access messages, or any combination thereof.
[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the UE may be in connected mode or idle mode.
[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the transmission timing includes one or more uplink symbols or one or more flexible symbols in an uplink frequency subband. In some examples, the one or more uplink symbols and the one or more flexible symbols may include SBFD symbols (e.g., at least one or more symbols of the transmission timing are uplink symbols or flexible symbols in an uplink frequency subband, and the transmission timing is at least partially within an SBFD symbol).
[0020] In the methods described herein, in some examples of UEs and non-transitory computer-readable media, the transmission timing includes RO, and the random access procedure includes a 4-step random access procedure.
[0021] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the transmission timing includes the PO, and the random access procedure includes a 4-step random access procedure or a 2-step random access procedure. Attached Figure Description
[0022] Figure 1 An example of a wireless communication system that supports timing considerations for transmission timing in full-duplex operation, according to one or more aspects of this disclosure, is shown.
[0023] Figure 2A and Figure 2B Examples of wireless communication systems and timing diagrams supporting timing considerations for transmission in full-duplex environments are shown, according to one or more aspects of this disclosure.
[0024] Figure 3A and Figure 3B An example of a timing diagram is shown that supports timing considerations for transmission timing in full-duplex operation according to one or more aspects of this disclosure.
[0025] Figure 4A and Figure 4B An example of a timing diagram is shown that supports timing considerations for transmission timing in full-duplex operation according to one or more aspects of this disclosure.
[0026] Figure 5 An example of a process flow for supporting timing considerations of transmission timing in full-duplex operation is shown, according to one or more aspects of this disclosure.
[0027] Figure 6 and Figure 7 A block diagram of a device for timing considerations of transmission timing in full-duplex operation, according to one or more aspects of this disclosure, is shown.
[0028] Figure 8 A block diagram of a communication manager that supports timing considerations for transmission in full-duplex mode, according to one or more aspects of this disclosure, is shown.
[0029] Figure 9 A diagram of a system including timing considerations for transmission timing in full-duplex mode, according to one or more aspects of this disclosure, is shown.
[0030] Figures 10 to 12 A flowchart illustrating a method for timing considerations of transmission timing in full-duplex operation according to one or more aspects of this disclosure is shown. Detailed Implementation
[0031] The network can support full-duplex operation at one or more devices. For example, the network can support subband full-duplex (SBFD) operation, where a frequency band can be split into one or more subbands for uplink (UL) communication and one or more subbands for downlink (DL) communication. In SBFD, a network entity can communicate with multiple user equipment (UEs) simultaneously in both UL and DL, while some UEs can support half-duplex operation involving communication in either UL or DL at the same time. The network can also configure one or more UEs to have multiple transmission opportunities for random access channel (RACH) procedures, such as physical RACH (PRACH) procedures. For example, in a 4-step RACH, the network entity can indicate one or more RACH (e.g., PRACH) opportunities (RO) for transmitting Msg1, while in 4-step and 2-step RACH, the network entity can indicate one or more physical uplink shared channel (PUSCH) opportunities (PO) for transmitting Msg3 or MsgA, respectively. If RO or PO is not before the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block (SSB), and if the timing is at least later than the last received symbol of the SSB... N g (For example, N g Symbol spacing, N 间隙 If the event begins with a symbol, then the timing can be considered valid. However, the validity of RO and PO may not yet be defined for SBFD communication, so there may be an opportunity to define new verification rules.
[0032] The techniques described herein enable further improvements to communication by defining effective transmission timing (e.g., RO and PO) and timing considerations in full-duplex (e.g., SBFD) communication. In some cases, conditions regarding transmission timing (e.g., location) relative to the SSB can be relaxed. For example, the network may allow RO / PO to precede the SSB, or for non-SSB-aware UEs, RO / PO and SSB may be allowed to be less than [a certain value]. N g Within the number of symbols, or allowing RO / PO and SSB to be adjacent or overlapping. Therefore, relaxing such rules provides a more flexible timing structure, which can improve network resource utilization efficiency and reduce latency in communication. In some examples, the RO / PO and SSB in SBFD symbols can involve any combination of spacing and arrangement (e.g., front) rules in SBFD-DL symbols, and in some cases, for Flexible Link (FL) symbols, can involve... N g The symbol gap spacing and RO / PO follow the SSB. In some examples, as described herein, if the RO or PO is at least later than the last received symbol of the SSB... N g (For example, N 间隙 If the signal begins with a symbol, then in some examples, this timing may be considered valid. In some cases, SBFD communication may involve minimum frequency gaps, the use of separate beams for UL and DL communication, minimum gaps between SSBs and RO / POs of the same index, and maximum transmit power on the RO / PO. In some cases, conflict handling in SBFD may involve: transmitting RACH messages or receiving overlapping SSBs on the RO / PO based on the UE specific implementation, the priority of the SSB or RO / PO, the type of RACH triggering event, or the SSB index.
[0033] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to wireless communication systems, timing diagrams, and process flows relating to timing considerations for transmission in full-duplex communication. The various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to timing considerations for transmission in full-duplex communication.
[0034] Figure 1An example of a wireless communication system 100 supporting timing considerations for transmission in full-duplex mode, according to one or more aspects of this disclosure, is illustrated. 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.
[0035] 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).
[0036] 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 Some example UE 115s are shown below. Figure 1 As shown, 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 the UE 115 or network entity 105).
[0037] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a 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. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a 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.
[0038] In some examples, network entity 105 may communicate with core network 130, communicate 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 entity 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 entity 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. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be 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, or may 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 may communicate with the core network 130 via communication link 155.
[0039] One or more network entities or network equipment in network entity 105 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, NodeB, eNodeB (eNB), next-generation NodeB or gigabit NodeB (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home NodeB, home eNodeB, 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).
[0040] 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 RTRIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 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)).
[0041] 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 upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). 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, Medium Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split 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.
[0042] 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 an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., RU 170) of IAB node 104 accessed via (e.g., referred to as a virtual IAB-MT (vIAB-MT)) DU 165. 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.
[0043] 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).
[0044] 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.
[0045] 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.
[0046] 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 set 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 using multiple DL component carriers and one or more UL component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (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)).
[0047] In some examples, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.
[0048] The communication link 125 of the wireless communication system 100 may include DL transmission (e.g., forward link transmission) from network entity 105 to UE 115, UL transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry DL communication or UL communication (e.g., in FDD mode), or may be configured to carry both DL communication and UL communication (e.g., in TDD mode).
[0049] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.
[0050] 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 one 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., in the transmission duration) and a relatively high modulation scheme order 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.
[0051] The time interval of network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, which can be, for example, a multiple of a basic time unit. The sampling period is seconds, where It can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. The time interval for organizing communication resources can be based on 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).
[0052] 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 certain 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 certain 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.
[0053] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can 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) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).
[0054] Depending on the technology, a carrier 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 technologies can be used to multiplex physical control channels and physical data channels for signaling via a DL carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can 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 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can 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 can 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 common search space set configured to transmit control information to UE 115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE 115 (e.g., a particular UE).
[0055] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.
[0056] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast to macro cells, small cells may be associated with network entities 105 operating at lower power (e.g., base station 140 operating at lower power) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.
[0057] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).
[0058] 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). The 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 in coverage areas 110 (e.g., different coverage areas).
[0059] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timing, and transmissions from different network entities (e.g., different network entities within network entity 105) can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities (e.g., different network entities within network entity 105) may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.
[0060] 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.
[0061] 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.
[0062] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.
[0063] 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 delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may 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.
[0064] 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 High 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).
[0065] 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 using 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 using licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include DL transmission, UL transmission, P2P transmission, or D2D transmission, etc.
[0066] 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.
[0067] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.
[0068] 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 specific 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 specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).
[0069] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.
[0070] The techniques described herein enable further improvements to communication by defining effective transmission timings (e.g., RO and PO) and timing considerations in full-duplex (e.g., SBFD) communication. For example, communication in wireless communication system 100 may allow RO / PO to precede SSB, or for non-SSB-aware UEs, may allow RO / PO and SSB to be less than [a certain value]. N g Within the number of symbols, or allowing RO / PO and SSB to be adjacent or overlapping. Therefore, relaxing such rules provides a more flexible timing structure, which can improve network resource utilization efficiency. In some examples, RO / PO and SSB in SBFD symbols can involve any combination of spacing and preceding rules in SBFD-DL symbols, and in some cases, for FL symbols, can involve... Ng The symbol gap spacing and RO / PO follow the SSB. In some examples, as described herein, if the RO or PO is at least later than the last received symbol of the SSB... N g (For example, N 间隙 If the signal begins with a symbol, then in some examples, this timing may be considered valid. In some cases, SBFD communication may involve minimum frequency gaps, the use of separate beams for UL and DL communication, minimum gaps between SSBs and RO / POs of the same index, and maximum transmit power on the RO / PO. In some cases, conflict handling in SBFD may involve: transmitting RACH messages or receiving overlapping SSBs on the RO / PO based on the UE specific implementation, the priority of the SSB or RO / PO, the type of RACH triggering event, or the SSB index.
[0071] Figure 2A An example of a wireless communication system 201 is shown, and Figure 2B An example of a timing diagram 202 supporting timing considerations for transmission timing in full-duplex communication is shown, according to one or more aspects of this disclosure. In some examples, the wireless communication system 201 and timing diagram 202 may implement or be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 201 may exemplify a network entity 105 (such as network entity 105-a) that can communicate with one or more UEs 115 (such as with UE 115-a). UE 115-a may include a DL communication link 205 and a UL communication link 210 with network entity 105-a. In some cases, UE 115-a and network entity 105-a may support the definition of effective transmission timing and timing considerations for full-duplex communication.
[0072] For example, wireless communication system 201 may support full-duplex and half-duplex communication. In some examples, full-duplex communication allows a device (such as network entity 105-a) to transmit and receive simultaneously using DL resource 215 and UL resource 220, while half-duplex communication allows a device (such as UE 115-a) to transmit on UL resource 220 or receive on one or more DL resources 215 at a given time. Wireless communication system 201 (e.g., wireless communication system 201, devices of wireless communication system 201, UE 115 of wireless communication system 201, network entity 105 of wireless communication system 201, etc.) may support different types of full-duplex configurations, including in-band full-duplex (IBFD), SBFD, and other types of full-duplex communication.
[0073] IBFD communication may involve transmission and reception on the same time and frequency resources, where UL and DL communication may share one or more of the same IBFD time resources, IBFD frequency resources, or both. For example, DL resource 215-a-1 and UL resource 220-a-1 may partially or completely overlap with one or more symbols and frequencies. SBFD communication (e.g., subband FDD, flexible duplex) may involve transmission and reception on different frequency resources at the same time (e.g., during one or more of the same symbols or time slots). For example, in an SBFD configuration, non-overlapping UL and DL subbands (e.g., component carriers) may be configured such that DL resource 215-a-2 may be separated from UL resources 220-a-2 and 220-a-3 in the frequency domain. In some cases, guard bands 225 (such as guard bands 225-a-1 and 225-a-2) may be included between DL resource 215 and UL resource 220 in the SBFD to protect communication from interference. Furthermore, although not shown, the wireless communication system 201 may include additional network entities 105 supporting full-duplex communication (e.g., FD network entity, FD gNB, IBFD / SBFD TDD gNB) and UEs 115 supporting half-duplex communication (e.g., HD UE) or full-duplex communication (e.g., FD UE, IBFD / SBFD aware UE), and may include multi-TRP (multi-TRP) communication. In some examples, full-duplex UE 115 may experience self-interference, while P2P communication between UEs 115 or backhaul communication between network entities may experience cross-link interference (CLI) from other UL or DL communication from the wireless communication system 201.
[0074] In some cases, for RACH operations used for SBFD-aware UEs (e.g., in RRC connected state) (or IBFD-aware UEs, or IBFD-aware UEs and SBFD-aware UEs), one or more configurations may be considered to define valid RO / PO (e.g., defining one or more RO / PO verification rules). For example, this could be for unpaired spectrum and having [something] from SIB1. ssb- PositionsInBurst Or by ServingCellConfigCommon The provided index's SSB defines multiple configurations. In some cases, network entity 105-a can use a single RACH configuration to configure one or more UEs 115 (e.g., UE 115 is provided with...). tdd-UL-DL-ConfigurationCommon In this context, the RO within the UL subband (UL-SB) of the SBFD symbol can be considered valid for an SBFD-aware UE (e.g., UE 115-a). Additionally or alternatively, network entity 105-a may use two separate RACH configurations to configure one or more UEs 115 (e.g., UE 115 is not provided). tdd-UL-DL- ConfigurationCommon These two separate RACH configurations include a first RACH configuration for non-SBFD-aware UE 115 (e.g., for TDD RACH) and a second RACH configuration for SBFD-aware UEs (e.g., for SBFD RACH). In the second configuration, the RO / PO within the UL-SB in the SBFD symbol can be considered valid for SBFD-aware UEs.
[0075] In some examples, such as configuring one or more ROs or POs in an SBFD FL symbol, using a single RACH configuration for all symbol types (e.g., SBFD symbols, DL symbols, FL symbols) can reduce signaling and overhead (or additional configuration) in the wireless communication system 201, while allowing non-SBFD-aware UEs 115 to utilize the RACH in the SBFD symbol (because non-SBFD-aware UEs may not support UL transmission in DL slots, even if those DL slots include UL subbands for SBFD). Furthermore, the single configuration may involve indications of SBFD-RO or SBFD-PO, and RO / PO validity rules may be defined in the SBFD-DL symbol (e.g., via TDD-DL-UL), and may include SSB-RO / PO mapping. In some examples, separate RACH configurations are used for each duplex type (e.g., for TDD). RO-Confg1 and for SBFD RO-Config2 This allows each RACH configuration to have separate parameters (e.g., RO / PO time and frequency resources, power configuration), while allowing independent SSB-RO / PO mapping and less ambiguity between non-SBFD-aware UEs and SBFD-aware UEs. Individual configurations may involve RO / PO validity rules for SBFD-aware UEs defined in the SBFD-DL symbol via TDD-DL-UL, and may involve the selection of RO / PO configurations by the SBFD-aware UE and the switching between RO / PO configurations.
[0076] In some examples, the wireless communication system 201 may support different RACH types, including 2-step RACH, 4-step RACH, or both. In a 4-step RACH, UE 115 and network entity 105 may exchange Msg1 (e.g., random access preamble on PRACH), Msg2 (e.g., random access response (RAR) on the Physical Downlink Shared Channel (PDSCH)), Msg3 (e.g., scheduled transmission on PUSCH), and Msg4 (e.g., contention resolution on PDSCH). As another example, a 2-step RACH may involve communication of MsgA (e.g., preamble and data, Msg1+Msg3) and MsgB (e.g., RAR and contention resolution, Msg2+Msg4). In some cases, using 2-step RACH can reduce latency and signaling overhead compared to 4-step RACH, and can support timing-free advance (TA) and unlicensed small UL packet transmission utilizing different transport block sizes and multiplexing decoding schemes. Furthermore, 2-step RACH can improve capacity and power efficiency compared to 4-step contention-based random access (CBRA) and can replace RACH-less handover. In some cases, 4-step RACH can have less performance degradation (e.g., because 2-step may not have a TA) and less PUSCH resource waste compared to 2-step RACH. Additionally, different RACH types may involve trade-offs between collision probability (e.g., the PUSCH portion of MsgA) and resource overhead (e.g., one-to-one or many-to-one mapping from preamble to PUSCH).
[0077] In some examples, RO / PO verification in SBFD (e.g., in SBFD-FL and SBFD-DL symbols or slots) can be based on one or more spacing or arrangement parameters. In some examples, if the configured RO / PO in the FL symbol is not before the SSB in the PRACH slot and is at least later than the last SSB received symbol... N g (For example, N 间隙If a RO / PO begins with a symbol, it can be considered valid. For example, UE 115-a can be configured by network entity 105-a with one or more transmission timings 230 in one or more SBFD symbols of time slot 240-a (e.g., RACH time slot, PRACH time slot), where transmission timing 230 can be an example of a candidate RO or PO for one or more RACH procedures. During a RACH procedure, UE 115-a can determine that transmission timing 230-a-1 is valid because the transmission timing is not before the last symbol of synchronization message 235-a-2, while UE 115-a can determine that transmission timing 230-a-2 is invalid because the transmission timing can precede synchronization message 235-a-1. Furthermore, UE 115-a can determine that transmission timing 230-a-1 is valid because the transmission timing can be at least later than the last symbol of synchronization message 235-a-2 (e.g., later than the latest SSB). N g A symbol (e.g., ≥) N g In some examples, N g One or more values can correspond to different preamble SCS values. Furthermore, one or more candidate indices can be provided for one or more SSBs. For example, the candidate SSB index of an SSB can correspond to the value specified in the SIB1 message or a parameter. ServingCellConfigCommon Parameters in ssb-PositionsInBurst The provided SSB index. In some cases, if set... channelAccessMode If RO / PO = "semiStatic", then RO / PO may not overlap with a group of consecutive symbols that UE 115 does not transmit before the start of the next channel occupancy time.
[0078] Define the symbol gap for effective RO / PO. N g This prevents RO / PO from interfering with RACH processes (e.g., in TDD) before SSBs (e.g., protecting PRACH from interference from other cell SSBs), and vice versa. However, while rules for valid RO / TO can be defined for one or more RACH processes (e.g., in TDD), some networks may lack definitions for valid timing relative to SBFD communication.
[0079] As described herein, wireless communication system 201 may support different authentication rules for transmission timing (e.g., RO and PO) in SBFD. For example, UE 115-a may receive control message 245-a from network entity 105-a for receiving one or more synchronization messages 235, wherein control message 245-a may indicate the configuration of one or more transmission timings 230 for transmitting random access messages 250 (such as random access message 250-a). Using one or more rules for SBFD communication (e.g., pre-configured at UE 115-a or indicated in control message 245-a or another message), UE 115-a may determine one or more valid transmission timings 230 and may receive one or more synchronization messages 235 and transmit one or more random access messages 250 accordingly. In some cases, in addition to as relative to Figures 3A to 5 In addition to the described frequency domain verification rules (e.g., RO within the UL subband), time domain constraints in SBFD may also be considered. For example, RO / PO verification may be based on the following conditions: RACH (e.g., PRACH) transmission (and the corresponding RO / PO) before or not before the SSB, and when the SSB is before the RACH transmission. N g The symbol gap, and one or more conditions used for other RACH procedures, are applicable to SBFD in DL and FL slots. Additionally, conflict handling rules between SSB and valid ROs can be considered. In some examples, as described herein, if the RO or PO is at least later than the last received symbol of the SSB... N g (For example, N 间隙 If the timing begins with a symbol, then in some examples, the timing can be considered valid.
[0080] Figure 3A and Figure 3B Examples of timing diagrams 301 and 302, respectively, are shown to consider timing considerations for transmission timing in full-duplex communication according to one or more aspects of this disclosure. In some examples, timing diagrams 301 and 302 may implement or be implemented by aspects of wireless communication systems 100 and 201 and timing diagram 202. For example, timing diagrams 301 and 302 may illustrate the timing of message reception and transmission between an SBFD-aware UE 115 and a network entity 105 supporting SBFD communication. In some cases, timing diagrams 301 and 302 may illustrate relaxed verification rules for determining valid transmission timing 230.
[0081] In some examples, the condition that the RACH procedure (e.g., PRACH transmission and the corresponding PO / RO) does not precede the SSB can be relaxed, where one or more configured ROs or POs in the SBFD-FL (or SBFD-DL) symbol can be considered valid even if the PRACH slot precedes the SSB. For example, relative to Figure 3A Transmission timings 230-b (e.g., RO or PO), including transmission timings 230-b-1, 230-b-2, 230-b-3, and 230-b-4, can be configured in UL resource 215-b-1 and can precede one or more synchronization messages 235 (e.g., one or more SSBs in an SSB burst), which include synchronization messages 235-b-1, 235-b-2 to 235-b-3 received in one or more DL resources 220-b-1. Transmission timings 230-b-1 to 230-b-4 can also be in the same time slot 240-b-1 (e.g., RACH time slot, PRACH time slot) as synchronization message 235-b-1. In some cases, each transmission timing 230 may include a symbol duration 305, such as duration 305-a-1, which may include one or more symbols preceding duration 310-a-2 of receiving synchronization message 235. By relaxing these conditions in this way, for example, many ROs or POs in the PRACH time slot can be considered valid before the SSB burst, in order to efficiently utilize one or more UL resources.
[0082] In some examples, the symbol gap can be relaxed or maintained when the SSB precedes one or more RACH processes. N g The condition is that the configuration RO / PO in an SBFD-FL (or SBFD-DL) symbol is considered valid if it starts any number of symbols later than the last SSB received symbol. In some examples, relative to Figure 3B The sending timings 230-b-5 and 230-b-6 may follow synchronization messages 235-b-4, 235-b-5 to 235-b-6, wherein the first symbol of sending timing 230-b-5 (timing of duration 305-a-2) may be less than the last symbol of synchronization message 235-b-6 (message of duration 310-a-2). N g The symbol, or it can be equal to the symbol that is later than the last symbol of synchronization message 235-b-6. N g The timing symbol can be adjacent to the synchronization message symbol, or it can be within a distance of less than [number] within the same time slot 240-b-2 (or different time slots). N gIn some cases, RACH reception in UL-SB may be... N g Interference from other cells is experienced regardless of the value, and may involve DL-UL handover gaps for one or more symbols at UE 115 (e.g., a handover gap for one symbol, a handover gap for multiple symbols). In some examples, RO / PO may be invalid if the gap between RO / PO and SSB (e.g., the gap between transmission timing 230-b-5 and synchronization message 235-b-6) is smaller than the DL-UL handover gap configured at UE (e.g., having fewer symbols than the DL-UL handover gap for one or more symbols). Furthermore, in some cases, N g (For example, it may be larger than the gap between RO / PO and SSB) and may include symbols that are larger than the DL-UL switching gap (e.g., larger than a DL-UL switching gap of 1 symbol). By relaxing the spacing in this way... N g Related conditions, for example, can reduce many delays in communication while providing a more flexible timing structure. Additionally or alternatively, based on relaxed spacing rules (e.g., N g In both the preceding and subsequent rules, RO or PO can be considered valid. For example, the last symbol of the transmission timing 230-b-4 can precede the first symbol of the synchronization message 235-b-1 by less than [a certain number of symbols]. N g A symbol.
[0083] Additionally or alternatively, for RACH in SBFD communication, one or more conditions (e.g., rules) for valid transmission timing may be the same as one or more other RACH procedures and configurations (e.g., no conditions are relaxed). For example, if RO / PO in SBFD-DL symbols are separated. N g Furthermore, if these RO / POs are listed before the SSB in the UL-SB, then these RO / POs are considered valid. Additionally, if the RO / POs in the SBFD-FL symbol are separated... N g Furthermore, if these ROs / POs are in the UL-SB prior to the SSB, then these ROs / POs can be considered valid. ROs and POs are defined as satisfying the limitations for non-SBFD-aware UE115 (e.g., N gThe spacing and the position of RO / PO before SSB ensure a corresponding RO-SSB mapping for a non-SBFD-aware UE 115, which can support communication in the FL symbol. Furthermore, when in UL-SB, one or more rules regarding the position of RO (or PO) relative to the SSB can be relaxed for different modes. For example, relaxation can be applied to one or more of idle modes (e.g., RRC_IDLE mode) and connected modes (e.g., RRC_CONNECTED mode). N g Symbol spacing and precedence rules. In some cases, conditions can be maintained for idle or connected modes (e.g., maintained in RRC_IDLE mode). N g Symbol gap). In some examples, if the timing is at least later than the last received symbol of the SSB. N g (For example, N 间隙 If a symbol is used to start a RO or PO, then RO or PO can be considered valid.
[0084] Figure 4A and Figure 4B Examples of timing diagrams 401 and 402, respectively, are shown to represent timing considerations for transmission timing in full-duplex communication according to one or more aspects of this disclosure. In some examples, timing diagrams 401 and 402 may implement aspects of wireless communication systems 100 and 201 and timing diagrams 202, 301 and 302, or be implemented by these aspects. For example, timing diagrams 401 and 402 may illustrate the timing of message transmission between an SBFD-aware UE 115 and a network entity 105 supporting SBFD communication. In some cases, timing diagrams 401 and 402 may illustrate permissible overlaps during the verification process.
[0085] For example, if as relative to Figure 3A and Figure 3B Widening the interspecies spacing as described N g Then one or more ROs or POs can overlap with one or more SSBs in time. For example, less than N g The number of symbols can be small enough to determine a temporal conflict between one or more ROs and POs and SSBs. In some cases, a conflict can be defined as the temporal overlap of ROs or POs and SSBs in one or more symbols, such as... Figure 4AAs illustrated. For example, one or more symbols of duration 305-b-1 corresponding to transmission timing 230-c-1 (before transmission timing 230-c-2) may overlap with one or more symbols of duration 310-b-1 of receiving synchronization message 235-c-2 (after synchronization message 235-c-1). Figure 4A The overlap in the text can represent conflict 405, such as conflict 405-a-1.
[0086] Additional or alternative locations, a time conflict can be defined as a time conflict between RO or PO and SSB that is less than [a certain value]. N g The symbol spacing, where N g The symbol gap can be used for one or more other RACH processes or communications (e.g., TDD). N g Same or different. For example, one or more symbols of duration 305-b-2 corresponding to transmission timing 230-c-3 (before transmission timing 230-c-4) may overlap with one or more symbols of duration 310-b-2 of receiving synchronization message 235-c-4 (after synchronization message 235-c-3), wherein Figure 4B The overlap in the text can represent conflict 405-a-2.
[0087] One or more rules or parameters can be defined to protect the SSB and ensure the correct reception of one or more RACH messages via the RO or PO. In some cases, a minimum frequency gap (e.g., guard band 225) can be defined between time-overlapping RO / PO and the SSB (e.g., to suppress interference and protect the SSB). For example, a minimum frequency gap can be defined between overlapping transmission timing 230 and synchronization message 235. In some cases, overlap can be allowed based on the correlation between the RO and the SSB. For example, overlap between signals with different indices can be allowed, where transmission timing 230-c-1 can be (e.g., index 0) RO0, and synchronization message 235-c-1 can be SSB0 of the same index, and overlapping synchronization message 235-c-2 can be (e.g., index 1) SSB1. In some cases, overlap between signals (e.g., between RO and SSB) may not be allowed. In some examples, for network entity 105 (e.g., gNB) that simultaneously transmits an SSB and receives a RACH message during RO / PO, an SSB transmission beam can be assumed or defined for the SSB and RO / PO. For example, the RO0 receive beam may differ from the SSB1 transmit beam to reduce leakage of network entity 105. One or more DL-UL handover gaps can also be defined, where RO / POs can be valid if they are separated from SSBs by at least the same number of symbols as the DL-UL handover gap. For example, UE 115 can determine whether to receive one or more SSBs, transmit one or more random access messages, or both, as long as each corresponding gap between transmission timing 230 and synchronization message 235 satisfies the handover gap value.
[0088] Minimum time gaps can also be defined for SSBs and ROs or POs with the same index. In some cases, time gaps can be used for ROs and associated SSBs (e.g., both with the same index, where there is a one-to-one mapping between SSBs and ROs). For example, if a transmission timing 230-c-3 (such as RO0) is separated from a synchronization message 235-c-1 (such as SSB0), that transmission timing can be considered valid. Additionally or alternatively, a maximum power can be defined for RACH transmissions on ROs or POs (e.g., for random access messages 250) that overlap with SSBs in time to reduce CLI. For example, the maximum power limit for RO0 can be lower than that for RO1.
[0089] For example, when a conflict is detected, conflict handling rules between the SSB and the valid RO can also be defined. For example, if the SSB overlaps with the valid RO in time (e.g., according to...), Figure 4A or Figure 4BIf the conflict definition is correct, then the half-duplex UE 115 can determine whether to receive an SSB or send a RACH message during the RO or PO. In some cases, this decision may depend on the specific implementation of the UE (e.g., similar to HD-FDD). For example, if the UE 115 does not perform any measurement of the SSB, the UE may send a RACH message on the overlapping RO. Otherwise, the UE 115 may perform the measurement. Additionally or alternatively, if no random access triggering event is detected or there is no such event (e.g., the UE 115 does not detect it), the UE 115 may instead measure the overlapping SSB. Additionally or alternatively, the UE 115 may prioritize SSB measurement regardless of additional signaling, or may instead prioritize RACH transmission (e.g., to reduce the increase in RACH latency, since the latency benefit of UL-SB can be reduced in SBFD slots with SSBs by allowing flexible RACH). In some cases, the UE 115 may make the determination based on the type of RACH (e.g., PRACH) triggering event. For example, if the triggering event is a beam fault recovery (BFR) operation or asynchronous transmission, the UE 115 can prioritize RACH transmission on the RO or PO and can measure overlapping SSBs for other triggering events.
[0090] Additionally or alternatively, UE 115 may make determinations based on SSB indices. For example, UE 115 may determine to ignore some SSB indices and transmit RACH. In some cases, UE 115 ignores SSBs and tends to transmit RACH for SSB indices corresponding to SSBs of poorer quality in the same cell (e.g., having lower received power than other SSBs) or SSBs in other serving cells (e.g., neighboring cells). UE 115 may also transmit RACH messages if the SSB index corresponds to another carrier in carrier aggregation (e.g., SCell). Otherwise, for indices associated with higher priority SSBs (e.g., higher received power, PCell), UE 115 may tend to measure the SSB and omit RACH transmission.
[0091] In some examples, for a certain type of transmission timing, the rules may be different, the same, or different for different types of RACH (e.g., 2-step RACH or 4-step RACH), different types of RACH transmission (Msg1, Msg3, or MsgA), or different types of transmission timing (e.g., RO or PO). For example, for a PO conflict with an SSB in an SBFD slot (e.g., MsgA or Msg3), the conflict handling rules may prioritize the SSB, while for a RO conflict with an SSB, the specific UE implementation may determine whether to favor SSB or RACH transmission.
[0092] In some cases, ROs and POs can be defined similarly or differently for 2-step RACH. For example, in 2-step RACH, an RO can be defined as the time and frequency resources allocated for MsgA preamble transmission, and multiple 2-step RACH UEs can share the same RO when transmitting the MsgA preamble. In some cases, different UEs can choose different preamble sequences (e.g., associated with code domain multiplexing). Additionally or alternatively, a PO can be defined as the time and frequency resources allocated for MsgA PUSCH transmission, where, to support asynchronous UL transmission in 2-step RACH, guard times and guard bands can be configured for each PO to mitigate inter-symbol interference (ISI) or inter-carrier interference (ICI). A PUSCH Resource Unit (PRU) can be defined as a PO and a DMRS port or sequence for MsgA payload transmission. In some examples, in 2-step RACH, determining a valid RO may involve mapping every consecutive index of valid ROs from the PRACH slot to a valid PO and an associated demodulation reference signal (DMRS) source. Furthermore, for SBFD or other formats, a PO can be valid if it does not overlap in time and frequency with any valid RO associated with a Type 1 RACH process or a Type 2 RACH process.
[0093] In resource allocation for the MsgA payload, the content and size of the MsgA can depend on the use case and link quality. For example, the RRC_IDLE / INACTIVE mode may involve a unique UE identifier, an RRC request, and relatively small amounts of data, while the RRC_CONNECTED mode may involve MAC-CE as well as data from the user plane (UP) and control plane (CP). Furthermore, multiple PO formats can be supported to accommodate different use cases and coverage requirements. In some cases, the MsgA may involve fixed or dynamic resource allocation (e.g., because bursty service patterns may make fixed allocation inefficient for a given payload size).
[0094] Figure 5An example of a process flow 500 supporting timing considerations for transmission timing in full-duplex communication is shown. In some examples, process flow 500 may implement aspects of or be implemented by wireless communication systems 100 and 201, timing diagrams 202, 301 and 302, or any combination thereof. For example, process flow 500 may include one or more UEs 115 (including UE 115-b) and one or more network entities 105 (including network entity 105-b), which may support further improvements to communication by defining effective transmission timings (e.g., RO and PO) and timing considerations in full-duplex communication (e.g., SBFD). In some cases, network entity 105-b may support SBFD communication with multiple UEs 115, while UE 115-b may support half-duplex communication.
[0095] In the following description of process flow 500, operations (such as reporting or providing) may be performed in a different order than those shown, or operations performed by the example device may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, or other operations may be added to process flow 500. Furthermore, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur simultaneously or at least partially concurrently.
[0096] At 505, UE 115-b may receive a control message (e.g., control message 245) indicating resources (e.g., one or more frequency or time resources of a common or two different RACH configurations) allocated for one or more random access messages associated with a random access procedure. In some examples, the resources may include full-duplex resources (e.g., SBFD resources) corresponding to one or more transmission times of the random access procedure (e.g., transmission time 230).
[0097] At 510, UE 115-b may receive a synchronization message (e.g., synchronization message 235) during the first duration.
[0098] At 515, UE 115-b may transmit a random access message associated with a random access procedure during a second duration that is different from the first duration, where the second duration may be associated with a corresponding transmission occasion of the one or more transmission occasions. For example, at 515, UE 115-b may transmit Msg1, where the transmission occasion may be an RO, and the random access procedure may be a 4-step random access procedure. Additionally or alternatively, UE 115-b may transmit Msg3 or MsgA, where the transmission occasion may be a PO, and the random access procedure may be a 4-step random access procedure or a 2-step random access procedure. The first duration corresponding to 510 (e.g., for SSB) and the second duration corresponding to 515 (e.g., for RO / PO) may be in any order or configuration, where the first duration may be before, after, adjacent to, or at least partially overlap with the second duration.
[0099] In some examples, the transmission of the random access message may be based on the validity of the transmission occasion, where the validity is based on the relationship between the first duration and the second duration. For example, at 511, UE 115-b may perform a validation procedure to determine the validity of the transmission occasion. In some examples, the validation procedure may determine that the transmission occasion is valid based on one or more symbols of the second duration being before one or more symbols of the first duration (e.g., the precondition is relaxed, so the RO / PO may be before the SSB). In some cases, UE 115-b may determine that the transmission occasion is valid based on the gap between the first duration and the second duration satisfying (e.g., >, ≥) a threshold time gap (e.g., N g ). In some examples, one or more symbols of the second duration are in the same slot in the time domain as one or more symbols of the first duration. Additionally or alternatively, UE 115-b may determine that the transmission occasion is valid based on the gap between the first duration and the second duration satisfying (e.g., >, ≥) a first threshold time gap, where the first threshold time gap is smaller than a second threshold time gap associated with a second random access procedure (e.g., N g ) (e.g., relaxing N g the symbol gap, so the RO / PO and SSB may be separated by <Ng, adjacent, or even overlapping). In some examples, the first threshold time gap may represent the number of symbols of a switching gap (e.g., a DL-UL switching gap including one or more symbols), where the transmission occasion may be valid if the transmission occasion includes at least the same number of symbols as the switching gap, and the transmission occasion may be invalid if the transmission occasion includes fewer symbols than the switching gap.
[0100] Additionally or alternatively, the UE 115-b can perform a verification process to determine that transmission timing is valid based on one or more symbols of a first duration preceding one or more symbols of a second duration and based on the gap between the first and second durations satisfying a threshold time gap (e.g., no condition is relaxed). In some examples, one or more symbols of the first duration may overlap with one or more symbols of the second duration. In some examples, symbols of the first duration may be determined to be valid based on the fact that one or more symbols of the first duration do not overlap with one or more symbols of the second duration. Additionally or alternatively, synchronization messages, random access messages, and transmission timing may be associated with threshold frequency gaps, two or more different beams, threshold time gaps for messages with the same index, minimum transmission power for random access messages, or any combination thereof. In some examples, the UE 115-b may be in connected or idle mode, where transmission timing may be valid based on whether the UE 115-b is in idle or connected mode. Additionally or alternatively, the transmission timing may include one or more UL symbols or one or more flexible (e.g., FL) symbols in UL-SB (e.g., at least one or more symbols of the transmission timing are UL symbols or flexible symbols in UL frequency subbands, and the transmission timing is at least partially within the SBFD symbol).
[0101] In some examples, at 516, network entity 105-b may determine whether UE 115-b is able to transmit during the transmission timing period, or whether it is able to receive synchronization messages; or it may find the transmission timing based on one or more rules. Network entity 105-b may do this before or after the transmission of one or more SSBs or random access messages, and one or more processes may influence or be based on the determination of network entity 105-b.
[0102] At points 520 and 525, UE 115-b may optionally receive one or more additional SSBs and transmit one or more additional random access messages during one or more random access timings. In some examples, at point 521, UE 115-b may perform another verification procedure to determine the validity of the second transmission timing. For example, the second transmission timing may involve an overlap between a second synchronization message to be received during a third duration and a second random access message associated with a second random access procedure to be transmitted during a fourth duration corresponding to the second transmission timing, wherein one or more symbols of the third duration may overlap with one or more symbols of the fourth duration.
[0103] The second verification process may involve one or more conflict resolution rules, whereby UE 115-b may determine whether to receive a second synchronization message or send a second random access message due to overlap. For example, at 510, UE 115-b may receive a second synchronization message during a third duration based on the overlap of one or more symbols of a third duration with one or more symbols of a fourth duration. In some examples, UE 115-b may receive a second synchronization message based on the second synchronization message having a higher priority than a second transmission timing, based on performing one or more measurements on the second synchronization message, or based on an index associated with the second synchronization message having a higher priority than one or more additional indices, or any combination thereof.
[0104] As another example, UE 115-b may determine to send a second random access message and suppress the reception of overlapping second synchronization messages during the second authentication process 521. For example, UE 115-b may send the second random access message during a fourth duration corresponding to the second transmission timing based on overlap. In some examples, UE 115-b may send the second random access message based on the second random access message and the second transmission timing having a higher priority than the second synchronization message, based on the occurrence of a random access triggering event, based on the random access triggering event having a higher priority than one or more additional random access triggering events, or based on an index associated with the second synchronization message having a lower priority than the one or more additional indices, or any combination thereof. Additionally or alternatively, at 526, network entity 105-b may determine whether UE 115-b is able to transmit during the second transmission timing or whether it is able to receive the second synchronization message; or may find the second transmission timing based on one or more rules.
[0105] Figure 6 A block diagram 600 illustrates a device 605 supporting timing considerations for transmission in full-duplex mode according to one or more aspects of this disclosure. Device 605 may be an example of various aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, communication manager 620), 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).
[0106] Receiver 610 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, etc., related to timing considerations for transmission in full-duplex). The information may be delivered to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.
[0107] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to timing considerations for transmission in full-duplex mode), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.
[0108] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of timing considerations for transmission timing in full-duplex as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.
[0109] In some examples, the communication manager 620, receiver 610, transmitter 615, 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).
[0110] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, 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).
[0111] In some examples, the communication manager 620 may be configured to use a receiver 610, a transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.
[0112] The communication manager 620 can support wireless communication according to the examples disclosed herein. For example, the communication manager 620 is capable of, configured to, or operable to support components for: receiving control messages indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure. The communication manager 620 is capable of, configured to, or operable to support components for: receiving synchronization messages during a first duration. The communication manager 620 is capable of, configured to, or operable to support components for: transmitting random access messages associated with a random access procedure during a second duration based on the validity of a transmission time corresponding to a second duration different from the first duration among the one or more transmission times, wherein the validity of the transmission time is based on the relationship between the first duration and the second duration.
[0113] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., controlling receiver 610, transmitter 615, communication manager 620 or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for reducing power consumption and making more efficient use of communication resources (e.g., maximizing the use of one or more radio resources) by using more flexible communication timing, including reducing the symbol gap between RO / PO and SSB and allowing RO / PO to precede one or more SSBs.
[0114] Figure 7 A block diagram 700 illustrates a device 705 supporting timing considerations for transmission in full-duplex mode according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720), 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).
[0115] Receiver 710 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 related to timing considerations for transmission in full-duplex). The information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.
[0116] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to timing considerations for transmission in full-duplex mode), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.
[0117] Device 705 or its various components may be examples of parts used to perform various aspects of timing considerations for transmission timing in full-duplex environments as described herein. For example, communication manager 720 may include control message component 725, synchronization message component 730, random access message component 735, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.
[0118] Communication manager 720 can support wireless communication according to examples disclosed herein. Control message component 725 is capable of, configured to, or operable to support components for receiving control messages indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure. Synchronization message component 730 is capable of, configured to, or operable to support components for receiving synchronization messages during a first duration. Random access message component 735 is capable of, configured to, or operable to support components for transmitting random access messages associated with a random access procedure during a second duration based on the validity of a transmission time corresponding to a second duration different from the first duration, wherein the validity of the transmission time is based on the relationship between the first duration and the second duration.
[0119] Figure 8 A block diagram 800 of a communication manager 820 supporting timing considerations for transmission timing in full-duplex operation according to one or more aspects of this disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of parts for performing various aspects of timing considerations for transmission timing in full-duplex operation as described herein. For example, the communication manager 820 may include a control message component 825, a synchronization message component 830, a random access message component 835, an authentication component 840, 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).
[0120] Communication manager 820 can support wireless communication according to examples disclosed herein. Control message component 825 is capable of, configured to, or operable to support components for receiving control messages indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure. Synchronization message component 830 is capable of, configured to, or operable to support components for receiving synchronization messages during a first duration. Random access message component 835 is capable of, configured to, or operable to support components for transmitting random access messages associated with a random access procedure during a second duration based on the validity of a transmission time corresponding to a second duration different from the first duration, wherein the validity of the transmission time is based on the relationship between the first duration and the second duration.
[0121] In some examples, the verification component 840 is capable of, configured to, or operable to support components for performing a verification process to determine that the timing of transmission is valid based on one or more symbols of the second duration preceding one or more symbols of the first duration. In some examples, the one or more symbols of the second duration are in the same time slot in the time domain as one or more symbols of the first duration.
[0122] In some examples, the verification component 840 is capable of, configured to, or operable to support components for: performing a verification process to determine that the timing of transmission is valid based on a first threshold time gap satisfied between a first duration and a second duration. In some examples, the verification component 840 is capable of, configured to, or operable to support components for: performing a verification process to determine that the timing of transmission is valid based on a first threshold time gap satisfied between a first duration and a second duration, wherein the first threshold time gap is less than a second threshold time gap associated with a second random access procedure.
[0123] In some examples, the verification component 840 is capable of, configured to, or able to operate to support components for performing the verification process to determine that the timing of transmission is valid based on the fact that one or more symbols of a first duration before one or more symbols of a second duration and the gap between the first duration and the second duration satisfy a threshold time gap associated with the second random access procedure.
[0124] In some examples, the synchronization message component 830 is capable of, configured to, or operable to support components for receiving a second synchronization message during a third duration based on the overlap of one or more symbols of a third duration that differs from a fourth duration corresponding to a second transmission timing with one or more symbols of a fourth duration. In some examples, the random access message component 835 is capable of, configured to, or operable to support components for transmitting a second random access message associated with a second random access procedure during a fourth duration corresponding to a second transmission timing based on overlap.
[0125] In some examples, to support receiving a second synchronization message or sending a second random access message, the synchronization message component 830 can, is configured, or is operable to support components for receiving the second synchronization message based on the second synchronization message having a higher priority than a second transmission timing, based on performing one or more measurements on the second synchronization message, or based on an index associated with the second synchronization message having a higher priority than one or more additional indices. In some examples, to support receiving a second synchronization message or sending a second random access message, the random access message component 835 can, is configured, or is operable to support components for sending the second random access message based on the second random access message and the second transmission timing having a higher priority than the second synchronization message, based on the occurrence of a random access triggering event, based on the random access triggering event having a higher priority than one or more additional random access triggering events, or based on an index associated with the second synchronization message having a lower priority than the one or more additional indices.
[0126] In some examples, the verification component 840 is capable, configured, or operable to support components for performing a verification process to determine that the timing of transmission is valid based on the fact that one or more symbols of a first duration do not overlap with one or more symbols of a second duration. In some examples, one or more symbols of the first duration overlap with one or more symbols of the second duration.
[0127] In some examples, synchronization messages, random access messages, and transmission timing are associated with threshold frequency gaps, two or more different beams, threshold time gaps for messages with the same index, and minimum transmission power for random access messages, or any combination thereof.
[0128] In some examples, the UE is in connected mode or idle mode.
[0129] In some examples, the transmission timing includes one or more UL symbols or one or more flexible (e.g., FL) symbols in a UL frequency subband. In some examples, the one or more UL symbols and the one or more flexible symbols include SBFD symbols (e.g., at least one or more symbols of the transmission timing are UL symbols or flexible symbols in a UL frequency subband, and the transmission timing is at least partially within an SBFD symbol).
[0130] In some examples, the timing of transmission includes the timing of random access. In some examples, the random access procedure may include a 4-step random access procedure.
[0131] In some examples, the transmission timing includes the PUSCH timing. In some examples, the random access procedure includes a 4-step random access procedure or a 2-step random access procedure.
[0132] Figure 9 A diagram of a system 900 including a device 905 supporting timing considerations for transmission in full-duplex mode, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller (e.g., I / O controller 910), a transceiver 915, one or more antennas 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 945).
[0133] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ®Or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.
[0134] In some cases, device 905 may include a single antenna. However, in other cases, device 905 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925 using a wired or wireless link as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.
[0135] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable code, computer-executable code, or processor-executable code, such as code 935. Code 935 may include instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 930 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.
[0136] At least one processor 940 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 940 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 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks that support timing considerations for transmission in full-duplex mode). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, wherein at least one processor 940 and at least one memory 930 are configured to perform the various functions described herein.
[0137] In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 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 940 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 940) and memory circuitry (which may include at least one memory 930)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 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” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 935 (e.g., processor-executable code) stored in at least one memory 930 or otherwise.
[0138] The communication manager 920 can support wireless communication according to the examples disclosed herein. For example, the communication manager 920 is capable of, configured to, or operable to support components for: receiving control messages indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure. The communication manager 920 is capable of, configured to, or operable to support components for: receiving synchronization messages during a first duration. The communication manager 920 is capable of, configured to, or operable to support components for: transmitting random access messages associated with a random access procedure during a second duration based on the validity of a transmission time corresponding to a second duration different from the first duration among the one or more transmission times, wherein the validity of the transmission time is based on the relationship between the first duration and the second duration.
[0139] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support technologies for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently (e.g., maximizing the use of one or more radio resources), improving coordination between devices, and extending battery life by using more flexible communication timing, including reducing the symbol gap between RO / PO and SSB and allowing RO / PO to precede one or more SSBs.
[0140] In some examples, the communication manager 920 may be configured to use or otherwise coordinate with the transceiver 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause the device 905 to perform various aspects of timing considerations for transmission timing in full-duplex as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.
[0141] Figure 10 A flowchart illustrating a method 1000 for timing considerations of transmission timing in full-duplex operation according to one or more aspects of this disclosure is shown. The operation of method 1000 can be implemented by a UE or its components as described herein. For example, the operation of method 1000 can be implemented by, as referenced... Figures 1 to 9The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.
[0142] At 1005, the method may include: receiving a control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure. The operation of 1005 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1005 may be provided by reference to [reference needed]. Figure 8 The control message component 825 described is used to execute this.
[0143] At point 1010, the method may include: receiving a synchronization message during a first duration. The operation of point 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of point 1010 may be derived from references... Figure 8 The described synchronous message component 830 is used to execute this.
[0144] At 1015, the method may include: transmitting a random access message associated with the random access procedure during the second duration, based on the validity of a transmission timing corresponding to a second duration different from the first duration among the one or more transmission timings, wherein the validity of the transmission timing is based on the relationship between the first duration and the second duration. The operation of 1015 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1015 may be derived from references... Figure 8 The random access message component 835 is used to execute this.
[0145] Figure 11 A flowchart illustrating a method 1100 for timing considerations of transmission timing in full-duplex operation according to one or more aspects of this disclosure is shown. Operation of method 1100 may be implemented by a UE or its components as described herein. For example, operation of method 1100 may be implemented by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.
[0146] At 1105, the method may include: receiving a control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure. Operation of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1105 may be provided by reference to [reference needed]. Figure 8 The control message component 825 described is used to execute this.
[0147] At 1110, the method may include: receiving a synchronization message during a first duration. The operation of 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1110 may be derived from references... Figure 8 The described synchronous message component 830 is used to execute this.
[0148] At 1115, the method may include: performing a verification process to determine the validity of the transmission timing based on one or more symbols of the second duration preceding one or more symbols of the first duration. The operation of 1115 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1115 may be derived from references... Figure 8 The verification component 840 is used to perform this.
[0149] At 1120, the method may include: transmitting a random access message associated with the random access procedure during the second duration, based on the validity of a transmission timing corresponding to a second duration different from the first duration among the one or more transmission timings, wherein the validity of the transmission timing is based on the relationship between the first duration and the second duration. The operation of 1120 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1120 may be derived from references... Figure 8 The random access message component 835 is used to execute this.
[0150] Figure 12 A flowchart illustrating a method 1200 for timing considerations of transmission timing in full-duplex operation according to one or more aspects of this disclosure is shown. Operation of method 1200 may be implemented by a UE or its components as described herein. For example, operation of method 1200 may be implemented by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.
[0151] At 1205, the method may include: receiving a control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure. Operation of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1205 may be provided by reference to... Figure 8 The control message component 825 described is used to execute this.
[0152] At 1210, the method may include: receiving a synchronization message during a first duration. The operation of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be derived from references... Figure 8 The described synchronous message component 830 is used to execute this.
[0153] At 1215, the method may include: performing a verification process to determine the validity of the transmission timing based on a first threshold time gap satisfied by a gap between a first duration and a second duration, the first threshold time gap being less than a second threshold time gap associated with a second random access procedure. The operation of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1215 may be provided by reference to [reference needed]. Figure 8 The verification component 840 is used to perform this.
[0154] At 1220, the method may include: transmitting a random access message associated with the random access procedure during the second duration, based on the validity of a transmission timing corresponding to a second duration different from the first duration among the one or more transmission timings, wherein the validity of the transmission timing is based on the relationship between the first duration and the second duration. The operation of 1220 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1220 may be derived from references... Figure 8 The random access message component 835 is used to execute this.
[0155] The following provides an overview of the various aspects of this disclosure:
[0156] Aspect 1: A method for wireless communication by a UE, the method comprising: receiving a control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure; receiving a synchronization message during a first duration; and transmitting the random access messages associated with the random access procedure during a second duration, based at least in part on the validity of a transmission time corresponding to a second duration different from the first duration among the one or more transmission times, wherein the validity of the transmission time is based at least in part on a relationship between the first duration and the second duration.
[0157] Aspect 2: According to the method of aspect 1, the method further includes: performing a verification process to determine, at least in part, that the timing of transmission is valid based on one or more symbols of the second duration preceding one or more symbols of the first duration.
[0158] Aspect 3: The method according to any one of aspects 1 to 2, wherein one or more symbols of the second duration are in the same time slot in the time domain as one or more symbols of the first duration.
[0159] Aspect 4: The method according to any one of aspects 1 to 3, the method further comprising: performing a verification process to determine that the transmission timing is valid based at least in part on the gap between the first duration and the second duration satisfying a first threshold time gap.
[0160] Aspect 5: The method according to any one of aspects 1 to 4, the method further comprising: performing a verification process to determine that the transmission timing is valid based at least in part on the fact that one or more symbols of the first duration precede one or more symbols of the second duration and the gap between the first duration and the second duration satisfies a threshold time gap associated with a second random access procedure.
[0161] Aspect 6: The method according to any one of aspects 1 to 5, the method further comprising: receiving a second synchronization message during the third duration based at least in part on the overlap of one or more symbols of a third duration different from the fourth duration corresponding to the second transmission timing with one or more symbols of the fourth duration; or transmitting a second random access message associated with a second random access procedure during the fourth duration corresponding to the second transmission timing based at least in part on the overlap.
[0162] Aspect 7: According to the method of Aspect 6, receiving the second synchronization message or sending the second random access message comprises: receiving the second synchronization message at least partially based on the second synchronization message having a higher priority than the second transmission timing, at least partially based on performing one or more measurements on the second synchronization message, or at least partially based on an index associated with the second synchronization message having a higher priority than one or more additional indices; or sending the second random access message at least partially based on the second random access message and the second transmission timing having a higher priority than the second synchronization message, at least partially based on the occurrence of a random access triggering event, at least partially based on the random access triggering event having a higher priority than one or more additional random access triggering events, or at least partially based on the index associated with the second synchronization message having a lower priority than the one or more additional indices.
[0163] Aspect 8: The method according to any one of aspects 1 to 7, the method further comprising: performing a verification process to determine, at least in part, that the transmission timing is valid based on the fact that one or more symbols of the first duration do not overlap with one or more symbols of the second duration.
[0164] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the synchronization message, the random access message, and the transmission timing are associated with a threshold frequency gap, two or more different beams, a threshold time gap for messages with the same index, and a minimum transmission power for the random access message, or any combination thereof.
[0165] Aspect 10: The method according to any one of aspects 1 to 9, wherein the UE is in connected mode or idle mode.
[0166] Aspect 11: The method according to any one of aspects 1 to 10, wherein the transmission timing includes one or more UL symbols or one or more flexible symbols in a UL frequency subband, wherein the one or more UL symbols and the one or more flexible symbols include SBFD symbols.
[0167] Aspect 12: The method according to any one of aspects 1 to 11, wherein the transmission timing includes RO, and the random access procedure includes a 4-step random access procedure.
[0168] Aspect 13: The method according to any one of Aspects 1 to 11, wherein the transmission timing includes PO, and the random access procedure includes a 4-step random access procedure or a 2-step random access procedure.
[0169] Aspect 14: 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 13.
[0170] Aspect 15: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 13.
[0171] Aspect 16: 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 13.
[0172] 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 also possible. Furthermore, aspects from two or more of these methods may be combined.
[0173] 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.
[0174] 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.
[0175] 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 combined 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.
[0176] 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.
[0177] 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. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. 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.
[0178] 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".
[0179] 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” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as 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” can refer to any or all of the 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".
[0180] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.
[0181] 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 of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.
[0182] 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 "serving 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 of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.
[0183] 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 control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure; Receive synchronization messages during the first duration; as well as Random access messages associated with the random access procedure are transmitted during the second duration, based at least in part on the validity of a transmission timing corresponding to a second duration that is different from the first duration, wherein the validity of the transmission timing is based at least in part on the relationship between the first duration and the second duration.
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: Performing a verification process to determine the timing of the transmission is effective, at least in part, based on the fact that one or more symbols of the second duration precede one or more symbols of the first duration.
3. The UE according to claim 2, wherein one or more symbols of the second duration are in the same time slot as one or more symbols of the first duration in the time domain.
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 verification process determines that the timing of the transmission is valid based at least in part on the fact that the gap between the first duration and the second duration satisfies a first threshold time gap.
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 verification process determines that the transmission timing is valid based at least in part on the fact that one or more symbols of the first duration precede one or more symbols of the second duration and the gap between the first duration and the second duration satisfy a threshold time gap associated with the second random access procedure.
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: The second synchronization message is received during the third duration, at least in part, based on the overlap of one or more symbols of a third duration that differs from the fourth duration corresponding to the second transmission timing, with one or more symbols of the fourth duration; or The second random access message associated with the second random access procedure is transmitted during the fourth duration corresponding to the second transmission timing, based at least in part on the overlap.
7. The UE of claim 6, wherein, in order to receive the second synchronization message or to send the second random access message, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The second synchronization message is received at least in part based on the fact that the second synchronization message has a higher priority than the second transmission timing, at least in part based on performing one or more measurements on the second synchronization message, or at least in part based on the fact that the index associated with the second synchronization message has a higher priority than one or more additional indices; or The second random access message is sent at least in part based on the second random access message and the second transmission timing having a higher priority than the second synchronization message, at least in part based on the occurrence of a random access triggering event, at least in part based on the random access triggering event having a higher priority than one or more additional random access triggering events, or at least in part based on the index associated with the second synchronization message having a lower priority than the one or more additional indices.
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 verification process is performed to determine that the timing of the transmission is valid, based at least in part on the fact that one or more symbols of the first duration do not overlap with one or more symbols of the second duration.
9. The UE of claim 1, wherein the synchronization message, the random access message, and the transmission timing are associated with a threshold frequency gap, two or more different beams, a threshold time gap for messages with the same index, and a minimum transmission power for the random access message, or any combination thereof.
10. The UE according to claim 1, wherein the UE is in connected mode or idle mode.
11. The UE of claim 1, wherein the transmission timing includes one or more uplink symbols or one or more flexible symbols in the uplink frequency subband, wherein the one or more uplink symbols and the one or more flexible symbols include subband full-duplex symbols.
12. The UE according to claim 1, wherein: The transmission timing includes random access timing, and The random access procedure consists of four steps.
13. The UE according to claim 1, wherein: The transmission timing includes the Physical Uplink Shared Channel (PUSCH) timing, and The random access procedure includes either a 4-step random access procedure or a 2-step random access procedure.
14. A method for wireless communication by a user equipment (UE), the method comprising: Receive a control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure; Receive synchronization messages during the first duration; as well as Random access messages associated with the random access procedure are transmitted during the second duration, based at least in part on the validity of a transmission timing corresponding to a second duration that is different from the first duration, wherein the validity of the transmission timing is based at least in part on the relationship between the first duration and the second duration.
15. The method according to claim 14, further comprising: Performing a verification process to determine the timing of the transmission is effective, at least in part, based on the fact that one or more symbols of the second duration precede one or more symbols of the first duration.
16. The method of claim 15, wherein one or more symbols of the second duration are in the same time slot in the time domain as one or more symbols of the first duration.
17. The method of claim 14, further comprising: The verification process determines that the timing of the transmission is valid based at least in part on the fact that the gap between the first duration and the second duration satisfies a first threshold time gap.
18. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: Receive a control message indicating resources allocated for one or more random access messages associated with a random access procedure, the resources including full-duplex resources corresponding to one or more transmission times of the random access procedure; Receive synchronization messages during the first duration; as well as Random access messages associated with the random access procedure are transmitted during the second duration, based at least in part on the validity of a transmission timing corresponding to a second duration that is different from the first duration, wherein the validity of the transmission timing is based at least in part on the relationship between the first duration and the second duration.
19. The non-transitory computer-readable medium of claim 18, wherein the instructions are further executable by the one or more processors to: Performing a verification process to determine the timing of the transmission is effective, at least in part, based on the fact that one or more symbols of the second duration precede one or more symbols of the first duration.
20. The non-transitory computer-readable medium of claim 19, wherein one or more symbols of the second duration are in the same time slot in the time domain as one or more symbols of the first duration.
