Physical random access channel (PRACH) and physical uplink control channel (PUCCH) repetitions for subband non-overlapping full duplex (SBFD) operation

Abstract

Various embodiments herein provide techniques relate to a user equipment (UE) configured to identify first configuration information related to uplink (UL) transmission on one or more subband non-overlapping full duplex (SBFD) symbols and second configuration information related to UL transmission on one or more non-SBFD symbols. The UE may be further configured to encode, based on the first configuration information and the second configuration information, a plurality of uplink (UL) transmissions. Other embodiments may be described and / or claimed.

Description

[0001] PHYSICAL RANDOM ACCESS CHANNEL (PRACH) AND PHYSICAL UPLINK CONTROL CHANNEL (PUCCH) REPETITIONS FOR SUBBAND NONOVERLAPPING FULL DUPLEX (SBFD) OPERATION

[0002] CROSS REFERENCE TO RELATED APPLICATION

[0003] The present application claims priority to U.S. Provisional Patent Application No. 63 / 614,243, which was filed December 22, 2023.

[0004] BACKGROUND

[0005] Various embodiments generally may relate to the field of wireless communications.

[0006] BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

[0008] Figure 1 illustrates an example of subband non-overlapping full duplex (SBFD) for NR, in accordance with various embodiments.

[0009] Figure 2 illustrates an example of physical uplink control channel (PUCCH) repetitions in both SBFD and non-SBFD symbols, in accordance with various embodiments.

[0010] Figure 3 illustrates an example of PUCCH repetitions in only non-SBFD symbols, in accordance with various embodiments.

[0011] Figure 4 illustrates an example of PRACH repetitions in both non-SBFD and SBFD symbols, in accordance with various embodiments.

[0012] Figure 5 illustrates an example of PRACH repetitions in only non-SBFD symbols, in accordance with various embodiments.

[0013] Figure 6 schematically illustrates an example of a wireless network, in accordance with various embodiments.

[0014] Figure 7 schematically illustrates example components of a wireless network, in accordance with various embodiments.

[0015] Figure 8 is a block diagram illustrating example components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

[0016] Figure 9 schematically illustrates an alternative example of a wireless network, in accordance with various embodiments.

[0017] Figure 10 depicts an example procedure for practicing the various embodiments discussed herein.

[0018] Figure 11 depicts an alternative example procedure for practicing the various embodiments discussed herein.

[0019] Figure 12 depicts an alternative example procedure for practicing the various embodiments discussed herein.

[0020] DETAILED DESCRIPTION

[0021] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the 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 the purposes of the present document, the phrases “A or B” and “A / B” mean (A), (B), or (A and B).

[0022] Time Division Duplex (TDD) may be used in commercial new radio (NR) deployments. As used herein, TDD may refer to a duplexing scheme wherein one or more time domain resource(s) is / are split between downlink (DL) and uplink (UL) symbols. Allocation of a limited time duration for the UL in TDD may result in reduced coverage and increased latency for a given target data rate. To improve the performance for UL transmission in TDD system, simultaneous transmission and reception of DL symbols and UL symbols, respectively, may be considered. This simultaneous transmission / reception may also be referred to herein as “full duplex communication.’’ In this regard, subband non-overlapping full duplex (SBFD) operation may be considered.

[0023] For SBFD, within a carrier bandwidth, some bandwidth can be allocated as UL, while some bandwidth can be allocated as DL within the same symbol. However, when the UL and DL is allocated within the same symbol (i.e., within the same time domain), the UL and DL resources are non-overlapping in frequency domain. Under this operational mode, at a given symbol a base station such as a gNodeB (gNB) may simultaneously transmit DL signals and receive UL signals. In some embodiments, however, the UE may only be configured to transmit or receive in a given symbol, and may not be configured to perform both functions simultaneously.

[0024] Figure 1 illustrates one example of subband non-overlapping full duplex (SBFD) for a NR system. In the figure, in the SBFD symbols, part of the carrier bandwidth may be allocated for DL while another part of the carrier bandwidth may be allocated for UL.

[0025] In order to improve the uplink coverage, repetitions of UL transmission including physical uplink control channel (PUCCH) and physical random access channel (PRACH) may be employed. For SBFD operation, separate configuration of uplink transmissions on SBFD symbols and non-SBFD symbols may be configured in some embodiments. In this case, it may be desirable to enable the repetitions of uplink transmission including PUCCH and PRACH in case of SBFD operations. Embodiments herein may relate to PRACH and / or PUCCH repetitions for subband non-overlapping full duplex (SBFD) operation.

[0026] PUCCH repetitions for SBFD operation

[0027] Example embodiments related to PUCCH repetitions for SBFD operation may include one or more of the following:

[0028] In one embodiment, separate PUCCH resource configuration may be configured for a UE for PUCCH transmission in SBFD symbols and non-SBFD symbols.

[0029] In one option, if a UE does not have dedicated PUCCH resource configuration, a UE can be provided with separate PUCCH resource sets which are indicated by separate pucch- ResourceCommon radio resource control (RRC) information element. In this case, a first pucch- ResourceCommon is configured for a first PUCCH resource set for non-SBFD symbols while a second pucch-ResourceCommon is configured for a second PUCCH resource set for SBFD symbols.

[0030] Further, if the second pucch-ResourceCommon is not configured, same PUCCH resource set indicated by the first pucch-ResourceCommon is used for both SBFD and non-SBFD symbols.

[0031] In some aspects, a physical resource block (PRB) location of the PUCCH transmission in non-SBFD symbols and SBFD symbols can be determined in accordance with the active UL bandwidth part (BWP) that is associated with non-SBFD symbols and in accordance with the UL subband (SB) that is associated with SBFD symbols, respectively.

[0032] In another embodiment, for PUCCH with repetitions, the PUCCH repetitions are transmitted on the PUCCH resources which are configured for both non-SBFD and SBFD symbols. For this option, the PUCCH resource configuration for the PUCCH repetitions is determined in accordance with the PUCCH resource configuration from the first PUCCH repetition.

[0033] In some aspects, the number of repetitions for the PUCCH transmission is determined in accordance with the PUCCH resource in the first PUCCH repetition.

[0034] In one option, for PUCCH carrying hybrid automatic repeat request (HARQ)- acknowledgement (ACK) feedback in response to Msg4 transmission, if only one value is configured for the PUCCH repetition via numberOfPUCCHforMsg4HARQACK-RepetitionsList, the number of repetitions for the PUCCH transmission on both non-SBFD and SBFD symbols is determined in accordance with the one value.

[0035] In another option, for PUCCH carrying HARQ-ACK feedback in response to Msg4 transmission, if more than one values are configured for the PUCCH repetitions via mimberOfPUCCHforMsg4HARQACK-RepetitionsList, the number of repetition for the PUCCH transmission on both non-SBFD and SBFD symbols is determined based on the value that is indicated by Downlink assignment index field in the DCI format l_0 with CRC scrambled by a temporary cell (TC) radio network temporary identifier (RNTI).

[0036] In one option, for PUCCH carrying HARQ-ACK feedback in response to Msg4 transmission, a UE can be provided with separate list of possible values for number of the PUCCH repetitions by separate numberOfPUCCHforMsg4HARQACK-RepetitionsList wherein a first numberOfRUCCHforMsg4HARQACK-RepetitionsList is configured for non-SBFD symbols while a second mimberOJPUCCHforMsg4HARQACK-RepetitionsList is configured for SBFD symbols.

[0037] In some aspects, UE applies the number of PUCCH repetitions corresponding to the first numberOfPUCCHforMsg4HARQACK-RepetitionsList if the first symbol of the PUCCH transmission is non-SBFD symbol, while UE applies the number of PUCCH repetitions corresponding to the second numberOfPUCCHforMsg4HARQACK-RepetitionsList if the first symbol of the PUCCH transmission is SBFD symbol.

[0038] In another option, a single value of number of repetitions of PUCCH may be provided that indicates the total number of repetitions of PUCCH spanning PUCCH transmissions in non-SBFD and SBFD symbols.

[0039] In some aspects, the above options can also apply for the PUCCH other than the PUCCH carrying HARQ-ACK feedback in response to Msg4 transmission, if a UE does not have dedicated PUCCH resource configuration.

[0040] In addition, the PUCCH resource index that is determined for the first PUCCH repetition is applied for the subsequent PUCCH repetitions in non-SBFD and / or SBFD symbols.

[0041] Further, in case of single-transmit / receive point (TRP) operation, the spatial relation or beam of PUCCH transmission for the subsequent PUCCH repetitions after the first PUCCH repetition is determined based on the spatial relation or beam of the first PUCCH transmissions. In one example, same spatial relation or beam as determined for the first PUCCH repetition is applied for that of the subsequent PUCCH repetitions.

[0042] Figure 2 illustrates one example of PUCCH repetitions in SBFD and non-SBFD symbols when a UE does not have dedicated PUCCH resource configuration. In the figure, two PUCCH repetitions are configured, and are transmitted in both non-SBFD and SBFD symbols. Further, the PUCCH resource index that is determined in the first slot is applied for the PUCCH repetition in the second slot. The PRB location of the PUCCH repetition in non-SBFD symbols and SBFD symbols is determined in accordance with the active UL bandwidth part (B WP) or the UL subband (SB) that is associated with non-SBFD symbols and SBFD symbols, respectively.

[0043] In another embodiment, for PUCCH with repetitions, the PUCCH repetitions are transmitted on the PUCCH resources which are configured for either non-SBFD or SBFD symbols. In this case, if the first PUCCH repetition is determined to be transmitted on the non- SBFD symbols, the subsequent PUCCH repetitions are also transmitted on the non-SBFD symbols. If the first PUCCH repetition is determined to be transmitted on the SBFD symbols, the subsequent PUCCH repetitions are also transmitted on the SBFD symbols.

