Dynamic slot format indication

Abstract

According to some embodiments, a method is performed by a wireless device for subband full duplex (SBFD) operation. The method comprises receiving an indication of a slot format for one or more symbols in a semi-static time division duplex (TDD) slot configuration. The indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols. The method further comprises transmitting or receiving wireless signals on one or more subbands of a SBFD symbol according to the indication of the slot format.

Description

DYNAMIC SLOT FORMAT INDICATIONTECHNICAL FIELD

[0001] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to dynamic slot format indication.BACKGROUND

[0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0003] Third Generation Partnership Project (3GPP) new radio (NR) provides service for multiple use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and machine type communication (MTC). Each of these services has different technical requirements. For example, the general requirement for eMBB is high data rate with moderate latency and moderate coverage, while URLLC service requires a low latency and high reliability transmission but perhaps for moderate data rates.

[0004] One of the solutions for low latency data transmission is shorter transmission time intervals. In NR in addition to transmission in a slot, a mini-slot transmission is also used to reduce latency. A mini-slot may consist of any number of 1 to 14 orthogonal frequency division multiplexing (OFDM) symbols. The concepts of slot and mini-slot are not specific to a specific service, meaning that a mini-slot may be used for either eMBB, URLLC, or other services.

[0005] FIGURE 1 is a time / frequency diagram illustrating an example radio resource in NR. The horizontal axis represents the time domain, and the other axis represents the frequency domain. In NR, a user equipment (UE) can be configured with up to four carrier bandwidth parts (BWPs) in the downlink with a single downlink carrier bandwidth part being active at agiven time. A UE can be configured with up to four carrier bandwidth parts in the uplink with a single uplink carrier bandwidth part being active at a given time. An NR slot consists of several OFDM symbols, either 7 or 14 symbols (OFDM subcarrier spacing < 60 kHz) and 4 symbols (OFDM subcarrier spacing > 60 kHz).

[0006] FIGURE 2 illustrates a subframe with 14 OFDM symbols. In FIGURE 2, Tsand Tsymbdenote the slot and OFDM symbol duration, respectively.

[0007] NR includes both frequency division duplex (FDD) and time division duplex (TDD) systems. Transmission and reception from a node, e.g. a terminal in a cellular system, can be multiplexed in the frequency domain or in the time domain (or combinations thereol). An example is illustrated in FIGURE 3.

[0008] FIGURE 3 illustrates FDD and TDD modes of operation. FDD is illustrated to the left in FIGURE 3. Downlink and uplink transmission take place in different, sufficiently separated, frequency bands. TDD is illustrated to the right in FIGURE 3. Downlink and uplink transmission take place in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum, whereas FDD uses paired spectrum.

[0009] Typically, the structure of the transmitted signal in a communication system is organized in the form of a frame structure. For example, NR uses ten equally-sized slots per radio frame as illustrated in FIGRE 4 fori 5 kHz subcarrier spacing.

[0010] FIGURE 4 illustrates uplink / downlink time / frequency structure for FDD and TDD. The horizontal axis represents the time domain and the vertical axis represents the frequency domain.

[0011] FDD operation (upper part of FIGURE 4) uses two carrier frequencies, one for uplink transmission (fun) and one for downlink transmission (for). At least with respect to the terminal in a cellular communication system, FDD can be either full duplex or half duplex. In the full duplex case, a terminal can transmit and receive simultaneously, while in half-duplex operation, the terminal cannot transmit and receive simultaneously (the base station is capable of simultaneous reception / transmission though, e.g., receiving from one terminal while simultaneously transmitting to another terminal). In long term evolution (LTE), a half-duplex terminal is monitoring / receiving in the downlink except when explicitly being instructed to transmit in a certain subframe.

[0012] TDD operation (lower part of FIGURE 4), uses a single carrier frequency and uplink and downlink transmissions are always separated in time also on a cell basis. Because the same carrier frequency is used for uplink and downlink transmission, both the base station and themobile terminals need to switch from transmission to reception and vice versa. An essential aspect of any TDD system is to provide the possibility for a sufficiently large guard time where neither downlink nor uplink transmissions occur. This is required to avoid interference between uplink and downlink transmissions. For NR, the guard time is provided by special subframes, which are split into three parts: symbols for downlink (DL), a guard period (GP), and symbols for uplink (UL). The remaining subframes are either allocated to uplink or downlink transmission.

[0013] In more detail, the following two information elements (IES) are defined in current specifications. The TDD pattern is typically configured with at least the first IE and optionally the 2nd l .TDD-DL-UL-ConfigCommon (cell-specific), TDD-DL-UL-ConfigDedicated (UE- specific).

[0014] The first IE is cell specific (common to all UEs) and is provided by broadcast signaling. It provides the number of slots in the TDD pattern via a reference subcarrier spacing and a periodicity such that the S-slot pattern repeats every S slots. This IE facilitates flexible configuration of the pattern characterized as follows. The flexible configuration includes a number of full downlink slots at the beginning of the pattern configured by the parameter nDownlinkSlots, a number of full uplink slots at the end of the pattern configured by the parameter nUplinkSlots, a number of downlink ('D') symbols following the full downlink slots configured by the parameter nDownlinkSymbols, and a number of uplink ('U') symbols preceding the full downlink slots configured by the parameter nUplinkSlots.

[0015] If there is a gap between the last downlink symbol and the first uplink symbol, then all symbols in the gap are characterized as flexible ('F'). A symbol classified as 'F' can be used for downlink or uplink.

[0016] A UE determines the direction in one of the following two ways. The UE may detect a downlink control information (DCI) that schedules / triggers a downlink signal / channel, e.g., physical downlink shared channel (PDSCH), channel state information reference signal (CSI- RS) or schedules / triggers an uplink signal / channel, e.g. physical uplink shared channel (PUSCH), sounding reference signal (SRS), etc.

[0017] As another option, the UE may receive dedicated (UE-specific) signaling in the IE TDD-DL-UL-ConfigDedicated. This parameter overrides some or all of the 'F' symbols in the pattern, thus providing a semi-static indication of whether a symbol is classified as 'D' or 'U'.

