Downlink (DL) or uplink (UL) transmission in duplex operation

Abstract

A system, apparatus, method, and computer-readable medium are provided for multiple operation modes for downlink (DL) or uplink (UL) transmission in duplex operation, where the method comprises: a fifth generation (5G) base station (gNB) configuring one or more UL and / or DL ​​resources within a serving cell or bandwidth portion (BWP) bandwidth for different symbols; a user equipment (UE) receiving an indication of the UL and DL resource configuration; and the UE receiving or transmitting a DL or UL channel / signal according to the DL or UL channel / signal configuration and / or DCI scheduling the DL or UL channel / signal. Other embodiments may be described and / or claimed.

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims priority to International Patent Application No. PCT / CN2022 / 085222, filed April 5, 2022; and U.S. Provisional Patent Application No. 63 / 333,964, filed April 22, 2022.

[0002] Various embodiments may generally relate to the field of wireless communications. For example, some embodiments may relate to downlink (DL) or uplink (UL) transmission in a duplex operation. Particular embodiments may relate to transmission modes or uplink control information (UCI) in a duplex operation. [Background technology]

[0003] Various embodiments may relate generally to the field of wireless communications. [Brief description of the drawings]

[0004] [Figure 1] 1 illustrates an example of non-overlapping sub-band full duplex (NOSB-FD) for new radio (NR), according to various embodiments.

[0005] [Diagram 2] 1 illustrates example modes of operation for physical uplink control channel (PUCCH) resources, according to various embodiments.

[0006] [Diagram 3] 1 illustrates an example of a physical uplink shared channel (PUSCH) repetition type A, according to various embodiments.

[0007] [Figure 4] 1 illustrates an example of a configured grant (CG) PUSCH configuration for operation mode A, according to various embodiments.

[0008] [Diagram 5] 1 illustrates examples of separate PUCCH parameters for two modes of operation, according to various embodiments.

[0009] [Figure 6] 4 illustrates a schematic example of a PUCCH and a PUSCH in normal symbols in an operating mode A according to various embodiments.

[0010] [Figure 7] 1 illustrates an exemplary network, in accordance with various embodiments.

[0011] [Figure 8] 8 illustrates an exemplary wireless network 800, in accordance with various embodiments.

[0012] [Figure 9] FIG. 1 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments.

[0013] [Figure 10] 4 illustrates an alternative exemplary network, according to various embodiments. [Figure 11] 1 illustrates an exemplary procedure for practicing various embodiments discussed herein.

[0014] [Figure 12] 1 illustrates another exemplary procedure for practicing various embodiments discussed herein.

[0015] [Figure 13] 1 illustrates another exemplary procedure for practicing various embodiments discussed herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The following detailed description refers to the accompanying drawings. The same reference numbers may be used to identify the same or similar elements in different drawings. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0017] Multiple operating modes for DL ​​or UL transmission in duplex operation Time Division Duplex (TDD) may be used in commercial New Radio (NR) deployments, where time domain resources are divided between downlink (also referred to as "DL") and uplink (also referred to as "UL") symbols. Allocating a limited duration for the uplink in TDD may result in reduced coverage and increased latency for a given target data rate. To improve performance for uplink transmission in TDD systems, simultaneous transmission and reception of the downlink and uplink, respectively, may be used, also referred to as "full duplex communication." One such technique for full duplex communication may be non-overlapping sub-band full duplex (NOSB-FD).

[0018] For NOSB-FD, within a carrier bandwidth, some bandwidth may be allocated as UL (referred to herein as “UL SB”), while some bandwidth may be allocated as DL (referred to herein as “DL SB”) within the same symbol. However, the UL SB and DL SB may be non-overlapping in the frequency domain. Under this mode of operation, in a given symbol, a base station such as a gNB may simultaneously transmit DL signals and receive UL signals, while a mobile device such as a UE may only transmit or receive during that symbol.

[0019] FIG. 1 illustrates an example of a non-overlapping subband full-duplex (NOSB-FD) for an NR system. In the figure, in a NOSB-FD symbol (which may be referred to as a "full-duplex (FD) symbol" for brevity), a portion of the carrier bandwidth is allocated for DL, while the remaining portion of the carrier bandwidth is allocated for UL. The other symbols may be referred to as "normal symbols" in this disclosure. A normal symbol may be used for DL ​​transmission only or for UL transmission only. A normal symbol may be a DL or UL symbol that is semi-statically configured by higher layer signaling, e.g., by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. A normal symbol may be a DL or UL symbol that is dynamically indicated by DCI format 2_0 (slot format indicator). Furthermore, a normal symbol may be a flexible symbol (which may also be referred to as an "F" symbol) that is configured by higher layer signaling or indicated by DCI format 2_0 if it is not configured or indicated as a NOSB-FD symbol.

[0020] Embodiments herein relate to systems and / or methods of multiple operating modes for DL ​​or UL transmission in dual operation. In particular, the embodiments may include or relate to one or more of the following: Operation mode decision for DL ​​or UL transmission Flexible operation modes for DL ​​or UL transmission Explicitly configured / indicated operation mode for DL ​​or UL transmission. The available DL or UL frequency resources and corresponding interference levels in NOSB-FD symbols may be different from normal symbols. Accordingly, the preferred DL and / or UL transmission parameters may be different in NOSB-FD symbols or normal symbols.

[0021] In one embodiment, the transmission parameters in the configuration of DL or UL transmission may be or may include one or more of the following: - DL or UL bandwidth part (BWP) - Frequency domain resource information - Modulation and coding scheme (MCS) table - transform precoding (i.e., information about discrete fourier transform-spread-orthogonal frequency division multiplex (DFT-s-OFDM) or other orthogonal frequency division multiplex (OFDM) waveforms); - Power control parameters - rate matching pattern for physical downlink shared channel (PDSCH) - Invalid symbol patterns for the Physical Uplink Shared Channel (PUSCH) - Spatial information - Transmit power scaling for DL ​​signal and channel relative to a reference; this may also be expressed as the relative difference in DL transmit power spectral density (PSD) in normal (DL or F) symbols and NOSB-FD symbols. In one example, different values ​​of powerControlOffset and powerControlOffsetSS may be provided for Non-Zero-Power channel state information-reference signal (NZP CSI-RS) resource configuration for normal and NOSB-FD symbols.

[0022] Throughout this disclosure, different operation modes for DL ​​or UL transmissions are introduced to distinguish between behaviors within the NOSB-FD symbol and / or normal symbols. In some embodiments, such behaviors based on different operation modes may be applied every time the NOSB-FD symbol is configured. In other embodiments, the behaviors may be applied only if the configured UL PRB in the NOSB-FD symbol is different from the UL BWP. Furthermore, if the configuration of the NOSB-FD symbol may be different in different slots or different groups of slots, the applicability of the behaviors may vary from slot to slot or group to group of slots.

[0023] In an embodiment, the UE may be configured to expect that any UL transmission that falls within the intersection of a PRB of an active UL BWP in a UL symbol and a PRB in a UL subband in a NOSB-FD symbol (i.e., a UL PRB) may be transmitted across one or more of normal (UL or F symbols) and NOSB-FD symbols, while for any other UL transmission that may fall only within an active UL BWP or only within a UL PRB in a NOSB-FD symbol, the transmission may not span a mix of normal and NOSB-FD symbols. As used herein, a "transmission" may include multiple repetitions of a single channel or signal. Alternatively, a "transmission" may be only one repetition of a single channel or signal.

[0024] In an embodiment, operating mode A is for transmission within NOSB-FD symbols, while operating mode B is for transmission within normal symbols. Equivalently, without explicitly introducing the concept of "operating mode", the above operations may be directly determined by the occupied NOSB-FD symbols and / or normal symbols, or the above operations may refer to different sets of transmission parameters. In the remainder of this disclosure, references to "operating modes A / B / C" are made for brevity, but are intended to include examples of cases where a dual "operating mode" definition may be implicit.

[0025] In an embodiment, different operating modes are explicitly defined or implicitly determined only for UL transmissions, while reception of DL transmissions is transparent regardless of whether the DL channel / signal is received in a normal (DL or F) symbol or a NOSB-FD symbol.

[0026] A mechanism for determining an operation mode for DL ​​or UL transmission. The operation mode for DL ​​or UL transmission may be determined based on a time unit that includes an assigned symbol of DL or UL transmission. In other words, the same operation mode is applied to DL or UL transmission in a time unit. The time unit may include all symbols in a slot, PUCCH slot, or multiple slots used by DL or UL transmission. Alternatively, the time unit may include exactly the assigned symbols of DL or UL transmission in a slot, PUCCH slot, or multiple slots used by DL or UL transmission. That is, the operation mode for DL ​​or UL transmission may be determined based on the assigned symbols of DL or UL transmission.

[0027] For example, in the case of a PDSCH or PUSCH, a time unit may simply include the assigned symbols as indicated by a time domain resource allocation (TDRA) information field in the downlink control information (DCI) or configured by higher layer signaling.

[0028] For example, in the case of CSI-RS transmission, a time unit may include multiple consecutive or non-consecutive symbols consisting of CSI-RS in a CSI-RS resource set.

[0029] For example, in case of DMRS bundling for multi-slot PUSCH including PUSCH repetition type A / B and transport block processing over multiple slots (TBoMS) and PUCCH repetition, a time unit may include an assigned symbol within a nominal or actual time domain window, in which case the UE is required to maintain phase continuity and power consistency within the nominal or actual time domain window.

[0030] For example, for PDSCH, PUSCH, PUCCH, if configured or indicated with repetitions, a time unit may include transmission opportunities for assigned symbols or multiple repetitions. Alternatively, a time unit may include single or multiple multiple repetitions of DL or UL transmission, where the multiple repetitions may carry the same TB or UCI.

[0031] For example, for CSI-RS or SRS, if configured or indicated with repetitions, a time unit may include an assigned symbol or transmission opportunity for multiple repetitions. Alternatively, a time unit may include a single or multiple multiple repetitions.

[0032] For example, for TBoMS, a time unit may include an assigned symbol of a slot assigned for TBoMS transmission, with or without repetition. Alternatively, for TBoMS, a time unit may include a single repetition of a TB spanning multiple slots, or multiple repetitions of a TB spanning multiple slots.

[0033] In an embodiment, if at least one symbol of a time unit is a NOSB-FD symbol, the UE uses operation mode A in that time unit, otherwise, the UE uses operation mode B in that time unit.

[0034] 2 shows an example regarding operation modes for PUCCH resources. Since PUCCH resource 1 occupies only NOSB-FD symbols, PUCCH resource 1 is associated with operation mode A. Since PUCCH resource 2 occupies only normal symbols, PUCCH resource 2 is associated with operation mode B. Furthermore, since PUCCH resource 3 includes both NOSB-FD and non-NOSB symbols, PUCCH resource 3 is associated with operation mode A.

[0035] In another embodiment, for a given time unit, the mode of operation for that time unit may be determined based on whether the first symbol of that time unit is a NOSB-FD symbol or a normal (DL / UL / FL) symbol. Similarly, for DL / UL transmissions with repetitions, the mode of operation for a time unit that spans multiple repetitions may be determined based on whether the first symbol of the first repetition in that time unit is a NOSB-FD symbol or a normal (DL / UL / FL) symbol.

[0036] In another embodiment, if all symbols in a time unit are NOSB-FD symbols, the UE may use operating mode A in that time unit. On the other hand, if all symbols in a time unit are normal symbols, the UE may use operating mode B in that time unit. The UE may not be configured to expect a time unit to contain both NOSB-FD and normal symbols. In this option, in FIG. 2, PUCCH resource 1 is valid and associated with operating mode A. PUCCH resource 2 is valid and associated with operating mode B. However, PUCCH resource 3 is invalid because it contains both NOSB-FD and non-NOSB symbols.

[0037] In another embodiment, if all symbols of a time unit are NOSB-FD symbols, the UE uses operating mode A in that time unit; if all symbols of the time unit are normal symbols, the UE uses operating mode B in that time unit. Furthermore, if some symbols of a time unit are NOSB-FD symbols while the remaining symbols of the time unit are normal symbols, the UE uses operating mode C in that time unit. For transmission parameters of operating mode C, the gNB may configure different values ​​than operating mode A and / or operating mode B for DL ​​or UL transmissions mapped to time units with both NOSB-FD and normal symbols.

[0038] In another embodiment, if any symbol in a time unit is a normal symbol, the UE may use operating mode B in that time unit, otherwise the UE uses operating mode A in that time unit.

[0039] Implicit Operational Modes in DL or UL Transmission Configuration In DL or UL transmission configuration, the UE may be configured with transmission parameters associated with one or more operating modes (e.g., operating modes A, B, C, etc.). The operating mode for DL ​​or UL transmission may be determined based on a time unit that includes an assigned symbol of the DL or UL transmission. The UE may then perform DL or UL transmission using the transmission parameters of the determined operating mode.

[0040] In one example, in case of dynamic PDSCH / PUSCH scheduling, the relevant configuration of transmission parameters of one or more operation modes may be provided by a higher layer, for example in a PDSCH-Config or PUSCH-Config. In another example, in case of SPS or CG PUSCH configuration, the relevant configuration of transmission parameters of one or more operation modes may be provided by a higher layer, for example in an SPS-Config or ConfiguredGrantConfig. In another example, in case of PUCCH configuration, the relevant configuration of transmission parameters of one or more operation modes may be provided by a higher layer, for example in a PUCCH-Config.

[0041] In one embodiment, DL or UL transmissions in different time units may be associated with the same or different operation modes, and the UE may perform DL or UL transmissions in a time unit according to corresponding parameters of the operation mode.

[0042] FIG. 3 shows an example of resource allocation for PUSCH repetition type A. For the purposes of discussion herein, it is assumed that two repetitions are configured or indicated for the PUSCH. The first PUSCH repetition 301 is in a NOSB-FD symbol, so it is associated with operation mode A. The second PUSCH repetition 302 is in a non-NOSB-FD symbol, so it is associated with operation mode B. Both repetitions are valid for transmission. These two repetitions may use different parameters, e.g., different UL power control for PUSCH Rep#1 and Rep#2.

[0043] In another embodiment, for DL ​​or UL transmission, the operation mode is determined over multiple time units of DL or UL transmission. For example, for CSI-RS transmission, the time unit may include only symbols of CSI-RS resources, and then multiple time units are associated with CSI-RS resources in the CSI-RS resource set. For DMRS bundling, the time unit may include only symbols of PUSCH in a slot or repetition, and then multiple time units are associated with PUSCH for DMRS bundling in a nominal or actual time domain window where the UE is required to maintain phase continuity and power consistency. For PDSCH, PUSCH, CSI-RS, or SRS including TBoMS, if configured or indicated with repetition, the multiple time units include all repetitions if the time unit includes only assigned symbols of the repetition. Multiple time units may carry the same TB or UCI. In this embodiment, transmit power control (TPC) commands in the DCI are applied to power control over multiple time units in the determined operation mode.

[0044] In one option, for DL ​​or UL transmission, the UE may expect that DL or UL transmission in multiple time units must use the same operation mode. As a result, the UE performs DL or UL transmission in multiple time units according to a corresponding set of parameters of the operation mode. In this embodiment, in FIG. 3, PUSCH repetitions #1 301 and #2 302 are not valid resources for PUSCH repetition type A.

[0045] In another option, for DL ​​or UL transmission, an operation mode may be determined based on a first time unit of the multiple time units. Then, the UE may perform DL or UL transmission in the same operation mode in any of the multiple time units. The UE may drop a time unit if the DL or UL transmission is not associated with the same operation mode. Specifically, for a PUCCH with repetition, the time resources of other PUCCH repetitions are determined by the first PUCCH repetition. In this embodiment, in FIG. 3, PUSCH repetition #2 302 is not valid for PUSCH transmission because it is associated with a different operation mode. PUSCH repetition #2 302 may be dropped.

[0046] In another option, an operation mode may be determined for DL ​​or UL transmission based on a first time unit of the multiple time units. The UE may then perform DL or UL transmission according to the same operation mode in all the multiple time units, regardless of the operation mode determined in the time unit. In this embodiment, in FIG. 3, PUSCH repetition #2 302 is not valid for PUSCH transmission because it is associated with a different operation mode. However, PUSCH repetition #2 302 is transmitted in the operation mode of PUSCH repetition #1 301.

[0047] In another option, for DL ​​or UL transmission with repetitions, e.g., PUSCH repetition type A with count based on available slots, or TBoMS, or PUCCH repetitions, the operation mode may be determined based on a first time unit of a number of time units. Then, if the assigned symbols in a slot are associated with a different operation mode, the slot is not considered an available slot. The DL or UL transmission may be delayed until the next available slot. In this embodiment, in FIG. 3, PUSCH repetition #2 302 is not valid for PUSCH transmission because it is associated with a different operation mode. The slot of PUSCH repetition #2 302 is not considered an available slot, and therefore PUSCH repetition #2 may be delayed until the next available slot 303.