[0044] Figure 3 illustrates one example of PUCCH repetitions in only non-SBFD symbols. In the example, 2 PUCCH repetitions are configured. Further, the first PUCCH repetition is determined to be transmitted on the non-SBFD symbol in the first slot. In this case, the second PUCCH repetition is also transmitted in the non-SBFD symbol in the third slot.

[0045] In another embodiment, when PUCCH is a sub-slot PUCCH, e.g., when subslotLengthForPUCCH is provided in PUCCH-Config, and sub-slot repetitions are enabled or disabled, the PUCCH resource determination for initial transmission and repetitions may apply the embodiments provided above for PUCCH transmissions / repetitions in both SBFD and non- SBFD symbols, or in either SBFD or non-SBFD symbols, with number of symbols in a slot for PUCCH equal to a sub-slot length provided by subslotLengthForPUCCH.

[0046] PRACH repetitions for SBFD operation

[0047] Example embodiments of PRACH repetitions for SBFD operation are provided as follows: In one embodiment, separate PRACH configurations may be configured for a UE in SBFD symbols and non-SBFD symbols.

[0048] In some aspects, UE may be provided with separate RACH-ConfigGeneric for SBFD symbols and non-SBFD symbols, respectively. In this case, a first RACH-ConfigGeneric may be configured for non-SBFD symbols, while a second RACH-ConfigGeneric may be configured for SBFD symbols.

[0049] In some aspects, the second PRACH configuration may be provided to a UE for PRACH transmissions in SBFD symbols or in both SBFD and non-SBFD symbols when in RRC_CONNECTED mode. Alternatively, the second PRACH configuration may be provided to a UE for PRACH transmission in SBFD or across both SBFD and non-SBFD symbols in each of RRC_CONNECTED and RRC_IDLE and RRC_INACTIVE states. Further, for the latter option, the second PRACH configuration may be provided to the UE as part of the RRCRelease message.

[0050] Further, if the second RACH-ConfigGeneric is not configured, same PRACH configuration indicated by the first RACH-ConfigGeneric is used for both SBFD and non-SBFD symbols. In this case, PRACH occasions that are within the UL subband and SBFD symbols can be considered as valid PRACH occasions and can be used for PRACH transmission. In addition, PRACH occasions that collide with DL subband in SBFD symbols can be considered as invalid PRACH occasions and cannot be used for PRACH transmissions.

[0051] For this option, UE may continue to use the configurations for random access which are based on the initial PRACH transmission on either SBFD or non-SBFD symbols. In particular, when a UE transmits the PRACH preamble using the PRACH configuration in non-SBFD symbols, UE continues to use the configurations during random access based on the PRACH configurations on non-SBFD symbols or vice versa.

[0052] In one example, when a UE transmits the PRACH preamble using the PRACH configuration in SBFD symbols, a UE attempts to detect a DCI format l_0 with CRC scrambled by a corresponding RA-RNTI during a window which is configured by ra-ResponseWindow in accordance with the PRACH configurations in SBFD symbols.

[0053] In another example, when a UE transmits the PRACH preamble using the PRACH configuration in SBFD symbols, UE may apply the power ramping step size in accordance with the PRACH configuration on SBFD symbols that may be different from that configured for PRACH transmissions in non-SBFD symbols.

[0054] Further, UE may only switch to the PRACH configurations for PRACH retransmission if the number of PRACH retransmission reaches to a maximum value, which may be configured by higher layers. In this case, if K PRACH retransmissions in accordance with the PRACH configuration on SBFD symbols are not successful, UE may switch to PRACH configuration on non-SBFD symbols for PRACH transmissions.

[0055] In another embodiment, for PRACH with repetitions, the PRACH repetitions may be transmitted on the valid PRACH occasions (which may also be referred to as “RACH occasions” or “ROs”) that are configured for both SBFD and non-SBFD symbols.

[0056] In one option, if each RO is associated with one synchronization signal block (SSB) for PRACH configuration in both SBFD and non-SBFD symbols, all ROs in both SBFD and non- SBFD symbols that are associated with the same synchronization signal block (SSB) index and have same starting resource block (RB) as the starting RO can form a RO group. As an example of this case, an RO may correspond to symbols - some of which are SBFD symbols and others are non-SBFD symbols. Further, for this example, the RO is mapped to the same PRBs in the frequency dimension in both SBFD and non-SBFD symbols.

[0057] In another option, if each RO is associated with multiple SSB for PRACH configuration in both SBFD and non-SBFD symbols, all ROs in both SBFD and non-SBFD symbols that are associated with the same SSB indexes and each same SSB index of the SSB indexes is associated with the same preambles, and have same starting RB as the starting RO can form a RO group.

[0058] Further, the first valid PRACH occasion of the first set is the first valid PRACH occasion and the first valid PRACH occasion of subsequent sets, if any, is determined according to an ordering of valid PRACH occasions in both SBFD and non-SBFD symbols

[0059] • first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions in both SBFD and non-SBFD symbols

[0060] • second, in increasing order of time resource indexes for time multiplexed PRACH occasions in both SBFD and non-SBFD symbols

[0061] In some aspects, for PRACH repetitions in both SBFD and non-SBFD symbols, a time period, starting from frame 0, is the smallest integer number of association pattern periods such that at least one set of valid PRACH occasions for both SBFD and non-SBFD symbols for each of the / VyfBSS / PBCH block indexes can be determined within the time period for all configured number of preamble repetitions. The set(s) of valid PRACH occasions for both SBFD and non- SBFD symbols for each configured number of preamble repetitions repeats every time period.

[0062] As a further extension, to enable PRACH repetitions in both SBFD and non-SBFD symbols, UE may expect a same PRACH configuration for one or more parameters, which may include a number of frequency division multiplexed (FDM’ed) PRACH occasions and / or a SSB to RO mapping ratio.

[0063] Figure 4 illustrates one example of PRACH repetitions in both non-SBFD and SBFD symbols. In the figure, 2 PRACH repetitions are configured and determined. 2 SSBs are configured and 1 SSB is associated with 1 PRACH occasion. In this case, UE may transmit two PRACH repetitions on RO#0 on non-SBFD symbols and RO#0 in SBFD symbols which are associated with SSB#0.

[0064] In another option, if each RO is associated with one SSB for PRACH configuration in both SBFD and non-SBFD symbols, all ROs in both SBFD and non-SBFD symbols that are associated with the same SSB index and have same frequency resource index as the starting RO can form a RO group.

[0065] In yet another option, if each RO is associated with multiple SSB for PRACH configuration in both SBFD and non-SBFD symbols, all ROs in both SBFD and non-SBFD symbols that are associated with the same SSB indexes and each same SSB index of the SSB indexes is associated with the same preambles, and have same frequency resource index as the starting RO can form a RO group.

[0066] Further, the first valid PRACH occasion of the first set is the first valid PRACH occasion and the first valid PRACH occasion of subsequent sets, if any, is determined according to an ordering of valid PRACH occasions in both SBFD and non-SBFD symbols

[0067] • first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions in both SBFD and non-SBFD symbols

[0068] • second, in increasing order of time resource indexes for time multiplexed PRACH occasions in both SBFD and non-SBFD symbols

[0069] In another embodiment, for PRACH with repetitions, the PRACH repetitions are transmitted on the valid PRACH occasions which are configured for either non-SBFD or SBFD symbols. In this case, if the first PRACH repetition is transmitted on the non-SBFD symbols, the subsequent PRACH repetitions are also transmitted on the non-SBFD symbols. If the first PRACH repetition is transmitted on the SBFD symbols, the subsequent PRACH repetitions are also transmitted on the SBFD symbols.

[0070] In this case, the existing SSB to RO group association rule and the mapping of PRACH repetition on valid RO group can be applied for PRACH repetitions on SBFD symbols and non- SBFD symbols, respectively.

[0071] In some aspects, for PRACH repetitions in either non-SBFD or SBFD symbols, a time period, starting from frame 0, is the smallest integer number of association pattern periods such that at least one set of valid PRACH occasions for either non-SBFD or SBFD symbols for each of theSBSS / PBCH block indexes can be determined within the time period for all configured number of preamble repetitions, respectively. The set(s) of valid PRACH occasions for either SBFD or non-SBFD symbols for each configured number of preamble repetitions repeats every time period, respectively.

[0072] Figure 5 illustrates one example of PRACH repetitions in only non-SBFD symbols. In the figure, 2 PRACH repetitions are configured and determined. 2 SSBs are configured and 1 SSB is associated with 1 PRACH occasion. In this case, UE may transmit two PRACH repetitions on RO#0 and RO#2 on non-SBFD symbols which are associated with SSB#0.

[0073] SYSTEMS AND IMPLEMENTATIONS

[0074] Figures 6-9 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

[0075] Figure 6 illustrates a network 600 in accordance with various embodiments. The network 600 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 regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

[0076] The network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 604 via an over-the-air connection. The UE 602 may be communicatively coupled with the RAN 604 by a Uu interface. The UE 602 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

[0077] In some embodiments, the network 600 may include a plurality of UEs coupled directly with one another 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.

[0078] In some embodiments, the UE 602 may additionally communicate with an AP 606 via an over-the-air connection. The AP 606 may manage a WLAN connection, which may serve to offload some / all network traffic from the RAN 604. The connection between the UE 602 and the AP 606 may be consistent with any IEEE 802.11 protocol, wherein the AP 606 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 602, RAN 604, and AP 606 may utilize cellular- WLAN aggregation (for example, LWA / LWIP). Cellular- WLAN aggregation may involve the UE 602 being configured by the RAN 604 to utilize both cellular radio resources and WLAN resources.

[0079] The RAN 604 may include one or more access nodes, for example, AN 608. AN 608 may terminate air-interface protocols for the UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 608 may enable data / voice connectivity between CN 620 and the UE 602. In some embodiments, the AN 608 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 608 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 608 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0080] In embodiments in which the RAN 604 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 604 is an LTE RAN) or an Xn interface (if the RAN 604 is a 5G RAN). The X2 / Xn interfaces, which may be separated into control / user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data / context transfers, mobility, load management, interference coordination, etc.

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