[0018] Optionally, a 2nd patern that is concatenated to the first patern can be configured as above. If a 2nd patern is configured, the constraint is that the sum of the periodicities of the two paterns must evenly divide 20 ms.

[0019] FIGURE 5 illustrates an example TDD DL / UL patern configured by TDD-DL-UL- ConfigCommon. The illustrated example TDD DL / UL patern consisting of S = 5 slots. TDD- DL-UL-ConfigCommon configures the cell-specific patern, and TDD-DL-UL- ConflgDedicated (if provided) UE-specifically configures the direction for some or all of the 'F' symbols in the cell-specific patern. The illustrated example consists of 3 full 'D' slots, 1 full 'U' slot, with a mixed slot in between consisting of 4 'D' symbols and 3 'U' symbols. The remaining 7 symbols in the mixed slot are classified as 'F.'

[0020] If a UE is not configured with TDD-DL-UL-ConflgDedicated, then the UE assumes the patern at the top of the diagram. As stated above, the network can use the 'F' symbols flexibly by scheduling / triggering either an uplink or a downlink signal / channel in a UE specific manner. This allows for dynamic behavior: the direction is not known to the UE a priori; rather, the direction becomes known after the UE detects a DCI scheduling / triggering a particular DL or UL signal / channel.

[0021] In contrast, the DL / UL direction for some or all of the 'F' symbols in a particular slot can be provided to the UE in a semi-static manner by Radio Resource Control (RRC) configuring the UE with TDD-DL-UL-ConflgDedicated. The lower part of FIGURE 5 illustrates 3 example configurations for overriding 'F' symbols in Slot 3. If the IE indicates 'allDownlink' or 'allUplink' for a particular slot (or slots), then all 'F' symbols in the slot are converted to either 'D' or 'U,' respectively. If the IE indicates 'explicit,' then a number of symbols at the beginning of the slot and / or a number of symbols at the end of the slot are indicated as 'D' and 'U,' respectively. In FIGURE 5, the first 7 and the last 5 are indicated as 'D' and 'U', which converts some of the 'F' symbols (but not all in this example) to 'D' and 'U.'

[0022] The key behavior is that the UE-specific IE TDD-DL-UL-ConflgDedicated can only override (i.e., specify 'D' or 'U') for symbols that are configured as 'F' by the cell-specific IE TDD-DL-UL-ConflgCommon. In other words, a UE does not expect to have a 'D' symbol converted to 'U' or vice versa.

[0023] FIGURE 6 illustrates three additional example TDD DL / UL paterns configured by TDD-DL-UL-ConflgCommon. The first and second paterns (a and b) do not include 'F' symbols, thus according to current behavior, the UE would not expect to be configured with TDD-DL-UL-ConflgDedicated. In the third patern (c), all symbols in Slots 1, 2, and 3 areconfigured as 'F'; thus, the UE could be configured with TDD-DL-UL-ConflgDedicated to provide a direction ('D' or 'U') for any or all symbols in these 3 slots. The current specifications allow the dedicated configuration of the TDD pattern on a slot-specific basis. In other words, TDD-DL-UL-ConflgDedicated is not restricted to be the same in each slot where 'F' symbols are overridden.

[0024] For dynamic TDD where the UL / DL allocation may vary depending on the scheduling DCI, it can be useful to indicate to a group of UEs what the instantaneous TDD pattern looks like for the current and potentially future slots. This is achieved by signaling of one or more slot format indicators (SFI) in DCI Format 2 0 carried by the group common control channel (GC-PDCCH).

[0025] Each SFI indicates which symbols in a slot are classified as ‘D’, ‘U’, or ‘F’. The indicated SFI(s) cannot override symbols that are already semi-statically configured as ‘D’ or ‘U’ as described previously; however, an SFI can indicate the direction (‘D’ or ‘U’) for symbols classified as flexible (‘F’). If the SFI indicates ‘F’ for symbols already classified as ‘F’, and PDCCH does not schedule any data or trigger reference signals in those symbols, then the UE shall neither transmit nor receive on those symbols. This can be useful to cancel an instance of a periodically transmitted / received reference signals (e.g., SRS, CSI-RS) to create ‘reserved resources’ for use by another technology, e.g., LTE.

[0026] SFI is carried by DCI format 2 0 and includes slot format indicator 1, slot format indicator 2, ... , slot format indicator N. Each of the “Slot format indicators” or “SFI-index” field in DCI format 2 0 indicates to a UE a slot format for each slot for a period of transmission for each DL bandwidth part (BWP) or each UL BWP starting from a slot where the UE detects the DCI format 2 0.

[0027] To receive dynamic TDD pattern indicated by SFI, the UE is provided by higher layer parameter slotFormatlndicator with slotFormatCombinationsPerCell for a serving cell in a set of configured serving cells, which configures the parameters used for interpretation of the detected SFI-index for the corresponding serving cell. The following parameters are configured in SlotFormatCombinationsPerCell for each serving cell: an identity of the serving cell by servingCellld,' the location of SFI-index field (i.e., “slot format indicator x” in DCI format 2_0) by positionlnDCI for corresponding servingCellld,' and a set of slot format combinations by slotFormatCombinations, which comprise a sequence of SlotFormatCombinatiori’s. This can be interpreted as a hash table where each “key” indicated by the SlotFormatCombinationldrefers to a specific ^slotFormatCombination” in the table, where each SlotFormatCombination includes two parameters.

[0028] The first parameter is one or more slot formats (up to 256 slots) indicated by slotFormats. The slotFormats comprise a sequence of indices form 0, 256. Each index refers to a slot format in a predefined table (Table 11.1.1-1) in the 3GPP specification TS 38.213.

[0029] The second parameter is a mapping of the slot format combination provided by the slotFormats to a corresponding SFI-index field value in DCI format 2_0 provided by the slotF ormatCombinationld.

[0030] FIGURE 7 illustrates an example for slot format combination configuration using DCI format 2 0 for slot format indication (SFI) for specific serving cell. The SFI indication mechanism is as specified in the current 3GPP specifications. In the example, SFI-index = 3 is detected for serving cell 3, which is mapped to row 3 in the configured table of SlotF ormatCombinations, indicating TDD pattern for 5 consecutive slots with slotFormats 0, 0, 55, 0 and 0 respectively. The actual transmission direction for the symbols in these slots can be obtained by the corresponding entries in the slot format table.