[0048] In an embodiment, for DL ​​or UL transmission, the UE may expect that every time unit of DL or UL transmission must use the same mode of operation, so that the UE may perform DL or UL transmission with a corresponding set of parameters of the mode of operation.

[0049] In an embodiment, for a UL / DL channel / signal with repetition, the UE may follow a single operating mode for all repetitions regardless of the actual mapping to normal symbols or symbols with NOSB-FD symbols, in which case the operating mode to be used is determined based on one or more of: (1) the operating mode applicable for the first symbol or first time unit; (2) as configured via higher layers or dynamically indicated by the gNB; (3) as determined based on a rule specified for determining the single operating mode.

[0050] As an example of the final decision method, the UE may be configured to use operating mode A if any NOSB-FD symbol is included in the set of repetitions, etc.

[0051] Explicitly configured or indicated operation modes for DL ​​or UL transmission For DL ​​or UL transmission, the first operation mode may be configured by higher layers or may be dynamically indicated by DCI. On the other hand, the second operation mode may be determined based on the time unit with the assigned symbols of DL or UL transmission. Based on the first and second operation modes for DL ​​or UL transmission, certain restrictions may apply.

[0052] In an embodiment, in the configuration of DL or UL transmission, the UE may be configured with corresponding parameters associated with the operation mode. The operation modes for different configurations of DL or UL transmission may be the same or different. For a semi-statically configured DL or UL transmission, the UE may receive or transmit in the configured time resource according to the operation mode configured in the configuration of DL or UL transmission.

[0053] In one example, in the configuration of a configuration grant (CG) PUSCH configuration, PUCCH configuration, sounding reference signal (SRS) resource configuration, PDCCH configuration, semi-persistent scheduling (SPS) PDSCH configuration, CSI-RS resource configuration, or CSI report configuration, associated operation modes may be configured together. A gNB may configure two separate PUCCH-Configs, where each PUCCH-Config may be associated with one operation mode. A gNB may configure multiple ConfiguredGrantConfigs, where each ConfiguredGrantConfig is associated with one operation mode. A gNB may configure multiple Search Space (SS) sets and / or CORESETs, where each SS set and / or CORESET may be associated with one operation mode.

[0054] The operating modes for different DL or UL transmissions can be configured separately.

[0055] For different UL / DL transmissions, different mechanisms for determining the operation mode may be applied. For example, the gNB may configure separate PUCCH or CG PUSCH resources for the two operation modes, while the gNB configures only a single SRS resource for both NOSB-FD and normal operation. For another example, for PUCCH resource determination, the operation mode for UL / DL transmissions in a slot may be determined by the symbol type in that slot / subslot, while for PUSCH resource determination, the operation mode for symbols l1 to l2 may be determined by the symbol type in that slot / subslot. n The operating mode for UL / DL transmission from the n The symbol type is determined by the

[0056] A set of transmission parameters may be configured and commonly applied to multiple configurations of DL or UL transmission in different operation modes. If a transmission parameter is not configured in a DL or UL transmission configuration, the parameter may be applied for the DL or UL transmission configuration in a default operation mode. For example, the default operation mode may be operation mode B. Alternatively, the parameter may be applicable for all configurations of DL or UL transmission in any operation mode, for example, applicable to both operation modes A and B. Alternatively, if the same parameter is not configured, the parameter is applied for the DL or UL transmission configuration. Alternatively, if a parameter is commonly configured and if the same parameter is also configured in a DL or UL transmission configuration, the UE may follow the dedicated configuration value of the parameter for the DL or UL transmission configuration.

[0057] In an embodiment, the gNB may explicitly indicate the operating mode in the DCI for scheduling DL or UL transmission.

[0058] In one option, when multiple configurations of DL or UL transmission are configured in different operation modes, the UE may receive or transmit in scheduled time resources according to the configuration in the operation mode indicated by the DCI. For example, the gNB may configure two frequency regions for FDRA for dynamically scheduled PUSCH or PDSCH, e.g., one frequency region is an active BWP and the other is within a configured PRB, and each FDRA is associated with one operation mode. The gNB indicates the operation mode in the scheduling DCI, and the UE interprets the FDRA for the scheduled PDSCH / PUSCH in the corresponding frequency region.

[0059] In another option, if the configuration of DL or UL transmission can be configured by transmission parameters with one or more operation modes, the UE may perform DL or UL transmission according to the parameters of the operation mode indicated by the DCI.

[0060] In the above options, the DCI format for DL ​​assignment or uplink grant may include one bit to indicate the operation mode. It is noted that the DCI format may include DCI format 0_1, 0_2 or 1_0, 1_2. For fallback DCI formats, i.e. DCI format 0_0 or 1_0, no explicit indication of the operation mode is included. Alternatively, the indicated operation mode may be determined by an existing field in the DCI. For example, based on the value of the PDSCH-to-HARQ_feedback timing indicator field, i.e. K1, the UE now determines the UL slot or PUCCH slot for HARQ-ACK transmission. The operation mode for HARQ-ACK transmission may be determined by the UL slot or PUCCH slot. Accordingly, the TPC command in the DCI is applied to power control for HARQ-ACK transmission in the indicated operation mode.

[0061] In an embodiment, for DL ​​or UL transmission in a configured or indicated mode of operation, the UE may expect that the configured or indicated mode of operation is consistent with the determined mode of operation in any time unit that includes an assigned symbol of DL or UL transmission.

[0062] In an embodiment, for DL ​​or UL transmission in a configured or indicated operating mode, if a different operating mode is determined for a time unit of DL or UL transmission, the UE may drop the DL or UL transmission for that time unit, or may drop the entire DL or UL transmission.

[0063] For example, if a gNB configures two CG PUSCH configurations for a UE, CG PUSCH configuration 1 is associated with operating mode A and CG PUSCH configuration 2 is associated with operating mode B. If CG PUSCH configuration 2 is configured on a set of symbols that belong to operating mode A, the UE may drop CG PUSCH configuration 2 on that set of symbols. Alternatively, the UE may drop any transmission of CG PUSCH configuration 2.

[0064] 4 shows an example for a CG PUSCH configuration in operating mode A. For purposes of discussion herein, the number of repetitions may be assumed to be two. The first CG PUSCH resource 401 is within a NOSB-FD symbol, so it is associated with operating mode A. The second CG PUSCH resource 402 is within a normal symbol, so it is not associated with operating mode A. The second CG PUSCH resource 402 is not valid and may be dropped.

[0065] In an embodiment, for DL ​​or UL transmission in a configured or indicated mode of operation, if the DL or UL transmission is configured with repetitions, e.g. PUSCH repetition type A with count based on available slots, or TBoMS, or PUCCH repetitions, if a different mode of operation is determined within a slot of DL or UL transmission, the slot is not considered an available slot. The DL or UL transmission may be delayed until the next available slot. In this option, in FIG. 4, since the second CG PUSCH resource 402 in slot 2 is not associated with mode of operation A, slot 2 is not considered an available slot, and therefore the second CG PUSCH resource may be delayed until the next available slot 403 or dropped.

[0066] In an embodiment, for DL ​​or UL transmission in a configured or indicated operation mode, if different operation modes are determined within a slot of DL or UL transmission, different solutions may be applied depending on the configured or indicated operation mode. For one configured or indicated operation mode, e.g., operation mode A, the UE may still receive or transmit DL or UL transmission. That is, the UE may ignore the difference in operation mode. On the other hand, for another configured or indicated operation mode, e.g., operation mode B, the UE may drop DL or UL transmission within the slot, or may drop DL or UL transmission within any slot. Alternatively, the slot is not considered as an available slot.

[0067] In an embodiment, for a DL or UL transmission in a configured or indicated operating mode, the UE may receive or transmit the DL or UL transmission based on the configured or indicated operating mode, regardless of the operating mode determined in the time unit of the DL or UL transmission.

[0068] In addition to the above, embodiments herein relate to apparatus, systems, and methods for UCI transmission and reception in dual operation. For example, aspects of various embodiments may include or relate to one or more of the following: UCI multiplexing / prioritization for PUCCH considering operation mode UCI multiplexing / prioritization for PUCCH and PUSCH considering operation mode PUCCH repetition considering operation mode SPS hybrid automatic repeat request-acknowledgement (HARQ-ACK) deferral. The available DL or UL frequency resources and corresponding interference levels in NOSB-FD symbols may be different from normal symbols. Accordingly, the preferred UCI transmission parameters may be different in NOSB-FD symbols or normal symbols.

[0069] The UCI transmission parameters may include one or more of the following: - PUCCH parameters including one or more of the following: o Frequency domain resource information, e.g. starting physical resource block (PRB) and number of PRBs. Frequency hopping o Time domain resource information, e.g. starting symbol and duration, slot or sub-slot based PUCCH resources. PUCCH format o π / 2-binary phase shift keying (BPSK) o Power control parameters Spatial information maxCodeRate o maxPayloadSize for each PUCCH resource set o Number of iterations o Orthogonal cover code (OCC) parameters o UCI on PUSCH parameters betaOffsets o Scaling factor. As in the previous section, different operation modes for UCI transmission may be used herein to distinguish UCI transmission behavior for NOSB-FD symbols and / or normal symbols. Operation mode A may be used herein to refer to transmission in NOSB-FD symbols, while operation mode B may be used herein to refer to transmission in normal symbols. Equivalently, without explicitly introducing the concept of "operation mode", the above operations may be determined by the occupied NOSB-FD symbols and / or normal symbols, or the above operations may refer to different sets of transmission parameters. In the remainder of this disclosure, references to "operation modes A / B / C" are made for brevity, but are intended to include examples of cases where a dual "operation mode" definition may be implicit.

[0070] Furthermore, in some instances, a single mode of operation may be applicable to both NOSB-FD symbols and normal symbols.

[0071] Separate UCI transmission parameters associated with different operation modes In one embodiment, separate configurations of PUCCH resources or PUCCH resource sets may be configured in different operation modes. In one option, the gNB may configure separate PUCCH resources, each PUCCH resource associated with one operation, e.g., the gNB configures separate PUCCH-Configs, each PUCCH-Config associated with one operation mode. In one example, for PUCCH resources for a CSI report PUCCH-CSI-Resource, the gNB may configure two PUCCH-CSI-Resources, each PUCCH-CSI-Resource associated with one operation mode. Alternatively, for PUCCH resources for a CSI report PUCCH-CSI-Resource, the gNB may configure two pucch-Resources, each pucch-Resource associated with one operation mode. In one example, for a PUCCH resource for an SR in SchedulingRequestResourceConfig, the gNB may configure two Resources, each Resource associated with one operation mode. In another option, the gNB configures multiple sets of parameters for one PUCCH resource, for example in one PUCCH-Config, the set of parameters including at least one of the PUCCH parameters listed above.

[0072] When a UE is configured with multiple priorities, in one example, the PUCCH-Config for a priority is associated with one mode of operation. In another example, multiple PUCCH-Configs may be configured for a priority, with each PUCCH-Config associated with a mode of operation. Alternatively, a PUCCH-Config may be configured for a priority, with the PUCCH-Config for a priority being associated with multiple modes of operation.

[0073] For both options, in one example, for a PUCCH resource with an index, the same time domain resource information may be applied to all PUCCH resources with the same index in all operation modes, or the UE does not expect different time domain resource information for different operation modes. In another example, the time domain resource information may be configured separately for different option modes.

[0074] As an extension of the above options, some parameters in the PUCCH-Config may be commonly applied to the configurations for different operation modes. The remaining parameters may be configured separately for different operation modes. In one embodiment, separate configurations of UCI on PUSCH may be configured in different operation modes. In one option, the gNB configures separate UCI-on-PUSCHs, each UCI-on-PUSCH associated with one operation mode. In another option, the gNB configures two sets of parameters in one UCI-on-PUSCH. The sets of parameters include at least one of the PUSCH parameters provided above.

[0075] Determination of UCI transmission parameters according to operation mode In one embodiment, for PUCCH, in one option the operation mode for UCI transmission over PUCCH is indicated by the gNB, e.g. by a DL allocation scheduling PDSCH on HARQ-ACK PUCCH, or configured by the gNB as part of a semi-static PUCCH configuration, e.g. for P / SP-CSI / SR / SPS HARQ-ACK PUCCH.

[0076] In another option, the operation mode for UCI transmission over PUCCH is determined by the operation mode associated with the time unit in which the PUCCH resource is located.

[0077] A time unit may include all symbols in a slot, all symbols in a PUCCH slot (slot or subslot), or multiple slots / PUCCH slots used by a PUCCH transmission. Alternatively, a time unit may include exactly the assigned symbols of a PUCCH transmission in one slot or multiple slots.

[0078] To determine the operation mode associated with a time unit, in one option, if at least one symbol of the time unit is a NOSB-FD symbol, operation mode A is associated with the time unit. Otherwise, operation mode B is associated with the time unit. In another option, for a given time unit, the operation mode associated with the time unit may be determined based on the first symbol of the time unit being a NOSB-FD symbol or a normal (DL / UL / FL) symbol. Similarly, in case of UL transmission with repetitions, the operation mode associated with a time unit that spans multiple repetitions may be determined based on the first symbol of the first repetition in the time unit being a NOSB-FD symbol or a normal (DL / UL / FL) symbol. In another option, if all symbols of a time unit are NOSB-FD symbols, operation mode A is associated with the time unit. On the other hand, if all symbols of a time unit are normal symbols, operation mode B is associated with the time unit. The UE does not expect a time unit to include both NOSB-FD and normal symbols. In another alternative, if all symbols in a time unit are NOSB-FD symbols, then operating mode A is associated with the time unit; if all symbols in a time unit are normal symbols, then operating mode B is associated with the time unit. Furthermore, if some symbols in a time unit are NOSB-FD symbols while the remaining symbols in the time unit are normal symbols, then a third mode, e.g., operating mode C, may be associated with the time unit. In another alternative, if any symbols in a time unit are normal symbols, then operating mode B is associated with the time unit. Otherwise, operating mode A is associated with the time unit.

[0079] 5 shows an example with separate UCI transmission parameters for PUCCHs associated with two operation modes. For HARQ-ACK feedback in slots 1 or 3 (e.g., for PUCCH1 501, PUCCH2 502, PUCCH1 503, and PUCCH2 504), the PUCCH parameters associated with operation mode A are applied since NOSB-FD symbols are present there. On the other hand, for HARQ-ACK feedback in slot 2 (e.g., for PUCCH1 506 and PUCCH2 505), the PUCCH parameters associated with operation mode B are applied.

[0080] In one embodiment, for UCI on PUSCH, in one option, the operation mode for UCI transmission on PUSCH may be indicated by the gNB, e.g., by an UL grant for scheduling PUSCH and / or a DL assignment for scheduling PDSCH in HARQ-ACK PUCCH, or may be configured by the gNB as part of the CG PUSCH configuration and / or as part of the PUCCH configuration. In one example, the UE may not be configured to expect that the operation modes indicated for PUSCH and PUCCH are different. In another example, the UE uses the operation mode indicated for PUSCH. In another option, the operation mode for UCI transmission on PUSCH is determined by the operation mode associated with the time unit in which the PUSCH resource is located.

[0081] A time unit may include all symbols in a slot or slots used by a PUSCH transmission. Alternatively, a time unit may include exactly the assigned symbols of a PUSCH transmission in a slot or slots. The mechanism for determining the operation mode associated with a time unit for PUSCH is similar to that for PUCCH provided above.

[0082] For both above embodiments, in one option, for UCI transmission parameters associated with a certain operation mode, the UE does not expect the PUCCH / PUSCH carrying UCI to be not restricted within symbols (NOSB-FD or normal symbols) for the corresponding operation mode. For example, if a PUCCH resource indicated for normal operation is selected, the UE does not expect any symbols in that PUCCH resource to be within NOSB-FD symbols. Typically, at least PUCCH / PUSCH dynamically scheduled by the gNB may reserve the indicated PUCCH / PUSCH resource restricted within symbols for the corresponding operation mode. For configured PUCCH / PUSCH resources, e.g., for SR / P / SP-CSI / SPS HARQ-ACK or CG PUSCH, the gNB may also reserve PUCCH / PUSCH resources restricted within symbols for the corresponding operation mode. Alternatively, the PUCCH / PUSCH resources may not be restricted within symbols for the corresponding operation mode. The UE considers such PUCCH / PUSCH resources as invalid PUCCH / PUSCH resources. In FIG. 5, PUCCH resource 2 504 in slot 3 overlaps with normal symbols and NOSB-FD symbols, and therefore PUCCH resource 2 504 in slot 3 is invalid.

[0083] In another option, for UCI transmission parameters associated with a certain operation mode, the PUCCH / PUSCH carrying UCI may overlap with both NOSB-FD symbols and normal symbols. With this option, the PUCCH resource associated with operation mode A in Figure 5 is not limited to only using NOSB-FD symbols. Thus, all PUCCH resources shown in Figure 5, including PUCCH resource 2 504, are valid configurations.