[0082] The RAN 604 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCells / Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium / carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

[0083] In V2X scenarios the UE 602 or AN 608 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) 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”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications / software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular / WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0084] In some embodiments, the RAN 604 may be an LTE RAN 610 with eNBs, for example, eNB 612. The LTE RAN 610 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 cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

[0085] In some embodiments, the RAN 604 may be an NG-RAN 614 with gNBs, for example, gNB 616, or ng-eNBs, for example, ng-eNB 618. The gNB 616 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 616 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 618 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 616 and the ng-eNB 618 may connect with each other over an Xn interface.

[0086] In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 614 and a UPF 648 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN614 and an AMF 644 (e.g., N2 interface).

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

[0088] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 602 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 602 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 602 and in some cases at the gNB 616. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

[0089] The RAN 604 is communicatively coupled to CN 620 that includes network elements to provide various functions to support data and telecommunications services to customers / subscribers (for example, users of UE 602). The components of the CN 620 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 620 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 620 may be referred to as a network sub-slice.

[0090] In some embodiments, the CN 620 may be an LTE CN 622, which may also be referred to as an EPC. The LTE CN 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 622 may be briefly introduced as follows.

[0091] The MME 624 may implement mobility management functions to track a current location of the UE 602 to facilitate paging, bearer activation / deactivation, handovers, gateway selection, authentication, etc.

[0092] The SGW 626 may terminate an S 1 interface toward the RAN and route data packets between the RAN and the LTE CN 622. The SGW 626 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

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

[0094] The HSS 630 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 630 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 630 and the MME 624 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 620.

[0095] The PGW 632 may terminate an SGi interface toward a data network (DN) 636 that may include an application / content server 638. The PGW 632 may route data packets between the LTE CN 622 and the data network 636. The PGW 632 may be coupled with the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 632 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 632 and the data network 6 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 632 may be coupled with a PCRF 634 via a Gx reference point.

[0096] The PCRF 634 is the policy and charging control element of the LTE CN 622. The PCRF 634 may be communicatively coupled to the app / content server 638 to determine appropriate QoS and charging parameters for service flows. The PCRF 632 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

[0097] In some embodiments, the CN 620 may be a 5GC 640. The 5GC 640 may include an AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 640 may be briefly introduced as follows.

[0098] The AUSF 642 may store data for authentication of UE 602 and handle authentication- related functionality. The AUSF 642 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 640 over reference points as shown, the AUSF 642 may exhibit an Nausf service-based interface.

[0099] The AMF 644 may allow other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and to subscribe to notifications about mobility events with respect to the UE 602. The AMF 644 may be responsible for registration management (for example, for registering UE 602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 644 may provide transport for SM messages between the UE 602 and the SMF 646, and act as a transparent proxy for routing SM messages. AMF 644 may also provide transport for SMS messages between UE 602 and an SMSF. AMF 644 may interact with the AUSF 642 and the UE 602 to perform various security anchor and context management functions. Furthermore, AMF 644 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 604 and the AMF 644; and the AMF 644 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 644 may also support NAS signaling with the UE 602 over an N3 IWF interface.

[0100] The SMF 646 may be responsible for SM (for example, session establishment, tunnel management between UPF 648 and AN 608); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 648 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 644 over N2 to AN 608; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 602 and the data network 636.

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

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

[0103] The NEF 652 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure / re-exposure, AFs (e.g., AF 660), edge computing or fog computing systems, etc. In such embodiments, the NEF 652 may authenticate, authorize, or throttle the AFs. NEF 652 may also translate information exchanged with the AF 660 and information exchanged with internal network functions. For example, the NEF 652 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 652 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 652 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 652 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 652 may exhibit an Nnef service-based interface.

[0104] The NRF 654 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 654 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 654 may exhibit the Nnrf service-based interface.

[0105] The PCF 656 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 656 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 658. In addition to communicating with functions over reference points as shown, the PCF 656 exhibit an Npcf service-based interface.

[0106] The UDM 658 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 602. For example, subscription data may be communicated via an N8 reference point between the UDM 658 and the AMF 644. The UDM 658 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 658 and the PCF 656, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 602) for the NEF 652. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 658, PCF 656, and NEF 652 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 658 may exhibit the Nudm service-based interface.

[0107] The AF 660 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

[0108] In some embodiments, the 5GC 640 may enable edge computing by selecting operator / 3rdparty services to be geographically close to a point that the UE 602 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 640 may select a UPF 648 close to the UE 602 and execute traffic steering from the UPF 648 to data network 636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 660. In this way, the AF 660 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 660 is considered to be a trusted entity, the network operator may permit AF 660 to interact directly with relevant NFs. Additionally, the AF 660 may exhibit an Naf service-based interface.

[0109] The data network 636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application / content server 638.

[0110] Figure 7 schematically illustrates a wireless network 700 in accordance with various embodiments. The wireless network 700 may include a UE 702 in wireless communication with an AN 704. The UE 702 and AN 704 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

[0111] The UE 702 may be communicatively coupled with the AN 704 via connection 706. The connection 706 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

[0112] The UE 702 may include a host platform 708 coupled with a modem platform 710. The host platform 708 may include application processing circuitry 712, which may be coupled with protocol processing circuitry 714 of the modem platform 710. The application processing circuitry 712 may run various applications for the UE 702 that source / sink application data. The application processing circuitry 712 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

[0113] The protocol processing circuitry 714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 706. The layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

[0114] The modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 714 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / de-mapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0115] The modem platform 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and RF front end (RFFE) 724, which may include or connect to one or more antenna panels 726. Briefly, the transmit circuitry 718 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 720 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 722 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 724 may include filters (for example, surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 718, receive circuitry 720, RF circuitry 722, RFFE 724, and antenna panels 726 (referred generically as “transmit / receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be disposed in the same or different chips / modules, etc.

[0116] In some embodiments, the protocol processing circuitry 714 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0117] A UE reception may be established by and via the antenna panels 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714. In some embodiments, the antenna panels 726 may receive a transmission from the AN 704 by receive-beamforming signals received by a plurality of antennas / antenna elements of the one or more antenna panels 726.

[0118] A UE transmission may be established by and via the protocol processing circuitry 714, digital baseband circuitry 716, transmit circuitry 718, RF circuitry 722, RFFE 724, and antenna panels 726. In some embodiments, the transmit components of the UE 704 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 726.

[0119] Similar to the UE 702, the AN 704 may include a host platform 728 coupled with a modem platform 730. The host platform 728 may include application processing circuitry 732 coupled with protocol processing circuitry 734 of the modem platform 730. The modem platform may further include digital baseband circuitry 736, transmit circuitry 738, receive circuitry 740, RF circuitry 742, RFFE circuitry 744, and antenna panels 746. The components of the AN 704 may be similar to and substantially interchangeable with like-named components of the UE 702. In addition to performing data transmission / reception as described above, the components of the AN 708 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0120] Figure 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory / storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 802 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 800.

[0121] The processors 810 may include, for example, a processor 812 and a processor 814. The processors 810 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.

[0122] The memory / storage devices 820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 820 may include, but are not limited to, any type of volatile, non-volatile, or semi- volatile memory such as 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.

[0123] The communication resources 830 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements via a network 808. For example, the communication resources 830 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0124] Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein. The instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory / storage devices 820, or any suitable combination thereof. Furthermore, any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory / storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.

[0125] Figure 9 illustrates a network 900 in accordance with various embodiments. The network 900 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 900 may operate concurrently with network 600. For example, in some embodiments, the network 900 may share one or more frequency or bandwidth resources with network 600. As one specific example, a UE (e.g., UE 902) may be configured to operate in both network 900 and network 600. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 600 and 900. In general, several elements of network 900 may share one or more characteristics with elements of network 600. For the sake of brevity and clarity, such elements may not be repeated in the description of network 900.

[0126] The network 900 may include a UE 902, which may include any mobile or non-mobile computing device designed to communicate with a RAN 908 via an over-the-air connection. The UE 902 may be similar to, for example, UE 602. The UE 902 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in- vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

[0127] Although not specifically shown in Figure 9, in some embodiments the network 900 may include a plurality of UEs coupled directly with one another 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 Figure 9, the UE 902 may be communicatively coupled with an AP such as AP 606 as described with respect to Figure 6. Additionally, although not specifically shown in Figure 9, in some embodiments the RAN 908 may include one or more ANss such as AN 608 as described with respect to Figure 6. The RAN 908 and / or the AN of the RAN 908 may be referred to as a base station (BS), a RAN node, or using some other term or name.

[0128] The UE 902 and the RAN 908 may be configured to communicate via 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 a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges.

[0129] The RAN 908 may allow for communication between the UE 902 and a 6G core network (CN) 910. Specifically, the RAN 908 may facilitate the transmission and reception of data between the UE 902 and the 6G CN 910. The 6G CN 910 may include various functions such as NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, AF 660, SMF 646, and AUSF 642. The 6G CN 910 may additional include UPF 648 and DN 636 as shown in Figure 9.

[0130] Additionally, the RAN 908 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 924 and a Compute Service Function (Comp SF) 936. The Comp CF 924 and the Comp SF 936 may be parts or functions of the Computing Service Plane. Comp CF 924 may be a control plane function that provides functionalities such as management of the Comp SF 936, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlying computing infrastructure for computing resource management, etc.. Comp SF 936 may be a user plane function that serves as the gateway to interface computing service users (such as UE 902) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 936 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 936 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 924 instance may control one or more Comp SF 936 instances.

[0131] Two other such functions may include a Communication Control Function (Comm CF) 928 and a Communication Service Function (Comm SF) 938, which may be parts of the Communication Service Plane. The Comm CF 928 may be the control plane function for managing the Comm SF 938, communication sessions creation / configuration / releasing, and managing communication session context. The Comm SF 938 may be a user plane function for data transport. Comm CF 928 and Comm SF 938 may be considered as upgrades of SMF 646 and UPF 648, which were described with respect to a 5G system in Figure 6. The upgrades provided by the Comm CF 928 and the Comm SF 938 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 646 and UPF 648 may still be used.

