Enhanced resource determination of signals and channels based on semi-static and dynamic dual configurations for wireless communications

Abstract

The present disclosure describes systems, methods, and devices for configuring uplink and downlink transmissions in a full-duplex system. A next-generation Node B (gNB) device configures uplink and downlink frequency resources within a serving cell or bandwidth portion for different symbols; provides a frequency resource configuration indicating the uplink and downlink frequency resources to a user equipment (UE); provides a signal configuration or downlink control information (DCI) to the UE that schedules signal transmissions; and may identify uplink transmissions from the UE based on the signal configuration and the frequency resource configuration, or provide downlink transmissions to the UE based on the signal configuration and the frequency resource configuration.

Description

[Technical Field]

[0001] [Cross-reference to related patent applications] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 485,501, filed February 16, 2023, the disclosure of which is incorporated herein by reference as if fully set forth.

[0002] The present disclosure relates generally to systems and methods for wireless communications, and more particularly to wireless communication resource determination for signals and channels based on semi-static and dynamic duplex configurations. [Background technology]

[0003] Wireless devices are becoming more prevalent and are increasingly using wireless channels. The 3rd Generation Partnership Program (3GPP®) is developing one or more standards for wireless communications. [Brief explanation of the drawings]

[0004] [Figure 1] FIG. 1 is a network diagram illustrating an exemplary network environment in accordance with one or more exemplary embodiments of the present disclosure.

[0005] [Figure 2] 1 illustrates an exemplary sub-band full duplex (SBFD) based resource allocation in a serving cell, in accordance with one or more exemplary embodiments of the present disclosure.

[0006] [Figure 3A] 1 illustrates an example frequency resource determination for a Physical Uplink Shared Control Channel (PUSCH) transmission with rate matching, in accordance with one or more example embodiments of the present disclosure.

[0007] [Figure 3B] 1 illustrates an example frequency resource determination for PUSCH transmission, in accordance with one or more example embodiments of the present disclosure.

[0008] [Figure 4] 1 illustrates an example frequency resource determination for PUSCH transmission, in accordance with one or more example embodiments of the present disclosure.

[0009] [Figure 5] 1 illustrates an example frequency resource determination for PUSCH transmission, in accordance with one or more example embodiments of the present disclosure.

[0010] [Figure 6] 1 illustrates example PUSCH repetitions within semi-statically configured SBFD symbols that are dynamically switched to downlink symbols, in accordance with one or more example embodiments of the present disclosure.

[0011] [Figure 7] 1 illustrates example PUSCH repetitions within semi-statically configured SBFD symbols that are dynamically switched to uplink symbols, in accordance with one or more example embodiments of the present disclosure.

[0012] [Figure 8] 1 illustrates a flow diagram of an example process for SBFD-based resource allocation in a serving cell, in accordance with one or more example embodiments of the present disclosure.

[0013] [Figure 9] 1 illustrates a network in accordance with one or more exemplary embodiments of the present disclosure.

[0014] [Figure 10] 1 illustrates a schematic diagram of a wireless network in accordance with one or more exemplary embodiments of the present disclosure.

[0015] [Figure 11] FIG. 1 is a block diagram illustrating components in accordance with one or more exemplary embodiments of the present disclosure.

[0016] [Figure 12] 1 illustrates a network in accordance with one or more exemplary embodiments of the present disclosure.

[0017] [Figure 13] FIG. 1 illustrates a simplified block diagram of artificial (AI)-assisted communication between a user equipment and a radio access network, in accordance with one or more exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0018] The following description and drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithmic, and other changes. Portions and features of some embodiments may be included in, or substituted for, portions and features of other embodiments. Embodiments set forth in the claims include all available equivalents of those claims.

[0019] Wireless devices may operate as defined by technical standards. For cellular telecommunications, the Third Generation Partnership Program (3GPP) defines communication technologies, including time division duplexing (TDD). In TDD communication, time domain resources are divided between downlink and uplink symbols. The limited duration allocation for the uplink in TDD may result in reduced coverage and increased latency for a given target data rate. To improve the performance of the uplink (UL) in TDD, simultaneous transmission / reception of the downlink and uplink, respectively, also referred to as "full duplex communication," may be considered. In this regard, the case of non-overlapping subband full duplex (SBFD) in gNBs is expected to be further studied in 3GPP.

[0020] For SBFD, some bandwidth of a carrier bandwidth or bandwidth portion (BWP) may be allocated as UL and some bandwidth may be allocated as DL within the same symbol. However, the UL and DL resources are non-overlapping in the frequency domain. In this mode of operation, in a given symbol, the gNB can simultaneously transmit DL signals and receive UL signals, but the UE can only transmit or receive at a time.

[0021] For a UE that is not aware of SBFD support in the gNB, the UE may identify only DL or UL resources within a symbol. For a UE that can be provided with information about SBFD operation in the gNB, the UE may identify both DL and UL resources within a symbol. The DL and UL resources within a symbol may be determined semi-statically or dynamically. The UE may determine the resources of a DL / UL signal / channel based on the resource allocation of that signal / channel, taking into account the DL and UL resources within the SBFD or non-SBFD symbol.

[0022] This disclosure provides details on determining DL and UL resources for DL / UL signals / channels according to semi-static or dynamic DL and UL resources within SBFD or non-SBFD symbols. As a result, the enhanced techniques herein may enable flexible resource configuration and efficient operation in full-duplex communication systems.

[0023] For a serving cell with SBFD operation, only some symbols (e.g., denoted as DL / UL / flexible symbols) may be used to map either DL or UL physical channels or signals, while some other symbols (denoted as symbols with potential SBFD operation) may be used to map both DL and UL physical channels or signals within the same symbol. Thus, for a given PRB within a symbol with potential SBFD operation, resources may be identified as DL, UL, or guard bands. In one example, frequency resources within a symbol may be divided into DL / UL / guard resources within different non-overlapping subbands. A "subband" corresponds to a set of physical resources within a carrier that are contiguous in frequency, e.g., the number of contiguous physical resource blocks (PRBs) on a common resource block (CRB) grid. The DL, UL, or guard bands may be explicitly or implicitly configured. In one example, the DL and UL subbands are explicitly configured, and the guard band is derived from the PRBs between the DL and UL subbands. In another example, the UL subbands and guard bands are explicitly configured, and the DL subbands are derived from the remaining PRBs.

[0024] For semi-static and dynamic subband information, the subband configuration, including time (symbols and / or slots with DL) and frequency (PRB) information for DL, UL, or guard bands, can be provided to the UE via semi-static or dynamic signaling. In one option, the subband configuration is provided semi-statically by RRC signaling. In another option, the subband configuration is provided dynamically by DCI. For example, both time and frequency information for DL, UL, or guard bands are provided by RRC signaling, and thus the SBFD and non-SBFD symbols and frequency locations of DL, UL, or guard bands within an SBFD symbol are determined semi-statically. In addition, time information can be provided by DCI, enabling dynamic switching between legacy DL / UL / flexible symbols (non-SBFD symbols) and SBFD symbols. Legacy DL / UL / flexible symbols mean that only one direction is allowed within the symbol as in legacy TDD systems. Note that if a symbol is determined as a legacy DL / UL / flexible symbol (non-SBFD symbol), any semi-statically configured DL, UL, or guard band is considered invalid. DL, UL, or guard band is considered valid only if the symbol is determined as an SBFD symbol based on dynamic indication.

[0025] In one embodiment of the present invention, in the case of dynamic subband configuration, the DCI format may be one of the existing non-fallback scheduling DCI formats used for DL ​​assignment or UL grant. In one option, a new bit field may be added in the DL assignment or UL grant DCI to indicate the switch between SBFD symbols and non-SBFD symbols. The presence of the new bit field may be predefined and associated with the configuration of SBFD-based operation, or may be configured by RRC signaling.

[0026] In one example, the new bit field may include one bit indicating whether the symbol type (SBFD or non-SBFD symbol) is the same as the semi-static configuration. The new bit field may be added only to the DL allocation, or added in both the DL allocation and the UL grant. The symbol type may be determined according to at least one of the following mechanisms: If the bit field indicates that the symbol type is the same as the semi-static configuration, the symbol type is determined by the semi-static configuration. If the bit field indicates that the symbol type is different from the semi-static configuration, and if the symbol type according to the semi-static configuration is a legacy DL or UL symbol, the symbol is switched to an SBFD symbol. If the bit field indicates that the symbol type is different from the semi-static configuration, and if the symbol type according to the semi-static configuration is a legacy flexible symbol, the symbol is switched to an SBFD symbol. If the bit field indicates that the symbol type is different from the semi-static configuration, and if the symbol type according to the semi-static configuration is an SBFD symbol, the symbol is switched to a non-SBFD symbol. If the DCI is a DL allocation, the symbol is switched to a legacy DL symbol. If the DCI is a UL grant, the symbol is switched to a legacy UL symbol.

[0027] In another example, the new bit field may include one or more bits indicating a symbol type (SBFD or non-SBFD symbol). The symbol type may be an SBFD symbol or a non-SBFD symbol. A non-SBFD symbol may be indicated as one of a legacy DL symbol, a legacy UL symbol, or a legacy flexible symbol. For example, the new bit field includes one bit indicating an SBFD symbol or a legacy DL symbol. In another example, the new bit field includes two bits indicating one of an SBFD symbol, a legacy DL symbol, or a legacy UL symbol.

[0028] The new bit field may be applied to all symbols in a slot containing a PDSCH / PUSCH scheduled by a DL assignment / UL grant (respectively). For example, if a DL assignment schedules a PDSCH in slot n, and the bit field indicates the symbol type as a legacy DL symbol, then all symbols in slot n are assumed to be legacy DL symbols. Alternatively, the new bit field may be applied to PDSCH / PUSCH symbols scheduled by a DL assignment / UL grant. For example, if a DL assignment schedules a PDSCH in symbols 2 to 10 in slot n, and the bit field indicates the symbol type as a legacy DL symbol, then all symbols of the PDSCH (symbols 2 to 10) are assumed to be legacy DL symbols.

[0029] If the UL grant or DL ​​allocation schedules multiple PUSCH / PDSCH transmission opportunities, e.g., PDSCH / PUSCH with repetition, multi-PUSCH / PDSCH scheduling, transport block over multiple slots (TBoMS), the new bit field may apply to a specific transmission / reception opportunity. The specific transmission / reception opportunity may be the first transmission / reception opportunity, or all transmission / reception opportunities, or all transmission / reception opportunities within a semi-statically configured SBFD symbol, or all transmission / reception opportunities within a semi-statically configured non-SBFD symbol. Alternatively, if the UL grant or DL ​​allocation schedules multiple PUSCH / PDSCH transmission opportunities, the new bit field is reserved or not indicated in the DCI.

[0030] If an UL grant or DL ​​allocation schedules multiple PUSCH / PDSCH transmission opportunities, the new bit field consists of a bitmap-based indication for each transmission / reception opportunity or each group of transmission / reception opportunities, where a group of transmission / reception opportunities may consist of one or more transmission / reception opportunities, and the size of the group may be configured by RRC signaling or determined according to the total number of transmission / reception opportunities.

[0031] In another option, the legacy frequency domain resource allocation (FDRA) bit field in the DL assignment or UL grant DCI may implicitly indicate a switch between SBFD and non-SBFD symbols. In one example, if the DL assignment schedules a PDSCH in a semi-statically configured SBFD symbol and the FDRA indicates all PRBs in the semi-statically configured UL subband, it implicitly indicates a symbol switched to a legacy DL symbol. In another example, if the DL assignment schedules a PDSCH in a semi-statically configured SBFD symbol and the FDRA indicates at least one RBG completely outside the semi-statically configured DL subband, it implicitly indicates a symbol switched to a legacy DL symbol. The UE receives the PDSCH on the indicated RBG. Similarly, if the DL allocation schedules a PDSCH in a semi-statically configured non-SBFD symbol and the FDRA indicates at least one RBG completely outside the semi-statically configured DL subbands, it implicitly indicates that the symbol is still a non-SBFD symbol, e.g., a legacy DL symbol or a flexible symbol. In another example, if the DL allocation schedules a PDSCH and the FDRA is for resource allocation type 1 that indicates at least one RB outside the semi-statically configured DL subbands, it implicitly indicates the symbol as a non-SBFD symbol. A similar mechanism can be applied for implicit indication via the UL grant.

[0032] In the case of dynamic subband configuration, the DCI may be a group-common DCI, such as slot format information (SFI) or a new group-common DCI, which indicates the symbol type, or whether the symbol type (SBFD) or non-SBFD symbols is the same as in the semi-static configuration.

[0033] In the case of dynamic subband configuration, in one option, the UE does not expect to receive dynamic subband information that leads to different symbol types (SBFD) or non-SBFD symbols of the DL / UL signal / channel.

[0034] The DL / UL signal / channel may be at least one of PDSCH / PDCCH / PUSCH / PUCCH / DL-PRS / PT-RS / CSI-RS / SRS / SSB / PRACH.

[0035] In another option, the UE may not expect to receive dynamic subband information that leads to different symbol types (SBFD or non-SBFD symbols) for the DL / UL signals / channels scheduled by the DL assignment / UL grant. In another option, the UE does not expect to receive dynamic subband information that leads to different symbol types (SBFD or non-SBFD symbols) for the DL / UL signals / channels scheduled by the DL assignment / UL grant, and the DL / UL signals / channels have a single reception / transmission opportunity, i.e., the DL / UL signals / channels are not configured with repetitive or multi-PDSCH / PUSCH scheduling or TBoMS.