[0084] In another option, for UCI transmission parameters associated with operation mode A, the UE does not expect the PUCCH / PUSCH carrying UCI to be confined within UL SBs or to overlap with DL SBs within NOSB-FD symbols. In this option, any of the PUCCH resources 501-504 in FIG. 5 may be considered as a valid PUCCH resource.

[0085] In another option, for UCI transmission parameters associated with a certain operation mode, if the PUCCH / PUSCH carrying UCI is not consistent with the operation mode determined by the symbols of the PUCCH / PUSCH resource, the UE may cancel or delay the PUCCH / PUSCH repetition, or may perform rate matching or transmitter side puncturing by not mapping some of the generated symbols to the time-frequency resources for the PUCCH / PUSCH resource to ensure that the transmitted PUCCH / PUSCH repetition is within the corresponding symbol. Alternatively, the UE determines the UCI transmission parameters for the PUCCH / PUSCH carrying UCI according to the operation mode determined by the symbols of the PUCCH / PUSCH resource.

[0086] In another option, for UCI transmission parameters associated with operating mode A, if a PUCCH / PUSCH resource is not constrained within a UL SB or overlaps with a DL SB in a NOSB-FD symbol, the UE may drop or delay the PUCCH / PUSCH, or may perform rate matching or transmitter side puncturing on the PUCCH / PUSCH resource to ensure that the transmitted PUCCH / PUSCH is within the corresponding UL SB.

[0087] Determining UCI Transmission Parameters for Multiple UCI with Same or Different Priorities A UE may be configured with multiple PUCCHs for different UCI types, e.g., a PUCCH for HARQ-ACK, a PUCCH for CSI, a PUCCH for SR, etc. Furthermore, a UE may be configured with multiple PUCCH configurations for different priorities, e.g., one PUCCH configuration for low priority (LP, priority index 0) for eMBB traffic and one PUCCH configuration for high priority (HP, priority index 1) for URLLC traffic.