[0132] Two other such functions may include a Data Control Function (Data CF) 922 and Data Service Function (Data SF) 932 may be parts of the Data Service Plane. Data CF 922 may be a control plane function and provides functionalities such as Data SF 932 management, Data service creation / configuration / releasing, Data service context management, etc. Data SF 932 may be a user plane function and serve as the gateway between data service users (such as UE 902 and the various functions of the 6G CN 910) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status.

[0133] Another such function may be the Service Orchestration and Chaining Function (SOCF) 920, which may discover, orchestrate and chain up communication / computing / data services provided by functions in the network. Upon receiving service requests from users, SOCF 920 may interact with one or more of Comp CF 924, Comm CF 928, and Data CF 922 to identify Comp SF 936, Comm SF 938, and Data SF 932 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 936, Comm SF 938, and Data SF 932 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 920 may also responsible for maintaining, updating, and releasing a created service chain.

[0134] Another such function may be the service registration function (SRF) 914, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 936 and Data SF 932 gateways and services provided by the UE 902. The SRF 914 may be considered a counterpart of NRF 654, which may act as the registry for network functions.

[0135] Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 926, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 912 and eSCP-U 934, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 926 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

[0136] Another such function is the AMF 944. The AMF 944 may be similar to 644, but with additional functionality. Specifically, the AMF 944 may include potential functional repartition, such as move the message forwarding functionality from the AMF 944 to the RAN 908.

[0137] Another such function is the service orchestration exposure function (SOEF) 918. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications. The UE 902 may include an additional function that is referred to as a computing client service function (comp CSF) 904. The comp CSF 904 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 920, Comp CF 924, Comp SF 936, Data CF 922, and / or Data SF 932 for service discovery, request / response, compute task workload exchange, etc. The Comp CSF 904 may also work with network side functions to decide on whether a computing task should be run on the UE 902, the RAN 908, and / or an element of the 6G CN 910.

[0138] The UE 902 and / or the Comp CSF 904 may include a service mesh proxy 906. The service mesh proxy 906 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 906 may include one or more of addressing, security, load balancing, etc.

[0139] EXAMPLE PROCEDURES

[0140] In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 6-9, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 10. The process may be performed by a UE or a portion thereof. For example, the process may include, at 1001, receiving a first resource configuration for physical uplink control channels (PUCCHs) resources or a physical random access channels (PRACHs) resources in subband nonoverlapping full duplex (SBFD) symbols. At 1002, the process may further include receiving a second resource configuration for PUCCH resources or PRACH resources in non-SBFD symbols. At 1003, the process may further include encoding a PUCCH or a PRACH for transmission with repetitions using the first resource configuration and the second resource configuration.

[0141] Another such process is depicted in Figure 11. The process of Figure 11 may be, include, 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 that include and / or implement a UE. The process may include identifying, at 1101, first configuration information related to uplink (UL) transmission on one or more subband non-overlapping full duplex (SBFD) symbols; identifying, at 1102, second configuration information related to UL transmission on one or more non-SBFD symbols; and generating, at 1103 based on the first configuration information and the second configuration information, a plurality of uplink (UL) transmissions.

[0142] Another such process is depicted in Figure 12. The process of Figure 12 may be, include or relate to a method to be performed by a base station, one or more elements of a base station, and / or one or more electronic devices that include and / or implement a base station. The process may include transmitting, at 1201 to a user equipment (UE), first configuration information related to uplink (UL) transmission on one or more subband non-overlapping full duplex (SBFD) symbols; transmitting, at 1202 to the UE, second configuration information related to UL transmission on one or more non-SBFD symbols; and identifying, at 1203 from the UE based on the first configuration information and the second configuration information, a plurality of uplink (UL) transmissions.

[0143] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

[0144] EXAMPLES

[0145] Example 1 may include a method of wireless communication (e.g., for a fifth generation (5G) or new radio (NR) system), the method comprising: receiving, by a UE, a separate configuration of physical uplink control channel (PUCCH) resource or physical random access channel (PRACH) for subband non-overlapping full duplex (SBFD) and non-SBFD symbols, respectively; and transmitting, by UE, a PUCCH or PRACH with repetitions using the configurations for both SBFD and non-SBFD symbols jointly.

[0146] Example 2 may include the method of example 1 and / or some other example herein, wherein if a UE does not have dedicated PUCCH resource configuration, a UE can be provided with separate PUCCH resource sets which are indicated by separate pucch-ResourceCommon.

[0147] Example 3 may include the method of example 1 and / or some other example herein, wherein PRB location of the PUCCH transmission in non-SBFD symbols and SBFD symbols can be determined in accordance with the active UL bandwidth part (BWP) that is associated with non-SBFD symbols and SBFD symbols, respectively.

[0148] Example 4 may include the method of example 1 and / or some other example herein, wherein for PUCCH with repetitions, the PUCCH repetitions are transmitted on the PUCCH resources which are configured for both non-SBFD and SBFD symbols.

[0149] Example 5 may include the method of example 1 and / or some other example herein, wherein PUCCH resource configuration for the PUCCH repetitions is determined in accordance with the PUCCH resource configuration from the first PUCCH repetition.

[0150] Example 6 may include the method of example 1 and / or some other example herein, wherein the number of repetitions for the PUCCH transmission is determined in accordance with the PUCCH resource in the first PUCCH repetition.

[0151] Example 7 may include the method of example 1 and / or some other example herein, wherein PUCCH resource index that is determined for the first PUCCH repetition is applied for the subsequent PUCCH repetitions in non-SBFD and / or SBFD symbols.

[0152] Example 8 may include the method of example 1 and / or some other example herein, wherein for PUCCH with repetitions, the PUCCH repetitions are transmitted on the PUCCH resources which are configured for either non-SBFD or SBFD symbols.

[0153] Example 9 may include the method of example 1 and / or some other example herein, wherein if the first PUCCH repetition is determined to be transmitted on the non-SBFD symbols, the subsequent PUCCH repetitions are also transmitted on the non-SBFD symbols. If the first PUCCH repetition is determined to be transmitted on the SBFD symbols, the subsequent PUCCH repetitions are also transmitted on the SBFD symbols.

[0154] Example 10 may include the method of example 1 and / or some other example herein, wherein separate PRACH configurations may be configured for a UE in SBFD symbols and non-SBFD symbols.

[0155] Example 11 may include the method of example 1 and / or some other example herein, wherein UE may be provided with separate RACH-ConfigGeneric for SBFD symbols and non- SBFD symbols, respectively.

[0156] Example 12 may include the method of example 1 and / or some other example herein, wherein UE may continue to use the configurations for random access which are based on the initial PRACH transmission on either SBFD or non-SBFD symbols.

[0157] Example 13 may include the method of example 1 and / or some other example herein, wherein UE may only switch to the PRACH configurations for PRACH retransmission if the number of PRACH retransmission reaches to a maximum value, which may be configured by higher layers.

[0158] Example 14 may include the method of example 1 and / or some other example herein, wherein for PRACH with repetitions, the PRACH repetitions may be transmitted on the valid PRACH occasions that are configured for both SBFD and non-SBFD symbols.

[0159] Example 15 may include the method of example 1 and / or some other example herein, wherein if each RO is associated with one SSB for PRACH configuration in both SBFD and non-SBFD symbols, all ROs in both SBFD and non-SBFD symbols that are associated with the same SSB index and have same starting RB as the starting RO can form a RO group.

[0160] Example 16 may include the method of example 1 and / or some other example herein, wherein if each RO is associated with multiple SSB for PRACH configuration in both SBFD and non-SBFD symbols, all ROs in both SBFD and non-SBFD symbols that are associated with the same SSB indexes and each same SSB index of the SSB indexes is associated with the same preambles, and have same starting RB as the starting RO can form a RO group.

[0161] Example 17 may include the method of example 1 and / or some other example herein, wherein for PRACH with repetitions, the PRACH repetitions may be transmitted on the valid PRACH occasions that are configured for both SBFD and non-SBFD symbols.

[0162] Example 18 may include the method of example 1 and / or some other example herein, wherein if each RO is associated with one SSB for PRACH configuration in both SBFD and non-SBFD symbols, all ROs in both SBFD and non-SBFD symbols that are associated with the same SSB index and have same frequency resource index as the starting RO can form a RO group.

[0163] Example 19 may include the method of example 1 and / or some other example herein, wherein if each RO is associated with multiple SSB for PRACH configuration in both SBFD and non-SBFD symbols, all ROs in both SBFD and non-SBFD symbols that are associated with the same SSB indexes and each same SSB index of the SSB indexes is associated with the same preambles, and have same frequency resource index as the starting RO can form a RO group.

[0164] Example 20 may include the method of example 1 and / or some other example herein, wherein for PRACH with repetitions, the PRACH repetitions are transmitted on the valid PRACH occasions which are configured for either non-SBFD or SBFD symbols.

[0165] Example 21 may include the method of example 1 and / or some other example herein, wherein if the first PRACH repetition is transmitted on the non-SBFD symbols, the subsequent PRACH repetitions are also transmitted on the non-SBFD symbols. If the first PRACH repetition is transmitted on the SBFD symbols, the subsequent PRACH repetitions are also transmitted on the SBFD symbols.

[0166] Example 22 may include the method of example 1 and / or some other example herein, wherein the existing SSB to RO group association rule and the mapping of PRACH repetition on valid RO group can be applied for PRACH repetitions on SBFD symbols and non-SBFD symbols, respectively.

[0167] Example 23 may include a method of a user equipment (UE), the method comprising: receiving a first resource configuration for physical uplink control channels (PUCCHs) resources or physical random access channels (PRACHs) resources in subband non-overlapping full duplex (SBFD) symbols; receiving a second resource configuration for PUCCH resources or PRACH resources in non-SBFD symbols; and encoding a PUCCH or a PRACH for transmission with repetitions using the first resource configuration and the second resource configuration.