[0031] As described above, in a conventional TDD system, the entire carrier bandwidth or all carriers in the same frequency band use the same DL transmission or UL reception directions. This is further illustrated in FIGURE 8.

[0032] FIGURE 8 includes two time / frequency diagrams illustrating a conventional TDD carrier and TDD carrier system.

[0033] For the Rel-18 evolution of the NR system, 3GPP will study the technical feasibilities and potential benefits of subband full duplex (SBFD) systems. In such a system, a portion of a wide bandwidth carrier may be used for a different direction than that of the rest of the carrier. This is illustrated in the left-hand side of FIGURE 9.

[0034] FIGURE 9 includes two time / frequency diagrams illustrating a subband full duplex system. Unlike a conventional TDD system as shown on the left-hand side of FIGURE 8 where the entire bandwidth is used for DL transmission in the first three slots, the center portion of the SBFD carrier is used for UL reception while the rest of the carrier continues to be used for DL transmission as shown in the left-hand side of FIGURE 9.

[0035] Similarly, instead of using all carriers for the same DL or UL directions in a conventional TDD system as shown in the right-hand side of FIGURE 8, some carriers in theSBFD system can be used for a different direction than that of the other carriers as shown in the right-hand side of FIGURE 9.

[0036] In the 3GPP Rel-18 study, the scope has been limited such that in SBFD operation, only gNBs transmit DL and receive UL simultaneously. An individual UE is scheduled in only one direction (DL or UL) at a time, following a half-duplex operation.

[0037] Modem cellular wireless communication systems use advance antenna array systems to perform beamforming and multiple-input multiple-output (MIMO) transmission to enhance the coverage and throughput of the system. A generic example antenna array for a TDD system is illustrated in FIGURE 10.

[0038] FIGURE 10 illustrates generic example TDD antenna array with 32 cross-polarized antenna elements (64 elements in total). In such an example array, multiple antenna elements are used and typically placed in a planar array with horizontal and vertical spacings suitable for the operating frequency bands. For a TDD base station, the antenna array is connected to a TX / RX switch such that the same antenna array can be used for transmitting DL signals in a DL slot as well as used for receiving UL signals in an UL slot.

[0039] In an SBFD system, the base station needs to perform DL transmission and UL reception simultaneously. It thus becomes necessary to use two antenna arrays for the two directions, respectively, as illustrated in FIGURE 11.

[0040] FIGURE 11 illustrates an example antenna architecture for SBFD systems. A first antenna array is used for UL reception only. A second antenna array is used for DL transmission only.

[0041] It is also generally necessary to introduce additional isolation material or mechanisms between the two antenna arrays to suppress the signal leaking from the TX array into the RX array. Without such isolation, the UL receiver can be de-sensitized because the DL transmit power is generally much higher than the UL receive power.

[0042] There currently exist certain challenges. For example, the dynamic slot format indication mechanism in the current (3GPP Rel-17) specifications does not support SBFD operation or specify how to dynamically indicate to the UE the slot format for SBFD symbols where the carrier is partitioned into multiple RB sets (subbands) with different transmission directions.

[0043] SUMMARY

[0044] As described above, certain challenges currently exist with dynamic slot format indication. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges.

[0045] For example, particular embodiments dynamically indicate transmission direction(s) for the subbands within subband full duplex (SBFD) symbols. Particular embodiments extend the existing dynamic slot format indication mechanism to support SBFD operation with minimum specification impact.

[0046] According to some embodiments, a method is performed by a wireless device for subband full duplex (SBFD) operation. The method comprises receiving an indication of a slot format for one or more symbols in a semi-static time division duplex (TDD) slot configuration. The indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols. The method further comprises transmitting or receiving wireless signals on one or more subbands of a SBFD symbol according to the indication of the slot format.

[0047] In particular embodiments, the indication of the slot format indicates that a symbol is one of a downlink symbol (D), uplink symbol (U), flexible (F), and SBFD symbol (S). For a symbol indicated as SBFD, the wireless device obtains transmission directions for one or more of the subbands within the symbol according to a predetermined configuration of subband size and location in the frequency domain. The indicator of the predetermined configuration may be preconfigured or received via signaling from a network node. The indicator of the predetermined configuration may be received in a downlink control indication (DCI) format contained in group common control signaling. The DCI format may be DCI format 2 0.

[0048] In particular embodiments, the one or more symbols include SBFD symbols and one or more of the SBFD symbols consist of one or more subbands with undetermined transmission direction. The indication of the slot format indicates a transmission direction for the one or more subbands with undetermined transmission direction. The one or more subbands with undetermined transmission direction may be semi-statically configured with direction as flexible.

[0049] In particular embodiments, the one or more symbols include SBFD symbols and one or more of the SBFD symbols consist of one or more subbands wherein at least one of the subbands has a semi-statically configured transmission direction, and the indication of the slot format overrides the semi-statically configured transmission direction. The semi-staticallyconfigured transmission direction for the at least one of the subbands may be uplink or downlink.

[0050] In particular embodiments, the indication of the slot format is contained in a downlink control information (DCI) format contained in group common control signaling. The DCI format may comprise DCI format 2 0.

[0051] In particular embodiments, the indication of the slot format comprises a slot format indicator (SFI).

[0052] In particular embodiments, the indication of the slot format is associated with a slot format indicator (SFI) radio network temporary identifier (RNTI).

[0053] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the methods of the wireless device described above.

[0054] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

[0055] According to some embodiments, a method is performed by a network node for configuring a wireless device for SBFD operation. The method comprises determining a slot format for one or more symbols in a semi-static time division duplex (TDD) slot configuration for a wireless device. The indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols. The method further comprises transmitting an indication of the slot format to the wireless device.

[0056] In particular embodiments, the slot format indicates that a symbol is one of a downlink symbol (D), uplink symbol (U), flexible (F), and SBFD symbol (S).

[0057] In particular embodiments, the method further comprises transmitting to the wireless device an indication of a predetermined configuration of transmission directions for one or more of the subbands within the symbol according to a predetermined configuration of subband size and location in the frequency domain. The indicator of the predetermined configuration may be transmitted in a DCI format contained in group common control signaling. The DCI format may be DCI format 2 0.