[0088] For a single priority, the UE may perform UCI multiplexing for PUCCH (element A) first, and if any PUSCH overlaps with PUCCH, perform UCI multiplexing on PUSCH (element B). If the UE is configured with multiple PUCCH configurations for different priorities, e.g., one PUCCH configuration for LP and one PUCCH configuration for HP, and the UE is configured with UCI multiplexing for different priorities (e.g., as defined in Rel-17 for UCI multiplexing for different priorities), the UE may perform UCI multiplexing for PUCCH (element 1-A) first, then UCI multiplexing on PUSCH (element 1-B) within the same priority, and then the UE performs UCI multiplexing / prioritization for PUCCH (element 2-A) and PUCCH / PUSCH (element 2-B) between different priorities. Alternatively, the UE may first perform UCI multiplexing for PUCCH (element 1-A) and then UCI multiplexing on PUSCH (element 1-B) for LP, and then the UE performs UCI prioritization for different priorities (element 2'-X) before or after UCI multiplexing for PUCCH (element 2'-A) and PUSCH (element 2'-B) for HP, e.g., as defined in Rel-16.

[0089] It should be noted that if there is no PUSCH overlapping with the PUCCH, the UE may not actually perform Element B / Element 1-B / Element 2-B / Element 2'-B, but for the sake of completeness, the inventors still include Element B / Element 1-B / Element 2-B / Element 2'-B as one element of the UCI multiplexing / prioritization procedure.

[0090] As another example, the UE may not be configured with multiple PUCCH transmission parameters for different operation modes, in such a case, the UE may first perform UCI multiplexing based on existing procedures and then check for any collisions between the resulting PUCCH or PUSCH resources and DL symbols or DL ​​subbands (if configured) or resources outside the UL subbands in the NOSB-FD symbols after the UCI multiplexing procedure, e.g., after element B for the single priority case or after element 2-B or element 2'-B for the multiple priority case. Alternatively, the UE checks for collisions between the PUCCH or PUSCH resources and DL symbols or DL ​​subbands before or after the UCI multiplexing procedure.

[0091] In the event that the gNB configures multiple UCI transmission parameters for different operation modes, in the following the multiplexing procedure, the operation mode decision for the UCI transmission parameters on the PUCCH, and the check for any collision between the PUCCH and resources outside the UL subband in the DL symbol or DL ​​subband (if configured) or in the NOSB-FD symbol are provided.

[0092] In a first embodiment, the operation mode for UCI transmission parameters, e.g., PUCCH transmission parameters, is determined separately for each PUCCH. Within a PUCCH slot, the UE performs UCI multiplexing / prioritization for PUCCHs regardless of the operation mode. For a group of overlapped PUCCHs, PUCCHs with different operation modes can be multiplexed or dropped according to a predefined rule. In one option, whether to drop or multiplex a PUCCH is determined according to a UCI type or priority as in Rel-15 / 16 / 17 regardless of the operation mode. In another option, whether to drop or multiplex a PUCCH is determined according to a UCI type or priority (e.g., low priority (LP) / high priority (HP)) or an operation mode. For example, a PUCCH with a specific operation mode is dropped before multiplexing. The specific operation mode is predefined or configured by the gNB.

[0093] For the case of LP and HP UCI multiplexing, when the UE performs UCI multiplexing within the same priority (element A, or element 1-A, or element 2'-A), for a group of overlapped PUCCHs, if the PUCCHs have different operation modes, the PUCCHs with different operation modes may be multiplexed or dropped according to a predefined rule. When the UE performs UCI multiplexing with different priority (element 2-A), for a group of overlapped PUCCHs, if the PUCCHs have different operation modes, the PUCCHs with different operation modes may be multiplexed or dropped according to a predefined rule, for example, LP PUCCH is dropped before multiplexing. The operation mode for the resulting PUCCH for UCI multiplexing is determined according to one or more of the following: (1) The resulting operation mode for the PUCCH may be configured by higher layer signaling (e.g., RRC, MAC-CE, etc.).

[0094] In one example, the operation mode for the resulting PUCCH for UCI multiplexing for the same priority may be configured separately for each priority. In another example, the operation mode for the resulting PUCCH for UCI multiplexing for the same priority and different priorities may be configured separately. (2) If at least one of the overlapped PUCCHs is associated with a particular operation mode, the resulting PUCCH is associated with the particular operation mode, the particular operation mode being predefined or configured by the gNB.

[0095] In one example, the specific operating mode for each priority may be configured separately.

[0096] In another example, the specific operation modes for UCI multiplexing for same priority and different priority may be configured separately. (3) The operation mode for the resulting PUCCH is determined by the operation mode associated with the time unit in which the resulting PUCCH resource is located. (4) If the resulting PUCCH is a PUCCH resource for a particular UCI type, the resulting PUCCH is associated with an operation mode associated with the PUCCH resource for that particular UCI type.

[0097] For example, if at least one of the overlapped PUCCHs is a HARQ-ACK PUCCH for a dynamic PDSCH, the resulting PUCCH is a PUCCH resource for the HARQ-ACK for the dynamic PDSCH. Then, the operation mode for the resulting PUCCH is the same as the operation mode for the HARQ-ACK PUCCH for the dynamic PDSCH. (5) If the resulting PUCCH is for UCI multiplexing between priorities (element 2-A), the resulting PUCCH is associated with an operating mode associated with PUCCH resources for a particular priority, for example, HP PUCCH. (6) If at least one of the overlapped PUCCHs is a HARQ-ACK PUCCH for a dynamic PDSCH, the resulting PUCCH is associated with the operation mode for the HARQ-ACK PUCCH for the dynamic PDSCH. (7) If at least one of the PUCCHs in a PUCCH slot is a HARQ-ACK PUCCH, the resulting PUCCH is associated with an operation mode for HARQ-ACK PUCCH.

[0098] In one option, if the operation modes for the overlapped PUCCHs are the same, the operation mode for the resulting PUCCH is the same as the PUCCH before multiplexing, otherwise at least one of (1) to (7) applies. In another option, regardless of whether the operation modes for the overlapped PUCCHs are the same or different, at least one of (1) to (7) applies.

[0099] In a second embodiment, the operation mode for UCI transmission parameters is determined separately for each PUCCH. Within a PUCCH slot, the UE performs multiplexing / prioritization between PUCCHs in each operation mode separately. When the UE performs multiplexing / prioritization within an operation mode, any resulting PUCCH is also associated with the same operation mode.

[0100] In one option, after the UE finishes multiplexing / prioritization between PUCCHs in the same operating mode, the UE does not expect a PUCCH with one operating mode to overlap with another PUCCH with another operating mode.

[0101] In another option, after the UE completes multiplexing / prioritization among PUCCHs in the same operation mode, the PUCCHs with one operation mode may overlap with another PUCCH with another operation mode. Then, the UE resolves the collision between the PUCCHs with different operation modes. In one example, when the UE resolves the collision between the PUCCHs with different operation modes, the PUCCHs with a particular operation mode are dropped. In another example, the PUCCHs with different operation modes may be multiplexed or dropped according to a predefined rule.

[0102] For the case of LP and HP UCI multiplexing, in one option, for each operation mode, the UE first performs multiplexing / prioritization among PUCCHs in the same priority, and second performs multiplexing / prioritization among PUCCHs with different priorities in the same operation mode, and then the UE does not expect any PUCCHs with different operation modes to overlap. Alternatively, if PUCCHs with different operation modes overlap, after processing for each operation mode, the UE processes PUCCHs with different operation modes. The UE first performs multiplexing / prioritization among PUCCHs in the same priority, and second performs multiplexing / prioritization among PUCCHs with different priorities for different operation modes. The operation mode for the resulting PUCCH for UCI multiplexing may be determined according to the mechanism in the first embodiment. In another option, within each priority, the UE first performs multiplexing / prioritization among PUCCHs in the same operation mode, and second performs multiplexing / prioritization among PUCCHs with different operation modes if overlap between different operation modes is allowed. And then, for different priorities, the UE first performs multiplexing / prioritization among PUCCHs in the same operating mode, and second performs multiplexing / prioritization among PUCCHs with different operating modes if overlap between different operating modes is allowed.

[0103] In a third embodiment, an operation mode for UCI transmission parameters is determined commonly for each PUCCH in a PUCCH slot. The operation mode is determined according to one or more of the following: (1) The operating mode is configured by higher layers.

[0104] If the operation modes for the PUCCHs in a PUCCH slot are different, the configured operation mode applies to all PUCCHs in that PUCCH slot. If the operation modes for all PUCCHs in a PUCCH slot are the same, the operation mode is determined by each PUCCH. (2) If at least one of the PUCCHs in a PUCCH slot is associated with a particular operating mode, then all PUCCHs in the PUCCH slot are associated with that particular operating mode.

[0105] The particular operation mode is predefined, e.g., operation mode A. Alternatively, the particular operation mode is configured by the gNB. (3) If at least one of the PUCCHs in a PUCCH slot is a HARQ-ACK PUCCH for a dynamic PDSCH, the operation mode for the HARQ-ACK PUCCH for a dynamic PDSCH applies to all PUCCHs in the PUCCH slot. (4) If at least one of the PUCCHs in a PUCCH slot is a HARQ-ACK PUCCH, the operation mode for the HARQ-ACK PUCCH applies to all PUCCHs in that PUCCH slot.

[0106] In case of HARQ-ACK PUCCH override, the operation mode for the HARQ-ACK PUCCH is determined by the indication in the final DL assignment, if applicable. Alternatively, the UE does not expect different operation modes indicated by different DL assignments for HARQ-ACK in the same PUCCH. (5) If at least one of the PUCCHs in a PUCCH slot is a HARQ-ACK PUCCH having a PUCCH resource other than n1PUCCH-AN, the operation mode for the HARQ-ACK PUCCH applies to all PUCCHs in that PUCCH slot.

[0107] If there is only a HARQ-ACK PUCCH with PUCCH resources configured by n1PUCCH-AN, and if there are CSI PUCCH resources, the operation mode for the CSI PUCCH is applied to all PUCCHs in that PUCCH slot. (6) If there are one or more PUCCH resources for CSI feedback and no HARQ-ACK PUCCH, the operation mode for the PUCCH resource with the lowest index applies to all PUCCHs in that PUCCH slot.

[0108] In this embodiment, in one option, the same operation mode is assumed for any intermediate or final resulting PUCCH after UCI multiplexing / prioritization procedure. In another option, the operation mode for any intermediate or final resulting PUCCH after UCI multiplexing / prioritization procedure may be different from the PUCCH before UCI multiplexing / prioritization. In another option, the same operation mode is assumed for any intermediate or final resulting PUCCH after UCI multiplexing / prioritization procedure for the same priority (element A, element 1-A, or element 2'-A), while any intermediate or final resulting PUCCH after UCI multiplexing / prioritization for a different priority (element 2-A) may be different from the PUCCH before UCI multiplexing / prioritization. In the case of different operation modes, in one example, some PUCCHs will be dropped before multiplexing, and in another example, the PUCCHs may be multiplexed.

[0109] In the fourth embodiment, the operation mode for UCI transmission parameters is determined commonly for each PUCCH in a PUCCH slot having the same priority (element A, element 1-A, or element 2'-A). The mechanism in the third embodiment may be applied within each priority. For configured operation modes or specific operation modes, the gNB may configure the operation mode for each priority separately.

[0110] Since the operation modes for PUCCHs with different priorities are determined separately, the operation modes for PUCCHs with different priorities may be different. In one option, for UCI multiplexing with different priorities (element 2-A), if PUCCHs with different priorities have different operation modes, one operation mode is determined and applied to all PUCCHs. For example, the operation mode is the operation mode for HP PUCCH. In another option, for a group of overlapping PUCCHs with different priorities, if PUCCHs with different priorities have different operation modes, LP PUCCH is dropped, and alternatively, LP and HP PUCCH are multiplexed / prioritized according to a predefined rule, regardless of the operation mode. Then, the operation mode for the resulting PUCCHs for UCI multiplexing with different priorities is determined according to one or more of the following: (1) The resulting operating mode for the PUCCH is configured by higher layers. (2) If at least one of the overlapping PUCCHs having different priorities is associated with a particular operating mode, the resulting PUCCH is associated with that particular operating mode. (3) The operation mode for the resulting PUCCH is determined by the operation mode associated with the time unit in which the resulting PUCCH resource is located. (4) If the resulting PUCCH is a PUCCH resource for a particular UCI type, the resulting PUCCH is associated with an operation mode associated with the PUCCH resource for that particular UCI type. (5) The resulting PUCCH is associated with a particular priority, e.g., an operating mode associated with PUCCH resources for the HP PUCCH. (6) If at least one of the overlapped PUCCHs is a HARQ-ACK PUCCH for a dynamic PDSCH, the resulting PUCCH is associated with the operation mode for the HARQ-ACK PUCCH for the dynamic PDSCH. (7) If at least one of the PUCCHs in a PUCCH slot is a HARQ-ACK PUCCH, the resulting PUCCH is associated with an operation mode for HARQ-ACK PUCCH.

[0111] In a fifth embodiment, the operation mode for UCI transmission parameters is determined for the resulting PUCCH after the UCI multiplexing / prioritization procedure.

[0112] For example, assuming the same time domain resources are configured for PUCCHs for different operation modes, the UE does not need to determine the operation mode for each PUCCH before the UCI multiplexing / prioritization procedure. If the UE is configured with only a single priority, the UE performs the UCI multiplexing procedure as in Rel-15. If the UE is configured with multiple priorities, the UE performs the UCI multiplexing / prioritization procedure for different priorities for each configuration as in Rel-16 or Rel-17. After the UCI multiplexing / prioritization procedure (e.g., after element-A for Rel-15 or after element 2-A for Rel-17), for each resulting PUCCH, the operation mode is determined according to the solution in the "Determining UCI Transmission Parameters According to Operation Mode" section above.

[0113] In the sixth embodiment, the operation mode for UCI transmission parameters is determined for PUCCHs after UCI multiplexing within the same priority (after element A, or after element 1-A, or after element 2'-A). In other words, the operation mode for the resulting PUCCHs for each priority is determined separately (before resolving collisions between PUCCHs with different priorities). Since the operation mode for the resulting PUCCHs for each priority is determined separately, the operation modes for PUCCHs with different priorities may be different. In one option, when a UE performs UCI multiplexing for different priorities (element 2-A), if the PUCCHs with different priorities have different operation modes, one operation mode is determined and applied to all PUCCHs. The operation mode is the operation mode for HP PUCCHs. In another option, if the PUCCHs with different priorities have different operation modes, for a group of overlapping PUCCHs with different priorities, the LP PUCCH is dropped, and alternatively, the LP and HP PUCCHs are multiplexed / prioritized according to a predefined rule regardless of the operation mode. Then, the operation mode for the resulting PUCCH for UCI multiplexing with different priorities is determined according to the mechanism in the third embodiment.

[0114] For the above embodiment, if the PUCCH is not consistent with the operation mode determined by the symbols of the PUCCH resource or if the PUCCH associated with the operation mode A is not restricted within the UL SB in the NOSB-FD symbol, the UE may drop / delay / rate match / puncture the PUCCH as described in the "Determining UCI transmission parameters according to the operation mode" section above. In one option, the UE checks only the potential inconsistency between the PUCCH resource and the operation mode determined for the PUCCH after the UCI multiplexing / prioritization procedure. In another option, the UE checks only the potential inconsistency between the PUCCH resource and the operation mode determined for the PUCCH after the UCI multiplexing / prioritization procedure within the same priority and after the UCI multiplexing / prioritization procedure between different priorities. In another option, the UE checks any PUCCH during or after UCI multiplexing / prioritization (intermediate PUCCH). In another option, the UE checks any PUCCH before or after UCI multiplexing / prioritization. In another option, the UE checks any PUCCH before or after UCI multiplexing / prioritization and any intermediate PUCCHs.

[0115] In the following multiplexing procedure, an operating mode decision is provided for UCI transmission parameters on the PUSCH and collision checking between the PUSCH and the DL symbol / DL subband (if configured) or PRBs outside the UL subband in the NOSB-FD symbol.

[0116] In the seventh embodiment, for a single priority, in one option, the UE first performs multiplexing / prioritization between PUCCH regardless of the operation mode, and then the UE performs multiplexing / prioritization between PUCCH and PUSCH regardless of the operation mode. In another option, the UE first performs multiplexing / prioritization between PUCCH and then between PUCCH and PUSCH in the same operation mode, and the UE second performs multiplexing / prioritization between PUCCH for different operation modes, and then between PUCCH and PUSCH for different operation modes. In another option, the UE first performs multiplexing / prioritization between PUCCH with the same operation mode, and then between PUCCH with different operation modes, and the UE second performs multiplexing / prioritization between PUCCH and PUSCH with the same operation mode, and then between PUCCH and PUSCH with different operation modes. In another option, the UE first performs multiplexing / prioritization between PUCCHs having the same operating mode, then performs multiplexing / prioritization between PUCCHs having different operating modes, and then performs multiplexing / prioritization between PUCCHs and PUSCHs regardless of the operating mode.

[0117] For the above options, in one example, the UE does not expect that a PUCCH after UCI multiplexing between PUCCHs having one operation mode overlaps with another PUCCH having another operation mode. Alternatively, such PUCCHs may overlap. In another example, the UE does not expect that a PUCCH after UCI multiplexing between PUCCHs having one operation mode overlaps with a PUSCH having another operation mode. Alternatively, PUCCHs and PUSCHs having different operation modes may overlap. In such a case, the UE may multiplex PUCCH with PUSCH, or alternatively, the UE may drop PUCCH or PUSCH, e.g., always drop PUSCH.

[0118] For multiple priorities, e.g., in case of LP and HP UCI multiplexing, in one option, regardless of the operation mode, the UE first performs multiplexing / prioritization among PUCCHs in the same priority, then the UE performs multiplexing / prioritization among PUCCHs and PUSCHs in the same priority, then the UE performs multiplexing / prioritization among PUCCHs for different priorities, then the UE performs multiplexing / prioritization among PUCCHs and PUSCHs for different priorities. In another option, for a certain priority, the UE first performs multiplexing / prioritization among PUCCHs in the same operation mode, then the UE performs multiplexing / prioritization among PUCCHs with different operation modes, then the UE performs multiplexing / prioritization among PUCCHs and PUSCHs, then for a different priority, the UE first performs multiplexing / prioritization among PUCCHs in the same operation mode, then the UE performs multiplexing / prioritization among PUCCHs with different operation modes, then the UE performs multiplexing / prioritization among PUCCHs and PUSCHs. In another option, for certain priorities, the UE first performs multiplexing / prioritization among PUCCHs in the same operation mode, then performs multiplexing / prioritization among PUCCHs and PUSCHs in the same operation mode, then performs multiplexing / prioritization among PUCCHs with different operation modes, and then performs multiplexing / prioritization among PUCCHs and PUSCHs with different operation modes. Then, for different priorities, the UE first performs multiplexing / prioritization among PUCCHs in the same operation mode, then performs multiplexing / prioritization among PUCCHs and PUSCHs with the same operation mode, then performs multiplexing / prioritization among PUCCHs with different operation modes, and then performs multiplexing / prioritization among PUCCHs and PUSCHs with different operation modes.In another option, for one operation mode, the UE first performs multiplexing / prioritization among PUCCHs in the same priority, then performs multiplexing / prioritization among PUCCHs and PUSCHs in the same priority, then the UE first performs multiplexing / prioritization among PUCCHs with different priorities, then performs multiplexing / prioritization among PUCCHs and PUSCHs with different priorities. Then, for a different operation mode, the UE first performs multiplexing / prioritization among PUCCHs in the same priority, then performs multiplexing / prioritization among PUCCHs and PUSCHs in the same priority, then the UE first performs multiplexing / prioritization among PUCCHs with different priorities, then performs multiplexing / prioritization among PUCCHs and PUSCHs with different priorities. In another option, for one operation mode, the UE first performs multiplexing / prioritization among PUCCHs in the same priority and then performs multiplexing / prioritization among PUCCHs with different priorities, and then, for a different operation mode, the UE first performs multiplexing / prioritization among PUCCHs in the same priority and then performs multiplexing / prioritization among PUCCHs with different priorities, then the UE performs multiplexing / prioritization among PUCCHs and PUSCHs for the same priority and then for different priorities.

[0119] For UCI multiplexing on PUSCHs with different operation modes, in one option, the UE may prefer to select a PUSCH with the same operation mode as the PUCCH. In another option, the UE may prefer to select a PUSCH with a specific operation mode, e.g., operation mode B, to protect UCI performance. In another option, the UE selects a PUSCH only from a set of PUSCHs with the same operation mode as the PUCCH. In another option, the UE selects a PUSCH only from a set of PUSCHs with a specific operation mode. If the UE fails to select a PUSCH from the set of PUSCHs, the UE may drop the PUSCHs that overlap with the PUCCH and transmit the PUCCH.

[0120] In an eighth embodiment, the operation mode for UCI transmission parameters is determined by the PUSCH carrying the UCI.

[0121] In one option, the UE determines the operation mode for PUCCH after or during UCI multiplexing / prioritization for PUCCH (element A or element 1-A / element 2-A or element 1-A / element 2'-A) according to any of the first to sixth embodiments, and if UCI is multiplexed onto PUSCH, the UE determines the operation mode for UCI transmission parameters according to PUSCH (element B or element 1-B / element 2-B or element 1-B / element 2'-B).

[0122] 6, the resulting PUCCH (PUCCH1 601) after UCI multiplexing among PUCCHs is associated with operation mode A, where PUCCH1 601 overlaps with PUSCH 602 that is in a normal symbol. PUCCH1 601 is multiplexed with PUSCH 602. Then, regardless of whether PUCCH1 601 is in a normal symbol or in a NOSB-FD symbol, the UCI transmission parameters are determined by operation mode B.

[0123] In another option, the UE does not determine the operation mode for PUCCH before the end of the UCI multiplexing / prioritization procedure. The UE determines the operation mode for UCI transmission parameters at the end of the UCI multiplexing / prioritization procedure (after element B or element 2-B, or element 2'-B). For example, for a single priority case, if UCI is to be multiplexed on PUSCH (element B is the last element) after the UCI multiplexing / prioritization procedure, the operation mode for UCI transmission parameters is determined by PUSCH, and if UCI is to be transmitted by PUCCH (element A may be considered as the last element, but since there is no PUSCH that overlaps with PUCCH after element A), the operation mode for UCI transmission parameters is determined by PUCCH according to the above fourth embodiment. For the example in FIG. 6, the UE does not determine the operation mode for PUCCH1. The UE determines only UCI transmission parameters according to PUSCH.

[0124] In another option, the UE does not determine the operation mode for the PUCCH before the end of the UCI multiplexing / prioritization procedure within the same priority level. In other words, if the UE is configured with different priorities, the UE determines the operation mode for the UCI transmission parameters at the end of the UCI multiplexing / prioritization procedure within the same priority level (after element 1-B or element 2'-B), and the UE determines the operation mode for the UCI transmission parameters at the end of the UCI multiplexing / prioritization procedure for a different priority level (after element 2-B).

[0125] In the ninth embodiment, the operation mode for UCI transmission parameters is determined by the PUCCH before UCI multiplexing on the PUSCH.

[0126] The UE determines an operation mode for the PUCCH after or during UCI multiplexing / prioritization for the PUCCH (element A or element 1-A / element 2-A or element 1-A / element 2'-A) according to any of the first to sixth embodiments, and determines an operation mode for UCI transmission parameters on the PUSCH according to the operation mode for the PUCCH.

[0127] For example, in FIG. 6 , the resulting PUCCH (PUCCH1) after UCI multiplexing among PUCCHs is associated with operation mode A, and the UCI transmission parameters are determined by operation mode A regardless of whether the PUSCH carrying UCI is within a normal symbol or not.

[0128] For the above embodiment, if the UE is configured with multiple priorities, in one option, at or after element 2-B, the operation mode for the UCI transmission parameters on the PUSCH carrying at least the HP UCI is determined by the HP PUCCH or HP PUSCH, if applicable. In another option, at or after element 2-B, the operation mode for the HP UCI transmission parameters on the PUSCH carrying at least the HP UCI is determined by the HP PUCCH or HP PUSCH, if applicable. For example, after element 2-B, the LP PUSCH carries the HP UCI, and the UCI transmission parameters for the HP UCI are determined by the HP PUCCH after element 1. If the HP PUSCH carries the HP UCI and the LP UCI, the UCI transmission parameters for the HP and LP UCI are determined by the HP PUSCH. In another option, at or after element 2-B, the operation mode for the UCI transmission parameters on the PUSCH is determined by the PUSCH. For example, after element 2-B, the LP PUSCH carries the HP UCI, and the UCI transmission parameters for the HP UCI are determined by the LP PUSCH.

[0129] Determining PUCCH Transmission Parameters for a PUCCH Repetition If the UE is configured with PUCCH repetition and the UE is configured with multiple PUCCH transmission parameters for different operating modes, the UE determines the PUCCH resource for each repetition according to a predefined rule.

[0130] In one embodiment, when an operation mode for UCI transmission via PUCCH is indicated by the gNB, the indicated operation mode is applied to all repetitions.

[0131] In another embodiment, when the operation mode for UCI transmission over PUCCH is determined by the operation mode associated with the time unit in which the PUCCH resource is located, in one option, the operation mode is determined for each repetition according to the time unit for each repetition. In another option, the operation mode is determined for all repetitions in common according to the time unit for all repetitions. In one example, the operation mode associated with a time unit spanning multiple repetitions may be determined based on the first symbol of the first repetition in the time unit being a NOSB-FD symbol or a normal (DL / UL / FL) symbol. In another example, the operation mode associated with the time unit for the first repetition is applied to all repetitions. In another example, the operation mode A (for the NOSB-FD symbol) may be assumed by the UE for all repetitions of PUCCH if any repetition may overlap with a NOSB-FD symbol.

[0132] If the operation mode is determined for each repetition respectively, in one option, if the operation mode is different for the repetitions, the UE transmits only a part of the PUCCH repetitions in the same operation mode, e.g., in a particular operation mode. In another option, if the number of available REs for each repetition / coding rate for each repetition is different, the UE transmits only a part of the PUCCH repetitions with the same coding rate / number of available REs. For example, the UE transmits only the first repetition, or an repetition with the same coding rate / number of available REs as the first repetition, or an repetition with the lowest coding rate. Alternatively, the UE does not expect repetitions with different coding rates / number of available REs. This option can be applied in single or multiple operation modes.

[0133] In one embodiment, for UCI transmission parameters associated with an operation mode, if the PUCCH repetition does not align with the operation mode determined by the symbols of the PUCCH resource, the UE may drop or delay the PUCCH repetition. For UCI transmission parameters associated with operation mode A, if the PUCCH repetition is not constrained within the UL SB in the NOSB-FD symbol, the UE may drop or delay the PUCCH repetition. For at least some channel coding mechanisms, rate matching or puncturing is not desirable because different coding rates for different PUCCH repetitions add complexity to the combination. In one option, whether rate matching can be applied is configured by the gNB. In another option, whether rate matching can be applied depends on the channel coding mechanism / PUCCH payload, for example, it can be applied for Reed-Muller (RM) codes but not for polar codes. In another option, whether rate matching can be applied depends on whether the same coding rate is achieved for all repetitions. For example, if the number of available REs after rate matching is the same for all repetitions, rate matching can be applied.

[0134] SPS HARQ-ACK Deferral SPS HARQ-ACK Deferral may be configured to reduce undesired dropping of SPS HARQ-ACK PUCCH colliding with DL symbols or DL ​​subbands. If the gNB does not configure NOSB-FD based duplexing, for SPS HARQ-ACK deferral, for the determination of valid symbols in the initial and target PUCCH slots, a symbol is not counted as a valid symbol if it overlaps with a symbol indicated by pdcch-ConfigSIB1 in the MIB for semi-static DL symbols, SSB, and CORESET for Type0-PDCCH CSS set. If the gNB configures NOSB-FD based duplexing, the invalid symbol may be determined as one of the following options:

[0135] In one embodiment, for the determination of valid symbols in the initial and target PUCCH slots in case of SPS HARQ-ACK deferral, a symbol is an invalid symbol if: At least one of the symbols of the PUCCH resource overlaps with a NOSB-FD symbol and all PRBs allocated for PUCCH transmission are not contained within the UL subband, or At least one of the symbols of the PUCCH resource overlaps with a NOSB-FD symbol and a DL subband is explicitly or implicitly indicated for the NOSB-FD symbol, and at least one PRB allocated for PUCCH transmission is contained within the DL subband; or At least one of the symbols of the PUCCH resource overlaps with a DL symbol or a symbol of an SS / PBCH block indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided, or If at least one of the symbols of the PUCCH resource overlaps with a DL symbol indicated as part of the CORESET for a Type-0 PDCCH configured in the MIB.

[0136] In one embodiment, for the determination of valid symbols in the initial and target PUCCH slots in case of SPS HARQ-ACK deferral, a symbol is an invalid symbol if: At least one of the symbols of the PUCCH resource overlaps with a NOSB-FD symbol and all PRBs allocated for PUCCH transmission are not contained within the UL subband, or At least one of the symbols of the PUCCH resource overlaps with a NOSB-FD symbol and a DL subband is explicitly or implicitly indicated for the NOSB-FD symbol, and at least one PRB allocated for PUCCH transmission is contained within the DL subband; or If at least one of the symbols of the PUCCH resource overlaps with a semi-static DL symbol.

[0137] In one option, the semi-static DL symbol is a DL symbol indicated by tdd-UL-DL-ConfigurationDedicated, if provided, or a DL symbol indicated by tdd-UL-DLConfigurationCommon, and the symbol is not indicated as a NOSB-FD symbol by dedicated higher layer signaling. In another option, the semi-static DL symbol is tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided.

[0138] For the above embodiment, the PUCCH resource is the resulting PUCCH resource after UCI multiplexing / prioritization. In other words, the UE first performs UCI multiplexing / prioritization, and if the UE transmits an SPS HARQ-ACK using a PUCCH with an SPS PUCCH resource, e.g., SPS-PUCCH-AN-List-r16 or n1PUCCH-AN, and the PUCCH resource consists of invalid symbols, the SPS HARQ-ACK configured for deferral is deferred. The gNB may configure SPS HARQ-ACK deferral based on whether NOSB-FD. For example, even if the gNB configures NOSB-FD based duplexing, the gNB may still configure SPS HARQ-ACK deferral as if NOSB-FD duplexing was not configured. The gNB may configure the SPS HARQ-ACK deferral mechanism for each SPS configuration, or for each configured BWP, or for each configured carrier, or for the UE. If the gNB configures SPS HARQ-ACK deferral as if NOSB-FD duplex was not configured, and if the UE would transmit an SPS HARQ-ACK with an SPS PUCCH resource that collides with a DL subband, the UE drops the PUCCH without deferral. Alternatively, the UE does not expect such a collision.

[0139] If the UE is configured with multiple sets of UCI transmission parameters for different operation modes, the gNB may configure the SPS HARQ-ACK deferral mechanism for each operation mode (based on whether NOSB-FD). In one option, the UE determines the SPS HARQ-ACK deferral mechanism according to the operation mode associated with the resulting SPS HARQ-ACK PUCCH in the initial slot. For example, in the initial slot n, if the resulting SPS HARQ-ACK PUCCH is associated with an operation mode having SPS HARQ-ACK deferral mechanism A, the UE determines the SPS HARQ-ACK deferral using the mechanism A. When the UE checks the next slot n+1, the resulting SPS HARQ-ACK PUCCH is associated with an operation mode having SPS HARQ-ACK deferral mechanism B, and the UE still determines the SPS HARQ-ACK deferral using SPS HARQ-ACK deferral mechanism A. In another option, the UE determines the SPS HARQ-ACK deferral mechanism according to the operation mode associated with the resulting SPS HARQ-ACK PUCCH in every slot checked. For example, if in an initial slot n, the resulting SPS HARQ-ACK PUCCH is associated with an operating mode having SPS HARQ-ACK deferral mechanism A, the UE determines SPS HARQ-ACK deferral using mechanism A, and when the UE checks the next slot n+1, the resulting SPS HARQ-ACK PUCCH is associated with an operating mode having SPS HARQ-ACK deferral mechanism B, and the UE determines SPS HARQ-ACK deferral using SPS HARQ-ACK deferral mechanism B.

[0140] System and Implementation 7-10 illustrate various systems, devices, and components in which aspects of the disclosed embodiments may be implemented.

[0141] 7 illustrates a network 700 according to various embodiments. Network 700 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.

[0142] The network 700 may include a UE 702, which may include any mobile or non-mobile computing device designed to communicate with a RAN 704 via an over-the-air connection. The UE 702 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, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an in-vehicle diagnostic device, a dash-top mobile instrument, 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 networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0143] In some embodiments, the network 700 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, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

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

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

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

[0147] The ANs of the RAN 704 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 702 with an air interface for network access. The UE 702 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 704. For example, the UE 702 and the RAN 704 may use carrier aggregation to enable the UE 702 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 ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0148] The RAN 704 may provide an air interface over licensed or unlicensed spectrum. To operate in the unlicensed spectrum, the node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques using PCell / Scell. Before accessing the unlicensed spectrum, the node may perform medium / carrier sensing operations, for example based on a Listen-Before-Talk (LBT) protocol.

[0149] In a V2X scenario, the UE 702 or AN 708 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable 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 eNB may be referred to as an "eNB type RSU"; a gNB may be referred to as a "gNB type RSU"; etc. In one example, the RSU is a computing device coupled to radio frequency circuits located on the roadside that provide connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuits that store intersection map geometry, traffic statistics, media, and applications / software that sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weather-resistant enclosure suitable for outdoor installation and may include a traffic signal controller or a network interface controller for providing a wired connection (e.g., Ethernet) to a backhaul network.

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

[0151] In some embodiments, the RAN 704 may be an NG-RAN 714 having a gNB, e.g., gNB 716, or an ng-eNB, e.g., ng-eNB 718. The gNB 716 may connect to a 5G-capable UE using a 5G NR interface. The gNB 716 may connect to a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 718 may also connect to a 5G core through an NG interface, but may connect to a UE through an LTE air interface. The gNB 716 and the ng-eNB 718 may connect to each other through an Xn interface.

[0152] 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 nodes in the NG-RAN 714 and the UPF 748, and an NG Control Plane (NG-C) interface (e.g., N2 interface), which is a signaling interface between nodes in the NG-RAN 714 and the AMF 744.

[0153] The NG-RAN 714 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 data control and LDPC. The 5G NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signals 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.

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

[0155] In some embodiments, the CN 720 may be an LTE CN 722, which may also be referred to as an EPC. The LTE CN 722 may include an MME 724, an SGW 726, an SGSN 728, an HSS 730, a PGW 732, and a PCRF 734 coupled together through interfaces (or "reference points") as shown. The functionality of the elements of the LTE CN 722 may be briefly introduced as follows.

[0156] The MME 724 may implement mobility management functions that track the current location of the UE 702 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0157] The SGW 726 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 722. The SGW 726 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.

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

[0159] The HSS 730 may include a database for network users, including subscription-related information, to support handling of communication sessions by network entities. The HSS 730 may provide support for routing / roaming, authentication, authorization, name / addressing resolution, location dependency, etc. An S6a reference point between the HSS 730 and the MME 724 may enable transfer of subscription and authentication data to authenticate / authorize user access to the LTE CN 720.

[0160] The PGW 732 may terminate the SGi interface towards a data network (DN) 736, which may include an application / content server 738. The PGW 732 may route data packets between the LTE CN 722 and the data network 736. The PGW 732 may be coupled to the SGW 726 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 732 may further include a node for policy enforcement and charging data collection (e.g., PCEF). In addition, the SGi reference point between the PGW 732 and the data network 736 may be an operator external public, private PDN, or intra-operator packet data network, for example, for provisioning of IMS services. The PGW 732 may be coupled to the PCRF 734 via a Gx reference point. The PCRF 734 is the policy and charging control element of the LTE CN 722. The PCRF 734 may be communicatively coupled to the app / content server 738 to determine appropriate QoS and charging parameters for the service flow. The PCRF 732 may provision the associated rules to the PCEF (via the Gx reference point) with the appropriate TFT and QCI.

[0161] In some embodiments, the CN 720 may be a 5GC 740. The 5GC 740 may include an AUSF 742, an AMF 744, an SMF 746, a UPF 748, an NSSF 750, an NEF 752, an NRF 754, a PCF 756, an UDM 758, and an AF 760 coupled together via interfaces (or "reference points") as shown. The functionality of the elements of the 5GC 740 may be briefly introduced as follows: The AUSF 742 may store data and handle authentication related functions for authentication of the UE 702. The AUSF 742 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 740 via reference points as shown, the AUSF 742 may exhibit a Nausf service based interface.

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

[0163] The SMF 746 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 748 and the AN 708); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering in the UPF 748 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 interception (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 744 to the AN 708 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 702 and the data network 736.

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

[0165] The NSSF 750 may select a set of network slice instances to serve the UE 702. The NSSF 750 may also determine the allowed NSSAI and, if necessary, the mapping to the subscribed S-NSSAI. The NSSF 750 may also determine the AMF set, or a list of candidate AMFs, to be used to serve the UE 702 based on the preferred configuration and possibly by querying the NRF 754. The selection of the set of network slice instances for the UE 702 may be triggered by the AMF 744 with which the UE 702 is registered by interacting with the NSSF 750, which may result in a change of the AMF. The NSSF 750 may interact with the AMF 744 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, the NSSF 750 may exhibit an Nnssf service-based interface.

[0166] The NEF 752 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal publication / republication, AFs (e.g., AFs 760), edge computing or fog computing systems, etc. In such an embodiment, the NEF 752 may authenticate, authorize, or throttle AFs. The NEF 752 may also translate information exchanged with the AFs 760 and with internal network functions. For example, the NEF 752 may translate between AF service identifiers and internal 5GC information. The NEF 752 may also receive information from other NFs based on the published capabilities of the other NFs. This information may be stored in the NEF 752 as structured data or in a data storage NF using a standardized interface. The stored information may then be republished by the NEF 752 to other NFs and AFs, or used for other purposes, such as analytics. Additionally, the NEF 752 may present an Nnef service-based interface. NRF754 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF754 also maintains information of 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 "instance" may refer to a concrete occurrence of an object, such as may occur during the execution of program code. Additionally, NRF754 may present an Nnrf service-based interface. The PCF 756 may provide policy rules to the control plane functions to enforce them and may support a unified policy framework for governing network behavior. The PCF 756 may also implement a front end to access subscription information related to policy decisions in the UDRs of the UDM 758. In addition to communicating with functions via reference points as shown, the PCF 756 exposes an Npcf service-based interface. The UDM 758 may handle subscription related information to support handling of communication sessions by network entities and may store subscription data of the UE 702. For example, the subscription data may be communicated between the UDM 758 and the AMF 744 via the N8 reference point. The UDM 758 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 758 and the PCF 756, and / or structured data and application data for publication for the NEF 752 (including PFD for application discovery, application requirement information for multiple UEs 702). A Nudr service-based interface may be exposed by the UDR 221 to allow the UDM 758, the PCF 756, and the NEF 752 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM may include a UDM-FE responsible for handling certificates, location management, subscription management, etc. Multiple different front ends may provide services to 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 758 may present a Nudm service-based interface. The AF 760 may provide application influence over traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0167] In some embodiments, the 5GC 740 may enable edge computing by selecting an operator / third-party service to be geographically close to the point where the UE 702 is connected to the network. This may reduce latency and load on the network. To provide edge computing implementation, the 5GC 740 may select a UPF 748 close to the UE 702 and perform traffic steering from the UPF 748 to the data network 736 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 760. In this way, the AF 760 may affect UPF (re)selection and traffic routing. Based on operator deployment, when the AF 760 is considered a trusted entity, the network operator may allow the AF 760 to directly interact with associated NFs. Additionally, the AF 760 may exhibit a Naf service-based interface. Data network 736 may represent various network operator services, Internet access, or third party services, which may be provided by one or more servers, including, for example, application / content server 738 .

[0168] 8 illustrates a schematic of a wireless network 800 according to various embodiments. The wireless network 800 may include a UE 802 in wireless communication with an AN 804. The UE 802 and the AN 804 may be similar to similarly named components described elsewhere herein and may be substantially interchangeable. The UE 802 may be communicatively coupled to the AN 804 via a connection 806. The connection 806 is illustrated as an air interface for enabling the communicative coupling and may correspond 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 802 may include a host platform 808 coupled to a modem platform 810. The host platform 808 may include an application processing circuit 812 that may be coupled to a protocol processing circuit 814 of the modem platform 810. The application processing circuit 812 may execute various applications for the UE 802 to source / sink application data. The application processing circuit 812 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 814 may implement one or more of the layer operations to facilitate the transmission or reception of data over the connection 806. The layer operations implemented by the protocol processing circuit 814 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations. The modem platform 810 may further include digital baseband circuitry 816 that may implement one or more layer operations that are "lower" layer operations performed by the protocol processing circuitry 814 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 that 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, control channel signal blind decoding, and other related functions. The modem platform 810 may further include a transmit circuitry 818, a receive circuitry 820, an RF circuitry 822, and an RF front end (RFFE) 824 that may include or be connected to one or more antenna panels 826.Briefly, the transmit circuitry 818 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 820 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 822 may include low noise amplifiers, power amplifiers, power tracking components, etc.; the RFFE 824 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 transmit circuitry 818, receive circuitry 820, RF circuitry 822, RFFE 824, and antenna panel 826 components (collectively "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether the communication is TDM or FDM at mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, disposed in the same or different chips / modules, etc. In some embodiments, the protocol processing circuitry 814 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 826, the RFFE 824, the RF circuitry 822, the receive circuitry 820, the digital baseband circuitry 816, and the protocol processing circuitry 814. In some embodiments, the antenna panel 826 may receive transmissions from the AN 804 by receive beamforming signals received by multiple antennas / antenna elements of one or more of the antenna panels 826.

[0169] UE transmissions may be established by and through protocol processing circuitry 814, digital baseband circuitry 816, transmit circuitry 818, RF circuitry 822, RFFE 824, and antenna panel 826. In some embodiments, the transmit components of the UE 804 may apply spatial filters to data to be transmitted to form transmit beams that are radiated by antenna elements of the antenna panel 826. Similar to the UE 802, the AN 804 may include a host platform 828 coupled to a modem platform 830. The host platform 828 may include an application processing circuit 832 coupled to a protocol processing circuit 834 of the modem platform 830. The modem platform may further include a digital baseband circuit 836, a transmit circuit 838, a receive circuit 840, an RF circuit 842, an RFFE circuit 844, and an antenna panel 846. The components of the AN 804 may be similar to and substantially interchangeable with similarly named components of the UE 802. In addition to performing data transmission / reception as described above, the components of the AN 808 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. FIG. 9 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some exemplary embodiments. 9 shows a diagrammatic representation of hardware resources 900 including one or more processors (or processor cores) 910, one or more memory / storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940 or other interface circuitry. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 900.

[0170] Processors 910 may include, for example, processor 912 and processor 914. Processor 910 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.

[0171] The memory / storage device 920 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 920 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.

[0172] Communications resources 930 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 904, or one or more databases 906, or other network elements over network 908. For example, communications resources 930 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® components, and other communications components.

[0173] The instructions 950 may include software, programs, applications, applets, apps, or other executable code for causing at least one of the processors 910 to perform any one or more of the methodologies discussed herein. The instructions 950 may reside completely or partially within at least one of the processors 910 (e.g., in a cache memory of the processor), the memory / storage device 920, or any suitable combination thereof. Furthermore, any portion of the instructions 950 may be transferred to the hardware resources 900 from any combination of the peripheral device 904 or the database 906. Accordingly, the memory of the processor 910, the memory / storage device 920, the peripheral device 904, and the database 906 are examples of computer-readable and machine-readable media.

[0174] FIG. 10 illustrates a network 1000 according to various embodiments. The network 1000 may operate in a manner consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 1000 may operate simultaneously with the network 700. For example, in some embodiments, the network 1000 may share one or more frequency or bandwidth resources with the network 700. As a specific example, a UE (e.g., the UE 1002) may be configured to operate in both the network 1000 and the network 700. Such a configuration may be based on the UE including circuitry configured to communicate with frequency and bandwidth resources of both the network 700 and the network 1000. In general, elements of the network 1000 may share one or more characteristics with elements of the network 700. For the sake of brevity and clarity, such elements may not be repeated in the description of the network 1000.

[0175] The network 1000 may include a UE 1002, which may include any mobile or non-mobile computing device designed to communicate with the RAN 1008 via an over-the-air connection. The UE 1002 may be similar to the UE 702, for example. The UE 1002 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, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an in-vehicle 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 networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0176] Although not specifically shown in FIG. 10, in some embodiments, the network 1000 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, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in FIG. 10, the UE 1002 may be communicatively coupled to an AP, such as the AP 706, as described with respect to FIG. 7. Additionally, although not specifically shown in FIG. 10, in some embodiments, the RAN 1008 may include one or more ANs, such as the AN 708, as described with respect to FIG. 7. The RAN 1008 and / or the ANs of the RAN 1008 may be referred to as a base station (BS), a RAN node, or using some other terminology or designation.

[0177] The UE 1002 and the RAN 1008 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 terahertz (THz) or sub-THz bandwidths, or cooperative communication and sensing. As used herein, the term "cooperative communication and sensing" may refer to systems that enable wireless communication and radar-based sensing through various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in frequency ranges of 80 GHz and above. Such frequency ranges may additionally or alternatively be referred to as "millimeter wave" or "mm-wave" frequency ranges.

[0178] The RAN 1008 may enable communication between the UE 1002 and a 6G core network (CN) 1010. Specifically, the RAN 1008 may facilitate transmission and reception of data between the UE 1002 and the 6G CN 1010. The 6G CN 1010 may include various functions, such as an NSSF 750, a NEF 752, an NRF 754, a PCF 756, a UDM 758, an AF 760, an SMF 746, and an AUSF 742. As shown in FIG. 10 , the 6G CN 1010 may further include a UPF 748 and a DN 736.

[0179] In addition, the RAN 1008 may include various additional functions in addition to or instead of the functions of a traditional cellular network, such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 1024 and a Compute Service Function (Comp SF) 1036. The Comp CF 1024 and the Comp SF 1036 may be part of or functions of a computing service plane. The Comp CF 1024 may be a control plane function that provides functions such as management of the Comp SF 1036, computing task context creation and management (e.g., create, read, modify, delete), interaction with the underlying computing infrastructure for computing resource management, etc. The Comp SF 1036 may be a user plane function that acts as a gateway to interface computing service users (e.g., UE 1002) and computing nodes behind the Comp SF instance. Some functions of Comp SF 1036 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 embodiments, a Comp SF 1036 instance may act as a user plane gateway for a cluster of computing nodes. A Comp CF 1024 instance may control one or more Comp SF 1036 instances. Two other such functions may include a Communication Control Function (Comm CF) 1028 and a Communication Service Function (Comm SF) 1038, which may be part of the communication service plane.The Comm CF 1028 may be a control plane function for management of the Comm SF 1038, communication session creation / configuration / release, and management of communication session context. The Comm SF 1038 may be a user plane function for data transport. The Comm CF 1028 and the Comm SF 1038 may be considered as upgrades of the SMF 746 and the UPF 748 described with respect to the 5G system in FIG. 7. The upgrades provided by the Comm CF 1028 and the Comm SF 1038 may enable service-aware transport. For traditional (e.g., 4G or 5G) data transport, the SMF 746 and the UPF 748 may still be used.

[0180] Two other such functions may include a Data Control Function (Data CF) 1022 and a Data Service Function (Data SF) 1032, which may be part of the data service plane. The Data CF 1022 may be a control plane function, providing functions such as Data SF 1032 management, data service creation / configuration / release, data service context management, etc. The Data SF 1032 may be a user plane function, acting as a gateway between data service users (e.g., UE 1002 and various functions of 6G CN 1010) and data service endpoints behind the gateway. Specific functions may include: parsing and forwarding data service user data to corresponding data service endpoints, generating charging data, reporting data service status. Another such function may be a Service Orchestration and Chaining Function (SOCF) 1020, which may discover, orchestrate, and chain communication / computing / data services provided by functions in the network. Upon receiving a service request from a user, the SOCF 1020 may interact with one or more of the Comp CF 1024, the Comm CF 1028, and the Data CF 1022 to identify instances of the Comp SF 1036, the Comm SF 1038, and the Data SF 1032, configure service resources, and generate a service chain that may include multiple instances of the Comp SF 1036, the Comm SF 1038, and the Data SF 1032 and their associated computing endpoints. Within the generated service chain, workload processing and data movement may then take place. The SOCF 1020 may also be responsible for maintaining, updating, and releasing the created service chain.

[0181] Another such function may be a service registration function (SRF) 1014, 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 1036 and Data SF 1032 gateways and services provided by the UE 1002. The SRF 1014 may be considered a counterpart to the NRF 754, which may act as a registry for network functions.

[0182] Other such functions may include an evolved service communication proxy (eSCP) and a service infrastructure control function (SICF) 1026, 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 a user plane service communication proxy function. The eSCP is thus represented in two parts, eCSP-C 1012 and eSCP-U 1034 for the control plane service communication proxy and the user plane service communication proxy, respectively. The SICF 1026 may control and configure the eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

[0183] Another such function is the AMF 1044. The AMF 1044 may be similar to 744, but with additional functions. In particular, the AMF 1044 may include potential functional subdivisions, such as moving message forwarding functions from the AMF 1044 to the RAN 1008.

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

[0185] The UE 1002 may include an additional function referred to as a computing client service function (comp CSF) 1004. The comp CSF 1004 may have both control plane and user plane functions and may interact with corresponding network side functions such as the SOCF 1020, Comp CF 1024, Comp SF 1036, Data CF 1022, and / or Data SF 1032 for service discovery, request / response, computational task workload exchange, etc. The Comp CSF 1004 may also coordinate with the network side functions to determine whether a computing task should be performed on the UE 1002, on the RAN 1008, and / or on elements of the 6G CN 1010.

[0186] The UE 1002 and / or the Comp CSF 1004 may include a service mesh proxy 1006. The service mesh proxy 1006 may act as a proxy for service-to-service communications within the user plane. The functionality of the service mesh proxy 1006 may include one or more of addressing, security, load balancing, and the like.

[0187] Exemplary Procedure In some embodiments, an electronic device, network, system, chip, or component of Figures 7-10 or any other Figures herein, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods, or portions thereof, as described herein. One such process is shown in Figure 11. In embodiments, the process of Figure 11 may be performed by a fifth generation (5G) base station (gNB), one or more elements of a gNB, and / or one or more electronic devices that include and / or implement a gNB. The process may include, at 1101, identifying that a full duplex (FD) symbol is to be transmitted within a transmission period; at 1102, based on the identification that an FD symbol is to be transmitted within the transmission period, identifying one or more uplink (UL) parameters for a UL transmission and / or one or more downlink (DL) parameters for a DL transmission; and, at 1103, performing a DL transmission within the transmission period in accordance with the one or more DL parameters and processing a UL transmission received within the transmission period in accordance with the one or more UL parameters.

[0188] Another such process is shown in Figure 12. In an embodiment, the process of Figure 12 may be performed by a user equipment (UE) in a fifth generation (5G) network, one or more elements of a UE, and / or one or more electronic devices including and / or implementing a UE. The process may include, at 1201, identifying one or more uplink (UL) parameters for a UL transmission and / or one or more downlink (DL) parameters for a DL transmission in an indication received from a 5G base station (gNB), where the one or more UL parameters and / or the one or more DL parameters are based on an identification by the gNB that a full duplex (FD) symbol is to be transmitted in a transmission period; and, at 1202, performing a UL transmission in the transmission period according to the one or more UL parameters or processing a DL transmission received in the transmission period according to the one or more DL parameters. Another such process is shown in Figure 13. In an embodiment, the process of Figure 13 may comprise or relate to a method to be performed by a user equipment (UE), one or more elements of a UE, and / or one or more electronic devices including and / or implementing the UE, the method including: receiving a non-overlapping sub-band full duplex with time and frequency resource allocation (NOSB-FD) configuration at 1301; determining one or more parameters for transmission of uplink control information (UCI) based on the NOSB-FD configuration at 1302; and transmitting the UCI based on the determined one or more parameters at 1303. For one or more embodiments, at least one of the components described in one or more of the drawings above may be configured to perform one or more operations, techniques, processes, and / or methods as described in the exemplary section below. For example, a baseband circuit as described above in connection with one or more of the drawings above 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., as described above in connection with one or more of the preceding drawings, may be configured to operate according to one or more of the examples described in the exemplary section below.

[0189] Example 1: a gNB configuring UL and DL resources within a serving cell or BWP bandwidth for different symbols; a UE receiving an UL and DL resource configuration; a UE receiving or transmitting a DL or UL channel / signal according to a configuration of the DL or UL channel / signal and / or a DCI scheduling the DL or UL channel / signal; The present invention may comprise a system and method for multiple operating modes for DL ​​or UL transmission in duplex operation, having:

[0190] Example 2 may comprise the method of example 1 and / or any other example herein, where the transmission parameters in the DL or UL transmission configuration include one or more of the following: - DL or UL BWP - Frequency domain resource information - MCS table - Transform Precoding (i.e. DFT-s-OFDM or OFDM waveforms) - Power control parameters - rate matching pattern for PDSCH - Invalid symbol pattern for PUSCH - Spatial information - Transmit power scaling for DL ​​signal and channel relative to the reference. Example 3 may comprise the method of example 1 and / or any other example herein, where different operating modes for DL ​​or UL transmissions are introduced to distinguish between operations within NOSB-FD symbols and / or normal symbols.

[0191] Example 4 may comprise the method of Example 3 and / or any other example herein, where the UE expects any UL transmission to be included within an intersection of a PRB of an active UL BWP in a UL symbol and a PRB in a UL subband in a NOSB-FD symbol (i.e., a UL PRB). Example 5 may comprise the method of Example 3 and / or any other example herein, where the operating mode for DL ​​or UL transmission is determined based on a time unit that includes an assigned symbol of the DL or UL transmission.

[0192] Example 6 may comprise the method of Example 5 and / or any other example herein, where the time unit may include all symbols in a slot, PUCCH slot, or multiple slots used by DL or UL transmission. Example 7 may comprise the method of Example 5 and / or any other example herein, where the time unit includes exactly the assigned symbols of DL or UL transmission in a slot, PUCCH slot, or multiple slots used by DL or UL transmission. Example 8 may comprise the method of Example 5 and / or any other example herein, where if at least one symbol of the time unit is a NOSB-FD symbol, the UE uses operating mode A in the time unit. Otherwise, the UE uses operating mode B in the time unit.

[0193] Example 9 may include the method of Example 5 and / or any other example herein, where, for a given time unit, the mode of operation for the time unit is determined based on whether a first symbol of the time unit is a NOSB-FD symbol or a normal (DL / UL / FL) symbol.

[0194] Example 10 may include the method of example 5 and / or any other example herein, where if all symbols in a time unit are NOSB-FD symbols, the UE uses operating mode A in the time unit; and if all symbols in the time unit are normal symbols, the UE uses operating mode B in the time unit.

[0195] Example 11 may include the method of Examples 3-10 and / or any other example herein, where in configuring DL or UL transmission, the UE is configured with transmission parameters associated with one or more operating modes, and the UE performs DL or UL transmission using the transmission parameters of the determined operating mode.

[0196] Example 12 may comprise the method of example 11 and / or any other example herein, where DL or UL transmissions in different time units may be associated with the same or different operational modes.

[0197] Example 13 may comprise the method of example 11 and / or any other example herein, where, for a DL or UL transmission, the operational mode is determined over multiple time units of the DL or UL transmission.

[0198] Example 14 may comprise the method of example 13 and / or any other example herein, where the UE expects DL or UL transmissions in multiple time units to use the same mode of operation.

[0199] Example 15 may include the method of Example 13 and / or any other example herein, where the operating mode is determined based on a first time unit of the plurality of time units, and the UE performs DL or UL transmission in the same operating mode in any of the plurality of time units.

[0200] Example 16 may comprise the method of Example 13 and / or any other example herein, where the operation mode is determined based on a first time unit of the multiple time units, and the UE performs DL or UL transmission according to the same operation mode in all of the multiple time units. Example 17 may comprise the method of Example 13 and / or any other example herein, where the operation mode is determined based on a first time unit of the multiple time units, and if assigned symbols in a slot are associated with a different operation mode, the slot is not considered an available slot.

[0201] Example 18 may comprise the method of example 11 and / or any other example herein, where, for DL ​​or UL transmission, the UE expects that every time unit of DL or UL transmission must use the same operating mode.

[0202] Example 19 may comprise the method of examples 3-10 and / or any other example herein, where in the configuration for DL ​​or UL transmission, the UE is configured with corresponding parameters associated with the operating mode.

[0203] Example 20 may comprise the method of Example 11 or Example 19 and / or some other example herein, where the operation mode is indicated by a DCI scheduling a DL or UL transmission. Example 21 may comprise the method of Example 18 or Example 19 and / or some other example herein, where the UE expects the configured or indicated operation mode to be consistent with the determined operation mode in any time unit that includes an assigned symbol of a DL or UL transmission.

[0204] Example 22 may include the method of Example 18 or Example 19 and / or any other example herein, where if a different operating mode is determined for a time unit of DL or UL transmission, the UE drops the DL or UL transmission for that time unit, or drops the entire DL or UL transmission.

[0205] Example 23 may include the method of example 18 or example 19 and / or any other example herein, where if a DL or UL transmission is configured with repetition, if a different operating mode is determined within a slot of the DL or UL transmission, the slot is not considered an available slot.

[0206] Example 24 may comprise the method of example 18 or example 19 and / or any other example herein, where the UE receives or transmits a DL or UL transmission based on a configured or indicated mode of operation.

[0207] Example 25 comprises a method to be performed by a fifth generation (5G) base station (gNB), where the method may include: identifying that a full duplex (FD) symbol is to be transmitted within a transmission period; identifying one or more uplink (UL) parameters for a UL transmission and / or one or more downlink (DL) parameters for a DL transmission based on identifying that an FD symbol is to be transmitted within the transmission period; and Performing a DL transmission within a transmission period in accordance with the one or more DL parameters, and processing a UL transmission received within a transmission period in accordance with the one or more UL parameters.

[0208] Example 26 may comprise the method of example 25 and / or any other example herein, where the FD symbols are non-overlapping subband FD (NOSB-FD) symbols.

[0209] Example 27 may comprise the method of any of Examples 25-26 and / or any other example herein, where the FD symbol is a symbol that allows simultaneous UL and DL transmission within the same symbol.

[0210] Example 28 may comprise the method of any of Examples 25-27 and / or any other example herein, where the transmission period is a slot or a group of slots.

[0211] Example 29 may include the method of any of Examples 25 to 28 and / or any other example herein, where the UL parameters or DL ​​parameters include one or more of the parameters provided in Example 2.

[0212] Example 30 comprises a method to be performed by a user equipment (UE) in a fifth generation (5G) network, where the method may include: Identifying, in an indication received from a 5G base station (gNB), one or more uplink (UL) parameters for a UL transmission and / or one or more downlink (DL) parameters for a DL transmission, where the one or more UL parameters and / or the one or more DL parameters are based on an identification by the gNB that a full duplex (FD) symbol is to be transmitted within the transmission period; and Performing a UL transmission within a transmission period according to the one or more UL parameters, or processing a DL transmission received within a transmission period according to the one or more DL parameters.

[0213] Example 31 may comprise the method of example 30 and / or any other example herein, where the FD symbols are non-overlapping subband FD (NOSB-FD) symbols.

[0214] Example 32 may comprise the method of any of Examples 30-31 and / or any other examples herein, where the FD symbol is a symbol that allows simultaneous UL and DL transmission within the same symbol.

[0215] Example 33 may include the method of any of Examples 30-32 and / or any other example herein, where the transmission period is a slot or a group of slots.

[0216] Example 34 may include the method of any of Examples 30 to 33 and / or any other example herein, where the UL parameters or DL ​​parameters include one or more of the parameters provided in Example 2.

[0217] Example 1B may comprise a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method including: The UE receiving a non-overlapping sub-band full duplex (NOSB-FD) configuration with time and frequency resource allocation from the gNB; and The UE determines UCI transmission parameters according to the NOSB-FD configuration.

[0218] Example 2B may comprise the method of example 1B or any other example herein, where the UCI transmission parameters include PUCCH transmission parameters and UCI parameters on the PUSCH.

[0219] Example 3B may include the method of example 1B or some other example herein, where UCI transmission parameters are configured and determined separately for different operating modes.

[0220] Example 4B may include the method of Examples 2B and 3B, or any other example herein, where a different mode of operation is introduced to distinguish between operations within NOSB-FD symbols and / or normal symbols.

[0221] Example 5B may include the method of Example 2B and Example 3B, or some other example herein, where the operational mode associated with the UCI transmission parameter is determined based on symbols in one or more PUCCH slots, or symbols of PUCCH resources, or symbols of a PUSCH, or an indication by a gNB.

[0222] Example 6B may include the method of Example 2B and Example 3B, or some other example herein, where the operating mode for the PUCCH resource is determined before UCI multiplexing, or before and after UCI multiplexing, or after UCI multiplexing.

[0223] Example 7B may comprise the method of example 6B or some other example herein, where the operation mode for the PUCCH resources is determined separately or jointly by the set of PUCCH resources.

[0224] Example 8B may include the method of example 6B and example 7B, or some other example herein, where UCI multiplexing is performed within each operating mode, respectively.

[0225] Example 9B may include the method of example 8B or any other example herein, where UCI multiplexing is further performed between different operating modes after UCI multiplexing within each operating mode.

[0226] Example 10B may comprise the method of example 8B or any other example herein, where UCI multiplexing is performed within the same priority and then between different priorities in the same operating mode.

[0227] Example 11B may include the method of Example 9B and Example 10B, or any other example herein, where UCI multiplexing is performed within the same priority after UCI multiplexing within each operating mode, and then between different priorities in different operating modes.

[0228] Example 12B may include the method of Example 6B and Example 7B, or any other example herein, where UCI multiplexing is performed regardless of the operating mode.

[0229] Example 13B may comprise the method of example 5B or any other example herein, where the UCI transmission parameters are determined according to a PUSCH.

[0230] Example 14B may comprise the method of Example 13B or some other example herein, where UCI multiplexing is performed within each operating mode for PUCCH and / or PUCCH with PUSCH.

[0231] Example 15B may comprise the method of Example 14B or some other example herein, where UCI multiplexing is further performed between different operating modes for PUCCH and / or PUCCH with PUSCH after UCI multiplexing within each operating mode.

[0232] Example 16B may comprise the method of Example 13B or some other example herein, where the operation mode for UCI parameters on the PUSCH is determined after UCI multiplexing or after UCI multiplexing for the PUCCH.

[0233] Example 17B may comprise the method of example 5B or some other example herein, where the operating mode for each PUCCH repetition is determined separately or jointly by all the repetitions.

[0234] Example 18B may comprise the method of example 1B or any other example herein, where the UCI transmission parameters include an SPS HARQ-ACK deferral decision.

[0235] Example 19B may comprise the method of Example 18B or any other example herein, where if the resulting PUCCH after UCI multiplexing is an SPS HARQ-ACK PUCCH resource that collides with a normal DL symbol or collides with a DL subband in a NOSB-FD symbol, the SPS HARQ-ACK is postponed.

[0236] Example 20B may comprise a method of a user equipment (UE), the method including: receiving a non-overlapping sub-band full duplex (NOSB-FD) configuration with time and frequency resource allocation; determining one or more parameters for transmission of uplink control information (UCI) based on the NOSB-FD configuration; and Transmitting UCI based on the determined one or more parameters.

[0237] Example 21B may comprise the method of Example 20B or any other example herein, where the one or more parameters include one or more PUCCH transmission parameters and / or UCI parameters on the PUSCH.

[0238] Example 22B may include the method of Example 20B, Example 21B, or some other example herein, where one or more parameters are configured and determined separately for different operating modes.

[0239] Example 1C includes a base station having: one or more processors; and one or more non-transitory computer-readable media containing instructions that, when executed by the one or more processors, cause the base station to: identify that a full duplex (FD) symbol is to be transmitted within a transmission period; identify one or more transmission parameters for a unidirectional transmission based on identifying that an FD symbol is to be transmitted within a transmission period; and facilitate wireless unidirectional transmission based on the one or more transmission parameters; where the FD symbol is a symbol capable of simultaneous uplink (UL) and downlink (DL) transmission within the same symbol.

[0240] Example 2C may include the base station of Example 1C and / or any other example herein, where the FD symbols are non-overlapping subband FD (NOSB-FD) symbols.

[0241] Example 3C includes the base station of example 1C and / or any other example herein, where the one or more transmission parameters include one or more DL transmission parameters or one or more UL transmission parameters.

[0242] Example 4C includes the base station of any of Examples 1C-3C and / or any other example herein, where the one or more transmission parameters are applied at all times within a transmission period.

[0243] Example 5C includes the base station of any of Examples 1C-3C and / or any other example herein, where the one or more transmission parameters are first one or more transmission parameters; the first one or more transmission parameters are applied at a first opportunity within a transmission period; and the second one or more transmission parameters are applied at a second opportunity within the transmission period.

[0244] Example 6C includes the base station of any of Examples 1C-3C and / or any other example herein, where the unidirectional transmission opportunities within a transmission period are within FD symbols and not within non-FD symbols.

[0245] Example 7C includes the base station of any of Examples 1C-3C and / or any other example herein, where the unidirectional transmission opportunities within a transmission period are within FD symbols and within non-FD symbols.

[0246] Example 8C includes a user equipment (UE) having: one or more processors; and one or more non-transitory computer-readable media containing instructions that, when executed by the one or more processors, cause the UE to: identify, in an indication received from a base station, one or more transmission parameters for a unidirectional wireless transmission, where the one or more transmission parameters are based on an identification by the base station that a full duplex (FD) symbol is to be transmitted by the base station within a transmission period, where the FD symbol is a symbol capable of simultaneous UL and DL transmission within the same symbol; and facilitate the unidirectional wireless transmission based on the one or more transmission parameters.

[0247] Example 9C includes the UE of example 8C and / or any other example herein, where the FD symbols are non-overlapping subband FD (NOSB-FD) symbols.

[0248] Example 10C includes the UE of example 8C and / or any other example herein, where the one or more transmission parameters include one or more DL transmission parameters or one or more UL transmission parameters.

[0249] Example 11C includes the UE of any of Examples 8C-10C and / or any other example herein, where the one or more transmission parameters are applied at all times within a transmission period.

[0250] Example 12C includes the UE of any of Examples 8C-10C and / or any other example herein, where the one or more transmission parameters are first one or more transmission parameters; the first one or more transmission parameters are applied to a first opportunity within a transmission period; and the second one or more transmission parameters are applied to a second opportunity within the transmission period.

[0251] Example 13C includes the UE of any of Examples 8C-10C and / or any other example herein, where the unidirectional transmission opportunities within a transmission period are within FD symbols and not within non-FD symbols.

[0252] Example 14C includes the UE of any of Examples 8C-10C and / or any other example herein, where the unidirectional transmission opportunities within a transmission period are within FD symbols and within non-FD symbols.

[0253] Example 15C includes one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to identify an indication of a non-overlapping subband full duplex (NOSB-FD) configuration, where the NOSB-FD configuration includes a time and frequency resource allocation; determine one or more parameters for transmission of uplink control information (UCI) based on the NOSB-FD configuration; and transmit UCI based on the determined one or more parameters.

[0254] Example 16C comprises one or more non-transitory computer-readable media of Example 15C and / or some other examples herein, where the one or more parameters include one or more physical uplink control channel (PUCCH) transmission parameters.

[0255] Example 17C comprises one or more non-transitory computer-readable media of Example 15C and / or some other examples herein, where the one or more parameters include one or more Physical Uplink Shared Channel (PUSCH) parameters.

[0256] Example 18C comprises a non-transitory computer-readable medium of one or more of Example 17C and / or any other example herein, where the UCI is to be transmitted on a PUSCH.

[0257] Example 19C includes one or more non-transitory computer-readable media of any of Examples 15C-18C and / or some other examples herein, where the one or more parameters are based on which of a plurality of operating modes is to be used for transmission of the UCI.

[0258] Example 20C includes one or more non-transitory computer-readable media of any of Examples 15C-18C and / or some other examples herein, where the multiple operating modes include an operating mode A that refers to transmission in NOSB-FD symbols and an operating mode B that refers to transmission in symbols that are not NOSB-FD symbols.

[0259] Example Z01 may include an apparatus having means for performing one or more elements of the method described in or related to any of Examples 1 to 20C, or any other method or process described herein.

[0260] Example Z02 may include one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 1-20C, or any other method or process described herein.

[0261] Example Z03 may include an apparatus having logic, modules, or circuitry for performing one or more elements of a method described in or relating to any of Examples 1 to 20C, or any other method or process described herein.

[0262] Example Z04 may comprise a method, technique, or process as or relating to any of Examples 1-20C, or any part or portion thereof.

[0263] Example Z05 may include an apparatus having one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process as described in or related to any of Examples 1-20C, or portions thereof.

[0264] Example Z06 may include signals as described or related to any of Examples 1-20C or any portion or part thereof.

[0265] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in, or relating to, any of Examples 1-20C, or any portion or part thereof, or otherwise described in this disclosure.

[0266] Example Z08 may include a data-encoded signal as described in or relating to any of Examples 1-20C, or any portion or part thereof, or otherwise described in this disclosure.

[0267] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in, or relating to, any of Examples 1-20C, or any portion or part thereof, or otherwise described in this disclosure.

[0268] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process as described in or related to any of Examples 1-20C, or portions thereof.

[0269] Example Z11 may have a computer program including instructions, where execution of the program by a processing element causes the processing element to perform a method, technique, or process as described in or related to any of Examples 1-20C or portions thereof.

[0270] Example Z12 may include signals in a wireless network as shown and described herein.

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

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

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

[0274] Any of the examples described above may be combined with any other example (or combination of examples) unless expressly stated otherwise. The above description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0275] Abbreviation Unless used differently herein, the terms, definitions and abbreviations may be consistent with those defined in 3GPP TR21.905 v16.0.0(2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein: 3GPP: 3rd Generation Partnership Project 4G: Fourth Generation 5G: Fifth Generation 5GC: 5G Core Network AC: Application Client ACR: Application Context Relocation ACK: Acknowledgement ACID: Application Client Identification AF: Application Features AM: Approval Mode AMBR: Aggregate Maximum Bitrate AMF: Access and Mobility Management Function AN: Access Network ANR: Automatic Neighbor Relations AOA: Angle of arrival AP: Application protocol, antenna port, access point API: Application Programming Interface APN: Access Point Name ARP: Allocation and retention priority ARQ: Automatic Repeat Request AS: Access Layer ASP: Application Service Provider ASN.1: Abstract Syntax Notation One AUSF: Authentication server function AWGN: Additive white Gaussian noise BAP: Backhaul Adaptation Protocol BCH: Broadcast Channel BER: Bit Error Ratio BFD: Beam Fault Detection BLER: Block Error Rate BPSK: Binary Phase Shift Keying BRAS: Broadband Remote Access Server BSS: Business Support System BS: Base station BSR: Buffer Status Report BW: Bandwidth BWP: Bandwidth part C-RNTI: Cell Radio Network Temporary Identity CA: Carrier Aggregation, Certificate Authority CAPEX: Capital expenditure CBRA: Contention-Based Random Access CC: Component Carrier, Country Code, Cryptographic Checksum CCA: Clear Channel Assessment CCE: Control Channel Element CCCH: Common Control Channel CE: Enhanced Coverage CDM: Content Delivery Network CDMA: Code Division Multiple Access CDR: Charging Data Request CDR: Charging Data Response CFRA: Contention-Free Random Access CG: Cell Group CGF: Charging Gateway Function CHF:Charging function CI: Cell Identity CID: Cell ID (e.g., positioning method) CIM: Common Information Model CIR: Carrier-to-Interference Ratio CK: Encryption Key CM: Connection Management, Conditional Obligations CMAS: Commercial Mobile Alarm Service CMD: Command CMS: Cloud Management System CO: Conditional Optional CoMP: Coordinated Multipoint CORESET: Control resource set COTS: Commercial Off-The-Shelf CP: Control Plane, Circular Prefix, Point of Attachment CPD: Connection Point Descriptor CPE: Customer Premises Equipment CPICH: Common Pilot Channel CQI: Channel Quality Indicator CPU: CSI processing unit, central processing unit C / R: Command / Response field bit CRAN: Cloud Radio Access Network, Cloud RAN CRB: Common Resource Block CRC: Cyclic Redundancy Check CRI: Channel State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI: Cell RNTI CS: Circuit Switch CSCF: Call Session Control Function CSAR: Cloud Services Archive CSI: Channel State Information CSI-IM:CSI interference measurement CSI-RS:CSI reference signal CSI-RSRP: CSI reference signal received power CSI-RSRQ: CSI reference signal reception quality CSI-SINR: CSI signal-to-noise and interference ratio CSMA: Carrier Sense Multiple Access CSMA / CA: CSMA with collision avoidance CSS: Common search space, cell-specific search space CTF: Charge trigger function CTS: Permit sending CW: Codeword CWS: Contention Window Size D2D: Device to Device DC: Dual connectivity, direct current DCI: Downlink control information DF: Expanded Flavor DL: DownlinkDMTF: Distributed Management Task ForceDPDK: Data Plane Development KitDM-RS, DMRS: Demodulation Reference Signal DN: Data Network DNN: Data Network Name DNAI: Data Network Access Identifier DRB: Data Radio Bearer DRS: Discovery Reference Signal DRX: Intermittent Reception DSL: Domain Specific Language. Digital Subscriber Line DSLAM: DSL Access Multiplexer DwPTS: Downlink pilot time slot E-LAN: Ethernet Local Area Network E2E: End-to-end EAS: Edge Application Server ECCA: Enhanced Clear Channel Assessment, Enhanced CCA ECCE: Enhanced Control Channel Element, Enhanced CCE ED: Energy detection EDGE: Enhanced Data Rates for GSM Evolution EAS: Edge Application Server EASID: Edge Application Server Identification ECS: Edge Configuration Server ECSP: Edge Computing Service Provider EDN: Edge Data Network EEC: Edge Enabler Client EECID: Edge Enabler Client Identification EES: Edge Enabler Server EESID: Edge Enabler Server Identification EHE: Edge Host Environment EGMF: Public Governance Management Facility EGPRS: Enhanced GPRS EIR: Equipment Identity Register eLAA: Enhanced License Assisted Access, enhanced LAA EM: Element Manager eMBB: Enhanced Mobile Broadband EMS: Element Management System eNB: Evolved NodeB, E-UTRAN NodeB EN-DC: E-UTRA-NR dual connectivity EPC: Evolved Packet Core EPDCCH: Enhanced PDCCH, Enhanced Physical Downlink Control Channel EPRE: Energy per resource element EPS: Evolved Packet System EREG: Enhanced REG, Enhanced Resource Element Group ETSI: European Telecommunications Standards Institute ETWS: Earthquake and Tsunami Warning System eUICC: Embedded UICC, Embedded Universal Integrated Circuit Card E-UTRA: Evolved UTRA E-UTRAN: Evolved UTRAN EV2X: Enhanced V2X F1AP: F1 Application Protocol F1-C: F1 control plane interface F1-U: F1 user plane interface FACCH: Fast Associated Control Channel FACCH / F: Fast Associated Control Channel / Full Rate FACCH: Fast Associated Control Channel / Half Rate FACH: Forward Access Channel FAUSCH: High Speed ​​Uplink Signaling Channel FB: Function block FBI: Feedback Information FCC: Federal Communications Commission FCCH: Frequency Correction Channel FDD: Frequency Division Duplex FDM: Frequency division multiplexing FDMA: Frequency Division Multiple Access FE: Front end FEC: Forward Error Correction FFS:For further research FFT: Fast Fourier Transform feLAA: Enhanced License Assisted Access, Enhanced LAA FN: Frame number FPGA: Field Programmable Gate Array FR: Frequency range FQDN: Fully Qualified Domain Name G-RNTI: GERAN Radio Network Transient Identity GERAN: GSM Edge RAN, GSM Edge Radio Access Network GGSN: Gateway GPRS Support Node GLONASS: Global Navigation Satellite System gNB: Next generation NodeB gNB-CU: gNB centralized unit, next generation NodeB centralized unit gNB-DU: gNB distributed unit, next generation NodeB distributed unit GNSS: Global Navigation Satellite System GPRS: General Packet Radio Service GPSI: General Purpose Public Subscription Identifier GSM: Global System for Mobile Communications, Groupe Special Mobile GTP: GPRS Tunneling Protocol GTP-U: GPRS Tunneling Protocol for the User Plane GTS: Go-to-sleep signal (related to WUS) GUMMEI: Globally Unique MME Identifier GUTI: Globally Unique Temporary UE Identity HARQ: Hybrid ARQ, Hybrid Automatic Repeat Request HANDO: Handover HFN: Hyperframe Number HHO: Hard Handover HLR: Home Location Register HN: Home Network HO: Handover HPLMN: Home Public Land Mobile Network HSDPA: High Speed ​​Downlink Packet Access HSN: Hopping sequence number HSPA: High Speed ​​Packet Access HSS: Home Subscriber Server HSUPA: High Speed ​​Uplink Packet Access HTTP: Hypertext Transfer Protocol HTTPS: Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, i.e. port 443) I-Block: Information Block ICCID: Integrated Circuit Card Identification IAB: Integrated Access and Backhaul ICIC: Inter-cell interference coordination ID: Identity, Identifier IDFT: Inverse Discrete Fourier Transform IE: Information Element IBE: In-band emission IEEE: Institute of Electrical and Electronics Engineers IEI: Information Element Identifier IEIDL: Information element identifier data length IETF: Internet Engineering Task Force IF: Infrastructure IIOT: Industrial Internet of Things IM: Interference Measurement, Intermodulation, IP Multimedia IMC: IMS Certificate IMEI: International Mobile Equipment Identity IMGI: International Mobile Group Identity IMPI: IP Multimedia Private Identity IMPU: IP Multimedia Public Identity IMS: IP Multimedia Subsystem IMSI: International Mobile Subscriber Identity IoT: Internet of Things IP: Internet Protocol Ipsec: IP Security, Internet Protocol Security IP-CAN: IP Connectivity Access Network IP-M: IP multicast IPv4: Internet Protocol version 4 IPv6: Internet Protocol version 6 IR: Infrared IS: Synchronous IRP: Integration Reference Point ISDN (registered trademark): Integrated Services Digital Network ISIM: IM Service Identity Module ISO: International Organization for Standardization ISP: Internet Service Provider IWF: Interworking Function I-WLAN: Interworking WLAN Constraint length of superimposed code, USIM: individual key kB: kilobyte (1000 bytes) kbps: kilobits per second Kc: encryption key Ki: Individual subscriber authentication key KPI: Key Performance Indicator KQI: Key Quality Indicator KSI: Key Set Identifier ksps: kilosymbols per second KVM: Kernel Virtual Machine L1: Layer 1 (physical layer) L1-RSRP: Layer 1 reference signal received power L2: Layer 2 (Data Link Layer) L3: Layer 3 (network layer) LAA: License Assisted Access LAN: Local Area Network LADN: Local Area Data Network LBT: Listen Before Talk LCM: Lifecycle Management LCR: Low Chip Rate LCS: Location Services LCID: Logical Channel ID LI: Layer Indicator LLC: Logical Link Control, Low Layer Compatibility LMF: Location management function LOS: Line of sight LPLMN: Local PLMN LPP: LTE Positioning Protocol LSB: least significant bit LTE: Long Term Evolution LWA: LTE-WLAN aggregation LWIP: LTE / WLAN radio level integration with IPsec tunnels LTE: Long Term Evolution M2M: Machine to Machine MAC: Medium Access Control (in the context of protocol layering) MAC: Message Authentication Code (Security / Encryption Context) MAC-A: MAC used for authentication and key agreement (TSG T WG3 context) MAC-I: MAC used for data integrity of signaling messages (TSG T WG3 context) MANO: Management and Orchestration MBMS: Multimedia Broadcast and Multicast Service MBSFN: Multimedia Broadcast Multicast Service Single Frequency Network MCC: Mobile Country Code MCG: Master Cell Group MCOT: Maximum Channel Occupancy Time MCS: Modulation and Coding Scheme MDAF: Managed Data Analysis Facility MDAS: Managed Data Analysis Services MDT: Minimizing Drive Testing ME: Mobile device MeNB: Master eNB MER: Message Error Ratio MGL: Measurement gap length MGRP: Measurement Gap Repetition Period MIB: Master Information Block, Management Information Base MIMO: Multiple Input Multiple Output MLC: Mobile Location Center MM: Mobility Management MME: Mobility Management Entity MN: Master node MNO: Mobile Network Operator MO: Measurement object, mobile originated MPBCH: MTC Physical Broadcast Channel MPDCCH: MTC physical downlink control channel MPDSCH: MTC physical downlink shared channel MPRACH: MTC Physical Random Access Channel MPUSCH: MTC physical uplink shared channel MPLS: Multiprotocol Label Switching MS: Mobile station MSB: Most significant bit MSC: Mobile Switching Center MSI: Minimum System Information, MCH Scheduling Information MSID: Mobile Station Identifier MSIN: Mobile Station Identification Number MSISDN: Mobile Subscriber ISDN Number MT: Mobile Terminated, Mobile Termination MTC: Machine Type Communication mMTC: Massive MTC, Massive Machine Type Communication MU-MIMO: Multi-User MIMO MWUS: MTC wake-up signal, MTC WUS NACK: Negative Acknowledgement NAI: Network Access Identifier NAS: Non-Access Stratum, Non-Access Stratum layer NCT: Network Connectivity Topology NC-JT: Non-coherent joint transmission NEC: Network function release NE-DC: NR-E-UTRA dual connectivity NEF: Network Publishing Function NF: Network function NFP: Network Forwarding Path NFPD: Network Forwarding Path Descriptor NFV: Network Functions Virtualization NFVI: NFV Infrastructure NFVO: NFV Orchestrator NG: Next Gen NGEN-DC: NG-RAN E-UTRA-NR dual connectivity NM: Network Manager NMS: Network Management System N-PoP: Network Point of Presence NMIB, N-MIB: Narrowband MIB NPBCH: Narrowband Physical Broadcast Channel NPDCCH: Narrowband Physical Downlink Control Channel NPDSCH: Narrowband Physical Downlink Shared Channel NPRACH: Narrowband Physical Random Access Channel NPUSCH: Narrowband Physical Uplink Shared Channel NPSS: Narrowband Primary Synchronization Signal NSSS: Narrowband Secondary Synchronization Signal NR: New Radio, Near-Field Relations NRF:NF Repository Function NRS: Narrowband Reference Signal NS: Network Services NSA: Non-standalone operation mode NSD: Network Service Descriptor NSR: Network Service Record NSSAI: Network Slice Selection Aid Information S-NNSAI Single NSSAI (Single-NSSAI) NSSF: Network Slice Selection Function NW:Network NWUS: Narrowband wake-up signal, narrowband WUS NZP: Non-zero power O&M: Operation and Maintenance ODU2: Optical Channel Data Unit Type 2 OFDM: Orthogonal Frequency Division Multiplexing OFDMA: Orthogonal Frequency Division Multiple Access OOB: Out of Band OOS: Out of sync OPEX: Operating cost OSI:Other Systems Information OSS: Operational Support System OTA: Over the Air PAPR: Peak to Average Power Ratio PAR: Peak to Average Ratio PBCH: Physical Broadcast Channel PC: Power control, personal computer PCC: Primary Component Carrier, Primary CC P-CSCF: Proxy CSCF PCell: Primary cell PCI: Physical Cell ID, Physical Cell Identity PCEF: Policy and Charging Enforcement Function PCF: Policy Control Function PCRF: Policy Control and Charging Rules Function PDCP: Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer PDCCH: Physical Downlink Control Channel PDCP: Packet Data Convergence Protocol PDN: Packet Data Network, Public Data Network PDSCH: Physical Downlink Shared Channel PDU: Protocol Data Unit PEI: Permanent Equipment Identifier PFD: Packet Flow Description P-GW: PDN Gateway PHICH: Physical Hybrid ARQ Indicator Channel PHY: Physical layer PLMN: Public Land Mobile Network PIN: Personal Identification Number PM: Performance measurement PMI: Precoding Matrix Indicator PNF: Physical Network Function PNFD: Physical Network Function Descriptor PNFR: Physical Network Function Record POC: PTT over Cellular PP, PTP: Point-to-Point PPP: Point-to-Point Protocol PRACH:Physical RACH PRB: Physical Resource Block PRG: Physical resource block group ProSe: Proximity Services, Proximity-Based Services PRS: Positioning Reference Signal PRR: Packet Receive Radio PS: Packet service PSBCH: Physical Sidelink Broadcast Channel PSDCH: Physical Sidelink Downlink Channel PSCCH: Physical Sidelink Control Channel PSSCH: Physical Sidelink Shared Channel PSCell: Primary SCell PSS: Primary Synchronization Signal PSTN: Public Switched Telephone Network PT-RS: Phase tracking reference signal PTT: Push to talk PUCCH: Physical uplink control channel PUSCH: Physical uplink shared channel QAM: Quadrature Amplitude Modulation QCI: QoS Class of Identifier QCL: Quasi-collocation QFI: QoS flow ID, QoS flow identifier QoS: Quality of Service QPSK: Quadrature (four-phase) phase shift keying QZSS: Quasi-Zenith Satellite System RA-RNTI: Random Access RNTI RAB: Radio Access Bearer, Random Access Burst RACH: Random Access Channel RADIUS: Remote Authentication Dial-In User Service RAN: Radio Access Network RAND: Random number (used for authentication) RAR: Random Access Response RAT: Radio Access Technology RAU: Routing Area Update RB: Resource block, radio bearer RBG: Resource Block Group REG: Resource Element Group Rel: Release REQ:Request RF: Radio Frequency RI: Rank Indicator RIV: Resource Indicator Value RL: Radio Link RLC: Radio Link Control, Radio Link Control Layer RLC AM: RLC acknowledged mode RLC UM: RLC unacknowledged mode RLF: Radio Link Failure RLM: Radio Link Monitoring RLM-RS: Reference signal for RLM RM: Registration Management RMC: Reference Measurement Channel RMSI Remaining MSI, Minimum Remaining System Information RN: Relay node RNC: Radio Network Controller RNL: Radio Network Layer RNTI: Radio Network Temporary Identifier ROHC: Robust Header Compression RRC: Radio Resource Control, Radio Resource Control Layer RRM: Radio Resource Management RS: Reference signal RSRP: Reference signal received power RSRQ: Reference signal reception quality RSSI: Received Signal Strength Indicator RSU: Roadside Unit RSTD: Reference signal time difference RTP: Real Time Protocol RTS: Request to send RTT: Round Trip Time Rx: Reception, receiving, receiver S1AP: S1 Application Protocol S1-MME: S1 for control plane S1-U: S1 for user plane S-CSCF: Serving CSCF S-GW: Serving Gateway S-RNTI: SRNC Radio Network Transient Identity S-TMSI:SAE Temporary Mobile Station Identifier SA: Standalone operation mode SAE: System Architecture Evolution SAP: Service Access Point SAPD: Service Access Point Descriptor SAPI: Service Access Point Identifier SCC: Secondary Component Carrier, Secondary CC SCell: Secondary cell SCEF: Service Function Exposure Function SC-FDMA: Single Carrier Frequency Division Multiple Access SCG: Secondary Cell Group SCM: Security Context Management SCS: Subcarrier spacing SCTP: Stream Control Transmission Protocol SDAP: Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer SDL: Auxiliary Downlink SDNF: Structured Data Storage Network Functions SDP: Session Description Protocol SDSF: Structured Data Storage Facility SDT: Small Data Transmission SDU: Service Data Unit SEAF: Security Anchor Function SeNB: Secondary eNB SEPP: Security Edge Protection Proxy SFI: Slot Format Index SFTD: Space-Frequency Time Diversity, SFN and Frame Timing Difference SFN: System Frame Number SgNB: Secondary gNB SGSN: Serving GPRS Support Node S-GW: Serving Gateway SI: System Information SI-RNTI: System Information RNTI SIB: System Information Block SIM: Subscriber Identity Module SIP: Session Initiation Protocol SiP: System in Package SL: Side link SLA: Service Level Agreement SM: Session Management SMF: Session Management Facility SMS: Short Message Service SMSF: SMS function SMTC: SSB-based measurement timing configuration SN: Secondary node, sequence number SoC: System on Chip SON: Self-organizing network SpCell: Special cell SP-CSI-RNTI: Semi-Persistent CSI RNTI SPS: Semi-persistent scheduling SQN: Sequence number SR: Scheduling Request SRB: Signalling Radio Bearer SRS: Sounding Reference Signal SS: Synchronization signal SSB: Synchronization signal block SSID: Service Set Identifier SS / PBCH Block SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator SSC: Session and Service Continuity SS-RSRP: Synchronization signal-based reference signal received power SS-RSRQ: Synchronization signal-based reference signal reception quality SS-SINR: Synchronization signal-based signal-to-noise-and-interference ratio SSS: Secondary Synchronization Signal SSSG: Search Space Set Group SSSIF: Search Space Set Indicator SST: Slice / Service Type SU-MIMO: Single User MIMO SUL: Auxiliary Uplink TA: Timing advance, tracking area TAC: Tracking Area Code TAG: Timing Advance Group TAI: Tracking Area Identity TAU: Tracking Area Update TB: Transport block TBS: Transport Block Size TBD: undefined TCI: Transmission Configuration Indicator TCP: Transmission Communication Protocol TDD: Time division duplex TDM: Time division multiplexing TDMA: Time Division Multiple Access TE: Terminal equipment TEID: Tunnel Endpoint Identifier TFT: Traffic Flow Template TMSI: Temporary Mobile Subscriber Identity TNL: Transport Network Layer TPC: Transmit Power Control TPMI: Transmit Precoding Matrix Indicator TR: Technical report TRP, TRxP: Transmission Receiving Point TRS: Tracking Reference Signal TRx: Transmitter / Receiver TS: Technical specifications, technical standards TTI: Transmission Time Interval Tx: Transmission, Transmitting, Transmitter U-RNTI: UTRAN Radio Network Temporary Identity UART: Universal Asynchronous Receiver and Transmitter UCI: Uplink Control Information UE: User Equipment UDM: Unified Data Management UDP: User Datagram Protocol UDSF: Unstructured Data Storage Network Functions UICC: Universal Integrated Circuit Card UL: Uplink UM: Unacknowledged Mode UML: Unified Modeling Language UMTS: Universal Mobile Telecommunications System UP: User plane UPF: User Plane Function URI: Uniform Resource Identifier URL: Uniform Resource Locator URLLC: Ultra-reliable and low latency USB: Universal Serial Bus USIM: Universal Subscriber Identity Module USS:UE specific search space UTRA: UMTS Terrestrial Radio Access UTRAN: Universal Terrestrial Radio Access Network UwPTS: Uplink pilot time slot V2I: Vehicle to Infrastructure V2P: Pedestrian-to-Vehicle V2V: Vehicle-to-vehicle distance V2X: Vehicle to Everything VIM: Virtualization Infrastructure Manager VL: Virtual Link VLAN: Virtual LAN, Virtual Local Area Network VM: Virtual machine VNF: Virtualized Network Functions VNFFG: VNF forwarding graph VNFFGD: VNF forwarding graph descriptor VNFM: VNF Manager VoIP: Voice over IP, Voice over Internet Protocol VPLMN: Visited Public Land Mobile Network VPN: Virtual Private Network VRB: Virtual Resource Block WiMAX(R): Worldwide Interoperability for Microwave Access WLAN: Wireless Local Area Network WMAN: Wireless Metropolitan Area Network WPAN: Wireless Personal Area Network X2-C: X2-Control Plane X2-U: X2-User Plane XML: Extensible Markup Language XRES: Expected User Response XOR: Exclusive OR ZC:Zadoff-Chu ZP: Zero Power term For purposes of this document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0276] 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 capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, a circuitry 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 circuits used in an electrical or electronic system) and program code used to perform the functions of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0277] As used herein, the term "processor circuitry" refers to, is a part of, or includes a circuitry capable of continuously and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The 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, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes. The processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The 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 "processor circuitry." 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.