[0036] For dynamic subband indication, in one option, the UE may not expect to receive dynamic subband information for any symbol of a DL / UL signal / channel that is dynamically scheduled or configured by higher layers over multiple reception / transmission opportunities. In another option, the UE may not expect to receive dynamic subband information for any symbol of a DL / UL signal / channel that is scheduled by a DL assignment / UL grant over multiple reception / transmission opportunities. In another option, the UE may not expect to receive dynamic subband information that leads to different frequency domain resources for different reception / transmission opportunities of a DL / UL signal / channel. In another option, the UE may not expect to receive dynamic subband information that leads to different frequency domain resources for different reception / transmission opportunities of a DL / UL signal / channel that is scheduled by a DL assignment / UL grant.

[0037] Note that in some cases, dynamic subband information may be equivalent to an indication of parameters associated with SBFD or non-SBFD symbols. For example, for PDSCH, the gNB may configure two sets of parameters. The set of parameters may include one or more of frequency domain resources, spatial domain resources (e.g., TCI or SRI), and power domain resources (e.g., transmit power, open / closed loop power control, high power radio between SSB and DMRS). The gNB may dynamically indicate which set of parameters is used.

[0038] For DL / UL subband-based frequency domain resource determination, in legacy TDD or FDD systems, the frequency domain resources of a signal / channel are typically provided with respect to the BWP, or with respect to the carrier, or with respect to CORESET0, or with respect to CRB#0 or reference point A. For example, for PDSCH / PUSCH resource allocation type 0, the RBGs shall be indexed in increasing frequency order, starting at the lowest frequency of the BWP. For PDSCH / PUSCH resource allocation type 1, the PRBs shall be indexed in increasing frequency order, starting at the lowest frequency of the BWP.

[0039] In an SBFD system, in one option (Option 1), frequency domain resources of signals / channels may be determined in the same manner as in legacy TDD / FDD systems, for example, based on the BWP, in both SBFD and non-SBFD symbols. In an SBFD system, in another option (Option 2), frequency domain resources of signals / channels may be determined based on the BWP in non-SBFD symbols and based on DL / UL subbands in SBFD symbols. For example, for Option 2, if PRB#n is indicated as the starting PRB in the FDRA and the symbol is a legacy UL symbol, the starting PRB of the PUSCH is PRB#n in the active UL BWP, where the first PRB is the starting PRB of the active UL BWP. If the symbol is an SBFD symbol, the starting PRB of the PUSCH is PRB#(n mod(N UL_sub-band)+Nstart_UL_sub-band) in the active UL BWP, where Nstart_UL_sub-band is the starting PRB of the UL subband relative to the active UL BWP and N UL_sub-band is the number of PRBs in the UL subband. If frequency hopping is configured, the starting PRB of the second hop of the PUSCH is PRB#(n+Nhop) mod(N UL_sub-band)+Nstart_UL_sub-band), where Nhop is the frequency offset in RBs between these two frequency hops. For option 2, in one example, the UE does not expect that the frequency domain resources of DL signals / channels determined relative to the DL subband in the SBFD symbol are unconstrained within the DL subband. The UE does not expect that the frequency domain resources of UL signals / channels determined relative to the UL subband in the SBFD symbol are unconstrained within the UL subband. In one example, the UE does not expect that the frequency domain resources of the UL signal / channel determined with respect to the UL subband within the SBFD symbol will result in non-contiguous frequency resources, e.g., the PUSCH will be split between the upper and lower UL subbands.In another example, the UE may expect that the frequency domain resources of the UL signal / channel determined with reference to the UL subbands within the SBFD symbol will lead to non-contiguous frequency resources, and the UE will cancel the UL transmission in this case.

[0040] Additionally, for both options, rate matching / puncturing / postponement / dropping by DL / UL subbands within the SBFD symbol may be applied to avoid DL signal / channel reception overlap with UL subbands and / or guard bands or UL signal / channel transmission overlap with DL subbands and / or guard bands.

[0041] In one example, for slot n, the gNB configures RB#1 to RB#60 as the first DL subband, RB#65 to RB#160 as the UL subband, and RB#165 to RB#210 as the second DL subband (SBFD symbols), and the gNB configures slot n+1 as a legacy UL slot (non-SBFD symbols). The gNB configures RB#1 to RB#210 as the UE's DL / UL BWP. The gNB schedules a first PUSCH within RB#50 to RB#89 in slot n and a second PUSCH within RB#50 to RB#89 in slot n+1. For option 1, RB#50 to RB#89 are referenced to the UL BWP for both slot n and slot n+1. In slot n, since rate matching may be performed around the DL subband and guard band, the first PUSCH is actually transmitted in RB #65 to RB #89, which is limited within the UL subband. In slot n+1, the second PUSCH is actually transmitted in RB #50 to RB #89. In FIG. 3, based on option 2, for slot n, since RB #50 to RB #89 refer to the UL subband, the first PUSCH is actually transmitted in RB #114 to RB #153, ​​which are referenced to the UL BWP. In slot n+1, the second PUSCH is actually transmitted in RB #50 to RB #89, which are referenced to the UL BWP. For both of the above options, time and frequency information of the DL, UL subband, and guard band may be obtained from semi-static signaling and / or dynamic signaling.

[0042] For determining resource for a signal / channel based on semi-static subband information, to determine reception / transmission of a signal / channel, the UE can determine resource for the signal / channel based on semi-static subband information in a first stage, and the UE can determine whether to receive / transmit the signal / channel based on dynamic subband information in a second stage.

[0043] In the first stage, the determination of the signal / channel resources includes at least one of the following aspects: Whether the time domain resources of the signals / channels within the set of symbols collide with the symbol types based on semi-static subband information.

[0044] When a DL / UL signal / channel is within a legacy UL / DL symbol (non-SBFD symbol) based on semi-static subband information, a collision between the time domain resource of the DL / UL signal / channel and the symbol type based on the semi-static subband information is identified.

[0045] If a collision is identified by the UE, the signal / channel is dropped / deferred regardless of the dynamic subband information.

[0046] For example, for a CG PUSCH in a set of legacy DL symbols based on semi-static subband information, the UE drops the CG PUSCH even if the dynamic subband information switches the set of symbols to SBFD symbols. The UE determines the frequency domain resources of the signals / channels in the symbol set based on the semi-static subband information. For example, for a PUSCH in a semi-statically configured SBFD symbol, the frequency resources are determined based on the UL subband information and on the UL BWP. If the PUSCH is in a semi-statically configured legacy UL symbol, the frequency resources are determined based on the semi-static subband information and on the UL BWP.

[0047] Since the frequency domain resources are determined based on semi-static subband information, false detection of the dynamic indication does not cause misalignment between the gNB and the UE regarding the frequency domain resources.

[0048] In one option, the UE does not expect a UL signal / channel to be scheduled by a UL grant in a way that collides with a legacy DL symbol provided by dynamic indication. The UE does not expect a DL signal / channel to be scheduled by a DL assignment in a way that collides with a legacy UL symbol provided by dynamic indication.

[0049] In one option, the UE does not expect a UL signal / channel to be scheduled in a single transmission opportunity by a UL grant such that it collides with a legacy DL symbol provided by dynamic indication. The UE does not expect a DL signal / channel to be scheduled in a single transmission opportunity by a DL assignment such that it collides with a legacy UL symbol provided by dynamic indication.

[0050] In one option, if the DL signal / channel is dynamically scheduled by the gNB, the UE does not expect the frequency domain resources of the DL signal / channel to collide with the valid UL subbands and guard bands provided by the dynamic indication. If the UL signal / channel is dynamically scheduled by the gNB, the UE does not expect the frequency domain resources of the UL signal / channel to collide with the valid DL subbands and guard bands provided by the dynamic indication.

[0051] In one option, when a DL signal / channel is dynamically scheduled by the gNB and the DL signal / channel has a single transmission opportunity, the UE does not expect the frequency domain resources of the DL signal / channel to collide with the valid UL sub-bands and guard bands provided by the dynamic indication. When a UL signal / channel is dynamically scheduled by the gNB and the UL signal / channel has a single transmission opportunity, the UE does not expect the frequency domain resources of the UL signal / channel to collide with the valid DL sub-bands and guard bands provided by the dynamic indication.

[0052] In one option, if the DL / UL signals / channels are higher layer configured signals / channels, the UE may expect the UL signals / channels to collide with legacy DL symbols provided by dynamic indication, or the DL signals / channels to collide with legacy UL symbols provided by dynamic indication.

[0053] In one option, if the DL / UL signal / channel is a higher layer configured signal / channel, the UE may expect that the frequency domain resources of the DL signal / channel will collide with the valid UL subbands and guard bands provided by the dynamic indication, or that the UL signal / channel will collide with the valid DL subbands and guard bands provided by the dynamic indication.

[0054] In the second stage, if the UE identifies a collision between the legacy DL / UL symbols provided by the dynamic subband information and the UL / DL signal / channel determined in the first stage based on the semi-static subband information, the UE drops the signal / channel.

[0055] In the second stage, if the UE identifies a collision between the valid subbands or guard bands provided by the dynamic subband information and the frequency domain resources of the signal / channel determined based on the semi-static subband information in the first stage, the UE drops the signal / channel.

[0056] In one example of PDSCH resource determination, PDSCH frequency resources are determined based on Option 1 (Option 1 in DL / UL subband section-based frequency domain resource determination). The gNB schedules a first PDSCH within RB#1 to RB#80 in slot n and a second PDSCH within RB#1 to RB#80 in slot n+1. In slot n, all symbols within slot n are SBFD symbols based on the semi-static subband configuration. The first PDSCH is rate-matched to the guard band and the vicinity of the UL subband so that the first PDSCH is within RB#1 to RB#60. In slot n+1, all symbols within slot n are non-SBFD symbols based on the semi-static subband configuration. The second PDSCH is within RB#1 to RB#80. The dynamic subband configuration switches the symbols within slot n to legacy DL symbols. The UE still receives only the first PDSCH within RB#1 to RB#60. Then, even if the dynamic subband information DCI is misdetected by the UE, the gNB and the UE share the same understanding of PDSCH rate matching in slot n.

[0057] In another example of PDSCH frequency resource determination, the PDSCH frequency resource is determined based on the above Option 1 (Option 1 in DL / UL subband section-based frequency domain resource determination). The gNB schedules a first PDSCH in RB#1 to RB#80 in slot n and a second PDSCH in RB#1 to RB#80 in slot n+1. In slot n, all symbols in slot n are legacy DL symbols based on the semi-static subband configuration. The first PDSCH is in RB#1 to RB#80. The dynamic subband information switches the symbols in slot n to SBFD symbols. Because the first PDSCH overlaps with the UL subband and guard band, the UE drops the first PDSCH.

[0058] Regarding resource determination of a signal / channel based on subband information, to determine reception / transmission of a signal / channel, the UE can determine resource of the signal / channel based on dynamic subband information. The UE can determine whether the time domain resources of the signals / channels in the set of symbols conflict with the symbol type based on the dynamic subband information.

[0059] For example, for a CG PUSCH in a set of legacy DL symbols based on semi-static subband information, if the UE receives dynamic subband information that switches the set of symbols to SBFD symbols, the UE assumes that the CG PUSCH can be transmitted based on the SBFD symbols.

[0060] In another example, for a CG PUSCH in a set of SBFD symbols based on semi-static subband information, if the UE receives dynamic subband information that switches the set of symbols to legacy DL symbols, the UE will identify a collision and therefore cancel the CG PUSCH. The UE can determine frequency domain resources for signals / channels within the set of symbols based on the dynamic subband information. For example, for a PUSCH within a semi-statically configured SBFD symbol, if the UE receives dynamic subband information to switch the set of symbols to a legacy UL symbol, the frequency resources are determined based on the dynamic subband information and on the UL BWP. If the PUSCH is within a semi-statically configured legacy flexible symbol and the UE receives dynamic subband information to switch the set of symbols to a SBFD symbol, the frequency resources are determined based on the dynamic subband information and on the UL subband.

[0061] Since the frequency domain resources are determined based on the dynamic subband information, the frequency resources can be fully utilized.

[0062] For the above embodiments, different embodiments may be applied for different signals / channels.

[0063] In one option, for higher layer configured DL / UL signals / channels, the resources are determined based on dynamic subband information.

[0064] In one option, for a DL / UL signal / channel configured by a higher layer, in a symbol that can be dynamically switched by the dynamic subband information, the resource is determined based on the dynamic subband information if the UE receives DCI carrying the dynamic subband information, and if the UE receives DCI carrying the dynamic subband information for that symbol, the UE drops the DL / UL signal / channel.

[0065] In one option, if dynamic subband information is not provided by the DL assignment / UL grant, for DL / UL signals / channels with multiple reception / transmission opportunities scheduled by the DL assignment / UL grant, the resources are determined based on semi-static subband information. For example, the dynamic subband information may be provided in a DCI other than the DL assignment / UL grant.

[0066] In one option, if dynamic subband information is maintained by the DL assignment / UL grant, for DL / UL signals / channels with multiple reception / transmission opportunities scheduled by the DL assignment / UL grant, resources are determined based on the dynamic subband information.

[0067] In one option, if dynamic subband information is not provided by the DL assignment / UL grant that schedules the DL / UL signal / channel, for the scheduled DL / UL signal / channel, the frequency domain resources are determined based on semi-static subband information. For example, the dynamic subband information may be provided in a DCI other than the DL assignment / UL grant.

[0068] In one option, if dynamic subband information is provided by a DL assignment / UL grant that schedules a DL / UL signal / channel, for the scheduled DL / UL signal / channel, the frequency domain resources are determined based on the dynamic subband information.

