[go: up one dir, main page]

WO2024241201A1 - Transmissions en liaison montante dans des créneaux en duplex intégral de sous-bande (sbfd) avec des ressources de surveillance de liaison descendante - Google Patents

Transmissions en liaison montante dans des créneaux en duplex intégral de sous-bande (sbfd) avec des ressources de surveillance de liaison descendante Download PDF

Info

Publication number
WO2024241201A1
WO2024241201A1 PCT/IB2024/054901 IB2024054901W WO2024241201A1 WO 2024241201 A1 WO2024241201 A1 WO 2024241201A1 IB 2024054901 W IB2024054901 W IB 2024054901W WO 2024241201 A1 WO2024241201 A1 WO 2024241201A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication
transmission
symbol
monitoring
host
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IB2024/054901
Other languages
English (en)
Inventor
Tai Do
Peter Alriksson
Yuhang Liu
Stephen Grant
Lorenza GIUPPONI
Narendar Madhavan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2024241201A1 publication Critical patent/WO2024241201A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H04L5/1469—Two-way operation using the same type of signal, i.e. duplex using time-sharing

Definitions

  • Embodiments of the disclosure relate to the field of wireless networking, more specifically, to uplink transmission in subband full duplex (SBFD) slots with downlink monitoring resources.
  • SBFD subband full duplex
  • Subband full duplex is a duplex mode being introduced to improve spectrum efficiency and cater to applications with stricter latency requirements.
  • Traditional cellular networks use Time Division Duplex (TDD) to divide the same frequency band into time slots for uplink (UL), which is from a user equipment (UE) sending data/signals to a base station, and downlink (DL), which is from the base station sending data/signal to the terminal.
  • TDD Time Division Duplex
  • UL uplink
  • UE user equipment
  • DL downlink
  • SBFD overcomes this limitation by splitting the carrier (frequency band) into sub-bands. This allows the UE to receive (downlink) and transmit (uplink) data simultaneously on non-overlapping sub-bands within the same time slot.
  • Embodiments include methods, apparatus, storage medium, and computer program for uplink transmission in subband full duplex (SBFD) slots with downlink monitoring resources.
  • a method is performed by a user equipment (UE) for uplink transmission in Subband Full Duplex (SBFD) slots, the method comprising: receiving a first indication to monitor for a downlink (DL) transmission in a symbol; receiving a second indication to prioritize transmission of an uplink (UL) signal/channel over monitoring for the DL transmission in the symbol; and performing uplink transmission based on one or more of the first indication and the second indication.
  • UE user equipment
  • SBFD Subband Full Duplex
  • a user equipment comprises a processor and machine-readable storage medium that provides instructions that, when executed by the processor, are capable of causing the processor to perform operations, including receiving a first indication to monitor for a downlink (DL) transmission in a symbol; receiving a second indication to prioritize transmission of an uplink (UL) signal/channel over monitoring for the DL transmission in the symbol; and performing uplink transmission based on one or more of the first indication and the second indication.
  • DL downlink
  • UL uplink
  • a machine-readable storage medium provides instructions that, when executed by a processor, are capable of causing the processor to perform operations, including receiving a first indication to monitor for a downlink (DL) transmission in a symbol; receiving a second indication to prioritize transmission of an uplink (UL) signal/channel over monitoring for the DL transmission in the symbol; and performing uplink transmission based on one or more of the first indication and the second indication.
  • DL downlink
  • UL uplink
  • uplink transmission is supported in a subband full duplex (SBFD) symbol, and a network can control how often a user equipment (UE) monitors for PDCCH or prioritizing uplink transmission.
  • SBFD subband full duplex
  • Figure 1A illustrates an exemplary signal transmission hierarchy in a wireless network.
  • Figure IB illustrates resource elements used for data and signaling transmission.
  • Figure 2 illustrates a subframe with 14 OFDM symbols.
  • FIG 3 illustrates multiplexing through Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • Figure 4 illustrates ten equally sized slots per radio frame for the case of 15 kHz subcarrier spacing in new radio (NR).
  • FIG. 5 illustrates the information elements (IES) for Time Division Duplex (TDD) uplink/downlink pattern configuration.
  • Figure 6 illustrates three additional Time Division Duplex (TDD) uplink/downlink pattern configurations.
  • Figure 7 illustrates the uplink and downlink allocation of carrier bandwidth and carriers.
  • Figure 8 illustrates the uplink and downlink allocation in subband full duplex (SBFD) systems.
  • Figure 9 illustrates different groups of UEs to prioritize uplink transmission per some embodiments.
  • Figure 10A illustrates configuration of UE with monitoring periodicity and duration per some embodiments.
  • Figure 10B illustrates configuration of UE with monitoring periodicity and duration per other embodiments.
  • Figure 11 illustrates prioritization of uplink transmission in symbols without monitoring occasions and guard per some embodiments.
  • Figure 12 illustrates operations performed by a User Equipment (UE) for uplink transmission in Subband Full Duplex (SBFD) slots per some embodiments.
  • UE User Equipment
  • SBFD Subband Full Duplex
  • Figure 13 illustrates operations performed by a base station for uplink transmission in Subband Full Duplex (SBFD) slots per some embodiments.
  • SBFD Subband Full Duplex
  • Figure 14 illustrates an electronic device implementing operations for uplink transmission in Subband Full Duplex (SBFD) slots per some embodiments.
  • SBFD Subband Full Duplex
  • Figure 15 illustrates an example of a communication system per some embodiments.
  • Figure 16 illustrates a user equipment (UE) per some embodiments.
  • Figure 17 illustrates a network node per some embodiments.
  • Figure 18 is a block diagram of a host, which may be an embodiment of the host of Figure 15, per various aspects described herein.
  • Figure 19 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 20 illustrates a communication diagram of a host communicating via a network node with a user equipment (UE) over a partially wireless connection per some embodiments.
  • UE user equipment
  • FIG. 1A illustrates an exemplary signal transmission hierarchy in a wireless network.
  • the exemplary signal transmission hierarchy includes the transmission unit of frame such as radio frame 102.
  • a radio frame 102 takes ten milliseconds to transmit in one embodiment.
  • the frame may contain a number of subframes such as subframe 104.
  • radio frame 102 contains ten subframes, each taking one millisecond.
  • Each subframe may contain a number of slots.
  • a subframe may contain two slots.
  • Each slot such as the slot at reference 106 may contain a number of symbols.
  • a slot contains either 7 or 14 symbols.
  • the symbol is an orthogonal frequency-division multiplexing (OFDM) symbol in one embodiment.
  • OFDM orthogonal frequency-division multiplexing
  • the frame - subframe - slot - symbol hierarchy is an example of time domain hierarchy.
  • each symbol may be transmitted over a number of subcarriers.
  • a symbol may be transmitted using a number of resource blocks (RBs), each of which may contain 12 subcarriers in one embodiment.
  • RBs resource blocks
  • each subcarrier includes a bandwidth (e.g., 7.5 kHz or 15 kHz) for transmission.
  • One subcarrier x one symbol may be referred to as a resource element (RE), which is the smallest unit of resource to be allocated for signal transmission in one embodiment.
  • RE resource element
  • the illustrated frame structure offers an example for signal transmission.
  • data and signaling transmission is performed at a lowest level of time unit (symbol level in this case), which is included in a time unit (slot level in this example) a level over the lowest level of time unit in one embodiment.
  • symbol level in this case
  • time unit slot level in this example
  • Data and signaling for one transmission from a source network device to a destination network device often use the same position within the signal transmission hierarchy, e.g., the same symbol position in consecutive slots (e.g., symbol #2 of each slot) or subframes, or in alternating slots (e.g., symbol #2 in every other slot) or subframes.
  • Figure IB illustrates resource elements used for data and signaling transmission.
  • the physical resources for transmission may be viewed as time and frequency grids as illustrated, where each resource element occupies a time period in the time domain and a frequency range in the frequency domain.
  • Each OFDM symbol includes a cyclic prefix as illustrated at reference 152.
  • Each OFDM symbol utilizes a number of resource elements.
  • the subcarrier spacing is 15k Hz
  • the resource element (RE) 152 occupies orthogonal frequencydivision multiplexing (OFDM) subcarriers within an OFDM symbol.
  • a network device may allocate some resource elements for a particular type of signaling. Such allocation may be specified through identifying the time period in the time domain and the frequency range in the frequency domain in a signal transmission hierarchy; or it may be specified through identifying specific resource elements within the signal transmission hierarchy.
  • a wireless network may use PDCCHs (physical downlink control channels) to transmit downlink control information (DCI), which provides downlink scheduling assignments and uplink scheduling grants.
  • DCI downlink control information
  • the PDCCHs are transmitted at the beginning of a slot and relate to data in the same or a later slot (for mini-slots PDCCH can also be transmitted within a regular slot) in some embodiments.
  • Different formats (sizes) of the PDCCHs are possible to handle different DCI payload sizes and different aggregation levels (i.e., different code rate for a given payload size).
  • a UE may be configured (implicitly and/or explicitly) to blindly monitor (or search) for a number of PDCCH candidates of different aggregation levels and DCI payload sizes.
  • the UE Upon detecting a valid DCI message (e.g., the decoding of a candidate being successful, and the DCI contains an ID that the UE is told to monitor) the UE follows the DCI (e.g., receives the corresponding downlink data or transmits in the uplink).
  • the blind decoding process comes at a cost in complexity in the UE but is required to provide flexible scheduling and handling of different DCI payload sizes.
  • the New radio (NR) standards in 3GPP are being designed to provide services for multiple use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and machine type communication (MTC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low latency communication
  • MTC machine type communication
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low latency communication
  • MTC machine type communication
  • NR use-cases e.g., MBB, URLLC
  • control regions e.g., time, frequency, numerologies etc.
  • PDCCH configurations e.g., operating points etc.
  • PDCCHs in NR are transmitted in configurable/dynamic control regions called control resource sets (CORESET) enabling variable use-cases.
  • CORESET is a subset of the downlink physical resource configured to carry control signaling. It is analogous to the control region in LTE but generalized in the sense that the set of physical resource blocks (PRBs) and the set of OFDM symbols in which it is located is configurable.
  • PRBs physical resource blocks
  • CORESET configuration in frequency allocation is done in units of 6 RBs using NR DL resource allocation Type 0: bitmap of RB groups (RBGs).
  • the CORESET span at the beginning of a slot is at most 2 if demodulation reference signal (DMRS) is located in OFDM Symbol (OS) #2 and is at most 3 if DMRS is located in OS #3.
  • DMRS demodulation reference signal
  • OS OFDM Symbol
  • a UE monitors one or more CORESETs. Multiple CORESETs can be overlapped in frequency and time for a UE.
  • a mini-slot transmission is also allowed to reduce latency.
  • a mini-slot may consist of any number of 1 to 14 OFDM symbols. It should be noted that 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.
  • a UE can be configured with up to four carrier bandwidth parts in the downlink with a single downlink carrier bandwidth part being active at a given 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, according to current agreements either 7 or 14 symbols (OFDM subcarrier spacing ⁇ 60 kHz) and 14 symbols (OFDM subcarrier spacing > 60 kHz).
  • Figure 2 illustrates a subframe with 14 OFDM symbols.
  • T s and T symb denote the slot and OFDM symbol duration, respectively.
  • Transmission and reception from a node can be multiplexed in the frequency domain or in the time domain (or combinations thereof).
  • Figure 3 illustrates multiplexing through Frequency Division Duplex (FDD) and Time Division Duplex (TDD). Note that the terms of terminal and user equipment (UE) are used interchangeably herein.
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • Frequency Division Duplex as illustrated to the left in Figure 3 implies that downlink and uplink transmission take place in different, sufficiently separated, frequency bands. Additionally, half-duplex FDD, implemented at the terminal-side (e.g., UE) only in some embodiments as shown to the middle of Figure 3, uses separated frequency bands in nonoverlapping time slots. Time Division Duplex (TDD), as illustrated to the right in Figure 3, implies that downlink and uplink transmission take place in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum, whereas FDD requires paired spectrum.
  • TDD can operate in unpaired spectrum
  • FDD requires paired spectrum.
  • the structure of the transmitted signal in a communication system is organized in the form of a frame structure.
  • Figure 4 illustrates ten equally sized slots per radio frame for the case of 15 kHz subcarrier spacing in new radio (NR).
  • FDD can be either full duplex or half duplex.
  • a terminal can transmit and receive simultaneously, while in half-duplex operation, the terminal cannot transmit and receive simultaneously (while a base station is capable of simultaneous reception/transmission though, e.g. receiving from one terminal while simultaneously transmitting to another terminal).
  • a half-duplex terminal is monitoring/receiving in the downlink except when explicitly being instructed to transmit in a certain subframe.
  • gNodeB also referred to as gNB
  • eNodeB Evolved Node B
  • Node B Node B
  • BTS Base Transceiver Station
  • RRH Remote Radio Head
  • small cells small cells.
  • 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.
  • this 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.
  • the TDD pattern is typically configured with at least the first IE and optionally the second IE:
  • the first IE TDD-DL-UL-ConfigCommon (cell-specific)
  • the first IE is cell specific (common to all UEs to transmit to a corresponding base station) 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 slot.
  • S slot is used in TDD frame structure and facilitates data transmission and reception between a base station and user devices (UEs) from a UE to a corresponding base station.
  • the first IE allows for very flexible configuration of the pattern characterized as follows:
  • a symbol classified as ‘F’ can be used for downlink or uplink.
  • a UE determines the direction in one of the following two ways: o Detecting a DCI that schedules/triggers a DL signal/channel, e.g., Physical Downlink Shared Channel (PDSCH), Channel State Information Reference Signal (CSI-RS), or schedules/triggers an UL signal/channel, e.g., Physical Uplink Shared Channel (PUSCH), Sounding Reference Signal (SRS), etc. o By dedicated (UE-specific) signaling of 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.’
  • a second pattern that is concatenated to the first pattern can be configured as above. If a second pattern is configured, the constraint is that the sum of the periodicities of the two patterns must evenly divide 20 ms.
  • FIG. 5 illustrates the information elements (IES) for Time Division Duplex (TDD) uplink/downlink pattern configuration.
  • the first IE, TDD-DL-UL-ConfigCommon as shown at reference 502 indicates three full ‘D’ slots, one full ‘U’ slot, with a mixed slot in between consisting of four ‘D’ symbols and three ‘U’ symbols. The remaining seven symbols in the mixed slot are classified as ‘F.’
  • the pattern as indicated by TDD-DL-UL-ConfigCommon at reference 502 is what the UE assumes.
  • the network can make use of the ‘F’ symbols flexibly, by scheduling/triggering either an uplink or a downlink signal/channel in a UE specific manner. This allows for very dynamic behavior: the direction is not known to the UE a priori; rather, the direction becomes known once the UE detects a DCI scheduling/triggering a particular DL or UL signal/channel.
  • 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-ConfigDedicated.
  • RRC radio resource control
  • the TDD-DL-UL-ConfigDedicated at reference 504 of Figure 5 illustrates three exemplary 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 (as shown in the first two exemplary configurations at reference 504.
  • 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.
  • the first seven and the last five are indicated as ‘D’ and ‘U,’ which converts some of the ‘F’ symbols (but not all in this example) to ‘D’ and ‘U,’ respectively.
  • TDD-DL-UL-ConfigDedicated can only override (i.e., specify ‘D’ or ‘U’) for symbols that are configured as ‘F’ by the cell- specific IE TDD-DL-UL-ConfigCommon.
  • a UE does not expect to have a ‘D’ symbol converted to ‘U’ or vice versa, only that a ‘F’ may be converted to a ‘D’ or a ‘U ”
  • Figure 6 illustrates three additional Time Division Duplex (TDD) uplink/downlink pattern configurations. These TDD UL/DL patterns (a), (b), and (c) are configured by TDD-DL- UL-ConfigCommon.
  • SFI slot format indicators
  • GC-PDCCH Group Common Physical Downlink Control Channel
  • 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’).
  • the UE shall neither transmit nor receive on those symbols. This can be useful to cancel an instance of periodically transmitted/received reference signals (e.g., SRS, CSI-RS) to create ‘reserved resources’ for use by another technology, e.g., LTE.
  • periodically transmitted/received reference signals e.g., SRS, CSI-RS
  • DCI downlink control information
  • the PDCCH may carry DCI in messages with different formats.
  • DCI format 0 0 and 0 1 are DCI messages used to convey uplink grants to the UE for transmission of the physical layer data channel in the uplink (PUSCH) and DCI format 1 0 and 1 1 are used to convey downlink grants for transmission of the Physical Downlink Shared Channel (PDSCH).
  • Other DCI formats (2 0, 2 1, 2 2 and 2 3) are used for other purposes such as transmission of slot format information, reserved resource, transmit power control information, etc.
  • a PDCCH is confined to one CORESET •
  • a PDCCH is carried by 1, 2, 4, 8 or 16 CCEs (control channel elements)
  • the number of CCEs of a PDCCH is referred to as the aggregation level (AL) of the PDCCH
  • a base station such as gNodeB configure/signal to the UEs information on where (on frequency) and when (on time) to monitor the PDCCH.
  • the information could include:
  • Search Space is a set of PDCCH candidates of a given aggregation level L monitored by one or several UEs.
  • a PDCCH candidate is a set of CCEs in which a UE may expect to receive a PDCCH of a certain DCI format and a certain aggregation level
  • a USS UE-specific search space
  • a CSS common search space
  • Each SS is associated with one control resource set (CORESET)
  • a CORESET is a subset of the downlink physical resource configured to carry control signaling (e.g., PDCCH).
  • SBFD subband full duplex
  • the left-hand side of Figure 8 is in contrast to a conventional TDD system as shown on the left-hand side of Figure 7, where the former indicates the center portion of the SBFD carrier in the first three slots is used for UL reception while the rest of the carrier continues to be used for DL transmission, unlike the latter where the entire bandwidth in the same slots is used for DL transmission.
  • the SBFD carrier at the left-hand side of Figure 8 uses a single carrier with three subbands, and implements both uplink and downlink traffic in that carrier at the same time. [0062] The similar contrast is shown between using SBFD and not using it at the right-hand side of Figures 7 and 8.
  • some carriers in the SBFD system can be used for a different direction than that of the other carriers as shown in the right-hand side of Figure 8.
  • three TDD carriers are implemented, and each carrier transmits only uplink or downlink traffic at the same time.
  • UEs are not allowed to transmit UL in those symbols. That is according to 38.213: “For a set of symbols of a slot that are indicated to a UE as downlink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, the UE does not transmit PUSCH, PUCCH, PRACH, or SRS when the PUSCH, PUCCH, PRACH, or SRS overlaps, even partially, with the set of symbols of the slot. ”
  • the UEs are not allowed to transmit UL.
  • a SBFD symbol is a symbol where SBFD is configured; and a SBFD symbol may be configured with UL, DL subbands (UL, DL resources) and transmit DL and UL in the same carrier (e.g., the symbols in the first three slots of the left-hand side of Figure 8 are SBFD symbols).
  • Figure 8 shows a SBFD carrier for both DL and UL transmission using subbands (with each subband used for one directional DL or UL transmission at a given time), while the right-hand side of Figure 8 shows multiple carriers each used for one directional DL or UL transmission at a given time.
  • Frequency locations of DL subband(s) are known to the SBFD aware UE o
  • the frequency location of DL subband(s) can be explicitly indicated or implicitly derived
  • UEs are indicated to prioritize UL transmissions over receiving or monitoring DL transmissions in SBFD slots.
  • Some embodiments implement a method where a UE operating in a subband full duplex (SBFD) or full duplex network receives: (a) a first indication to monitor for a DL transmission in a symbol, and (b) a second indication to prioritize transmission of an UL signal/channel over monitoring for the DL transmission in the symbol.
  • SBFD subband full duplex
  • the first indication configures the symbol as a symbol with DL transmission.
  • the symbol with DL transmission may be a DL symbol, a flexible symbol, or a SBFD symbol.
  • the symbol with DL transmission may be configured via cellspecific signaling of the TDD UL/DL pattern.
  • the cell specific signaling is via the higher layer IE, TDD-DL-UL-ConfigCommon.
  • the first indication configures the symbol as DL via UE dedicated signaling of the TDD UL/DL pattern.
  • the UE dedicated signaling is via the higher layer IE, TDD-DL-UL-ConfigDedicated.
  • the first indication configures one of the following in the symbol: (a) common search space (CSS) for PDCCH monitoring, and (b) UE-specific search space (USS) for PDCCH monitoring.
  • SCS common search space
  • USS UE-specific search space
  • the first indication is received via higher layer signaling.
  • the second indication: [0077] (i) may be received implicitly by a UE-dedicated DCI that schedules an UL transmission in the symbol;
  • (iii) may be received explicitly as part of the configuration of a configured grant UL signal/channel in the symbol that is one of (a) configured grant (CG) PUSCH, (b) SRS, (c) PRACH, and (d) PUCCH.
  • (iv) may be received via a cell-specific or UE-specific RRC parameter
  • (v) may be received via LI signaling that applies to one of the following: (a) a single UE and (b) a group of UEs.
  • (vi) may be received via media access control (MAC) Control element (CE);
  • MAC media access control
  • CE Control element
  • (vii) may be included in the configuration of each search space (SS); and/or
  • (viii) may apply to both a dynamically scheduled UL transmission and a transmission of a configured grant UL signal/channel.
  • the network tell UEs when (in which symbol) to monitor DL transmissions, e.g., configure the symbol as DL in TDD DL/UL pattern (IE TDD- DL-UL-ConfigCommon or TDD-DL-UL-ConfigDedicated), or configure SS (USS or CSS) for PDCCH monitoring over the symbol, or one of the higher layer signals.
  • Such ways may use the first indication discussed above for the network to tell the UEs when to monitor the DL transmission.
  • a second indication/configuration could be provided to a subset of UEs using one or more of the following options per some embodiments:
  • a UE could prioritize a configured UL transmission in the symbol over DL monitoring if it is received implicitly or explicitly an indicator as part of the configuration of a configured UL signal/channel in the symbol that is one of (a) configured grant (CG) PUSCH, (b) SRS, (c) PRACH, and (d) PUCCH.
  • CG configured grant
  • SRS SRS
  • PRACH PRACH
  • PUCCH PUCCH
  • the indicator is included in CG UL activation DCI (only applicable for Type 2 CG).
  • a UE could prioritize an UL transmission over DL monitoring in the symbol if the UE receives a UE-specified RRC parameter, e.g., TDD-DL-UL-ConfigDedicated indicating that the symbol is UL or flexible, or any other symbol type other than DL.
  • a UE-specified RRC parameter e.g., TDD-DL-UL-ConfigDedicated indicating that the symbol is UL or flexible, or any other symbol type other than DL.
  • a UE could prioritize an UL transmission over DL monitoring in the symbol if the UE receives a (cell specific) RRC parameter indicating the priority, e.g., new RRC parameter to indicate the prioritization.
  • a UE receives implicitly or explicitly an indicator to prioritize an UL transmission over DL monitoring by a dedicated DCI.
  • a UE receives implicitly or explicitly an indicator to prioritize an UL transmission over DL monitoring by a common DCI.
  • the prioritization could also be indicated via MAC CE.
  • a parameter can be added to the search space configuration indicating if monitoring of this search space should be prioritized over UL transmissions or not.
  • TypeO-PDCCH CSS is at least used to schedule System Information Block 1 (SIB1) and the time locations are coupled to the SSB positions and described by fixed rules in 38.213 ⁇ 13.
  • SIB1 System Information Block 1
  • the same or different indicators/configurations can be used to indicate the prioritization for a dynamically scheduled UL transmission and a configured grant UL transmission.
  • prioritization may occur if the UL transmission and the DL monitoring occur in time resources that are either: (a) partially overlapping, (b) fully overlapping, or (c) not overlapping, but with a time gap less than a threshold.
  • a first prioritization may be a default prioritization
  • a second prioritization may be applied for an indicated duration of time before reverting to the default prioritization, where the indicated duration of time is included in the second indication.
  • the default prioritization may be prioritizing DL monitoring over UL transmission and the second prioritization is the opposite in some embodiments, while in alternative embodiment, the default prioritization prioritizes UL transmission over DL monitoring and the second prioritization is the opposite.
  • the UL prioritization is only applied over a certain duration of time.
  • a gNodeB could indicate a certain duration of time, where the UE only prioritizes dynamically scheduled and/or configured UL transmissions over monitoring DL transmissions during the duration of time; and outside of that duration of time, the UE prioritizes monitoring DL transmissions.
  • an indicator is introduced for group-common DCI to turn on/off the UL prioritization. Then, the duration between applicable timings of two group-common DCIs (one to turn on and one to turn off) can be used as the prioritization period.
  • PDCCH skipping indicators introduced in DCI formats 0 1/0 2/1 1/1-2, defined for PDCCH monitoring adaptation in TS 38.213, and which apply to Type3-PDCCH CSS set or UE-specific search space.
  • a UE can be triggered to skip PDCCH monitoring during a specific period from the next slot after the indication is received. After this duration the UE is required to monitor PDCCH again.
  • PDCCH skipping configuration values, and duration set specified in Release 17 should be adapted to the UL prioritization case. For instance, the UE may skip those PDCCH monitoring occasions if the DCIs indicate so and the UE is scheduled with UL transmissions overlapping with those PDCCH monitoring occasions. Otherwise, the UE still monitors those monitoring occasions.
  • the location of the indicated duration of time may be shifted between the DL monitoring occasions.
  • the duration of the indicated duration of time is different between the DL monitoring occasions.
  • the duration of time could be used as a prioritization window, where it could be shifted between time occasions. For instance, we have CSS every five slots and the duration of time is one slot, then this “duration of time” will be shifted to be appeared in every five slots or every 10 slots depending on how often the network wants to let the UE prioritize UL transmissions.
  • gNodeB could configure/indicate prioritization so that a UE does not skip too many consecutive DL monitoring occasions. For instance, gNodeB could configure/indicate one group of UEs to prioritize UL transmissions in the n-th DL monitoring occasion, then a different group of UEs to prioritize UL transmissions in the next DL monitoring occasion.
  • Figure 9 illustrates different groups of UEs to prioritize uplink transmission per some embodiments. USS and CSS at the beginnings of SBFD symbols of each slot in the figure are search spaces where UEs monitoring for DL control information.
  • the CSS in the first and sixth slots could be prioritized to different UEs. For example, a first group of UEs at reference 902 may prioritize UL transmissions and skip monitoring CSS in the first slot, a second group of UEs at reference 904 may prioritize UL transmissions and skip monitoring CSS in the sixth slot.
  • the framework specified in Release 17 TS38.213 for dynamic search space group switching could be extended to the scope of adjusting the UL prioritization pattern for different UEs or groups of UEs.
  • the UE can be indicated to switch to a specific search space group and stop PDCCH monitoring in any other search space group in order to prioritize UL.
  • the different search space groups can be defined with different patterns or periodicity depending on quality of service (QoS) needs of UL communications, per UE or group of UEs (with very few monitoring occasions, or with sparser monitoring occasions, etc.).
  • QoS quality of service
  • Search space group switching applies to Type3 -PDCCH CSS set or UE-specific search space set for PDCCH monitoring on an active downlink and is based on an indication in DCI formats 0_l/0_2/l_l/l_2. They have been specified in Release 17, in the context of PDCCH monitoring adaptation.
  • a UE can be configured with up to three different search space groups, and this could be extended for UL prioritization purposes.
  • the DL monitoring occasions may occur periodically, and the second indication may indicate for each period whether the UE can skip monitoring for DL transmission(s) in a period; and if so, which occasions(s) in a period the UE can skip in order to prioritize transmission of UL signal(s)/channel(s).
  • the UE in the first indication, is configured with a time domain pattern of monitoring occasions with periodicity P and duration D (number of monitoring occasions) within each period.
  • the UE receives signaling (either via LI, MAC-CE, or RRC) to indicate that it should skip PDCCH monitoring in specific monitoring occasions of the time domain pattern and prioritize an UL transmission instead.
  • signaling either via LI, MAC-CE, or RRC
  • Figure 10A illustrates configuration of UE with monitoring periodicity and duration per some embodiments.
  • Figure 10B illustrates configuration of UE with monitoring periodicity and duration per other embodiments.
  • D 1
  • the signaling can indicate that the UE should skip every N-th monitoring occasion across periods of the monitoring pattern. As shown, every second monitoring occasion is skipped.
  • UEs may only prioritize an UL transmission in the symbol if it does not overlap with a monitoring occasion of a CSS.
  • UEs only prioritize UL transmissions in symbols that do not overlap with CSS and some possible guard symbols for switching from DL monitoring/receiving to UL transmissions.
  • gNodeB could schedule a UE to transmit on UL mini-slots where some symbols are punctured for CSS monitoring and switching gap.
  • Figure 11 illustrates prioritization of uplink transmission in symbols without monitoring occasions and guard per some embodiments. As shown, either a first group of UEs at reference 1102 or a second group of UEs at reference 1104 prioritizes uplink transmission in symbols without CSS plus guard band.
  • the first and second groups of UEs may be the same or different groups of UEs in a same wireless network.
  • UEs only transmit UL in symbols that do not overlap with CSS (see that CSS does not overlap with “U” in time as shown in the figure) and some possible guard symbols for switching from DL monitoring/receiving to UL transmissions.
  • a gNB could schedule a UE to transmit on UL mini-slots where some symbols are punctured for CSS monitoring and switching gap.
  • Figure 11 is different from Figure 9 as the latter allows a UE to transmit uplink in symbols of CSS + guard while the former does not.
  • the network can dynamically control how often the UE monitors for PDCCH vs. prioritizing UL. For example, the network can configure the UE to monitor for PDCCH frequently, but then dynamically change whether PDCCH monitoring, or UL transmission is prioritized.
  • Figure 12 illustrates operations performed by a User Equipment (UE) for uplink transmission in Subband Full Duplex (SBFD) slots per some embodiments.
  • the UE receives a first indication to monitor for a downlink (DL) transmission in a symbol.
  • the UE receives a second indication to prioritize transmission of an uplink (UL) signal/channel over monitoring for the DL transmission in the symbol.
  • the UE performs uplink transmission based on the first and/or second indication.
  • the first indication is to configure the symbol as DL via cellspecific signaling of the time division duplex (TDD) UL/DL pattern.
  • TDD time division duplex
  • the cell-specific signaling is via a higher lay information element (IE) that indicates TDD-DL-UL-ConfigCommon.
  • IE higher lay information element
  • the first indication is to configure the symbol as DL via UE dedicated signaling of the TDD UL/DL pattern.
  • the UE dedicated signaling is via the higher layer IE TDD-DL- UL-ConfigDedicated.
  • the first indication is to configure one of the following in the symbol: common search space (CSS) for PDCCH monitoring, and UE-specific search space (USS) for PDCCH monitoring.
  • SCS common search space
  • USS UE-specific search space
  • the first indication is received via higher layer signaling.
  • the higher layer signaling is from the radio resource control (RRC) RRC layer.
  • RRC radio resource control
  • the second indication is received implicitly by a UE-dedicated DCI that schedules an UL transmission in the symbol.
  • the second indication is received implicitly or explicitly by a group-common DCI.
  • the second indication is received implicitly or explicitly as part of the configuration of a configured UL signal/channel in the symbol that is one of configured grant (CG) PUSCH, SRS (Sounding Reference Signal), PRACH (Physical Random Access Channel), and PUCCH (Physical Uplink Control Channel).
  • CG configured grant
  • SRS Sounding Reference Signal
  • PRACH Physical Random Access Channel
  • PUCCH Physical Uplink Control Channel
  • the second indication is received via a cell-specific or UE-specific radio resource control (RRC) parameter.
  • RRC radio resource control
  • the second indication is received via LI signaling that applies to one of a single UE and a group of UEs.
  • the second indication is received via media access control (MAC) Control element (CE).
  • MAC media access control
  • CE Control element
  • the second indication is included in the configuration of each search space (SS).
  • the second indication applies to both a dynamically scheduled UL transmission and a transmission of a configured grant UL signal/channel.
  • the second indication includes one indication applies to a dynamically scheduled UL transmission and a different indication applies to transmission of a configured grant UL signal/channel.
  • the prioritization occurs if the UL transmission and the DL monitoring occur in resources that are either partially overlapping, fully overlapping, or not overlapping, but with a time gap less than a threshold.
  • a first prioritization is a default prioritization
  • a second prioritization is applied for an indicated duration of time before reverting to the default prioritization, where the indicated duration of time is included in the second indication.
  • a location of the indicated duration of time is shifted between the DL monitoring occasions.
  • the duration of the indicated duration of time is different between the DL monitoring occasions.
  • the DL monitoring occasions occur periodically and the second indication indicates for each period whether the UE can skip monitoring for DL transmission(s) in a period, and if so, which occasions(s) in a period the UE can skip in order to prioritize transmission ofUL signal(s)/channel(s).
  • UEs only prioritizes an UL transmission in the symbol if it does not overlap with a monitoring occasion of a common search space (CSS).
  • SCS common search space
  • Figure 13 illustrates operations performed by a base station for uplink transmission in Subband Full Duplex (SBFD) slots per some embodiments.
  • the base station transmits to a User Equipment (UE) a first indication to monitor for a downlink (DL) transmission in a symbol.
  • the base station transmits to the UE a second indication to prioritize transmission of an uplink (UL) signal/channel over monitoring for the DL transmission in the symbol.
  • the base station monitors uplink transmission from the UE based on the first and/or second indication.
  • UE User Equipment
  • the first indication is to configure the symbol as DL via cellspecific signaling of the time division duplex (TDD) UL/DL pattern.
  • TDD time division duplex
  • the cell-specific signaling is via an information element (IE) that specifies a TDD UL/DL pattern that is cell specific but common to a plurality of UEs.
  • the cell-specific signal may be the higher lay information element (IE) TDD-DL-UL- ConfigCommon .
  • the first indication is to configure the symbol as DL via UE dedicated signaling of the TDD UL/DL pattern.
  • the UE dedicated signaling is via the higher layer IE TDD-DL- UL-ConfigDedicated.
  • the first indication is to configure one of the following in the symbol: common search space (CSS) for PDCCH monitoring, and UE-specific search space (USS) for PDCCH monitoring.
  • CSS common search space
  • USS UE-specific search space
  • the first indication is transmitted via higher layer signaling.
  • the second indication is transmitted implicitly by a UE- dedicated DCI that schedules an UL transmission in the symbol.
  • the second indication is transmitted implicitly or explicitly by a group-common DCI.
  • the second indication is transmitted implicitly or explicitly as part of the configuration of a configured UL signal/channel in the symbol that is one of configured grant (CG) PUSCH, SRS (Sounding Reference Signal), PRACH (Physical Random Access Channel), and PUCCH (Physical Uplink Control Channel).
  • CG configured grant
  • SRS Sounding Reference Signal
  • PRACH Physical Random Access Channel
  • PUCCH Physical Uplink Control Channel
  • the second indication is transmitted via a cell-specific or UE-specific radio resource control (RRC) parameter.
  • RRC radio resource control
  • the second indication is transmitted via LI signaling that applies to one of a single UE and a group of UEs.
  • the second indication is transmitted via media access control (MAC) Control element (CE).
  • MAC media access control
  • CE Control element
  • the second indication is included in the configuration of each search space (SS).
  • the second indication applies to both a dynamically scheduled UL transmission and a transmission of a configured grant UL signal/channel.
  • the second indication includes one indication applies to a dynamically scheduled UL transmission and a different indication applies to transmission of a configured grant UL signal/channel.
  • the prioritization occurs if the UL transmission and the DL monitoring occur in resources that are either partially overlapping, fully overlapping, or not overlapping, but with a time gap less than a threshold.
  • a first prioritization is a default prioritization
  • a second prioritization is applied for an indicated duration of time before reverting to the default prioritization, where the indicated duration of time is included in the second indication.
  • a location of the indicated duration of time is shifted between the DL monitoring occasions.
  • the duration of the indicated duration of time is different between the DL monitoring occasions.
  • the DL monitoring occasions occur periodically and the second indication indicates for each period whether the UE can skip monitoring for DL transmission(s) in a period, and if so, which occasions(s) in a period the UE can skip in order to prioritize transmission of UL signal(s)/channel(s).
  • UEs only prioritizes an UL transmission in the symbol if it does not overlap with a monitoring occasion of a common search space (CSS).
  • SCS common search space
  • FIG. 14 illustrates an electronic device implementing operations for uplink transmission in Subband Full Duplex (SBFD) slots per some embodiments.
  • the electronic device may be a host in a cloud system, or a network node/UE in a wireless/wireline network, and the operating environment and further embodiments the host, the network node, the UE are discussed in more details herein below.
  • the electronic device 1402 may be implemented using custom application-specific integrated-circuits (ASICs) as processors and a special-purpose operating system (OS), or common off-the-shelf (COTS) processors and a standard OS.
  • ASICs application-specific integrated-circuits
  • OS special-purpose operating system
  • COTS common off-the-shelf
  • the electronic device 1402 implements a coordinator for uplink transmission in SBFD slots 1455.
  • the electronic device 1402 includes hardware 1440 comprising a set of one or more processors 1442 (which are typically COTS processors or processor cores or ASICs) and physical NIs 1446, as well as non-transitory machine-readable storage media 1449 having stored therein software 1450.
  • the one or more processors 1442 may execute the software 1450 to instantiate one or more sets of one or more applications 1464A-R. While one embodiment does not implement virtualization, alternative embodiments may use different forms of virtualization.
  • the virtualization layer 1454 represents the kernel of an operating system (or a shim executing on a base operating system) that allows for the creation of multiple instances 1462A-R called software containers that may each be used to execute one (or more) of the sets of applications 1464A-R.
  • the multiple software containers also called virtualization engines, virtual private servers, or jails
  • the set of applications running in a given user space cannot access the memory of the other processes.
  • the virtualization layer 1454 represents a hypervisor (sometimes referred to as a virtual machine monitor (VMM)) or a hypervisor executing on top of a host operating system, and each of the sets of applications 1464A-R run on top of a guest operating system within an instance 1462A-R called a virtual machine (which may in some cases be considered a tightly isolated form of software container) that run on top of the hypervisor - the guest operating system and application may not know that they are running on a virtual machine as opposed to running on a “bare metal” host electronic device, or through paravirtualization the operating system and/or application may be aware of the presence of virtualization for optimization purposes.
  • a hypervisor sometimes referred to as a virtual machine monitor (VMM)
  • VMM virtual machine monitor
  • one, some, or all of the applications are implemented as unikemel(s), which can be generated by compiling directly with an application only a limited set of libraries (e.g., from a library operating system (LibOS) including drivers/libraries of OS services) that provide the particul r OS services needed by the application.
  • libraries e.g., from a library operating system (LibOS) including drivers/libraries of OS services
  • unikernel can be implemented to run directly on hardware 1440, directly on a hypervisor (in which case the unikemel is sometimes described as running within a LibOS virtual machine), or in a software container
  • embodiments can be implemented fully with unikemels running directly on a hypervisor represented by virtualization layer 1454, unikemels running within software containers represented by instances 1462A-R, or as a combination of unikemels and the above-described techniques (e.g., unikemels and virtual machines both run directly on a hypervisor, unikemels, and sets of applications that are run in different software containers).
  • the software 1450 contains the coordinator for uplink transmission in SBFD slots 1455 that performs operations described with reference to operations as discussed relating to Figures 1 to 13.
  • the coordinator for uplink transmission in SBFD slots 1455 may be instantiated within the applications 1464A-R.
  • the instantiation of the one or more sets of one or more applications 1464A-R, as well as virtualization if implemented, are collectively referred to as software instance(s) 1452.
  • Each set of applications 1464A-R, corresponding virtualization construct e.g., instance 1462A-R
  • that part of the hardware 1440 that executes them forms a separate virtual electronic device 1460A-R.
  • a network interface may be physical or virtual.
  • IP Internet Protocol
  • an interface address is an IP address assigned to an NI, be it a physical NI or virtual NI.
  • a virtual NI may be associated with a physical NI, with another virtual interface, or stand on its own (e.g., a loopback interface, a point-to-point protocol interface).
  • a NI (physical or virtual) may be numbered (a NI with an IP address) or unnumbered (a NI without an IP address).
  • the NI is shown as network interface card (NIC) 1444.
  • the physical network interface 1446 may include one or more antenna of the electronic device 1402. An antenna port may or may not correspond to a physical antenna. The antenna comprises one or more radio interfaces.
  • FIG. 15 illustrates an example of a communication system 1500 per some embodiments.
  • the communication system 1500 includes a telecommunication network 1502 that includes an access network 1504, such as a radio access network (RAN), and a core network 1506, which includes one or more core network nodes 1508.
  • the access network 1504 includes one or more access network nodes, such as network nodes 1510A and 1510B (one or more of which may be generally referred to as network nodes 1510), or any other similar 3rd Generation Partnership Project (3 GPP) access nodes or non-3GPP access points.
  • 3 GPP 3rd Generation Partnership Project
  • a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor.
  • the telecommunication network 1502 includes one or more Open-RAN (ORAN) network nodes.
  • ORAN Open-RAN
  • An ORAN network node is a node in the telecommunication network 1502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1502, including one or more network nodes 1510 and/or core network nodes 1508.
  • ORAN Open-RAN
  • Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • the network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
  • the network nodes 1510 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1512A, 1512B, 1512C, and 1512D (one or more of which may be generally referred to as UEs 1512) to the core network 1506 over one or more wireless connections.
  • UE user equipment
  • 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.
  • the communication system 1500 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 1500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1512 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 1510 and other communication devices.
  • the network nodes 1510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1512 and/or with other network nodes or equipment in the telecommunication network 1502 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 1502.
  • the core network 1506 connects the network nodes 1510 to one or more hosts, such as host 1516. These connections may be direct or indirect via one or more intermediary networks or devices.
  • the core network 1506 includes one more core network nodes (e.g., core network node 1508) 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 1508.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber 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).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1516 may be under the ownership or control of a service provider other than an operator or provider of the access network 1504 and/or the telecommunication network 1502, and may be operated by the service provider or on behalf of the service provider.
  • the host 1516 may host a variety of applications to provide one or more services. 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.
  • the communication system 1500 of Figure 15 enables connectivity between the UEs, network nodes, and hosts.
  • 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.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 1502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 1502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1502. For example, the telecommunication network 1502 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.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 1512 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1504.
  • a UE may be configured for operating in single- or multiple radio access technology (rnulti- RAT) or multi-standard mode.
  • rnulti- RAT single- or multiple radio access technology
  • 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).
  • MR- DC multi-radio dual connectivity
  • the hub 1514 communicates with the access network 1504 to facilitate indirect communication between one or more UEs (e.g., UE 1512C and/or 1512D) and network nodes (e.g., network node 1510B).
  • the hub 1514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1514 may be a broadband router enabling access to the core network 1506 for the UEs.
  • the hub 1514 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1514 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.
  • the hub 1514 may be a content source. For example, for a UE that is a virtual reality (VR) headset, display, loudspeaker or other media delivery device, the hub 1514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
  • the hub 1514 may have a constant/persistent or intermittent connection to the network node 1510b.
  • the hub 1514 may also allow for a different communication scheme and/or schedule between the hub 1514 and UEs (e.g., UE 1512C and/or 1512D), and between the hub 1514 and the core network 1506.
  • the hub 1514 is connected to the core network 1506 and/or one or more UEs via a wired connection.
  • the hub 1514 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 1504 and/or to another UE over a direct connection.
  • M2M machine-to-machine
  • UEs may establish a wireless connection with the network nodes 1510 while still connected via the hub 1514 via a wired or wireless connection.
  • the hub 1514 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 1510B.
  • the hub 1514 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1510B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 16 illustrates a UE 1600 per some embodiments.
  • 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, vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • 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
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • 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), vehi cl e-to- vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-infrastructure
  • V2X vehicle- to-everything
  • 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).
  • 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).
  • the UE 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input/output interface 1606, a power source 1608, a memory 1610, a communication interface 1612, 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.
  • the processing circuitry 1602 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 1610.
  • the processing circuitry 1602 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.
  • the processing circuitry 1602 may include multiple central processing units (CPUs).
  • the input/output interface 1606 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 1600.
  • 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.
  • USB Universal Serial Bus
  • the power source 1608 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 1608 may further include power circuitry for delivering power from the power source 1608 itself, and/or an external power source, to the various parts of the UE 1600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1608.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1608 to make the power suitable for the respective components of the UE 1600 to which power is supplied.
  • the memory 1610 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 readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1610 includes one or more application programs 1614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1616.
  • the memory 1610 may store, for use by the UE 1600, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1610 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 Universal Subscriber Identity Module (USIM) and/or IP Multimedia Services Identity Module (ISIM), other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.’
  • the memory 1610 may allow the UE 1600 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 1610, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1602 may be configured to communicate with an access network or other network using the communication interface 1612.
  • the communication interface 1612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1622.
  • the communication interface 1612 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 1618 and/or a receiver 1620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1618 and receiver 1620 may be coupled to one or more antennas (e.g., antenna 1622) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1612 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.
  • GPS global positioning system
  • 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/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), Quick UDP Internet Connections (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/internet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Quick UDP Internet Connections
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 1612, 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).
  • 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.
  • the states of the actuator, the motor, or the switch may change.
  • 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.
  • 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.
  • 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 voice controlled 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-
  • AR Augmented Reality
  • VR
  • 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 3 GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • 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.
  • any number of UEs may be used together with respect to a single use case.
  • 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.
  • 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.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • the UE 1600 may implement the coordinator for uplink transmission in SBFD slots 1455 and perform operations described herein.
  • FIG. 17 illustrates a network node 1700 per some embodiments.
  • 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.
  • 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) NodeBs
  • 0RAN nodes or components of an 0-RAN node e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR.
  • 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, distributed units (e.g., in an 0-RAN access node) 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).
  • DAS distributed antenna system
  • 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).
  • MSR multi -standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1700 includes a processing circuitry 1702, a memory 1704, a communication interface 1706, and a power source 1708.
  • the network node 1700 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.
  • the network node 1700 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1704 for different RATs) and some components may be reused (e.g., a same antenna 1710 may be shared by different RATs).
  • the network node 1700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (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 1700.
  • RFID Radio Frequency Identification
  • the processing circuitry 1702 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 1700 components, such as the memory 1704, to provide network node 1700 functionality.
  • the processing circuitry 1702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1702 includes one or more of radio frequency (RF) transceiver circuitry 1712 and baseband processing circuitry 1714. In some embodiments, the radio frequency (RF) transceiver circuitry 1712 and the baseband processing circuitry 1714 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 1712 and baseband processing circuitry 1714 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 1702 includes one or more of radio frequency (RF) transceiver circuitry 1712 and baseband processing circuitry 1714.
  • the radio frequency (RF) transceiver circuitry 1712 and the baseband processing circuitry 1714 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
  • the memory 1704 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 1702.
  • 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
  • the memory 1704 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 1702 and utilized by the network node 1700.
  • the memory 1704 may be used to store any calculations made by the processing circuitry 1702 and/or any data received via the communication interface 1706.
  • the processing circuitry 1702 and memory 1704 is integrated.
  • the communication interface 1706 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1706 comprises port(s)/terminal(s) 1716 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1706 also includes radio front-end circuitry 1718 that may be coupled to, or in certain embodiments a part of, the antenna 1710.
  • Radio front-end circuitry 1718 comprises filters 1720 and amplifiers 1722.
  • the radio front-end circuitry 1718 may be connected to an antenna 1710 and processing circuitry 1702.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1710 and processing circuitry 1702.
  • the radio front-end circuitry 1718 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 1718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1720 and/or amplifiers 1722. The radio signal may then be transmitted via the antenna 1710. Similarly, when receiving data, the antenna 1710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1718. The digital data may be passed to the processing circuitry 1702. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
  • the network node 1700 does not include separate radio front-end circuitry 1718, instead, the processing circuitry 1702 includes radio front-end circuitry and is connected to the antenna 1710.
  • the processing circuitry 1702 includes radio front-end circuitry and is connected to the antenna 1710.
  • all or some of the RF transceiver circuitry 1712 is part of the communication interface 1706.
  • the communication interface 1706 includes one or more ports or terminals 1716, the radio front-end circuitry 1718, and the RF transceiver circuitry 1712, as part of a radio unit (not shown), and the communication interface 1706 communicates with the baseband processing circuitry 1714, which is part of a digital unit (not shown).
  • the antenna 1710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1710 may be coupled to the radio front-end circuitry 1718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1710 is separate from the network node 1700 and connectable to the network node 1700 through an interface or port.
  • the antenna 1710, communication interface 1706, and/or the processing circuitry 1702 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 1710, the communication interface 1706, and/or the processing circuitry 1702 may be configured to perform any transmitting operations described herein as being performed 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.
  • the power source 1708 provides power to the various components of network node 1700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1700 with power for performing the functionality described herein.
  • the network node 1700 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 1708.
  • the power source 1708 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.
  • Embodiments of the network node 1700 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.
  • the network node 1700 may include user interface equipment to allow input of information into the network node 1700 and to allow output of information from the network node 1700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1700.
  • the network node 1700 may implement the coordinator for uplink transmission in SBFD slots 1455 and perform operations described herein.
  • FIG 18 is a block diagram of a host 1800, which may be an embodiment of the host 1516 of Figure 15, per various aspects described herein.
  • the host 1800 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 1800 may provide one or more services to one or more UEs.
  • the host 1800 may implement the coordinator for uplink transmission in SBFD slots 1455 and perform operations described herein.
  • the host 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input/output interface 1806, a network interface 1808, a power source 1810, and a memory 1812.
  • processing circuitry 1802 that is operatively coupled via a bus 1804 to an input/output interface 1806, a network interface 1808, a power source 1810, and a memory 1812.
  • 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 16 and 17, such that the descriptions thereof are generally applicable to the corresponding components of host 1800.
  • the memory 1812 may include one or more computer programs including one or more host application programs 1814 and data 1816, which may include user data, e.g., data generated by a UE for the host 1800 or data generated by the host 1800 for a UE.
  • Embodiments of the host 1800 may utilize only a subset or all of the components shown.
  • the host application programs 1814 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), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (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).
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG Moving Picture Experts Group
  • VP9 Moving Picture Experts Group
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • the host application programs 1814 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 1800 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1814 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.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG 19 is a block diagram illustrating a virtualization environment 1900 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • 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 1900 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.
  • VMs virtual machines
  • the virtualization environment 1900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
  • Applications 1902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q500 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 1902 may implement the coordinator for uplink transmission in SBFD slots 1455 and perform operations described herein.
  • Hardware 1904 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 1906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1908 A and 1908B (one or more of which may be generally referred to as VMs 1908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1906 may present a virtual operating platform that appears like networking hardware to the VMs 1908.
  • the VMs 1908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1906.
  • Different embodiments of the instance of a virtual appliance 1902 may be implemented on one or more of VMs 1908, 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.
  • NFV network function virtualization
  • a VM 1908 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 1908, and that part of hardware 1904 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.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1908 on top of the hardware 1904 and corresponds to the application 1902.
  • Hardware 1904 may be implemented in a standalone network node with generic or specific components. Hardware 1904 may implement some functions via virtualization. Alternatively, hardware 1904 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 1910, which, among others, oversees lifecycle management of applications 1902.
  • hardware 1904 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 to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1912 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 20 illustrates a communication diagram of a host 2002 communicating via a network node 2004 with a UE 2006 over a partially wireless per some embodiments.
  • Either host 2002 or network node 2004 may implement the coordinator for uplink transmission in SBFD slots 1455 and perform operations described herein. In some embodiments, each of host 2002 or network node 2004 may perform a portion of the operations performed by the coordinator for uplink transmission in SBFD slots 1455 and perform operations described herein.
  • host 2002 Like host 1800, embodiments of host 2002 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 2002 also includes software, which is stored in or accessible by the host 2002 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 2006 connecting via an over-the-top (OTT) connection 2050 extending between the UE 2006 and host 2002.
  • OTT over-the-top
  • the network node 2004 includes hardware enabling it to communicate with the host 2002 and UE 2006.
  • connection 2060 may be direct or pass through a core network (like core network 1506 of Figure 15) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 1506 of Figure 15
  • intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 2006 includes hardware and software, which is stored in or accessible by UE 2006 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 2006 with the support of the host 2002.
  • 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 2006 with the support of the host 2002.
  • an executing host application may communicate with the executing client application via the OTT connection 2050 terminating at the UE 2006 and host 2002.
  • 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 2050 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 2050.
  • the OTT connection 2050 may extend via a connection 2060 between the host 2002 and the network node 2004 and via a wireless connection 2070 between the network node 2004 and the UE 2006 to provide the connection between the host 2002 and the UE 2006.
  • the connection 2060 and wireless connection 2070, over which the OTT connection 2050 may be provided, have been drawn abstractly to illustrate the communication between the host 2002 and the UE 2006 via the network node 2004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 2002 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 2006.
  • the user data is associated with a UE 2006 that shares data with the host 2002 without explicit human interaction.
  • the host 2002 initiates a transmission carrying the user data towards the UE 2006.
  • the host 2002 may initiate the transmission responsive to a request transmitted by the UE 2006.
  • the request may be caused by human interaction with the UE 2006 or by operation of the client application executing on the UE 2006.
  • the transmission may pass via the network node 2004, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the network node 2004 transmits to the UE 2006 the user data that was carried in the transmission that the host 2002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 2006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2006 associated with the host application executed by the host 2002.
  • the UE 2006 executes a client application which provides user data to the host 2002.
  • the user data may be provided in reaction or response to the data received from the host 2002.
  • the UE 2006 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 2006.
  • the UE 2006 initiates, in step 2018, transmission of the user data towards the host 2002 via the network node 2004.
  • the network node 2004 receives user data from the UE 2006 and initiates transmission of the received user data towards the host 2002.
  • the host 2002 receives the user data carried in the transmission initiated by the UE 2006.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 2006 using the OTT connection 2050, in which the wireless connection 2070 forms the last segment. More precisely, the teachings of these embodiments may improve UL subband transmission in a SBFD symbol.
  • factory status information may be collected and analyzed by the host 2002.
  • the host 2002 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 2002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 2002 may store surveillance video uploaded by a UE.
  • the host 2002 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 2002 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.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 2002 and/or UE 2006.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2050 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 2050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2004. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 2002.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2050 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computational
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • references in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” and so forth, 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 affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • Coupled is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, co-operate or interact with each other.
  • Connected is used to indicate the establishment of wireless or wireline communication between two or more elements that are coupled with each other.
  • a “set,” as used herein can refer to any whole number of items including one item.
  • An electronic device stores and transmits (internally and/or with other electronic devices over a network) code (which is composed of software instructions and which is sometimes referred to as a computer program code or a computer program) and/or data using machine-readable media (also called computer-readable media), such as machine-readable storage media (e.g., magnetic disks, optical disks, solid state drives, read only memory (ROM), flash memory devices, phase change memory) and machine- readable transmission media (also called a carrier) (e.g., electrical, optical, radio, acoustical, or other form of propagated signals - such as carrier waves, infrared signals).
  • machine-readable media also called computer-readable media
  • machine-readable storage media e.g., magnetic disks, optical disks, solid state drives, read only memory (ROM), flash memory devices, phase change memory
  • machine-readable transmission media also called a carrier
  • carrier e.g., electrical, optical, radio, acoustical, or other form of propagated signals - such as
  • an electronic device e.g., a computer
  • includes hardware and software such as a set of one or more processors (e.g., of which a processor is a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), other electronic circuitry, or a combination of one or more of the preceding) coupled to one or more machine-readable storage media to store code for execution on the set of processors and/or to store data.
  • processors e.g., of which a processor is a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), other electronic circuitry, or a combination of one or more of the preceding
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • an electronic device may include non-volatile memory containing the code since the non-volatile memory can persist code/data even when the electronic device is turned off (when
  • Typical electronic devices also include a set of one or more physical network interface(s) (NI(s)) to establish network connections (to transmit and/or receive code and/or data using propagating signals) with other electronic devices.
  • NI(s) physical network interface(s)
  • the set of physical NIs may perform any formatting, coding, or translating to allow the electronic device to send and receive data whether over a wired and/or a wireless connection.
  • a physical NI may comprise radio circuitry capable of (1) receiving data from other electronic devices over a wireless connection and/or (2) sending data out to other devices through a wireless connection.
  • This radio circuitry may include transmitter(s), receiver(s), and/or transceiver(s) suitable for radio frequency communication.
  • the radio circuitry may convert digital data into a radio signal having the proper parameters (e.g., frequency, timing, channel, bandwidth, and so forth).
  • the radio signal may then be transmitted through antennas to the appropriate recipient(s).
  • the set of physical NI(s) may comprise network interface controller(s) (NICs), also known as a network interface card, network adapter, or local area network (LAN) adapter.
  • NICs network interface controller
  • the NIC(s) may facilitate in connecting the electronic device to other electronic devices allowing them to communicate with wire through plugging in a cable to a physical port connected to an NIC.
  • One or more parts of an embodiment may be implemented using different combinations of software, firmware, and/or hardware.
  • module may refer to a circuit for performing the function specified.
  • the function specified may be performed by a circuit in combination with software such as by software executed by a general -purpose processor.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • the term unit may have conventional meaning in the field of electronics, electrical devices, and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • a method performed by a user equipment for uplink transmission in Subband Full Duplex (SBFD) slots comprising: receiving a first indication to monitor for a downlink (DL) transmission in a symbol; receiving a second indication to prioritize transmission of an uplink (UL) signal/channel over monitoring for the DL transmission in the symbol; and performing uplink transmission based on the first and/or second indication.
  • SBFD Subband Full Duplex
  • PRACH Physical Random Access Channel
  • PUCCH Physical Uplink Control Channel
  • a first prioritization is a default prioritization
  • a second prioritization is applied for an indicated duration of time before reverting to the default prioritization, where the indicated duration of time is included in the second indication.
  • a method performed by a base station for uplink transmission in Subband Full Duplex (SBFD) slots comprising: transmitting to a user equipment (UE) a first indication to monitor for a downlink (DL) transmission in a symbol; transmitting to the UE a second indication to prioritize transmission of an uplink (UL) signal/channel over monitoring for the DL transmission in the symbol to the UE; and monitoring uplink transmission from the UE that is based on the first and/or second indication.
  • SBFD Subband Full Duplex
  • PRACH Physical Random Access Channel
  • PUCCH Physical Uplink Control Channel
  • a first prioritization is a default prioritization
  • a second prioritization is applied for an indicated duration of time before reverting to the default prioritization, where the indicated duration of time is included in the second indication.
  • a user equipment for uplink transmission in Subband Full Duplex (SBFD) slots 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 processing circuitry.
  • SBFD Subband Full Duplex
  • a network node for uplink transmission in Subband Full Duplex (SBFD) slots 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 processing circuitry.
  • SBFD Subband Full Duplex
  • a user equipment (UE) for uplink transmission in Subband Full Duplex (SBFD) slots 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.
  • SBFD Subband Full Duplex
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • UE user equipment
  • a communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • the communication system of the previous embodiment further comprising: the network node; and/or the UE.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • UE user equipment
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host.
  • OTT over-the-top
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • UE user equipment
  • the method of the previous embodiment further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • OTT over-the-top
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • UE user equipment
  • the method of the previous embodiment further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de l'invention comprennent des procédés, un appareil, un support de stockage et un programme informatique pour une transmission en liaison montante dans des créneaux en duplex intégral de sous-bande (SBFD) avec des ressources de surveillance de liaison descendante. Dans un mode de réalisation, un procédé est mis en œuvre par un équipement utilisateur (UE) pour une transmission de liaison montante dans des créneaux de duplex intégral de sous-bande (SBFD), le procédé consistant à : recevoir une première indication pour surveiller une transmission de liaison descendante (DL) dans un symbole; recevoir une seconde indication pour prioriser la transmission d'un signal/canal de liaison montante (UL) sur la surveillance de la transmission DL dans le symbole; et effectuer une transmission de liaison montante sur la base d'une ou de plusieurs de la première indication et de la seconde indication.
PCT/IB2024/054901 2023-05-22 2024-05-20 Transmissions en liaison montante dans des créneaux en duplex intégral de sous-bande (sbfd) avec des ressources de surveillance de liaison descendante Pending WO2024241201A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363468260P 2023-05-22 2023-05-22
US63/468,260 2023-05-22

Publications (1)

Publication Number Publication Date
WO2024241201A1 true WO2024241201A1 (fr) 2024-11-28

Family

ID=91193531

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2024/054901 Pending WO2024241201A1 (fr) 2023-05-22 2024-05-20 Transmissions en liaison montante dans des créneaux en duplex intégral de sous-bande (sbfd) avec des ressources de surveillance de liaison descendante

Country Status (1)

Country Link
WO (1) WO2024241201A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025235070A1 (fr) * 2024-05-07 2025-11-13 Qualcomm Incorporated Techniques de résolution de collisions dans le domaine temporel en duplex intégral (sbfd) de sous-bande

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
INTERDIGITAL ET AL: "On subband non-overlapping full duplex operations", vol. RAN WG1, no. Incheon, Korea; 20230522 - 20230526, 14 May 2023 (2023-05-14), XP052376310, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_113/Docs/R1-2304789.zip R1-2304789 On subband non-overlapping full duplex operations_Final.docx> [retrieved on 20230514] *
MARTIN BEALE ET AL: "Considerations on Subband Full Duplex TDD operations", vol. 3GPP RAN 1, no. Incheon, KR; 20230522 - 20230526, 15 May 2023 (2023-05-15), XP052310482, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_113/Docs/R1-2305036.zip R1-2305036 - Rel-18 Duplex Evo - 9.3.2 SBFD v02.docx> [retrieved on 20230515] *
WEI ZENG ET AL: "Views on subband non-overlapping full duplex", vol. 3GPP RAN 1, no. Incheon, KR; 20230522 - 20230526, 15 May 2023 (2023-05-15), XP052310683, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_113/Docs/R1-2305241.zip R1-2305241 Views on subband non-overlapping full duplex.docx> [retrieved on 20230515] *
XIANGHUI HAN ET AL: "Discussion of subband non-overlapping full duplex", vol. 3GPP RAN 1, no. Incheon, KR; 20230522 - 20230526, 15 May 2023 (2023-05-15), XP052310055, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_113/Docs/R1-2304596.zip R1-2304596 Discussion of subband non-overlapping full duplex.docx> [retrieved on 20230515] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025235070A1 (fr) * 2024-05-07 2025-11-13 Qualcomm Incorporated Techniques de résolution de collisions dans le domaine temporel en duplex intégral (sbfd) de sous-bande

Similar Documents

Publication Publication Date Title
US20250254018A1 (en) Carrier configuration and scheduling for sub-band full duplex systems
EP4515793A1 (fr) Indication de format de créneau dynamique
US20240430979A1 (en) Multiple drx configurations with traffic flow information
US20250193889A1 (en) Method for implicit association between multi-trp pusch transmission and unified tci states
WO2024241201A1 (fr) Transmissions en liaison montante dans des créneaux en duplex intégral de sous-bande (sbfd) avec des ressources de surveillance de liaison descendante
US20250192966A1 (en) CSI-RS TRANSMISSION AND RECEPTION WITH UNIFIED TCI STATES FOR MULTIPLE TRPs
EP4490871A1 (fr) États de tci unifiés pour pdsch à multiples trp
US20240372678A1 (en) Physical downlink control channel monitoring for enhanced cross carrier scheduling
US20250392422A1 (en) Modification of periodic multi-slot allocations
US20240244624A1 (en) Devices and Methods for Semi-Static Pattern Configuration for PUCCH Carrier Switching
US20250141638A1 (en) Pucch carrier-switching for semi-statically configured periodic pucch
WO2025177179A1 (fr) Configuration de ressource de domaine temporel sbfd
WO2025178549A1 (fr) Transmission à multiples créneaux en fonctionnement sbfd
WO2024172747A1 (fr) Signalisation d&#39;occasions de transmission d&#39;autorisation configurées inutilisées
EP4666780A1 (fr) Signalisation d&#39;occasions de transmission d&#39;autorisation configurées inutilisées
WO2024172741A1 (fr) Procédures de couche physique pour indiquer des occasions de transmission de canal pusch d&#39;autorisation configurées inutilisées
EP4666779A1 (fr) Procédures de couche physique pour indiquer des occasions de transmission de canal pusch d&#39;autorisation configurées inutilisées
WO2024096807A1 (fr) Pdsch pour équipement utilisateur à capacité réduite
WO2025010020A1 (fr) Sélection de mode duplex d&#39;ue pour économie d&#39;énergie
WO2024141989A1 (fr) Amplification de puissance adaptative pour signal de référence de sondage
WO2024033821A1 (fr) Transmission à créneaux multiples avec une attribution préconfigurée
EP4635121A1 (fr) Amélioration de pt-rs pour plusieurs ports dmrs
WO2025027480A1 (fr) Rétroaction par ue de différences de fréquence de liaison descendante entre des trp
WO2024003382A1 (fr) Modification d&#39;attributions périodiques à intervalles multiples
WO2025186598A1 (fr) Planification à puissance de liaison montante limitée

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24727844

Country of ref document: EP

Kind code of ref document: A1