[0278] 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, wireless equipment, reconfigurable wireless equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0279] 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 may be 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, and / or NFVI, etc.

[0280] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Additionally, 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.

[0281] 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.

[0282] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components in a computing environment, and / or physical or virtual components in a particular device, such as, for example, computer devices, mechanical devices, 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, databases and applications, and / or workload units. A "hardware resource" may refer to computational, storage, and / or network resources provided by a physical hardware element. A "virtualized resource" may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The term "network resource" or "communication resource" may refer to resources that are accessible by a computer device / system via a communication network. The term "system resource" may refer to any type 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.

[0283] 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.

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

[0285] 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, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean 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 contact with each other by means of communication, including through a wired or other interconnected connection scheme, and / or through a wireless communication channel or link.

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

[0287] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0288] The term "SSB" refers to SS / PBCH block.

[0289] The term "primary cell" refers to an MCG cell operating on a primary frequency on which the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0290] The term "primary SCG cell" refers to an SCG cell to which the UE performs random access when performing a Reconfiguration with Sync procedure for DC operation.

[0291] The term "secondary cell" refers to a cell that provides additional radio resources over a special cell for UEs configured with CA.

[0292] The term "secondary cell group" refers to a subset of a serving cell, including a PSCell, and zero or more secondary cells for a UE configured with a DC.