[0058] In particular embodiments, the one or more symbols include SBFD symbols and one or more of the SBFD symbols consist of one or more subbands with undetermined transmission direction. The indication of the slot format indicates a transmission direction for the one or more subbands with undetermined transmission direction. The one or more subbands withundetermined transmission direction may be semi-statically configured with direction as flexible.

[0059] In particular embodiments, the one or more symbols include SBFD symbols and one or more of the SBFD symbols consist of one or more subbands wherein at least one of the subbands has a semi-statically configured transmission direction, and the indication of the slot format overrides the semi-statically configured transmission direction. The semi-statically configured transmission direction for the at least one of the subbands may be uplink or downlink.

[0060] In particular embodiments, the indication of the slot format is contained in a DCI format contained in group common control signaling. The DCI format may comprise DCI format 2 0.

[0061] In particular embodiments, the indication of the slot format comprises a SFI.

[0062] In particular embodiments, the indication of the slot format is associated with a SFI RNTI.

[0063] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0064] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network nodes described above.

[0065] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments enable dynamic slot format indication for SBFD operation.BRIEF DESCRIPTION OF THE DRAWINGS

[0066] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:FIGURE 1 is a time / frequency diagram illustrating an example radio resource in New Radio (NR);FIGURE 2 illustrates a subframe with 14 orthogonal frequency division multiplexing (OFDM) symbols;FIGURE 3 illustrates frequency division duplex (FDD) and time division duplex (TDD) mode of operation;FIGURE 4 illustrates uplink / downlink time / frequency structure for FDD and TDD;FIGURE 5 illustrates an example TDD DL / UL pattern configured by TDD-DL-UL- ConflgCommon ;FIGURE 6 illustrates three additional example TDD DL / UL patterns configured by TDD-DL- UL-ConflgCommon;FIGURE 7 illustrates an example for slot format combination configuration using DCI format 2_0 for slot format indication (SFI) for specific serving cell;FIGURE 8 includes two time / frequency diagrams illustrating a conventional TDD carrier and TDD carrier system;FIGURE 9 includes two time / frequency diagrams illustrating a subband full duplex system;FIGURE 10 illustrates a generic example antenna array for a TDD system;FIGURE 11 illustrates an example antenna architecture for SBFD systems;FIGURE 12 illustrates an example SBFD configuration in a SBFD symbol;FIGURE 13 illustrates an example of dynamic slot format indication for SBFD operation;FIGURE 14 illustrates an example of dynamic slot format indication for SBFD operation;FIGURE 15 illustrates an example communication system, according to certain embodiments;FIGURE 16 illustrates an example UE, according to certain embodiments;FIGURE 17 illustrates an example network node, according to certain embodiments;FIGURE 18 illustrates a block diagram of a host, according to certain embodiments;FIGURE 19 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;FIGURE 20 illustrates a host communicating via a network node with a UE over a partially wireless connection, according to certain embodiments;FIGURE 21 illustrates a method performed by a wireless device, according to certain embodiments; andFIGURE 22 illustrates a method performed by a network node, according to certain embodiments.DETAILED DESCRIPTION

[0067] As described above, certain challenges currently exist with dynamic slot format indication. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments dynamically indicate transmission direction(s) for the subbands within suband full duplex (SBFD) symbols.

[0068] Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0069] A first group of embodiments include a new symbol type for slot format indicator (SFI). In particular embodiments, a new symbol type, SBFD symbol, is used to support dynamic slot format indication for SBFD operation.

[0070] In a non-limiting example, in addition to the existing ‘D’, ‘U’ and ‘F’ symbols, which denote downlink symbol, uplink symbol and flexible symbol, respectively, a new symbol type ‘S’ is used to denote SBFD symbol in a slot. The existing slot format table (i.e., Table 11.1.1- 1 in TS 38.213) is extended with a set of new slot formats where SBFD is indicated for some or all of the symbols in the slot. An example extended slot format table is illustrated below, where the rows 56-63 are new slot formats that support SBFD operation.Table 11.1.1-1: Slot formats for normal cyclic prefix

[0071] For SBFD symbols, i.e., symbols indicated as ‘S’, the actual radio band (RB) set configuration, i.e., partitioning of a carrier into multiple radio band sets (subbands) with different transmission directions, is either fixed by specification or configured by higher layer. One such SBFD configuration example is illustrated in FIGURE 12.

[0072] FIGURE 12 illustrates an example SBFD configuration (D-U-D) in a SBFD symbol. Although a UE may be configured with multiple radio band set configurations (such as D-U- D or U-D-U with different bandwidths for D / U RB sets, etc.), some embodiments prefer that there is only one active radio band set configuration at any point in time, which can be semi- statically configured by a higher layer. Alternatively, a new parameter may be included in SFI to explicitly indicate which one of the configured radio band set configurations should be applied in the indicated SBFD symbols for the time duration of the indicated SFI.

[0073] In some embodiments, when multiple radio band set configurations (such as D-U-D or U-D-U with different bandwidths for D / U radio band sets, etc.) are configured / active, more than one new symbol type, e.g., “SI”, “S2”, and so on may be used to denote the SBFD symbols corresponding to the different RB set configurations.

[0074] The legacy dynamic slot format indication mechanism may be reused. As described above, a UE is configured with a slotFormatCombinationsPerCell for each configured serving cell, which consists of a set of slot format combinations by slotFormatCombinations. A detected SFI dynamically points to one of the slot format combinations. For SBFD capable UEs, some of the slot formation combinations may indicate slot formats that contains SBFD symbols. The new slot format may be used to enable SBFD operation for new SBFD capable UEs, which should not be used in the slot format combination configuration for legacy UEs not capable of SBFD operation.

[0075] Only ‘F’ symbols indicated by semi-static TDD pattern configuration (by TDD-DL- UL-ConfigCommon and TDD-DL-UL-ConfigDedicated) can be overridden with different symbol type (i.e., ‘D’, ‘U’ or ‘S’).

