Time division duplex and sub-band full duplex symbol transition configuration
By exchanging information elements between the base station and user equipment (UE), indicating the transition protection symbols for TDD symbols to SBFD symbols and SBFD symbols to TDD symbols, the problem of transition point indication and configuration in the prior art is solved, and effective management of scheduling UEs across different subbands is realized, and the flexibility and efficiency of network operations are improved.
Patent Information
- Application Number
- CN202411731065.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-10-31
- Filing Date
- 2024-11-29
- Publication Date
- 2025-06-03
AI Technical Summary
In the transition between time division duplex (TDD) symbols and subband full duplex (SBFD) symbols, it is difficult for the prior art to effectively manage the indication and configuration of transition points, especially when scheduling user equipment (UEs) across different subbands.
By exchanging information elements between the base station and the user equipment (UE), a protection symbol for the transition, including a first protection symbol and a second protection symbol, is indicated, respectively, for the transition from the TDD symbol to the SBFD symbol and from the SBFD symbol to the TDD symbol. The duration and offset of these protection symbols are determined by specific parameters (such as TDD2SBFD_Guard, SBFD2TDD_Guard, Offset_transition1_1, Offset_transition1_2).
Effective indication and configuration of transition points are realized, ensuring the feasibility of scheduling UEs across different subbands in SBFD symbols/time slots, and improving the flexibility and efficiency of network operations.
Smart Images