[0293] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell, including the primary cell.

[0294] The term "serving cell" or "serving cells" refers to a set of cells including special cells and all secondary cells for a UE in RRC_CONNECTED configured with CA / .

[0295] The term "special cell" refers to a PCell of an MCG or a PSCell of an SCG in case of DC operation; otherwise, the term "special cell" refers to a Pcell.

Claims

1. 13. A base station comprising: one or more processors; and One or more non-transitory computer-readable media that, when executed by the one or more processors, cause the base station to: Identifying that a full duplex (FD) symbol is to be transmitted within a transmission period; identifying one or more transmission parameters for a unidirectional transmission based on the identification that an FD symbol is to be transmitted within the transmission period; and facilitating wireless one-way transmission based on the one or more transmission parameters; Here, the FD symbol is a symbol that allows simultaneous uplink (UL) and downlink (DL) transmission within the same symbol. One or more non-transitory computer-readable media containing the instructions A base station comprising:

2. The base station of claim 1 , wherein the FD symbols are non-overlapping subband FD (NOSB-FD) symbols.

3. The base station of claim 1 , wherein the one or more transmission parameters include one or more DL transmission parameters or one or more UL transmission parameters.

4. The base station according to any one of claims 1 to 3, wherein the one or more transmission parameters are applied at every opportunity within the transmission period.