[0069] In one option, if dynamic subband information is provided by a DL assignment / UL grant that schedules a DL / UL signal / channel, for a scheduled DL / UL signal / channel that has a single reception / transmission opportunity, the frequency domain resources are determined based on the dynamic subband information.

[0070] For frequency domain resource determination and available slot counting, for PUSCH transmission with repetition type A or with transport block over multiple slots (TBoMS), counting based on available slots may be supported based on the gNB configuration. A similar mechanism applies to physical uplink control channel (PUCCH) repetition and SRS transmission in unpaired spectrum or half-duplex (HD)-FDD. For example, a DCI-triggered aperiodic SRS resource set may be transmitted at the (t+1)th available slot count from the reference slot, where t is configured by higher layer signaling with or without DCI indication.

[0071] For counting available slots, a two-stage approach may be used, where in the first stage, the UE determines available slots for K repetitions based on DL / UL configuration as well as time-domain resource allocation and frequency-domain resources for PUSCH / PUCCH / SRS. In the second stage, the UE decides whether to drop PUSCH repetitions / PUCCH repetitions / SRS according to dynamic DL / UL information, but the PUSCH repetitions / PUCCH repetitions are still counted in K repetitions, and the SRS is still counted as being transmitted without further postponement.

[0072] The DL / UL configuration may be a semi-static DL / UL configuration including a semi-static configuration of subbands. In one option, in a first stage, if the PUSCH / PUCCH / SRS is within an SBFD symbol determined by the semi-static DL / UL configuration, the slot of the PUSCH / PUCCH / SRS is counted as an available slot; otherwise, the slot is not counted as an available slot. In a second stage, for an available slot determined in the first stage, if the UE determines that the frequency domain resource of the PUSCH / PUCCH / SRS collides with a valid DL subband and guard band provided by the dynamic subband information, or if the UE determines that the PUSCH / PUCCH / SRS collides with a legacy DL symbol (non-SBFD symbol) provided by the dynamic subband information, the UE cancels the PUSCH / PUCCH / SRS and does not postpone the canceled PUSCH / PUCCH / SRS transmission. In this option, it may be assumed that the gNB always ensures that the frequency resources for PUSCH / PUCCH / SRS derived based on the semi-static subband configuration are restricted within the UL subband, so the UE only needs to check the time domain resources in the first stage.

[0073] In one example of a PUSCH with two repetitions, slot n+1 consists of SBFD symbols based on a semi-static subband configuration, and the symbols are dynamically switched to DL symbols based on dynamic subband information. For PUSCH repetition #2 in slot n+1, the frequency resources of the PUSCH are determined based on the semi-static subband configuration and are limited within the UL subband. Therefore, slot n+1 is counted as an available slot in the first stage. The UE identifies the symbols in slot n+1 and switches to DL symbols based on the dynamic subband information. Therefore, the UE drops the PUSCH in slot n+1 in the second stage.

[0074] In another option, if the PUSCH / PUCCH / SRS is within an SBFD symbol determined by a semi-static DL / UL configuration and the frequency domain resource of the PUSCH / PUCCH / SRS is restricted within the UL subband, the slot of the PUSCH / PUCCH / SRS is counted as an available slot; otherwise, the slot is not counted as an available slot. In the first stage, the frequency domain resource of the PUSCH / PUCCH / SRS may be determined based on a semi-static subband configuration. In one example, based on Option 1 in the DL / UL subband section-based frequency domain resource determination, the frequency domain resource of the PUSCH is determined based on the BWP regardless of whether it is an SBFD symbol or a non-SBFD symbol. In the first stage, if the symbol is an SBFD symbol based on the semi-static subband configuration and all PRBs of the PUSCH are restricted within the UL subband, the slot is counted as an available slot. If at least one of the PRBs of the PUSCH is outside the UL subband, the slot is counted as an unavailable slot. If the symbol is a flexible symbol based on the semi-static subband configuration, the slot is counted as an available slot. In the second step, for the available slot determined in the first step, if the UE determines that the frequency domain resource of the PUSCH / PUCCH / SRS collides with the valid DL subbands and guard bands provided by the dynamic subband information, or if the UE determines that the PUSCH / PUCCH / SRS collides with the legacy DL symbol (non-SBFD symbol) provided by the dynamic subband information, the UE cancels the PUSCH / PUCCH / SRS.

[0075] In another example of a PUSCH with two repetitions, slot n+1 consists of a semi-static SBFD symbol based on a semi-static subband configuration, and the symbol is dynamically switched to a legacy UL symbol based on dynamic subband information. For PUSCH repetition #2 in slot n+1, the frequency resource of the PUSCH is determined based on the UL BWP. Because the PUSCH overlaps with the semi-static DL subband, PUSCH repetition #2 is postponed to the next slot n+2 along with the semi-static UL slot. Slot n+1 is not counted as an available slot in the first stage. In the second stage, the UE does not check slot n+1, but it is switched to a full UL slot.

[0076] For the above embodiment, if the dynamic subband information leads to the cancellation of an UL signal / channel, the gap between the DCI of the dynamic subband information and the UL signal / channel should provide sufficient time for the cancellation of the UL transmission. In one example, the gap between the last symbol of CORESET at which the UE detects the DCI format including the dynamic subband information and the first symbol from which the UL signal / channel can be canceled may be specified to be at least T_(proc,2), where T_(proc,2) is the PUSCH preparation time for the corresponding UE processing capability (e.g., 3GPP technical standard 38.214) assuming d_2,1=1, and μ corresponds to the smallest SCS configuration among the SCS configuration of the PDCCH that carries the DCI format and the SCS configurations of SRS, PUCCH, PUSCH, or μ_r, where μ_r corresponds to the SCS configuration of the PRACH if it is 15 kHz or greater; otherwise, μ_r=0.

[0077] For the above embodiment, when the frequency resources of the UL signal / channel are determined by dynamic subband information, the gap between the DCI of the dynamic subband information and the UL signal / channel should provide sufficient time for UL signal / channel transmission preparation. In one example, the gap between the last symbol of CORESET at which the UE detects the DCI format including the dynamic subband information and the first symbol from which the UL signal / channel may be transmitted may be specified to be at least T_(proc,2), where T_(proc,2) is the PUSCH preparation time for the corresponding UE processing capability (e.g., 3GPP technical standard 38.214) assuming d_2,1=1, and μ corresponds to the smallest SCS configuration among the SCS configuration of the PDCCH that carries the DCI format and the SCS configurations of SRS, PUCCH, PUSCH, or μ_r, where μ_r corresponds to the SCS configuration of the PRACH if μ_r is 15 kHz or greater; otherwise, μ_r=0. In another example, for UL signals / channels other than the PUSCH, a minimum preparation time different from that of the PUSCH preparation time may be defined.

[0078] When the frequency resource of the DL signal / channel is determined by the dynamic subband information, the gap between the DCI and the DL signal / channel of the dynamic subband information should provide sufficient time for DL ​​signal / channel reception preparation. In one example, the minimum reception preparation time may include the minimum time for PDCCH decoding and any Tx-Rx switching time (if applicable). Furthermore, such a minimum processing timeline for DL ​​signal / channel reception preparation may be defined for cases where legacy UL symbols may be switched to SBFD with DL reception.

[0079] In the case of resource determination for UCI multiplexing based on semi-static or dynamic subband configuration, for UCI multiplexing, in one option, the multiplexed PUCCH and PUSCH are based on semi-static subband information. After multiplexing, the availability of the resulting PUSCH or resulting PUCCH is checked based on dynamic subband information. If a collision occurs, for example, if the symbol of the resulting PUSCH in a semi-static SBFD symbol switches to a legacy DL symbol based on dynamic subband information, the resulting PUSCH is dropped. In another example, if the resulting PUSCH in a flexible symbol overlaps with a valid DL subband or guard band based on dynamic subband information, the resulting PUSCH is dropped.

[0080] In another option, the candidate PUSCHs for UCI multiplexing are determined based on dynamic subband information. For example, based on the dynamic subband information, if the PUSCH collides with a legacy DL symbol or overlaps with a valid DL subband or guard band, the PUSCH is excluded from the candidate PUSCHs for UCI multiplexing.

[0081] The above description is for purposes of illustration and is not intended to be limiting. Many other examples, configurations, processes, algorithms, etc. may exist, some of which are described in more detail below. Exemplary embodiments will now be described with reference to the accompanying drawings.

[0082] FIG. 1 is a network diagram illustrating an exemplary network environment 100 in accordance with one or more exemplary embodiments of the present disclosure.

[0083] The wireless network 100 may include one or more UEs 120 and one or more RANs 102 (e.g., gNBs), which may communicate according to 3GPP® communications standards. The UEs 120 may be mobile devices that are non-stationary (e.g., do not have a fixed location) or may be stationary devices.

[0084] In some embodiments, the UE 120 and the RAN 102 may include one or more computer systems similar to those in FIGS.

[0085] One or more exemplary UEs 120 and / or RAN 102 may be operable by one or more users 110. A UE may assume multiple distinct characteristics, each of which shapes its functionality. For example, a single addressable unit may simultaneously be a portable UE, a quality of service (QoS) UE, a subordinate UE, and a hidden UE. The UE 120 (e.g., 124, 126, or 128) and / or RAN 102 may include any suitable processor-driven device, including, but not limited to, a mobile device or a non-mobile, e.g., static, device. For example, the UE 120 may be a software-enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., a bracelet, a watch, eyeglasses, a ring, etc.), a desktop computer, a mobile computer, a laptop computer, an Ultrabook® computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an Internet of Things (IoT) device, a sensor device, a PDA® device, a handheld PDA® device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular telephone functionality with PDA® device functionality), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular phone, a PCS device, a PDA® device incorporating a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a "carry small live" device, aThe device may include a "Computing Device for Large Scale (CSLL)" (CDMA) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID), an "origami" device or computing device, a device supporting Dynamically Configurable Computing (DCC), a context-aware device, a video device, an audio device, an A / V device, a set-top box (STB), a Blu-ray Disc (BD) player, a BD recorder, a Digital Video Disc (DVD) player, a High Definition (HD) DVD player, a DVD recorder, an HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, or a music player. Other devices may also be included in this list, including smart devices such as lamps, environmental controls, automobile components, home components, appliances, etc.

[0086] As used herein, the term “Internet of Things (IoT) device” is used to refer to any object (e.g., appliance, sensor, etc.) that has an addressable interface (e.g., Internet Protocol (IP) address, Bluetooth® identifier (ID), Near Field Communication (NFC) ID, etc.) and can transmit information to one or more other devices via a wired or wireless connection. An IoT device may have a passive communication interface, such as a Quick Response (QR) code, a Radio Frequency Identifier (RFID) tag, or an NFC tag, or an active communication interface, such as a modem, transceiver, or transmitter-receiver. An IoT device may have a set of specific attributes (e.g., device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, cooling or heating capabilities, environmental monitoring or recording capabilities, light or sound emitting capabilities, etc.) that may be embedded in and / or controlled / monitored by a central processing unit (CPU), microprocessor, ASIC, etc., configured for connection to an IoT network, such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwave ovens, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, lighting fixtures, vacuum cleaners, sprinklers, power meters, gas meters, etc. IoT devices may also include mobile phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Thus, an IoT network may be composed of a combination of "traditional" internet-accessible devices (e.g., laptop or desktop computers, mobile phones, etc.) in addition to devices that typically do not have internet connectivity (e.g., dishwashers, etc.).

[0087] Any of the UEs 120 (e.g., UEs 124, 126, 128) and UEs 120 may be configured to communicate with each other wirelessly or wired via one or more communication networks 130 and / or 135. The UEs 120 may also communicate with each other peer-to-peer or directly, with or without the RAN 102. Any of the communication networks 130 and / or 135 may include any one or a combination of different types of suitable communication networks, such as, but not limited to, a broadcast network, a cable network, a public network (e.g., the Internet), a private network, a wireless network, a cellular network, or any other suitable private and / or public network. Furthermore, any of the communication networks 130 and / or 135 may have any suitable communication range associated therewith, including, for example, a cellular network. Additionally, either of communications networks 130 and / or 135 may include any type of medium over which network traffic can be carried, including, but not limited to, coaxial cable, twisted pair wire, optical fiber, hybrid fiber coaxial (HFC) medium, microwave terrestrial transceiver, radio frequency communications medium, white space communications medium, very high frequency communications medium, satellite communications medium, or any combination thereof.

[0088] Both the UE 120 (e.g., UEs 124, 126, 128) and the RAN 102 may include one or more communication antennas. The one or more communication antennas may be any suitable type of antenna compatible with the communication protocols used by the UE 120 (e.g., UEs 124, 126, and 128) and the RAN 102. Some non-limiting examples of suitable communication antennas include a cellular antenna, a 3GPP® standard family compliant antenna, a directional antenna, an omnidirectional antenna, a dipole antenna, a folded dipole antenna, a patch antenna, a multiple-input multiple-output (MIMO) antenna, an omnidirectional antenna, or a quasi-omnidirectional antenna, etc. The one or more communication antennas may be communicatively coupled to radio components for transmitting and / or receiving signals, such as communication signals, to and / or from the UE 120 and / or the RAN 102.

[0089] Both the UE 120 (e.g., UEs 124, 126, 128) and the RAN 102 may be configured to perform directional transmission and / or directional reception in conjunction with wireless communication in a wireless network. Both the UE 120 (e.g., UEs 124, 126, 128) and the RAN 102 may be configured to perform such directional transmission and / or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays, etc.). Each of the multiple antenna arrays may be used for transmission and / or reception in a specific respective direction or range of directions. Both the UE 120 (e.g., UEs 124, 126, 128) and the RAN 102 may be configured to perform any given directional transmission to one or more defined transmitting sectors. Both the UE 120 (e.g., UEs 124, 126, 128) and the RAN 102 may be configured to perform any given directional reception from one or more defined receiving sectors.