[0168] Example 24 may include the method of example 23-24 and / or some other example herein, wherein the first and / or second resource configurations are dedicated resource configurations.

[0169] Example 25 may include the method of example 23-25 and / or some other example herein, wherein the first and / or separate resource configurations are common resource configurations.

[0170] Example 26 may include the method of example 23-25 and / or some other example herein, wherein the PUCCH or the PRACH is the PUCCH.

[0171] Example 27 may include the method of example 26 and / or some other example herein, further comprising determining a physical resource block (PRB) location of the PUCCH in the non-SBFD symbols and the SBFD symbols in accordance with an active uplink bandwidth part (BWP) that is associated with the non-SBFD symbols and the SBFD symbols, respectively.

[0172] Example 28 may include the method of example 23-27 and / or some other example herein, further comprising determining a number of the repetitions based on an uplink resource in a first (e.g., earliest) repetition.

[0173] Example 29 may include the method of example 26-28 and / or some other example herein, further comprising: determining a PUCCH resource index for a first PUCCH repetition; and applying the PUCCH resource index for subsequent PUCCH repetitions in the non- SBFD symbols and the SBFD symbols.

[0174] Example 30 may include the method of example 23-25 and / or some other example herein, wherein the PUCCH or PRACH is the PRACH.

[0175] Example 31 may include the method of example 30 and / or some other example herein, further comprising receiving a separate RACH-ConfigGeneric for SBFD symbols and non- SBFD symbols, respectively.

[0176] Example 32 may include the method of example 30-31 and / or some other example herein, wherein the repetitions are transmitted on the valid PRACH occasions that are configured for SBFD and non-SBFD symbols.

[0177] Example 33 may include the method of example 30-32 and / or some other example herein, wherein the PRACH with repetitions is transmitted on a random access channel occasion (RO) group. Example 34 may include the method of example 33 and / or some other example herein, wherein individual ROs are associated with one SSB for both the SBFD symbols and the non- SBFD symbols, and wherein the RO group corresponds to all ROs in both the SBFD symbols and the non-SBFD symbols that are associated with a same SSB index and have a same starting RB as a starting RO.

[0178] Example 35 may include the method of example 33 and / or some other example herein, wherein ROs are associated with multiple SSBs for the SBFD symbols and the non-SBFD symbols, and wherein the RO group corresponds to all ROs in both the SBFD symbols and the non-SBFD symbols that are associated with the same SSB indexes have same starting RB as the starting RO.

[0179] Example 36 may include the method of example 35 and / or some other example herein, wherein the SSB indexes for the ROs of the RO group are associated with the same respective preambles.

[0180] Example 37 may include a method to be performed by a user equipment (UE), one or more elements of a UE, and / or one or more electronic devices that include and / or implement a UE, wherein the method comprises: identifying first configuration information related to uplink (UL) transmission on one or more subband non-overlapping full duplex (SBFD) symbols; identifying second configuration information related to UL transmission on one or more non-SBFD symbols; and generating, based on the first configuration information and the second configuration information, a plurality of uplink (UL) transmissions.

[0181] Example 38 may include the method of example 37, and / or some other example herein, wherein the plurality of UL transmissions are transmitted on SBFD symbols, or the plurality of UL transmissions are transmitted on non-SBFD symbols.

[0182] Example 39 may include the method of example 37, and / or some other example herein, wherein at least one of the plurality of UL transmissions is transmitted on an SBFD symbol, and another of the plurality of UL transmissions is transmitted on a non-SBFD symbol.

[0183] Example 40 may include the method of any one or more of examples 37-39, and / or some other example herein, wherein the plurality of UL transmissions are a plurality of physical uplink control channel (PUCCH) transmissions.

[0184] Example 41 may include the method of any one or more of examples 37-39, and / or some other example herein, wherein the plurality of UL transmissions are a plurality of physical random access channel (PRACH) transmissions.

[0185] Example 42 may include the method of example 41 , and / or some other example herein, wherein the plurality of PRACH transmissions are associated with a same synchronization signal block (SSB) as one another.

[0186] Example 43 may include the method of any one or more of example 37-42, and / or some other example herein, wherein the plurality of UL transmissions include a first UL transmission and a repetition of the first UL transmission.

[0187] Example 44 may include the method of any one or more of examples 37-43, and / or some other example herein, wherein a SBFD symbol is a time domain symbol that simultaneously carries UL data and downlink (DL) data.

[0188] Example 45 may include the method of example 44, and / or some other example herein, wherein the UL data is carried on different frequency resources of the SBFD symbol than the DL data.

[0189] Example 46 may include the method of any one or more of examples 37-45, and / or some other example herein, wherein a non-SBFD symbol is a time domain symbol that is not configured to simultaneously carry UL and downlink (DL) data.

[0190] Example 47 may include a method to be performed by a base station, one or more elements of a base station, and / or one or more electronic devices that include and / or implement a base station, wherein the method comprises: transmitting, to a user equipment (UE), first configuration information related to uplink (UL) transmission on one or more subband nonoverlapping full duplex (SBFD) symbols; transmitting, to the UE, second configuration information related to UL transmission on one or more non-SBFD symbols; and identifying, from the UE based on the first configuration information and the second configuration information, a plurality of uplink (UL) transmissions.

[0191] Example 48 may include the method of example 47, and / or some other example herein, wherein the plurality of UL transmissions are transmitted on SBFD symbols, or the plurality of UL transmissions are transmitted on non-SBFD symbols.

[0192] Example 49 may include the method of example 47, and / or some other example herein, wherein at least one of the plurality of UL transmissions is transmitted on an SBFD symbol, and another of the plurality of UL transmissions is transmitted on a non-SBFD symbol.

[0193] Example 50 may include the method of any one or more of examples 47-49, and / or some other example herein, wherein the plurality of UL transmissions are a plurality of physical uplink control channel (PUCCH) transmissions.

[0194] Example 51 may include the method of any one or more of examples 47-49, and / or some other example herein, wherein the plurality of UL transmissions are a plurality of physical random access channel (PRACH) transmissions.

[0195] Example 52 may include the method of example 51 , and / or some other example herein, wherein the plurality of PRACH transmissions are associated with a same synchronization signal block (SSB) as one another.

[0196] Example 53 may include the method of any one or more of example 47-52, and / or some other example herein, wherein the plurality of UL transmissions include a first UL transmission and a repetition of the first UL transmission.

[0197] Example 54 may include the method of any one or more of examples 47-53, and / or some other example herein, wherein a SBFD symbol is a time domain symbol that simultaneously carries UL data and downlink (DL) data.

[0198] Example 55 may include the method of example 54, and / or some other example herein, wherein the UL data is carried on different frequency resources of the SBFD symbol than the DL data.

[0199] Example 56 may include the method of any one or more of examples 47-55, and / or some other example herein, wherein a non-SBFD symbol is a time domain symbol that is not configured to simultaneously carry UL and downlink (DL) data.

[0200] Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-56, and / or any other method or process described herein.

[0201] Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-56, and / or any other method or process described herein.

[0202] Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-56, and / or any other method or process described herein.

[0203] Example Z04 may include a method, technique, or process as described in or related to any of examples 1-56, and / or portions or parts thereof.

[0204] Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-56, and / or portions thereof.

[0205] Example Z06 may include a signal as described in or related to any of examples 1-56, or portions or parts thereof.

[0206] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-56, and / or portions or parts thereof, or otherwise described in the present disclosure.

[0207] Example Z08 may include a signal encoded with data as described in or related to any of examples 1-56, and / or portions or parts thereof, or otherwise described in the present disclosure.

[0208] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-56, and / or portions or parts thereof, or otherwise described in the present disclosure.

[0209] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-56, and / or portions thereof.

[0210] Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-56, and / or portions thereof.

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

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

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

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

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

[0216] Abbreviations

[0217] Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 V16.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein. 3 GPP Third Generation Arrival BRAS Broadband Remote

[0218] Partnership Project AP Application Access Server

[0219] 4G Fourth Generation Protocol, Antenna BSS Business Support

[0220] 5G Fifth Generation Port, Access Point System

[0221] 5GC 5G Core network API Application BS Base Station

[0222] AC Application Programming Interface BSR Buffer Status

[0223] Client APN Access Point Name Report

[0224] ACR Application ARP Allocation and BW Bandwidth

[0225] Context Relocation Retention Priority BWP Bandwidth Part

[0226] ACK Acknowledgement ARQ Automatic Repeat C-RNTI Cell Radio

[0227] ACID Application Request Network Temporary

[0228] Client Identification AS Access Stratum Identity

[0229] ADRF Analytics Data ASP Application CA Carrier

[0230] Repository Service Provider Aggregation,

[0231] Function Certification

[0232] AF Application ASN.l Abstract Syntax Authority

[0233] Function Notation One CAPEX CAPital

[0234] AM Acknowledged AUSF Authentication Expenditure

[0235] Mode Server Function CBD Candidate Beam

[0236] AMBR Aggregate AWGN Additive Detection

[0237] Maximum Bit Rate White Gaussian CBRA Contention Based

[0238] AMF Access and Noise Random Access

[0239] Mobility BAP Backhaul CC Component Carrier,

[0240] Management Adaptation Protocol Country Code,

[0241] Function BCH Broadcast Channel Cryptographic

[0242] AN Access Network BER Bit Error Ratio Checksum

[0243] AnLF Analytics Logical BFD Beam Failure CCA Clear Channel

[0244] Function Detection Assessment

[0245] ANR Automatic BLER Block Error Rate CCE Control Channel

[0246] Neighbour Relation BPSK Binary Phase Shift Element

[0247] AOA Angle of Keying CCCH Common Control Channel Mobile Alert Service Cloud RAN