5. the one or more transmission parameters are first one or more transmission parameters; the first one or more transmission parameters are applied at a first opportunity within the transmission period; and a second one or more transmission parameters are applied at a second opportunity within the transmission period; A base station according to any one of claims 1 to 3.

6. The base station according to any one of claims 1 to 3, wherein the one-way transmission opportunities within the transmission period are within FD symbols and not within non-FD symbols.

7. The base station according to any one of claims 1 to 3, wherein the unidirectional transmission opportunities within the transmission period are within FD symbols and non-FD symbols.

8. A user equipment (UE) comprising: one or more processors; and One or more non-transitory computer-readable media that, when executed by the one or more processors, cause the UE to: identifying, in the indication received from the base station, one or more transmission parameters for the one-way wireless transmission; wherein the one or more transmission parameters are based on an identification by the base station that a full duplex (FD) symbol is to be transmitted by the base station within a transmission period, where the FD symbol is a symbol capable of simultaneous UL and DL transmission within the same symbol; and Facilitating the one-way wireless transmission based on the one or more transmission parameters. One or more non-transitory computer-readable media containing the instructions A user equipment (UE) comprising:

9. The UE of claim 8 , wherein the FD symbols are non-overlapping subband FD (NOSB-FD) symbols.

10. The UE of claim 8 , wherein the one or more transmission parameters include one or more DL transmission parameters or one or more UL transmission parameters.