[0090] MIMO beamforming in a wireless network may be achieved using RF beamforming and / or digital beamforming. In some embodiments, during a given MIMO transmission, the UE 120 and / or the RAN 102 may be configured to perform MIMO beamforming using all or a subset of its one or more communication antennas.

[0091] Both the UE 120 (e.g., UEs 124, 126, 128) and the RAN 102 may include any suitable radio and / or transceiver for transmitting and / or receiving radio frequency (RF) signals in a bandwidth and / or channel corresponding to a communication protocol utilized by either the UE 120 or the RAN 102 to communicate with each other. The radio component may include hardware and / or software for modulating and / or demodulating communication signals according to a pre-established transmission protocol. The radio component may further include hardware and / or software instructions for communicating via one or more 3GPP® protocols and using a 3GPP® bandwidth. The radio component may include any known receiver and baseband suitable for communication via the communication protocol. The radio component may further include a low noise amplifier (LNA), an additional signal amplifier, an analog-to-digital (A / D) converter, one or more buffers, and a digital baseband.

[0092] 1, in one or more embodiments, one or more of the UEs 120 may exchange frames 140 with the RAN 102. The frames 140 may include UL and DL frames that include SBFD and non-SBFD symbols, simultaneous transmissions and resource signaling, etc., as described throughout this disclosure.

[0093] It is understood that the above description is for purposes of illustration and is not intended as limiting.

[0094] FIG. 2 illustrates an example subband full duplex (SBFD) based resource allocation 200 in a serving cell, in accordance with one or more example embodiments of the present disclosure.

[0095] 2, non-SBFD symbols and SBFD symbols may be transmitted over multiple time segments (e.g., segment 202, segment 204, segment 206). For example, DL non-SBFD symbol 208 may be transmitted in segment 202. DL SBFD symbol 209, then guard 210, then UL SBFD symbol 212, then guard 214, then DL SBFD symbol 216 may be transmitted in segment 204. In segment 206, flexible non-SBFD symbol 218 and UL non-SBFD symbol 220 may be transmitted.

[0096] For a serving cell with SBFD operation, only some symbols (e.g., denoted as DL / UL / flexible symbols) may be used to map either DL or UL physical channels or signals, while some other symbols (e.g., denoted as symbols with potential SBFD operation) may be used to map both DL and UL physical channels or signals within the same symbol. Thus, for a given PRB within a symbol with potential SBFD operation, resources may be identified as DL, UL, or guard bands as shown in FIG. 2. In one example, frequency resources within a symbol may be divided into DL / UL / guard resources within different non-overlapping subbands. Here, and in the remainder of this disclosure, a "subband" corresponds to a set of physical resources within a carrier that are contiguous in frequency, e.g., the number of contiguous physical resource blocks (PRBs) on a common resource block (CRB) grid. The DL, UL, or guard bands may be explicitly or implicitly configured. In one example, the DL and UL subbands are explicitly configured, and the guard band is derived from the PRBs between the DL and UL subbands. In another example, the UL subbands and guard bands are explicitly configured, and the DL subbands are derived from the remaining PRBs.

[0097] FIG. 3A illustrates an example frequency resource determination for a physical uplink shared control channel (PUSCH) transmission 300 with rate matching, in accordance with one or more example embodiments of the present disclosure.

[0098] 3A, a semi-static SBFD symbol may be transmitted during timeslot n, and a semi-static UL symbol 304 may be transmitted during timeslot n+1. For example, a gNB (e.g., gNB 916 in FIG. 9) may configure RB#1 through RB#60 as a first DL subband 306, RB#65 through RB#160 as a UL subband 308, and RB#165 through RB#210 as a second DL subband 310 for slot n (SBFD symbols), and the gNB may configure slot n+1 as a legacy UL slot (non-SBFD symbols). The gNB may configure RB#1 through RB#210 as a DL / UL BWP for a UE (e.g., gNB 916 in FIG. 9). The gNB schedules the first PUSCH 312 in RB #50 through RB #89 in slot n and the second PUSCH 314 in RB #50 through RB #89 in slot n+1. In FIG. 3A, based on Option 1, RB #50 through RB #89 are referenced to the UL BWP for both slot n and slot n+1. In slot n, the first PUSCH 312 is actually transmitted in RB #65 through RB #89, which is constrained within the UL subband 308, because rate matching may be performed around the DL subband and guard bands (e.g., guard 316, guard 318). In slot n+1, the second PUSCH 314 is actually transmitted in RB #50 through RB #89.

[0099] FIG. 3B illustrates an example frequency resource determination for a PUSCH transmission 350 in accordance with one or more example embodiments of the present disclosure.

[0100] 3B, based on Option 2, for slot n, RB#50 to RB#89 are referenced to the UL subband 308, so the first PUSCH 312 is actually transmitted in RB#114 to RB#153, ​​which are referenced to the UL BWP. In slot n+1, the second PUSCH 314 is actually transmitted in RB#50 to RB#89, which are referenced to the UL BWP.

[0101] 3A and 3B, in an SBFD system, in one option (e.g., FIG. 3A), frequency domain resources of signals / channels may be determined in the same manner as in legacy TDD / FDD systems, for example, based on the BWP, in both SBFD symbols and non-SBFD symbols. In an SBFD system, in another option (option 2-FIG. 3B), frequency domain resources of signals / channels may be determined based on the BWP in non-SBFD symbols and based on DL / UL subbands in SBFD symbols. For example, for option 2, if PRB#n is indicated as the starting PRB in the FDRA, and the symbol is a legacy UL symbol, the starting PRB of the PUSCH is PRB#n in the active UL BWP, where the first PRB is the starting PRB of the active UL BWP. If the symbol is an SBFD symbol, the starting PRB of the PUSCH is PRB#(n mod(N UL_sub-band)+Nstart_UL_sub-band) in the active UL BWP, where Nstart_UL_sub-band is the starting PRB of the UL subband relative to the active UL BWP and N UL_sub-band is the number of PRBs in the UL subband. If frequency hopping is configured, the starting PRB of the second hop of the PUSCH is PRB#(n+Nhop) mod(N UL_sub-band)+Nstart_UL_sub-band), where Nhop is the frequency offset in RBs between these two frequency hops. For option 2, in one example, the UE does not expect that the frequency domain resources of DL signals / channels determined relative to the DL subband in the SBFD symbol are unconstrained within the DL subband. The UE does not expect that the frequency domain resources of UL signals / channels determined relative to the UL subband in the SBFD symbol are unconstrained within the UL subband. In one example, the UE does not expect that the frequency domain resources of the UL signal / channel determined with respect to the UL subband within the SBFD symbol will result in non-contiguous frequency resources, e.g., the PUSCH will be split between the upper and lower UL subbands.In another example, the UE may expect that the frequency domain resources of the UL signal / channel determined with reference to the UL subbands within the SBFD symbol will lead to non-contiguous frequency resources, and the UE will cancel the UL transmission in this case.

[0102] For both of the above options, the time and frequency information of the DL, UL sub-bands and guard bands may be obtained from semi-static and / or dynamic signaling.

[0103] FIG. 4 illustrates an example frequency resource determination for PUSCH transmission 400 in accordance with one or more example embodiments of the present disclosure.

[0104] FIG. 4 provides an example of PDSCH resource determination. PDSCH frequency resources are determined based on Option 1 above. Slot n may have a semi-static SBFD symbol 402 that is dynamically switched to a DL symbol, and slot n+1 may have a semi-static DL slot 404 symbol. A gNB (e.g., gNB 916 in FIG. 9 ) schedules a first PDSCH 406 within RB#1 to RB#80 in slot n and a second PDSCH 408 within RB#1 to RB#80 in slot n+1. In slot n, based on the semi-static subband configuration, all symbols in slot n are SBFD symbols. The first PDSCH 406 is rate-matched to the guard band 410 and the vicinity of the UL subband 412 so that the first PDSCH 406 is within RB#1 to RB#60. In slot n+1, based on the semi-static subband configuration, all symbols in slot n are non-SBFD symbols. The second PDSCH 408 is in RB#1 to RB#80. The dynamic subband configuration switches the symbols in slot n to legacy DL symbols 414. The UE still receives only the first PDSCH 406 in RB#1 to RB#60. Then, even if the dynamic subband information DCI is falsely detected by the UE, the gNB and the UE share the same understanding of the PDSCH rate matching in slot n.

[0105] FIG. 5 illustrates an example frequency resource determination for PUSCH transmission 500, in accordance with one or more example embodiments of the present disclosure.

[0106] Referring to FIG. 5, PDSCH frequency resources are determined based on Option 1 above. There may be a semi-static SBFD symbol 402 in slot n that is dynamically switched to a DL symbol, and a semi-static DL slot 404 symbol in slot n+1. A gNB (e.g., gNB 916 in FIG. 9) schedules a first PDSCH 506 in RB#1 to RB#80 in slot n and a second PDSCH 508 in RB#1 to RB#80 in slot n+1. In slot n, based on the semi-static subband configuration, all symbols in slot n are legacy DL symbols. The first PDSCH 506 is in RB#1 to RB#80. The dynamic subband information switches the symbol 502 in slot n to an SBFD symbol 503. Because the first PDSCH 506 overlaps with the UL subband 510 and the guard band 512, the UE drops the first PDSCH 506.

[0107] FIG. 6 illustrates an example PUSCH repetition 600 within a semi-statically configured SBFD symbol that is dynamically switched to a downlink symbol, in accordance with one or more example embodiments of the present disclosure.

[0108] FIG. 6 provides an example of a PUSCH with two repetitions. There may be a semi-static UL slot 602 and a semi-static SBFD symbol 604 that is dynamically switched to a DL symbol 606. Slot n+1 consists of an SBFD symbol 604 based on a semi-static subband configuration, and the SBFD symbol 604 is dynamically switched to a DL symbol 606 based on dynamic subband information. For PUSCH repetition #2 in slot n+1, the frequency resources of the PUSCH are determined based on the semi-static subband configuration and are limited within the UL subband 608. Therefore, slot n+1 is counted as an available slot in the first stage. A UE (e.g., UE 902 in FIG. 9) identifies the symbol in slot n+1 and switches to the DL symbol 606 based on the dynamic subband information. Therefore, the UE drops the PUSCH in slot n+1 in the second stage.

[0109] In another option, if the PUSCH / PUCCH / SRS is within an SBFD symbol determined by a semi-static DL / UL configuration and the frequency domain resource of the PUSCH / PUCCH / SRS is restricted within the UL subband, the slot of the PUSCH / PUCCH / SRS is counted as an available slot; otherwise, the slot is not counted as an available slot. In the first stage, the frequency domain resource of the PUSCH / PUCCH / SRS may be determined based on a semi-static subband configuration. In one example, based on Option 1 in the DL / UL subband section-based frequency domain resource determination, the frequency domain resource of the PUSCH is determined based on the BWP regardless of whether it is an SBFD symbol or a non-SBFD symbol. In the first stage, if the symbol is an SBFD symbol based on the semi-static subband configuration and all PRBs of the PUSCH are restricted within the UL subband, the slot is counted as an available slot. If at least one of the PRBs of the PUSCH is outside the UL subband, the slot is counted as an unavailable slot. If the symbol is a flexible symbol based on the semi-static subband configuration, the slot is counted as an available slot. In the second step, for the available slot determined in the first step, if the UE determines that the frequency domain resource of the PUSCH / PUCCH / SRS collides with the valid DL subbands and guard bands provided by the dynamic subband information, or if the UE determines that the PUSCH / PUCCH / SRS collides with the legacy DL symbol (non-SBFD symbol) provided by the dynamic subband information, the UE cancels the PUSCH / PUCCH / SRS.

[0110] FIG. 7 illustrates an example PUSCH repetition 700 within a semi-statically configured SBFD symbol that is dynamically switched to an uplink symbol, in accordance with one or more example embodiments of the present disclosure.

[0111] FIG. 7 provides an example of a PUSCH with two repetitions. There may be a semi-static UL slot 702, a semi-static SBFD symbol 704 dynamically switched to a UL symbol 706, and a semi-static UL slot 708. Slot n+1 consists of a semi-static SBFD symbol 704 based on a semi-static subband configuration, which is dynamically switched to a legacy UL symbol 706 based on dynamic subband information. For PUSCH repetition #2 in slot n+1, the frequency resource for the PUSCH is determined based on the UL BWP. Because the PUSCH overlaps with the semi-static DL subband 710, PUSCH repetition #2 is postponed to the next slot n+2 along with the semi-static UL slot. Slot n+1 is not counted as an available slot in the first stage. In the second stage, a UE (e.g., UE 902 in FIG. 9) does not check slot n+1, but slot n+1 is switched to a full UL slot.

[0112] FIG. 8 illustrates a flow diagram of an example process 800 for SBFD-based resource allocation in a serving cell, in accordance with one or more example embodiments of the present disclosure.

[0113] Referring to block 802, a device (e.g., gNB 916 of FIG. 9) may configure UL subband resources (e.g., uplink time and uplink frequency) and DL subband resources (e.g., downlink time and downlink frequency) within a serving cell or bandwidth portion for different symbols.

[0114] At block 804, the device may provide a frequency resource configuration to the UE indicating UL subband resources and DL subband resources.

[0115] At block 806, the device may provide a signaling configuration or DCI that schedules signaling transmissions between the device and the UE.