[0248] CE Coverage CMD Command CRB Common Resource Enhancement CMS Cloud Management Block CDM Content Delivery System CRC Cyclic Redundancy Network CO Conditional Check CDMA Code- Optional CRI Channel-State Division Multiple CoMP Coordinated MultiInformation Resource Access Point Indicator, CSI-RS

[0249] CDR Charging Data CORESET Control Resource Indicator Request Resource Set C-RNTI Cell RNTI

[0250] CDR Charging Data COTS Commercial Off- CS Circuit Switched Response The-Shelf CSCF call session CFRA Contention Free CP Control Plane, control function Random Access Cyclic Prefix, Connection CSAR Cloud Service CG Cell Group Point Archive CGF Charging CPD Connection Point CSI Channel-State

[0251] Gateway Function Descriptor Information CHF Charging CPE Customer Premise CSI-IM CSI

[0252] Function Equipment Interference CI Cell Identity CPICHCommon Pilot Measurement CID Cell-ID (e.g., Channel CSI-RS CSI positioning method) CQI Channel Quality Reference Signal CIM Common Indicator CSI-RSRP CSI Information Model CPU CSI processing reference signal CIR Carrier to unit, Central Processing received power Interference Ratio Unit CSI-RSRQ CSI CK Cipher Key C / R reference signal CM Connection Command / Respons received quality Management, Conditional e field bit CSI-SINR CSI signal- Mandatory CRAN Cloud Radio to-noise and interference CMAS Commercial Access Network, ratio CSMA Garner Sense DNAI Data Network Application Server

[0253] Multiple Access Access Identifier EASID Edge

[0254] CSMA / CA CSMA with Application Server collision avoidance DRB Data Radio Bearer Identification

[0255] CSS Common Search DRS Discovery ECS Edge

[0256] Space, Cell- specific Reference Signal Configuration Server

[0257] Search Space DRX Discontinuous ECSP Edge

[0258] CTF Charging Reception Computing Service

[0259] Trigger Function DSL Domain Specific Provider

[0260] CTS Clear-to-Send Language. Digital EDN Edge Data

[0261] CW Codeword Subscriber Line Network

[0262] CWS Contention DSLAM DSL Access EEC Edge

[0263] Window Size Multiplexer Enabler Client

[0264] D2D Device-to-Device DwPTS Downlink EECID Edge

[0265] DC Dual Connectivity, Pilot Time Slot Enabler Client

[0266] Direct Current E-LAN Ethernet Identification

[0267] DO Downlink Control Local Area Network EES Edge

[0268] Information E2E End-to-End Enabler Server

[0269] DF Deployment EAS Edge Application EESID Edge

[0270] Flavour Server Enabler Server

[0271] DL Downlink ECCA extended clear Identification

[0272] DMTF Distributed channel assessment, EHE Edge

[0273] Management Task Force extended CCA Hosting Environment

[0274] DPDK Data Plane ECCE Enhanced Control EGMF Exposure

[0275] Development Kit Channel Element, Governance

[0276] DM-RS, DMRS Enhanced CCE Management

[0277] Demodulation ED Energy Detection Function

[0278] Reference Signal EDGE Enhanced Datarates EGPRS Enhanced

[0279] DN Data network for GSM Evolution GPRS

[0280] DNN Data Network (GSM Evolution) EIR Equipment Identity

[0281] Name EAS Edge Register eEAA enhanced Eicensed System FCC Federal

[0282] Assisted Access, cUICC embedded UICC, Communications enhanced EAA embedded Universal Commission

[0283] EM Element Manager Integrated Circuit Card FCCH Frequency eMBB Enhanced Mobile E-UTRA Evolved Correction CHannel

[0284] Broadband UTRA FDD Frequency Division

[0285] EMS Element E-UTRAN Evolved Duplex

[0286] Management System UTRAN FDM Frequency Division eNB evolved NodeB, E- EV2X Enhanced V2X Multiplex UTRAN Node B F1AP Fl Application FDM A Frequency Division

[0287] EN-DC E-UTRA- Protocol Multiple Access

[0288] NR Dual Fl-C F 1 Control plane FE Front End

[0289] Connectivity interface FEC Forward Error

[0290] EPC Evolved Packet Fl-U Fl User plane Correction Core interface FFS For Further Study

[0291] EPDCCH enhanced FACCH Fast FFT Fast Fourier PDCCH, enhanced Associated Control Transformation

[0292] Physical Downlink CHannel feEAA further enhanced

[0293] Control Cannel FACCH / F Fast Eicensed Assisted

[0294] EPRE Energy per Associated Control Access, further resource element Channel / Full rate enhanced EAA

[0295] EPS Evolved Packet FACCH / H Fast FN Frame Number System Associated Control FPGA Field-

[0296] EREG enhanced REG, Channel / Half rate Programmable Gate enhanced resource FACH Forward Access Array element groups Channel FR Frequency Range ETSI European FAUSCH Fast Uplink FQDN Fully Qualified

[0297] Telecommunication Signalling Channel Domain Name s Standards Institute FB Functional Block G-RNTI GERAN ETWS Earthquake and FBI Feedback Radio Network Tsunami Warning Information Temporary Identity GERAN Mobile Access

[0298] GSM EDGE RAN, Communications, HSN Hopping Sequence GSM EDGE Radio Groupe Special Number Access Network Mobile HSPA High Speed Packet

[0299] GGSN Gateway GPRS GTP GPRS Tunneling Access Support Node Protocol HSS Home Subscriber GLONASS GTP-UGPRS Tunnelling Server

[0300] GLObal'naya Protocol for User HSUPA High Speed

[0301] NAvigatsionnaya Plane Uplink Packet Access

[0302] Sputnikovaya GTS Go To Sleep Signal HTTP Hyper Text

[0303] Sistema (Engl.: (related to WUS) Transfer Protocol

[0304] Global Navigation GUMMEI Globally HTTPS Hyper Text

[0305] Satellite System) Unique MME Identifier Transfer Protocol gNB Next Generation GUTI Globally Unique Secure (https is NodeB Temporary UE Identity http / Ll over SSL, gNB-CU gNB- HARQ Hybrid ARQ, i.e. port 443) centralized unit, Next Hybrid Automatic LBlock Information

[0306] Generation NodeB Repeat Request Block centralized unit HANDO Handover ICCID Integrated Circuit gNB-DU gNB- HFN HyperFrame Card Identification distributed unit, Next Number IAB Integrated Access

[0307] Generation NodeB HHO Hard Handover and Backhaul distributed unit HLR Home Location ICIC Inter-Cell

[0308] GNSS Global Navigation Register Interference Satellite System HN Home Network Coordination GPRS General Packet HO Handover ID Identity, identifier

[0309] Radio Service HPLMN Home IDFT Inverse Discrete

[0310] GPSI Generic Public Land Mobile Fourier Transform

[0311] Public Subscription Network IE Information

[0312] Identifier HSDPA High Speed element

[0313] GSM Global System for Downlink Packet IBE In-Band Emission IMST International I-WLAN

[0314] IEEE Institute of Mobile Subscriber Interworking

[0315] Electrical and Electronics Identity WLAN

[0316] Engineers loT Internet of Things Constraint length of

[0317] IEI Information IP Internet Protocol the convolutional code,

[0318] Element Identifier Ipsec IP Security, USIM Individual key

[0319] IEIDL Information Internet Protocol kB Kilobyte (1000

[0320] Element Identifier Security bytes)

[0321] Data Length IP-CAN IP- kbps kilo-bits per second

[0322] IETF Internet Connectivity Access Kc Ciphering key

[0323] Engineering Task Network Ki Individual Force IP-M IP Multicast subscriber

[0324] IF Infrastructure IPv4 Internet Protocol authentication key

[0325] IIOT Industrial Internet Version 4 KPI Key Performance of Things IPv6 Internet Protocol Indicator

[0326] IM Interference Version 6 KQI Key Quality

[0327] Measurement, IR Infrared Indicator Intermodulation, IP IS In Sync KSI Key Set Identifier Multimedia IRP Integration ksps kilo-symbols per

[0328] IMC IMS Credentials Reference Point second

[0329] IMEI International ISDN Integrated Services KVM Kernel Virtual

[0330] Mobile Equipment Digital Network Machine

[0331] Identity ISIM IM Services LI Layer 1 (physical

[0332] IMGI International Identity Module layer) mobile group identity ISO International Ll-RSRP Layer 1 IMPI IP Multimedia Organisation for reference signal

[0333] Private Identity Standardisation received power

[0334] IMPU IP Multimedia ISP Internet Service L2 Layer 2 (data link

[0335] PUblic identity Provider layer)

[0336] IMS IP Multimedia IWF Interworking- L3 Layer 3 (network

[0337] Subsystem Function layer) LAA Licensed Assisted LWIP LTE / WLAN Radio Network

[0338] Access Level Integration with MCC Mobile Country

[0339] LAN Local Area IPsec Tunnel Code

[0340] Network LTE Long Term MCG Master Cell Group

[0341] LADN Local Area Evolution MCOT Maximum Channel

[0342] Data Network M2M Machine-to- Occupancy Time

[0343] LBT Listen Before Talk Machine MCS Modulation and

[0344] LCM LifeCycle MAC Medium Access coding scheme

[0345] Management Control (protocol MD AF Management Data

[0346] LCR Low Chip Rate layering context) Analytics Function

[0347] LCS Location Services MAC Message MDAS Management Data

[0348] LCID Logical authentication code Analytics Service

[0349] Channel ID (security / encryption MDT Minimization of

[0350] LI Layer Indicator context) Drive Tests

[0351] LLC Logical Link MAC-A MAC used ME Mobile Equipment

[0352] Control, Low Layer for authentication and MeNB master eNB

[0353] Compatibility key agreement (TSG T MER Message Error

[0354] LMF Location WG3 context) Ratio

[0355] Management Function MAC-IMAC used for data MGL Measurement Gap

[0356] LOS Line of integrity of Length

