WO2018089879A1 - Configuration de mesurage de gestion de ressources radio - Google Patents

Configuration de mesurage de gestion de ressources radio Download PDF

Info

Publication number
WO2018089879A1
WO2018089879A1 PCT/US2017/061263 US2017061263W WO2018089879A1 WO 2018089879 A1 WO2018089879 A1 WO 2018089879A1 US 2017061263 W US2017061263 W US 2017061263W WO 2018089879 A1 WO2018089879 A1 WO 2018089879A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
signal
reference signal
transmission
network
Prior art date
Application number
PCT/US2017/061263
Other languages
English (en)
Inventor
Candy YIU
Daewon Lee
Yang Tang
Seunghee Han
Rui Huang
Youn Hyoung Heo
Hwan-Joon Kwon
Jie Cui
Kyeongin Jeong
Alexei Davydov
Original Assignee
Intel IP 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 IP Corporation filed Critical Intel IP Corporation
Priority to CN201780062149.4A priority Critical patent/CN109804592B/zh
Publication of WO2018089879A1 publication Critical patent/WO2018089879A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/03Reselecting a link using a direct mode connection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0014Three-dimensional division
    • H04L5/0023Time-frequency-space
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0617Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal for beam forming
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048Allocation of pilot signals, i.e. of signals known to the receiver
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • H04L5/006Quality of the received signal, e.g. BER, SNR, water filling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078Timing of allocation
    • H04L5/0082Timing of allocation at predetermined intervals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signaling for the administration of the divided path
    • H04L5/0094Indication of how sub-channels of the path are allocated
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0079Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/03Reselecting a link using a direct mode connection
    • H04W36/037Reselecting a link using a direct mode connection by reducing handover delay, e.g. latency
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/30Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/302Reselection being triggered by specific parameters by measured or perceived connection quality data due to low signal strength