[0076] FIGURE 13 illustrates an example of dynamic slot format indication for SBFD operation. The cell-specifically configured semi-static TDD pattern in the example in the upper part of the figure consists of 5 slots. The overall pattern has a number of DL-only symbols at the beginning of the pattern and a number of UL-only symbols at the end of the pattern. In between are the 'F' symbols, some or all of which may be used for SBFD operation.

[0077] Configuration of such a cell-specific patern is supported already in current (Rel-17) specifications. Thus, the patern is valid for both new UEs that support SBFD operation and legacy UEs that are not capable of SBFD operation. Furthermore, an SFI-index is detected in DCI format 2_0, pointing to a slot format combination of 5 slots which consists of 5 slot formats with value 4, 56, 56, 63 and 1 respectively. From the example extended slot format table as given above, the SBFD configuration may be identified, as shown in the lower part of FIGURE 13.

[0078] In some embodiments, legacy UEs and new SBFD UEs monitor the same SFI. In some embodiments, legacy UEs and new SBFD capable UEs are assigned with different SFI-RNTI, so that the two groups of UEs monitor different SFIs.

[0079] In some embodiments, to support legacy UEs and SBFD capable UEs in the same cell using the same DCI 2_0, the network may configure different sets of slot format combinations for legacy UEs and SBFD capable UEs. For example, in the above example the SFI-index points to slot format combination of 4-56-56-63-1 for SBFD UEs. For legacy UEs, the SFI- index may point to a slot format combination of SFx-SFy-SFz-SFw-SFu, where SFx,SFy,SFz,SFw,SFu are legacy slot formats from Table 11.1.1-1, i.e., the values of SFx,SFy,SFz,SFw,SFu are from "0” to “55” in this table. Moreover, SFy-SFz-SFw are preferable to be ‘0’ (DL only slot) from Table 11.1.1-1, but they may also be any legacy slot formats from ‘0’ to ‘55’.

[0080] In a non-limiting example, where the same DCI 2 0 is used for both legacy UEs and SBFD capable UEs, the network may configure different sets of slot format combinations for the legacy UEs and the SBFD capable UEs such that, for a given SFI index, the conventional ‘D’,’U’,’F’ symbols are identical for both group of UEs, whereas the SBFD symbols are indicated differently, which are identified as S symbols for the SBFD capable UEs and conventional symbols (preferable as ‘D’ symbols, but possible to configure as ‘U’ or ‘F’ symbols) for the legacy UEs. For example, in the above example, the SFI-index points to the slot format combination of 4-56-56-63-1 for the SBFD UEs. For the legacy UEs, the SFI-index points to the slot format combination of 4-SFy-SFz-SFw-l, where SFy-SFz-SFw are preferable to be ‘0’ (DL only slot) from Table 11.1.1-1, but they may also be any legacy slot formats from ‘0’ to ‘55’.

[0081] A second group of embodiments indicate transmission direction for radio band set(s) configured as ‘F’. The legacy semi-static TDD patern configuration procedure may be extended to configure SBFD capable UE with enhanced TDD patern wherein some or all ofthe flexible (‘F’) symbols are further indicated as SBFD symbols. For these SBFD symbols, a radio band set configuration is provided to indicate the partitioning of the carrier into multiple radio band sets (subbands) with different transmission directions. The transmission direction of each radio band set may be set to ‘D’, ‘U’ or ‘F’.

[0082] According to some embodiments, SFI carried in DCI format 2 0 may dynamically indicate transmission direction for a symbol, wherein the indicated transmission direction is applicable to any radio band set that is RRC configured flexible (‘F’) in the symbol. More specifically, for a SBFD symbol, the slot format identified by SFI indicates transmission direction for the symbol, which is applicable to any radio band sets in the symbol configured as flexible (‘F’) by RRC. For anon-SBFD symbol where there is only one radio band set across the entire carrier, the indicated transmission direction is applicable if the symbol is configured as flexible (‘F’) by RRC, as already supported in the current (Rel-17) specifications.

[0083] A non-limiting example of particular embodiments is demonstrated in FIGURE 14. FIGURE 14 illustrates an example of dynamic slot format indication for SBFD operation. The upper part of FIGURE 14 shows a RRC configured semi-static TDD pattern that supports SBFD operation in slot 1, 2 and 3. Three radio band sets are configured in the SBFD symbols where the central radio band set is set to flexible (‘F’). In other words, the radio band set configuration is ‘D-F-D’. The central radio band set for the SBFD symbols is further indicated as uplink (‘U’) by the slot formats identified from the detected SFI, dynamically converting the radio band set configuration to ‘D-U-D’, for the time duration of the indicated SFI.

[0084] In this example, the slot format is identified by the SFI using the legacy slot format table (i.e., Table 11.1.1-1 in TS 38.213). To support full scheduling flexibility, the legacy slot format table may be extended with some new entries, i.e., additional slot formats with SBFD operation in some symbols. For example, new slot formats may be added wherein the first symbols are configured to uplink followed by downlink or flexible symbols in the remainder of the slot.

[0085] A third group of embodiments use radio band set specific SFI. According to some embodiments, when SBFD operation is enabled, multiple SFIs may be indicated for a serving cell by DCI format 2 0, wherein each SFI explicitly indicates the transmission direction for a particular configured radio band set. The radio band set specific SFI may be implemented in different ways as described below.

[0086] In some embodiments, the current DCI format 2 0 in Rel-17 is extended to carry multiple SFI values for a serving cell, one for each configured RB set. The number of SFIvalues carried in the DCI for a serving cell is determined by the maximum number of radio band sets configured for the serving cell. For SBFD symbols, the slot format identified by the first SFI value applies to the first radio band set, the slot format identified by the second SFI value applies to the second radio band set, and so on.

[0087] For non-SBFD symbols, where there is only one radio band set across the entire carrier, the first SFI value applies. Alternatively, some embodiments may include an indicator in the DCI or higher layer configuration to tell which SFI value among multiple SFI values applies to the non-SBFD symbols.