Figure CN120090779A_ABST
Abstract
Description
[0001] Cross - Reference to Related Applications
[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 605,151, titled "Time Division Duplex and Sub - band Full Duplex Symbol Transition Configuration", filed on December 1, 2023, and U.S. Non - Provisional Patent Application No. 18 / 933,889, titled "Time Division Duplex and Sub - band Full Duplex Symbol Transition Configuration", filed on October 31, 2024. The disclosures of these applications are hereby incorporated by reference in their entireties for all purposes. Field of the Invention
[0003] This application relates to the field of wireless technologies, and more particularly to operations for transitions between time - division duplex (TDD) symbols and sub - band full - duplex (SBFD) symbols. Background Art
[0004] Third Generation Partnership Project (3GPP) networks provide different duplex configurations for time slots to be used for transmission. The duplex configuration defines which times and / or frequencies are available for the transmission of different signals. A base station and a user equipment (UE) may exchange transmissions for configuring the duplex configuration of a time slot. Brief Description of the Drawings
[0005] Figure 1 An example time - slot arrangement according to some embodiments is illustrated.
[0006] Figure 2 An example information element providing an indication of a protected symbol according to some embodiments is illustrated.
[0007] Figure 3 An example of a symbol arrangement according to some embodiments is illustrated.
[0008] Figure 4 An example of a symbol arrangement according to some embodiments is illustrated.
[0009] Figure 5 An example information element for Methods 1 - 4 according to some embodiments is illustrated.
[0010] Figure 6 An example transmission arrangement for a user equipment (UE) according to some embodiments is illustrated.
[0011] Figure 7Illustrates an example signaling diagram according to some embodiments.
[0012] Figure 8 Illustrates an example time slot arrangement according to some embodiments.
[0013] Figure 9 Illustrates an example time slot representation according to some embodiments.
[0014] Figure 10 Illustrates an example time slot representation according to some embodiments.
[0015] Figure 11 Illustrates an example time slot representation according to some embodiments.
[0016] Figure 12 Illustrates an example process for configuring one or more transitions between sub - band full - duplex (SBFD) symbols and non - SBFD symbols according to some embodiments.
[0017] Figure 13 Illustrates an example process for configuring one or more transitions between SBFD symbols and non - SBFD symbols according to some embodiments.
[0018] Figure 14 Illustrates an example process for scheduling transmissions extended to both SBFD symbols and non - SBFD symbols according to some embodiments.
[0019] Figure 15 Illustrates an example UE according to some embodiments.
[0020] Figure 16 Illustrates an example next - generation base station (gNB) according to some embodiments. Detailed Description
[0021] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, for purposes of illustration and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, technologies, etc., in order to provide a thorough understanding of various aspects of the embodiments. However, it will be apparent to those skilled in the art who have benefited from the present disclosure that various aspects of the embodiments may be practiced in other examples that depart from these specific details. In some cases, descriptions of well - known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary details. For the purposes of this document, the phrase “A or B” means (A), (B), or (A and B); and the phrase “based on A” means “at least partially based on A,” e.g., it may be “only based on A” or it may be “partially based on A.”
[0022] The following is a glossary that can be used in this disclosure.
[0023] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or group), or memories (shared, dedicated, or group) configured to provide the functions, application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable system on chips (SoCs)), digital signal processors (DSPs), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of the hardware element and the program code may be referred to as a particular type of circuit.
[0024] As used herein, the term "processor circuit" refers to, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating on computer-executable instructions (such as program code, software modules, and / or functional procedures).
[0025] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.
[0026] As used herein, the term "user equipment" or "UE" refers to a device of a remote user having radio communication capabilities and capable of describing network resources in a communication network. Additionally, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device including a wireless communication interface.
[0027] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Further, the term "computer system" or "system" may refer to multiple computing devices or multiple computing systems that are communicatively coupled to each other and are configured to share computing resources or networking resources.
[0028] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as a computing device, a mechanical device, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and applications, workload units, etc. "Hardware resources" may refer to computing, storage, or networking resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, or networking resources provided by a virtualization infrastructure to applications, devices, systems, etc. The term "network resource" or "communication resource" may refer to resources that a computing device / system can access via a communication network. The term "system resource" may refer to any kind of shared entity that provides services and may include computing resources or networking resources. System resources may be regarded as a set of coherent functions, network data objects, or services that can be accessed via a server, where such system resources reside on a single host or multiple hosts and can be clearly identified.
[0029] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to convey data or a data stream. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier", or any other similar term that represents the path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection established between two devices for sending and receiving information.
[0030] As used herein, the terms "instantiate", "instantiation", etc. refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.
[0031] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other via a communication channel, link, interface, or reference point.
[0032] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networked hardware, network equipment, network node, virtualized network function, etc.
[0033] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to each content of an information element, or a data element that contains content. An information element may include one or more additional information elements.
[0034] As used herein, the term "at least partially based on" may indicate that an item is based only on another item and / or on an item of another item and one or more additional items. For example, in an embodiment, determining item 1 at least partially based on item 2 may indicate determining item 1 based only on item 2 and / or determining item 1 based on item 2 and one or more other items.
[0035] The term "base station" as used herein may refer to Node B, evolved Node B (eNB), next-generation Node B (gNB), and / or radio access network node. In addition, the term "gNB" as used herein may be interpreted as a base station, such that the term gNB may refer to a base station, eNB, gNB, and / or radio access network node.
[0036] The term "symbol" or "symbols" as used herein may be prefixed, such as SBFD symbol. The prefix may indicate the use for which one or more symbols are configured. For example, an SBFD symbol may refer to a symbol configured for SBFD operation. A non-SBFD symbol may refer to a symbol configured for non-SBFD operation.
[0037] With the advancement of network technology, different methods for configuring time slots may be beneficial to network operation. Methods for transitioning between time division duplex (TDD) symbols and sub-band full duplex (SBFD) symbols for configuring time slots are described herein.
[0038] SBFD and Dynamic TDD
[0039] As part of the enhancements in Release 18 (Rel-18) (as well as the sixth generation (6G)), full duplex (FD) operation within the TDD band is being discussed. The FD described herein mainly refers to the case where (at least) the next-generation base station (gNB) operates in full duplex, that is, transmits and receives simultaneously. In Rel-18, dynamic TDD and full duplex operation at the gNB will be studied under the assumption of a half-duplex UE.
[0040] In Figure 1 an example of full duplex operation is shown. Specifically, Figure 1Illustrates an example time slot arrangement 100 according to some embodiments. The time slot arrangement 100 illustrates an example of resource assignment in different time slots. The x-axis of the time slot arrangement 100 corresponds to time, while the y-axis of the time slot arrangement 100 corresponds to frequency.
[0041] The time slot arrangement 100 includes an example TDD time slot arrangement 102. The TDD time slot arrangement 102 illustrates an example of resource assignment for time slots configured with TDD and FD operations. The TDD time slot may have a resource assignment for the entire duration of the TDD time slot.
[0042] In the illustrated embodiment, the TDD time slot arrangement 102 includes a downlink (DL) assignment portion 104, where the resources within the DL assignment portion 104 will be used for DL transmission. Additionally, the illustrated TDD time slot arrangement 102 includes a guard band 106, where the resources within the guard band 106 may not be used for transmission. The illustrated TDD time slot arrangement 102 also includes an uplink (UL) assignment portion 108, where the resources within the UL assignment portion 108 will be used for UL transmission.
[0043] The guard band 106 may separate the DL assignment portion 104 from the UL assignment portion 108 to provide a transition between the assignment portions. Although the TDD time slot arrangement 102 illustrates an example resource assignment arrangement, it should be noted that in other embodiments, the TDD time slots in FD operation may have other assignment arrangements including a DL assignment portion, a UL assignment portion, and / or a guard band.
[0044] The time slot arrangement 100 includes an example SBFD time slot arrangement 150. The SBFD time slot arrangement 150 illustrates an example of resource assignment for time slots configured with SBFD and FD operations. The SBFD time slot may have a resource assignment for the entire sub-band of the SBFD time slot.
[0045] In the illustrated embodiment, the SBFD time slot arrangement 150 includes a first DL assignment portion 152 and a second DL assignment portion 160, where the resources within the first DL assignment portion 152 and the second DL assignment portion 160 will be used for DL transmission. Additionally, the illustrated SBFD time slot arrangement 150 includes a first guard band 154 and a second guard band 158, where the resources within the first guard band 154 and the second guard band 158 may not be used for transmission. The illustrated SBFD time slot arrangement 150 also includes a UL assignment portion 156, where the resources within the UL assignment portion 156 will be used for UL transmission.
[0046] The first guard band 154 can separate the first DL assignment part 152 and the UL assignment part 156 to avoid interference between signals transmitted via resources in the first DL assignment part 152 and signals transmitted via resources in the UL assignment part 156. The second guard band 158 can separate the second DL assignment part 160 and the UL assignment part 156 to avoid interference between signals transmitted via resources in the second DL assignment part 160 and signals transmitted via resources in the UL assignment part 156. Although the SBFD time slot arrangement 150 illustrates an example resource assignment arrangement, it should be noted that in other embodiments, the SBFD time slots in the FD operation may have other assignment arrangements including DL assignment parts, UL assignment parts, and / or guard bands.
[0047] Problem statement
[0048] The Radio Access Network Working Group 1 (RAN1) has studied the feasibility and possible enhancements required for SBFD operation at the next-generation Node B (gNB). It has been concluded that at most two transition points within the TDD UL / DL mode cycle (including one transition point from a non-SBFD symbol to an SBFD symbol and one transition point from an SBFD symbol to a non-SBFD symbol) can be considered such that the transition points can be aligned with the time slot boundaries or the starting points within the time slots.
[0049] This disclosure describes the open aspects of the indication / configuration of the transition points, and whether / how user equipment (UE) can be scheduled across different subbands in SBFD symbols / time slots. For the indication / configuration of the transition points, the aspects described herein include guard symbols required for transitioning to / from SBFD symbols, and / or cell-specific to UE-specific components and indications. For whether / how UE can be scheduled across different subbands in SBFD symbols / time slots, the aspects described herein include the requirements and procedures for scheduling UE in the UL subband within the indicated SBFD symbol / time slot at time T 0 and in the DL subband at time T 1 and the requirements and procedures for scheduling UE in the upper DL subband within the indicated SBFD symbol / time slot at time T 0 and in the lower DL subband at time T 1 in the indicated SBFD symbol / time slot.
[0050] Indication of guard symbols for transitions
[0051] For Method 1-1, the indication of the guard symbols required for the transition between traditional TDD symbols and traditional SBFD symbols can be part of the SBFD configuration indication within the TDD-UL-DL-Pattern. For example, the base station can generate and / or transmit a message that includes an indication of the guard symbols required for transmission between TDD symbols and SBFD symbols. The indication can be included within the TDD-UL-DL-Pattern provided in the message as part of the SBFD configuration indication. The base station can send the message to the UE that is to implement the required guard symbols.
[0052] For each UL-DL TDD pattern, the UE can be configured with TDD parameters, including a reference subcarrier spacing parameter (referenceSubcarrierSpacing), a transmission periodicity parameter (dl-UL-TransmissionPeriodicity), a number of DL slots parameter (nrofDownlinkSlot), a number of DL symbols parameter (nrofDownlinkSymbol), a number of UL slots parameter (nrofUplinkSlot), and / or a number of UL symbols parameter (nrofUplinkSymbol). These parameters can define a TDD pattern with a periodicity P that starts with nrofDownlinkSlot and ends with nrofUplinkSlots, and in between there are nrofDownlinkSymbol, flexible symbols, and nrofUplinkSymbol, all of which have a reference subcarrier spacing (SCS) given by referenceSubcarrierSpacing.
[0053] The new signaling may include a first transition offset parameter (Offset_transition1_1) and / or a second transition offset parameter (Offset_transition1_2). Offset_transition1_1 may indicate (as an offset starting from each periodic P) the first time when the gNB transitions from non - SBFD to SBFD. This offset may be defined by a first slot offset parameter (Offset_slot) and / or a first symbol offset parameter (Offset_symbl). Offset_transition1_2 may indicate (as an offset starting from each periodic P) the first time when the gNB transitions from SBFD to non - SBFD. This offset may be defined by a second slot offset parameter (Offset_slot) and / or a second symbol offset parameter (Offset_symbl). A first guard time parameter (TDD2SBFD_Guard) and a second guard time parameter (SBFD2TDD_Guard) may respectively represent the guard time (in milliseconds (ms)) required for the operation mode switch at the gNB.
[0054] Figure 2 An example information element 200 that provides an indication of a guard symbol according to some embodiments is illustrated. For example, the information element 200 may provide information for configuring the UE for an operation mode switch. The information element 200 may be sent from the base station to the UE in a message including configuration information.
[0055] The information element 200 includes a common configuration information element 202 (TDD - UL - DL - ConfigCommon) for configuring the UE. The common configuration information element 202 may include one or more mode fields 204. In the illustrated embodiment, the mode field value 206 of one of the mode fields 204 has the value of TDD - UL - DL - Pattern.
[0056] The information element 200 includes a mode information element 208 (TDD - UL - DL - Pattern). The mode field value 206 having the value of TDD - UL - DL - Pattern may indicate that the mode information element 208 will be used to configure the UE that receives the common configuration information element 202. For example, the UE may identify the common configuration information element 202 within the message received from the base station and determine that the mode information element 208 will be used to configure the UE based on the mode field value 206 being TDD - UL - DL - Pattern. The mode information element 208 may provide configuration information for the transition between TDD symbols and SBFD symbols.
[0057] The mode information element 208 may include a transmission periodicity parameter 210 (dl-UL-TransmissionPeriodicity), a number of DL slot parameter 212 (nrofDownlinkSlot), a number of DL symbol parameter 214 (nrofDownlinkSymbol), a number of UL slot parameter 216 (nrofUplinkSlot), and / or a number of UL symbol parameter 218 (nrofUplinkSymbol). These parameters may define UL assignments and / or DL assignments within one or more corresponding time slots for a UE receiving the common configuration information element 202.
[0058] The mode information element 208 may further include information on one or more guard symbols to be used when transitioning between non-SBFD symbols and SBFD symbols. In the illustrated embodiment, the information on the guard symbols may apply to the transition between TDD symbols and SBFD symbols. The information on one or more guard symbols may indicate the time when the UE does not send signals to the base station and / or does not expect to receive signals from the base station.
[0059] The illustrated mode information element 208 includes a first guard symbol parameter 220. The first guard symbol parameter 220 may provide information on the guard symbols associated with the transition. In the illustrated embodiment, the first guard symbol parameter 220 provides information on the guard symbols for the transition from TDD symbols to SBFD symbols, as indicated by the TDD2SBFD_Guard parameter 222 within the first guard symbol parameter 220. The TDD2SBFD_Guard parameter 222 may have a value indicating the duration of the guard symbols when implementing the transition from TDD symbols to SBFD symbols.
[0060] The first guard symbol parameter 220 may further indicate the offset at which the guard symbols begin. For example, the first guard symbol parameter 220 may include a slot offset parameter 224 (Offset_slot) and / or a symbol offset parameter 226 (Offset_symbl). The slot offset parameter 224 and the symbol offset parameter 226 may indicate the number of slots and the number of symbols by which the start of the guard symbols will be offset from the start of each period. For example, the start of the guard symbols will be offset by the number of slots indicated by the value of the slot offset parameter 224 plus the number of symbols indicated by the value of the symbol offset parameter 226. A UE receiving the common configuration information element 202 may determine that the guard symbols for the TDD symbol to SBFD symbol transition will begin at the offset indicated by the slot offset parameter 224 and the symbol offset parameter 226, and that the guard symbols will extend for the duration indicated by the value of the TDD2SBFD_Guard parameter 222.
[0061] The exemplary pattern information element 208 includes a second guard symbol parameter 228. The second guard symbol parameter 228 may provide information on the guard symbol associated with the transition. In the exemplary embodiment, the second guard symbol parameter 228 provides information on the guard symbol for the transition from an SBFD symbol to a TDD symbol, as indicated by the SBFD2TDD_Guard parameter 230 within the second guard symbol parameter 228. The SBFD2TDD_Guard parameter 230 may have a value indicating the duration of the guard symbol when the transition from an SBFD symbol to a TDD symbol is implemented.
[0062] The second guard symbol parameter 228 may also indicate the offset at which the guard symbol starts. For example, the second guard symbol parameter 228 may include a time slot offset parameter 232 (Offset_slot) and / or a symbol offset parameter 234 (Offset_symbl). The time slot offset parameter 232 and the symbol offset parameter 234 may indicate the number of time slots and the number of symbols by which the start of the guard symbol will be offset from the start of each period. For example, the start of the guard symbol will be offset by the number of time slots indicated by the value of the time slot offset parameter 232 plus the number of symbols indicated by the value of the symbol offset parameter 234. A UE receiving the common configuration information element 202 may determine that the guard symbol for the transition from an SBFD symbol to a TDD symbol will start at the offset indicated by the time slot offset parameter 232 and the symbol offset parameter 234, and that the guard symbol will extend for the duration indicated by the value of the TDD2SBFD_Guard parameter 230.
[0063] Figure 3 An example of a symbol arrangement 300 according to some embodiments is illustrated. The symbol arrangement 300 illustrates the transition from a DL symbol to a UL symbol according to some embodiments.
[0064] The symbol arrangement 300 may be defined by a TDD-UL-DL-ConfigCommon information element such as the common configuration information element 202 ( Figure 2 ). In the exemplary embodiment, the symbol arrangement 300 may be defined using an SCS (referenceSubcarrierSpacing) of 30 kilohertz (kHz), a periodicity (dl-UL-TransmissionPeriodicity) of 5 ms, a number of DL time slots (nrofDownlinkSlot) of 7, a number of DL symbols (nrofDownlinkSymbol) of 0, a number of UL time slots (nrofUplinkSlot) of 2, and a number of UL symbols (nrofUplinkSymbol) of 2.
[0065] The symbol arrangement 300 may include one or more time slots. In the illustrated embodiment, the symbol arrangement 300 includes a first time slot 302, a second time slot 304, a third time slot 306, a fourth time slot 308, a fifth time slot 310, a sixth time slot 312, a seventh time slot 314, an eighth time slot 316, a ninth time slot 318, and a tenth time slot 320. According to the information provided by the parameters within the TDD-UL-DL-ConfigCommon information element, the symbol arrangement 300 may include 7 time slots configured for DL transmission, as indicated by the representation of the first time slot 302 to the seventh time slot 314 being shown as unfilled. Additionally, the symbol arrangement may include 2 time slots and 2 symbols configured for UL transmission, as indicated by the representation of the ninth time slot 318, the tenth time slot 320, and a portion of the eighth time slot 316 being shown as filled with diagonal crosshatching. The time slots and symbols between the DL-configured time slots and symbols and the UL-configured time slots and symbols may be configured to be flexible, as indicated by the representation of a portion of the eighth time slot 316 being shown as filled with diagonals. The flexibly configured time slots and symbols may be used for UL transmission and / or DL transmission.
[0066] Figure 4 An example of a symbol arrangement 400 according to some embodiments is illustrated. The symbol arrangement 400 illustrates the transition from DL symbols to UL symbols according to some embodiments. Additionally, the symbol arrangement 400 illustrates the transition between TDD symbols and SBFD symbols. The symbol arrangement 400 illustrates guard symbols for the transition, as defined according to the methods described herein.
[0067] The symbol arrangement 400 may be provided by a TDD-UL-DL-ConfigCommon information element such as the common configuration information element 202( Figure 2)Definition. In an exemplary embodiment, the symbol arrangement 300 can be defined using an SCS (reference Subcarrier Spacing) of 30 kHz, a periodicity (dl-UL-TransmissionPeriodicity) of 5 ms, a number of DL slots (nrofDownlinkSlot) of 7, a number of DL symbols (nrofDownlinkSymbol) of 0, a number of UL slots (nrofUplinkSlot) of 2, and a number of UL symbols (nrofUplinkSymbol) of 2. Additionally, the symbol arrangement 400 is defined to have guard symbols for transitions between TDD symbols and SBFD symbols. For example, the symbol arrangement 400 in the exemplary embodiment is defined to have a guard symbol for the transition from a TDD symbol to an SBFD symbol, which has an offset (Offset_transition1_1) of 2 slots and 7 symbols ({Offset_slot = 2, Offset_symbl = 7}) and a duration (TDD2SBFD_Guard) of 0.25 ms. Additionally, the symbol arrangement 400 in the exemplary embodiment is defined to have a guard symbol for the transition from an SBFD symbol to a TDD symbol, which has an offset (Offset_transition1_2) of 5 slots and 0 symbols ({Offset_slot = 5, Offset_symbl = 0}) and a duration (SBFD2TDD_Guard) of 0.25 ms.
[0068] The symbol arrangement 400 can include one or more time slots. In the exemplary embodiment, the symbol arrangement 400 includes a first time slot 402, a second time slot 404, a third time slot 406, a fourth time slot 408, a fifth time slot 410, a sixth time slot 412, a seventh time slot 414, an eighth time slot 416, a ninth time slot 418, and a tenth time slot 420. The symbol arrangement 400 can have the same UL and DL symbol arrangements as the symbol arrangement 300 ( Figure 3 ). However, the symbol arrangement 400 also includes a transition from a TDD symbol to an SBFD symbol and a transition from an SBFD symbol to a TDD symbol.
[0069] The symbol arrangement 400 may include a first protection symbol 422, as indicated by the vertical / horizontal crosshatch fill. The first protection symbol 422 may correspond to the transition from a TDD symbol to an SBFD symbol. The first protection symbol 422 may be defined by Offset_transition1_1. For example, the first protection symbol 422 may be offset 2 time slots and 7 symbols from the start of the period (which occurs at the start of the first time slot 402), as defined by Offset_transition1_1. Thus, the first protection symbol 422 is located within the third time slot 406 at a position 2 time slots and 7 symbols from the start of the period. The duration of the first protection symbol 422 may be 0.25 ms, as defined by Offset_transition1_1.
[0070] The symbol arrangement 400 may include a second protection symbol 424, as indicated by the vertical / horizontal crosshatch fill. The second protection symbol 424 may correspond to the transition from an SBFD symbol to a TDD symbol. The second protection symbol 424 may be defined by Offset_transition1_2. For example, the second protection symbol 424 may be offset 5 time slots and 0 symbols from the start of the period (which occurs at the start of the first time slot 402), as defined by Offset_transition1_2. Thus, the second protection symbol 424 is located within the sixth time slot 412 at a position 5 time slots and 0 symbols from the start of the period. The duration of the second protection symbol 424 may be 0.25 ms, as defined by Offset_transition1_2.
[0071] The symbol before the first protection symbol 422 may be a TDD symbol. The first transition may occur during the first protection symbol 422 such that the symbol after the first protection symbol 422 is an SBFD symbol. The symbol before the second protection symbol 424 may be an SBFD symbol. The second transition may occur during the second protection symbol 424 such that the symbol after the second protection symbol 424 is a TDD symbol. Thus, the SBFD symbol 426 may be located between the first protection symbol 422 and the second protection symbol 424, as indicated by the vertical line fill. In the illustrated embodiment, the SBFD symbol 426 is located within the fourth time slot 408 and the fifth time slot 410.
[0072] For Method 1-2, the UE can indicate with more than one non-SBFD-SBFD-non-SBFD transition, where Offset_transitionj_1 and Offset_transitionj_2 correspond to the j-th non-SBFD-SBFD-non-SBFD. For example, during one period, there can be more than one set of transitions from a non-SBFD symbol to an SBFD symbol and back to a non-SBFD symbol. Each pair of Offset_transitionj_1 and Offset_transitionj_2 can define guard symbols for the transitions from a non-SBFD symbol to an SBFD symbol and from an SBFD symbol to a non-SBFD symbol for the corresponding set of transitions. As an example, Symbol Arrangement 400 illustrates one set of transitions from a non-SBFD symbol to an SBFD symbol and back to a non-SBFD symbol, and Method 1-2 can have one or more sets of transitions.
[0073] For Method 1-3, the configuration of the transitions can be maintained within the DL or X (flexible) symbols in TDD-UL-DL-ConfigCommon. That is, for any j, the UE may not expect Offset_transitionj_1 or Offset_transitionj_2 to overlap with UL symbols in TDD-UL-DL-ConfigCommon. For example, any guard symbols (such as the first guard symbol 422 and the second guard symbol 424) can be defined within the DL or flexible symbols in one period. It is not allowed for TDD-UL-DL-ConfigCommon to define guard symbols that overlap with UL symbols.
[0074] For Method 1-4, within TDD-UL-DL-ConfigCommon, the indication of the guard symbols required for transitioning between traditional TDD symbols and SBFD symbols can be separated from the SBFD configuration indication. Figure 5 Example Information Element 500 for Method 1-4 according to some embodiments is illustrated. Information Element 500 can provide information for configuring the UE to perform an operation mode switch. Information Element 500 can be sent from the base station to the UE in a message including configuration information.
[0075] Information Element 500 includes a Common Configuration Information Element 502 (TDD-UL-DL-ConfigCommon) and a Mode Information Element 504 (TDD-UL-DL-Pattern). The Common Configuration Information Element 502 can include one or more features of the Common Configuration Information Element 202 ( Figure 2 ). The Mode Information Element 504 can include one or more features of the Mode Information Element 208 ( Figure 2 ).
[0076] The common configuration information element 502 may include an indication of a guard symbol for transitioning between non-SBFD symbols and SBFD symbols. For example, the common configuration information element 502 includes a first guard indication 506 (TDD2SBFD_Guard) for a first guard symbol and a second guard indication 508 (SBFD2TDD_Guard) for a second guard symbol. The first guard indication 506 may indicate that the first guard symbol for transitioning from a TDD symbol to an SBFD symbol will be included in a time slot. The second guard indication 508 may indicate that the second guard symbol for transitioning from an SBFD symbol to a TDD symbol will be included in a time slot. The first guard indication 506 may indicate the duration of the first guard symbol, and the second guard indication 508 may indicate the duration of the second guard symbol.
[0077] For methods 1-5, the indication of method 1-1 or the indication of method 1-4 may be cell-specific and may be via broadcast signaling (ServingCellConfigCommonSIB in System Information Block 1 (SIB1)) or UE-specific signaling (ServingCellConfigCommon).
[0078] For method 2-1, if the UE requires more time to switch from non-SBFD to SBFD (and / or from SBFD to non-SBFD), it may be indicated to the network (NW) as part of the UE capability signaling. For example, the UE may generate UE capability signaling that indicates the additional time and / or amount of symbols required for the UE to switch from non-SBFD symbols to SBFD symbols and / or the additional time and / or amount of symbols required for the UE to switch from SBFD symbols to non-SBFD symbols. TDD2SBFD_Guard (such as the TDD2SBFD_Guard parameter 222 ( Figure 2 )) and / or the first guard indication 506 ( Figure 5 )) and SBFD2TDD_Guard (such as the SBFD2TDD_Guard parameter 230 ( Figure 2 )) and / or the second guard indication 508 ( Figure 5 )) may be cell-specific. The network may update the values of TDD2SBFD_Guard and / or SBFD2TDD_Guard based on the indication from the UE for the additional time and / or symbols.
[0079] For Method 2-2, for a given UE that requires Y more symbols (i.e., Y+TDD2SBFD_Guard) for the transition from non-SBFD symbols to SBFD symbols, the additional required symbols can be extended. For example, the additional time and / or symbols indicated in Method 2-1 can cause the guard symbols to be extended according to any of the options described below.
[0080] In Option 1, the guard symbols can be extended towards the SBFD symbols. That is, the first Y SBFD symbols may not be available for the UE to use, and it is not expected that the UE receives or transmits within the first Y SBFD symbols.
[0081] In Option 2, the guard symbols can be extended backwards from the non-SBFD symbols. That is, the last Y traditional TDD symbols may not be available for the UE to use, and it is not expected that the UE receives within the last Y SBFD symbols.
[0082] Option 3 can be a combination of Option 1 and Option 2. For example, the guard symbols can be extended towards the non-SBFD symbols by floor(Y / 2), and can be extended towards the SBFD symbols by ceil(Y / 2).
[0083] Method 2-3 can be a method similar to Method 2-2, and can be applicable to a given UE that requires Z more symbols (i.e., Z+SBFD2TDD_Guard) for the transition from SBFD to non-SBFD symbols. For example, the Z more symbols indicated for the switch from SBFD to non-SBFD can be extended according to any one of Options 1, 2, or 3 from Method 2-2.
[0084] For Method 2-4, the UE-specific values Y>=0 (and / or Z>=0) can be different for different handover states. For example, the additional time and / or symbols for switching between SBFD symbols and non-SBFD symbols can be different for changes between UL symbols, DL symbols, and / or X symbols. The UE can indicate these different additional times and / or symbols. Instead of Y, the UE can indicate Y 1 and Y 2 for switching from non-SBFD (downlink (D) or X) to the SBFD DL sub-band and the SBFD UL sub-band respectively. For example, if switching from a non-SBFD DL BWP to the SBFD DL sub-band requires the UE to perform a DL BWP switch, then Y 1 can be greater than Y 2 . In this case, the UE may not be scheduled in both DL sub-bands (the UE may only be scheduled in one or more DL sub-bands).
[0085] Instead of Z, the UE can indicate some or all of the following. For example, the UE can indicate Z 1A symbol is used to switch from an SBFD UL sub - band to a non - SBFD D (or X) symbol. The UE may indicate Z 2 A symbol is used to switch from an SBFD UL sub - band to a non - SBFD uplink (U) symbol. The UE may indicate Z 3 A symbol is used to switch from an SBFD DL sub - band to a non - SBFD D (or X) symbol. The UE may indicate Z 4 A symbol is used to switch from an SBFD DL sub - band to a non - SBFD U symbol. Note that if the UE has to perform a DL BWP switch from / to an SBFD sub - band, then Z 3 (and Z 4 ) may be greater than Z 1 (and Z 2 ).
[0086] Sub - band hopping within SBFD
[0087] For method 3 - 1, within the indicated set of SBFD symbols / slots, if the scheduler meets the timeline required to switch sub - bands, the UE may be scheduled on different sub - bands at different times. Such timeline requirements may be specified as different UE capabilities. More precisely, the following capabilities may be defined. N x A symbol is used to switch from a UL sub - band to one of the DL sub - bands in the DL sub - band (or vice versa). N y A symbol is used to switch from an upper DL sub - band to a lower DL sub - band (or vice versa).
[0088] Figure 6 Illustrates an example transmission arrangement 600 for a UE according to some embodiments. The transmission arrangement 600 illustrates an example of a scheduled transmission that may be scheduled for a UE. The UE may be configured to transmit at different sub - bands.
[0089] The transmission arrangement 600 may include a first DL sub - band 602 and a second DL sub - band 604 configured for DL transmission. The first DL sub - band 602 may be an upper DL sub - band, and the second DL sub - band 604 may be a lower DL sub - band.
[0090] The transmission arrangement 600 may include a UL sub - band 606 configured for UL transmission. The UL sub - band 606 may be located between the first DL sub - band 602 and the second DL sub - band 604. A first guard band 608 may be located between the first DL sub - band 602 and the UL sub - band 606 to avoid interference between transmissions on the first DL sub - band 602 and the UL sub - band 606. A second guard band 610 may be located between the second DL sub - band 604 and the UL sub - band 606 to avoid interference between transmissions on the second DL sub - band 604 and the UL sub - band 606.
[0091] In an exemplary embodiment, downlink control information (DCI) transmission 612 may be scheduled on a first DL subband 602 for the UE. Physical downlink shared channel (PDSCH) transmission 614 may be scheduled on a second DL subband 604. A first number of symbols 616 (N y ) may be defined as the minimum number of symbols for switching from an upper DL subband to a lower DL subband and / or from a lower DL subband to an upper DL subband. Since the PDSCH transmission 614 on the second DL subband 604 includes a switch from the first DL subband 602 on which the DCI transmission 612 is scheduled, the PDSCH transmission 614 may be scheduled at least the first number of symbols 616 after the DCI transmission 612 to allow for the switch.
[0092] Physical uplink control channel (PUCCH) transmission 618 may be scheduled on a UL subband 606. A second number of symbols 620 (N x ) may be defined as the minimum number of symbols for switching from a DL subband to a UL subband and / or from a UL subband to a DL subband. Since the UL transmission 618 on the UL subband 606 includes a switch from the second DL subband 604 on which the PDSCH transmission 614 is scheduled, the PUCCH transmission 618 may be scheduled at least the second number of symbols 620 after the PDSCH transmission 614 to allow for the switch.
[0093] Alternatively, the UE may not expect to be scheduled on different subbands.
[0094] Figure 7 An example signaling diagram 700 according to some embodiments is illustrated. For example, the example signaling diagram 700 illustrates example signals, messages, and / or operations that may be performed according to the above methods.
[0095] The signaling diagram 700 may include a UE 702. The UE 702 may include one or more of the features of the UE 1500 ( Figure 15 ). The signaling diagram 700 may further include a base station 704. The base station 704 may include one or more of the features of the gNB 1600 ( Figure 16 ).
[0096] The UE 702 may generate a first message 706 and / or send the first message to the base station 704. The first message 706 may include capability signaling information, such as UE capability signaling. The UE capability signaling may indicate the time and / or the number of symbols required for the UE to switch between non-SBFD symbols and SBFD symbols according to the above methods 2-1, 2-2, 2-3, and / or 2-4. In some embodiments, the first message 706 may be omitted.
[0097] The base station 704 may generate a second message 708 and / or send the second message to the UE 702. The second message 708 may include configuration information for the UE 702 regarding the transition between SBFD symbols and non-SBFD symbols. The configuration information may include information and corresponding values according to Method 1-1, Method 1-2, Method 1-3, Method 1-4, Method 1-5, and / or Method 3-1.
[0098] The UE 702 and the base station 704 may exchange one or more transmissions 710. The UE 702 and the base station 704 may utilize the configuration information for one or more transmissions 710, including performing one or more transmissions between SBFD symbols and non-SBFD symbols for the transmission 710.
[0099] SB-FD and Dynamic TDD
[0100] Figure 8 An example time slot arrangement 800 according to some embodiments is illustrated. The time slot arrangement 800 illustrates an example of resource assignment in different time slots. The x-axis of the time slot arrangement 800 corresponds to time, and the y-axis of the time slot arrangement 800 corresponds to frequency.
[0101] The time slot arrangement 800 includes an example TDD time slot arrangement 802. The TDD time slot arrangement 802 illustrates an example of resource assignment for time slots configured with TDD and FD operations. The TDD time slot may have a resource assignment for the entire duration of the TDD time slot.
[0102] In the illustrated embodiment, the TDD time slot arrangement 802 includes a downlink (DL) assignment portion 804, where the resources within the DL assignment portion 804 will be used for DL transmission. Additionally, the illustrated TDD time slot arrangement 802 includes a guard band 806, where the resources within the guard band 806 may not be used for transmission. The illustrated TDD time slot arrangement 802 further includes an uplink (UL) assignment portion 808, where the resources within the UL assignment portion 808 will be used for UL transmission.
[0103] The guard band 806 may separate the DL assignment portion 804 from the UL assignment portion 808 to provide a transition between the assignment portions. Although the TDD time slot arrangement 802 illustrates an example resource assignment arrangement, it should be noted that in other embodiments, the TDD time slots in FD operation may have other assignment arrangements including a DL assignment portion, a UL assignment portion, and / or a guard band.
[0104] The time slot arrangement 800 includes an example FDD time slot arrangement 850. The FDD time slot arrangement 850 illustrates an example of resource assignment for time slots configured with FDD and FD operations. The FDD time slot may have a resource assignment for the entire sub-band of the FDD time slot.
[0105] In an exemplary embodiment, the FDD time slot arrangement 850 includes a first DL assignment portion 852 and a second DL assignment portion 860, where the resources within the first DL assignment portion 852 and the second DL assignment portion 860 will be used for DL transmission. Additionally, the exemplary FDD time slot arrangement 850 includes a first guard band 854 and a second guard band 858, where the resources within the first guard band 854 and the second guard band 858 may not be used for transmission. The exemplary FDD time slot arrangement 850 further includes a UL assignment portion 856, where the resources within the UL assignment portion 856 will be used for UL transmission.
[0106] The first guard band 854 may separate the first DL assignment portion 852 and the UL assignment portion 856 to avoid interference between signals transmitted via the resources in the first DL assignment portion 852 and signals transmitted via the resources in the UL assignment portion 856. The second guard band 858 may separate the second DL assignment portion 860 and the UL assignment portion 856 to avoid interference between signals transmitted via the resources in the second DL assignment portion 860 and signals transmitted via the resources in the UL assignment portion 856. Although the FDD time slot arrangement 850 illustrates an example resource assignment arrangement, it should be noted that in other embodiments, the FDD time slots in FD operation may have other assignment arrangements including DL assignment portions, UL assignment portions, and / or guard bands.
[0107] Problem Statement
[0108] This disclosure describes open aspects of UE behavior on transition symbols. The described UE behavior on transition symbols includes whether and / or how a physical channel or signal can be transmitted (or received) in the case of a transition point including a mixture of non - SBFD symbols and SBFD symbols. The methods described herein can address the indication of time - domain resource allocation (TDRA), frequency - domain resource allocation (FDRA), demodulation reference signal (DMRS), transport block (TB) determination, power allocation, etc. These methods can be used for both UL and DL channels / signals (when applicable).
[0109] FDRA Indication
[0110] For Method 4 - 1, for UL transmission or DL reception within a time slot spanning both SBFD symbols and non - SBFD symbols, the UE may not expect the frequency - domain allocation to change across different symbol types. A single FDRA indication can be applied to all symbol types. If the FDRA is not suitable for the corresponding sub - band or bandwidth part (BWP), the UE may discard the uplink transmission or DL reception. Alternatively, the UE behavior may not be defined for FDRA not suitable within the corresponding sub - band or BWP.
[0111] Figure 9Illustrates an example time slot representation 900 according to some embodiments. The time slot representation 900 illustrates an example transmission scheduled to extend within SBFD symbols and non-SBFD symbols of the time slot represented by the time slot representation 900. A transition from a non-SBFD symbol to an SBFD symbol is illustrated in the time slot representation 900.
[0112] The time slot representation 900 may include one or more non-SBFD symbols 902. In the illustrated embodiment, the non-SBFD symbols 902 extend from symbol 0 to symbol 6 of the time slot. The non-SBFD symbols 902 may include a first DL sub-band 908, a first guard band 910, a UL sub-band 912, a second guard band 914, and / or a second DL sub-band 916.
[0113] The time slot representation 900 may include one or more SBFD symbols 906. In the illustrated embodiment, the SBFD symbols 906 extend from symbol 10 to symbol 13 of the time slot. The SBFD symbols 906 may include a UL BWP 918. The UL BWP 918 may not extend on the same bandwidth as the non-SBFD symbols 902, as indicated by the lack of padding above and below the UL BWP 918.
[0114] The time slot representation 900 may include one or more guard symbols 904. The guard symbols may extend between the non-SBFD symbols 902 and the SBFD symbols 906. In the illustrated embodiment, the guard symbols 904 extend from symbol 7 to symbol 9 of the time slot. No transmission may be scheduled during the guard symbols 904 to provide a transition between the non-SBFD symbols 902 and the SBFD symbols 906.
[0115] The time slot representation 900 may include a transmission 920 scheduled to occur during at least a portion of both the non-SBFD symbols 902 and at least a portion of the SBFD symbols 906. For example, in the illustrated embodiment, the transmission 920 spans from symbol 3 to symbol 12. The transmission 920 may be a UL transmission or a DL transmission. In the illustrated embodiment, the transmission 920 includes a PUSCH transmission.
[0116] According to method 4-1, the transmission 920 may have the same frequency domain allocation throughout the duration of the transmission 920 because the FDRA of the transmission 920 is suitable for the UL BWP 918. A single FDRA indication may be applied to the transmission 920. For example, the base station may provide a UE with an FDRA indication that indicates the FDRA for the transmission 920. In other embodiments where the FDRA of the transmission 920 is not suitable for the UL BWP 918, the transmission 920 may be discarded by the UE.
[0117] TDRA indication
[0118] For method 5-1, for UL transmission or DL reception within a time slot that spans both SBFD symbols and non-SBFD symbols, the start and length indicator value (SLIV) columns in the indicated TDRA row indicate the available and unavailable symbols for UL transmission (or DL reception). For example, referring to Figure 9 , the SLIV can indicate S = 3 and L = 10 for transmission. The SLIV indicating S = 3 and L = 10 can indicate that symbols 3 to 12 are available for UL transmission and / or DL reception.
[0119] For method 5-2, for grants that span both SBFD symbols and non-SBFD symbols, option 1 or option 2 described below can be implemented. In option 1, for UL transmission, all symbols are considered available according to UE capabilities (e.g., when the UL sub-band is within the UL BWP or the same size as the UL BWP). For example, the UE can consider all symbols indicated by the SLIV to be available. In this option, the transition can be transparent for UL transmission. Regarding Figure 9 , for option 1, the available symbols can be symbols 3 to 12. If the phase continuity is lost at the gNB due to the transition between SBFD and traditional TDD, the gNB can ensure that the PUSCH contains DMRS symbols in both sets of SBFD symbols and non-SBFD symbols.
[0120] In option 2, for UL transmission or DL reception, the available symbols are all symbols within the indicated SLIV except for the symbols used for the transition. For example, the symbols indicated by the SLIV can be considered available except for any guard symbols that are considered unavailable. This can be for all DL repetitions that overlap with the transition and for cases where uplink transmission cannot remain transparent at the UE side when the gNB switches between SBFD and traditional TDD. For example, regarding Figure 9 , since symbols 7 to 9 are guard symbols, SBFD symbols 3 - 6 and non-SBFD symbols 10 - 12 can be used for transmission 920 (PUSCH).
[0121] For method 5-3, for DL grants (or UL transmissions where the UE needs to exclude protected symbols, i.e., method 5-2, option 2) that span both SBFD symbols and non-SBFD symbols, the first allocated symbol indicated by the SLIV may not be in the set of protected symbols. The SLIV may not indicate only one symbol in each segment of the SBFD symbol or non-SBFD symbol. For example, the SLIV may indicate at least two SBFD symbols and at least two non-SBFD symbols for UL transmission and / or DL transmission that span both SBFD symbols and non-SBFD symbols. For DL reception (or UL transmission under method 5-2 option 2), repetition type B may be applied. When DMRS and data are frequency division multiplexed (FDM), repetition may be allowed only on 1 symbol allocation, where the symbol is the DMRS.
[0122] For method 5-4, for DL reception or UL transmission, repetition type B may be applied on consecutive available symbols. Regarding Figure 9 And for method 5-4, under method 5-2 option 2, the UE may perform two actual repetitions on available symbols 3-6 and 10-12. Each repetition may start at a DMRS symbol (at symbols 3 and 10). The TB (transport block size) may be determined based on the nominal grant (from symbol 3 to 12, including unavailable symbols). Alternatively, the TB may be determined based on the maximum (or minimum) of the actual segmentation within the time slot. The RV indices associated with different actual repetitions may be the same or rotated based on a predetermined pattern (such as 0, 2, 3, 1), where the RV associated with the first repetition may be given by the nominal grant.
[0123] Figure 10 An example time slot representation 1000 according to some embodiments is illustrated. The time slot representation 1000 illustrates a version of the time slot representation 900 ([ Figure 9 ) according to method 5-2 option 2 and method 5-4. For example, the time slot representation 1000 may have unavailable protected symbols and a repetition configuration.
[0124] The time slot representation 1000 may include one or more of the features of the time slot representation 900. The SLIV may have symbols 3 to symbol 12 indicated. Based on the protected symbol 1004 being unavailable (according to method 5-2 option 2), it may be determined that symbols 3 to symbol 6 in the non-SBFD symbol 1002 and symbols 10 to symbol 12 in the SBFD symbol 1006 are available.
[0125] The time slot representation 1000 may have a first actual repetition 1008 scheduled for symbols 3 to symbol 6 in the non-SBFD symbol 1002. Based on symbols 3 to symbol 6 being the first consecutive available symbols in the time slot, the first actual repetition 1008 may be scheduled for symbols 3 to symbol 6. The first actual repetition 1008 may start at a DMRS symbol.
[0126] The slot representation 1000 may have a second actual repetition 1010 scheduled for symbols 10 to 12 in the SBFD symbol 1006. Based on symbols 10 to 12 being the second consecutive available symbols in the slot, the second actual repetition 1010 may be scheduled for symbols 10 to 12. The second actual repetition 1010 may start from a DMRS symbol.
[0127] The RV index for the repetition in the indicated slot representation 1000 may be rotated based on a predetermined pattern. The first actual repetition 1008 may have an RV index 0, and the second actual repetition 1010 may have an RV index 2 indicated by the cycle 1012.
[0128] For method 5-5, for DL reception or UL transmission, a single PUSCH transmission with rate matching on consecutive available symbols may be applied. Regarding Figure 9 And for method 5-5, under proposal 5-2 option 2, the UE may map the decoded bits (after scrambling, modulation, etc.) from the cyclic buffer starting from the indicated RV index to the available resource elements (REs) on the available symbols 3-6 and 10-12. It is assumed that the first symbol of each segment is a DMRS symbol (at symbols 3 and 10). The TB may be determined based on the nominal grant (from symbols 3 to 12, including the unavailable symbols) or based on the available symbols (3-6 and 10-12). A single RV index associated with the nominal grant may be applied.
[0129] Figure 11 An example slot representation 1100 according to some embodiments is illustrated. The slot representation 1100 illustrates a version of the slot representation 900 ([ Figure 9 ) according to method 5-2 option 2 and method 5-5. For example, the slot representation 1100 may have an unavailable guard symbol and a single PUSCH transmission configuration.
[0130] The slot representation 1100 may include one or more of the features of the slot representation 900. The SLIV may have the indicated symbols 3 to 12. Based on the guard symbol 1104 being unavailable (according to method 5-2 option 2), it may be determined that symbols 3 to 6 in the non-SBFD symbol 1102 and symbols 10 to 12 in the SBFD symbol 1106 are available.
[0131] The slot representation 1100 may have a first part of the PUSCH transmission 1108 scheduled for symbols 3 to 6 in the non-SBFD symbol. Based on symbols 3 to 6 being the first consecutive available symbols in the slot, the first part of the PUSCH transmission 1108 may be scheduled for symbols 3 to 6. The first part of the PUSCH transmission 1108 may start from a DMRS symbol.
[0132] The slot indication 1100 may have a second part of the PUSCH transmission 1110 scheduled for symbols 10 to 12 in the non-SBFD symbols. Based on symbols 10 to 12 being the second consecutive available symbols in the slot, the second part of the PUSCH transmission 1110 may be scheduled for symbols 10 to 12. The second part of the PUSCH transmission 1110 may start from a DMRS symbol. The second part of the PUSCH transmission 1110 may be rate-matched with the first part of the PUSCH transmission 1108. The first part of the PUSCH transmission 1108 and the second part of the PUSCH transmission 1110 may have the same RV index, as indicated by the cycle 1112.
[0133] Uplink Power Control
[0134] Due to the following reasons, UL transmissions across different SBFD symbols and non-SBFD symbols may require different power control parameters (such as Po, α, loop index). For the first reason, for SBFD operation, the gNB may require more UL transmission power of the UE to combat the self-interference (SI) at the gNB. For the second reason, in SBFD operation, the victim UE may suffer from cross-link interference (CLI) from the active UE, which can be compensated by a lower UL transmission power.
[0135] Some detailed methods have been proposed to indicate different open-loop and closed-loop power control parameters for transmissions in SBFD slots and non-SBFD slots. In these proposed methods, each transmission spans either SBFD symbols or non-SBFD symbols, rather than their mixture.
[0136] For Proposal 6-1, when the gNB performs full-duplex operation, the UE may be configured with two sets of open power control parameters (Po, α). The sounding parameter signal resource indication (SRI) may indicate the (Po, α) associated with the corresponding set based on the transmission on the SBFD symbol or non-SBFD symbol.
[0137] This is different from the previously proposed methods, where each SRI points to two pairs (Po, α), and additional signaling is required to indicate which pair should be applied. In some embodiments, Method 6-1 may not work for the case where a single PUSCH transmission spans both SBFD symbols and non-SBFD symbols (i.e., the case of Proposal 5-2 Option 1).
[0138] For Method 6-2, for UL grants that span both SBFD symbols and non-SBFD symbols, if segmentation and / or repetition are not involved, one or more of the following options may be achieved. For Option 1, the UE may apply the power control parameters associated with the type of the first allocated symbol. Regarding Figure 9And for Method 5-4, the UE may apply the power control parameters associated with SBFD transmission to the entire PUSCH transmission (symbols 3-12).
[0139] For Option 2, the UE may apply the power control parameters that result in the minimum transmission power. For example, if SBFD operation requires the UE to reduce the transmission power, the power control parameters associated with SBFD transmission may be applied to the entire PUSCH transmission (symbols 3-12 in this example).
[0140] For Option 3, an implicit indication in the downlink control information (DCI) may indicate which set of parameters to use. For example, if the current granted loop index across both SBFD and non-SBFD is different from the previously uplink granted loop index across only SBFD (or only non-SBFD), the currently granted (Po, α) may be selected from the non-SBFD (or SBFD) parameter set. For example, if the current granted loop index is the same as the previous UL grant across only SBFD or only non-SBFD, the parameters (Po, α) may be selected from the parameter set that is the same as the previous UL grant. If the current granted loop index is different from the previous UL grant across only SBFD or only non-SBFD, the parameters (Po, α) may be selected from the parameters of the opposite of SBFD or non-SBFD from the previous UL grant.
[0141] For Option 4, an explicit indication in the DCI may indicate which set of parameters should be used for the entire uplink transmission. For example, an additional 1 (or 2) bit already present in the DCI indicating the SRI is associated with which pair (Po, α) will be used for the uplink transmission.
[0142] For Method 6-3, for UL grants that span both SBFD symbols and non-SBFD symbols, when repetition is involved and DMRS bundling is enabled, in this case, phase continuity may be maintained across different repetitions, so a change in transmission power may not be allowed / desired. All repetitions may follow the power control parameters corresponding to the first repetition.
[0143] For case 1, if the first repetition only spans SBFD symbols, the current quasi-grant that spans both SBFD and non-SBFD symbols applies the power control parameters associated with SBFD operation. For case 2, if the first repetition only spans non-SBFD symbols, the current quasi-grant that spans both SBFD symbols and non-SBFD symbols applies the power control parameters associated with non-SBFD (i.e., traditional TDD) operation. For case 3, if the current grant is the first repetition, all upcoming repetitions, whether spanning only in SBFD symbols or only in non-SBFD symbols, may follow the same power control parameters as the current grant, where the power control parameters of the current grant (1st repetition) can be determined by method 6-2.
[0144] Figure 12 Illustrates an example process 1200 for configuring one or more transitions between SBFD symbols and non-SBFD symbols according to some embodiments. One or more transitions may be performed according to a configuration. Process 1200 may be performed by a device such as UE1500( Figure 15 )).
[0145] Process 1200 may include: identifying configuration information for one or more transitions at 1202. For example, the UE may identify configuration information for one or more transitions between SBFD symbols and non-SBFD symbols for transmission corresponding to the device.
[0146] In some embodiments, identifying the configuration information may include identifying an indication of one or more guard symbols for one or more transitions between SBFD symbols and non-SBFD symbols. In some of these embodiments, the indication of one or more guard symbols may be included in the TDD-UL-DL-Pattern. Additionally, the one or more guard symbols may be included within the TDD-UL-DL-Pattern as part of the SBFD configuration.
[0147] In some of the embodiments where an indication of one or more guard symbols is identified, the indication of one or more guard symbols may include an indication of a first one or more guard symbols corresponding to a first transition from a non-SBFD symbol to an SBFD symbol and an indication of a second one or more guard symbols corresponding to a second transition from an SBFD symbol to a non-SBFD symbol. Additionally, in some of the embodiments, the indication of one or more guard symbols may include a time slot offset indication for one or more guard symbols, a symbol offset for one or more guard symbols, and a guard time indication for one or more guard symbols.
[0148] In some embodiments of the embodiments identifying an indication of one or more protection symbols, one or more protection symbols may be within a DL symbol or an X symbol. Further, in some embodiments of the embodiments, the indication of one or more protection symbols may be included in a TDD-UL-DL-ConfigCommon information element separate from the SBFD configuration indication. In some embodiments of the embodiments, the indication of one or more protection symbols may be cell-specific.
[0149] In some embodiments, the identification configuration information may include: a first indication identifying one or more first protection symbols for a first set of transitions from non-SBFD symbols to SBFD symbols and back to non-SBFD symbols; and a second indication identifying one or more second protection symbols for a second set of transitions from non-SBFD symbols to SBFD symbols and back to non-SBFD symbols.
[0150] In some embodiments, process 1200 may further include: generating capability signaling that indicates a first handover time for a device from non-SBFD symbols to SBFD symbols or a second handover time for the device from SBFD symbols to non-SBFD symbols.
[0151] In some embodiments, process 1200 may further include: generating capability signaling that indicates a plurality of additional protection symbols for a transition of a device from non-SBFD symbols to SBFD symbols. In some embodiments, the plurality of additional protection symbols may be applied to SBFD symbols, backward from non-SBFD symbols, or both to SBFD symbols and backward from non-SBFD symbols.
[0152] In some embodiments, process 1200 may further include: generating capability signaling that indicates a plurality of additional protection symbols for a transition of a device from SBFD symbols to non-SBFD symbols. In some embodiments, the plurality of additional protection symbols may be applied to non-SBFD symbols, backward from SBFD symbols, or both to non-SBFD symbols and backward from SBFD symbols.
[0153] In some embodiments, process 1200 may further include: generating capability signaling that indicates a first number of additional protection symbols for a transition between a first symbol state and a second number of additional protection symbols for a transition between a second symbol state.
[0154] In some embodiments, process 1200 may further include: identifying first scheduling information that schedules a first transmission for a device on a first sub - band within a first SBFD symbol. Additionally, process 1200 may include: identifying second scheduling information that schedules a second transmission for the devices on a second sub - band within the first SBFD symbol, wherein in these embodiments, the number of symbols between the first transmission and the second transmission may exceed a threshold number of symbols. In some of these embodiments, the threshold number of symbols may include a threshold number of symbols for switching from a UL sub - band to a DL sub - band, a threshold number of symbols for switching from a DL sub - band to a UL sub - band, a threshold number of symbols for switching from an upper DL sub - band to a lower DL sub - band, or a threshold number of symbols for switching from a lower DL sub - band to an upper DL sub - band.
[0155] Process 1200 may include: performing one or more transitions in 1204 using configuration information. For example, a UE may use configuration information to perform one or more transitions between SBFD symbols and non - SBFD symbols. In embodiments that indicate an indication of one or more guard symbols, using the configuration information may include using one or more guard symbols indicated for one or more transitions between SBFD symbols and non - SBFD symbols.
[0156] In some embodiments, using the configuration information may include: when a first indication of a first one or more guard symbols is identified for a first set of transitions, using the first one or more guard symbols for the first set of transitions; and when a second indication of a second one or more guard symbols is identified for a second set of transitions, using the second one or more guard symbols for the second set of transitions.
[0157] Although Figure 12 it may arguably imply an order of operations for process 1200, it should be understood that in embodiments, one or more of these operations may be performed in a different order and / or one or more of these operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, one or more of these operations may be omitted and / or one or more additional operations may be added to process 1200.
[0158] Figure 13 An example process 1300 for configuring one or more transitions between SBFD symbols and non - SBFD symbols according to some embodiments is illustrated. A message with the configuration may be generated for transmission to a UE. Process 1300 may be performed by a base station such as gNB 1600( Figure 16 )
[0159] Procedure 1300 may include: determining, at 1302, a configuration for one or more transitions. For example, a base station may determine a configuration for one or more transitions between SBFD symbols and non-SBFD symbols corresponding to transmissions of a UE.
[0160] In some embodiments, procedure 1300 may further include: identifying capability signaling received from a UE, and determining, based on the capability signaling, a first handover time for the UE from non-SBFD symbols to SBFD symbols or a second handover time for the UE from SBFD symbols to non-SBFD symbols, wherein the configuration is determined at least in part based on the first handover time or the second handover time.
[0161] In some embodiments, procedure 1300 may further include: identifying capability signaling received from a UE; and determining, based on the capability signaling, a plurality of additional guard symbols for a transition of the UE from non-SBFD symbols to SBFD symbols or a plurality of additional guard symbols for a transition of the UE from SBFD symbols to non-SBFD symbols. The configuration may be determined at least in part based on the plurality of additional guard symbols for the transition of the UE from non-SBFD symbols to SBFD symbols or the plurality of additional guard symbols for the transition of the UE from SBFD symbols to non-SBFD symbols.
[0162] In some embodiments, procedure 1300 may further include: identifying capability signaling received from a UE, and determining, based on the capability signaling, a first number of additional guard symbols for a transition between a first symbol state and a second number of additional guard symbols for a transition between a second symbol state.
[0163] Procedure 1300 may include: generating, at 1304, a message having configuration information corresponding to the configuration. For example, a base station may generate a message having configuration information corresponding to a configuration for transmission to a UE.
[0164] In some embodiments, the configuration information may include an indication of one or more guard symbols for one or more transitions between SBFD symbols and non-SBFD symbols. In some of these embodiments, the indication of the one or more guard symbols may be included within a TDD-UL-DL-Pattern of the configuration information as part of the SBFD configuration. In some of these embodiments, the indication of the one or more guard symbols may include an indication of a first one or more guard symbols corresponding to a first transition from non-SBFD symbols to SBFD symbols and an indication of a second one or more guard symbols corresponding to a second transition from SBFD symbols to non-SBFD symbols.
[0165] In some embodiments having an indication of one or more guard symbols, the indication of one or more guard symbols may include a slot offset indication for one or more guard symbols and a guard time indication for one or more guard symbols. In some embodiments, the indication of one or more guard symbols may be included within a DL symbol or an X symbol. In some embodiments, the indication of one or more guard symbols may be included in a TDD-UL-DL-ConfigCommon information element separate from the SBFD configuration indication. In some embodiments, the indication of one or more guard symbols may be cell-specific.
[0166] In some embodiments, the configuration information may include: a first indication of a first one or more guard symbols for a first set of transitions from non-SBFD symbols to SBFD symbols and back to non-SBFD symbols; and a second indication of a second one or more guard symbols for a second set of transitions from non-SBFD symbols to SBFD symbols and back to non-SBFD symbols.
[0167] In some embodiments, process 1300 may further include: generating first scheduling information for scheduling a first transmission for a UE in a first sub-band within a first SBFD symbol; and generating second scheduling information for scheduling a second transmission for the UE in a second sub-band within the first SBFD symbol. The number of symbols between the first transmission and the second transmission may exceed a threshold number of symbols. In some of these embodiments, the threshold number of symbols may include a threshold number of symbols for switching from a UL sub-band to a DL sub-band, a threshold number of symbols for switching from a DL sub-band to a UL sub-band, a threshold number of symbols for switching from an upper DL sub-band to a lower DL sub-band, or a threshold number of symbols for switching from a lower DL sub-band to an upper DL sub-band.
[0168] While Figure 13 it may arguably imply an order of operations for process 1300, it should be understood that in an embodiment, one or more of these operations may be performed in a different order and / or one or more of these operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, one or more of these operations may be omitted and / or one or more additional operations may be added to process 1300.
[0169] Figure 14 Illustrates an example process 1400 for scheduling transmissions extended to both SBFD symbols and non-SBFD symbols. A configuration may be determined and utilized for the transmission. Process 1400 may be performed by a UE such as UE1500( Figure 15 ).
[0170] Procedure 1400 may include: identifying, at 1402, a schedule for transmissions extended to both SBFD symbols and non-SBFD symbols. For example, a UE may identify a schedule for transmissions extended to both SBFD symbols and non-SBFD symbols. In some embodiments, the transmission may include UL transmission or DL reception.
[0171] In some embodiments, procedure 1400 may include: identifying, in the SLIV column of the indicated TDRA row, an indication of available and unavailable symbols for a transmission. In some of these embodiments, depending on the capabilities of the device, all the indicated available and unavailable symbols for a transmission are considered available.
[0172] In some embodiments of identifying an indication of available and unavailable symbols, a portion of the indicated available and unavailable symbols is excluded from symbols used for transitions between SBFD symbols and non-SBFD symbols. In some of these embodiments, the first allocated symbol indicated by the value of the SLIV column may not be in the set of protection symbols, and the SLIV column may not indicate only one symbol in either an SBFD symbol or a non-SBFD symbol.
[0173] Procedure 1400 may include: determining, at 1404, a configuration for a transmission. For example, a UE may determine a configuration for a transmission. In some embodiments, determining the configuration may include determining that the FDRA for a transmission is the same for both SBFD symbols and non-SBFD symbols.
[0174] In some embodiments, determining the configuration may include determining that the FDRA for a transmission is the same for both SBFD symbols and non-SBFD symbols. In these embodiments, procedure 1400 may further include: determining that the FDRA is not suitable for a corresponding subband or BWP.
[0175] In some embodiments, determining a configuration for a transmission may include determining to apply a signal PUSCH transmission with rate matching on consecutive available symbols. In some of these embodiments, the TB for a transmission may be determined based on a nominal grant or consecutive available symbols. In some of these embodiments, a single RV index may be applied to a single PUSCH transmission, and the signal RV index may be associated with the nominal grant.
[0176] In some embodiments, determining the configuration may include determining to enable DMRS bundling; determining that the schedule for a transmission is to achieve repetition; and determining that the transmission power will be the same for the repetition.
[0177] Procedure 1400 may include: utilizing, at 1406, the configuration for a transmission. For example, a UE may utilize the configuration for a transmission.
[0178] In some embodiments of determining the FDRA for transmission, using the configuration may include using the FDRA for processing the transmission.
[0179] In some embodiments, in the case where it is determined that the FDRA is not suitable for the corresponding subband or BWP, using the configuration may include discarding the transmission at least partially based on the determination that the FDRA is not suitable for the corresponding subband or BWP.
[0180] In some embodiments, repetition type B may be applied to the transmission. In some of these embodiments, determining the configuration may include determining that two actual repetitions are to be performed on the available symbols for transmission, and using the configuration may include processing two actual repetitions on the available symbols for transmission. In some of these embodiments, the TB for transmission may be determined based on the nominal grant, the maximum of the actual segmentation of the time slot for transmission, or the minimum of the actual segmentation within the time slot for transmission. Additionally, in some of these embodiments, the RV indices for the two actual repetitions may be the same or rotated based on a predetermined pattern for the RV indices.
[0181] In some embodiments of determining to apply a single PUSCH transmission, using the configuration for transmission may include using a single PUSCH transmission.
[0182] In some embodiments, using the configuration may include applying a power control parameter associated with the type of the first allocated symbol for transmission to the transmission, or applying a power control parameter that results in the minimum transmission power to the transmission.
[0183] In some embodiments where it is determined that the transmission power is the same for repetitions, using the configuration for transmission may include using the transmission power for the repetitions.
[0184] In some embodiments, process 1400 may include: identifying an SRI indicating a set of open power control parameters for transmission, the set of open power control parameters being at least partially based on the transmission on SBFD symbols or non - SBFD symbols. In some of these embodiments, determining the configuration may include determining the set of open power control parameters. Additionally, in some of these embodiments, using the configuration may include using the set of open power control parameters for transmission.
[0185] In some embodiments, process 1400 may include: identifying an implicit indication of a set of open power control parameters for transmission. In some of these embodiments, utilizing the configuration may include utilizing the indicated set of open power control parameters for transmission. Additionally, in some of these embodiments, identifying the implicit indication may include determining whether a first loop index corresponding to a scheduling of transmission matches or differs from a second loop index corresponding to a previous scheduling.
[0186] In some embodiments, process 1400 may include identifying an explicit indication of a set of open power control parameters for transmission in DCI.
[0187] While Figure 14 it may arguably imply an order of operations of process 1400, it should be understood that in an embodiment, one or more of these operations may be performed in a different order and / or one or more of these operations may be performed concurrently. Additionally, it should be understood that in other embodiments, one or more of these operations may be omitted and / or one or more additional operations may be added to process 1400.
[0188] Figure 15 An example UE 1500 according to some embodiments is illustrated. The UE 1500 can be any mobile or non - mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter, actuator, etc.), a video surveillance / monitoring device (e.g., camera, video camera, etc.), a wearable device (e.g., smart watch), a loose IoT device. In some embodiments, the UE 1500 can be a RedCap UE or an NR - Light UE.
[0189] The UE 1500 may include a processor 1504, an RF interface circuit 1508, a memory / storage device 1512, a user interface 1516, sensors 1520, a drive circuit 1522, a power management integrated circuit (PMIC) 1524, an antenna structure 1526, and a battery 1528. The components of the UE 1500 may be implemented as integrated circuits (ICs), parts of integrated circuits, discrete electronic devices, or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 15 The block diagram is intended to show a high - level view of some of the components of the UE 1500. However, some of the shown components may be omitted, there may be additional components, and different arrangements of the shown components may occur in other specific implementations.
[0190] The components of the UE 1500 may be coupled to various other components via one or more interconnects 1532, which may represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, optical connector, etc., that allows various circuit components (on common or different chips or chip sets) to interact with each other.
[0191] The processor 1504 may include processor circuitry, such as baseband processor circuitry (BB) 1504A, central processing unit circuitry (CPU) 1504B, and graphics processing unit circuitry (GPU) 1504C. The processor 1504 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from the memory / storage 1512) to cause the UE 1500 to perform the operations described herein.
[0192] In some embodiments, the baseband processor circuitry 1504A may access the communication protocol stack 1536 in the memory / storage 1512 to communicate via a 3GPP-compliant network. Generally, the baseband processor circuitry 1504A may access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access stratum. In some embodiments, the PHY layer operations may additionally / alternatively be performed by components of the RF interface circuit 1508.
[0193] The baseband processor circuitry 1504A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some embodiments, the waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
[0194] The memory / storage device 1512 may include one or more non-transitory computer-readable media that include instructions (e.g., communication protocol stack 1536) that may be executed by one or more of the processors 1504 to cause the UE 1500 to perform the various operations described herein. The memory / storage device 1512 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1500. In some embodiments, some of the memory / storage device 1512 may be located on the processor 1504 itself (e.g., L1 cache and L2 cache), while other memory / storage device 1512 is located external to the processor 1504 but may be accessed via a memory interface. The memory / storage device 1512 may include any suitable volatile or non-volatile memory, such as but not limited to dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.
[0195] The RF interface circuit 1508 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows the UE 1500 to communicate with other devices via a radio access network. The RF interface circuit 1508 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.
[0196] In the receive path, the RFEM may receive a radiated signal from the air interface via the antenna structure 1526 and continue to filter and amplify the signal (using a low-noise amplifier). The signal may be provided to the receiver of the transceiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1504.
[0197] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the signal via a power amplifier before the RF signal is radiated across the air interface via the antenna structure 1526.
[0198] In various embodiments, the RF interface circuit 1508 may be configured to transmit / receive signals in a manner compatible with NR access technology.
[0199] The antenna structure 1526 may include antenna elements to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. These antenna elements may be arranged into one or more antenna panels. The antenna structure 1526 may have antenna panels that are omni-directional, directional, or a combination thereof to enable beamforming and multi-input, multi-output communication. The antenna structure 1526 may include a microstrip antenna, a printed antenna fabricated on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, and the like. The antenna structure 1526 may have one or more panels that are designed for a specific frequency band within FR1 or FR2.
[0200] The user interface 1516 includes various input / output (I / O) devices that are designed to enable a user to interact with the UE 1500. The user interface circuitry 1516 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual component for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, and the like. The output device circuitry includes any physical or virtual component for displaying information or otherwise communicating information such as sensor readings, actuator positions, or other similar information. The output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary state indicators such as light-emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs such as a display device or a touchscreen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1500.
[0201] The sensor 1520 may include a device, module, or subsystem aimed at detecting an event or change in its environment and sending information about the detected event (sensor data) to some other device, module, subsystem, etc. Examples of such sensors particularly include: an inertial measurement unit including an accelerometer, a gyroscope, or a magnetometer; a microelectromechanical or nanoelectromechanical system including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravimeter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and so on.
[0202] The driver circuit 1522 may include software elements and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1500. The driver circuit 1522 may include various drivers, thereby allowing other components to interact with or control various input / output (I / O) devices that may be present within or connected to the UE 1500. For example, the driver circuit 1522 may include: a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface, a sensor driver for obtaining sensor readings from the sensor circuit 1520 and controlling and allowing access to the sensor circuit 1520, a driver for obtaining the actuator position of an electromechanical component or controlling and allowing access to the electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.
[0203] The PMIC 1524 may manage the power provided to various components of the UE 1500. Specifically, with respect to the processor 1504, the PMIC 1524 may control power selection, voltage scaling, battery charging, or DC-DC conversion.
[0204] In some embodiments, the PMIC 1524 may control or otherwise be part of various power saving mechanisms of the UE 1500. For example, if the platform UE is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the UE 1500 may power off for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1500 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The UE 1500 enters a very low power state and performs paging, in which the device wakes up periodically again to listen for the network and then powers off again. The UE 1500 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may render the device unable to use the network for periods of time exceeding the paging interval (from seconds to hours). During this time, the device is completely disconnected from the network and may be powered off completely. Any data transmitted during this time will incur significant latency, and it is assumed that the latency is acceptable.
[0205] The battery 1528 can power the UE 1500, but in some examples, the UE 1500 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 1528 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1528 can be a typical lead-acid car battery.
[0206] Figure 16 An example gNB 1600 is illustrated in accordance with some embodiments. The gNB 1600 may include a processor 1604, RF interface circuitry 1608, core network (CN) interface circuitry 1612, memory / storage circuitry 1616, and antenna structures 1626.
[0207] The components of gNB 1600 may be coupled to various other components via one or more interconnects 1628.
[0208] The processor 1604, RF interface circuit 1608, memory / storage circuit 1616 (including communication protocol stack 1610), antenna structure 1626 and interconnect 1628 may be similar to those of reference Figure 15 Like named elements are shown and described.
[0209] The CN interface circuitry 1612 may provide connectivity to a core network (e.g., a 5th Generation Core Network (5GC) using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the gNB 1600 via optical fiber or wireless backhaul. The CN interface circuitry 1612 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1612 may include multiple controllers for providing connectivity to other networks using the same or different protocols.
[0210] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.
[0211] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the example section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples set forth below. As another example, circuitry associated with a UE, base station, network element, etc. described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples set forth in the example section below.
[0212] Embodiment
[0213] In the following section, additional exemplary embodiments are provided.
[0214] Embodiment 1 may include a method of operating a device, the method including: identifying configuration information for one or more transitions between subband full-duplex (SBFD) symbols and non-SBFD symbols for transmission corresponding to the device; and utilizing the configuration information to perform the one or more transitions between SBFD symbols and non-SBFD symbols.
[0215] Embodiment 2 may include the method according to Embodiment 1, wherein identifying the configuration information includes identifying an indication of one or more guard symbols for the one or more transitions between SBFD symbols and non-SBFD symbols, and wherein utilizing the configuration information includes utilizing the one or more guard symbols indicated for the one or more transitions between SBFD symbols and non-SBFD symbols.
[0216] Embodiment 3 may include the method according to Embodiment 2, wherein the indication of the one or more guard symbols is included within a time-division duplex (TDD)-uplink (UL)-downlink (DL) mode.
[0217] Embodiment 4 may include the method according to Embodiment 3, wherein the indication of the one or more guard symbols is included within the TDD-UL-DL mode as part of an SBFD configuration.
[0218] Embodiment 5 may include the method according to Embodiment 2, wherein the indication of the one or more guard symbols includes an indication of a first one or more guard symbols corresponding to a first transition from a non-SBFD symbol to an SBFD symbol and an indication of a second one or more guard symbols corresponding to a second transition from an SBFD symbol to a non-SBFD symbol.
[0219] Example 6 may include the method according to Example 2, wherein the indication of the one or more guard symbols includes a time slot offset indication for the one or more guard symbols, a symbol offset indication for the one or more guard symbols, and a guard time indication for the one or more guard symbols.
[0220] Example 7 may include the method according to Example 2, wherein the one or more guard symbols are within a downlink (DL) symbol or a flexible (X) symbol.
[0221] Example 8 may include the method according to Example 2, wherein the indication of the one or more guard symbols is included in a time division duplex (TDD)-uplink (UL)-downlink (DL)-ConfigCommon information element separate from the SBFD configuration indication.
[0222] Example 9 may include the method according to Example 2, wherein the indication of the one or more guard symbols is cell-specific.
[0223] Example 10 may include the method according to Example 1, wherein identifying the configuration information includes identifying a first indication of a first one or more guard symbols for a first set of transitions from non-SBFD symbols to SBFD symbols and back to non-SBFD symbols, and identifying a second indication of a second one or more guard symbols for a second set of transitions from non-SBFD symbols to SBFD symbols and back to non-SBFD symbols, and utilizing the configuration information includes utilizing the first one or more guard symbols for the first set of transitions and utilizing the second one or more guard symbols for the second set of transitions.
[0224] Example 11 may include the method according to Example 1, the method further comprising: generating capability signaling that indicates a first switching time for the device to transition from non-SBFD symbols to SBFD symbols or a second switching time for the device to transition from SBFD symbols to non-SBFD symbols.
[0225] Example 12 may include the method according to Example 1, the method further comprising: generating capability signaling that indicates a plurality of additional guard symbols for the device's transition from non-SBFD symbols to SBFD symbols.
[0226] Example 13 may include the method according to Example 12, wherein the plurality of additional guard symbols are applied to SBFD symbols, backward from non-SBFD symbols, or both to SBFD symbols and backward from non-SBFD symbols.
[0227] Example 14 may include the method according to Example 1, the method further comprising: generating capability signaling indicating a plurality of additional protection symbols for transitioning the device from SBFD symbols to non-SBFD symbols.
[0228] Example 15 may include the method according to Example 14, wherein the plurality of additional protection symbols are applied to non-SBFD symbols, backward from SBFD symbols, or both to non-SBFD symbols and backward from SBFD symbols.
[0229] Example 16 may include the method according to Example 1, the method further comprising: generating capability signaling indicating a first number of additional protection symbols for transitions between first symbol states and a second number of additional protection symbols for transitions between second symbol states.
[0230] Example 17 may include the method according to Example 1, the method further comprising: identifying first scheduling information that schedules a first transmission for the device on a first subband within a first SBFD symbol; and identifying second scheduling information that schedules a second transmission for the device on a second subband within the first SBFD symbol, wherein the number of symbols between the first transmission and the second transmission exceeds a threshold number of symbols.
[0231] Example 18 may include the method according to Example 17, wherein the threshold number of symbols includes a threshold number of symbols for switching from an uplink (UL) subband to a downlink (DL) subband, a threshold number of symbols for switching from a DL subband to a UL subband, a threshold number of symbols for switching from an upper DL subband to a lower DL subband, or a threshold number of symbols for switching from a lower DL subband to an upper DL subband.
[0232] Example 19 may include a method of operating a base station, the method comprising: determining a configuration for one or more transitions between subband full-duplex (SBFD) symbols and non-SBFD symbols for a transmission corresponding to a user equipment (UE); and generating a message having configuration information corresponding to the configuration for transmission to the UE.
[0233] Example 20 may include the method according to Example 19, wherein the configuration information includes an indication of one or more protection symbols for the one or more transitions between SBFD symbols and non-SBFD symbols.
[0234] Embodiment 21 may include the method according to Embodiment 20, wherein the indication of the one or more guard symbols is included within a time division duplex (TDD)-uplink (UL)-downlink (DL) mode of the configuration information as part of an SBFD configuration.
[0235] Embodiment 22 may include the method according to Embodiment 20, wherein the indication of the one or more guard symbols includes an indication of a first one or more guard symbols corresponding to a first transition from a non-SBFD symbol to an SBFD symbol and an indication of a second one or more guard symbols corresponding to a second transition from an SBFD symbol to a non-SBFD symbol.
[0236] Embodiment 23 may include the method according to Embodiment 20, wherein the indication of the one or more guard symbols includes a time slot offset indication for the one or more guard symbols, a symbol offset indication for the one or more guard symbols, and a guard time indication for the one or more guard symbols.
[0237] Embodiment 24 may include the method according to Embodiment 20, wherein the indication of the one or more guard symbols is included within a downlink (DL) symbol or a flexible (X) symbol.
[0238] Embodiment 25 may include the method according to Embodiment 20, wherein the indication of the one or more guard symbols is included within a time division duplex (TDD)-uplink (UL)-downlink (DL)-ConfigCommon information element separate from an SBFD configuration indication.
[0239] Embodiment 26 may include the method according to Embodiment 20, wherein the indication of the one or more guard symbols is cell-specific.
[0240] Embodiment 27 may include the method according to Embodiment 19, wherein the configuration information includes a first indication of a first one or more guard symbols for a first set of transitions from a non-SBFD symbol to an SBFD symbol and back to a non-SBFD symbol and a second indication of a second one or more guard symbols for a second set of transitions from a non-SBFD symbol to an SBFD symbol and back to a non-SBFD symbol.
[0241] Embodiment 28 may include the method according to Embodiment 19, the method further including: identifying the capability signaling received from the UE, and determining, according to the capability signaling, a first switching time for the UE from a non-SBFD symbol to an SBFD symbol or a second switching time for the UE from an SBFD symbol to a non-SBFD symbol, wherein the configuration is determined at least in part based on the first switching time or the second switching time.
[0242] Embodiment 29 may include the method according to Embodiment 19, the method further including: identifying the capability signaling received from the UE; and determining, according to the capability signaling, a plurality of additional guard symbols for the transition of the UE from a non-SBFD symbol to an SBFD symbol or a plurality of additional guard symbols for the transition of the UE from an SBFD symbol to a non-SBFD symbol, wherein the configuration is determined at least in part based on the plurality of additional guard symbols for the transition of the UE from a non-SBFD symbol to an SBFD symbol or the plurality of additional guard symbols for the transition of the UE from an SBFD symbol to a non-SBFD symbol.
[0243] Embodiment 30 may include the method according to Embodiment 19, the method further including: identifying the capability signaling received from the UE, and determining, according to the capability signaling, a first number of additional guard symbols for the transition between a first symbol state and a second number of additional guard symbols for the transition between a second symbol state.
[0244] Embodiment 31 may include the method according to Embodiment 19, the method further including: generating first scheduling information for scheduling a first transmission for the UE on a first sub-band within a first SBFD symbol, and generating second scheduling information for scheduling a second transmission for the UE on a second sub-band within the first SBFD symbol, wherein the number of symbols between the first transmission and the second transmission exceeds a threshold number of symbols.
[0245] Embodiment 32 may include the method according to Embodiment 31, wherein the threshold number of symbols includes a threshold number of symbols for switching from an uplink (UL) sub-band to a downlink (DL) sub-band, a threshold number of symbols for switching from a DL sub-band to a UL sub-band, a threshold number of symbols for switching from an upper DL sub-band to a lower DL sub-band, or a threshold number of symbols for switching from a lower DL sub-band to an upper DL sub-band.
[0246] Embodiment 33 may include a method of operating a device, the method including: identifying a scheduling of a transmission extended to both sub-band full-duplex (SBFD) symbols and non-SBFD symbols; determining a configuration for the transmission; and utilizing the configuration for the transmission.
[0247] Example 34 may include the method according to Example 33, wherein the transmission includes uplink (UL) transmission or downlink (DL) reception.
[0248] Example 35 may include the method according to Example 33, wherein determining the configuration includes determining that the frequency-domain resource allocation (FDRA) for the transmission will be the same for both SBFD symbols and non-SBFD symbols, and wherein utilizing the configuration includes utilizing the FDRA for processing the transmission.
[0249] Example 36 may include the method according to Example 33, wherein determining the configuration includes determining that the frequency-domain resource allocation (FDRA) for the transmission will be the same for both the SBFD symbols and the non-SBFD symbols, wherein the method further includes: determining that the FDRA is not suitable for a corresponding subband or bandwidth part (BWP), and wherein utilizing the configuration includes discarding the transmission at least partially based on the determination that the FDRA is not suitable for the corresponding subband or BWP.
[0250] Example 37 may include the method according to Example 33, the method further includes: identifying an indication of available and unavailable symbols for the transmission in the start and length indicator value (SLIV) column of the indicated time-domain resource allocation (TDRA) row.
[0251] Example 38 may include the method according to Example 37, wherein all the indicated available and unavailable symbols for the transmission are considered available according to the capabilities of the device.
[0252] Example 39 may include the method according to Example 37, wherein a part of the indicated available and unavailable symbols excludes symbols for transitions between the SBFD symbols and the non-SBFD symbols.
[0253] Example 40 may include the method according to Example 39, wherein the first allocated symbol indicated by the value of the SLIV column is not in the set of protection symbols, and the SLIV column does not indicate only one symbol in either the SBFD symbols or the non-SBFD symbols.
[0254] Example 41 may include the method according to Example 33, wherein repetition type-B is applied to the transmission, wherein determining the configuration includes determining that two actual repetitions are to be performed on the available symbols for the transmission, and wherein utilizing the configuration includes processing the two actual repetitions on the available symbols for the transmission.
[0255] Example 42 may include the method according to Example 41, wherein the transport block size (TB) for the transmission is determined based on a nominal grant, the maximum of the actual segmentation of the time slot for the transmission, or the minimum of the actual segmentation within the time slot for the transmission.
[0256] Example 43 may include the method according to Example 41, wherein the redundancy version (RV) indices for the two actual repetitions are the same or rotated based on a predetermined pattern for the RV indices.
[0257] Example 44 may include the method according to Example 33, wherein determining the configuration for the transmission includes determining to apply a single physical uplink shared channel (PUSCH) transmission with rate matching on continuously available symbols, and wherein utilizing the configuration for the transmission includes utilizing the single PUSCH transmission.
[0258] Example 45 may include the method according to Example 44, wherein the transport block size (TB) for the transmission is determined based on a nominal grant or the continuously available symbols.
[0259] Example 46 may include the method according to Example 44, wherein a single redundancy version (RV) index is applied to the single PUSCH transmission, and wherein the single RV index is associated with a nominal grant.
[0260] Example 47 may include the method according to Example 33, the method comprising: identifying a sounding reference signal indication (SRI) indicating a set of open power control parameters for the transmission, the set of open power control parameters being at least partially based on transmissions on the SBFD symbols or the non - SBFD symbols, wherein determining the configuration includes determining the set of open power control parameters, and wherein utilizing the configuration includes utilizing the set of open power control parameters for the transmission.
[0261] Example 48 may include the method according to Example 33, wherein utilizing the configuration includes applying a power control parameter associated with the type of the first allocated symbol for the transmission to the transmission, or applying a power control parameter that results in the minimum transmission power to the transmission.
[0262] Example 49 may include the method according to Example 33, the method further comprising: identifying an implicit indication of a set of open power control parameters for the transmission, wherein utilizing the configuration includes utilizing the indicated set of open power control parameters for the transmission.
[0263] Example 50 may include the method according to Example 49, wherein identifying the implicit indication includes determining whether a first loop index corresponding to the scheduling of the transmission matches or is different from a second loop index corresponding to a previous scheduling.
[0264] Example 51 may include the method according to Example 33, the method further including: identifying an explicit indication of a set of open power control parameters for the transmission in downlink control information (DCI).
[0265] Example 52 may include the method according to Example 33, wherein determining the configuration includes: determining that demodulation reference signal (DMRS) bundling is enabled; determining that the scheduling of the transmission is to achieve repetition; and determining that the transmission power will be the same for the repetition, and wherein utilizing the configuration for the transmission includes using the transmission power for the repetition.
[0266] Example 53 may include an apparatus including means for performing one or more elements of the method according to any one of Examples 1 to 52 or related thereto or any other method or process described herein.
[0267] Example 54 may include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method according to any one of Examples 1 to 52 or related thereto or any other method or process described herein.
[0268] Example 55 may include an apparatus including logic components, modules, or circuits for performing one or more elements of the method according to any one of Examples 1 to 52 or related thereto or any other method or process described herein.
[0269] Example 56 may include the method, technique, or process according to any one of Examples 1 to 52 or related thereto, or a part or segment thereof.
[0270] Example 57 may include an apparatus including: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, technique, or process according to any one of Examples 1 to 52 or related thereto, or a part thereof.
[0271] Example 58 may include the signal according to any one of Examples 1 to 52 or related thereto, or a part or segment thereof.
[0272] Example 59 may include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any one of Examples 1 to 52, or otherwise described in the present disclosure, or a part or portion thereof.
[0273] Example 60 may include a signal encoded with data as described in or related to any one of Examples 1 to 52, or otherwise described in the present disclosure, or a part or portion thereof.
[0274] Example 61 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any one of Examples 1 to 52, or otherwise described in the present disclosure, or a part or portion thereof.
[0275] Example 62 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process as described in or related to any one of Examples 1 to 52, or a part thereof.
[0276] Example 63 may include a computer program that includes instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process as described in or related to any one of Examples 1 to 52, or a part thereof.
[0277] Example 64 may include a signal in a wireless network as shown and described herein.
[0278] Example 65 may include a method of communicating in a wireless network as shown and described herein.
[0279] Example 66 may include a system for providing wireless communication as shown and described herein.
[0280] Example 67 may include a device for providing wireless communication as shown and described herein.
[0281] Unless otherwise expressly stated, any one of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings, or may be acquired from practice of various embodiments.
[0282] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be interpreted to cover all such variations and modifications.
Claims
1. One or more computer-readable media having instructions that, when executed, cause a processing circuit to: receiving configuration information indicating a slot index and a symbol index; and One or more sub-band full-duplex (SBFD) symbols within a time division duplex (TDD) uplink (UL)-downlink (DL) mode period are determined based on the configuration information.
2. One or more computer-readable media according to claim 1, wherein the time slot index is a first time slot index and the symbol index is a first symbol index, wherein the configuration information further indicates a second time slot index and a second symbol index, wherein the first time slot index and the first symbol index indicate a first one or more guard symbols before the one or more SBFD symbols, and wherein the second time slot index and the second symbol index indicate a second one or more guard symbols after the one or more SBFD symbols.
3. The one or more computer-readable media of claim 2, wherein the first one or more guard symbols correspond to a first transition from first one or more non-SBFD symbols to the one or more SBFD symbols, and wherein the second one or more guard symbols correspond to a second transition from the one or more SBFD symbols to a second one or more non-SBFD symbols.
4. The one or more computer-readable media of any one of claims 1 to 3, wherein the slot index and the symbol index indicate one or more guard symbols for transitions between SBFD symbols and non-SBFD symbols, and wherein the instructions, when executed, further cause the processing circuit to: The transition is performed using the configuration information, and the one or more guard symbols are used for the transition.
5. The one or more computer-readable media of any one of claims 1 to 3, wherein the slot index and the symbol index are included in a TDD-UL-DL mode as part of a SBFD configuration.
6. One or more computer-readable media according to any one of claims 1 to 3, wherein the time slot index is included in a time slot offset indication, and wherein the symbol index is included in a symbol offset indication.
7. One or more computer-readable media according to any one of claims 1 to 3, wherein the time slot index and the symbol index correspond to one or more guard symbols, and wherein the configuration information also indicates a guard time indication for the one or more guard symbols.
8. One or more computer-readable media according to any one of claims 1 to 3, wherein the time slot index and the symbol index correspond to one or more guard symbols, and wherein the one or more guard symbols are within a downlink (DL) symbol or a flexible (X) symbol.
9. The one or more computer-readable media of any one of claims 1 to 3, wherein the configuration information is included in a TDD-UL-DL-ConfigCommon information element, the TDD-UL-DL-ConfigCommon information element being separate from a SBFD configuration indication.
10. A method comprising: determining configuration information for one or more sub-band full-duplex (SBFD) symbols within a time division duplex (TDD) uplink (UL)-downlink (DL) mode, the configuration information indicating a slot index and a symbol index corresponding to the one or more SBFD symbols; and A message having the configuration information is generated for sending.
11. The method of claim 10, wherein the time slot index is a first time slot index and the symbol index is a first symbol index, wherein the configuration information further indicates a second time slot index and a second symbol index, wherein the first time slot index and the first symbol index indicate a first one or more guard symbols before the one or more SBFD symbols, and wherein the second time slot index and the second symbol index indicate a second one or more guard symbols after the one or more SBFD symbols.
12. The method of claim 11, wherein the first one or more guard symbols correspond to a first transition from first one or more non-SBFD symbols to the one or more SBFD symbols, and wherein the second one or more guard symbols correspond to a second transition from the one or more SBFD symbols to a second one or more non-SBFD symbols.
13. The method according to any one of claims 10 to 12, wherein the slot index and the symbol index indicate one or more guard symbols for transitions between SBFD symbols and non-SBFD symbols, and wherein the method further comprises: The transition is performed using the configuration information, and the one or more guard symbols are used for the transition.
14. The method according to any one of claims 10 to 12, wherein the slot index is included in a slot offset indication, and wherein the symbol index is included in a symbol offset indication.
15. The method according to any one of claims 10 to 12, wherein the time slot index and the symbol index correspond to one or more guard symbols, and wherein the configuration information further indicates a guard time indication for the one or more guard symbols.
16. A device for: identifying configuration information for a time division duplex (TDD) uplink (UL)-downlink (DL) mode period, the configuration information comprising a slot index and a symbol index; and One or more sub-band full duplex (SBFD) symbols having the TDD-UL-DL mode period are determined based on the configuration information.
17. The apparatus of claim 16, wherein the slot index is a first slot index and the symbol index is a first symbol index, wherein the configuration information further indicates a second slot index and a second symbol index, wherein the first slot index and the first symbol index indicate a first one or more guard symbols before the one or more SBFD symbols, and wherein the slot index and the second symbol index indicate a second one or more guard symbols after the one or more SBFD symbols.
18. The apparatus of claim 17, wherein the first one or more guard symbols correspond to a first transition from first one or more non-SBFD symbols to the one or more SBFD symbols, and wherein the second one or more guard symbols correspond to a second transition from the one or more SBFD symbols to a second one or more non-SBFD symbols.
19. The apparatus according to any one of claims 16 to 18, wherein the slot index and the symbol index indicate one or more guard symbols for transitions between SBFD symbols and non-SBFD symbols, and wherein the apparatus is further configured to: The transition is performed using the configuration information, and the one or more guard symbols are used for the transition.
20. The apparatus according to any one of claims 16 to 18, wherein the slot index and the symbol index correspond to one or more guard symbols, and wherein the configuration information further indicates a guard time indication for the one or more guard symbols.