WO2024097726A1 - Allocation de ressources pour mise en forme du spectre dans le domaine fréquentiel avec extension du spectre - Google Patents

Allocation de ressources pour mise en forme du spectre dans le domaine fréquentiel avec extension du spectre Download PDF

Info

Publication number
WO2024097726A1
WO2024097726A1 PCT/US2023/078312 US2023078312W WO2024097726A1 WO 2024097726 A1 WO2024097726 A1 WO 2024097726A1 US 2023078312 W US2023078312 W US 2023078312W WO 2024097726 A1 WO2024097726 A1 WO 2024097726A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
pusch
fdss
frequency domain
extended
Prior art date
Application number
PCT/US2023/078312
Other languages
English (en)
Inventor
Gang Xiong
Yi Wang
Avik SENGUPTA
Yingyang Li
Prerana Rane
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2024097726A1 publication Critical patent/WO2024097726A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2626—Arrangements specific to the transmitter only
    • H04L27/2627—Modulators
    • H04L27/2634—Inverse fast Fourier transform [IFFT] or inverse discrete Fourier transform [IDFT] modulators in combination with other circuits for modulation
    • H04L27/2636—Inverse fast Fourier transform [IFFT] or inverse discrete Fourier transform [IDFT] modulators in combination with other circuits for modulation with FFT or DFT modulators, e.g. standard single-carrier frequency-division multiple access [SC-FDMA] transmitter or DFT spread orthogonal frequency division multiplexing [DFT-SOFDM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2626—Arrangements specific to the transmitter only
    • H04L27/2627—Modulators
    • H04L27/2634—Inverse fast Fourier transform [IFFT] or inverse discrete Fourier transform [IDFT] modulators in combination with other circuits for modulation
    • H04L27/26362—Subcarrier weighting equivalent to time domain filtering, e.g. weighting per subcarrier multiplication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2626—Arrangements specific to the transmitter only
    • H04L27/2627—Modulators
    • H04L27/264—Pulse-shaped multi-carrier, i.e. not using rectangular window
    • H04L27/26412—Filtering over the entire frequency band, e.g. filtered orthogonal frequency-division multiplexing [OFDM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2626—Arrangements specific to the transmitter only
    • H04L27/2646—Arrangements specific to the transmitter only using feedback from receiver for adjusting OFDM transmission parameters, e.g. transmission timing or guard interval length
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • This disclosure generally relates to systems and methods for wireless communications and, more particularly, to resource allocation for frequency domain spectrum shaping with spectrum extension.
  • 5G next generation wireless communication system
  • NR new radio
  • FIGs. 1-5 depict illustrative schematic diagrams for enhanced resource allocation, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 illustrates a flow diagram of illustrative process for an illustrative enhanced resource allocation system, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 illustrates an example network architecture, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 8 schematically illustrates a wireless network, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 9 illustrates components of a computing device, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 10 illustrates a network in accordance with various embodiments. DETAILED DESCRIPTION
  • NR next generation wireless communication system
  • 5G may also be referred to as “new radio” or (NR) herein
  • NR new radio
  • 3GPP third generation partnership project
  • LTE long term evolution
  • RATs Radio Access Technologies
  • NR For cellular systems, coverage may be an important factor for successful operation. Compared to LTE. NR can be deployed at a relatively higher carrier frequency in frequency range 1 (FR1). e.g., at 3.5 gigahertz (GHz). In this case, coverage loss is expected due to a larger path-loss, which makes it more challenging to maintain an adequate quality of service. Typically, uplink coverage is the bottleneck for system operation considering the low transmit power at UE side.
  • FR1 frequency range 1
  • GHz gigahertz
  • NR supports Frequency Domain Spectral Shaping (FDSS) without spectrum extension for a/2 binary phase shift keying (BPSK) to reduce the Peak-to-Average-Power Ratio (PAPR). With a smooth transition at the occupied bandwidth, PAPR for the physical uplink shared channel (PUSCH) transmission may be reduced accordingly.
  • FDSS Frequency Domain Spectral Shaping
  • BPSK binary phase shift keying
  • PAPR Peak-to-Average-Power Ratio
  • FDSS frequency domain spectrum shaping
  • DFT-s-OFDM Discrete Fourier Transform-spread-orthogonal frequency-division multiplexing
  • Example embodiments of the present disclosure relate to systems, methods, and devices for resource allocation for frequency domain spectrum shaping with spectrum extension.
  • Embodiments herein relate to mechanisms on the resource allocation for frequency domain spectrum shaping with spectrum extension.
  • embodiments may include one or more of the following:
  • DMRS Demodulation reference signal
  • TBS transport block size
  • FIG. 1 depicts an illustrative schematic diagram for enhanced resource allocation, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 1 illustrates one example of frequency domain spectrum shaping with spectrum extension (FDSS-SE) scheme with symmetric extension.
  • FDSS-SE frequency domain spectrum shaping with spectrum extension
  • Frequency Domain Spectrum Shaping with Spectrum Extension is an advanced digital signal processing technique commonly used in wireless communications to optimize system performance. It combines the advantages of Frequency Domain Spectrum Shaping (FDSS). which manipulates the signal in the frequency domain to optimize power and reduce out-of-band radiation, with Spectrum Extension (SE), which artificially extends the signal’s bandwidth to enhance data throughput or reception.
  • FDSS Frequency Domain Spectrum Shaping
  • SE Spectrum Extension
  • the FDSS-SE scheme allows for better utilization of the frequency spectrum, reduced interference with adjacent channels, and improved signal-to-noise ratios.
  • FDSS-SE offers a balanced compromise between efficiency, interference reduction, and performance improvement in communication systems.
  • modulated symbols after discrete fourier transform (DFT) operation are input to spectrum extension block, where either symmetric extension or cyclic extension may be applied.
  • DFT discrete fourier transform
  • symmetnc extension lower and upper part of modulated symbols after DFT operation are exchanged and appended to upper and lower part of the allocated resource, respectively.
  • cyclic extension lower part of modulated symbols after DFT operation are cyclically appended to the upper part of the allocated resource.
  • the modulated symbols after spectrum extension are filtered for spectrum shaping, followed by resource mapping on the allocated resource including extended resources and inverse fast fourier transformation (IFFT) operation.
  • IFFT inverse fast fourier transformation
  • gNodeB gNodeB
  • UE user equipment
  • whether frequency domain spectrum shaping with spectrum extension (FDSS-SE) is enabled or disabled can be configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling, dynamically indicated in the downlink control information (DCI), or a combination thereof.
  • RMSI remaining minimum system information
  • OSI NR other system information
  • RRC dedicated radio resource control
  • FDSS-SE for dynamic grant PUSCH (DG-PUSCH) scheduled by a DCI, whether FDSS-SE is enabled or disabled can be dynamically indicated in the scheduling DCI.
  • FDSS-SE for configured grant PUSCH (CG-PUSCH), including Type 1 and/or Type 2 CG-PUSCH, whether FDSS-SE is enabled or disabled can be configured by higher layers via RRC signalling.
  • UE is not expected to be indicated or configured with enabling FDSS-SE.
  • CP-OFDM orthogonal frequency division multiplexing
  • UE does not apply FDSS-SE for the PUSCH.
  • the allocated resource in frequency domain which is determined from frequency domain resource allocation (FDRA) indicated in the DCI, e.g., for DG-PUSCH or provided by RRC signalling, e.g., for CG-PUSCH, does not include the extended resource for FDSS-SE operation.
  • FDRA frequency domain resource allocation
  • FIG. 2 depicts an illustrative schematic diagram for enhanced resource allocation, in accordance with one or more example embodiments of the present disclosure.
  • UE determines the number of PRBs for extended resource on each side of allocated resource based on the indicated/configured scaling factor and the number of PRBs for the allocated resource for PUSCH transmission.
  • the allocated resource in frequency domain which is determined from frequency domain resource allocation (FDRA) indicated in the DCI, e.g.. for DG-PUSCH or provided by RRC signalling, e.g., for CG-PUSCH, includes the extended resource for FDSS-SE operation.
  • FDRA frequency domain resource allocation
  • FIG. 3 depicts an illustrative schematic diagram for enhanced resource allocation, in accordance with one or more example embodiments of the present disclosure.
  • UE determines the number of PRBs for extended resource on each side of allocated resource based on the indicated/configured scaling factor and the number of PRBs for the allocated resource for PUSCH transmission.
  • a scaling factor that is the ratio between the number of PRBs for allocated resource and extended resources can be configured by higher layers via RMSI, OSI, or RRC signalling or dynamically indicated in the DCI or a combination thereof.
  • a set of scaling factor may be configured by higher layers via RRC configuration, while one field in the DCI can be used to indicate one scaling factor from the configured set of scaling factors for FDSS-SE operation.
  • UE can determine the number of PRBs for extended resource. Denote the scaling factor as a. the number of PRBs for the extended resource on each side, may be determined as
  • the number of PRBs for the extended resource on each side is N ⁇ /2. Specifically, if /V, ⁇ is an odd value, it indicates that the extend resource on each side is a number of PRBs plus a half PRB or a full PRB.
  • the number of PRBs for the extended resource may be determined as
  • N ⁇ SCH is indicated or configured number of PRBs for PUSCH transmission.
  • a set of numbers of the PRBs as the extended resource can be configured by a high layer signaling depending on the number of allocated PRBs of PUSCH.
  • the above embodiments may be applied for the case when allocated resource for PUSCH transmission excludes or includes extended resource for FDSS-SE scheme.
  • a single DMRS sequence is associated with PUSCH transmission with FDSS-SE scheme, where the length of DMRS sequence is determined in accordance with the number of PRBs including extended resources for PUSCH transmission.
  • the reference point for k for DMRS sequence mapping is subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation including extended resource if transform precoding is enabled.
  • FIG. 4 depicts an illustrative schematic diagram for enhanced resource allocation, in accordance with one or more example embodiments of the present disclosure.
  • reference point for DMRS sequence mapping for FDSS-SE scheme (Option 1).
  • the reference point for DMRS sequence mapping on the physical resource is the lowest PRB for the allocated resource for PUSCH transmission with FDSS-SE scheme, including extended resource.
  • the length of DMRS sequence is determined in accordance with the number of PRBs excluding extended resources for PUSCH transmission.
  • the reference point for k for DMRS sequence mapping is subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation excluding extended resource if transform precoding is enabled.
  • FIG. 5 depicts an illustrative schematic diagram for enhanced resource allocation, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 there is shown one example of reference point for DMRS sequence mapping for FDSS-SE scheme (Option 2).
  • the reference point for DMRS sequence mapping on the physical resource is the lowest PRB for the allocated resource for PUSCH transmission with FDSS-SE scheme, excluding extended resource.
  • the DM-RS sequence can be generated according to the previous embodiment, and then SE can be performed on the DM-RS sequence and subsequently, the extended DM-RS sequence is modulated using a pi/2-BPSK constellation wherein the length of the DM-RS sequence provided as input to the modulation mapper is based on the number of PRBs including extended resources for PUSCH transmission.
  • the DM-RS sequence can be generated based on the allocated resources for PUSCH transmission excluding the extended resources. The sequence is then mapped to a pi/2-BPSK constellation. SE is subsequently performed for the modulated DM-RS symbols wherein, a fixed phased offset is applied to the DM-RS sequence mapped to the REs which are part of the extended resources.
  • Embodiments of determination of transport block size (TBS) for FDSS-SE scheme are provided as follows:
  • the number of PRBs used for TBS determination for the corresponding PUSCH transmission excludes the number of PRBs for extended resource.
  • a UE determines the total number of REs allocated for PUSCH (A RE ) as follows:
  • N RE N * min(156, N E ) • n PRB
  • n PRB is the total number of allocated PRBs excluding the number of PRBs for extended resource for the UE and N is the number of slots used for TBS determination indicated by numberOfSlotsTBoMS.
  • N RE min(156, N RE ) ⁇ n PRB .
  • a UE determines the total number of REs allocated for PUSCH (N RE ) as follows:
  • N RE N * min(156, N RE ) ⁇ n' PRB
  • n 'pRB n PRB — 2 ⁇ [a ⁇ n PRB /2]
  • n PRB is the total number of allocated PRBs for the UE and a is a scaling factor, which is provided by higher layer;
  • N is the number of slots used for TBS determination indicated by numberOfSlotsTBoMS.
  • N RE min(156, N RE • n' PRB .
  • Embodiments of determination of phase tracking reference signal (PT-RS) group pattern are provided as follows:
  • group pattern for PT-RS associated with PUSCH transmission can be determined in accordance with the number of scheduled RBs, which may include the number of RBs for extended resources for FDSS-SE scheme.
  • group pattern for PT-RS associated with PUSCH transmission can be determined in accordance with the number of scheduled RBs, which may exclude the number of RBs for extended resources for FDSS-SE scheme. This may apply for the case when allocated resource includes extended resource for FDSS-SE scheme.
  • Table 1 PT-RS group pattern as a function of scheduled bandwidth excluding extended bandwidth:
  • UE performs transform precoding according to: resulting in a block of complex-valued symbols — 1 .
  • the number of PRBs to determine PUSCH transmission power is the number of PRBs allocated for PUSCH transmission excluding the number of PRBs for extended resource.
  • M RB b C (i) in the equation below is the number of PRBs allocated for PUSCH transmission excluding the number of PRBs for extended resource.
  • Embodiments of determination of UL transmission overlapping with PRBs indicated by UL cancellation indication (CI) are provided as follows:
  • a UE if a UE is scheduled or configured for a PUSCH transmission with priority 0 with FDSS-SE operation, and if any PRB allocated or configured for the PUSCH excluding the extended resource for FDSS-SE operation overlaps with a PRB for UL Cancellation by UL CI, the UE cancels the PUSCH.
  • a UE if a UE is scheduled or configured for a PUSCH transmission with priority 0 with FDSS-SE operation, and if any PRB allocated or configured the PUSCH including extended resource for FDSS-SE operation overlaps with a PRB for UL Cancellation by UL CI, the UE cancels the PUSCH.
  • a UE if a UE is scheduled or configured for a PUSCH transmission with priority 0 with FDSS-SE operation, and if any PRB allocated or configured the PUSCH excluding extended resource for FDSS-SE operation does not overlap with a PRB for UL Cancellation by UL CI, and at least one PRB of the extended resource for FDSS-SE operation for the PUSCH overlaps with a PRB for UL Cancellation by UL CL UE does not transmit on the overlapped PRB, or does not transmit the PRB in the extended resource. In this case, UE transmits PUSCH on PRBs excluding these PRBs. Alternatively, UE does not apply FDSS-SE for the PUSCH.
  • the FDSS-SE scheme may also apply for the transmission of PUCCH format 3 or format 4 which is based on DFT-s-OFDM waveform.
  • a scaling factor may be included as part of PUCCH resource configuration or PUCCH resource set configuration.
  • the actual transmitted number of PRBs is determined in accordance with the number of configured PRBs for PUCCH transmission, excluding the number of PRBs for the extended resource.
  • an enhanced resource allocation system may enable wireless communication for 5G or NR systems, where a gNB may indicate a scaling factor and an enabling of FDSS-SE for PUSCH transmission, and a UE may transmit the PUSCH in accordance with the indicated scaling factor and FDSS-SE scheme.
  • the enhanced resource allocation system may also configure whether FDSS-SE is enabled or disabled through higher layers via RMSI, OSI, or dedicated RRC signaling, or dynamically indicate it in the DCI, or a combination thereof. For a PUSCH configured with CP-OFDM waveform or when a transform precoder is disabled, the UE may not apply FDSS-SE.
  • the allocated resource in the frequency domain for PUSCH transmission may be determined from FDRA indicated in the DCI or provided by RRC signaling, and may either include or not include extended resources for FDSS-SE operation.
  • the scaling factor which is the ratio between the number of PRBs for allocated and extended resources, may also be configured by higher layers or dynamically indicated in the DCI.
  • a set of numbers of PRBs as extended resources may be configured by high-layer signaling depending on the number of allocated PRBs for PUSCH.
  • a single DMRS sequence may be associated, and its length may be determined based on the number of PRBs, including extended resources.
  • the reference point for k for DMRS sequence mapping may be subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation, either including or excluding extended resources, depending on whether transform precoding is enabled. Similar procedures may apply for the DMRS sequence itself, affecting its length in accordance with the number of PRBs either including or excluding extended resources.
  • the number of PRBs may either include or exclude extended resources.
  • the UE may cancel the PUSCH. If there is no overlap but at least one PRB of the extended resource does overlap, the UE may either not transmit on the overlapped PRB or not transmit the PRB in the extended resource. Additionally, FDSS-SE may also be applied to PUCCH format 3 or format 4 transmissions. Finally, the actual number of transmitted PRBs may be determined in line with the number of configured PRBs for PUCCH transmission, excluding the number of PRBs for the extended resource.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of FIGs. 7-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 FIG. 6.
  • the process may include, at 602, receiving from a next generation radio access network (gNB) an indication of a scaling factor and an indication of enabling frequency domain spectrum shaping with spectrum extension (FDSS-SE) for a physical uplink shared channel (PUSCH) transmission.
  • gNB next generation radio access network
  • FDSS-SE frequency domain spectrum shaping with spectrum extension
  • the process further includes, at 604, selecting a scaling factor as a ratio between a number of physical resource blocks (PRBs) for allocated resource and extended resources or total resource including extended resource.
  • PRBs physical resource blocks
  • the process further includes, at 606, selecting an allocated resource in a frequency domain for a physical uplink shared channel (PUSCH) from frequency domain resource allocation (FDRA) indicated in a downlink control information (DCI) or provided by radio resource control (RRC) signaling.
  • PUSCH physical uplink shared channel
  • FDRA frequency domain resource allocation
  • DCI downlink control information
  • RRC radio resource control
  • the process further includes, at 608, transmitting the PUSCH in accordance with the scaling factor and the indication of FDSS-SE using the allocated resource and extended resource.
  • the device may receive configuration of whether FDSS-SE is enabled or disabled from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling.
  • the device may not apply FDSS-SE for the PUSCH when a cyclic prefix (CP)-orthogonal frequency-division multiplexing (OFDM) waveform is indicated or when transform precoding is disabled.
  • the device may determine the allocated resource in the frequency domain from FDRA indicated for Dynamic grant PUSCH (DG-PUSCH) or provided by RRC signaling for Configured grant PUSCH (CG-PUSCH).
  • DG-PUSCH Dynamic grant PUSCH
  • CG-PUSCH Configured grant PUSCH
  • the device may select the scaling factor either from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling or dynamically indicated in the downlink control information (DCI).
  • the device may include the extended resource for FDSS-SE operation when determining the allocated resource in the frequency domain.
  • the device may determine a set of numbers of the PRBs as the extended resource based on high layer signaling depending on the number of allocated PRBs of PUSCH and/or indication in the DCI.
  • the device may associate a single demodulation reference signal (DMRS) sequence with the PUSCH transmission with FDSS-SE scheme with length determined in accordance with the allocated resource and extended resource.
  • DMRS demodulation reference signal
  • the device in any one of the preceding claims, may determine the reference point for k for DMRS sequence mapping as subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation including extended resource when transform precoding is enabled.
  • 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.
  • 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'.
  • 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.
  • FIGs. Error! Reference source not found.- 10 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 7 illustrates an example network architecture 700 according to various embodiments.
  • the network 700 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • 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 3GPP systems, or the like.
  • the network 700 includes a UE 702, which is any mobile or non-mobile computing device designed to communicate with a RAN 704 via an over-the-air connection.
  • the UE 702 is communicatively coupled with the RAN 704 by a Uu interface, which may be applicable to both LTE and NR systems.
  • Examples of the UE 702 include, but are not limited to, a smartphone, tablet computer, wearable computer, desktop computer, laptop computer, in- vehicle infotainment system, in-car entertainment system, instrument cluster, head-up display (HUD) 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, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) device, Internet of Things (loT) device, and/or the like.
  • HUD head-up display
  • the network 700 may include a plurality of UEs 702 coupled directly with one another via a D2D, ProSe, PC5, and/or sidelink (SL) interface.
  • UEs 702 may be M2M/D2D/MTC/IoT devices and/or vehicular systems that communicate using physical sidelink channels such as. but not limited to, PSBCH. PSDCH, PSSCH. PSCCH, PSFCH, etc.
  • the UE 702 may perform blind decoding attempts of SL channels/links according to the various embodiments herein.
  • the UE 702 may additionally communicate with an AP 706 via an over-the-air (OTA) connection.
  • the AP 706 manages a WLAN connection, which may serve to offload some/all network traffic from the RAN 704.
  • the connection between the UE 702 and the AP 706 may be consistent with any IEEE 802.11 protocol.
  • the UE 702, RAN 704, and AP 706 may utilize cellular- WLAN aggregation/integration (e.g., LWA/LWIP).
  • Cellular-WLAN aggregation may involve the UE 702 being configured by the RAN 704 to utilize both cellular radio resources and WLAN resources.
  • the RAN 704 includes one or more access network nodes (ANs) 708.
  • the ANs 708 terminate air-interface(s) for the UE 702 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and PHY/L1 protocols. In this manner, the AN 708 enables data/voice connectivity between CN 720 and the UE 702.
  • the ANs 708 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; or some combination thereof.
  • an AN 708 be referred to as a BS, gNB, RAN node. eNB. ng-eNB, NodeB. RSU, TRxP, etc.
  • One example implementation is a ”CU/DU split” architecture where the ANs 708 are embodied as a gNB-Central Unit (CU) that is communicatively coupled with one or more gNB- Distributed Units (DUs), where each DU may be communicatively coupled with one or more Radio Units (RUs) (also referred to as RRHs, RRUs, or the like) (see e g., 3GPP TS 38.401 V16.1.0 (2020-03)).
  • RUs Radio Units
  • the one or more RUs may be individual RSUs.
  • the CU/DU split may include an ng-eNB-CU and one or more ng- eNB-DUs instead of, or in addition to, the gNB-CU and gNB-DUs, respectively.
  • the ANs 708 employed as the CU 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 including a virtual Base Band Unit (BBU) or BBU pool, cloud RAN (CRAN), Radio Equipment Controller (REC), Radio Cloud Center (RCC), centralized RAN (C-RAN), virtualized RAN (vRAN), and/or the like (although these terms may refer to different implementation concepts). Any other type of architectures, arrangements, and/or configurations can be used.
  • BBU Virtual Base Band Unit
  • CRAN cloud RAN
  • REC Radio Equipment Controller
  • RRCC Radio Cloud Center
  • C-RAN centralized RAN
  • vRAN virtualized RAN
  • the plurality of ANs may be coupled with one another via an X2 interface (if the RAN 704 is an LTE RAN or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 710) or an Xn interface (if the RAN 704 is a NG-RAN 714).
  • 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.
  • the ANs of the RAN 704 may each manage one or more cells, cell groups, component earners, etc. to provide the UE 702 with an air interface for network access.
  • the UE 702 may be simultaneously connected with a plurality of cells provided by the same or different ANs 708 of the RAN 704.
  • the UE 702 and RAN 704 may use carrier aggregation to allow the UE 702 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN 708 may be a master node that provides an MCG and a second AN 708 may be secondary node that provides an SCG.
  • the first/second ANs 708 may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 704 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/camer-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 702 or AN 708 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications.
  • 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 -t pe RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • 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.
  • the RAN 704 may be an E-UTRAN 710 with one or more eNBs 712.
  • the an E-UTRAN 710 provides an LTE air interface (Uu) 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.
  • the RAN 704 may be an next generation (NG)-RAN 714 with one or more gNB 716 and/or on or more ng-eNB 718.
  • the gNB 716 connects with 5G-enabled UEs 702 using a 5G NR interface.
  • the gNB 716 connects with a 5GC 740 through an NG interface, which includes an N2 interface or an N3 interface.
  • the ng-eNB 718 also connects with the 5GC 740 through an NG interface, but may connect with a UE 702 via the Uu interface.
  • the gNB 716 and the ng-eNB 718 may connect with each other over an Xn interface.
  • 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 714 and a UPF 748 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 714 and an AMF 744 (e.g., N2 interface).
  • NG-U NG user plane
  • N-C NG control plane
  • the NG-RAN 714 may provide a 5G-NR air interface (which may also be referred to as a Uu 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 CSI-RS, 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.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 702 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 702, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 702 with different amount of frequency resources (e.g., 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 702 and in some cases at the gNB 716.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 704 is communicatively coupled to CN 720 that includes network elements and/or network functions (NFs) to provide various functions to support data and telecommunications services to customers/subscribers (e.g., UE 702).
  • the components of the CN 720 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 720 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 720 may be referred to as a network slice, and a logical instantiation of a portion of the CN 720 may be referred to as a network sub-slice.
  • the CN 720 may be an LTE CN 722 (also referred to as an Evolved Packet Core (EPC) 722).
  • the EPC 722 may include MME 724, SGW 726, SGSN 728, HSS 730, PGW 732, and PCRF 734 coupled with one another over interfaces (or ‘‘reference points'’) as shown.
  • the NFs in the EPC 722 are briefly introduced as follows.
  • the MME 724 implements mobility management functions to track a current location of the UE 702 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 726 terminates an SI interface toward the RAN 710 and routes data packets between the RAN 710 and the EPC 722.
  • the SGW 726 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 728 tracks a location of the UE 702 and performs security functions and access control.
  • the SGSN 728 also performs inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 724; MME 724 selection for handovers; etc.
  • the S3 reference point between the MME 724 and the SGSN 728 enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 730 includes a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 730 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 730 and the MME 724 may enable transfer of subscription and authentication data for authenticating/ authorizing user access to the EPC 720.
  • the PGW 732 may terminate an SGi interface toward a data network (DN) 736 that may include an application (app)/content server 738.
  • the PGW 732 routes data packets between the EPC 722 and the data network 736.
  • the PGW 732 is communicatively coupled with the SGW 726 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 732 may further include a node for policy enforcement and charging data collection (e.g., PCEF).
  • the SGi reference point may communicatively couple the PGW 732 with the same or different data network 736.
  • the PGW 732 may be communicatively coupled with a PCRF 734 via a Gx reference point.
  • the PCRF 734 is the policy and charging control element of the EPC 722.
  • the PCRF 734 is communicatively coupled to the app/content server 738 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 732 also provisions associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 720 may be a 5GC 740 including an AUSF 742, AMF 744, SMF 746, UPF 748, NSSF 750, NEF 752, NRF 754, PCF 756, UDM 758, and AF 760 coupled with one another over various interfaces as shown.
  • the NFs in the 5GC 740 are briefly introduced as follows.
  • the AUSF 742 stores data for authentication of UE 702 and handle authentication- related functionality.
  • the AUSF 742 may facilitate a common authentication framework for various access types..
  • the AMF 744 allows other functions of the 5GC 740 to communicate with the UE 702 and the RAN 704 and to subscribe to notifications about mobility events with respect to the UE 702.
  • the AMF 744 is also responsible for registration management (e.g., for registering UE 702), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 744 provides transport for SM messages between the UE 702 and the SMF 746, and acts as a transparent proxy for routing SM messages.
  • AMF 744 also provides transport for SMS messages between UE 702 and an SMSF.
  • AMF 744 interacts with the AUSF 742 and the UE 702 to perform various security anchor and context management functions.
  • AMF 744 is a termination point of a RAN-CP interface, which includes the N2 reference point between the RAN 704 and the AMF 744.
  • the AMF 744 is also a termination point of NAS (Nl) signaling, and performs NAS ciphering and integrity protection.
  • AMF 744 also supports NAS signaling with the UE 702 over an N3IWF interface.
  • the N3IWF provides access to untrusted entities.
  • N3IWF may be a termination point for the N2 interface between the (R)AN 704 and the AMF 744 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 714 and the 748 for the user plane.
  • the AMF 744 handles N2 signalling from the SMF 746 and the AMF 744 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, marks N3 user-plane packets in the uplink, and enforces QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received overN2.
  • N3IWF may also relay UL and DL control-plane NAS signalling between the UE 702 and AMF 744 via an Nl reference point between the UE 702and the AMF 744, and relay uplink and downlink user-plane packets between the UE 702 and UPF 748.
  • the N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 702.
  • the AMF 744 may exhibit an Namf service- based interface, and may be a termination point for an N14 reference point between two AMFs 744 and an N17 reference point between the AMF 744 and a 5G-EIR (not shown by FIG. 7).
  • the SMF 746 is responsible for SM (e.g., session establishment, tunnel management between UPF 748 and AN 708); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 748 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 744 over N2 to AN 708; and determining SSC mode of a session.
  • SM refers to management of a PDU session
  • a PDU session or ⁇ ’session refers to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 702 and the DN 736.
  • the UPF 748 acts as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data netw ork 736, and a branching point to support multihomed PDU session.
  • the UPF 748 also performs packet routing and forwarding, packet inspection, enforces user plane part of policy rules, lawfully intercept packets (UP collection), performs traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and performs downlink packet buffering and downlink data notification triggering.
  • UPF 748 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 750 selects a set of network slice instances serving the UE 702.
  • the NSSF 750 also determines allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 750 also determines an AMF set to be used to serve the UE 702, or a list of candidate AMFs 744 based on a suitable configuration and possibly by querying the NRF 754.
  • the selection of a set of network slice instances for the UE 702 may be triggered by the AMF 744 with which the UE 702 is registered by interacting with the NSSF 750; this may lead to a change of AMF 744.
  • the NSSF 750 interacts with the AMF 744 via an N22 reference point; and may communicate w ith another NSSF in a visited network via an N31 reference point (not shown).
  • the NEF 752 securely exposes services and capabilities provided by 3GPP NFs for third party, internal exposure/re-exposure, AFs 760, edge computing or fog computing systems (e.g., edge compute node, etc.
  • the NEF 752 may authenticate, authorize, or throttle the AFs.
  • NEF 752 may also translate information exchanged with the AF 760 and information exchanged with internal network functions. For example, the NEF 752 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 752 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 752 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 752 to other NFs and AFs, or used for other purposes such as analytics.
  • the NRF 754 supports service discovery functions, receives NF discovery requests from NF instances, and provides information of the discovered NF instances to the requesting NF instances. NRF 754 also maintains information of available NF instances and their supported services. The NRF 754 also supports service discovery functions, wherein the NRF 754 receives NF Discovery Request from NF instance or an SCP (not shown), and provides information of the discovered NF instances to the NF instance or SCP.
  • the PCF 756 provides policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 756 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 758.
  • the PCF 756 exhibit an Npcf service-based interface.
  • the UDM 758 handles subscription-related information to support the network entities’ handling of communication sessions, and stores subscription data of UE 702. For example, subscription data may be communicated via an N8 reference point between the UDM 758 and the AMF 744.
  • the UDM 758 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 758 and the PCF 756. and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 702) for the NEF 752.
  • the Nudr sendeebased interface may be exhibited by the UDR 221 to allow the UDM 758, PCF 756, and NEF 752 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.
  • the UDM 758 may exhibit the Nudm service-based interface.
  • AF 760 provides application influence on traffic routing, provide access to NEF 752, and interact with the policy framework for policy control.
  • the AF 760 may influence UPF 748 (re)selection and traffic routing. Based on operator deployment, when AF 760 is considered to be a trusted entity, the network operator may permit AF 760 to interact directly with relevant NFs. Additionally, the AF 760 may be used for edge computing implementations,
  • the 5GC 740 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 702 is attached to the netw ork. This may reduce latency and load on the network.
  • the 5GC 740 may select a UPF 748 close to the UE 702 and execute traffic steering from the UPF 748 to DN 736 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 760, which allows the AF 760 to influence UPF (re)selection and traffic routing.
  • the data network (DN) 736 may represent various netw ork operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application (app)Zcontent server 738.
  • the DN 736 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the app server 738 can be coupled to an IMS via an S-CSCF or the I-CSCF.
  • the DN 736 may represent one or more local area DNs (LADNs), which are DNs 736 (or DN names (DNNs)) that is/are accessible by a UE 702 in one or more specific areas. Outside of these specific areas, the UE 702 is not able to access the LADN/DN 736.
  • LADNs local area DNs
  • DNNs DN names
  • the DN 736 may be an Edge DN 736, which is a (local) Data Network that supports the architecture for enabling edge applications.
  • the app server 738 may represent the physical hardware systems/devices providing app server functionality and/or the application software resident in the cloud or at an edge compute node that performs server function(s).
  • the app/content server 738 provides an edge hosting environment that provides support required for Edge Application Server’s execution.
  • the 5GS can use one or more edge compute nodes to provide an interface and offload processing of wireless communication traffic.
  • the edge compute nodes may be included in, or co-located with one or more RAN710, 714.
  • the edge compute nodes can provide a connection between the RAN 714 and UPF 748 in the 5GC 740.
  • the edge compute nodes can use one or more NFV instances instantiated on virtualization infrastructure within the edge compute nodes to process wireless connections to and from the RAN 714 and UPF 748.
  • the interfaces of the 5GC 740 include reference points and service-based itnterfaces.
  • the reference points include: N1 (between the UE 702 and the AMF 744), N2 (betw een RAN 714 and AMF 744), N3 (between RAN 714 and UPF 748), N4 (between the SMF 746 and UPF 748), N5 (between PCF 756 and AF 760), N6 (between UPF 748 and DN 736), N7 (between SMF 746 and PCF 756), N8 (between UDM 758 and AMF 744), N9 (between two UPFs 748), N10 (between the UDM 758 and the SMF 746), Ni l (between the AMF 744 and the SMF 746), N12 (between AUSF 742 and AMF 744), N13 (between AUSF 742 and UDM 758), N14 (between two AMFs 744; not shown), N15 (between PCF 756 and AMF 744 in case of
  • the service-based representation of FIG. 7 represents NFs within the control plane that enable other authorized NFs to access their services.
  • the service-based interfaces include: Namf (SBI exhibited by AMF 744), Nsmf (SBI exhibited by SMF 746), Nnef (SBI exhibited by NEF 752), Npcf (SBI exhibited by PCF 756), Nudm (SBI exhibited by the UDM 758), Naf (SBI exhibited by AF 760), Nnrf (SBI exhibited by NRF 754), Nnssf (SBI exhibited by NSSF 750), Nausf (SBI exhibited by AUSF 742).
  • the NEF 752 can provide an interface to edge compute nodes 736x, which can be used to process wireless connections with the RAN 714.
  • the system 700 may include an SMSF, which is responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 702 to/from other entities, such as an SMS-GMSC/IWMSC/SMS- router.
  • the SMS may also interact with AMF 744 and UDM 758 for a notification procedure that the UE 702 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 758 when UE 702 is available for SMS).
  • AMF 744 and UDM 758 for a notification procedure that the UE 702 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 758 when UE 702 is available for SMS).
  • the 5GS may also include an SCP (or individual instances of the SCP) that supports indirect communication (see e.g., 3GPP TS 23.501 section 7.1.1); delegated discovery (see e.g., 3GPP TS 23.501 section 7.1.1); message forwarding and routing to destination NF/NF service(s), communication security (e.g., authorization of the NF Service Consumer to access the NF Service Producer API) (see e.g., 3GPP TS 33.501), load balancing, monitoring, overload control, etc.; and discovery and selection functionality for UDM(s), AUSF(s), UDR(s), PCF(s) with access to subscription data stored in the UDR based on UE’s SUPI, SUCI or GPSI (see e.g., 3GPP TS 23.501 section 6.3).
  • SCP or individual instances of the SCP
  • indirect communication see e.g., 3GPP TS 23.501 section 7.1.1
  • delegated discovery see e.g.,
  • Load balancing, monitoring, overload control functionality provided by the SCP may be implementation specific.
  • the SCP may be deployed in a distributed manner. More than one SCP can be present in the communication path betw een various NF Services.
  • the SCP although not an NF instance, can also be deployed distributed, redundant, and scalable.
  • FIG. 8 schematically illustrates a wireless network 800 in accordance with various embodiments.
  • the wireless network 800 may include a UE 802 in wireless communication with an AN 804.
  • the UE 802 and AN 804 may be similar to, and substantially interchangeable with, like-named components described with respect to FIG. 7.
  • the UE 802 may be communicatively coupled with the AN 804 via connection 806.
  • the connection 806 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.
  • the UE 802 may include a host platform 808 coupled with a modem platform 810.
  • the host platform 808 may include application processing circuitry 812, which may be coupled with protocol processing circuitry 814 of the modem platform 810.
  • the application processing circuitry 812 may run various applications for the UE 802 that source/sink application data.
  • the application processing circuitry 812 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 814 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 806.
  • the layer operations implemented by the protocol processing circuitry 814 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 810 may further include digital baseband circuitry 816 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 814 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ acknowledgement (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.
  • PHY operations including one or more of HARQ acknowledgement (ACK) functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding
  • the modem platform 810 may further include transmit circuitry' 818, receive circuitry 820, RF circuitry 822, and RF front end (RFFE) 824, which may include or connect to one or more antenna panels 826.
  • the transmit circuitry 818 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive ci rcui try 820 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 822 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 824 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • filters for example, surface/bulk acoustic wave filters
  • switches for example, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • 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.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 814 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE 802 reception may 7 be established by and via the antenna panels 826, RFFE 824, RF circuitry 7 822, receive circuitry 820, digital baseband circuitry 7 816, and protocol processing circuitry 814.
  • the antenna panels 826 may receive a transmission from the AN 804 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 826.
  • a UE 802 transmission may be established by and via the protocol processing circuitry 814, digital baseband circuitry 816, transmit circuitry' 818, RF circuitry 822, RFFE 824, and antenna panels 826.
  • the transmit components of the UE 804 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 826.
  • the AN 804 may include a host platform 828 coupled with a modem platform 830.
  • the host platform 828 may include application processing circuitry 832 coupled with protocol processing circuitry 834 of the modem platform 830.
  • the modem platform may further include digital baseband circuitry 836, transmit circuitry 838, receive circuitry 7 840, RF circuitry 7 842, RFFE circuitry 7 844, and antenna panels 846.
  • the components of the AN 804 may be similar to and substantially interchangeable with like-named components of the UE 802.
  • the components of the AN 808 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.
  • FIG. 9 illustrates components of a computing device 900 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 7 one or more of the methodologies discussed herein.
  • FIG. 9 shows a diagrammatic representation of hardware resources 901 including one or more processors (or processor cores) 910, one or more memory /storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940 or other interface circuitry 7 .
  • a hypervisor 902 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 901.
  • the processors 910 include, for example, processor 912 and processor 914.
  • the processors 910 include circuitry such as, but not limited to one or more processor cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface circuit, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as secure digital/multi-media card (SD/MMC) or similar, interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.
  • LDOs low drop-out voltage regulators
  • interrupt controllers serial interfaces such as SPI, I2C or universal programmable serial interface circuit
  • RTC real time clock
  • timer-counters including interval and watchdog timers
  • general purpose I/O general purpose I/O
  • memory card controllers such as secure digital/multi-media card (SD/MMC) or similar
  • SD/MMC secure digital/multi-media card
  • MIPI mobile industry processor
  • the processors 910 may be, for example, a central processing unit (CPU), reduced instruction set computing (RISC) processors, Acom RISC Machine (ARM) processors, complex instruction set computing (CISC) processors, graphics processing units (GPUs), one or more Digital Signal Processors (DSPs) such as a baseband processor, Application-Specific Integrated Circuits (ASICs), an Field-Programmable Gate Array (FPGA), a radio-frequency integrated circuit (RFIC), one or more microprocessors or controllers, another processor (including those discussed herein), or any suitable combination thereof.
  • the processor circuitry 910 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices (e.g., FPGA, complex programmable logic devices (CPLDs), etc.), or the like.
  • the memory/storage devices 920 may include main memory', disk storage, or any suitable combination thereof.
  • the memory/storage devices 920 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), erasable programmable read-only memory' (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, phase change RAM (PRAM), resistive memory such as magnetoresistive random access memory (MRAM), etc., and may incorporate three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • the memory/storage devices 920 may also comprise persistent storage devices, which may be temporal and/or persistent storage of any type, including, but not limited to, nonvolatile memory, optical, magnetic, and/or solid state mass storage, and so forth.
  • the communication resources 930 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 904 or one or more databases 906 or other network elements via a network 908.
  • the communication resources 930 may include wired communication components (e.g., for coupling via USB, Ethernet, Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), Ethernet over USB, Controller Area Network (CAN), Local Interconnect Network (LIN), DeviceNet, ControlNet, Data Highway+, PROFIBUS, or PROFINET, among many others), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, WiFi® components, and other communication components.
  • wired communication components e.g., for coupling via USB, Ethernet, Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), Ethernet over USB, Controller Area Network (CAN), Local Interconnect Network (LIN), DeviceNet, ControlNet, Data Highway+, PROFIBUS, or PROFINET, among many others
  • Network connectivity may be provided to/from the computing device 900 via the communication resources 930 using a physical connection, which may be electrical (e.g.. a "‘copper interconnect'’) or optical.
  • the physical connection also includes suitable input connectors (e.g., ports, receptacles, sockets, etc.) and output connectors (e.g., plugs, pins, etc ).
  • the communication resources 930 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned netw ork interface protocols.
  • Instructions 950 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 910 to perform any one or more of the methodologies discussed herein.
  • the instructions 950 may reside, completely or partially, within at least one of the processors 910 (e.g., within the processor’s cache memory), the memory/storage devices 920. or any suitable combination thereof.
  • any portion of the instructions 950 may be transferred to the hardware resources 901 from any combination of the peripheral devices 904 or the databases 906. Accordingly, the memory of processors 910, the memory/storage devices 920, the peripheral devices 904, and the databases 906 are examples of computer-readable and machine-readable media.
  • FIG. 10 illustrates a network 1000 in accordance with various embodiments.
  • the network 1000 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems.
  • the network 1000 may operate concurrently with network 700.
  • the network 1000 may share one or more frequency or bandwidth resources with network 700.
  • a UE e.g., UE 1002
  • UE 1002 may be configured to operate in both network 1000 and network 700.
  • Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 700 and 1000.
  • several elements of network 1000 may share one or more characteristics with elements of network 700. For the sake of brevity and clarity, such elements may not be repeated in the description of netw ork 1000.
  • the network 1000 may include a UE 1002, which may include any mobile or non- mobile computing device designed to communicate with a RAN 1008 via an over-the-air connection.
  • the UE 1002 may be similar to, for example, UE 702.
  • the UE 1002 may be, but is not limited to, a smartphone, tablet computer, w earable 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, electron! c/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-ty pe communication device, M2M or D2D device. loT device, etc.
  • the network 1000 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.
  • the UE 1002 may be communicatively coupled with an AP such as AP 706 as described with respect to FIG. 7.
  • the RAN 1008 may include one or more ANss such as AN 708 as described with respect to FIG. 7.
  • the RAN 1008 and/or the AN of the RAN 1008 may be referred to as a base station (BS), a RAN node, or using some other term or name.
  • the UE 1002 and the RAN 1008 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.
  • THz terahertz
  • sub-THz bandwidth may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing.
  • 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.
  • the RAN 1008 may allow for communication between the UE 1002 and a 6G core network (CN) 1010. Specifically, the RAN 1008 may facilitate the transmission and reception of data between the UE 1002 and the 6G CN 1010.
  • the 6G CN 1010 may include various functions such as NSSF 750. NEF 752, NRF 754, PCF 756, UDM 758, AF 760, SMF 746, and AUSF 742.
  • the 6G CN 1010 may additional include UPF 748 and DN 736 as shown in FIG. 10.
  • the RAN 1008 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular netw ork such as a 4G or 5G network.
  • Two such functions may include a Compute Control Function (Comp CF) 1024 and a Compute Service Function (Comp SF) 1036.
  • the Comp CF 1024 and the Comp SF 1036 may be parts or functions of the Computing Service Plane.
  • Comp CF 1024 may be a control plane function that provides functionalities such as management of the Comp SF 1036, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlaying computing infrastructure for computing resource management, etc..
  • Comp SF 1036 may be a user plane function that sen es as the gateway to interface computing service users (such as UE 1002) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 1036 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 1036 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 1024 instance may control one or more Comp SF 1036 instances.
  • Two other such functions may include a Communication Control Function (Comm CF) 1028 and a Communication Service Function (Comm SF) 1038, which may be parts of the Communication Service Plane.
  • the Comm CF 1028 may be the control plane function for managing the Comm SF 1038, communication sessions creation/configuration/releasing, and managing communication session context.
  • the Comm SF 1038 may be a user plane function for data transport.
  • Comm CF 1028 and Comm SF 1038 may be considered as upgrades of SMF 746 and UPF 748, which were described with respect to a 5G system in FIG. 7.
  • the upgrades provided by the Comm CF 1028 and the Comm SF 1038 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 746 and UPF 748 may still be used.
  • Data CF 1022 may be a control plane function and provides functionalities such as Data SF 1032 management, Data service creation/configuration/releasing. Data service context management, etc.
  • Data SF 1032 may be a user plane function and serve as the gateway between data sendee users (such as UE 1002 and the various functions of the 6G CN 1010) and data sen ice endpoints behind the gateway. Specific functionalities may include include: parse data sendee user data and forward to corresponding data service endpoints, generate charging data, report data service status.
  • SOCF 1020 may discover, orchestrate and chain up communication/computing/data services provided by functions in the network.
  • SOCF 1020 may interact with one or more of Comp CF 1024, Comm CF 1028, and Data CF 1022 to identify Comp SF 1036, Comm SF 1038, and Data SF 1032 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 1036.
  • the SOCF 1020 may also responsible for maintaining, updating, and releasing a created service chain.
  • SRF service registration function
  • NRF 754 may act as the registry for network functions.
  • eSCP evolved service communication proxy
  • SCP service infrastructure control function
  • SICF service infrastructure control function
  • the SICF 1026 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.
  • the AMF 1044 may be similar to 744, but with additional functionality. Specifically, the AMF 1044 may include potential functional repartition, such as move the message forwarding functionality from the AMF 1044 to the RAN 1008.
  • SOEF service orchestration exposure function
  • the SOEF may be configured to expose service orchestration and chaining services to external users such as applications.
  • the UE 1002 may include an additional function that is referred to as a computing client service function (comp CSF) 1004.
  • the comp CSF 1004 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 1020, Comp CF 1024, Comp SF 1036, Data CF 1022, and/or Data SF 1032 for service discovery, request/response, compute task workload exchange, etc.
  • the Comp CSF 1004 may also work with network side functions to decide on whether a computing task should be run on the UE 1002, the RAN 1008, and/or an element of the 6G CN 1010.
  • the UE 1002 and/or the Comp CSF 1004 may include a service mesh proxy 1006.
  • the service mesh proxy 1006 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 1006 may include one or more of addressing, security, load balancing, etc.
  • 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.
  • 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • Example 1 may include an apparatus for a user equipment (UE) comprising receive from a next generation radio access network (gNB) an indication of a scaling factor and an indication of enabling frequency domain spectrum shaping with spectrum extension (FDSS- SE) for a physical uplink shared channel (PUSCH) transmission; select a scaling factor as a ratio between a number of physical resource blocks (PRBs) for allocated resource and extended resources or total resource including extended resources; select an allocated resource in a frequency domain for a physical uplink shared channel (PUSCH) from frequency domain resource allocation (FDRA) indicated in a downlink control information (DCI) or provided by radio resource control (RRC) signaling; and transmit the PUSCH in accordance with the scaling factor and the indication of FDSS-SE using the allocated resource and extended resource.
  • gNB next generation radio access network
  • FDSS- SE frequency domain spectrum shaping with spectrum extension
  • Example 2 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to receive configuration of whether FDSS-SE may be enabled or disabled from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling.
  • NR new radio
  • RMSI remaining minimum system information
  • OSI NR other system information
  • RRC Radio Resource Control
  • Example 3 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to not apply FDSS-SE for the PUSCH when a cyclic prefix (CP)-orthogonal frequency-division multiplexing (OFDM) waveform may be indicated or when transform precoding may be disabled.
  • CP cyclic prefix
  • OFDM orthogonal frequency-division multiplexing
  • Example 4 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to determine the allocated resource in the frequency domain from FDRA indicated for Dynamic grant PUSCH (DG-PUSCH) or provided by RRC signaling for Configured grant PUSCH (CG-PUSCH).
  • DG-PUSCH Dynamic grant PUSCH
  • CG-PUSCH Configured grant PUSCH
  • Example 5 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to select the scaling factor either from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling or dynamically indicated in the downlink control information (DCI).
  • NR new radio
  • RMSI remaining minimum system information
  • OSI NR other system information
  • DCI downlink control information
  • Example 6 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to include the extended resource for FDSS-SE operation when determining the allocated resource in frequency domain.
  • Example 7 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to determine a set of numbers of the PRBs as the extended resource based on high layer signaling depending on the number of allocated PRBs of PUSCH and/or indication in the DCI.
  • Example 8 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to associate a single demodulation reference signal (DMRS) sequence with the PUSCH transmission with FDSS-SE scheme with length determined in accordance with the allocated resource and extended resource.
  • DMRS demodulation reference signal
  • Example 9 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to determine the reference point for k for DMRS sequence mapping as subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation including extended resource when transform precoding may be enabled.
  • Example 10 may include a computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: receiving from a next generation radio access network (gNB) an indication of a scaling factor and an indication of enabling frequency domain spectrum shaping with spectrum extension (FDSS-SE) for a physical uplink shared channel (PUSCH) transmission; selecting a scaling factor as a ratio between a number of physical resource blocks (PRBs) for allocated resource and extended resources or total resource including extended resources; selecting an allocated resource in a frequency domain for a physical uplink shared channel (PUSCH) from frequency domain resource allocation (FDRA) indicated in a downlink control information (DO) or provided by radio resource control (RRC) signaling; and transmitting the PUSCH in accordance with the scaling factor and the indication of FDSS-SE using the allocated resource and extended resource.
  • gNB next generation radio access network
  • FDSS-SE frequency domain spectrum shaping with spectrum extension
  • Example 11 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise receiving configuration of whether FDSS-SE may be enabled or disabled from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling.
  • NR new radio
  • RMSI remaining minimum system information
  • OSI NR other system information
  • RRC Radio Resource Control
  • Example 12 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise not apply FDSS-SE for the PUSCH when a cyclic prefix (CP)-orthogonal frequency-division multiplexing (OFDM) waveform may be indicated or when transform precoding may be disabled.
  • CP cyclic prefix
  • OFDM orthogonal frequency-division multiplexing
  • Example 13 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise determining the allocated resource in the frequency domain from FDRA indicated for Dynamic grant PUSCH (DG- PUSCH) or provided by RRC signaling for Configured grant PUSCH (CG-PUSCH).
  • DG- PUSCH Dynamic grant PUSCH
  • CG-PUSCH Configured grant PUSCH
  • Example 14 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise selecting the scaling factor either from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling or dynamically indicated in the downlink control information (DCI).
  • NR new radio
  • RMSI remaining minimum system information
  • OSI NR other system information
  • DCI downlink control information
  • Example 15 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise including the extended resource for FDSS-SE operation when determining the allocated resource in frequency domain.
  • Example 16 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise determining a set of numbers of the PRBs as the extended resource based on high layer signaling depending on the number of allocated PRBs of PUSCH and/or indication in the DCI.
  • Example 17 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise associate a single demodulation reference signal (DMRS) sequence with the PUSCH transmission with FDSS-SE scheme with length determined in accordance with the allocated resource and extended resource.
  • DMRS demodulation reference signal
  • Example 18 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise determining the reference point for k for DMRS sequence mapping as subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation including extended resource when transform precoding may be enabled.
  • Example 19 may include a method comprising: receiving, by one or more processors, from a next generation radio access network (gNB) an indication of a scaling factor and an indication of enabling frequency domain spectrum shaping with spectrum extension (FDSS- SE) for a physical uplink shared channel (PUSCH) transmission; selecting a scaling factor as a ratio between a number of physical resource blocks (PRBs) for allocated resource and extended resources or total resource including extended resources; selecting an allocated resource in a frequency domain for a physical uplink shared channel (PUSCH) from frequency domain resource allocation (FDRA) indicated in a downlink control information (DCI) or provided by radio resource control (RRC) signaling; and transmitting the PUSCH in accordance with the scaling factor and the indication of FDSS-SE using the allocated resource and extended resource.
  • gNB next generation radio access network
  • FDSS- SE frequency domain spectrum shaping with spectrum extension
  • Example 20 may include the method of example 19 and/or some other example herein, further comprising receiving configuration of whether FDSS-SE may be enabled or disabled from higher layers via new' radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling.
  • NR new' radio
  • RMSI remaining minimum system information
  • OSI NR other system information
  • RRC Radio Resource Control
  • Example 21 may include the method of example 19 and/or some other example herein, further comprising not applying FDSS-SE for the PUSCH when a cyclic prefix (CP)- orthogonal frequency-division multiplexing (OFDM) waveform may be indicated or when transform precoding may be disabled.
  • CP cyclic prefix
  • OFDM orthogonal frequency-division multiplexing
  • Example 22 may include the method of example 19 and/or some other example herein, further comprising determining the allocated resource in the frequency domain from FDRA indicated for Dynamic grant PUSCH (DG-PUSCH) or provided by RRC signaling for Configured grant PUSCH (CG-PUSCH).
  • DG-PUSCH Dynamic grant PUSCH
  • CG-PUSCH Configured grant PUSCH
  • Example 23 may include the method of example 19 and/or some other example herein, further comprising selecting the scaling factor either from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling or dynamically indicated in the downlink control information (DCI).
  • NR new radio
  • RMSI remaining minimum system information
  • OSI NR other system information
  • DCI downlink control information
  • Example 24 may include the method of example 19 and/or some other example herein, further comprising including the extended resource for FDSS-SE operation when determining the allocated resource in frequency domain.
  • Example 25 may include the method of example 19 and/or some other example herein, further comprising determining a set of numbers of the PRBs as the extended resource based on high layer signaling depending on the number of allocated PRBs of PUSCH and/or indication in the DCI.
  • Example 26 may include the method of example 19 and/or some other example herein, further comprising associating a single demodulation reference signal (DMRS) sequence with the PUSCH transmission with FDSS-SE scheme with length determined in accordance with the allocated resource and extended resource.
  • DMRS demodulation reference signal
  • Example 27 may include the method of example 19 and/or some other example herein, further comprising determining the reference point for k for DMRS sequence mapping as subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation including extended resource when transform precoding may be enabled.
  • Example 28 may include an apparatus comprising means for: receiving from a next generation radio access network (gNB) an indication of a scaling factor and an indication of enabling frequency domain spectrum shaping with spectrum extension (FDSS-SE) for a physical uplink shared channel (PUSCH) transmission; selecting a scaling factor as a ratio between a number of physical resource blocks (PRBs) for allocated resource and extended resources or total resource including extended resources; selecting an allocated resource in a frequency’ domain for a physical uplink shared channel (PUSCH) from frequency domain resource allocation (FDRA) indicated in a downlink control information (DCI) or provided by radio resource control (RRC) signaling; and transmitting the PUSCH in accordance with the scaling factor and the indication of FDSS-SE using the allocated resource and extended resource.
  • gNB next generation radio access network
  • FDSS-SE frequency domain spectrum shaping with spectrum extension
  • Example 29 may’ include the apparatus of example 28 and/or some other example herein, further comprising receiving configuration of whether FDSS-SE may be enabled or disabled from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling.
  • NR new radio
  • RMSI remaining minimum system information
  • OSI NR other system information
  • RRC Radio Resource Control
  • Example 30 may include the apparatus of example 28 and/or some other example herein, further comprising not applying FDSS-SE for the PUSCH when a cyclic prefix (CP)- orthogonal frequency-division multiplexing (OFDM) waveform may be indicated or when transform precoding may be disabled.
  • CP cyclic prefix
  • OFDM orthogonal frequency-division multiplexing
  • Example 31 may include the apparatus of example 28 and/or some other example herein, further comprising determining the allocated resource in the frequency domain from FDRA indicated for Dynamic grant PUSCH (DG-PUSCH) or provided by RRC signaling for Configured grant PUSCH (CG-PUSCH).
  • DG-PUSCH Dynamic grant PUSCH
  • CG-PUSCH Configured grant PUSCH
  • Example 32 may include the apparatus of example 28 and/or some other example herein, further comprising selecting the scaling factor either from higher layers via new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or RRC signaling or dynamically indicated in the downlink control information (DCI).
  • NR new radio
  • RMSI remaining minimum system information
  • OSI NR other system information
  • DCI downlink control information
  • Example 33 may include the apparatus of example 28 and/or some other example herein, further comprising including the extended resource for FDSS-SE operation when determining the allocated resource in frequency domain.
  • Example 34 may include the apparatus of example 28 and/or some other example herein, further comprising determining a set of numbers of the PRBs as the extended resource based on high layer signaling depending on the number of allocated PRBs of PUSCH and/or indication in the DCI.
  • Example 35 may include the apparatus of example 28 and/or some other example herein, further comprising associating a single demodulation reference signal (DMRS) sequence with the PUSCH transmission with FDSS-SE scheme with length determined in accordance with the allocated resource and extended resource.
  • DMRS demodulation reference signal
  • Example 36 may include the apparatus of example 28 and/or some other example herein, further comprising determining the reference point for k for DMRS sequence mapping as subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation including extended resource when transform precoding may be enabled.
  • Example 37 may include an apparatus comprising means for performing any of the methods of examples 1-36.
  • Example 38 may include a network node comprising a communication interface and processing circuitry connected thereto and configured to perform the methods of examples 1- 36.
  • Example 39 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process described herein.
  • Example 40 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-36, or any other method or process described herein.
  • Example 41 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-36, or any other method or process described herein.
  • Example 42 may include a method, technique, or process as described in or related to any of examples 1-36, or portions or parts thereof.
  • Example 43 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-36, or portions thereof.
  • Example 44 may include a signal as described in or related to any of examples 1-36, or portions or parts thereof.
  • Example 45 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-36, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 46 may include a signal encoded with data as described in or related to any of examples 1-36. or portions or parts thereof, or otherwise described in the present disclosure.
  • Example 47 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-36, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 48 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-36, or portions thereof.
  • Example 49 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-36, or portions thereof.
  • Example 50 may include a signal in a wireless network as shown and described herein.
  • Example 51 may include a method of communicating in a wireless network as shown and described herein.
  • Example 52 may include a system for providing wireless communication as shown and described herein.
  • Example 53 may include a device for providing wireless communication as show n and described herein.
  • An example implementation is an edge computing system, including respective edge processing devices and nodes to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is a client endpoint node, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an aggregation node, network hub node, gateway node, or core data processing node, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an access point, base station, road-side unit, street-side unit, or on-premise unit, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge provisioning node, service orchestration node, application orchestration node, or multi-tenant management node, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge node operating an edge provisioning service, application or service orchestration service, virtual machine deployment, container deployment, function deployment, and compute management, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subj ect matter described herein.
  • Another example implementation is an edge computing system operable as an edge mesh, as an edge mesh with side car loading, or with mesh-to-mesh communications, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge computing system including aspects of netw ork functions, acceleration functions, acceleration hardw are, storage hardware, or computation hardware resources, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • Another example implementation is an edge computing system adapted for supporting client mobility, vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or vehicle-to-infrastructure (V2I) scenarios, and optionally operating according to ETSI MEC specifications, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • V2V vehicle-to-vehicle
  • V2X vehicle-to-everything
  • V2I vehicle-to-infrastructure
  • Another example implementation is an edge computing system adapted for mobile wireless communications, including configurations according to an 3GPP 4G/LTE or 5G network capabilities, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • Another example implementation is a computing system adapted for network communications, including configurations according to an O-RAN capabilities, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • the phrase “A and/or B” means (A), (B), or (A and B).
  • the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
  • the description may use the phrases “in an embodiment,” or “In some embodiments,” which may each refer to one or more of the same or different embodiments.
  • the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure are synonymous.
  • 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.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • 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 ink, and/or the like.
  • circuitry 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.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • 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 cany' 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.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carry ing 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.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.
  • 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.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or baseband circuitry' may be considered synonymous to, and may be referred to as, “processor circuitry'.”
  • memory and/or “memory circuitry” as used herein refers to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM, and/or SDRAM, core memory', ROM, magnetic disk storage mediums, optical storage mediums, flash memory devices or other machine readable mediums for storing data.
  • computer-readable medium may include, but is not limited to, memory', portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instructions or data.
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • 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.
  • user equipment 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.
  • the term “user equipment” or “UE” may include any type of wireless/ wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • 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.
  • computer system 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.
  • appliance 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.
  • element refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary', wherein an element may be any type of entity including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof.
  • device refers to a physical entity embedded inside, or attached to, another physical entity in its vicinity, with capabilities to convey digital information from or to that physical entity.
  • entity refers to a distinct component of an architecture or device, or information transferred as a payload.
  • controller refers to an element or entity that has the capability to affect a physical entity, such as by changing its state or causing the physical entity to move.
  • cloud computing refers to a paradigm for enabling network access to a scalable and elastic pool of shareable computing resources with self-service provisioning and administration on-demand and without active management by users.
  • Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities offered via cloud computing that are invoked using a defined interface (e.g., an API or the like).
  • computing resource or simply “resource” refers to any physical or virtual component, or usage of such components, of limited availability within a computer system or network.
  • Examples of computing resources include usage/access to, for a period of time, servers, processor(s), storage equipment, memory' devices, memory areas, networks, electrical power, input/output (peripheral) devices, mechanical devices, network connections (e.g., channels/links, ports, network sockets, etc ), operating systems, virtual machines (VMs), software/applications, computer files, 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/systems via a communications network.
  • 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.
  • cloud service provider or CSP indicates an organization which operates typically large-scale “cloud” resources comprised of centralized, regional, and edge data centers (e.g., as used in the context of the public cloud).
  • a CSP may also be referred to as a Cloud Service Operator (CSO).
  • CSO Cloud Service Operator
  • References to “cloud computing” generally refer to computing resources and services offered by a CSP or a CSO, at remote locations with at least some increased latency, distance, or constraints relative to edge computing.
  • data center refers to a purpose-designed structure that is intended to house multiple high-performance compute and data storage nodes such that a large amount of compute, data storage and network resources are present at a single location. This often entails specialized rack and enclosure systems, suitable heating, cooling, ventilation, security, fire suppression, and power delivery systems.
  • the term may also refer to a compute and data storage node in some contexts.
  • a data center may vary in scale between a centralized or cloud data center (e.g., largest), regional data center, and edge data center (e.g., smallest).
  • edge computing refers to the implementation, coordination, and use of computing and resources at locations closer to the “edge” or collection of “edges” of a network. Deploying computing resources at the network’s edge may reduce application and network latency, reduce network backhaul traffic and associated energy consumption, improve service capabilities, improve compliance with security or data privacy requirements (especially as compared to conventional cloud computing), and improve total cost of ownership).
  • edge compute node refers to a real-world, logical, or virtualized implementation of a compute-capable element in the form of a device, gateway, bridge, system or subsystem, component, whether operating in a server, client, endpoint, or peer mode, and whether located at an “edge” of an network or at a connected location further within the network.
  • references to a “node” used herein are generally interchangeable with a “device”, “component”, and “sub-system”; however, references to an “edge computing system” or “edge computing network” generally refer to a distributed architecture, organization, or collection of multiple nodes and devices, and which is organized to accomplish or offer some aspect of services or resources in an edge computing setting.
  • the term “Edge Computing” refers to a concept, as described in [6], that enables operator and 3rd party services to be hosted close to the UE’s access point of attachment, to achieve an efficient service delivery through the reduced end-to- end latency and load on the transport network.
  • the term 'Edge Computing Service Provider’’ refers to a mobile network operator or a 3rd party service provider offering Edge Computing service.
  • the term “Edge Data Network” refers to a local Data Network (DN) that supports the architecture for enabling edge applications.
  • the term “Edge Hosting Environment” refers to an environment providing support required for Edge Application Server’s execution.
  • the term “Application Server” refers to application software resident in the cloud performing the server function.
  • loT Internet of Things
  • loT devices are usually low-power devices without heavy compute or storage capabilities.
  • “Edge loT devices” may be any kind of loT devices deployed at a network’s edge.
  • cluster refers to a set or grouping of entities as part of an edge computing system (or systems), in the form of physical entities (e.g., different computing systems, networks or network groups), logical entities (e.g., applications, functions, security' constructs, containers), and the like.
  • a “cluster” is also referred to as a “group” or a “domain”.
  • the membership of cluster may be modified or affected based on conditions or functions, including from dynamic or property -based membership, from network or system management scenarios, or from various example techniques discussed below which may add, modify, or remove an entity in a cluster.
  • Clusters may also include or be associated with multiple layers, levels, or properties, including variations in security features and results based on such layers, levels, or properties.
  • the term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment.
  • AI/ML application or the like may be an application that contains some AI/ML models and application-level descriptions.
  • 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.
  • an ML algorithm is a computer program that leams from experience with respect to some task and some performance measure
  • 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.
  • 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.
  • machine learning model 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), decision 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-leaming, multi-armed bandit learning, deep RL, etc.), neural networks, and the like.
  • 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).
  • ML training host refers to an entity, such as a network function, that hosts the training of the model.
  • 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).
  • 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.
  • instantiate 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.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • database object' may refer to any representation of information that is in the form of an object, attribute-value pair (AVP). key -value pair (KVP).
  • tuple may include variables, data structures, functions, methods, classes, database records, database fields, database entities, associations between data and/or database entities (also referred to as a “relation”), blocks and links between blocks in block chain implementations, and/or the like.
  • An “information object,” as used herein, refers to a collection of structured data and/or any representation of information, and may include, for example electronic documents (or “documents”), database objects, data structures, files, audio data, video data, raw data, archive files, application packages, and/or any other like representation of information.
  • electronic document or “document,” may refer to a data structure, computer file, or resource used to record data, and includes various file types and/or data formats such as word processing documents, spreadsheets, slide presentations, multimedia items, webpage and/or source code documents, and/or the like.
  • the information objects may include markup and/or source code documents such as HTML, XML, JSON, Apex®, CSS, JSP, MessagePackTM, Apache® ThriftTM, ASN. 1, Google® Protocol Buffers (protobuf), or some other document(s)/format(s) such as those discussed herein.
  • An information object may have both a logical and a physical structure. Physically, an information object comprises one or more units called entities. An entity is a unit of storage that contains content and is identified by a name. An entity may refer to other entities to cause their inclusion in the information object. An information object begins in a document entity, which is also referred to as a root element (or “root”). Logically, an information object comprises one or more declarations, elements, comments, character references, and processing instructions, all of which are indicated in the information object (e.g., using markup).
  • data item refers to an atomic state of a particular object with at least one specific property at a certain point in time.
  • Such an object is usually identified by an object name or object identifier, and properties of such an object are usually defined as database objects (e.g., fields, records, etc.), object instances, or data elements (e.g., mark-up language elements/tags, etc.).
  • database objects e.g., fields, records, etc.
  • object instances e.g., mark-up language elements/tags, etc.
  • data elements e.g., mark-up language elements/tags, etc.
  • data item may refer to data elements and/or content items, although these terms may refer to difference concepts.
  • data element or “element” as used herein refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary.
  • a data element is a logical component of an information object (e.g., electronic document) that may begin with a start tag (e.g., “ ⁇ element>“) and end with amatching end tag (e.g., “ ⁇ /element>“), or only has an empty element tag (e.g., “ ⁇ element />“). Any characters between the start tag and end tag, if any, are the element's content (referred to herein as "‘content items” or the like).
  • the content of an entity may include one or more content items, each of which has an associated datatype representation.
  • a content item may include, for example, attribute values, character values, URIs, qualified names (qnames), parameters, and the like.
  • a qname is a fully qualified name of an element, attribute, or identifier in an information object.
  • a qname associates a URI of a namespace with a local name of an element, attribute, or identifier in that namespace. To make this association, the qname assigns a prefix to the local name that corresponds to its namespace.
  • the qname comprises a URI of the namespace, the prefix, and the local name. Namespaces are used to provide uniquely named elements and attributes in information objects.
  • child elements e.g., “ ⁇ elementl> ⁇ element2>content item ⁇ /element2> ⁇ /elementl>“).
  • An “attribute” may refer to a markup construct including a name-value pair that exists within a start tag or empty element tag. Attributes contain data related to its element and/or control the element’s behavior.
  • resource 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.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/sy stems via a communications network.
  • 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.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • 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.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • radio technology refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer.
  • radio access technology or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network.
  • the term “communication protocol” refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.
  • radio technology refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer.
  • radio access technology or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network.
  • communication protocol (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.
  • wireless communications protocols may be used in various embodiments include a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology’, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology including, for example, 3GPP Fifth Generation (5G) or New Radio (NR), Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), Long Term Evolution (LTE), LTE- Advanced (LTE Advanced), LTE Extra, LTE-A Pro, cdmaOne (2G).
  • GSM Global System for Mobile Communications
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data Rates for GSM Evolution
  • 3GPP Third Generation Partnership Project
  • 3GPP Third Generation Partnership Project
  • 5G Fifth Generation
  • NR Universal Mobile Telecommunications System
  • UMTS Universal Mobile Telecommunications System
  • FOMA Freedom of Multimedia Access
  • LTE Long Term Evolution
  • LTE- Advanced L
  • CDMA 2000 Code Division Multiple Access 2000
  • CDPD Cellular Digital Packet Data
  • Mobitex Circuit Switched Data
  • HSD High-Speed CSD
  • UMTS Universal Mobile Telecommunications System
  • W-CDM Wideband Code Division Multiple Access
  • High Speed Packet Access HSPA
  • HSPA Plus HSPA+
  • Time Division-Code Division Multiple Access TD-CDMA
  • Time Division-Synchronous Code Division Multiple Access TD-SCDMA
  • LTE LAA MuLTEfire
  • UTRA Evolved UTRA
  • E-UTRA Evolution- Data Optimized or Evolution-Data Only
  • AMPS Advanced Mobile Phone System
  • D-AMPS Digital AMPS
  • TCP Mobile Telephone System
  • MTS Mobile Telephone System
  • IMTS Improved Mobile Telephone System
  • AMTS Advanced Mobile Telephone System
  • CDPD DataTAC
  • Integrated Digital Enhanced Network iDEN
  • PDC Personal Digital Cellular
  • PHS Personal Handy-phone System
  • WiDEN Wideband Integrated Digital Enhanced Network
  • UMA Unlicensed Mobile Access
  • WiFi-direct ANT/ANT+, ZigBee, Z-Wave, 3GPP device-to-device (D2D) or Proximity Services (ProSe), Universal Plug and Play (UPnP), Low-Power Wide- Area-Network (LPWAN), Long Range Wide Area Network (LoRA) or LoRaWANTM developed by Semtech and the LoRa Alliance, Sigfox, Wireless Gigabit Alliance (WiGig) standard.
  • WiMAX Worldwide Interoperability for Microwave Access
  • mmWave standards in general e g., wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. Had, IEEE 802.
  • V2X communication technologies including 3GPP C-V2X
  • DSRC Dedicated Short Range Communications
  • ITS Intelligent- Transport-Systems
  • any number of satellite uplink technologies may be used for purposes of the present disclosure including, for example, radios compliant with standards issued by the International Telecommunication Union (ITU), or the European Telecommunications Standards Institute (ETSI), among others.
  • ITU International Telecommunication Union
  • ETSI European Telecommunications Standards Institute
  • the term “access network” refers to any network, using any combination of radio technologies. RATs, and/or communication protocols, used to connect user devices and service providers.
  • an “access network” is an IEEE 802 local area network (LAN) or metropolitan area network (MAN) between terminals and access routers connecting to provider services.
  • the term “access router” refers to router that terminates a medium access control (MAC) service from terminals and forwards user traffic to information servers according to Internet Protocol (IP) addresses.
  • MAC medium access control
  • IP Internet Protocol
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConflguration.
  • SSB refers to a synchronization signal/Physical Broadcast Channel (SS/PBCH) block, which includes a Primary Syncrhonization Signal (PSS), a Secondary Syncrhonization Signal (SSS), and a PBCH.
  • PSS Primary Syncrhonization Signal
  • SSS Secondary Syncrhonization Signal
  • PBCH Physical Broadcast Channel
  • Primary Celf 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.
  • 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.
  • 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 PSCell and zero or more secondary cells for a UE configured with DC.
  • 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.
  • 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.
  • 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.
  • Al policy refers to a ty pe of declarative policies expressed using formal statements that enable the non-RT RIC function in the SMO to guide the near-RT RIC function, and hence the RAN, towards better fulfilment of the RAN intent.
  • Al Enrichment information refers to information utilized by near-RT RIC that is collected or derived at SMO/non-RT RIC either from non-network data sources or from network functions themselves.
  • Al -Policy Based Traffic Steering Process Mode refers to an operational mode in which the Near-RT RIC is configured through Al Policy to use Traffic Steering Actions to ensure a more specific notion of network performance (for example, applying to smaller groups of E2 Nodes and UEs in the RAN) than that which it ensures in the Background Traffic Steering.
  • Background Traffic Steering Processing Mode refers to an operational mode in which the Near-RT RIC is configured through 01 to use Traffic Steering Actions to ensure a general background network performance which applies broadly across E2 Nodes and UEs in the RAN.
  • Baseline RAN Behavior refers to the default RAN behavior as configured at the E2 Nodes by SMO
  • E2 refers to an interface connecting the Near-RT RIC and one or more O- CU-CPs, one or more O-CU-UPs, one or more O-DUs, and one or more O-eNBs.
  • E2 Node refers to a logical node terminating E2 interface.
  • ORAN nodes terminating E2 interface are: for NR access: O-CU-CP, O- CU-UP, O-DU or any combination; and for E-UTRA access: O-eNB.
  • non-RT RIC refers to a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in Near-RT RIC.
  • Near-RT RIC or “O-RAN near-real-time RAN Intelligent Controller” refers to a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained (e.g.. UE basis, Cell basis) data collection and actions over E2 interface.
  • fine-grained e.g. UE basis, Cell basis
  • O-RAN Central Unit refers to a logical node hosting RRC, SDAP and PDCP protocols.
  • O-RAN Central Unit - Control Plane or “O-CU-CP” refers to a logical node hosting the RRC and the control plane part of the PDCP protocol.
  • O-RAN Central Unit - User Plane or “O-CU-UP” refers to a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol
  • O-RAN Distributed Unit refers to a logical node hosting RLC/MAC/EIigh-PHY layers based on a lower layer functional split.
  • O-RAN eNB or “O-eNB” refers to an eNB or ng-eNB that supports E2 interface.
  • O-RAN Radio Unit refers to a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP’s “TRP” or “RRH” but more specific in including the Low-PFIY layer (FFT/iFFT, PRACH extraction).
  • the term “01” refers to an interface between orchestration & management entities (Orchestration/NMS) and O-RAN managed elements, for operation and management, by which FCAPS management, Software management, File management and other similar functions shall be achieved.
  • the term “RAN UE Group” refers to an aggregations of UEs whose grouping is set in the E2 nodes through E2 procedures also based on the scope of Al policies. These groups can then be the target of E2 CONTROL or POLICY messages.
  • Traffic Steering Action refers to the use of a mechanism to alter RAN behavior. Such actions include E2 procedures such as CONTROL and POLICY.
  • Traffic Steering Inner Loop refers to the part of the Traffic Steering processing, triggered by the arrival of periodic TS related KPM (Key Performance Measurement) from E2 Node, which includes UE grouping, setting additional data collection from the RAN, as well as selection and execution of one or more optimization actions to enforce Traffic Steering policies.
  • KPM Key Performance Measurement
  • Traffic Steering Outer Loop refers to the part of the Traffic Steering processing, triggered by the near-RT RIC setting up or updating Traffic Steering aware resource optimization procedure based on information from Al Policy setup or update, Al Enrichment Information (El) and/or outcome of Near-RT RIC evaluation, which includes the initial configuration (preconditions) and injection of related Al policies, Triggering conditions for TS changes.
  • Al Policy setup or update Al Enrichment Information (El) and/or outcome of Near-RT RIC evaluation, which includes the initial configuration (preconditions) and injection of related Al policies, Triggering conditions for TS changes.
  • El Al Enrichment Information
  • Triggering conditions for TS changes Triggering conditions for TS changes.
  • Traffic Steering Processing Mode refers to an operational mode in which either the RAN or the Near-RT RIC is configured to ensure a particular network performance. This performance includes such aspects as cell load and throughput, and can apply differently to different E2 nodes and UEs. Throughout this process. Traffic Steering Actions are used to fulfill the requirements of this configuration.
  • Traffic Steering Target refers to the intended performance result that is desired from the network, which is configured to Near-RT RIC over 01.
  • any of the disclosed embodiments and example implementations can be embodied in the form of various types of hardware, software, firmware, middleware, or combinations thereof, including in the form of control logic, and using such hardware or software in a modular or integrated manner.
  • any of the software components or functions described herein can be implemented as software, program code, script, instructions, etc., operable to be executed by processor circuitry. These components, functions, programs, etc., can be developed using any suitable computer language such as, for example. Python, PyTorch, NurnPy, Ruby, Ruby on Rails, Scala, Smalltalk, JavaTM, C++, C#, “C”, Kotlin, Swift, Rust, Go (or “Golang”), EMCAScript, JavaScript, TypeScript.
  • Jscript ActionScript, Server- Side JavaScript (SSJS), PHP. Pearl, Lua, Torch/Lua with Just-In Time compiler (LuaJIT), Accelerated Mobile Pages Script (AMPscript), VBScript, JavaServer Pages (JSP), Active Server Pages (ASP), Node.js, ASP.NET, JAMscript, Hypertext Markup Language (HTML), extensible HTML (XHTML). Extensible Markup Language (XML).
  • XML User Interface Language (XUL), Scalable Vector Graphics (SVG), RESTful API Modeling Language (RAML), wiki markup or Wikitext, Wireless Markup Language (WML), Java Script Object Notion (JSON), Apache® MessagePackTM, Cascading Sty lesheets (CSS), extensible sty lesheet language (XSL), Mustache template language.
  • Handlebars template language Guide Template Language (GTL), Apache® Thrift, Abstract Syntax Notation One (ASN. l), Google® Protocol Buffers (protobuf).
  • the software code can be stored as a computer- or processorexecutable instructions or commands on a physical non-transi tory computer-readable medium.
  • suitable media include RAM, ROM, magnetic media such as a hard-drive or a floppy disk, or an optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like, or any combination of such storage or transmission devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Discrete Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes, des procédés et des dispositifs ayant trait à une allocation de ressources améliorée. Un dispositif peut recevoir, d'un réseau d'accès radio de nouvelle génération (gNB), une indication d'un facteur d'échelle et une indication d'activer une mise en forme du spectre dans le domaine fréquentiel avec extension du spectre (FDSS-SE) pour une émission de canal partagé de liaison montante physique (PUSCH). Le dispositif peut sélectionner un facteur d'échelle comme rapport entre un nombre de blocs de ressources physiques (PRB) pour une ressource allouée et une ressource étendue ou une ressource totale y compris une ressource étendue. Le dispositif peut sélectionner une ressource allouée dans le domaine fréquentiel pour un canal partagé de liaison montante physique (PUSCH) à partir d'une allocation de ressources du domaine fréquentiel (FDRA) indiquée dans des informations de commande de liaison descendante (DCI) ou fournie par une signalisation de commande de ressources radio (RRC). Le dispositif peut émettre le PUSCH conformément au facteur d'échelle et à l'indication de FDSS-SE en utilisant la ressource allouée et la ressource étendue.