[0088] Legacy UEs and new SBFD-capable UEs may be configured to monitor the same DCI 2 0. In that case for a legacy UE only the first SFI value for a serving cell in the DCI is valid. Alternatively, legacy UEs and new SBFD capable UEs are assigned with different SFI-RNTI, so that the two groups of UEs monitor different DCI 2 0. A legacy UE monitors legacy DCI 2 0, which indicates a single SFI value for each serving cell, while a new SBFD-capable UE monitors new DCI 2 0, which indicates multiple SFI values for each serving cell, one for each configured radio band set.

[0089] In some embodiments, a single SFI value is carried in DCI 2 0 for a serving cell, which points to one of the RRC configured slot format combinations, as specified in the Rel-17 specification. To support radio band set specific slot formation indication, a slot format combination configured to a SBFD-capable UE may comprise multiple sequences of slot format, one for each configured RB set. A sequence of slot formats may take similar form as the legacy slot format combination. As such, for SBFD-capable UEs, transmission directions for multiple configured radio band sets in SBFD symbols may be identified from a single SFI carried in DCI 2 0. For non-SBFD symbols, where there is only one radio band set across the entire carrier, the first sequence of slot format applies. Alternatively, an indicator in the DCI or higher layer configuration may indicate which slot format sequence among multiple slot format sequences applies to the non-SBFD symbols.

[0090] The current DCI format 2 0 in Rel-17 may be used to transmit SFI to both legacy UEs and SBFD-capable UEs. Therefore, some embodiments prefer that legacy UEs and new SBFD- capable UEs are configured to monitor the same DCI 2 0. However, in some embodiments legacy UEs and new SBFD capable UEs may be assigned with different SFI-RNTI, so that the two groups of UEs monitor different DCI 2 0.

[0091] FIGURE 15 illustrates an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes atelecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0092] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0093] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0094] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), HomeSubscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0095] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0096] As a whole, the communication system 100 of 1FIGURE 15 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0097] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0098] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit informationto the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0099] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0100] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In otherembodiments, the hub 114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0101] FIGURE 16 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0102] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0103] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 16. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0104] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0105] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0106] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0107] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0108] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0109] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may becoupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0110] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0111] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0112] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0113] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voicecontrolled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in FIGURE 16.

[0114] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0115] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0116] FIGURE 17 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to,access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0117] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0118] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0119] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio FrequencyIdentification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0120] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0121] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0122] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0123] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, forexample to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0124] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0125] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0126] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as beingperformed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0127] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0128] Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 17 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0129] FIGURE 18 is a block diagram of a host 400, which may be an embodiment of the host 116 of FIGURE 15, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.

[0130] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 3 and 4, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

[0131] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0132] FIGURE 19 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0133] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0134] Hardware 504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.

[0135] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0136] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.

[0137] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.

[0138] FIGURE 20 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of FIGURE 15 and / or UE 200 of FIGURE 16), network node (such as network node 110a of FIGURE 15 and / or network node 300 of FIGURE 17), and host (such as host 116 of FIGURE 15 and / or host 400 of FIGURE 18) discussed in the preceding paragraphs will now be described with reference to FIGURE 20.

[0139] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650.

[0140] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of FIGURE 15) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0141] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.

[0142] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0143] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.

[0144] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606.

[0145] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the delay to directly activate an SCell by RRC and power consumption of user equipment and thereby provide benefits such as reduced user waiting time and extended battery lifetime.

[0146] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0147] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and / or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may be implemented in that software causes messages tobe transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.

[0148] FIGURE 21 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 21 may be performed by UE 200 described with respect to FIGURE 16. The wireless device is capable of subband full duplex (SBFD) operation.

[0149] The method begins at step 2112, where the wireless device (e.g., UE 200) receives an indication of a slot format for one or more symbols in a semi-static time division duplex (TDD) slot configuration. The indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols. The indication of the slot format may be according to any of the three groups of embodiments described above with respect to FIGURES 12-14.

[0150] For example, in particular embodiments the indication of the slot format indicates that a symbol is one of a downlink symbol (D), uplink symbol (U), flexible (F), and SBFD symbol (S). For a symbol indicated as SBFD, the wireless device obtains transmission directions for one or more of the subbands within the symbol according to a predetermined configuration of subband size and location in the frequency domain (e.g., D-U-D). An example configuration is illustrated in FIGURE 12.

[0151] The indicator of the predetermined configuration may be preconfigured (e.g., defined in a specification) or received via signaling from a network node. The indicator of the predetermined configuration may be received in a DCI format contained in group common control signaling (e.g., DCI format 2_0).

[0152] In another group of embodiments, the one or more symbols include SBFD symbols and one or more of the SBFD symbols comprise one or more subbands with undetermined transmission direction. The indication of the slot format indicates a transmission direction for the one or more subbands with undetermined transmission direction. The one or more subbands with undetermined transmission direction may be semi-statically configured with direction as flexible. An example is illustrated in FIGURE 14.

[0153] In another group of embodiments, the one or more symbols include SBFD symbols and one or more of the SBFD symbols comprise one or more subbands wherein at least one of the subbands has a semi-statically configured transmission direction. The indication of the slot format overrides the semi-statically configured transmission direction. The semi-staticallyconfigured transmission direction for the at least one of the subbands may be uplink or downlink.

[0154] In particular embodiments, the indication of the slot format is contained in a downlink control information (DCI) format contained in group common control signaling (e.g., DCI format 2_0).

[0155] In particular embodiments, the indication of the slot format comprises a slot format indicator (SFI).

[0156] In particular embodiments, the indication of the slot format is associated with a slot format indicator (SFI) radio network temporary identifier (RNTI).

[0157] At step 2114, the wireless device transmits or receives wireless signals on one or more subbands of a SBFD symbol according to the indication of the slot format.

[0158] Modifications, additions, or omissions may be made to method 2100 of FIGURE 21. Additionally, one or more steps in the method of FIGURE 21 may be performed in parallel or in any suitable order.

[0159] FIGURE 22 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 22 may be performed by network node 300 described with respect to FIGURE 17. The network node is operable to configure a wireless device for SBFD operation.

[0160] The method may begin at step 2212, where the network node (e.g., network node 300) transmits to the wireless device an indication of a predetermined configuration of transmission directions for one or more of the subbands within the symbol according to a predetermined configuration of subband size and location in the frequency domain. An example configuration is illustrated in FIGURE 12.