[0116] At block 808, the device may either identify a UL transmission from the UE or provide a DL transmission to the UE based on the signal configuration and the subband resource configuration.

[0117] These embodiments are not intended to be limiting.

[0118] 9 illustrates a network 900 according to various embodiments. Network 900 may operate in a manner consistent with 3GPP® technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this respect, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP® systems.

[0119] The network 900 may include a UE 902, which may include any mobile or non-mobile computing device designed to communicate with the RAN 904 via an over-the-air connection. The UE 902 may be communicatively coupled to the RAN 904 by a Uu interface. The UE 902 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network appliance, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0120] In some embodiments, the network 900 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices communicating using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0121] In some embodiments, the UE 902 may additionally communicate with an AP 906 via a wireless connection. The AP 906 may manage a WLAN connection, which may function to offload some / all network traffic from the RAN 904. The connection between the UE 902 and the AP 906 may conform to any IEEE 802.11 protocol, where the AP 906 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 902, the RAN 904, and the AP 906 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may involve the UE 902 being configured by the RAN 904 to utilize both cellular radio resources and WLAN resources.

[0122] The RAN 904 may include one or more access nodes, such as the AN 908. The AN 908 may terminate the air interface protocols of the UE 902 by providing access stratum protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 908 may enable data / voice connectivity between the CN 920 and the UE 902. In some embodiments, the AN 908 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, which may be referred to as, for example, a CRAN or a virtual baseband unit pool. The AN 908 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 908 may be a macrocell base station or a low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0123] In embodiments where the RAN 904 includes multiple ANs, they may be coupled to one another via an X2 interface (if the RAN 904 is an LTE RAN) or an Xn interface (if the RAN 904 is a 5G RAN). In some embodiments, the X2 / Xn interface, which may be separated into control / user plane interfaces, may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0124] Each AN of the RAN 904 may manage one or more cells, cell groups, component carriers, etc. to provide the UE 902 with an air interface for network access. The UE 902 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 904. For example, the UE 902 and the RAN 904 may use carrier aggregation to enable the UE 902 to connect to multiple component carriers, each corresponding to a Pcell or an Scell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second AN may be any combination of an eNB, a gNB, an ng-eNB, etc.

[0125] The RAN 904 may provide an air interface via licensed or unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques using a PCell / Scell. Before accessing the unlicensed spectrum, the node may perform a medium / carrier sensing operation, for example, based on a listen-before-talk (LBT) protocol.

[0126] In a V2X scenario, the UE 902 or the AN 908 may be or function as an RSU, which may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by an appropriate AN or a static (or relatively static) UE. An RSU implemented in or by a UE may be referred to as a “UE-type RSU”; an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU”; an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU”; etc. In one example, an RSU is a computing device coupled to radio frequency circuits located on the roadside that provides connectivity support for passing vehicular UEs. The RSU may also include internal data storage circuits that store intersection map geometry, traffic statistics, media, and applications / software for detecting and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high-speed events, such as collision avoidance and traffic warnings. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0127] In some embodiments, the RAN 904 may be an LTE RAN 910 including an eNB, such as eNB 912. The LTE RAN 910 may provide the LTE air interface with the following characteristics: a 15 kHz SCS; a CP-OFDM waveform for DL ​​and an SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on the CSI-RS for CSI acquisition and beam management; the PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and the CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate in sub-6 GHz bands.

[0128] In some embodiments, the RAN 904 may be an NG-RAN 914 including a gNB, e.g., gNB 916, or an ng-eNB, e.g., ng-eNB 918. The gNB 916 may connect to a 5G-capable UE using a 5G NR interface. The gNB 916 may connect to a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 918 may also connect to a 5G core through the NG interface, but may connect to a UE through an LTE air interface. The gNB 916 and the ng-eNB 918 may connect to each other through an Xn interface.

[0129] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface (e.g., N3 interface), which carries traffic data between the NG-RAN 914 nodes and the UPF 948, and an NG Control Plane (NG-C) interface (e.g., N2 interface), which is the signaling interface between the NG-RAN 914 nodes and the AMF 944.

[0130] The NG-RAN 914 may provide the 5G NR air interface with the following characteristics: variable SCS; CP-OFDM for DL ​​and CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G NR air interface, like the LTE air interface, may rely on CSI-RS and PDSCH / PDCCH DMRS. The 5G NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for PDSCH phase tracking; and a tracking reference signal for time tracking. The 5G NR air interface may operate in the FR1 band, which includes sub-6 GHz bands, or the FR2 band, which includes bands from 24.25 GHz to 52.6 GHz. The 5G NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0131] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs may be used for dynamic adaptation of the SCS. For example, a UE 902 may be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 902, the SCS of the transmission is also changed. Another example use case of BWPs relates to power saving. In particular, multiple BWPs may be configured for a UE 902 with different amounts of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. A BWP including a smaller number of PRBs may be used for data transmissions with a light traffic load, while enabling power savings in the UE 902 and, in some cases, the gNB 916. A BWP including a larger number of PRBs may be used in scenarios with higher traffic loads. The RAN 904 is communicatively coupled to a CN 920, which includes network elements providing various functions to support data and telecommunication services to customers / subscribers (e.g., users of the UE 902). The components of CN920 may be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of CN920 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of CN920 may be referred to as a network slice, and a logical instantiation of a portion of CN920 may be referred to as a network sub-slice.

[0132] In some embodiments, the CN 920 may be an LTE CN 922, which may also be referred to as an EPC. The LTE CN 922 may include an MME 924, an SGW 926, an SGSN 928, an HSS 930, a PGW 932, and a PCRF 934, which are coupled to each other via the indicated interfaces (or reference points). The functionality of the elements of the LTE CN 922 may be briefly introduced as follows.

[0133] The MME 924 may implement mobility management functions that track the current location of the UE 902 and facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0134] The SGW 926 terminates the S1 interface towards the RAN and may route data packets between the RAN and the LTE CN 922. The SGW 926 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other roles may include lawful interception, charging, and some policy enforcement.

[0135] The SGSN 928 may track the location of the UE 902 and perform security functions and access control. In addition, the SGSN 928 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by the MME 924; MME selection for handover, etc. The S3 reference point between the MME 924 and the SGSN 928 may enable user and bearer information exchange for mobility between 3GPP access networks in idle / active states.

[0136] The HSS 930 may include a database for network users, including subscription-related information, to support processing of communication sessions by network entities. The HSS 930 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 930 and the MME 924 may enable transfer of subscription and authentication data to authenticate / authorize user access to the LTE CN 920.

[0137] The PGW 932 may terminate the SGi interface toward a data network (DN) 936, which may include an application / content server 938. The PGW 932 may route data packets between the LTE CN 922 and the data network 936. The PGW 932 may be coupled to the SGW 926 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 932 may further include a node for policy enforcement and charging data collection (e.g., a PCEF). Additionally, the SGi reference point between the PGW 932 and the data network 936 may be a public or private PDN external to the operator, or an operator's internal packet data network, e.g., for provisioning of IMS services. The PGW 932 may be coupled to a PCRF 934 via a Gx reference point. The PCRF 934 is the policy and charging control element of the LTE CN 922. The PCRF 934 may be communicatively coupled to the app / content server 938 to determine appropriate QoS and charging parameters for service flows. The PCRF 932 may provision the relevant rules to the PCEF (via the Gx reference point) using the appropriate TFT and QCI.

[0138] In some embodiments, the CN 920 may be a 5GC 940. The 5GC 940 may include an AUSF 942, an AMF 944, an SMF 946, a UPF 948, an NSSF 950, an NEF 952, an NRF 954, a PCF 956, a UDM 958, and an AF 960 coupled to each other via interfaces (or "reference points") as shown. The functionality of the elements of the 5GC 940 may be briefly introduced as follows: The AUSF 942 may store data and handle authentication-related functions for authentication of the UE 902. The AUSF 942 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 940 via reference points as shown, the AUSF 942 may exhibit a Nausf service-based interface.

[0139] The AMF 944 may enable other functions of the 5GC 940 to communicate with the UE 902 and the RAN 904 and to subscribe to notifications regarding mobility events for the UE 902. The AMF 944 may be responsible for registration management (e.g., registration of the UE 902), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 944 may provide transport for SM messages between the UE 902 and the SMF 946 and act as a transparent proxy for routing SM messages. The AMF 944 may also provide transport for SMS messages between the UE 902 and the SMSF. The AMF 944 may interact with the AUSF 942 and the UE 902 to perform various security anchor and context management functions. Furthermore, the AMF 944 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 904 and the AMF 944; the AMF 944 may be the termination point of the NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 944 may also support NAS signaling with the UE 902 over the N3 IWF interface.

[0140] The SMF 946 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 948 and the AN 908); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering in the UPF 948 to route traffic to the appropriate destination; termination of the interface to the policy control function; control of policy enforcement, charging, and parts of QoS, lawful intercept (of SM events and the interface to the LI system); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information sent through the AMF 944 to the AN 908 through the N2; and determination of the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 902 and the data network 936.

[0141] The UPF 948 may function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 936, and a branching point supporting multi-homed PDU sessions. The UPF 948 may also perform packet routing and forwarding, packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform user plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering, and downlink data notification triggering. The UPF 948 may include an uplink classifier to support routing of traffic flows to the data network.

[0142] The NSSF 950 may select a set of network slice instances to serve the UE 902. The NSSF 950 may also determine the allowed NSSAIs and, if needed, their mapping to subscribed S-NSSAIs. The NSSF 950 may also determine the AMF set to be used to serve the UE 902, or a list of candidate AMFs based on an appropriate configuration and possibly by querying the NRF 954. The selection of the set of network slice instances for the UE 902 may be triggered by the AMF 944 with which the UE 902 is registered by interacting with the NSSF 950, which may lead to a change of the AMF. The NSSF 950 may interact with the AMF 944 via the N22 reference point; it may communicate with another NSSF in the visited network via the N31 reference point (not shown). Additionally, the NSSF 950 may exhibit an Nnssf service-based interface.

[0143] The NEF 952 may securely expose services and functions provided by 3GPP® network functions for third parties, internal publication / republication, AFs (e.g., AFs 960), edge computing or fog computing systems, etc. In such embodiments, the NEF 952 may authenticate, authorize, or throttle AFs. The NEF 952 may also translate information exchanged with the AF 960 and with internal network functions. For example, the NEF 952 may translate between AF service identifiers and internal 5GC information. The NEF 952 may also receive information from other NFs based on the other NFs' published capabilities. This information may be stored in the NEF 952 as structured data or in a data storage NF using a standardized interface. The stored information may then be republished by the NEF 952 to other NFs and AFs, or used for other purposes, such as analytics. Additionally, the NEF 952 may expose NEF service-based interfaces. The NRF 954 supports service discovery functions, receives NF discovery requests from NF instances, and may provide information about discovered NF instances to the NF instances. The NRF 954 also maintains information about available NF instances and their supported services. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and an "instance" may refer to a specific occurrence of an object, such as may occur during the execution of program code. Additionally, the NRF 954 may exhibit an Nnrf service-based interface. The PCF 956 may provide policy rules to control plane functions and enforce them, and may support a unified policy framework for managing network behavior. The PCF 956 may also implement a front end to access subscription information related to policy decisions in the UDRs of the UDM 958. In addition to communicating with functions via reference points as shown, the PCF 956 exhibits an Npcf service-based interface.The UDM 958 may process subscription-related information to support network entities in processing communication sessions and may store subscription data for the UE 902. For example, the subscription data may be communicated between the UDM 958 and the AMF 944 via the N8 reference point. The UDM 958 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 958 and the PCF 956, and / or structured data and application data for publication for the NEF 952 (including PFDs for application discovery and application requirement information for multiple UEs 902). A Nudr service-based interface may be exposed by the UDR to enable the UDM 958, the PCF 956, and the NEF 952 to access specific sets of stored data and to read, update (e.g., add, modify), delete, and subscribe to notifications of changes in the associated data in the UDR. The UDM may include a UDM-FE responsible for handling credential, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identity handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown, the UDM 958 may expose a Nudm service-based interface. The AF 960 may provide application influence over traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0144] In some embodiments, the 5GC 940 may enable edge computing by selecting operator / third-party services to be geographically close to the point where the UE 902 connects to the network. This may reduce latency and load on the network. To provide an edge computing implementation, the 5GC 940 may select a UPF 948 close to the UE 902 and perform traffic steering from the UPF 948 to the data network 936 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 960. In this way, the AF 960 may influence UPF (re)selection and traffic routing. Based on operator deployment, if the AF 960 is considered a trusted entity, the network operator may allow the AF 960 to interact directly with associated NFs. Additionally, the AF 960 may represent a NAF service-based interface. The data network 936 may represent various network operator services, Internet access, or third-party services, which may be provided by one or more servers, including, for example, the application / content server 938.