Definitions

  • the present disclosure relates to the field of wireless networks. More particularly, the present disclosure relates to configuration of radio resource management measurement in wireless networks that implement beamforming.
  • Figure 1 illustrates a portion of an example network arrangement, according to various embodiments.
  • Figure 2 illustrates a representation of an example signal transmission arrangement representation, according to various embodiments.
  • Figure 3 illustrates an example procedure to be performed by a network, according to various embodiments.
  • Figure 4 illustrates a first portion of an example procedure to be performed by user equipment, according to various embodiments.
  • Figure 5 illustrates a second portion of the example procedure to be performed by the user equipment of Figure 4, according to various embodiments.
  • Figure 6 illustrates an example representation of a configuration signal, according to various embodiments.
  • Figure 7 illustrates another example representation of a configuration signal, according to various embodiments.
  • Figure 8 illustrates an example architecture of a system of a network, according to various embodiments.
  • Figure 9 illustrates another example architecture of a system of a network, according to various embodiments.
  • Figure 10 illustrates example components of an electronic device, according to various embodiments.
  • Figure 11 illustrates example interfaces of baseband circuitry, according to various embodiments.
  • Figure 12 illustrates an example control plane protocol stack, according to various embodiments.
  • Figure 13 illustrates an example user plane protocol stack, according to various embodiments.
  • Figure 14 illustrates a block diagram of example components, according to various embodiments.
  • Figure 15 illustrates an example computer-readable non-transitory storage medium, according to various embodiments.
  • an apparatus of a transmission and reception point may include processing circuitry to determine a resource for transmission of a beamformed reference signal of a network that implements beamforming and generate a signal that indicates the resource.
  • the apparatus may further include encoding circuitry, coupled with the processing circuitry, to encode the signal for transmission to a user equipment (UE) that is to utilize the beamformed reference signal to perform a radio resource management measurement.
  • UE user equipment
  • phrase “A and/or B” means (A), (B), or (A and B).
  • phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
  • circuitry may refer to, be part of, or include an
  • ASIC Application Specific Integrated Circuit
  • an electronic circuit a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
  • processor shared, dedicated, or group
  • memory shared, dedicated, or group
  • synchronization signals such as primary synchronization signal and/or secondary synchronization signal
  • xSS synchronization signals
  • the term "cell” may refer to a new radio (NR) cell.
  • the NR cell may be tied to a same identifier carried by NR-synchronization signal (SS).
  • SS NR-synchronization signal
  • the user equipment which may be NR UE described throughout this disclosure, may operate in an IDLE mode refers to a UE state similar to long term evolution (LTE) IDLE state.
  • LTE long term evolution
  • the definition of the IDLE mode may be defined by radio access network group 2 (RAN2).
  • RAN2 radio access network group 2
  • the networks described herein may support cell-level mobility based on downlink (DL) cell-level measurement (e.g. reference signal received power (RSRP) for each cell) in IDLE mode UE.
  • DL downlink
  • RSRP reference signal received power
  • DL signals may be used for IDLE mode radio resource management (RRM) measurement: synchronization signal (e.g., NR-primary synchronization signal (PSS), NR-secondary synchronization signal (SSS)); reference signal (RS) for IDLE mode radio resource management (RRM) measurement: synchronization signal (e.g., NR-primary synchronization signal (PSS), NR-secondary synchronization signal (SSS)); reference signal (RS) for IDLE mode radio resource management (RRM) measurement: synchronization signal (e.g., NR-primary synchronization signal (PSS), NR-secondary synchronization signal (SSS)); reference signal (RS) for IDLE mode radio resource management (RRM) measurement: synchronization signal (e.g., NR-primary synchronization signal (PSS), NR-secondary synchronization signal (SSS)); reference signal (RS) for IDLE mode radio resource management (RRM) measurement: synchronization signal (e.g., NR-primary
  • RS for mobility which may have cell identifier associated with this RS and/or this RS may be for multi-beam and/or single-beam); and/or any combinations of the previous. Other signals may not be precluded.
  • Quasi-Co-Location may be defined for DL signal for IDLE mode RRM measurement. Further, NR cell may be defined only for "IDLE mode" or for both IDLE and CONNECTED mode.
  • UEs described herein may operate in a UE state of CONNECTED mode, which may be similar to LTE CONNECTED state.
  • the definition of LTE CONNECTED mode may be up to RAN2.
  • Layer 3 (L3) mobility may be based on DL measurement in CONNECTED mode
  • At least non-UE-specific DL signals can be used for CONNECTED mode RRM measurement.
  • UE-specific DL signals may be utilized for this.
  • the following DL signals may be utilized for CONNECTED mode RRM measurement: cell related RS which is carrying Cell-identifier (ID) (e.g. NR-PSS, NR- SSS); RS for mobility (which may be associated with beam-ID and/or Cell-ID); RS for demodulating broadcast channel; a combination of cell related RS which is carrying Cell- ID and RS for mobility. Other signals may not be precluded from use.
  • ID Cell-identifier
  • RS for mobility which may be associated with beam-ID and/or Cell-ID
  • RS for demodulating broadcast channel a combination of cell related RS which is carrying Cell- ID and RS for mobility.
  • Other signals may not be precluded from use.
  • At least one of cell-level and beam-level measurement quantities may be supported for RRM reporting.
  • RRM measurement quantities may be defined, e.g., RSRP, reference signal received quality (RSRQ).
  • the following options may be utilized for RRM measurement quantities to be reported for L3 mobility: derived per cell (e.g., if multi- beam, as a function of multi-beam measurements); derived per beam; some combination thereof. Other options may not be precluded.
  • Other UE states may be introduced (if introduced by RAN2).
  • the UEs described herein may operate in an RRC INACTIVE state.
  • a UE and at least 1 next generation NodeB (gNB) may keep the application server (AS) context information in the RRC INACTIVE state.
  • AS application server
  • RRC INACTIVE state number of radio network identifiers may be limited.
  • a UE location can be known at the radio access network (RAN) based area level where that area may be a single cell or more than one cell. Area may be determined by the network.
  • RAN radio access network
  • DL-based mobility in RRC CONNECTED mode may include mobility with RRC involvement, concerning beams and the relation to the NR cell definition.
  • UE may at least measure one or more individual beams and gNB may have mechanisms to consider those beams to perform handover (HO). This may at least trigger inter-gNB handovers and to optimize HO ping-pongs and/or HO failures.
  • UE may report individual and/or combined quality of multiple beams.
  • UE may be able to distinguish between the beams from its serving cell and beams from non-serving cells for RRM measurements in active mobility.
  • UE may be able to determine if a beam is from its serving cell.
  • Serving/non serving cell may be termed "serving/non serving set of beam.”
  • the UE may be informed via dedicated signalling or implicitly detected by the UE based on some broadcast signals.
  • the cell in connected may relate to the cell in idle.
  • a cell quality may be derived based on measurements from individual beams.
  • RRC radio resource control
  • the UE may be able to identify a beam.
  • the beams may be identified as defined by radio access network group 1 (RANI).
  • RANI radio access network group 1
  • UE may perform cell selection and reselection on NR Cells.
  • a cell quality may be derived based on measurements.
  • DL-based handover may be supported, and UL based mobility can be supported or unsupported.
  • DL-based reselection may be supported, and UL-based mobility can be supported or unsupported.
  • Benefits of UL based mobility, compared to DL based mobility, may be implemented.
  • CSI-RS channel state information reference signal
  • the signal On the top of the RS design, the signal may be fixed periodic or dynamically configured by the network.
  • the configuration in the higher layer may become very complex in case of a flexible design in physical layer.
  • Embodiments herein may relate to how the higher layer configuration in different combination.
  • Figure 1 illustrates a portion of an example network arrangement 1000, according to various embodiments.
  • the network arrangement 1000 may provide for connectivity to a network, such as the network associated with Figure 8 and/or Figure 9.
  • the network may be a new radio (NR) network and/or a fifth generation network.
  • the network arrangement 1000 may include one or more cells, transmission and reception points, or some combination thereof, that implement beamforming.
  • the beamforming may be in high frequency.
  • the network arrangement 1000 includes a first cell 1002 and a second cell 1004.
  • the first cell 1002 may be associated with a first NodeB 1006, which may be a NodeB, an evolved NodeB (eNodeB), a next generation NodeB (gNodeB), or some combination thereof.
  • the first NodeB 1006 may provide connectivity of one or more elements within the first cell 1002 to the network.
  • the elements may include one or more transmission and reception points (TRPs), one or more user equipments (UEs), or some combination thereof.
  • TRPs transmission and reception points
  • UEs user equipments
  • the first NodeB 1006 may provide connectivity between the elements and a core network, such as core network XS20 (Fig. 8).
  • a first group of TRPs 1010 may be located within the first cell 1002.
  • the first group of TRPs 1010 may provide for connectivity between the first NodeB 1006 and UEs located within the first cell 1002.
  • the first group of TRPs 1010 may include antennas to relay communications, NodeBs (such as NodeBs, eNodeBs, and/or gNodeBs), or some combination thereof.
  • Each of the TRPs within the first group of TRPs 1010 may transmit signals, via broadcasting and/or beamforming, to UEs.
  • the signals may be generated by the first NodeB 1006 and each of the TRPs may relay the signals to the UEs.
  • the TRPs are illustrated as transmitting the signals via beamforming, as illustrated via the beams 1012.
  • the signals may include, but are not limited to, reference signals, which may include channel state information reference signals (CSI-RS), synchronization signals (such as primary synchronization signals (PSS) and/or secondary synchronization signals (SSS)), beam reference signals (BRS), measurement reference signals (MRS), and/or other reference signals.
  • the signals may be beamformed reference signals.
  • the signals may be transmitted at a periodicity, in response to triggers (such as reception of signals from UEs), or some combination thereof.
  • the signals may be transmitted when the system frame number (SFN) modulo the periodicity is equal to a time indicated by the time information 606 (Fig. 6).
  • SFN system frame number
  • the time indicated by the time information 606 is equal to one, then the signal is transmitted when the SFN modulo the periodicity is equal to one.
  • the time may be indicated by a timing index included in the time information 606.
  • the second cell 1004 may be associated with a second NodeB 1008, which may be a NodeB, an evolved NodeB (eNodeB), a next generation NodeB (gNodeB), or some combination thereof.
  • the second NodeB 1008 may provide connectivity of one or more elements within the second cell 1004 to the network.
  • the elements may include one or more transmission and reception points (TRPs), one or more UEs, or some combination thereof.
  • TRPs transmission and reception points
  • the second NodeB 1008 may provide connectivity between the elements and the core network, such as core network XS20 (Fig. 8).
  • a second group of TRPs 1014 may be located within the second cell 1004.
  • the second group of TRPs 1014 may provide for connectivity between the second NodeB 1008 and UEs located within the second cell 1004.
  • the second group of TRPs 1014 may include antennas to relay communications, NodeBs (such as NodeBs, eNodeBs, and/or gNodeBs), or some combination thereof.
  • Each of the TRPs within the second group of TRPs 1014 may transmit signals, via broadcasting and/or beamforming, to UEs.
  • the signals may be generated by the second NodeB 1008 and each of the TRPs may relay the signals to the UEs.
  • a first TRP within the second group of TRPs 1014 broadcasts the signals (as illustrated by broadcast 1016) and the other TRPs within the second group of TRPs 1014 beamform the signals (as illustrated by beams 1018).
  • the signals may include, but are not limited to, reference signals, which may include CSI-RS, synchronization signals (such as PSS and/or SSS), BRS, MRS, and/or other reference signals.
  • the signals may be beamformed reference signals.
  • the signals may be transmitted at a periodicity, in response to triggers (such as reception of signals from UEs), or some combination thereof.
  • the signals may be transmitted when the SFN modulo the periodicity is equal to a time indicated by the time information 606 (Fig. 6).
  • the time indicated by the time information 606 is equal to one, then the signal is transmitted when the SFN modulo the periodicity is equal to one.
  • the time may be indicated by a timing index included in the time information 606.
  • a first UE 1020 and a second UE 1022 are illustrated within the network arrangement 1000.
  • the first UE 1020 and the second UE 1022 may include one or more of the features of the UE XS01 (Fig. 8) and/or the UE XS02 (Fig. 8).
  • the first NodeB 1006 and/or the second NodeB 1008 may provide connectivity to the network for the first UE 1020 and/or the second UE 1022.
  • the first UE 1020 is illustrated as being moved from a first location 1020a within the first cell 1002 to a second location 1020b within the second cell 1004.
  • connectivity to the network may transition from being provided by one of the TRPs within the first group of TRPs 1010 of the first cell 1002 to being provided by one of the TRPs within the second group of TRPs 1014 of the second cell 1004.
  • the transition may be implemented via a handover (HO) procedure.
  • HO procedure may be any HO procedure known by one having ordinary skill in the art utilized for HO of a UE moving between cells of a network.
  • the network (which may include the core network, the first NodeB 1006, and/or the second NodeB 1008) and/or the first UE 1020 may determine which of the TRPs within the first cell 1002 and/or the second cell 1004 are to provide connectivity to the first UE 1020 based on measurements of the signals transmitted by the TRPs. For example, the first UE 1020 may perform measurements on the signals received from the TRPs and the HO procedure may be initiated by the network based on the results of the measurement. For example, the HO procedure may be initiated based on the
  • the first UE 1020 may generate a measurement report based on the measurements of the signals performed by the first UE 1020 and transmit the measurement report to the network (via the TRPs, the first NodeB 1006, the second NodeB 1008, or some combination thereof).
  • the network may initiate the HO procedure based on the measurement report.
  • the core network or some component thereof, may initiate the HO procedure.
  • the first UE 1020 may perform the measurements on the beamformed reference signals (which may include CSI-RS, synchronization signals (such as the PSS and/or the SSS), the BRS, the MRS, other references signals, or some combination thereof) received from each of the TRPs.
  • the measurements may include radio resource management (RRM) measurements, which may include a received power measurement, a received quality measurement, or some combination thereof.
  • RRM radio resource management
  • the measurement report may include the results of the RRM measurements for each of the signals received by the first UE 1020.
  • the signals may further include an identifier of the TRP that transmitted the signal, the cell with which the signal is associated, the NodeB (such as the first NodeB 1006 and/or the second NodeB 1008) with which the signal is associated, or some combination thereof.
  • the measurement report may include an indication of the TRP, the cell, and/or the NodeB with which each of the measurements in the measurement report are associated.
  • a first TRP 1024 within the first cell 1002, may be providing connectivity to the first UE 1020 when the first UE 1020 is located at the first location 1020a.
  • the network and/or the first UE 1020 may determine that a second TRP 1026, located within the second cell 1004, can provide better connectivity to the first UE 1020 than the first TRP 1024 based on the measurements performed by the first UE 1020.
  • the network and/or the first UE 1020 may initiate the HO procedure based on the determination that the second TRP 1026 can provide better connectivity than the first TRP 1024.
  • the core network of the network may initiate the HO procedure.
  • the second TRP 1026 may provide connectivity to the first UE 1020.
  • the second UE 1022 is illustrated as being moved from a first location 1022a within the second cell 1004 to a second location 1022b within the second cell 1004.
  • connectivity to the network may transition from being provided by one of the TRPs within the second group of TRPs 1014 of the second cell 1004 to being provided by another of the TRPs within the second group of TRPs 1014 of the second cell 1004.
  • the transition may be implemented via a HO procedure. It is to be understood that the HO procedure may be any HO procedure known by one having ordinary skill in the art utilized for HO of a UE moving between TRPs of a cell within a network.
  • the management of connectivity as a UE transitions between TRPs within a cell may be referred to as beam management.
  • the network (which may include the core network, the first NodeB 1006, and/or the second NodeB 1008) and/or the second UE 1022 may determine which of the TRPs within the first cell 1002 and/or the second cell 1004 are to provide connectivity to the second UE 1022 based on measurements of the signals transmitted by the TRPs.
  • the second UE 1022 may perform measurements on the signals received from the TRPs and the HO procedure may be initiated based on the results of the measurement.
  • the HO procedure may be initiated based on the measurements performed by the second UE 1022 indicating that a TRP other than a current TRP providing connectivity to the second UE 1022 would provide better connectivity to the second UE 1022.
  • the second UE 1022 may generate a measurement report based on the measurements of the signals performed by the second UE 1022 and transmit the measurement report to the network (via the TRPs, the first NodeB 1006, the second NodeB 1008, or some combination thereof).
  • the network may initiate the HO procedure based on the measurement report.
  • the core network, or some component thereof may initiate the HO procedure.
  • the second UE 1022 may perform the measurements on the beamformed reference signals (which may include CSI-RS, synchronization signals (such as the PSS and/or the SSS), the BRS, the MRS, other reference signals, or some combination thereof) received from each of the TRPs.
  • the measurements may include RRM measurements, which may include a received power measurement, a received quality measurement, or some combination thereof.
  • the measurement report may include the results of the RRM measurements for each of the signals received by the second UE 1022.
  • the signals may further include an identifier of the TRP that transmitted the signal, the cell with which the signal is associated, the NodeB (such as the first NodeB 1006 and/or the second NodeB 1008) with which the signal is associated, or some combination thereof.
  • the measurement report may include an indication of the TRP, the cell, and/or the NodeB with which each of the measurements in the measurement report are associated.
  • a third TRP 1028 within the second cell 1004, may be providing connectivity to the second UE 1022 when the second UE 1022 is located at the first location 1022a.
  • the network and/or the second UE 1022 may determine that the second TRP 1026, located within the second cell 1004, can provide better connectivity to the second UE 1022 than the third TRP 1028 based on the measurements performed by the second UE 1022.
  • the network and/or the second UE 1022 may initiate the HO procedure based on the determination that the second TRP 1026 can provide better connectivity than the second TRP 1026.
  • the core network of the network may initiate the HO procedure.
  • the second TRP 1026 may provide connectivity to the second UE 1022.
  • Figure 2 illustrates a representation of an example signal transmission arrangement representation 200, according to various embodiments.
  • the representation 200 may represent resources for transmissions of signals via beams (such as the beams 1012 (Fig. 1) and/or the beams 1018 (Fig. 1)) and/or broadcast (such as the broadcast 1016 (Fig. 1)).
  • each of the squares in the representation 200 may represent a resource for transmission of a signal.
  • Each resource may correspond to a frequency at which a signal transmitted on the resource would be transmitted and a time that the signal would be transmitted.
  • description of the representation 200 may refer only to signals transmitted via beams (referred to as "beams") and, particularly, to a first beam and a second beam, which may be beamformed reference signals.
  • the description of the representation 200 refers to resources on which beams are not transmitted. However, this is to be understood to indicate resources that are not utilized for the beamformed reference signals described herein, but may be utilized for transmission of other signals than the beamformed reference signals.
  • the white squares may indicate resources on which beams are not transmitted and the gray squares may indicate resources on which beams are transmitted. Each gray square may represent transmission of a single beam on the resource.
  • the representation 200 may be a representation of a signal transmission arrangement for a single cell (such as the first cell 1002 (Fig. 1) and/or the second cell 1004 (Fig. 1)) within the network.
  • multiple beams may be transmitted at the same time with each beam being transmitted at a different frequency.
  • a first beam may be transmitted on a first resource 202 corresponding to a first frequency and a first time
  • a second beam may be transmitted on a second resource 204 corresponding to a second frequency, different from the first frequency, and the first time.
  • the first beam may be transmitted by a TRP within a cell and the second beam may be transmitted by a TRP within the same cell, wherein the TRP that transmits the second beam may be the same TRP as or a different TRP from the TRP that transmits the first beam.
  • Other beams within the cell may be transmitted at the same time and at different frequencies from the first beam and the second beam.
  • the beams may be transmitted periodically.
  • the first beam may be transmitted on the first resource 202 corresponding to the first frequency and the first time, and may be transmitted again on a third resource 206 corresponding to the first frequency and a second time, the second time being different than the first time.
  • the first beam may be transmitted again on a fourth resource 208 corresponding to the first frequency and a third time, the third time being different from both the first time and the second time.
  • the period between the first time, the second time, and the third time may be indicated by periodicity 210.
  • the beams may be transmitted when the SFN modulo the periodicity is equal to a time indicated by the time information 606 (Fig. 6). For further example, if the time indicated by the time information 606 is equal to one, then the signal is transmitted when the SFN modulo the periodicity is equal to one. In some
  • the time may be indicated by a timing index included in the time information 606.
  • the beams may be referred to as a synchronized cell arrangement.
  • the beams may be transmitted at different times, which may be referred to as an unsynchronized cell arrangement.
  • the first beam may be transmitted at a different time from the second beam in the unsynchronized cell arrangement.
  • different beams may be transmitted at the same frequency at different times.
  • the first beam may be transmitted on a resource corresponding to a frequency and a time
  • the second beam may be transmitted on another resource corresponding to the same frequency and a different time.
  • the beams may transmitted dynamically (such as in response to a trigger) rather than periodically.
  • a NodeB such as an NodeB, an eNB, and/or a gNB
  • the NodeB may cause one or more of the TRPs to transmit beams in response to receiving a signal from one or more of the UEs.
  • the NodeB may cause the TRPs to transmit the beams in response to receiving a request from a UE for transmission of the beams to be measured.
  • the UE may transmit the request in response to the UE detecting that a previously received configuration for performing measurements of the signals is no longer valid.
  • the UE may transmit the request via a physical random access channel (PRACH) transmission, which may be differentiated from other PRACH transmissions occurring during initial access or a cell re-selection procedure.
  • PRACH physical random access channel
  • UEs may measure signals transmitted by TRPs (such as the first group of TRPs 1010 (Fig. 1) and the second group of TRPs 1014 (Fig. 1)).
  • TRPs such as the first group of TRPs 1010 (Fig. 1) and the second group of TRPs 1014 (Fig. 1)
  • the signals may be transmitted by the TRPs within a cell at certain frequencies and certain times.
  • the UEs would need to monitor for the signals at the certain frequencies and the certain times to perform the measurements on the signals.
  • the UEs may be configured to monitor for the signals as described further in relation to Figure 3 through Figure 7.
  • Figure 3 illustrates an example procedure 300 to be performed by a network, according to various embodiments.
  • the network may include one or more of the features of and/or may implemented by the network described in relation to the network arrangement 1000.
  • the network may include a core network (such as the core network XS20 (Fig. 8)), one or more NodeBs (such as the first NodeB 1006 (Fig. 1) and/or the second NodeB 1008 (Fig. 1)), one or more TRPs (such as the first group of TRPs 1010 (Fig. 1) and/or the second group of TRPs 1014 (Fig. 1)), or some combination thereof.
  • a core network such as the core network XS20 (Fig. 8)
  • NodeBs such as the first NodeB 1006 (Fig. 1) and/or the second NodeB 1008 (Fig. 1)
  • TRPs such as the first group of TRPs 1010 (Fig. 1) and/or the second group of TRPs 1014 (Fig. 1)
  • the network may determine a resource for transmission of a beamformed reference signal.
  • the core network and/or the NodeBs may determine the resource for transmission of the beamformed reference signal.
  • the network may determine that the first resource 202 (Fig. 2).
  • the network may define the resource for transmission of the beamformed reference signal based on determining which resources are available for transmission of the beamformed reference signal and defining one of the available resources as the resource for transmission of the beamformed reference signal.
  • the network may determine resources for transmission of beamformed reference signals for all the beams (such as the beams 1012 (Fig. 1) and/or the beams 1018 (Fig. 1)) transmitted by a TRP, within a cell, within the network, or some combination thereof in stage 302.
  • the resource for each of the transmissions of the beamformed reference signals may be different from the resources utilized for transmission of the other beamformed reference signals.
  • the network may determine a periodicity associated with the beamformed reference signal.
  • the beamformed reference signal may be transmitted periodically, wherein the determined resource may be utilized for one for transmission of the beamformed reference signal. Other resources occurring at times associated with the periodicity of the beamformed reference signal may be utilized for subsequent transmissions of the beamformed reference signal.
  • the network may further determine a measurement gap offset associated with the beamformed reference signal.
  • the network may generate a signal to indicate the resource for the transmission of the beamformed reference signal.
  • the signal may include one or more of the features of the configuration signals described in relation to Figure 6 and Figure 7.
  • the signal may further indicate the resources for the transmission of the beamformed reference signals for all the beams transmitted by a TRP, within a cell, within the network, or some combination thereof.
  • the network may encode the signal for transmission to a UE.
  • encoding circuitry may encode the signal for transmission.
  • the network may generate a mapping based on the signal.
  • the mapping may indicate a relationship between the information included in the signal generated in stage 304 and one or more of the features of the network architecture.
  • the mapping may indicate that combination of the process identifier, the time, and the frequency are associated with a beam, a beam identifier, a cell, or some combination thereof.
  • the time may be indicated by a timing index, wherein the time index may uniquely identify the beam, the beam identifier, the cell, or some combination thereof.
  • stage 306 may be omitted and the network may not generate the mapping.
  • the network may identify a PRACH transmission received from a UE, the PRACH transmission including a request for transmission of the beamformed reference signal for measurement by the UE.
  • stage 308 may be performed prior to stage 302, stage 304, stage 306, or some combination thereof.
  • stage 302, stage 304, stage 306, stage 312, or some combination thereof may be performed in response to the network identifying the PRACH transmission.
  • stage 308 may be omitted.
  • the network may identify a cell level measurement report received from a UE.
  • the cell level measurement report may include results of a cell level measurement performed by the UE.
  • the network may dynamically assign when the cell level measurement is to be reported to the network.
  • stage 310 may be performed prior to stage 302, stage 304, stage 306, or some combination thereof.
  • stage 302, stage 304, stage 306, stage 312, or some combination thereof may be performed in response to the network identifying the cell level
  • stage 310 may be omitted.
  • the network may transmit the signal to a UE.
  • the core network and/or the NodeB may transmit the signal via the NodeB and/or a TRP to the UE.
  • the signal may be transmitted via higher layers of the network.
  • the network may transmit the signal to the UE in response to identifying the PRACH transmission and/or the cell level measurement report.
  • the PRACH transmission and/or the cell level measurement report may trigger the network to transmit the signal. Accordingly, in these embodiments, the transmission of the signal may be dynamic rather than periodic.
  • the network may transmit the mapping to a UE.
  • the core network and/or the NodeB may transmit the signal via the NodeB and/or a TRP to the UE.
  • the mapping may be transmitted via higher layers of the network.
  • the mapping may be transmitted via a dedicated signal or broadcast to UEs.
  • stage 314 may be omitted.
  • stage 314 may be omitted in embodiments where stage 306 is omitted.
  • the network may transmit the beamformed reference signal.
  • the beamformed reference signal may be transmitted on the determined resource.
  • the core network and/or the NodeB may transmit the beamformed signal via the NodeB and/or a TRP.
  • Figure 4 illustrates a first portion of an example procedure 400 to be performed by UE, according to various embodiments.
  • the UE may include one or more of the features of and/or be implemented by the first UE 1020 (Fig. 1), the second UE 1022 (Fig. 1), the UE XSOl (Fig. 8), and/or the UE XS02 (Fig. 8).
  • the first portion of the procedure 400 may be omitted and the procedure may initiate at the second portion illustrated in Figure 5.
  • the UE may generate a PRACH transmission that includes a request for a transmission of a beamformed reference signal to be measured by the UE.
  • the UE may generate the PRACH transmission based on the UE determining that a current configuration of the UE for measurement of the beamformed reference signal is no longer valid. Further, the UE may determine that it is still within transmission range of a cell of the network.
  • the UE may encode the PRACH transmission for transmission to the network.
  • encoding circuitry (described in relation to Fig. 10) may encode the PRACH transmission for transmission.
  • the UE may transmit the PRACH transmission to a network.
  • the UE may transmit the PRACH transmission to a core network (such as the core network XS20 (Fig. 8)) and/or a NodeB (such as the first NodeB 1006 (Fig. 1) and/or the second NodeB 1008 (Fig. 1)) via a NodeB and/or a TRP (such as a TRP of the first group of TRPs 1010 (Fig. 1) and/or the second group of TRPs 1014 (Fig. 1)).
  • a core network such as the core network XS20 (Fig. 8)
  • a NodeB such as the first NodeB 1006 (Fig. 1) and/or the second NodeB 1008 (Fig. 1)
  • a TRP such as a TRP of the first group of TRPs 1010 (Fig. 1) and/or the second group of TRPs 1014 (Fig. 1)
  • stage 402 and stage 404 may be omitted.
  • the UE may perform a cell level RRM measurement.
  • the UE may perform a received power measurement, a received quality measurement, or some combination thereof on one or more reference signals associated with one or more cells (such as the first cell 1002 (Fig. 1) and/or the second cell 1004 (Fig. 1)).
  • the UE may perform the cell level RRM measurement on a synchronization signal (such as the PSS and/or the SSS).
  • the PSS and/or the SSS may be utilized for the cell level RRM measurement while the UE is in an IDLE state.
  • the network may configure the cell level measurement. Further, the UE may perform the cell level measurement periodically.
  • the UE may initiate countdown of a time-to-trigger (TTT) counter.
  • TTT time-to-trigger
  • the countdown of the TTT counter may be initiated in response to the UE performing the cell level RRM measurement.
  • the TTT counter may initiate counting from a value which may be predetermined, determined by the UE, signaled by the network, or some combination thereof.
  • the UE may generate a cell level measurement report.
  • the cell level measurement report may include results of the cell level RRM measurement performed in stage 406.
  • the UE may encode the cell level measurement report for transmission to the network.
  • encoding circuitry (described in relation to Fig. 10) may encode the cell level measurement report for transmission.
  • the UE may transmit the cell level measurement report to the network.
  • the cell level measurement may be transmitted to the core network and/or the NodeB via a NodeB and/or a TRP.
  • the cell level measurement report may be transmitted in response to expiration of the TTT counter initiated in stage 408.
  • the cell level measurement report may be transmitted to other UEs in addition to, or in lieu of, being transmitted to the network. In other embodiments, the cell level measurement report may not be transmitted.
  • stage 410 and stage 412 may be omitted. In some other embodiments, stages 406, 408, 410, and 412 may be omitted.
  • Off-page connector 414 may indicate continuation of the first portion of the procedure 400 illustrated in Figure 4 to the off-page connector 414 of the second portion of the procedure 400 illustrated in Figure 5.
  • Figure 5 illustrates a second portion of the example procedure 400 to be performed by the UE of Figure 4, according to various embodiments.
  • the second portion of the procedure 400 may be initiated in response to the first portion of the procedure 400 being completed.
  • one or more of the stages of the second portion may be performed prior to and/or concurrently to one or more of the stages of the first portion.
  • the second portion of the procedure 400 may be initiated independently from the first portion and/or periodically.
  • the UE may identify an indication of a resource in a signal received from the network.
  • the UE may identify the indication of the resource in the signal transmitted by the network in stage 312 (Fig. 3).
  • the resource may be associated with a beamformed reference signal to be transmitted by the network.
  • the UE may identify the indication for all, or some portion thereof, of the resources indicated by the signal.
  • Each of the resources may be associated with individual beamformed reference signals to be transmitted by the network, with a one-to-one ratio of resources to beamformed reference signals.
  • stage 418 the UE may identify a mapping received from the network.
  • the UE may identify the mapping transmitted by the network in stage 314 (Fig. 3).
  • stage 418 may be omitted.
  • stage 418 may also be omitted.
  • the UE may perform an RRM measurement on at least one beamformed reference signal associated with the resource or resources identified in stage 416.
  • the UE may monitor the identified resource or resources for the beamformed reference signal or the beamformed reference signals, respectively.
  • the beamformed reference signals may include CSI-RS, synchronization signals (such as PSS and/or SSS), BRS, MRS, and/or other reference signals.
  • the UE may not be monitoring the non-identified resources for beamformed reference signals, which may result in energy saving operation of the UE.
  • the RRM measurement may include a received power measurement, a received quality measurement, or some combination thereof.
  • the UE may perform the RRM measurement in response to expiration of the TTT counter initiated in stage 408.
  • the RRM measurement may be a beam level measurement and the network may configure the beam level measurement.
  • the UE may perform the RRM measurement on the CSI-RS in response to the expiration of the TTT counter initiated in stage 408 in response to the cell level RRM measurement performed in stage 406, wherein the cell level RRM
  • the synchronization signal may be a new radio
  • NR-SS synchronization signal
  • NR-PSS such as the NR-PSS and/or the NR-SSS
  • the UE may generate a measurement report.
  • the measurement report may include a result or results of the RRM measurement performed in stage 420.
  • the UE may encode the measurement report for transmission to the network.
  • encoding circuitry (described in relation to Fig. 10) may encode the measurement report for transmission.
  • the UE may transmit the measurement report to the network.
  • the UE may transmit the measurement report to the core network and/or the NodeB via a NodeB and/or a TRP.
  • the network may determine whether to initiate and/or perform a HO operation for the UE based on the measurement report.
  • the cell level measurement report may be transmitted to other UEs in addition to, or in lieu of, being transmitted to the network.
  • Figure 6 illustrates an example representation 600 of a configuration signal, according to various embodiments.
  • the configuration signal may be the signal generated by the network in stage 304 (Fig. 3) and transmitted in stage 312 (Fig. 3) in some embodiments.
  • the configuration signal may be received by the UE and the UE may identify indication of a resource in the configuration signal, as described in stage 416 (Fig. 5).
  • the representation 600 may illustrate information included in the configuration signal that may indicate a resource. Further, the information included in the configuration signal may be associated with a beamformed reference signal that is to be transmitted on the resource.
  • the configuration signal may include a process identifier 602, as indicated by the representation 600.
  • the process identifier 602 may be a cell identifier in some embodiments.
  • the cell identifier may identify a cell (such as the first cell 1002 (Fig. 1) and/or the second cell 1004 (Fig. 1)) within the network.
  • the process identifier 602 may be an identifier that is uniquely associated with a TRP (such as a TRP of the first group of TRPs 1010 (Fig. 1) and/or the second group of TRPs 1014 (Fig. 1)).
  • the UE may utilize the process identifier 602 to determine a cell or TRP associated with a beamformed reference signal to be transmitted on the resource when the UE identifies the indication of the resource in stage 416 (Fig. 5).
  • the configuration signal may include frequency information 604, as indicated by the representation 600.
  • the frequency information 604 may provide a frequency of the resource.
  • the frequency information 604 may provide the frequency at which the beamformed reference signal is to be transmitted on the resource.
  • the configuration signal may include time information 606, as indicated by the representation 600.
  • the time information 606 may provide a time of the resource.
  • the time information 606 may provide the time at which the beamformed reference signal is to be transmitted on the resource.
  • the time information 606 may include a time index that indicates the time of the resource.
  • the UE may utilize the frequency information 604 and the time information 606 to determine a specific resource on which the beamformed reference signal is to be transmitted. For example, the UE may monitor for the beamformed reference signal on the resource by monitoring for the beamformed reference signal being transmitted at the frequency provided by the frequency information 604 and at the time provided by the time information 606.
  • the process identifier 602 and one of the frequency information 604 and the time information 606 may retain a value for each beam, whereas the other of the frequency information 604 and the time information 606 may be incremented and/or set equal to a beam identifier associated with the beam.
  • a beam with beam identifier of 1 within a cell with cell identifier of 1 may have a process identifier 602 of 1, frequency information 604 that indicates 1 , and time information 606 that indicates 1.
  • a beam with a beam identifier of 2 within the same cell may have a process identifier 602 of 1 , frequency information 604 that indicates 1, and time information 606 that indicates 2.
  • the configuration signal may further include periodicity information 608, as indicated by the representation 600.
  • the periodicity information 608 may provide a time between transmissions of the beamformed reference signal.
  • the UE may utilize the periodicity information 608 to determine subsequent resources on which the beamformed reference signal is to be transmitted. For example, the UE may determine the resource for a first transmission of the beamformed reference signal based on the frequency information 604 and the time information 606, and may determine the resource for a subsequent transmission of the beamformed reference signal by determining a resource having the frequency of the resource for the first transmission and occurring at the time after the resource for the first transmission.
  • the periodicity information 608 may be omitted.
  • the process identifier 602, the frequency information 604, and the time information 606 may be utilized to uniquely identify a beam identifier associated with a beam (such as the beams 1012 (Fig. 1) and/or the beams 1018 (Fig. 1)), wherein the beam may carry the beamformed reference signal.
  • the network may generate a mapping (described in stage 306 (Fig. 3)) between the beam identifier and the associated process identifier 602, the frequency information 604, and the time information 606 that indicates the relationship between the elements.
  • Figure 7 illustrates another example representation 700 of a configuration signal, according to various embodiments.
  • the configuration signal may be the signal generated by the network in stage 304 (Fig. 3) and transmitted in stage 312 (Fig. 3) in some embodiments.
  • the configuration signal may be received by the UE and the UE may identify indication of a resource in the configuration signal, as described in stage 416 (Fig. 5).
  • the representation 700 may illustrate information included in the configuration signal that may indicate a resource. Further, the information included in the configuration signal may be associated with a beamformed reference signal that is to be transmitted on the resource.
  • the configuration signal may include measurement gap offset information 702 associated with the beamformed reference signal, as indicated by the representation 700. Further, the configuration signal may include periodicity information 704 associated with the beamformed reference signal, as indicated by the representation 700. The UE may determine a resource that the beamformed reference signal is to be transmitted on based on the measurement gap offset information 702 and the periodicity information 704.
  • FIG. 8 illustrates an architecture of a system XS00 of a network in accordance with some embodiments.
  • the system XS00 is shown to include a user equipment (UE) XS01 and a UE XS02.
  • the UEs XS01 and XS02 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • any of the UEs XS01 and XS02 can comprise an Internet of
  • IoT Internet-to-machine
  • M2M machine-to-machine
  • MTC machine-type communications
  • PLMN public land mobile network
  • Proximity - Based Service ProSe
  • D2D device-to-device
  • the M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with shortlived connections.
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UEs XS01 and XS02 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) XS 10—
  • the RAN XS10 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs XS01 and XS02 utilize connections XS03 and XS04, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections XS03 and XS04 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the UEs XS01 and XS02 may further directly exchange communication data via a ProSe interface XS05.
  • the ProSe interface XS05 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE XS02 is shown to be configured to access an access point (AP) XS06 via connection XS07.
  • the connection XS07 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP XS06 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP XS06 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN XS10 can include one or more access nodes that enable the connections XS03 and XS04. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN XS10 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node XS11, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node XS 12.
  • macrocells e.g., macro RAN node XS11
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes XS11 and XS12 can terminate the air interface protocol and can be the first point of contact for the UEs XSOl and XS02.
  • any of the RAN nodes XS11 and XS12 can fulfill various logical functions for the RAN XS 10 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs XSOl and XS02 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes XS11 and XS12 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes XS11 and XS12 to the UEs XS01 and XS02, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel may carry user data and higher- layer signaling to the UEs XS01 and XS02.
  • the physical downlink control channel may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs XS01 and XS02 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE XS02 within a cell) may be performed at any of the RAN nodes XS11 and XS12 based on channel quality information fed back from any of the UEs XS01 and XS02.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs XS01 and XS02.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub- block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN XS10 is shown to be communicatively coupled to a core network (CN) XS20— via an SI interface XS13.
  • the CN XS20 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface XS13 is split into two parts: the Sl-U interface XS14, which carries traffic data between the RAN nodes XS11 and XS12 and the serving gateway (S-GW) XS22, and the SI -mobility management entity (MME) interface XS15, which is a signaling interface between the RAN nodes XS11 and XS12 and MMEs XS21.
  • S-GW serving gateway
  • MME SI -mobility management entity
  • the CN XS20 comprises the MMEs XS21, the S-GW XS22, the Packet Data Network (PDN) Gateway (P-GW) XS23, and a home subscriber server (HSS) XS24.
  • the MMEs XS21 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs XS21 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS XS24 may comprise a database for network users, including subscription-related information to support the network entities ' handling of communication sessions.
  • the CN XS20 may comprise one or several HSSs XS24, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS XS24 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW XS22 may terminate the S 1 interface XS 13 towards the RAN XS 10, and routes data packets between the RAN XS10 and the CN XS20.
  • the S-GW XS22 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW XS23 may terminate an SGi interface toward a PDN.
  • the P-GW XS23 may route data packets between the EPC network XS20 and external networks such as a network including the application server XS30 (altematively referred to as application function (AF)) via an Internet Protocol (IP) interface XS25.
  • AF application function
  • IP Internet Protocol
  • the application server XS30 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • the P-GW XS23 is shown to be communicatively coupled to an application server XS30 via an IP communications interface XS25.
  • the application server XS30 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs XS01 and XS02 via the CN XS20.
  • VoIP Voice-over- Internet Protocol
  • the P-GW XS23 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCEF) XS26 is the policy and charging control element of the CN XS20.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF XS26 may be communicatively coupled to the application server XS30 via the P-GW XS23.
  • the application server XS30 may signal the PCRF XS26 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF XS26 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server XS30.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 9 illustrates an architecture of a system XR00 of a network in accordance with some embodiments.
  • the system XR00 is shown to include a UE XR01, which may be the same or similar to UEs XS01 and XS02 discussed previously; a RAN node XR11, which may be the same or similar to RAN nodes XS11 and XS12 discussed previously; a User Plane Function (UPF) XR02; a Data network (DN) XR03, which may be, for example, operator services, Internet access or 3rd party services; and a 5G Core Network (5GC or CN) XR20.
  • UPF User Plane Function
  • DN Data network
  • 5GC or CN 5G Core Network
  • the CN XR20 may include an Authentication Server Function (AUSF) XR22; a Core Access and Mobility Management Function (AMF) XR21; a Session Management Function (SMF) XR24; a Network Exposure Function (NEF) XR23; a Policy Control function (PCF) XR26; a Network Function (NF) Repository Function (NRF) XR25; a Unified Data Management (UDM) XR27; and an Application Function (AF) XR28.
  • the CN XR20 may also include other elements that are not shown, such as a Structured Data Storage network function (SDSF), an Unstructured Data Storage network function (UDSF), and the like.
  • SDSF Structured Data Storage network function
  • UDSF Unstructured Data Storage network function
  • the UPF XR02 may act as an anchor point for intra-RAT and inter-RAT mobility, an external protocol data unit (PDU) session point of interconnect to DN XR03, and a branching point to support multi-homed PDU session.
  • the UPF XR02 may also perform packet routing and forwarding, packet inspection, enforce user plane part of policy rules, lawfully intercept packets (UP collection), traffic usage reporting, perform QoS handling for user plane (e.g. packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering.
  • SDF service data flow
  • UPF XR02 may include an uplink classifier to support routing traffic flows to a data network.
  • the DN XR03 may represent various network operator services, Internet access, or third party services.
  • DN XR03 may include, or be similar to, application server XS30 discussed previously.
  • the AUSF XR22 may store data for authentication of UE XROl and handle authentication related functionality.
  • the AUSF XR22 may facilitate a common authentication framework for various access types.
  • the AMF XR21 may be responsible for registration management (e.g., for registering UE XROl, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization.
  • AMF XR21 may provide transport for SM messages between UE XROl and/or RAN nodes XRl l and SMF XR24, and act as a transparent proxy for routing SM messages.
  • AMF XR21 may also provide transport for short message service (SMS) messages between UE XROl and an SMS function (SMSF) (not shown by FIG. 9).
  • SMS short message service
  • AMF XR21 may act as Security Anchor Function (SEA), which may include interaction with the AUSF XR22 and the UE XROl, receipt of an intermediate key that was established as a result of the UE XROl authentication process. Where universal subscriber identity module (USIM) based authentication is used, the AMF XR21 may retrieve the security material from the AUSF XR22. AMF XR21 may also include a Security Context Management (SCM) function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF XR21 may be a termination point of RAN CP interface (N2 reference point), a termination point of NAS (Nl) signalling, and perform NAS ciphering and integrity protection.
  • SEA Security Anchor Function
  • AMF XR21 may also support NAS signalling with a UE XR01 over an N3 interworking-function (IWF) interface.
  • the N3IWF may be used to provide access to untrusted entities.
  • N33IWF may be a termination point for the N2 and N3 interfaces for control plane and user plane, respectively, and as such, may handle N2 signalling from SMF and AMF for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated to such marking received over N2.
  • N3IWF may also relay uplink and downlink control-plane NAS (Nl) signalling between the UE XR01 and AMF XR21, and relay uplink and downlink user-plane packets between the UE XR01 and UPF XR02.
  • the N3IWF also provides mechanisms for IPsec tunnel establishment with the UE XR01.
  • the SMF XR24 may be responsible for session management (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation & management (including optional Authorization); Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; termination of interfaces towards Policy control functions; control part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI System); termination of SM parts of NAS messages; downlink Data Notification; initiator of AN specific SM information, sent via AMF over N2 to AN; determine SSC mode of a session.
  • session management e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node
  • UE IP address allocation & management including optional Authorization
  • Selection and control of UP function Configures traffic steering at UPF to route traffic to proper destination; termination of interfaces towards Policy control functions; control part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI System); termination
  • the SMF XR24 may include the following roaming functionality: handle local enforcement to apply QoS service level agreements (SLAs) (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI System); support for interaction with external DN for transport of signalling for PDU session authorization/authenti cation by external DN.
  • SLAs QoS service level agreements
  • VPLMN charging data collection and charging interface
  • lawful intercept in VPLMN for SM events and interface to LI System
  • support for interaction with external DN for transport of signalling for PDU session authorization/authenti cation by external DN.
  • the NEF XR23 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re- exposure, Application Functions (e.g., AF XR28), edge computing or fog computing systems, etc.
  • the NEF XR23 may authenticate, authorize, and/or throttle the AFs.
  • NEF XR23 may also translate information exchanged with the AF XR28 and information exchanged with internal network functions. For example, the NEF XR23 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF XR23 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions.
  • NFs network functions
  • This information may be stored at the NEF XR23 as structured data, or at a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF XR23 to other NFs and AFs, and/or used for other purposes such as analytics.
  • the NRF XR25 may support service discovery functions, receive NF Discovery Requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF XR25 also maintains information of available NF instances and their supported services.
  • the PCF XR26 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behaviour.
  • the PCF XR26 may also implement a front end (FE) to access subscription information relevant for policy decisions in a user data repository (UDR) of UDM XR27.
  • FE front end
  • the UDM XR27 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE XR01.
  • the UDM XR27 may include two parts, an application FE and a User Data Repository (UDR).
  • the UDM XR27 may include a UDM FE, which is in charge of processing of 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 UDR may interact with PCF XR26.
  • UDM XR27 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously.
  • the AF XR28 may provide application influence on traffic routing, access to the
  • the NCE may be a mechanism that allows the 5GC and AF XR28 to provide information to each other via NEF XR23, which may be used for edge computing implementations.
  • the network operator and third party services may be hosted close to the UE XR01 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.
  • the 5GC may select a UPF XR02 close to the UE XR01 and execute traffic steering from the UPF XR02 to DN XR03 via the N6 interface.
  • AF XR28 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF XR28 to interact directly with relevant NFs.
  • the CN XR20 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE XROl to/from other entities, such as an SMS-gateway mobile swith center (GMSC)/interworking mobile services switching center (IWMSC)/SMS -router.
  • the SMS may also interact with AMF XR21 and UDM XR27 for notification procedure that the UE XROl is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM XR27 when UE XRO 1 is available for SMS).
  • the system XR00 may include the following service-based interfaces: Namf: Service-based interface exhibited by AMF; Nsmf: Service-based interface exhibited by SMF; Nnef: Service-based interface exhibited by NEF; Npcf: Service-based interface exhibited by PCF; Nudm: Service-based interface exhibited by UDM; Naf: Service-based interface exhibited by AF; Nnrf: Service-based interface exhibited by NRF; and Nausf: Service-based interface exhibited by AUSF.
  • Namf Service-based interface exhibited by AMF
  • Nsmf Service-based interface exhibited by SMF
  • Nnef Service-based interface exhibited by NEF
  • Npcf Service-based interface exhibited by PCF
  • Nudm Service-based interface exhibited by UDM
  • Naf Service-based interface exhibited by AF
  • Nnrf Service-based interface exhibited by NRF
  • Nausf Service-based interface exhibited by AUSF.
  • the system XR00 may include the following reference points: Nl : Reference point between the UE and the AMF; N2: Reference point between the (R)AN and the AMF; N3: Reference point between the (R)AN and the UPF; N4: Reference point between the SMF and the UPF; and N6: Reference point between the UPF and a Data Network.
  • N5 reference point may be between the PCF and the AF; an N7 reference point may be between the PCF and the SMF; an Ni l reference point may be between the AMF and SMF; etc.
  • the CN XR20 may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME XS21) and the AMF XR21 in order to enable interworking between CN XR20 and CN XS20.
  • MME e.g., MME XS21
  • AMF XR21 e.g., MME XS21
  • system XR00 may include multiple RAN nodes XR11 wherein an Xn interface is defined between two or more RAN nodes XR11 (e.g., gNBs and the like) that connecting to 5GC XR20, between a RAN node XR11 (e.g., gNB) connecting to 5GC XR20 and an eNB (e.g., a RAN node XS 11 of FIG. 8), and/or between two eNBs connecting to 5GC XR20.
  • RAN node XR11 e.g., gNB
  • eNB e.g., a RAN node XS 11 of FIG. 8
  • the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface.
  • the Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality.
  • the Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE XROl in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes XRl 1.
  • a connected mode e.g., CM-CONNECTED
  • the mobility support may include context transfer from an old (source) serving RAN node XRl 1 to new (target) serving RAN node XRl 1 ; and control of user plane tunnels between old (source) serving RAN node XRl 1 to new (target) serving RAN node XRl 1.
  • a protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a general packet radio service tunneling protocol user (GTP-U) layer on top of a universal datagram protocol (UDP) and/or IP layer(s) to carry user plane PDUs.
  • IP Internet Protocol
  • GTP-U general packet radio service tunneling protocol user
  • UDP universal datagram protocol
  • IP Internet Protocol
  • GTP-U general packet radio service tunneling protocol user
  • UDP universal datagram protocol
  • IP layer(s) to carry user plane PDUs.
  • the Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on an stream control transmission protocol (SCTP) layer.
  • SCTP stream control transmission protocol
  • the SCTP layer may be on top of an IP layer.
  • the SCTP layer provides the guaranteed delivery of application layer messages.
  • point-to-point point-to-point
  • the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.
  • Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.
  • Figure 10 illustrates, for one embodiment, example components of an electronic device 100.
  • the electronic device 100 may be, implement, be incorporated into, or otherwise be a part of a user equipment (UE), an evolved NodeB (eNB), and/or some other electronic device.
  • UE user equipment
  • eNB evolved NodeB
  • Figure 10 illustrates, for one embodiment, example components of an electronic device 100.
  • the electronic device 100 may be, implement, be incorporated into, or otherwise be a part of a user equipment (UE), an evolved NodeB (eNB), and/or some other electronic device.
  • UE user equipment
  • eNB evolved NodeB
  • the electronic device 100 may include application circuitry 102, baseband circuitry 104, Radio Frequency (RF) circuitry 106, front-end module (FEM) circuitry 108 and one or more antennas 110, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the electronic device 100 may also include network interface circuitry (not shown) for communicating over a wired interface (for example, an X2 interface, an SI interface, and the like).
  • the application circuitry 102 may include one or more application processors.
  • the application circuitry 102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors 102a.
  • the processor(s) 102a may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors 102a may be coupled with and/or may include computer-readable media 102b (also referred to as "CRM 102b", “memory 102b”, “storage 102b”, or “memory /storage 102b") and may be configured to execute instructions stored in the CRM 102b to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 104 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 106 and to generate baseband signals for a transmit signal path of the RF circuitry 106.
  • Baseband circuity 104 may interface with the application circuitry 102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 106.
  • the baseband circuitry 104 may include a second generation (2G) baseband processor 104a, third generation (3G) baseband processor 104b, fourth generation (4G) baseband processor 104c, and/or other baseband processor(s) 104d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 104 e.g., one or more of baseband processors 104a-d
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like.
  • modulation/demodulation circuitry of the baseband circuitry 104 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 104 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • the encoding/decoding circuitry may encode and/or decode signals for transmission between components described herein.
  • the encoding/decoding circuitry may encode the signal generated in stage 304 (Fig. 3) for transmission to the UE.
  • the encoding/decoding circuitry may encode the measurement report generated in stage 422 (Fig. 5) for transmission to the network.
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 104 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (E-UTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements.
  • E-UTRAN evolved universal terrestrial radio access network
  • a central processing unit (CPU) 104e of the baseband circuitry 104 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 104f.
  • the audio DSP(s) 104f may include elements for
  • the baseband circuitry 104 may further include computer-readable media 104g (also referred to as “CRM 104g”, “memory 104g", “storage 104g”, or “CRM 104g”).
  • CRM 104g may be used to load and store data and/or instructions for operations performed by the processors of the baseband circuitry 104.
  • CRM 104g for one embodiment may include any combination of suitable volatile memory and/or non-volatile memory.
  • the CRM 104g may include any combination of various levels of memory /storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc.).
  • ROM read-only memory
  • DRAM dynamic random access memory
  • the CRM 104g may be shared among the various processors or dedicated to particular processors.
  • Components of the baseband circuitry 104 may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 104 and the application circuitry 102 may be implemented together, such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 104 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 104 may support communication with an E-UTRAN and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 104 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 106 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 106 may include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network.
  • RF circuitry 106 may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry 108 and provide baseband signals to the baseband circuitry 104.
  • RF circuitry 106 may also include a transmit signal path that may include circuitry to up- convert baseband signals provided by the baseband circuitry 104 and provide RF output signals to the FEM circuitry 108 for transmission.
  • the RF circuitry 106 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 106 may include mixer circuitry 106a, amplifier circuitry 106b and filter circuitry 106c.
  • the transmit signal path of the RF circuitry 106 may include filter circuitry 106c and mixer circuitry 106a.
  • RF circuitry 106 may also include synthesizer circuitry 106d for synthesizing a frequency for use by the mixer circuitry 106a of the receive signal path and the transmit signal path.
  • the mixer circuitry 106a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 108 based on the synthesized frequency provided by synthesizer circuitry 106d.
  • the amplifier circuitry 106b may be configured to amplify the down-converted signals and the filter circuitry 106c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 104 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 106a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 106a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 106d to generate RF output signals for the FEM circuitry 108.
  • the baseband signals may be provided by the baseband circuitry 104 and may be filtered by filter circuitry 106c.
  • the filter circuitry 106c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion, respectively.
  • the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 104 may include a digital baseband interface to communicate with the RF circuitry 106.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio integrated circuit (IC) circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 106d may be a fractional -N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 106d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 106d may be configured to synthesize an output frequency for use by the mixer circuitry 106a of the RF circuitry 106 based on a frequency input and a divider control input.
  • the synthesizer circuitry 106d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 104 or the application circuitry 102 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 102.
  • Synthesizer circuitry 106d of the RF circuitry 106 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 106d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 106 may include an IQ/polar converter.
  • FEM circuitry 108 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 110, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 106 for further processing.
  • FEM circuitry 108 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 106 for transmission by one or more of the one or more antennas 110.
  • the FEM circuitry 108 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 108 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 108 may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 106).
  • the transmit signal path of the FEM circuitry 108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1 10).
  • PA power amplifier
  • the electronic device 100 may include additional elements such as, for example, a display, a camera, one or more sensors, and/or interface circuitry (for example, input/output (I/O) interfaces or buses) (not shown).
  • the electronic device may include network interface circuitry.
  • the network interface circuitry may be one or more computer hardware components that connect electronic device 100 to one or more network elements, such as one or more servers within a core network or one or more other eNBs via a wired connection.
  • the network interface circuitry may include one or more dedicated processors and/or field programmable gate arrays (FPGAs) to
  • AP application protocol
  • SI AP Stream Control Transmission Protocol
  • SCTP Stream Control Transmission Protocol
  • Ethernet Ethernet
  • PPP Point-to-Point
  • FDDI Fiber Distributed Data Interface
  • the electronic device 100 of Figure 10 may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof.
  • FIG. 11 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 104 of FIG. 10 may comprise processors 104a-104e and a memory 104g utilized by said processors.
  • Each of the processors 104a-104e may include a memory interface, XU04A-XU04E, respectively, to send/receive data to/from the memory 104g.
  • the baseband circuitry 104 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface XU12 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 104), an application circuitry interface XU14 (e.g., an interface to send/receive data to/from the application circuitry 102 of FIG. 10), an RF circuitry interface XU16 (e.g., an interface to send/receive data to/from RF circuitry 106 of FIG.
  • a memory interface XU12 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 104
  • an application circuitry interface XU14 e.g., an interface to send/receive data to/from the application circuitry 102 of FIG. 10
  • an RF circuitry interface XU16 e.g., an interface to send/receive data to/from RF circuit
  • a wireless hardware connectivity interface XU18 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface XU20 e.g., an interface to send/receive power or control signals to/from power management circuitry.
  • FIG. 12 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane XV00 is shown as a communications protocol stack between the UE XS01 (or alternatively, the UE XS02), the RAN node XS 11 (or alternatively, the RAN node XS 12), and the MME XS21.
  • the PHY layer XV01 may transmit or receive information used by the MAC layer XV02 over one or more air interfaces.
  • the PHY layer XV01 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer XV05.
  • the PHY layer XV01 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.
  • FEC forward error correction
  • MIMO Multiple Input Multiple Output
  • the MAC layer XV02 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.
  • SDUs MAC service data units
  • TB transport blocks
  • HARQ hybrid automatic repeat request
  • the RLC layer XV03 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM Acknowledged Mode
  • the RLC layer XV03 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • PDUs protocol data units
  • ARQ automatic repeat request
  • the RLC layer XV03 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
  • the PDCP layer XV 04 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
  • security operations e.g., ciphering, deciphering, integrity protection, integrity verification, etc.
  • the main services and functions of the RRC layer XV05 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting.
  • SIBs may comprise one or more information elements (IEs), which may each comprise individual data fields or data structures.
  • the UE XS01 and the RAN node XS11 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer XV01, the MAC layer XV02, the RLC layer XV03, the PDCP layer XV04, and the RRC layer XV05.
  • a Uu interface e.g., an LTE-Uu interface
  • the non-access stratum (NAS) protocols XV06 form the highest stratum of the control plane between the UE XS01 and the MME XS21.
  • the NAS protocols XV06 support the mobility of the UE XS01 and the session management procedures to establish and maintain IP connectivity between the UE XS01 and the P-GW XS23.
  • the SI Application Protocol (Sl-AP) layer XV 15 may support the functions of the SI Application Protocol (Sl-AP) layer XV 15.
  • the Sl-AP layer services may comprise two groups: UE-associated services andnon UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.
  • E-RAB E-UTRAN Radio Access Bearer
  • RIM RAN Information Management
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) XV 14 may ensure reliable delivery of signaling messages between the RAN node XSl l and the MME XS21 based, in part, on the IP protocol, supported by the IP layer XV13.
  • the L2 layer XV12 and the LI layer XVI 1 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • the RAN node XS11 and the MME XS21 may utilize an SI -MME interface to exchange control plane data via a protocol stack comprising the LI layer XVI 1, the L2 layer XV 12, the IP layer XV 13, the SCTP layer XV 14, and the Sl-AP layer XV15.
  • FIG. 13 is an illustration of a user plane protocol stack in accordance with some embodiments.
  • a user plane XW00 is shown as a communications protocol stack between the UE XS01 (or alternatively, the UE XS02), the RAN node XS11 (or alternatively, the RAN node XS12), the S-GW XS22, and the P-GW XS23.
  • the user plane XW00 may utilize at least some of the same protocol layers as the control plane XV00.
  • the UE XS01 and the RAN node XS11 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer XV01, the MAC layer XV02, the RLC layer XV03, the PDCP layer XV04.
  • a Uu interface e.g., an LTE-Uu interface
  • the General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer XW04 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer XW03 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node XS 11 and the S-GW XS22 may utilize an Sl-U interface to exchange user plane data via a protocol stack comprising the LI layer XVI 1, the L2 layer XV12, the UDP/IP layer XW03, and the GTP-U layer XW04.
  • the S-GW XS22 and the P-GW XS23 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the LI layer XVI 1, the L2 layer XV12, the UDP/IP layer XW03, and the GTP-U layer XW04.
  • NAS protocols support the mobility of the UE XS01 and the session management procedures to establish and maintain IP connectivity between the UE XS01 and the P-GW XS23.
  • FIG. 14 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • FIG. 14 shows a diagrammatic representation of hardware resources XZ00 including one or more processors (or processor cores) XZ10, one or more memory /storage devices XZ20, and one or more communication resources XZ30, each of which may be communicatively coupled via a bus XZ40.
  • a hypervisor XZ02 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources XZ00.
  • the processors XZ10 may include, for example, a processor XZ12 and a processor XZ14.
  • the memory /storage devices XZ20 may include main memory, disk storage, or any suitable combination thereof.
  • the memory /storage devices XZ20 may include, but are not limited to, any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read- only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources XZ30 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices XZ04 or one or more databases XZ06 via a network XZ08.
  • the communication resources XZ30 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • Instructions XZ50 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors XZ10 to perform any one or more of the methodologies discussed herein.
  • the instructions XZ50 may reside, completely or partially, within at least one of the processors XZ10 (e.g., within the processor's cache memory), the memory /storage devices XZ20, or any suitable combination thereof.
  • any portion of the instructions XZ50 may be transferred to the hardware resources XZ00 from any combination of the peripheral devices XZ04 or the databases XZ06. Accordingly, the memory of processors XZ10, the memory /storage devices XZ20, the peripheral devices XZ04, and the databases XZ06 are examples of computer-readable and machine-readable media.
  • the present disclosure may be embodied as methods or computer program products. Accordingly, the present disclosure, in addition to being embodied in hardware as earlier described, may take the form of an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to as a "circuit," "module” or “system.” Furthermore, the present disclosure may take the form of a computer program product embodied in any tangible or non-transitory medium of expression having computer-usable program code embodied in the medium.
  • Figure 15 illustrates an example computer-readable non-transitory storage medium that may be suitable for use to store instructions that cause an apparatus, in response to execution of the instructions by the apparatus, to practice selected aspects of the present disclosure.
  • non-transitory computer-readable storage medium 1502 may include a number of programming instructions 1504.
  • Programming instructions 1504 may be configured to enable a device, e.g., a NodeB (such as the first NodeB 1006 (Fig. 1) and/or the second NodeB 1008 (Fig. 1)), a TRP (such as a TRP of the first group of TRPs 1010 (Fig. 1) and/or the second group of TRPs 1014 (Fig. 1)), a UE (such as the first UE 1020 (Fig.
  • a NodeB such as the first NodeB 1006 (Fig. 1) and/or the second NodeB 1008 (Fig. 1)
  • TRP such as a TRP of the first group of TRPs 1010 (Fig. 1) and/or the second group of T
  • programming instructions 1504 may be disposed on multiple computer-readable non-transitory storage media 1502 instead. In still other embodiments, programming instructions 1504 may be disposed on computer-readable transitory storage media 1502, such as signals.
  • the computer-usable or computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium.
  • the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • CD-ROM compact disc read-only memory
  • a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device.
  • the computer- usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
  • a computer-usable or computer- readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
  • the computer- usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave.
  • the computer usable program code may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc.
  • Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Example 1 may include an apparatus of a next generation NodeB (gNB), comprising processing circuitry to determine a resource for transmission of a beamformed reference signal of a network that implements beamforming and generate a signal that indicates the resource, and encoding circuitry, coupled with the processing circuitry, to encode the signal for transmission to a user equipment (UE) that is to utilize the beamformed reference signal to perform a radio resource management measurement.
  • gNB next generation NodeB
  • UE user equipment
  • Example 2 may include the apparatus of example 1 , wherein the signal includes a process identifier, frequency information associated with the resource, and time information associated with the resource.
  • Example 3 may include the apparatus of example 2, wherein the process identifier is a cell identifier.
  • Example 4 may include the apparatus of example 2, wherein the process identifier is an identifier that is uniquely associated with a transmission and reception point.
  • Example 5 may include the apparatus of example 2, wherein the signal further includes a periodicity associated with the beamformed reference signal.
  • Example 6 may include the apparatus of example 2, wherein the process identifier, the frequency information, and the time information uniquely identify a beam identifier, and wherein the processing circuitry is to further generate a mapping between a cell identifier and the beam identifier, and wherein the encoding circuitry is to further encode the mapping for transmission to the UE.
  • Example 7 may include the apparatus of example 2, wherein the time information includes an indication of a timing index.
  • Example 8 may include the apparatus of example 1 , wherein the signal includes a measurement gap offset and a periodicity associated with the beamformed reference signal.
  • Example 9 may include the apparatus of any of examples 1-8, wherein the beamformed reference signal is a channel state information reference signal.
  • Example 10 may include the apparatus of any of examples 1 -8, wherein the beamformed reference signal is a synchronization signal.
  • Example 1 1 may include the apparatus of any of examples 1 -8, wherein the beamformed reference signal is a beam reference signal or a measurement reference signal.
  • Example 12 may include the apparatus of any of examples 1 -8, wherein the processing circuitry is to further identify a physical random access channel (PRACH) transmission received from the UE, and wherein the signal is to be transmitted to the UE in response to identification of the PRACH transmission.
  • Example 13 may include the apparatus of any of examples 1-8, wherein the beamformed reference signal is associated with a beam level measurement, wherein the processing circuitry is further to identify a cell level measurement report received from the UE, and wherein the signal is to be transmitted in response to identification of the cell level measurement report.
  • PRACH physical random access channel
  • Example 14 may include one or more computer-readable media having instructions stored thereon, wherein the instructions, in response to execution by a next generation NodeB (gNB), cause the gNB to determine a resource for transmission of a beamformed reference signal, wherein the beamformed reference signal is a channel state information reference signal, a synchronization signal, a beam reference signal, or a measurement reference signal, generate a signal that indicates the resource, and encode the signal for transmission to a user equipment (UE) that utilizes the beamformed reference signal to perform a radio resource management measurement.
  • a next generation NodeB gNB
  • the instructions in response to execution by a next generation NodeB (gNB), cause the gNB to determine a resource for transmission of a beamformed reference signal, wherein the beamformed reference signal is a channel state information reference signal, a synchronization signal, a beam reference signal, or a measurement reference signal, generate a signal that indicates the resource, and encode the signal for transmission to a user equipment (UE) that utilizes the beamformed reference signal to
  • Example 15 may include the one or more computer-readable media of example 14, wherein the signal includes a process identifier, frequency information, and time information associated with the resource.
  • Example 16 may include the one or more computer-readable media of example 15, wherein the process identifier is a cell identifier.
  • Example 17 may include the one or more computer-readable media of example 15, wherein the process identifier is an identifier that is uniquely associated with a transmission and reception point.
  • Example 18 may include the one or more computer-readable media of example 15, wherein the signal further includes a periodicity associated with the beamformed reference signal.
  • Example 19 may include the one or more computer-readable media of example 15, wherein the process identifier, the frequency information, and the time information uniquely identify a beam identifier, and wherein the instructions, in response to execution by the gNB, further cause the gNB to generate a mapping between a cell identifier and the beam identifier and encode the mapping for transmission to the UE.
  • Example 20 may include the one or more computer-readable media of example 15, wherein the time information includes an indication of a timing index.
  • Example 21 may include the one or more computer-readable media of example 13, wherein the signal includes a measurement gap offset and a periodicity associated with the resource.
  • Example 22 may include the one or more computer-readable media of any of examples 13-21 , wherein the instructions, in response to execution by the gNB, further cause the gNB to identify a physical random access channel (PRACH) transmission received from the UE, and wherein the signal is to be transmitted to the UE in response to identification of the PRACH transmission.
  • PRACH physical random access channel
  • Example 23 may include the one or more computer-readable media of any of examples 13-21 , wherein the beamformed reference signal is associated with a beam level measurement, wherein the instructions, in response to execution by the gNB, further cause the gNB to identify a cell level measurement report received from the UE, and wherein the signal is to be transmitted in response to identification of the cell level measurement report.
  • Example 24 may include a method for configuring radio resource management (RRM) measurement in a network that implements beamforming, comprising determining, via a next generation NodeB (gNB), a resource for transmission of a beamformed reference signal of a network that implements beamforming, generating, via the gNB, a signal that indicates the resource, and encoding, via the gNB, the signal for transmission to a user equipment (UE) that utilizes the beamformed reference signal to perform an RRM measurement.
  • RRM radio resource management
  • Example 25 may include the method of example 24, wherein the signal includes a process identifier, frequency information, and time information associated with the resource.
  • Example 26 may include the method of example 25, wherein the process identifier is a cell identifier.
  • Example 27 may include the method of example 25, wherein the process identifier is an identifier that is uniquely associated with a transmission and reception point.
  • Example 28 may include the method of example 25, wherein the signal further includes a periodicity associated with the resource.
  • Example 29 may include the method of example 25, wherein the process identifier, the frequency, and the time information uniquely identify a beam identifier, and wherein the method further comprises generating, via the gNB, a mapping between a cell identifier and the beam identifier and encoding, via the gNB, the mapping for transmission to the UE.
  • Example 30 may include the method of example 25, wherein the time information includes an indication of a timing index.
  • Example 31 may include the method of example 22, wherein the signal includes a measurement gap offset and a periodicity associated with the resource.
  • Example 32 may include the method of any of examples 22-31, wherein the beamformed reference signal is a channel state information reference signal.
  • Example 33 may include the method of any of examples 22-31, wherein the beamformed reference signal is a synchronization signal.
  • Example 34 may include the method of any of examples 22-31, wherein the beamformed reference signal is a beam reference signal or a measurement reference signal.
  • Example 35 may include the method of any of examples 22-31, further comprising identifying, via the gNB, a physical random access channel (PRACH) transmission received from the UE, and wherein the signal is to be transmitted to the UE in response to identification of the PRACH transmission.
  • PRACH physical random access channel
  • Example 36 may include the method of any of examples 22-31, wherein the beamformed reference signal is associated with a beam level measurement, wherein the method further comprises identifying, via the gNB, a cell level measurement report received from the UE, and wherein the signal is to be transmitted in response to identification of the cell level measurement report.
  • Example 37 may include an apparatus of a next generation NodeB (gNB), comprising means for determining a resource for transmission of a beamformed reference signal of a network that implements beamforming and generating a signal that indicates the resource and means for encoding the signal for transmission to a user equipment (UE) that utilizes the beamformed reference signal to perform an RRM measurement.
  • gNB next generation NodeB
  • UE user equipment
  • Example 38 may include the apparatus of example 37, wherein the signal includes a process identifier, frequency information, and time information associated with the resource.
  • Example 39 may include the apparatus of example 38, wherein the process identifier is a cell identifier.
  • Example 40 may include the apparatus of example 38, wherein the process identifier is an identifier that is uniquely associated with a transmission and reception point.
  • Example 41 may include the apparatus of example 38, wherein the signal further includes a periodicity associated with the resource.
  • Example 42 may include the apparatus of example 38, wherein the process identifier, the frequency, and the time information uniquely identify a beam identifier, and wherein the apparatus further includes means for generating a mapping between a cell identifier and the beam identifier and means for encoding the mapping for transmission to the UE.
  • Example 43 may include the apparatus of example 38, wherein the time information includes an indication of a timing index.
  • Example 44 may include the apparatus of any of examples 37-43, wherein the signal includes a measurement gap offset and a periodicity associated with the resource.
  • Example 45 may include the apparatus of any of examples 37-43, wherein the beamformed reference signal is a channel state information reference signal.
  • Example 46 may include the apparatus of any of examples 37-43, wherein the beamformed reference signal is a synchronization signal.
  • Example 47 may include the apparatus of any of examples 37-43, wherein the beamformed reference signal is a beam reference signal or a measurement reference signal.
  • Example 48 may include the apparatus of any of examples 37-43, further comprising means for identifying a physical random access channel (PRACH) transmission received from the UE, and wherein the signal is to be transmitted to the UE in response to identification of the PRACH transmission.
  • PRACH physical random access channel
  • Example 49 may include the apparatus of any of examples 37-43, wherein the beamformed reference signal is associated with a beam level measurement, wherein the apparatus further comprises means for identifying, via the gNB, a cell level measurement report received from the UE, and wherein the signal is to be transmitted in response to identification of the cell level measurement report.
  • Example 50 may include an apparatus for a user equipment, comprising processing circuitry to identify an indication of a resource in a signal received from a next generation NodeB (gNB), the resource to be utilized for transmission of a beamformed reference signal and perform a radio resource management (RRM) measurement with the beamformed reference signal on the resource.
  • processing circuitry to identify an indication of a resource in a signal received from a next generation NodeB (gNB), the resource to be utilized for transmission of a beamformed reference signal and perform a radio resource management (RRM) measurement with the beamformed reference signal on the resource.
  • RRM radio resource management
  • Example 51 may include the apparatus of example 50, wherein the processing circuitry is to further generate a measurement report based on the RRM measurement, and wherein the apparatus further comprises encoding circuitry, coupled with the processing circuitry, to encode the measurement report for transmission to the gNB.
  • Example 52 may include the apparatus of any of examples 50 or 51, wherein the indication includes a process identifier, frequency information, and time information associated with the resource.
  • Example 53 may include the apparatus of example 52, wherein the process identifier is a cell identifier.
  • Example 54 may include the apparatus of example 52, wherein the process identifier is an identifier that is uniquely associated with a transmission and reception point.
  • Example 55 may include the apparatus of example 52, wherein the indication further includes a periodicity associated with the resource.
  • Example 56 may include the apparatus of example 52, wherein the process identifier, the frequency information, and the time information uniquely identify a beam identifier, wherein the processing circuitry is to further identify a mapping received from the gNB, and wherein the mapping indicates a relationship between the beam identifier and a cell identifier.
  • Example 57 may include the apparatus of example 52, wherein the time information includes an indication of a timing index.
  • Example 58 may include the apparatus of any of examples 50 or 51, wherein the indication includes a measurement gap offset and a periodicity associated with the resource.
  • Example 59 may include the apparatus of any of examples 50 or 51, wherein the beamformed reference signal is a channel state information reference signal.
  • Example 60 may include the apparatus of any of examples 50 or 51, wherein the beamformed reference signal is a synchronization signal.
  • Example 61 may include the apparatus of any of examples 50 or 51, wherein the beamformed reference signal is a beam reference signal or a measurement reference signal.
  • Example 62 may include the apparatus of any of examples 50 or 51, wherein the processing circuitry is to further generate a physical random access channel (PRACH) transmission, wherein the apparatus further comprises encoding circuitry, coupled to the processing circuitry, to encode the PRACH transmission for transmission to the gNB, and wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the PRACH transmission.
  • PRACH physical random access channel
  • Example 63 may include the apparatus of any of examples 50 or 51, wherein RRM measurement is a beam level RRM measurement, and wherein the processing circuitry is to further perform a cell level RRM measurement and generate a cell level measurement report based on the cell level RRM measurement, and the apparatus further comprises encoding circuitry, coupled to the processing circuitry, to encode the cell level measurement report for transmission to the gNB, wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the cell level RRM measurement.
  • Example 64 may include the apparatus of example 63, wherein the processing circuitry is to further initiate countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the cell level measurement report is to be transmitted to the gNB upon expiration of the time-to-trigger.
  • Example 65 may include the apparatus of any of examples 50 or 51, wherein the RRM measurement is a beam level RRM measurement, and wherein the processing circuitry is to further perform a cell level RRM measurement and initiate countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the beam level RRM measurement is to be performed upon expiration of the time-to- trigger.
  • the RRM measurement is a beam level RRM measurement
  • the processing circuitry is to further perform a cell level RRM measurement and initiate countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the beam level RRM measurement is to be performed upon expiration of the time-to- trigger.
  • Example 66 may include one or more computer-readable media having instructions stored thereon, wherein the instructions, in response to execution by a user equipment (UE), cause the UE to identify an indication of a resource in a signal received, via the RF circuitry, from a next generation NodeB (gNB), the resource to be utilized for transmission of a beamformed reference signal, wherein the beamformed reference signal is a channel state information reference signal, a synchronization signal, a beam reference signal, or a measurement reference signal and perform a radio resource management (RRM) measurement with the beamformed reference signal on the resource.
  • UE user equipment
  • gNB next generation NodeB
  • RRM radio resource management
  • Example 67 may include the one or more computer-readable media of example 66, wherein the instructions, in response to execution by the UE, further cause the UE to generate a measurement report based on the RRM measurement and encode the measurement report for transmission to the gNB.
  • Example 68 may include the one or more computer-readable media of any of examples 66 or 67, wherein the indication includes a process identifier, frequency information, and a time information associated with the resource.
  • Example 69 may include the one or more computer-readable media of example 68, wherein the process identifier is a cell identifier.
  • Example 70 may include the one or more computer-readable media of example 68, wherein the process identifier is an identifier that is uniquely associated with a transmission and reception point.
  • Example 71 may include the one or more computer-readable media of example 68, wherein the indication further includes a periodicity associated with the resource.
  • Example 72 may include the one or more computer-readable media of example 68, wherein the process identifier, the frequency information, and the time information uniquely identify a beam identifier, wherein the instructions, in response to execution by the UE, further cause the UE to identify a mapping received from the gNB, and wherein the mapping indicates a relationship between the beam identifier and a cell identifier.
  • Example 73 may include the one or more computer-readable media of example 68, wherein the time information includes an indication of a timing index.
  • Example 74 may include the one or more computer-readable media of any of examples 66 or 67, wherein the indication includes a measurement gap offset and a periodicity associated with the resource.
  • Example 75 may include the one or more computer-readable media of any of examples 66 or 67, wherein the instructions, in response to execution by the UE, further cause the UE to generate a physical random access channel (PRACH) transmission and encode the PRACH transmission for transmission to the gNB, wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the PRACH transmission.
  • PRACH physical random access channel
  • Example 76 may include the one or more computer-readable media of any of examples 66 or 67, wherein RRM measurement is a beam level RRM measurement, and wherein the instructions, in response to execution by the UE, further cause the UE to perform a cell level RRM measurement, generate a cell level measurement report based on the cell level RRM measurement, and encode the cell level measurement report for transmission to the gNB, wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the cell level RRM measurement.
  • RRM measurement is a beam level RRM measurement
  • the instructions in response to execution by the UE, further cause the UE to perform a cell level RRM measurement, generate a cell level measurement report based on the cell level RRM measurement, and encode the cell level measurement report for transmission to the gNB, wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the cell level RRM measurement.
  • Example 77 may include the one or more computer-readable media of example 76, wherein the instructions, in response to execution by the UE, further cause the UE to initiate countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the cell level measurement report is to be transmitted to the gNB upon expiration of the time-to-trigger.
  • Example 78 may include the one or more computer-readable media of any of examples 66 or 67, wherein the RRM measurement is a beam level RRM measurement, and wherein the instructions, in response to execution by the UE, further cause the UE to perform a cell level RRM measurement and initiate countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the beam level RRM measurement is to be performed upon expiration of the time-to-trigger.
  • Example 79 may include a method for performing radio resource management
  • RRM radio resource measurement in a network that implements beamforming, comprising identifying, via a user equipment (UE), an indication of a resource in a signal received from a next generation NodeB (gNB), the resource to be utilized for transmission of a beamformed reference signal and performing, via the UE, the RRM measurement with the beamformed reference signal on the resource.
  • UE user equipment
  • gNB next generation NodeB
  • Example 80 may include the method of example 79, further comprising generating, via the UE, a measurement report based on the RRM measurement, and encoding, via the UE, the measurement report for transmission to the gNB.
  • Example 81 may include the method of any of examples 79 or 80, wherein the indication includes a process identifier, frequency information, and time information associated with the resource.
  • Example 82 may include the method of example 81, wherein the process identifier is a cell identifier.
  • Example 83 may include the method of example 81, wherein the process identifier is an identifier that is uniquely associated with a transmission and reception point.
  • Example 84 may include the method of example 81, wherein the indication further includes a periodicity associated with the resource.
  • Example 85 may include the method of example 81, wherein the process identifier, the frequency information, and the time information uniquely identify a beam identifier, wherein the method further comprises identifying, via the UE, a mapping received, via the RF circuitry, from the gNB, and wherein the mapping indicates a relationship between the beam identifier and a cell identifier.
  • Example 86 may include the method of example 81, wherein the time information includes an indication of a timing index.
  • Example 87 may include the method of any of examples 79 or 80, wherein the indication includes a measurement gap offset and a periodicity associated with the resource.
  • Example 88 may include the method of any of examples 79 or 80, wherein the beamformed reference signal is a channel state information reference signal.
  • Example 89 may include the method of any of examples 79 or 80, wherein the beamformed reference signal is a synchronization signal.
  • Example 90 may include the method of any of examples 79 or 80, wherein the beamformed reference signal is a beam reference signal or a measurement reference signal.
  • Example 91 may include the method of any of examples 79 or 80, further comprising generating, via the UE, a physical random access channel (PRACH) transmission and encoding, via the UE, the PRACH transmission for transmission to the gNB, wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the PRACH transmission.
  • PRACH physical random access channel
  • Example 92 may include the method of any of examples 79 or 80, wherein RRM measurement is a beam level RRM measurement, and wherein the method further comprises performing, via the UE, a cell level RRM measurement, generating, via the UE, a cell level measurement report based on the cell level RRM measurement, and encoding, via the UE, the cell level measurement report for transmission to the gNB, wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the cell level RRM measurement.
  • Example 93 may include the method of example 92, further comprising initiating, via the UE, countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the cell level measurement report is to be transmitted upon expiration of the time-to-trigger.
  • Example 94 may include the method of any of examples 79 or 80, wherein the RRM measurement is a beam level RRM measurement, and wherein the method further comprises performing, via the UE, a cell level RRM measurement and initiating, via the UE, countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the beam level RRM measurement is to be performed upon expiration of the time-to-trigger.
  • Example 95 may include an apparatus for a user equipment, comprising means for identifying an indication of a resource in a signal received from a next generation NodeB (gNB), the resource to be utilized for transmission of a beamformed reference signal and means for performing a radio resource management (RRM) measurement with the beamformed reference signal on the resource.
  • gNB next generation NodeB
  • RRM radio resource management
  • Example 96 may include the apparatus of example 95, further comprising means for generating a measurement report based on the RRM measurement and means for encoding the measurement report for transmission to the gNB.
  • Example 97 may include the apparatus of any of examples 95 or 96, wherein the indication includes a process identifier, frequency information, and time information associated with the resource.
  • Example 98 may include the apparatus of example 97, wherein the process identifier is a cell identifier.
  • Example 99 may include the apparatus of example 97, wherein the process identifier is an identifier that is uniquely associated with a transmission and reception point.
  • Example 100 may include the apparatus of example 97, wherein the indication further includes a periodicity associated with the resource.
  • Example 101 may include the apparatus of example 97, wherein the process identifier, the frequency information, and the time information uniquely identify a beam identifier, wherein the apparatus further comprises means for identifying a mapping received from the gNB, and wherein the mapping indicates a relationship between the beam identifier and a cell identifier.
  • Example 102 may include the apparatus of example 97, wherein the time information includes an indication of a timing index.
  • Example 103 may include the apparatus of any of examples 95 or 96, wherein the indication includes a measurement gap offset and a periodicity associated with the resource.
  • Example 104 may include the apparatus of any of examples 95 or 96, wherein the beamformed reference signal is a channel state information reference signal.
  • Example 105 may include the apparatus of any of examples 95 or 96, wherein the beamformed reference signal is a synchronization signal.
  • Example 106 may include the apparatus of any of examples 95 or 96, wherein the beamformed reference signal is a beam reference signal or a measurement reference signal.
  • Example 107 may include the apparatus of any of examples 95 or 96, further comprising means for generating a physical random access channel (PRACH) transmission and means for encoding the PRACH transmission for transmission to the gNB, wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the PRACH transmission.
  • PRACH physical random access channel
  • Example 108 may include the apparatus of any of examples 95 or 96, wherein RRM measurement is a beam level RRM measurement, and wherein the apparatus further comprises means for performing a cell level RRM measurement, means for generating a cell level measurement report based on the cell level RRM measurement, and means for encoding the cell level measurement report for transmission to the gNB, wherein the gNB is to transmit the signal with the indication of the resource in response to reception of the cell level RRM measurement.
  • Example 109 may include the apparatus of example 108, further comprising means for initiating, via the UE, countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the cell level measurement report is to be transmitted upon expiration of the time-to-trigger.
  • Example 1 10 may include the apparatus of any of examples 95 or 96, wherein the RRM measurement is a beam level RRM measurement, and wherein the apparatus further comprises means for performing a cell level RRM measurement and means for initiating countdown of a time-to-trigger in response to performance of the cell level RRM measurement, wherein the beam level RRM measurement is to be performed upon expiration of the time-to-trigger.

Abstract

L'invention concerne des appareils, des systèmes et des procédés associés à la configuration d'un mesurage de gestion de ressources radio (RRM). Un appareil d'un nœud B de prochaine génération (gNB) peut comprendre un montage de circuits de traitement pour déterminer une ressource pour la transmission d'un signal de référence à formation de faisceau d'un réseau implémentant une formation de faisceau, et générer un signal qui indique la ressource. L'appareil peut comprendre en outre un montage de circuits de codage, couplé au montage de circuits de traitement, pour coder le signal en vue d'une transmission à un équipement d'utilisateur (UE), autrement dit pour utiliser le signal de référence soumis à formation de faisceau pour exécuter un mesurage de gestion de ressources radio. L'invention concerne également d'autres modes de réalisation.
PCT/US2017/061263 2016-11-14 2017-11-13 Configuration de mesurage de gestion de ressources radio WO2018089879A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201780062149.4A CN109804592B (zh) 2016-11-14 2017-11-13 用于无线电资源管理测量的配置的装置及计算机可读介质

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662421864P 2016-11-14 2016-11-14
US62/421,864 2016-11-14

Publications (1)

Publication Number Publication Date
WO2018089879A1 true WO2018089879A1 (fr) 2018-05-17

Family

ID=60480452

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/061263 WO2018089879A1 (fr) 2016-11-14 2017-11-13 Configuration de mesurage de gestion de ressources radio

Country Status (2)

Country Link
CN (1) CN109804592B (fr)
WO (1) WO2018089879A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020033688A1 (fr) * 2018-08-10 2020-02-13 Intel Corporation Techniques de mesure de rétroaction basée sur un intervalle dans un réseau cellulaire sans fil de nouvelle radio
WO2020036428A1 (fr) * 2018-08-13 2020-02-20 삼성전자 주식회사 Procédé de transmission de données non ip dans un réseau 5g
CN113228726A (zh) * 2019-03-29 2021-08-06 苹果公司 利用细波束信道状态信息进行新无线电辅小区激活
CN113273102A (zh) * 2019-01-11 2021-08-17 苹果公司 新无线电(nr)定位的资源分配、参考信号设计和波束管理
CN113330710A (zh) * 2019-02-01 2021-08-31 苹果公司 利用dft-s-ofdm波形对pdsch传输进行调度

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111181710B (zh) * 2019-12-31 2022-11-22 展讯通信(上海)有限公司 通信方法及装置
CN113965938B (zh) * 2020-07-02 2023-07-18 中国联合网络通信集团有限公司 切片业务系统及切片业务处理方法
CN115913288A (zh) * 2021-09-30 2023-04-04 大唐移动通信设备有限公司 波束测量方法、测量配置方法、装置、终端及网络设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014182383A1 (fr) * 2013-05-09 2014-11-13 Intel IP Corporation Communications de réseau de téléphonie mobile à entrée multiple sortie multiple
US20160309376A1 (en) * 2013-12-30 2016-10-20 Huawei Technologies Co., Ltd. Channel measurement method, cell handover method, related apparatus, and system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2984765B1 (fr) * 2013-04-10 2018-12-26 LG Electronics Inc. Procédé et appareil d'alignement de couches pour formation de faisceaux tridimensionnelle multi-couches dans un système de communication sans fil
US20150163036A1 (en) * 2013-12-11 2015-06-11 Nokia Solutions And Networks Oy High Resolution Channel Sounding for FDD Communications

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014182383A1 (fr) * 2013-05-09 2014-11-13 Intel IP Corporation Communications de réseau de téléphonie mobile à entrée multiple sortie multiple
US20160309376A1 (en) * 2013-12-30 2016-10-20 Huawei Technologies Co., Ltd. Channel measurement method, cell handover method, related apparatus, and system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NOKIA NETWORKS: "On RRM measurement enhancements for EBF/FD-MIMO", vol. RAN WG1, no. Fukuoka, Japan; 20150525 - 20150529, 24 May 2015 (2015-05-24), XP050970638, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20150524] *
NVIDIA: "On the need of RRM enhancements for FD-MIMO", vol. RAN WG1, no. Belgrade, Serbia; 20150420 - 20150424, 19 April 2015 (2015-04-19), XP050934615, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20150419] *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020033688A1 (fr) * 2018-08-10 2020-02-13 Intel Corporation Techniques de mesure de rétroaction basée sur un intervalle dans un réseau cellulaire sans fil de nouvelle radio
CN112567655A (zh) * 2018-08-10 2021-03-26 苹果公司 用于新无线电无线蜂窝网络中的基于间隙的反馈测量的技术
CN112567655B (zh) * 2018-08-10 2022-12-23 苹果公司 用于新无线电无线蜂窝网络中的基于间隙的反馈测量的技术
US11570649B2 (en) 2018-08-10 2023-01-31 Apple Inc. Techniques for gap-based feedback measurement in new radio wireless cellular network
US11937116B2 (en) 2018-08-10 2024-03-19 Apple Inc. Techniques for gap-based feedback measurement in new radio wireless cellular network
WO2020036428A1 (fr) * 2018-08-13 2020-02-20 삼성전자 주식회사 Procédé de transmission de données non ip dans un réseau 5g
CN113273102A (zh) * 2019-01-11 2021-08-17 苹果公司 新无线电(nr)定位的资源分配、参考信号设计和波束管理
CN113330710A (zh) * 2019-02-01 2021-08-31 苹果公司 利用dft-s-ofdm波形对pdsch传输进行调度
CN113330710B (zh) * 2019-02-01 2024-05-03 苹果公司 利用dft-s-ofdm波形对pdsch传输进行调度
CN113228726A (zh) * 2019-03-29 2021-08-06 苹果公司 利用细波束信道状态信息进行新无线电辅小区激活

Also Published As

Publication number Publication date
CN109804592A (zh) 2019-05-24
CN109804592B (zh) 2021-10-15

Similar Documents

Publication Publication Date Title
US10716096B2 (en) Enabling network slicing in a 5G network with CP/UP separation
EP3451553B1 (fr) Mécanismes pour surveiller un canal de commande physique de liaison descendante comportant un espace de recherche commun et un espace de recherche spécifique d&#39;un équipement utilisateur dans un système à formation de faisceau
US11871291B2 (en) Data forwarding tunnel establishment between two user plane functions in fifth generation
US11291030B2 (en) Sidelink control information for vehicle-to-vehicle communications
US10749587B2 (en) Systems, methods and devices for using S-measure with new radio
US20190394834A1 (en) Measurement gap sharing
CN109804592B (zh) 用于无线电资源管理测量的配置的装置及计算机可读介质
US10979958B2 (en) Systems, methods, and apparatuses for providing and obtaining scheduling information for SIB1-BR during handover
EP3454477A1 (fr) Mesures d&#39;interférence dans de nouveaux systèmes radio
US10841808B2 (en) Apparatus and medium for enabling multi-carrier operation
US11018903B2 (en) Channel estimation using a plurality of beamformed reference signals
US10631256B2 (en) Power headroom of grantless uplink
US11502805B2 (en) Resource mapping schemes for channel state information reporting on new radio physical uplink control channel
US11838839B2 (en) V2X policy and parameters provisioning to user equipment by a policy and control function
US11109355B2 (en) Interruption and delay for V2X sidelink carrier aggregation
CN110582121A (zh) 用于ue请求ue策略初始配给或更新的解决方案
WO2019032532A1 (fr) Nouvelle gestion d&#39;enregistrement radio
WO2018085713A2 (fr) Sélection d&#39;accès initial et de mode dans des réseaux d&#39;évolution à long terme (lte) évolués
US20200220673A1 (en) Frame structure for unlicensed narrowband internet-of-things system
US20190044810A1 (en) Channel whitelist and flexible frame design for enhanced machine-type communications systems in unlicensed spectrum
EP3834484A1 (fr) Procédés pour améliorer la gestion de transfert de session d&#39;unité de données de protocole dans un réseau d&#39;accès radio de prochaine génération

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: 17805071

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17805071

Country of ref document: EP

Kind code of ref document: A1