[0161] The indicator of the predetermined configuration may be transmitted in a DCI format contained in group common control signaling. The DCI format may be DCI format 2 0.

[0162] At step 2214, the network node determines a slot format for one or more symbols in a semi-static TDD slot configuration for a wireless device. The indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols.

[0163] The network node may determine the slot format according to any of the embodiments and examples described herein.

[0164] At step 2216, the network node transmits an indication of the slot format to the wireless device.

[0165] Modifications, additions, or omissions may be made to method 2200 of FIGURE 22. Additionally, one or more steps in the method of FIGURE 22 may be performed in parallel or in any suitable order.

[0166] Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

[0167] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0168] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0169] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0170] Some example embodiments are described below.1. A method performed by a wireless device operating with a carrier partitioned into multiple subbands with different transmission directions, the method comprising:- receiving an indication of a slot format for one or more subband full duplex (SBFD) symbols; and- transmitting or receiving wireless signals according to the slot format.2. The method of the previous embodiment, wherein the indication of the slot format comprises any of the indication in the first, second, and third group of embodiments described herein.3. A method performed by a wireless device, the method comprising:- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.4. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.5. The method of any of the previous embodiments, further comprising:- providing user data; and- forwarding the user data to a host computer via the transmission to the base station.6. A method performed by a base station operating with a carrier partitioned into multiple subbands with different transmission directions, the method comprising:- transmitting an indication of a slot format for one or more subband full duplex (SBFD) symbols to a wireless device; and- transmitting or receiving wireless signals according to the slot format.7. The method of the previous embodiment, wherein the indication of the slot format comprises any of the indication in the first, second, and third group of embodiments described herein.8. A method performed by a base station, the method comprising:- any of the steps, features, or functions described above with respect to base station, either alone or in combination with other steps, features, or functions described above.9. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.10. The method of any of the previous embodiments, further comprising:- obtaining user data; and- forwarding the user data to a host computer or a wireless device.11. A mobile terminal comprising:- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and- power supply circuitry configured to supply power to the wireless device.12. A base station comprising:- processing circuitry configured to perform any of the steps of any of the Group B embodiments;- power supply circuitry configured to supply power to the wireless device.13. A user equipment (UE) comprising:- an antenna configured to send and receive wireless signals;- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and- a battery connected to the processing circuitry and configured to supply power to the UE.14. A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),- wherein the cellular network comprises a base station having a radio interfaceand processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.15. The communication system of the pervious embodiment further including the base station.16. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.17. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and- the UE comprises processing circuitry configured to execute a client application associated with the host application.18. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, providing user data; and- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.19. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.20. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.21. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments.22. A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward user data to a cellular networkfor transmission to a user equipment (UE),- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.23. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.24. The communication system of the previous 2 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and- the UE’s processing circuitry is configured to execute a client application associated with the host application.25. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, providing user data; and- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.26. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.27. A communication system including a host computer comprising:- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.28. The communication system of the previous embodiment, further including the UE.29. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicatewith the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.30. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application; and- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.31. The communication system of the previous 4 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.32. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.33. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.34. The method of the previous 2 embodiments, further comprising:- at the UE, executing a client application, thereby providing the user data to be transmitted; and- at the host computer, executing a host application associated with the client application.35. The method of the previous 3 embodiments, further comprising:- at the UE, executing a client application; and- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated withthe client application, wherein the user data to be transmitted is provided by the client application in response to the input data.36. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.37. The communication system of the previous embodiment further including the base station.38. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.39. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application;- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.40. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.41. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.42. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

CLAIMS:

1. A method performed by a wireless device for subband full duplex (SBFD) operation, the method comprising: receiving (2112) an indication of a slot format for one or more symbols in a semi-static time division duplex (TDD) slot configuration, wherein the indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols; and transmitting or receiving (2114) wireless signals on one or more subbands of a SBFD symbol according to the indication of the slot format.

2. The method of claim 1, wherein the indication of the slot format indicates that a symbol is one of a downlink symbol (D), uplink symbol (U), flexible (F), and SBFD symbol (S).

3. The method of claim 2, wherein for a symbol indicated as SBFD, the wireless device obtains transmission directions for one or more of the subbands within the symbol according to a predetermined configuration of subband size and location in the frequency domain.

4. The method of claim 3, wherein an indicator of the predetermined configuration is preconfigured or received via signaling from a network node.

5. The method of claim 4, wherein the indicator of the predetermined configuration is received in a downlink control indication (DCI) format contained in group common control signaling.

6. The method of claim 5, wherein the DCI format is DCI format 2 0.

7. The method of claim 1, wherein the one or more symbols include SBFD symbols and one or more of the SBFD symbols comprise one or more subbands with undetermined transmission direction., and wherein the indication of the slot format indicates a transmission direction for the one or more subbands with undetermined transmission direction.

8. The method of claim 7, wherein the one or more subbands with undetermined transmission direction are semi-statically configured with direction as flexible.

9. The method of claim 1, wherein the one or more symbols include SBFD symbols and one or more of the SBFD symbols consist of one or more subbands wherein at least one of the subbands has a semi-statically configured transmission direction, and the indication of the slot format overrides the semi-statically configured transmission direction.

10. The method of claim 9, wherein the semi-statically configured transmission direction for the at least one of the subbands is uplink or downlink.

11. The method of any one of claim 1-10, wherein the indication of the slot format is contained in a downlink control information (DCI) format contained in group common control signaling.

12. The method of claim 11, wherein the DCI format comprises DCI format 2 0.

13. The method of any one of claim 1-12, wherein the indication of the slot format comprises a slot format indicator (SFI).

14. The method of any one of claim 1-13, wherein the indication of the slot format is associated with a slot format indicator (SFI) radio network temporary identifier (RNTI).

15. A wireless device (200) capable of subband full duplex (SBFD) operation, the wireless device comprising processing circuitry (202) operable to: receive an indication of a slot format for one or more symbols in a semi-static time division duplex (TDD) slot configuration, wherein the indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols; and transmit or receive wireless signals on one or more subbands of a SBFD symbol according to the indication of the slot format.

16. The wireless device of claim 15, wherein the indication of the slot format indicates that a symbol is one of a downlink symbol (D), uplink symbol (U), flexible (F), andSBFD symbol (S).