[0145] FIG. 10 schematically illustrates a wireless network 1000 according to various embodiments. The wireless network 1000 may include a UE 1002 in wireless communication with an AN 1004. The UE 1002 and the AN 1004 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein. The UE 1002 may be communicatively coupled to the AN 1004 via a connection 1006. The connection 1006 is illustrated as an air interface for enabling the communicative coupling and may conform to a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies. The UE 1002 may include a host platform 1008 coupled to a modem platform 1010. The host platform 1008 may include an application processing circuit 1012 that may be coupled to a protocol processing circuit 1014 of the modem platform 1010. The application processing circuit 1012 may execute various applications for the UE 1002 to source / sink application data. The application processing circuit 1012 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations. The protocol processing circuit 1014 may implement one or more of the layer operations to facilitate the transmission or reception of data over the connection 1006. The layer operations implemented by the protocol processing circuit 1014 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations. The modem platform 1010 may further include a digital baseband circuit 1016 that may implement one or more layer operations that are "below" layer operations performed by the protocol processing circuit 1014 in the network protocol stack.These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding which may include one or more of space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions. The modem platform 1010 may further include transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, and an RF front end (RFFE) 1024 (which may include or be connected to one or more antenna panels 1026). Briefly, the transmit circuitry 1018 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 1020 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 1022 may include low-noise amplifiers, power amplifiers, power tracking components, etc.; and the RFFE 1024 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components in the transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, RFFE 1024, and antenna panel 1026 (collectively referred to as “transmit / receive components”) may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, whether mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be arranged on the same or different chips / modules, etc. In some embodiments, the protocol processing circuit 1014 may include one or more instances of control circuitry (not shown) for providing control functions to the transmit / receive components.UE reception may be established by and through the antenna panel 1026, RFFE 1024, RF circuitry 1022, receive circuitry 1020, digital baseband circuitry 1016, and protocol processing circuitry 1014. In some embodiments, the antenna panel 1026 may receive transmissions from the AN 1004 by receiving beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 1026.

[0146] UE transmissions may be established by and through the protocol processing circuitry 1014, digital baseband circuitry 1016, transmit circuitry 1018, RF circuitry 1022, RFFE 1024, and antenna panel 1026. In some embodiments, the transmit components of the UE 1004 may apply spatial filters to data to be transmitted to form transmit beams emitted by antenna elements of the antenna panel 1026. Similar to the UE 1002, the AN 1004 may include a host platform 1028 coupled to a modem platform 1030. The host platform 1028 may include an application processing circuit 1032 coupled to the protocol processing circuitry 1034 of the modem platform 1030. The modem platform may further include digital baseband circuitry 1036, transmit circuitry 1038, receive circuitry 1040, RF circuitry 1042, RFFE circuitry 1044, and antenna panel 1046. The components of the AN 1004 may be similar to and substantially interchangeable with similarly named components of the UE 1002. In addition to performing data transmission / reception as described above, the components of the AN 1008 may perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. Figure 11 is a block diagram illustrating components according to some example embodiments that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 11 shows a diagrammatic representation of hardware resources 1100 including one or more processors (or processor cores) 1110, one or more memory / storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140 or other interface circuitry. In embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1102 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1100.

[0147] Processors 1110 may include, for example, processor 1112 and processor 1114. Processor 1110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0148] The memory / storage device 1120 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1120 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0149] Communications resources 1130 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1104 or one or more databases 1106 or other network elements over network 1108. For example, communications resources 1130 may include wired communications components (e.g., for coupling via USB, Ethernet, etc.), cellular communications components, NFC components, Bluetooth (or Bluetooth Low Energy) components, Wi-Fi (or other communications components), and other communications components.

[0150] The instructions 1150 may include software, programs, applications, applets, apps, or other executable code for causing at least one of the processors 1110 to perform any one or more of the methodologies discussed herein. The instructions 1150 may reside completely or partially within at least one of the processors 1110 (e.g., a processor's cache memory), the memory / storage devices 1120, or any suitable combination thereof. Furthermore, any portion of the instructions 1150 may be transferred to the hardware resources 1100 from any combination of the peripheral devices 1104 or the database 1106. Thus, the memory of the processor 1110, the memory / storage devices 1120, the peripheral devices 1104, and the database 1106 are examples of computer-readable and machine-readable media.

[0151] FIG. 12 is a diagram illustrating a network in accordance with one or more exemplary embodiments of the present disclosure.

[0152] Network 1200 may operate in a manner consistent with 3GPP® technical specifications or technical reports for 6G systems. In some examples, network 1200 may operate concurrently with network 900. For example, in some examples, network 1200 may share one or more frequency or bandwidth resources with network 900. As one specific example, a UE (e.g., UE 902) may be configured to operate in both network 1200 and network 900. Such a configuration may be based on the UE including circuitry configured to communicate with the frequency and bandwidth resources of both networks 900 and 1200. Generally, some elements of network 1200 may share one or more characteristics with elements of network 900. For brevity and clarity, such elements may not be repeated in the description of network 1200.

[0153] The network 1200 may include a UE 1202, which may include any mobile or non-mobile computing device designed to communicate with the RAN 1208 via an over-the-air connection. The UE 1202 may be similar to, for example, the UE 902. The UE 1202 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network appliance, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0154] Although not specifically shown in FIG. 12 , in some examples, the network 1200 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels, such as, but not limited to, a PSBCH, a PSDCH, a PSSCH, a PSCCH, a PSFCH, etc. Similarly, although not specifically shown in FIG. 12 , the UE 1202 may be communicatively coupled to an AP, such as the AP 906 described with respect to FIG. 9 . Additionally, although not specifically shown in FIG. 12 , in some examples, the RAN 1208 may include one or more ANs, such as the AN 908 described with respect to FIG. 12 . The RAN 1208 and / or the ANs of the RAN 1208 may be referred to as a base station (BS), a RAN node, or using some other terminology or designation.

[0155] The UE 1202 and the RAN 1208 may be configured to communicate over an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features, such as communication in the terahertz (THz) or sub-THz bandwidth, or cooperative communication and sensing. As used herein, the term "cooperative communication and sensing" may refer to a system that enables wireless communication and radio-based sensing through various types of multiplexing. As used herein, the THz or sub-THz bandwidth may refer to communication in a frequency range above 80 GHz. Such frequency ranges may additionally or alternatively be referred to as "millimeter wave" or "mm-wave" frequency ranges.

[0156] The RAN 1208 may enable communication between the UE 1202 and a 6G core network (CN) 1210. Specifically, the RAN 1208 may facilitate transmission and reception of data between the UE 1202 and the 6G CN 1210. The 6G CN 1210 may include various functions, such as an NSSF 950, an NEF 952, an NRF 954, a PCF 956, a UDM 958, an AF 960, an SMF 946, and an AUSF 942. The 6G CN 1210 may additionally include a UPF 948 and a DN 936 shown in FIG. 12 .

[0157] Additionally, the RAN 1208 may include various additional functions in addition to or instead of the functions of a legacy cellular network, such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 1224 and a Compute Service Function (Comp SF) 1236. The Comp CF 1224 and the Comp SF 1236 may be part of or functions of a computing service plane. The Comp CF 1224 may be a control plane function that provides functions such as management of the Comp SF 1236, computational task context creation and management (e.g., creation, retrieval, modification, deletion), and interaction with the underlying computing infrastructure for computing resource management. The Comp SF 1236 may be a user plane function that acts as a gateway to interface computing service users (e.g., UE 1202) and the computing nodes behind the Comp SF instance. Some functions of Comp SF 1236 may include analyzing computing service data received from users to compute tasks that can be performed by computing nodes; maintaining a service mesh ingress gateway or service API gateway; service and billing policy enforcement; performance monitoring and telemetry collection; etc. In some examples, a Comp SF 1236 instance may act as a user plane gateway for a cluster of computing nodes. A Comp CF 1224 instance may control one or more Comp SF 1236 instances. Two other such functions may include a Communication Control Function (Comm CF) 1228 and a Communication Service Function (Comm SF) 1238, which may be part of the communication service plane.The Comm CF 1228 may be a control plane function for the Comm SF 1238, communication session creation / configuration / release management and communication session context management. The Comm SF 1238 may be a user plane function for data transport. The Comm CF 1228 and Comm SF 1238 may be considered upgrades to the SMF 946 and UPF 948 described with respect to the 5G system in FIG. 9. The upgrades provided by the Comm CF 1228 and Comm SF 1238 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, the SMF 946 and UPF 948 may still be used.

[0158] Two other such functions may include a Data Control Function (Data CF) 1222 and a Data Service Function (Data SF) 1232, which may be part of the data service plane. The Data CF 1222 may be a control plane function, providing functions such as Data SF 1232 management, data service creation / configuration / release, and data service context management. The Data SF 1232 may be a user plane function, acting as a gateway between data service users (e.g., the UE 1202 and various functions of the 6G CN 1210) and data service endpoints behind the gateway. Specific functions may include parsing data service user data, forwarding it to corresponding data service endpoints, generating charging data, and reporting data service status. Another such function may be a Service Orchestration and Chaining Function (SOCF) 1220, which may discover, orchestrate, and chain up communication / computing / data services provided by functions within the network. When SOCF 1220 receives a service request from a user, it may interact with one or more of Comp CF 1224, Comm CF 1228, and Data CF 1222 to identify Comp SF 1236, Comm SF 1238, and Data SF 1232 instances, configure service resources, and create a service chain, which may include multiple Comp SF 1236, Comm SF 1238, and Data SF 1232 instances and their associated computing endpoints. Workload processing and data movement may then occur within the created service chain. SOCF 1220 may also be responsible for maintaining, updating, and releasing the created service chain.

[0159] Another such function may be a service registration function (SRF) 1214, which may act as a registry for system services provided in the user plane, such as services provided by service endpoints behind the Comp SF 1236 and Data SF 1232 gateways and services provided by the UE 1202. The SRF 1214 may be considered a counterpart to the NRF 954, which may act as a registry for network functions.

[0160] Other such functions may include an evolved service communication proxy (eSCP) and a service infrastructure control function (SICF) 1226, which may provide a service communication infrastructure for control plane services and user plane services. The eSCP may refer to a 5G service communication proxy (SCP) with the addition of user plane service communication proxy functionality. Thus, the eSCP is represented by two parts: eCSP-C 1212 and eSCP-U 1234 for the control plane service communication proxy and the user plane service communication proxy, respectively. The SICF 1226 may control and configure the eCSP instances with respect to service traffic routing policies, access rules, load balancing configuration, performance monitoring, etc.

[0161] Another such function is the AMF 1244. The AMF 1244 may be similar to 944, but has additional functionality. Specifically, the AMF 1244 may include potential functional repartitioning, such as moving message forwarding functionality from the AMF 1244 to the RAN 1208.

[0162] Another such function is the service orchestration exposure function (SOEF) 1218. The SOEF can be configured to expose service orchestration and chaining services to external users, such as applications.

[0163] The UE 1202 may include an additional function referred to as a computing client service function (comp CSF) 1204. The comp CSF 1204 may have both control plane and user plane functions and may interact with corresponding network-side functions, such as the SOCF 1220, Comp CF 1224, Comp SF 1236, Data CF 1222, and / or Data SF 1232, for service discovery, request / response, computational task workload exchange, etc. The comp CSF 1204 may also work with the network-side functions to determine whether computational tasks should be performed in elements of the UE 1202, the RAN 1208, and / or the 6G CN 1210.

[0164] The UE 1202 and / or Comp CSF 1204 may include a service mesh proxy 1206. The service mesh proxy 1206 may act as a proxy for service-to-service communications within the user plane. The capabilities of the service mesh proxy 1206 may include one or more of addressing, security, load balancing, and / or the like.

[0165] FIG. 13 illustrates a simplified block diagram of artificial (AI)-assisted communication between user equipment and a radio access network, in accordance with one or more exemplary embodiments of the present disclosure.

[0166] 13 illustrates an exemplary artificial intelligence (AI)-assisted communications architecture. More specifically, as described in further detail below, AI / machine learning (ML) models may be used or leveraged to facilitate wireless communications between the UE 1305 and the RAN 1310.

[0167] In this example, the UE 1305 and the RAN 1310 operate in a manner consistent with 3GPP® technical specifications and / or technical reports for 6G systems. In some examples, the wireless cellular communication between the UE 1305 and the RAN 1310 may be part of or may operate concurrently with the networks 900, 1200 and / or some other networks described herein.

[0168] The UE 1305 may be similar to and share one or more features with the UE 902, the UE 1202, and / or some other UE described herein. The UE 1305 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network appliance, a machine-type communications device, an M2M or D2D device, an IoT device, etc. The RAN 1310 may be similar to and share one or more features with the RAN 914, the RAN 1208, and / or some other RAN described herein.

[0169] 13, the AI-related elements of the UE 1305 may be similar to the AI-related elements of the RAN 1310. For purposes of discussion herein, descriptions of various elements are provided from the perspective of the UE 1305, but it will be understood that such discussion or description also applies to similarly named / numbered elements of the RAN 1310 unless expressly stated otherwise.

[0170] As mentioned above, the UE 1305 may include various elements or functions related to AI / ML. Such elements may be implemented as hardware, software, firmware, and / or some combination thereof. In examples, one or more of these elements may be implemented as part of the same hardware (e.g., chip or multiprocessor chip), software (e.g., computing program), or firmware of another element.

[0171] One such element may be the data repository 1315. The data repository 1315 may be responsible for data collection and storage. Specifically, the data repository 1315 may collect and store RAN configuration parameters, measurement data, key performance indicators (KPIs), model performance metrics, etc. for model training, updates, and inference. More generally, collected data is stored in the repository. The stored data may be discovered and extracted from the data repository 1315 by other elements. For example, as can be seen, the inference data selection / filter element 1350 may retrieve data from the data repository 1315. In various examples, the UE 1305 may be configured to discover and request data from the data repository 1315 within the RAN (and vice versa). More generally, the data repository 1315 of the UE 1305 may be communicatively coupled to the data repository 1315 of the RAN 1310 such that the respective data repositories of the UE and the RAN may share collected data with each other.

[0172] Another such element may be the training data selection / filtering function block 1320. The training data selection / filtering function block 1320 may be configured to generate training, validation, and test datasets for model training. The training data may be extracted from the data repository 1315. The data may be selected / filtered based on the particular AI / ML model being trained. The data may optionally be transformed / augmented / preprocessed (e.g., normalized) before being loaded into the dataset. The training data selection / filtering function block 1320 may label the data in the dataset for supervised learning. The generated dataset may then be provided to the model training function block 1325.