[0357] Sight signalling messages (TSG MGRP Measurement Gap

[0358] LPLMN Local T WG3 context) Repetition Period

[0359] PLMN MANO MIB Master Information

[0360] LPP LTE Positioning Management and Block, Management

[0361] Protocol Orchestration Information Base

[0362] LSB Least Significant MB MS Multimedia MIMO Multiple Input

[0363] Bit Broadcast and Multicast Multiple Output

[0364] LTE Long Term Service MLC Mobile Location

[0365] Evolution MBSFN Multimedia Centre

[0366] LWA LTE-WLAN Broadcast multicast MM Mobility aggregation service Single Frequency Management MME Mobility Information, MCH Stratum layer

[0367] Management Entity Scheduling NCT Network

[0368] MN Master Node Information Connectivity Topology

[0369] MNO Mobile MSID Mobile Station NC-JT Non¬

[0370] Network Operator Identifier coherent Joint

[0371] MO Measurement MSIN Mobile Station Transmission

[0372] Object, Mobile Identification NEC Network Capability

[0373] Originated Number Exposure

[0374] MPBCH MTC MSISDN Mobile NE-DC NR-E-

[0375] Physical Broadcast Subscriber ISDN UTRA Dual

[0376] CHannel Number Connectivity

[0377] MPDCCH MTC MT Mobile Terminated, NEF Network Exposure

[0378] Physical Downlink Mobile Termination Function

[0379] Control CHannel MTC Machine-Type NF Network Function

[0380] MPDSCH MTC Communications NFP Network

[0381] Physical Downlink MTLF Model Training Forwarding Path

[0382] Shared CHannel Logical Functions NFPD Network

[0383] MPRACH MTC mMTCmassive MTC, Forwarding Path

[0384] Physical Random massive Machine- Descriptor

[0385] Access CHannel Type Communications NFV Network Functions

[0386] MPUSCH MTC MU-MIMO Multi User Virtualization

[0387] Physical Uplink Shared MIMO NFVI NFV Infrastructure

[0388] Channel MWUS MTC wakeNFVO NFV Orchestrator

[0389] MPLS MultiProtocol up signal, MTC NG Next Generation,

[0390] Label Switching WUS Next Gen

[0391] MS Mobile Station NACK Negative NGEN-DC NG-RAN

[0392] MSB Most Significant Acknowledgement E-UTRA-NR Dual

[0393] Bit NAI Network Access Connectivity

[0394] MSC Mobile Switching Identifier NM Network Manager

[0395] Centre NAS Non-Access NMS Network

[0396] MSI Minimum System Stratum, Non- Access Management System N-PoP Network Point of NRS Narrowband OFDMA Orthogonal

[0397] Presence Reference Signal Frequency Division

[0398] NMIB, N-MIB NS Network Service Multiple Access

[0399] Narrowband MIB NS A Non-Standalone OOB Out-of-band

[0400] NPBCH Narrowband operation mode OOS Out of Sync

[0401] Physical Broadcast NSD Network Service OPEX OPerating EXpense

[0402] CHannel Descriptor OSI Other System

[0403] NPDCCH Narrowband NSR Network Service Information

[0404] Physical Downlink Record OSS Operations Support

[0405] Control CHannel NSSAINetwork Slice System

[0406] NPDSCH Narrowband Selection Assistance OTA over-the-air

[0407] Physical Downlink Information PAPR Peak-to-Average

[0408] Shared CHannel S-NNSAI Single- Power Ratio

[0409] NPRACH Narrowband NSSAI PAR Peak to Average

[0410] Physical Random NSSF Network Slice Ratio

[0411] Access CHannel Selection Function PBCH Physical Broadcast

[0412] NPUSCH Narrowband NW Network Channel

[0413] Physical Uplink NWDAF Network PC Power Control,

[0414] Shared CHannel Data Analytics Personal Computer

[0415] NPSS Narrowband Function PCC Primary

[0416] Primary NWUS Narrowband wakeComponent Carrier,

[0417] Synchronization up signal, Narrowband Primary CC

[0418] Signal wus P-CSCF Proxy

[0419] NSSS Narrowband NZP Non-Zero Power CSCF

[0420] Secondary O&M Operation and PCell Primary Cell

[0421] Synchronization Maintenance PCI Physical Cell ID,

[0422] Signal 0DU2 Optical channel Physical Cell

[0423] NR New Radio, Data Unit - type 2 Identity

[0424] Neighbour Relation OFDM Orthogonal PCEF Policy and

[0425] NRF NF Repository Frequency Division Charging

[0426] Function Multiplexing Enforcement Function PHY Physical layer PRR Packet Reception

[0427] PCF Policy Control PLMN Public Land Mobile Radio Function Network PS Packet Services

[0428] PCRF Policy Control and PIN Personal PSBCH Physical Charging Rules Identification Number Sidelink Broadcast Function PM Performance Channel

[0429] PDCP Packet Data Measurement PSDCH Physical Convergence Protocol, PMI Preceding Matrix Sidelink Downlink Packet Data Indicator Channel

[0430] Convergence PNF Physical Network PSCCH Physical Protocol layer Function Sidelink Control

[0431] PDCCH Physical PNFD Physical Network Channel

[0432] Downlink Control Function Descriptor PSSCH Physical

[0433] Channel PNFR Physical Network Sidelink Shared

[0434] PDCP Packet Data Function Record Channel Convergence Protocol POC PTT over Cellular PSFCH physical PDN Packet Data PP, PTP Point-to- sidelink feedback Network, Public Data Point channel

[0435] Network PPP Point-to-Point PSCell Primary SCell

[0436] PDSCH Physical Protocol PSS Primary

[0437] Downlink Shared PRACH Physical S y nchronization

[0438] Channel RACH Signal

[0439] PDU Protocol Data Unit PRB Physical resource PSTN Public Switched

[0440] PEI Permanent block Telephone Network Equipment Identifiers PRG Physical resource PT-RS Phase-tracking PFD Packet Flow block group reference signal Description ProSe Proximity Services, PTT Push-to-Talk

[0441] P-GW PDN Gateway Proximity-Based PUCCH Physical PHICH Physical Service Uplink Control hybrid-ARQ indicator PRS Positioning Channel channel Reference Signal PUSCH Physical Uplink Shared Response Management Channel RAT Radio Access RMC Reference

[0442] QAM Quadrature Technology Measurement Channel

[0443] Amplitude Modulation RAU Routing Area RMSI Remaining MSI,

[0444] QCI QoS class of Update Remaining Minimum identifier RB Resource block, System Information

[0445] QCL Quasi co-location Radio Bearer RN Relay Node QFI QoS Flow ID, QoS RBG Resource block RNC Radio Network Flow Identifier group Controller

[0446] QoS Quality of Service REG Resource Element RNL Radio Network QPSK Quadrature Group Layer (Quaternary) Phase Shift Rel Release RNTI Radio Network Keying REQ REQuest Temporary Identifier

[0447] 8SS Quasi-Zenith RF Radio Frequency ROHC RObust Header

[0448] Satellite System RI Rank Indicator Compression

[0449] RA-RNTI Random RIV Resource indicator RRC Radio Resource

[0450] Access RNTI value Control, Radio

[0451] RAB Radio Access RL Radio Link Resource Control layer

[0452] Bearer, Random RLC Radio Link RRM Radio Resource

[0453] Access Burst Control, Radio Link Management

[0454] RACH Random Access Control layer RS Reference Signal

[0455] Channel RLC AM RLC RSRP Reference Signal

[0456] RADIUS Remote Acknowledged Mode Received Power

[0457] Authentication Dial In RLC UM RLC RSRQ Reference Signal

[0458] User Service Unacknowledged Mode Received Quality

[0459] RAN Radio Access RLF Radio Link Failure RS SI Received Signal

[0460] Network RLM Radio Link Strength Indicator

[0461] RAND RANDom number Monitoring RSU Road Side Unit (used for RLM-RS Reference RSTD Reference Signal authentication) Signal for RLM Time difference RAR Random Access RM Registration RTP Real Time Protocol RTS Ready-To-Send Secondary CC Transmission RTT Round Trip Time SCcll Secondary Cell SDU Service Data Unit Rx Reception, SCEF Service SEAF Security Anchor Receiving, Receiver Capability Exposure Function S1AP SI Application Function SeNB secondary eNB Protocol SC-FDMA Single SEPP Security Edge

[0462] SI -MME SI for the Carrier Frequency Protection Proxy control plane Division Multiple SFI Slot format

[0463] Sl-U SI for the user Access indication plane SCG Secondary Cell SFTD Space-Frequency

[0464] S-CSCF serving Group Time Diversity, SFN and CSCF SCM Security Context frame timing difference

[0465] S-GW Serving Gateway Management SFN System Frame

[0466] S-RNTI SRNC SCS Subcarrier Spacing Number

[0467] Radio Network SCTP Stream Control SgNB Secondary gNB

[0468] Temporary Identity Transmission SGSN Serving GPRS S-TMSI SAE Protocol Support Node Temporary Mobile SDAP Service Data S-GW Serving Gateway

[0469] Station Identifier Adaptation Protocol, SI System Information

[0470] SA Standalone Service Data Adaptation SI-RNTI System operation mode Protocol layer Information RNTI SAE System SDL Supplementary SIB System Information Architecture Evolution Downlink Block SAP Service Access SDNF Structured Data SIM Subscriber Identity Point Storage Network Module

[0471] SAPD Service Access Function SIP Session Initiated Point Descriptor SDP Session Description Protocol SAPI Service Access Protocol SiP System in Package Point Identifier SDSF Structured Data SL Sidelink SCC Secondary Storage Function SLA Service Level Component Carrier, SDT Small Data Agreement SM Session Identifier SST Slice / Service Types

[0472] Management SS / PBCH Block SU-MIMO Single User

[0473] SMF Session SSBRI SS / PBCH Block MIMO

[0474] Management Function Resource Indicator, SUL Supplementary