17. The wireless device of claim 16, wherein for a symbol indicated as SBFD, the wireless device obtains transmission directions for one or more of the subbands within the symbol according to a predetermined configuration of subband size and location in the frequency domain.

18. The wireless device of claim 17, wherein an indicator of the predetermined configuration is preconfigured or received via signaling from a network node.

19. The wireless device of claim 18 wherein the indicator of the predetermined configuration is received in a downlink control indication (DCI) format contained in group common control signaling.

20. The wireless device of claim 19, wherein the DCI format is DCI format 2 0.

21. The wireless device of claim 1 , wherein the one or more symbols include SBFD symbols and one or more of the SBFD symbols comprise one or more subbands with undetermined transmission direction., and wherein the indication of the slot format indicates a transmission direction for the one or more subbands with undetermined transmission direction.

22. The wireless device of claim 21, wherein the one or more subbands with undetermined transmission direction are semi-statically configured with direction as flexible.

23. The wireless device of claim 15, wherein the one or more symbols include SBFD symbols and one or more of the SBFD symbols consist of one or more subbands wherein at least one of the subbands has a semi-statically configured transmission direction, and the indication of the slot format overrides the semi-statically configured transmission direction.

24. The wireless device of claim 23, wherein the semi-statically configured transmission direction for the at least one of the subbands is uplink or downlink.

25. The wireless device of any one of claim 15-24, wherein the indication of theslot format is contained in a downlink control information (DCI) format contained in group common control signaling.

26. The wireless device of claim 25, wherein the DCI format comprises DCI format 2_0.

27. The wireless device of any one of claim 15-26, wherein the indication of the slot format comprises a slot format indicator (SFI).

28. The wireless device of any one of claim 15-27, wherein the indication of the slot format is associated with a slot format indicator (SFI) radio network temporary identifier (RNTI).

29. A method performed by a network node for configuring a wireless device for subband full duplex (SBFD) operation, the method comprising: determining (2214) a slot format for one or more symbols in a semi-static time division duplex (TDD) slot configuration for a wireless device, wherein the indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols; and transmitting (2216) an indication of the slot format to the wireless device.

30. The method of claim 29, wherein the slot format indicates that a symbol is one of a downlink symbol (D), uplink symbol (U), flexible (F), and SBFD symbol (S).

31. The method of claim 30, further comprising transmitting (2212) to the wireless device an indication of a predetermined configuration of transmission directions for one or more of the subbands within the symbol according to a predetermined configuration of subband size and location in the frequency domain.

32. The method of claim 31, wherein the indicator of the predetermined configuration is transmitted in a downlink control indication (DCI) format contained in group common control signaling.

33. The method of claim 32, wherein the DCI format is DCI format 2 0.

34. The method of claim 29, wherein the one or more symbols include SBFD symbols and one or more of the SBFD symbols comprise one or more subbands with undetermined transmission direction, and wherein the indication of the slot format indicates a transmission direction for the one or more subbands with undetermined transmission direction.

35. The method of claim 34, wherein the one or more subbands with undetermined transmission direction are semi-statically configured with direction as flexible.

36. The method of claim 29, wherein the one or more symbols include SBFD symbols and one or more of the SBFD symbols consist of one or more subbands wherein at least one of the subbands has a semi-statically configured transmission direction, and the indication of the slot format overrides the semi-statically configured transmission direction.

37. The method of claim 36, wherein the semi-statically configured transmission direction for the at least one of the subbands is uplink or downlink.

38. The method of any one of claim 29-37, wherein the indication of the slot format is contained in a downlink control information (DCI) format contained in group common control signaling.

39. The method of claim 38, wherein the DCI format comprises DCI format 2 0.

40. The method of any one of claim 29-39, wherein the indication of the slot format comprises a slot format indicator (SFI).

41. The method of any one of claim 29-40, wherein the indication of the slot format is associated with a slot format indicator (SFI) radio network temporary identifier (RNTI).

42. A network node (300) capable of configuring a wireless device (200) for subband full duplex (SBFD) operation, the network node comprising processing circuitry (302) operable to: determine a slot format for one or more symbols in a semi-static time division duplex(TDD) slot configuration for a wireless device, wherein the indication of the slot format indicates a transmission direction for one or more subbands of the one or more symbols; and transmit an indication of the slot format to the wireless device.

43. The network node of claim 42, wherein the slot format indicates that a symbol is one of a downlink symbol (D), uplink symbol (U), flexible (F), and SBFD symbol (S).

44. The network node of claim 30, the processing circuitry further operable to transmit to the wireless device an indication of a predetermined configuration of transmission directions for one or more of the subbands within the symbol according to a predetermined configuration of subband size and location in the frequency domain.

45. The network node of claim 44, wherein the indicator of the predetermined configuration is transmitted in a downlink control indication (DCI) format contained in group common control signaling.

46. The network node of claim 45, wherein the DCI format is DCI format 2 0.

47. The network node of claim 42, wherein the one or more symbols include SBFD symbols and one or more of the SBFD symbols comprise one or more subbands with undetermined transmission direction, and wherein the indication of the slot format indicates a transmission direction for the one or more subbands with undetermined transmission direction.

48. The network node of claim 47, wherein the one or more subbands with undetermined transmission direction are semi-statically configured with direction as flexible.

49. The network node of claim 42, wherein the one or more symbols include SBFD symbols and one or more of the SBFD symbols consist of one or more subbands wherein at least one of the subbands has a semi-statically configured transmission direction, and the indication of the slot format overrides the semi-statically configured transmission direction.

50. The network node of claim 49, wherein the semi-statically configured transmission direction for the at least one of the subbands is uplink or downlink.

51. The network node of any one of claim 42-50, wherein the indication of the slot format is contained in a downlink control information (DCI) format contained in group common control signaling.

52. The network node of claim 51, wherein the DCI format comprises DCI format 2_0.

53. The network node of any one of claim 42-52, wherein the indication of the slot format comprises a slot format indicator (SFI).

54. The network node of any one of claim 42-53, wherein the indication of the slot format is associated with a slot format indicator (SFI) radio network temporary identifier (RNTI).

Images