PCT/US2023/078312 2022-11-04 2023-11-01 Allocation de ressources pour mise en forme du spectre dans le domaine fréquentiel avec extension du spectre WO2024097726A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263422568P 2022-11-04 2022-11-04
US63/422,568 2022-11-04

Publications (1)

Publication Number Publication Date
WO2024097726A1 true WO2024097726A1 (fr) 2024-05-10

Family

ID=90931642

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/078312 WO2024097726A1 (fr) 2022-11-04 2023-11-01 Allocation de ressources pour mise en forme du spectre dans le domaine fréquentiel avec extension du spectre

Country Status (1)

Country Link
WO (1) WO2024097726A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022152368A1 (fr) * 2021-01-13 2022-07-21 Nokia Technologies Oy Mise en forme de spectre pour communications sans fil
WO2022164999A1 (fr) * 2021-01-28 2022-08-04 Ofinno, Llc Réinterprétation sélective de champs de dci

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022152368A1 (fr) * 2021-01-13 2022-07-21 Nokia Technologies Oy Mise en forme de spectre pour communications sans fil
WO2022164999A1 (fr) * 2021-01-28 2022-08-04 Ofinno, Llc Réinterprétation sélective de champs de dci

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Enhancements to reduce MPR/PAR", 3GPP DRAFT; R4-2215515, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG4, no. E-meeting; 20221010 - 20221019, 30 September 2022 (2022-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052266953 *
VIVO: "Discussion on power domain enhancements to reduce MPR", 3GPP DRAFT; R4-2216121, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG4, no. Electronic meeting; 20221010 - 20221019, 30 September 2022 (2022-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052267514 *
ZTE CORPORATION: "Discussion on power domain enhancements to reduce MPR/PAR", 3GPP DRAFT; R4-2215891, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG4, no. Electronic Meeting; 20221010 - 20221019, 30 September 2022 (2022-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052267320 *

Similar Documents

Publication Publication Date Title
WO2022087474A1 (fr) Hiérarchisation d'équipements intra-utilisateur pour gérer un chevauchement de canaux de commande montants et de données de liaison montante
EP4233419A1 (fr) Attribution de ressources pour un service de diffusion/multidiffusion en nouvelle radio
WO2022221260A1 (fr) Support de service de gestion de cycle de vie o-cloud
WO2022031553A1 (fr) Plan de données pour mégadonnées et données en tant que service dans des réseaux cellulaires de nouvelle génération
WO2022221495A1 (fr) Support d'apprentissage automatique pour services de gestion et services d'analyse de données de gestion
WO2022087489A1 (fr) Indication de faisceau basée sur des informations de commande de liaison descendante (dci) pour une nouvelle radio (nr)
WO2022125296A1 (fr) Mécanismes pour permettre des services informatiques en réseau
WO2024097726A1 (fr) Allocation de ressources pour mise en forme du spectre dans le domaine fréquentiel avec extension du spectre
US20240155393A1 (en) Measurement reporting efficiency enhancement
WO2024092132A1 (fr) Chargement d'entité d'intelligence artificielle et d'apprentissage automatique dans des réseaux cellulaires
US20240196178A1 (en) Data functions and procedures in the non-real time radio access network intelligent controller
WO2024031028A1 (fr) Activation et désactivation d'une planification semi-persistante à l'aide de techniques multicellulaires
WO2023069750A1 (fr) Bons critères de qualité cellulaire
WO2024015747A1 (fr) Sélection de fonction de gestion de session dans des réseaux cellulaires prenant en charge une strate de non-accès distribuée entre un dispositif et des fonctions de réseau
WO2023049345A1 (fr) Optimisation d'équilibrage de charge (lbo) pour systèmes 5g
WO2024081642A1 (fr) Services de traitement en pipeline dans des réseaux cellulaires de prochaine génération
WO2024026211A1 (fr) Régulation de puissance d'émission et de congestion pour positionnement en liaison latérale
WO2022232038A1 (fr) Mesures de performances pour un référentiel de données unifié (udr)
WO2024020519A1 (fr) Systèmes et procédés de partage de services d'une fonction de stockage de données non structurées
WO2024039950A2 (fr) Protocole d'application contrainte pour des services de calcul dans des réseaux cellulaires
WO2024011244A1 (fr) Commande de puissance et chronologie pour ordonnancement multi-cellules pour des opérations de nouvelle radio
WO2024097783A1 (fr) Autorisation à des groupes d'apprentissage fédéré d'accéder à des fonctions d'analyse de données de réseau dans un noyau 5g
WO2024026515A1 (fr) Test d'entité d'intelligence artificielle et d'apprentissage machine
WO2023122037A1 (fr) Mesures et données de localisation prenant en charge une analyse de données de gestion (mda) pour analyse de problème de couverture
WO2022240850A1 (fr) Restriction de domaine temporel pour une configuration de signal de référence d'informations d'état de canal

Legal Events

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

Ref document number: 23886912

Country of ref document: EP

Kind code of ref document: A1