[0173] As mentioned above, another such element may be the model training function block 1325. This function block may be responsible for training and updating (retraining) AI / ML models. Selected models may be trained using the supplied datasets (including training, validation, and testing) from the training data selection / filtering function block. The model training function block 1325 may generate trained and tested AI / ML models ready for deployment. The generated trained and tested models may be stored in the model repository 1335.

[0174] The model repository 1335 may be responsible for storing and publishing AI / ML models (both trained and untrained). Trained / updated models may be stored in the model repository 1335. Models and model parameters may be discovered and requested by other functional blocks (e.g., the training data selection / filter functional block 1320 and / or the model training functional block 1325). In some examples, the UE 1305 may discover and request AI / ML models from the model repository 1335 of the RAN 1310. Similarly, the RAN 1310 may be able to discover and / or request AI / ML models from the model repository 1335 of the UE 1305. In some examples, the RAN 1310 may configure models and / or model parameters in the model repository 1335 of the UE 1305.

[0175] Another such element may be the model management function block 1340. The model management function block 1340 may be responsible for managing the AI / ML models generated by the model training function block 1325. Such management functions may include deployment of trained models, monitoring model performance, etc. In model deployment, the model management function block 1340 may allocate and schedule hardware and / or software resources for inference based on received trained and tested models. As used herein, "inference" refers to the process of using a trained AI / ML model to generate data analysis, actions, policies, etc. based on input inference data. In performance monitoring, based on radio performance KPIs and model performance metrics, the model management function block 1340 may decide to terminate a running model, initiate model retraining, select a different model, etc. In an example, the model management function block 1340 of the RAN 1310 may configure model management policies in the UE 1305 as shown.

[0176] Another such element may be the inference data selection / filtering function block 1350. The inference data selection / filter function block 1350 may be responsible for generating a dataset for model inference in the inference function block 1345, as described below. Specifically, inference data may be extracted from the data repository 1315. The inference data selection / filter function block 1350 may select and / or filter the data based on the deployed AI / ML model. The data may be transformed / augmented / preprocessed after the same transformation / augmentation / preprocessing as in the training data selection / filtering described with respect to function block 1320. The generated inference dataset may be provided to the inference function block 1345.

[0177] Another such element may be the inference function block 1345. The inference function block 1345 may be responsible for performing the inference described above. Specifically, the inference function block 1345 may consume an inferred data set provided by the inference data selection / filtering function block 1350 and generate one or more results. Such results may be or may include data analysis, actions, policies, etc. The results may be provided to the performance measurement function block 1330.

[0178] The performance measurement function block 1330 may be configured to measure model performance metrics (e.g., accuracy, model bias, runtime latency, etc.) of the deployed and running models based on the inference results for monitoring purposes. The model performance data may be stored in the data repository 1315.

[0179] The following examples relate to further embodiments.

[0180] For one or more embodiments, at least one of the components depicted in one or more of the foregoing drawings may be configured to perform one or more operations, techniques, processes, and / or methods as described in the exemplary section below. For example, the baseband circuitry described above in connection with one or more of the foregoing drawings may be configured to operate according to one or more of the examples described below. For another example, circuitry associated with a UE, a base station, a network element, etc. described above in connection with one or more of the foregoing drawings may be configured to operate according to one or more of the examples described in the exemplary section below.

[0181] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. As used herein, the terms "computing device," "user device," "communication station," "station," "handheld device," "mobile device," "wireless device," and "user equipment" (UE) refer to wireless communication devices such as cellular phones, smartphones, tablets, netbooks, wireless terminals, laptop computers, femtocells, high data rate (HDR) subscriber stations, access points, printers, point-of-sale devices, access terminals, or other personal communications system (PCS) devices. Devices may be either mobile or stationary.

[0182] As used herein, the term "communicate" is intended to include transmitting, receiving, or both transmitting and receiving. This can be particularly useful in claims describing an organization of data being transmitted by one device and received by another, but where only one function of the devices is required to inflict the claim. Similarly, a two-way exchange of data between two devices (where both devices transmit and receive during the exchange) can be described as "communicating" when only one function of the devices is claimed. When used herein with respect to wireless communication signals, the term "communicating" includes transmitting wireless communication signals and / or receiving wireless communication signals. For example, a wireless communication unit capable of communicating wireless communication signals can include a wireless transmitter for transmitting wireless communication signals to at least one other wireless communication unit and / or a wireless communication receiver for receiving wireless communication signals from at least one other wireless communication unit.

[0183] As used herein, unless otherwise specified, the use of ordinal adjectives such as "first," "second," "third," etc. to describe a common object merely indicates that different instances of the same object are being referred to and is not intended to imply that the objects so described must be in a given order temporally, spatially, sequentially, or in any other manner.

[0184] As used herein, the term "access point" (AP) may refer to a fixed station. An access point may also be referred to as an access node, a base station, an evolved Node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be referred to as a mobile station, a user equipment (UE), a wireless communication device, or some other similar terminology known in the art. The embodiments disclosed herein generally relate to wireless networks. Some embodiments may relate to wireless networks that operate according to one of the IEEE 802.11 standards.

[0185] Some embodiments may be used in conjunction with a variety of devices and systems, such as, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A / V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), etc.

[0186] Some embodiments may be used in conjunction with one-way and / or two-way wireless communication systems, cellular radiotelephone communication systems, mobile phones, cellular phones, radiotelephones, personal communication system (PCS) devices, PDA devices incorporating wireless communication devices, mobile or portable global positioning system (GPS) devices, devices incorporating GPS receivers or transceivers or chips, devices incorporating RFID elements or chips, multiple-input multiple-output (MIMO) transceivers or devices, single-input multiple-output (SIMO) transceivers or devices, multiple-input single-output (MISO) transceivers or devices, devices with one or more internal and / or external antennas, digital video broadcast (DVB) devices or systems, multi-standard wireless devices or systems, wired or wireless handheld devices such as smartphones, wireless application protocol (WAP) devices, etc.

[0187] Some embodiments may utilize a variety of communication technologies, such as radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), time division multiplexing (TDM), time division multiple access (TDMA), enhanced TDMA (E-TDMA), general packet radio service (GPRS), enhanced GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA), CDMA2000, single carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multitone (DMT), Bluetooth, global positioning systems, and the like. The present invention may be used in conjunction with one or more types of wireless communication signals and / or systems according to one or more wireless communication protocols, such as GPS, Wi-Fi, Wi-Max, ZigBee, Ultra Wideband (UWB), Global System for Mobile Communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, Enhanced Data Rates for GSM Evolution (EDGE), etc. Other embodiments may be used in various other devices, systems and / or networks.

[0188] Various embodiments are described below.

[0189] Example 1 may include a next generation Node B (gNB) device for configuring uplink and downlink transmissions in a full-duplex system, the gNB device comprising: processing circuitry coupled to storage for storing information associated with the configuration, the processing circuitry configured to: configure uplink subband resources and downlink subband resources within a serving cell or bandwidth portion for different symbols, where the uplink subband resources include uplink time and uplink frequency resources, and where the downlink subband resources include downlink time and downlink frequency resources; provide a subband resource configuration to a user equipment (UE) indicating the uplink time, the uplink frequency resources, the downlink time, and the downlink frequency resources; provide a signal configuration or downlink control information (DCI) to the UE that schedules a signal transmission; and detect an uplink transmission from the UE based on the signal configuration and the subband resource configuration or provide a downlink transmission to the UE based on the signal configuration and the subband resource configuration.

[0190] Example 2 may include the gNB device of Example 1 and / or any other example herein, wherein the subband resource configuration includes a time-domain configuration of at least one of uplink symbols, downlink symbols, or flexible symbols that include subband frequency information, signaled by semi-static signaling or dynamic signaling.

[0191] Example 3 may include a gNB device as described in Example 1 and / or any other example herein that uses dynamic signaling in which the subband resource configuration is carried by a bit field within a downlink assignment or uplink grant DCI or by a DCI other than the DCI used for the downlink assignment or uplink grant.

[0192] Example 4 may include the gNB device of Example 3 and / or any other example herein, wherein the dynamic signaling by the bit field in the downlink assignment or the uplink grant DCI indicates that a set of symbols includes or does not include a flexible subband, and the set of symbols is for a physical downlink shared control channel (PDSCH) scheduled by the downlink assignment, or for a physical uplink shared control channel (PUSCH) scheduled by the uplink grant, or all symbols are for a timeslot in which the PDSCH is scheduled by the downlink assignment or the PUSCH is scheduled by the uplink grant.

[0193] Example 5 may include the gNB device of Example 1 and / or any other example herein, wherein the subband resource configuration uses semi-static signaling.

[0194] Example 6 may include the gNB device of Example 5 and / or any other example herein, wherein the uplink transmission from the UE or the downlink transmission to the UE is based on dynamic signaling.

[0195] Example 7 may include the gNB device of Example 1 and / or any other example herein, wherein the subband resource configuration uses dynamic signaling.

[0196] Example 8 may include the gNB device of Example 7 and / or any other example herein, wherein available slots for the UE are based on the subband resource configuration using semi-static signaling, and the subband resource configuration indicates whether the UE should transmit or drop the uplink transmission based on dynamic signaling in the available slots if the uplink transmission repetition overlaps with a symbol associated with a different subband resource configuration.

[0197] Example 9 may include a computer-readable storage medium comprising instructions that, upon execution of the instructions by processing circuitry of a user equipment (UE) device for configuring uplink and downlink transmissions in a full-duplex system, cause the processing circuitry to perform the following procedures: identifying from a next generation Node B (gNB) device a subband resource configuration indicating uplink time and uplink frequency resources, downlink time and downlink frequency resources within a serving cell or bandwidth portion for different symbols; identifying from the gNB device a signaling configuration or downlink control information (DCI) that schedules signaling transmissions; and identifying a downlink transmission from the gNB device based on the signaling configuration and the subband resource configuration, or providing an uplink transmission to the gNB device based on the subband resource configuration.

[0198] Example 10 may include the computer-readable storage medium of Example 9 and / or any other example herein, wherein the subband resource configuration includes a time-domain configuration of at least one of uplink symbols, downlink symbols, or flexible symbols containing subband information, signaled by semi-static signaling or dynamic signaling.

[0199] Example 11 may include the computer-readable storage medium of Example 9 and / or any other example herein, using dynamic signaling in which the subband resource configuration is carried by a bit field within a downlink assignment or uplink grant DCI or by a DCI other than the DCI used for the downlink assignment or uplink grant.

[0200] Example 12 may include the computer-readable storage medium of Example 11 and / or any other example herein, wherein the dynamic signaling by the bit field in the downlink assignment or the uplink grant DCI indicates that a set of symbols includes or does not include a flexible subband, and the set of symbols is for a physical downlink shared control channel (PDSCH) scheduled by the downlink assignment, or for a physical uplink shared control channel (PUSCH) scheduled by the uplink grant, or all symbols are for a time slot in which the PDSCH is scheduled by the downlink assignment, or the PUSCH is scheduled by the uplink grant.

[0201] Example 13 may include the computer-readable storage medium of Example 9 and / or any other example herein, wherein the frequency resource configuration uses semi-static signaling.

[0202] Example 14 may include the computer-readable storage medium of Example 13 and / or any other example herein, wherein the uplink transmission from the UE device or the downlink transmission to the UE device is based on dynamic signaling.

[0203] Example 15 may include the computer-readable storage medium of Example 9 and / or any other example herein, wherein the subband resource configuration uses dynamic signaling.

[0204] Example 16 may include the computer-readable storage medium of Example 15 and / or any other example herein, wherein available slots for the UE device are based on the subband resource configuration using semi-static signaling, and the subband resource configuration indicates whether the UE device should transmit or drop the uplink transmission based on dynamic signaling in the available slots if the uplink transmission repetition overlaps with a symbol associated with a different subband resource configuration.

[0205] Example 17 may include a method of configuring uplink and downlink transmissions in a full-duplex system, the method comprising: configuring, by a processing circuit of a next-generation Node B (gNB) device, uplink subband resources and downlink subband resources within a serving cell or bandwidth portion for different symbols, where the uplink subband resources include uplink time and uplink frequency resources, and where the downlink subband resources include downlink time and downlink frequency resources; providing, by the processing circuit, a subband resource configuration to a user equipment (UE) indicating the uplink time, the uplink frequency resources, the downlink time, and the downlink frequency resources; providing, by the processing circuit, a signaling configuration or downlink control information (DCI) to the UE that schedules a signaling transmission; and identifying, by the processing circuit, an uplink transmission from the UE based on the signaling configuration and the subband resource configuration, or providing a downlink transmission to the UE based on the signaling configuration and the subband resource configuration.

[0206] Example 18 may include a method as described in Example 17 and / or any other example herein, wherein the subband resource configuration includes a time-domain configuration of at least one of uplink symbols, downlink symbols, or flexible symbols containing subband information, signaled by semi-static signaling or dynamic signaling.

[0207] Example 19 may include a method as described in Example 17 and / or any other example herein, using dynamic signaling in which the subband resource configuration is carried by a bit field within a downlink assignment or uplink grant DCI, or by a DCI other than the DCI used for the downlink assignment or uplink grant.