11. The UE according to any one of claims 8 to 10, wherein the one or more transmission parameters are applied at all occasions within the transmission period.

12. the one or more transmission parameters are first one or more transmission parameters; the first one or more transmission parameters are applied at a first opportunity within the transmission period; and a second one or more transmission parameters are applied at a second opportunity within the transmission period; A UE according to any one of claims 8 to 10.

13. The UE of any one of claims 8 to 10, wherein the unidirectional transmission opportunities within the transmission period are within FD symbols and not within non-FD symbols.

14. The UE of any one of claims 8 to 10, wherein the unidirectional transmission opportunities within the transmission period are within FD symbols and within non-FD symbols.

15. One or more non-transitory computer-readable media that, when executed by one or more processors of a user equipment (UE), cause the UE to: identifying an indication of a non-overlapping subband full duplex (NOSB-FD) configuration, where the NOSB-FD configuration includes a time and frequency resource allocation; determining one or more parameters for transmission of uplink control information (UCI) based on the NOSB-FD configuration; and Transmitting the UCI based on the determined one or more parameters. One or more non-transitory computer-readable media containing the instructions.

16. 16. The one or more non-transitory computer-readable media of claim 15, wherein the one or more parameters include one or more Physical Uplink Control Channel (PUCCH) transmission parameters.

17. 20. The one or more non-transitory computer-readable media of claim 16, wherein the one or more parameters are identified prior to execution of a multiplexing procedure for the UCI.

18. 17. The one or more non-transitory computer-readable media of claim 16, wherein the one or more parameters are identified after execution of a multiplexing procedure for the UCI.

19. 16. The one or more non-transitory computer-readable media of claim 15, wherein the one or more parameters include one or more Physical Uplink Shared Channel (PUSCH) parameters.

20. The one or more parameters are based on which of a plurality of operating modes is to be used for the transmission of the UCI, where the plurality of operating modes are: Mode A of operation for transmission within the NOSB-FD symbol; and NOSB - Operational mode B for transmission in symbols that are not FD symbols 19. One or more non-transitory computer readable media according to any one of claims 15 to 18, comprising:

Images