[0475] SMS Short Message Synchronization Uplink Service Signal Block TA Timing Advance,

[0476] SMSF SMS Function Resource Indicator Tracking Area

[0477] SMTC SSB-based SSC Session and Service TAC Tracking Area

[0478] Measurement Timing Continuity Code Configuration SS-RSRP TAG Timing Advance

[0479] SN Secondary Node, Synchronization Group Sequence Number Signal based Reference TAI Tracking SoC System on Chip Signal Received Area Identity SON Self-Organizing Power TAU Tracking Area

[0480] Network SS-RSRQ Update

[0481] SpCell Special Cell Synchronization TB Transport Block SP-CSI-RNTISemi- Signal based Reference TBS Transport Block

[0482] Persistent CSI RNTI Signal Received Size

[0483] SPS Semi-Persistent Quality TBD To Be Defined

[0484] Scheduling SS-SINR TCI Transmission

[0485] SQN Sequence number Synchronization Configuration Indicator SR Scheduling Request Signal based Signal to TCP Transmission

[0486] SRB Signalling Radio Noise and Interference Communication Bearer Ratio Protocol

[0487] SRS Sounding SSS Secondary TDD Time Division

[0488] Reference Signal Synchronization Duplex

[0489] SS Synchronization Signal TDM Time Division

[0490] Signal SSSG Search Space Set Multiplexing

[0491] SSB Synchronization Group TDMATime Division Signal Block SSSIF Search Space Set Multiple Access

[0492] SSID Service Set Indicator TE Terminal Equipment Temporary Identity Locator

[0493] TEID Tunnel End Point UART Universal URLLC Ultra¬

[0494] Identifier Asynchronous Reliable and Low

[0495] TFT Traffic Flow Receiver and Latency

[0496] Template Transmitter USB Universal Serial

[0497] TMSI Temporary Mobile UCI Uplink Control Bus

[0498] Subscriber Identity Information USIM Universal

[0499] TNL Transport Network UE User Equipment Subscriber Identity Module

[0500] Layer UDM Unified Data USS UE- specific search

[0501] TPC Transmit Power Management space

[0502] Control UDP User Datagram UTRA UMTS Terrestrial

[0503] TPMI Transmitted Protocol Radio Access

[0504] Precoding Matrix UDSF Unstructured Data UTRAN Universal

[0505] Indicator Storage Network Terrestrial Radio

[0506] TR Technical Report Function Access Network

[0507] TRP, TRxP UICC Universal UwPTS Uplink Pilot

[0508] Transmission Integrated Circuit Card Time Slot

[0509] Reception Point UL Uplink V2I Vehicle-to-

[0510] TRS Tracking Reference UM Unacknowledged Infrastruction

[0511] Signal Mode V2P Vehicle-to-

[0512] TRx Transceiver UML Unified Modelling Pedestrian

[0513] TS Technical Language V2V Vehicle-to-Vehicle

[0514] Specifications, UMTS Universal Mobile V2X Vehicle-to-

[0515] Technical Standard Telecommunication every thing

[0516] TTI Transmission Time s System VIM Virtualized

[0517] Interval UP User Plane Infrastructure Manager

[0518] Tx Transmission, UPF User Plane VL Virtual Link,

[0519] Transmitting, Function VLAN Virtual LAN,

[0520] Transmitter URI Uniform Resource Virtual Local Area

[0521] U-RNTI UTRAN Identifier Network

[0522] Radio Network URL Uniform Resource VM Virtual Machine VNF Virtualized Network WPANWireless Personal

[0523] Network Function VPN Virtual Private Area Network

[0524] VNFFG VNF Network X2-C X2-Control plane

[0525] Forwarding Graph VRB Virtual Resource X2-U X2-User plane

[0526] VNFFGD VNF Block XML extensible Markup

[0527] Forwarding Graph WiMAX Worldwide Language

[0528] Descriptor Interoperability for XRES EXpected user

[0529] VNFM VNF Manager Microwave Access RESponse VoIP Voice-over- IP, WLANWireless Local XOR exclusive OR Voice-over- Internet Area Network ZC Zadoff-Chu Protocol WMAN Wireless ZP Zero Power

[0530] VPLMN Visited Metropolitan Area

[0531] Public Land Mobile Network

[0532] Terminology

[0533] For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0534] The term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment. The term “AI / ML application” or the like may be an application that contains some AI / ML models and application-level descriptions.

[0535] The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field- programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the 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 a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality 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.

[0536] The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store 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 computerexecutable instructions, such as program code, software modules, and / or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or 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 to, and may be referred to as, “processor circuitry.”

[0537] The term “interface circuitry” as used herein refers to, is 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, for example, buses, I / O interfaces, peripheral component interfaces, network interface cards, and / or the like.

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

[0539] The term “network element” as used herein 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 to and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and / or the like.

[0540] The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and / or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled with one another and configured to share computing and / or networking resources.

[0541] The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

[0542] The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and applications, workload units, and / or the like. A “hardware resource” may refer to compute, storage, and / or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and / or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices / sy stems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and / or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0543] The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and / or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and / or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0544] The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

[0545] The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact 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 with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and / or the like.

[0546] The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

[0547] The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .

[0548] The term “SSB” refers to an SS / PBCH block.

[0549] The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0550] The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

[0551] The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA. The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCcll and zero or more secondary cells for a UE configured with DC.

[0552] The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA / DC there is only one serving cell comprising of the primary cell.

[0553] The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA / .

[0554] The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

[0555] The term “machine learning” or “ML” refers to the use of computer systems implementing algorithms and / or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences. ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets. Although the term “ML algorithm” refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.

[0556] The term “machine learning model,” “ML model,” or the like may also refer to ML methods and concepts used by an ML-assisted solution. An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), descision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like. Depending on the implementation a specific ML model could have many sub-models as components and the ML model may train all sub-models together. Separately trained ML models can also be chained together in an ML pipeline during inference. An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference). The term “ML training host” refers to an entity, such as a network function, that hosts the training of the model. The term “ML inference host” refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable). The ML- host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution). The term “model inference information” refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.

Claims

CLAIMS1. A user equipment (UE) comprising: memory to store: first configuration information related to uplink (UL) transmission on one or more subband non-overlapping full duplex (SBFD) symbols; and second configuration information related to UL transmission on one or more non- SBFD symbols; and one or more processors configured to encode, based on the first configuration information and the second configuration information, a plurality of uplink (UL) transmissions.

2. The UE of claim 1, wherein the plurality of UL transmissions are transmitted on SBFD symbols, or the plurality of UL transmissions are transmitted on non-SBFD symbols.

3. The UE of claim 1, wherein at least one of the plurality of UL transmissions is transmitted on an SBFD symbol, and another of the plurality of UL transmissions is transmitted on a non-SBFD symbol.

4. The UE of claim 1, wherein the plurality of UL transmissions are a plurality of physical uplink control channel (PUCCH) transmissions.

5. The UE of claim 1, wherein the plurality of UL transmissions are a plurality of physical random access channel (PRACH) transmissions.

6. The UE of claim 5, wherein the plurality of PRACH transmissions are associated with a same synchronization signal block (SSB) as one another.

7. The UE of any of claims 1-6, wherein the plurality of UL transmissions include a first UL transmission and a repetition of the first UL transmission.

8. The UE of any of claims 1-6, wherein a SBFD symbol is a time domain symbol thatsimultaneously carries UL data and downlink (DL) data.

9. The UE of claim 8, wherein the UL data is carried on different frequency resources of the SBFD symbol than the DL data.

10. The UE of any of claims 1-6, wherein a non-SBFD symbol is a time domain symbol that is not configured to simultaneously carry UL and downlink (DL) data.

11. One or more computer-readable media comprising instructions that, upon execution of the instructions by one or more processors of an electronic device, are to cause a base station to: transmit, to a user equipment (UE), first configuration information related to uplink (UL) transmission on one or more subband non-overlapping full duplex (SBFD) symbols; transmit, to the UE, second configuration information related to UL transmission on one or more non-SBFD symbols; and identify, from the UE based on the first configuration information and the second configuration information, a plurality of uplink (UL) transmissions.

12. The one or more computer-readable media of claim 11, wherein the plurality of UL transmissions are transmitted on SBFD symbols, or the plurality of UL transmissions are transmitted on non-SBFD symbols.

13. The one or more computer-readable media of claim 11, wherein at least one of the plurality of UL transmissions is transmitted on an SBFD symbol, and another of the plurality of UL transmissions is transmitted on a non-SBFD symbol.

14. The one or more computer-readable media of claim 11, wherein the plurality of UL transmissions are a plurality of physical uplink control channel (PUCCH) transmissions.

15. The one or more computer-readable media of claim 11, wherein the plurality of UL transmissions are a plurality of physical random access channel (PRACH) transmissions.

16. The one or more computer-readable media of any of claims 11-15, wherein the plurality of UL transmissions include a first UL transmission and a repetition of the first UL transmission.

17. One or more computer readable media comprising instructions that, upon execution of the instructions by one or more processors of an electronic device, are to cause a user equipment (UE) to: identify first configuration information related to uplink (UL) transmission on one or more subband non-overlapping full duplex (SBFD) symbols; identify second configuration information related to UL transmission on one or more non-SBFD symbols; and transmit, based on the first configuration information and the second configuration information, a plurality of uplink (UL) transmissions.

18. The one or more computer-readable media of claim 17, wherein the plurality of UL transmissions are transmitted on SBFD symbols, or the plurality of UL transmissions are transmitted on non-SBFD symbols.

19. The one or more computer-readable media of claim 17, wherein at least one of the plurality of UL transmissions is transmitted on an SBFD symbol, and another of the plurality of UL transmissions is transmitted on a non-SBFD symbol.

20. The one or more computer-readable media of any of claims 19, wherein the plurality of UL transmissions are a plurality of physical uplink control channel (PUCCH) transmissions or a plurality of physical random access channel (PRACH) transmissions.

Images