[0208] Example 20 may include the method of Example 19 and / or any other example herein, wherein the dynamic signaling by the bit field in the downlink assignment or the uplink grant DCI indicates that a set of symbols includes or does not include a subband, and the set of symbols is for a Physical Downlink Shared Control Channel (PDSCH) scheduled by the downlink assignment, or for a Physical Uplink Shared Control Channel (PUSCH) scheduled by the uplink grant, or all symbols are for a timeslot in which the PDSCH is scheduled by the downlink assignment or the PUSCH is scheduled by the uplink grant.

[0209] Example 21 may include the method of example 17 and / or any other example herein, wherein the subband resource configuration uses semi-static signaling.

[0210] Example 22 may include the method of Example 21 and / or any other example herein, wherein the uplink transmission from the UE or the downlink transmission to the UE is based on dynamic signaling.

[0211] Example 23 may include the method of example 22 and / or any other example herein, wherein the subband resource configuration uses dynamic signaling.

[0212] Example 24 may include an apparatus comprising means for: configuring, by a next generation Node B (gNB) device, uplink subband resources and downlink subband resources within a serving cell or bandwidth portion for different symbols, where the uplink subband resources include uplink time and uplink frequency resources, and where the downlink subband resources include downlink time and downlink frequency resources; providing a subband resource configuration to a user equipment (UE) indicating the uplink time, the uplink frequency resources, the downlink time, and the downlink frequency resources; providing a signal configuration or downlink control information (DCI) to the UE that schedules a signal transmission; and identifying an uplink transmission from the UE based on the signal configuration and the subband resource configuration, or providing a downlink transmission to the UE based on the signal configuration and the subband resource configuration.

[0213] Example 25 may include one or more non-transitory computer-readable media comprising instructions that, upon execution by one or more processors of the electronic device, cause the electronic device to perform one or more elements of the method described in or related to any of Examples 1-24 or any other method or process described herein. Example 26 may include an apparatus comprising logic, modules, and / or circuitry for performing one or more elements of the method described in or related to any of Examples 1-24 or any other method or process described herein.

[0214] Example 27 may include any method, technique, or process described in or related to any of Examples 1-24, or any portion or part thereof.

[0215] Example 28 may include an apparatus that includes one or more processors and one or more computer-readable media having instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portions thereof, described in or related to any of Examples 1 through 24.

[0216] Example 29 may include a method of communication in a wireless network as shown and described herein.

[0217] Example 30 may include a system for providing wireless communication as shown and described herein.

[0218] Example 31 may include a device for providing wireless communication as shown and described herein.

[0219] Embodiments according to the present disclosure are particularly disclosed in the appended claims directed to methods, storage media, devices, and computer program products, and any feature recited in one claim category, e.g., a method, may also be claimed in another claim category, e.g., a system. Dependencies or references back to preceding items in the appended claims have been selected for formality reasons only. However, any subject matter resulting from an intentional reference (e.g., multiple dependency) back to any previous claim may be claimed, and consequently, any combination of claims and their features is disclosed and may be claimed regardless of the dependency selected in the appended claims. Subject matter that may be claimed comprises not only combinations of features set forth in the appended claims, but also any other combination of features in the claims, and each feature recited in a claim may be combined with any other feature or combination of features in the claim. Furthermore, any embodiment or feature described or shown in this specification may be claimed in a separate claim and / or in any combination with any embodiment or feature described or shown in this specification or with any of the features in the appended claims. The foregoing description of one or more implementations has been provided for illustration and description, and is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0220] Certain aspects of the present disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and / or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, respectively, can be implemented by computer-executable program instructions. Similarly, some blocks of the block diagrams and flow diagrams may not necessarily be performed in the order shown, or may not necessarily be performed at all, according to some implementations.

[0221] These computer-executable program instructions may be loaded onto a special purpose computer or other specific machine, processor, or other programmable data processing apparatus to produce a specific machine, such that the instructions, when executed on a computer, processor, or other programmable data processing apparatus, produce means for implementing one or more functions specified in one or more blocks of the flowcharts. These computer program instructions may also be stored in a computer-readable storage medium or memory that can direct a computer or other programmable data processing apparatus to function in a specific way, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means for implementing one or more functions specified in one or more blocks of the flowcharts. As an example, a particular implementation may provide a computer program product comprising a computer-readable storage medium having computer-readable program code or program instructions embodied therein, the computer-readable program code adapted to be executed to implement one or more functions specified in one or more blocks of the flowcharts. Furthermore, computer program instructions may be loaded onto a computer or other programmable data processing apparatus such that the instructions, which execute on the computer or other programmable apparatus, provide elements or steps for implementing the functions specified in one or more blocks of the flow diagram, and a series of operational elements or steps may be executed on the computer or other programmable apparatus to generate a computer-implemented process.

[0222] Thus, the blocks in the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, can be implemented by a dedicated hardware-based computer system that performs the specified functions, elements, or steps, or a combination of dedicated hardware and computer instructions.

[0223] In particular, conditional language such as "can," "could," "might," or "may," unless otherwise stated or understood otherwise within the context in which it is used, is generally intended to convey that certain implementations may include particular features, elements, and / or operations, while other implementations do not. Thus, such conditional language is generally not intended to imply that features, elements, and / or operations are in any way required for one or more implementations, or that one or more implementations necessarily include logic for determining, with or without user input or prompts, whether those features, elements, and / or operations should be included or performed in any particular implementation.

[0224] It will be apparent that many modifications and other implementations of the disclosure set forth herein will have the benefit of the teachings presented in the foregoing descriptions and the associated drawings. It will therefore be understood that the disclosure is not limited to the particular implementations disclosed, and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0225] For purposes of this specification, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0226] As used herein, the term “circuitry” refers to, is a part of, or includes hardware components configured to provide a described functionality, such as, for example, electronic circuits, logic circuits, processors (shared, dedicated, or groups) and / or memories (shared, dedicated, or groups), application-specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-volume PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or combinations of circuitry used in an electrical or electronic system) and program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0227] As used herein, the term “processor circuitry” refers to, is a part of, or includes circuitry capable of continuously and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. A processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes. A processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuitry” and / or “baseband circuitry” may be considered synonymous with “processor circuitry” and may be referred to as such. As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, and / or a network interface card.

[0228] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0229] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[0230] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or component thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and / or "system" may refer to multiple computing devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0231] As used herein, terms such as "appliance" or "computer appliance" refer to a computing device or system that includes program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computing appliance or is otherwise dedicated to providing specific computing resources.

[0232] As used herein, the term “resource” refers to a physical or virtual device, a physical or virtual component in a computing environment, and / or a physical or virtual component in a particular device, such as, for example, a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and application, and / or workload unit. “Hardware resources” may refer to computational, storage, and / or network resources provided by physical hardware elements. “Virtualized resources” may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The terms “network resources” or “communication resources” may refer to resources accessible by a computer device / system via a communication network. The term “system resources” may refer to any kind of shared entity for providing services and may include computing and / or network resources. A system resource may be viewed as a set of coherent functions, network data objects, or services that reside on a single host or on multiple hosts and are accessible through a clearly identifiable server.

[0233] As used herein, the term "channel" refers to any transmission medium, either tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous with and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term meaning a path or medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0234] As used herein, terms such as "instantiate" and "instantiation" refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0235] The terms "coupled" and "communicatively coupled," along with their derivatives, are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or that one or more other elements are coupled or connected between the elements that are said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in communication with each other, including through a wired or other interconnect connection and / or through a wireless communication channel or link.

[0236] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element or the data element that contains the contents.

[0237] Unless used differently herein, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP® TR 21.905 v16.0.0 (2019-06) and / or any other 3GPP® standard. For purposes of this specification, the following abbreviations (shown in Table 1) may apply to the examples and embodiments discussed herein:

[0238] Table 1: Abbreviations [Table 1] [Table 2] [Table 3] [Table 4] [Table 5] [Table 6] [Table 7] [Table 8] [Table 9] [Table 10]

Claims

1. A next generation Node B (gNB) device for configuring uplink and downlink transmission in a full duplex system, comprising: a processing circuit coupled to a storage for storing information associated with the configuration; Equipped with The processing circuitry Configuring uplink subband resources and downlink subband resources within a serving cell or bandwidth portion for different symbols, where the uplink subband resources include uplink time and uplink frequency resources, and where the downlink subband resources include downlink time and downlink frequency resources; providing a subband resource configuration to a user equipment (UE) indicating the uplink time, the uplink frequency resources, the downlink time, and the downlink frequency resources; providing the UE with signal configuration or downlink control information (DCI) that schedules signal transmissions; and Detecting an uplink transmission from the UE based on the signal configuration and the sub-band resource configuration, or providing a downlink transmission to the UE based on the signal configuration and the sub-band resource configuration. configured to: gNB device.

2. The gNB device of claim 1, wherein the subband resource configuration includes a time-domain configuration of at least one of uplink symbols, downlink symbols, or flexible symbols containing subband frequency information, signaled by semi-static signaling or dynamic signaling.

3. The gNB device of claim 1, wherein the subband resource configuration uses dynamic signaling carried by a bit field within a downlink assignment or uplink grant DCI, or by a DCI other than a DCI used for the downlink assignment or uplink grant.

4. 4. The gNB device of claim 3, wherein the dynamic signaling by the bit field in the downlink assignment or the uplink grant DCI indicates that a set of symbols includes or does not include a flexible subband, and the set of symbols is for a physical downlink shared control channel (PDSCH) scheduled by the downlink assignment, or for a physical uplink shared control channel (PUSCH) scheduled by the uplink grant, or all symbols are for a time slot in which the PDSCH is scheduled by the downlink assignment or the PUSCH is scheduled by the uplink grant.

5. The gNB device of claim 1 , wherein the subband resource configuration uses semi-static signaling.

6. The gNB device of claim 5, wherein the uplink transmission from the UE or the downlink transmission to the UE is based on dynamic signaling.

7. The gNB device of claim 1, wherein the subband resource configuration uses dynamic signaling.

8. 8. The gNB device of claim 7, wherein available slots for the UE are based on the subband resource configuration using semi-static signaling, and the subband resource configuration indicates whether the UE should transmit or drop the uplink transmission based on dynamic signaling in the available slots if an uplink transmission repetition overlaps with a symbol associated with a different subband resource configuration.

9. 1. A computer program comprising instructions that, upon execution by processing circuitry of a user equipment (UE) device for configuring uplink and downlink transmissions in a full-duplex system, Identifying from a next generation Node B (gNB) device a subband resource configuration indicating uplink time and uplink frequency resources, downlink time and downlink frequency resources within a serving cell or bandwidth portion for different symbols; A procedure for identifying a signal configuration or downlink control information (DCI) for scheduling signal transmission from the gNB device; and Identifying a downlink transmission from the gNB device based on the signal configuration and the subband resource configuration, or providing an uplink transmission to the gNB device based on the subband resource configuration. causing the processing circuitry to execute Computer program.

10. 10. The computer program product of claim 9, wherein the subband resource configuration comprises a time domain configuration of at least one of uplink symbols, downlink symbols, or flexible symbols containing subband information, signaled by semi-static signaling or dynamic signaling.

11. 10. The computer program product of claim 9, wherein the subband resource configuration uses dynamic signaling carried by a bit field within a downlink assignment or uplink grant DCI or by a DCI other than a DCI used for a downlink assignment or uplink grant.

12. 12. The computer program product of claim 11, wherein the dynamic signaling by the bit field in the downlink assignment or the uplink grant DCI indicates whether a set of symbols includes a flexible subband, and the set of symbols is for a Physical Downlink Shared Control Channel (PDSCH) scheduled by the downlink assignment, or for a Physical Uplink Shared Control Channel (PUSCH) scheduled by the uplink grant, or all symbols are for a time slot in which the PDSCH is scheduled by the downlink assignment or the PUSCH is scheduled by the uplink grant.

13. The computer program product of claim 9 , wherein the subband resource configuration uses semi-static signaling.

14. The computer program product of claim 13 , wherein the uplink transmission from the UE device or the downlink transmission to the UE device is based on dynamic signaling.

15. The computer program product of claim 9 , wherein the subband resource configuration uses dynamic signaling.

16. 16. The computer program product of claim 15, wherein available slots for the UE device are based on the subband resource configuration using semi-static signaling, and the subband resource configuration indicates whether the UE device should transmit or drop the uplink transmission based on dynamic signaling in the available slots if an uplink transmission repetition overlaps with a symbol associated with a different subband resource configuration.

17. 1. A method for configuring uplink and downlink transmissions in a full duplex system, comprising: configuring, by a processing circuit of a next generation Node B (gNB) device, uplink subband resources and downlink subband resources within a serving cell or bandwidth portion for different symbols, where the uplink subband resources include uplink time and uplink frequency resources, and where the downlink subband resources include downlink time and downlink frequency resources; providing, by the processing circuitry, a subband resource configuration to a user equipment (UE) indicating the uplink time, the uplink frequency resources, the downlink time, and the downlink frequency resources; providing, by the processing circuitry, signal configuration or downlink control information (DCI) to the UE that schedules signal transmissions; and and identifying, with the processing circuitry, an uplink transmission from the UE based on the signal configuration and the sub-band resource configuration, or providing a downlink transmission to the UE based on the signal configuration and the sub-band resource configuration. A method comprising:

18. 18. The method of claim 17, wherein the subband resource configuration comprises a time-domain configuration of at least one of uplink symbols, downlink symbols, or flexible symbols containing subband information, signaled by semi-static signaling or dynamic signaling.

19. 19. A computer program comprising instructions for causing said processing circuitry to perform the method according to claim 17 or 18.

20. Apparatus comprising means for carrying out the method according to claim 17 or 18.

21. A computer-readable recording medium storing a computer program according to any one of claims 9 to 16.

22. A computer-readable recording medium storing the computer program according to claim 19.

Images