[go: up one dir, main page]

WO2025122036A1 - Gestion combinée de faisceaux d'émission-réception - Google Patents

Gestion combinée de faisceaux d'émission-réception Download PDF

Info

Publication number
WO2025122036A1
WO2025122036A1 PCT/SE2023/051221 SE2023051221W WO2025122036A1 WO 2025122036 A1 WO2025122036 A1 WO 2025122036A1 SE 2023051221 W SE2023051221 W SE 2023051221W WO 2025122036 A1 WO2025122036 A1 WO 2025122036A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
reception
beams
determined
elements
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/SE2023/051221
Other languages
English (en)
Inventor
Mårten SUNDBERG
Adrian GARCIA RODRIGUEZ
Tamas Borsos
András RÁCZ
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/SE2023/051221 priority Critical patent/WO2025122036A1/fr
Publication of WO2025122036A1 publication Critical patent/WO2025122036A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection

Definitions

  • the present disclosure relates generally to communications, and more particularly to communication methods and related user equipment and network nodes performing beam management.
  • New Radio As compared to previous generation of wireless networks, is the ability to operate in higher frequencies (e.g., above 10 gigahertz (GHz)).
  • GHz gigahertz
  • the available large transmission bandwidths in these high frequency ranges can potentially provide large data rates.
  • pathloss and penetration loss increase.
  • highly directional beams are required to focus the radio transmitter energy in a particular direction on the receiver.
  • large radio antenna arrays - at both the receiver side and the transmitter side - are needed to create such highly directional beams.
  • Beam management procedures in NR are defined by a set of Layerl/Layer2 (L1/L2) procedures that establish and maintain a suitable beam pair for both transmitting and receiving data.
  • a beam management procedure can include sub procedures such as beam determination, beam measurements, beam reporting, and beam sweeping.
  • P1/P2/P3 beam management procedures can be performed to overcome the challenges of establishing and maintaining the beam pairs when, for example, a UE moves or some blockage in the environment requires changing the beams.
  • a Pl procedure may be used to enable UE measurement on different transmission-reception point (TRP) transmission (Tx) beams to support selection of TRP Tx beams/UE reception (Rx) beam(s).
  • TRP transmission-reception point
  • Rx UE reception
  • gNB Next Generation Node B
  • SSB synchronization signal block
  • Each UE measures the signal quality on the corresponding SSB signals to detect and select the appropriate SSB beam. Random access is then initiated using the random access channel (RACH) resources determined by the selected SSB.
  • RACH random access channel
  • the network node infers which SSB beam was selected by the UE without any explicit signaling.
  • it typically includes an intra/inter-TRP Tx beam sweep from a set of different beams.
  • it usually includes a UE Rx beam sweep from a set of different beams.
  • a P2 procedure may be used to enable UE measurement on different TRP Tx beams to possibly change inter/intra-TRP Tx beam(s).
  • the network node can use the SSB beam as an indication of which (narrow) Channel Status Information-Reference Signal (CSI-RS) beams to try, i.e., a candidate set of narrow CSI-RS beams for beam management is based on the best SSB beam.
  • CSI-RS Channel Status Information-Reference Signal
  • the UE measures the Reference Signal Received Power (RSRP) and reports the result to the network. If the network node receives a CSI-RSRP report from the UE where a new CSI-RS beam is better than the old beam used to transmit physical downlink control channel (PDCCH)/physical downlink shared channel (PDSCH), the network updates the serving beam for the UE accordingly and can modify the candidate set of CSI-RS beams.
  • PDCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • the network node can also instruct the UE to perform measurements on SSBs. If the network node receives a report from the UE where a new SSB beam is better than the previous best SSB beam, a corresponding update of the candidate set of CSI-RS beams for the UE may be needed.
  • the P2 procedure may be performed on a smaller set of beams for beam refinement as compared to the Pl procedure.
  • the P2 procedure can be a special case of the Pl procedure.
  • the gNB configures the UE with different CSI-RSs and transmits each CSI-RS on a corresponding beam.
  • the UE measures the quality of each CSI-RS beam on its current Rx beam and sends feedback about the quality of the measured beams. Thereafter, based on this feedback, the gNB will decide and possibly indicate to the UE which beam will be used in future transmissions.
  • a P3 procedure may be used to enable UE measurement on the same TRP Tx beam to change the UE Rx beam in the event the UE uses beamforming.
  • the UE is configured with a set of reference signals. Based on measurements, the UE determines which Rx beam is suitable to receive each reference signal in the set. The network then indicates which reference signals are associated with the beam that will be used to transmit PDCCH/PDSCH, and the UE uses this information to adjust its Rx beam when receiving PDCCH/PDSCH.
  • the P3 procedure can be used by the UE to find the best Rx beam for a corresponding Tx beam.
  • the gNB keeps one CSI-RS Tx beam at a time, and the UE performs the sweeping and measurements on its own Rx beams for that specific Tx beam. The UE then finds the best corresponding Rx beam based on the measurements and will use that beam in the future for reception when the gNB indicates the use of that Tx beam.
  • a UE can be configured to report RSRP or/and Signal to Interference and Noise Ratio (SINR) for each beam up to four beams, either on CSI-RS or SSB.
  • SINR Signal to Interference and Noise Ratio
  • the UE measurement reports can be sent over either PUCCH or PUSCH to the network node, e.g., gNB.
  • the disclosed subject matter includes a method performed by a user equipment (UE) in a network.
  • the method includes coordinating, with a network node, a configuration to be utilized for reference signal measurements conducted by the UE, performing reference signal measurements in accordance with the configuration, over elements in a set of reception beam patterns determined by the UE, each element in the set of reception beam patterns corresponding to an amplitude and phase weight for each of the UE receiving antenna elements, and providing, to the network node, information indicating one or more of the elements in the set of reception beam patterns and respective reference signal measurement results.
  • UE user equipment
  • the method further includes receiving, from the network node, information indicating a set of preferred reception (Rx) beams determined by the network node based on the provided information, and selecting, by the UE, a set of Rx beams from among the indicated set of preferred Rx beams for establishing a communications session with the network node.
  • Rx preferred reception
  • the disclosed subject matter includes a UE that comprises a processing circuitry and memory, which is coupled with the processing circuitry.
  • the memory includes instructions that when executed by the processing circuitry causes the UE to perform steps including: coordinating, with a network node, a configuration to be utilized for reference signal measurements conducted by the UE, performing reference signal measurements in accordance with the configuration, over elements in a set of reception beam patterns determined by the UE, each element in the set of reception beam patterns corresponding to an amplitude and phase weight for each of the UE receiving antenna elements, and providing, to the network node, information indicating one or more of the elements in the set of reception beam patterns and respective reference signal measurement results.
  • the steps further include receiving, from the network node, information indicating a set of preferred Rx beams determined by the network node based on the provided information, and selecting, by the UE, a set of Rx beams from among the indicated set of preferred Rx beams for establishing a communications session with the network node.
  • the disclosed subject matter includes a computer program comprising program code to be executed by processing circuitry of a UE, whereby execution of the program code causes the UE to perform operations comprising: coordinating, with a network node, a configuration to be utilized for reference signal measurements conducted by the UE, performing reference signal measurements in accordance with the configuration, over elements in a set of reception beam patterns determined by the UE, each element in the set of reception beam patterns corresponding to an amplitude and phase weight for each of the UE receiving antenna elements, and providing, to the network node, information indicating one or more of the elements in the set of reception beam patterns and respective reference signal measurement results.
  • the operations further include receiving, from the network node, information indicating a set of preferred Rx beams determined by the network node based on the provided information, and selecting, by the UE, a set of Rx beams from among the indicated set of preferred Rx beams for establishing a communications session with the network node.
  • the disclosed subject matter includes a method performed by a network node that comprises coordinating, with a UE a configuration to be utilized for reference signal measurements conducted by the UE, and receiving, from the UE, in accordance with the configuration, information indicating one or more of elements in a set of reception beam patterns and respective reference signal measurement results, each element in the set of reception beam patterns corresponding to an amplitude and phase weight for each of the UE receiving antenna elements determined by the UE.
  • the method further includes determining, a set of transmissionreception (Tx-Rx) beam pairs based on the received information and a set of transmission beam patterns determined by the network node, each element in the set of transmission beam patterns corresponding to an amplitude and phase weight for each of the network node transmitting antenna elements, and providing, to the UE, information indicating a set of preferred reception (Rx) beams for establishing a communications session with the UE, the set of preferred Rx beams being determined by the network node based on the determined set of Tx-Rx beam pairs.
  • Tx-Rx transmissionreception
  • the disclosed subject matter includes a network node comprising processing circuitry and memory coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node to perform steps including: coordinating, with a UE a configuration to be utilized for reference signal measurements conducted by the UE, and receiving, from the UE, in accordance with the configuration, information indicating one or more of elements in a set of reception beam patterns and respective reference signal measurement results, each element in the set of reception beam patterns corresponding to an amplitude and phase weight for each of the UE receiving antenna elements determined by the UE.
  • the method further includes determining, a set of transmissionreception (Tx-Rx) beam pairs based on the received information and a set of transmission beam patterns determined by the network node, each element in the set of transmission beam patterns corresponding to an amplitude and phase weight for each of the network node transmitting antenna elements, and providing, to the UE, information indicating a set of preferred reception (Rx) beams for establishing a communications session with the UE, the set of preferred Rx beams being determined by the network node based on the determined set of Tx-Rx beam pairs.
  • Tx-Rx transmissionreception
  • the disclosed subject matter includes a computer program comprising program code to be executed by processing circuitry of a network node, whereby execution of the program code causes the network to perform operations comprising: coordinating, with a UE a configuration to be utilized for reference signal measurements conducted by the UE, and receiving, from the UE, in accordance with the configuration, information indicating one or more of elements in a set of reception beam patterns and respective reference signal measurement results, each element in the set of reception beam patterns corresponding to an amplitude and phase weight for each of the UE receiving antenna elements determined by the UE.
  • the method further includes determining, a set of Tx-Rx beam pairs based on the received information and a set of transmission beam patterns determined by the network node, each element in the set of transmission beam patterns corresponding to an amplitude and phase weight for each of the network node transmitting antenna elements, and providing, to the UE, information indicating a set of preferred Rx beams for establishing a communications session with the UE, the set of preferred Rx beams being determined by the network node based on the determined set of Tx-Rx beam pairs.
  • the disclosed subject matter affords many technical advantages and advancements over the current state of the art. For example, reduced beam scanning time and reduced reference signal transmissions and resources used when both network side and UE side beamforming is applied to find the best Tx-Rx beam pair. It is noted that determining the best Tx-Rx beam pair is not guaranteed in general NR beam management procedures due to its sequential nature, i.e., the selection of the best Tx beam is not guaranteed in P2 protocol due to the choice being performed based on an Rx beam that is potentially different than that finally chosen in P3.
  • Figure 1 is a transmission beamforming matrix system model that does not execute any reception beamforming operations
  • Figure 2 is an exemplary matrix system model that performs transmission and reception beamforming operations according to some embodiments
  • Figure 3 is an exemplary matrix system model with reception beamforming posed as a compressed sensing problem according to some embodiments
  • Figure 4 is an exemplary signaling diagram for conducting reception beamforming with a sparse decoding module located at a base station according to some embodiments
  • Figure 5 is a flow chart illustrating example operations for performing reception beamforming according to a first embodiment
  • Figure 6 is an exemplary signaling diagram for conducting j oint optimization of beam-pairs between the base station and user equipment where the sparse decoding module resides at the user equipment according to some embodiments;
  • Figure 7 is a flow chart illustrating example operations for performing reception beamforming according to a second embodiment
  • Figure 8 is an exemplary signaling diagram for conducting j oint optimization of beam-pairs between the base station and user equipment where the sparse decoding module resides at the base station according to some embodiments;
  • Figure 9A is a flow chart illustrating example operations performed at a UE according to a third embodiment
  • Figure 9B is a flow chart illustrating example operations performed at a network node according to a third embodiment
  • Figure 10 is a block diagram of a communication system in accordance with some embodiments.
  • Figure 11 is a block diagram of a user equipment in accordance with some embodiments
  • Figure 12 is a block diagram of a network node in accordance with some embodiments
  • Figure 13 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments.
  • Figure 14 is a block diagram of a virtualization environment in accordance with some embodiments.
  • a beam management solution currently utilized is based on compressed sensing, which optimizes beam patterns for a fast scanning of beams typically over a certain geographical location.
  • a beam pattern may refer to any wireless signal and/or radiation shape (e.g., single beam or multi-beam) generated by one or more beamforming techniques via at least one antenna.
  • Compressed sensing is a signal processing technique which says that if a signal is sparse in some domain, then the signal can be fully reconstructed from a fewer number of measurement samples than what would be required by sampling theory. Being sparse means that the signal contains a lot of zero elements when it is expressed in a certain domain or basis.
  • a signal can be sparse in the Fourier domain containing only a few non-zero Fourier components or an image can be sparse when transformed into the Discrete Fourier or Discrete Cosine Transform domain.
  • compressed sensing for beam sweeping can be used such that the best beam directions from all possible APs can be determined from a few transmissions without requiring a full scan search.
  • the APs can transmit the same reference signal in all directions using the same time frequency resource and vary the transmit power allocations in a few combinations.
  • the UE needs to measure only the composite received signal from all directions, it does not have to identify beams individually.
  • Such an approach contrasts with the conventional way of performing beam management where a set of spatially directive beams are defined and where the beams are sequentially scanned irrespective of geographical location (as described above with respect to Pl, P2, and/or P3 procedures).
  • the optimization in the aforementioned beam management solution based on compressed sensing instead lies in finding a pattern of beams to be used by the base station transmitter and/or finding an area/site- specific set of beams patterns.
  • measurement vector 101 can be determined from a combination of i) the allocated power in the different beam directions (1, ... , ) as represented by power allocation matrix 102 (e.g., matrix P Tx ) and the associated link gain represented by beam gain vector 103 (e.g., vector g).
  • the disclosed subject matter enables the use of Rx beamforming such that beam patterns are optimized to allow an accurate and prompt determination of the beams to be used for communication using compressed sensing and/or sparse decoding, for example.
  • the enabling of Rx beamforming can be achieved by various embodiments.
  • the Rx beamforming is not part of the sparse decoding performed at the base station but is still incorporated in a process to i) determine the best (set of) Tx beam(s) to be used by the base station for an intended user equipment, and ii) determine the Rx beam weights to be used receiving those (set of) Tx beam(s).
  • the Rx beamforming is included in the sparse decoding processing that determines the best (set of) Tx-Rx beam pair(s) to be used by the base station and the intended user equipment, respectively. It is noted that although compressed sensing is described as a method for tracking the beams in the present disclosure, the scope of the disclosed subject matter is not limited to that specific algorithm being used at the base station and/or UE. [0040] In various embodiments, the disclosed subject matter utilizes both transmission beam patterns (BPT) and reception beam patterns (BPR). As used herein, BPT may be used to refer to a set of beam weights (applied over time) that is used by the base station transmitter.
  • BPT transmission beam patterns
  • BPR reception beam patterns
  • Each element in the BPT corresponds to an amplitude and phase weight for each of the base station transmitting antenna elements.
  • BPR may be used to refer to a set of beam weights (applied over time) that is used by the UE receiver.
  • Each element in the BPR corresponds to an amplitude and phase weight for each of the UE receiving antenna elements.
  • a sparse decoding module refers to an artificial intelligence/machine learning (AI/ML) module that is configured to perform sparse decoding operations that determine the (set of) Tx and/or Rx beam(s) (e.g., Tx-Rx beam pairs in case of both Tx and Rx being part of the sparse decoding) based on measurements made by a receiving node and knowing the beam pattern (BP) used (i.e., at the Tx and/or Rx entity).
  • BP beam pattern
  • MM measurement module
  • MM is referred to herein as the module in the receiving node (e.g., UE) that is configured to perform signal-related measurements.
  • a system of the disclosed subject matter may be mathematically represented as a plurality of matrix operations.
  • Figure 2 is an exemplary matrix system model that performs transmission and reception beamforming operations according to some embodiments.
  • measurements may be performed over the different Tx beam patterns (1,... JV/) and Rx beam patterns (1,... ,K) collected in measurement matrix 201, instead of a measurement vector.
  • measurement matrix 201 is equal to the product of a Tx power allocation matrix 202 (PT X ), a Tx-Rx beam gain matrix 203, and Rx power allocation matrix 204 (PR X ).
  • the measurement matrix 201 includes beam measurement values for all the combinations of Tx beam patterns and Rx beam patterns.
  • Tx beamforming power allocation matrix 202 (PT X ) includes the power values for each of the Tx beam patterns (i.e., beam directions) originating from the base station antennas.
  • matrix 202 is generated by a beam path transmitter module at the base station.
  • Tx-Rx beam gain matrix 203 includes the gain values for all the combinations of Tx beam directions (from the network node) matched with Rx beam transmissions (at the UE).
  • Tx-Rx beam gain matrix 203 is generated by the SDM (residing either at the network node or at the UE depending on the embodiment).
  • the Rx beamforming power allocation matrix 204 is generated by a UE receiver module at the UE.
  • matrix 204 comprises BPR that includes Rx beam power/gain values for each of the Rx beam patterns that are received in “L” different beam directions at the UE.
  • the measurement matrix 201 and the gain matrix 203 may be flattened to vectors, thereby executing a Kronecker product between the Tx beam pattern and Rx beam pattern.
  • y' PRX+TX ⁇ g' PRX®PTX
  • Figure 3 illustrates exemplary flattened measurement vector 301 (y') and Tx beam gain vector 303 (g').
  • Figure 3 depicts a system model with Rx beamforming posed as a compressed sensing (CS) problem.
  • CS compressed sensing
  • the system model depicted in Figure 3 further includes a power allocation matrix 302 (PRX+TX), where PTX defines the BPT and PRX defines the BPR.
  • the disclosed subject matter may be implemented in accordance to at least the three embodiments described herein. Although only three exemplary embodiments are described, additional embodiments may be utilized without departing from the scope of the present disclosure.
  • the network node e.g., a base station
  • the network node includes an SDM (e.g., SDM 1250 in Figure 12) that allows the network node to perform and/or execute sparse decoding processing that determines the best (set of) beam pairs to use.
  • the UE determines proprietary BPR that can be used to determine the best/preferred Rx beam sets.
  • the network node may use its BPT to transmit a set of beam patterns to the UE.
  • measurement data refers to beam pattern measurements.
  • the network node utilizes the measurement data to determine the best one or more Tx beams (e.g., the best set of Tx beams) to serve and/or establish a wireless connection with the UE.
  • the UE may be configured in a proprietary manner to determine both i) the set size of the set of reception beam pattern the UE wants to apply and ii) the specific Rx beam weight values (i. e. , defining the proprietary BPR).
  • Figure 4 is an exemplary signaling diagram for conducting reception beamforming by a network node provisioned with an SDM according to a first embodiment. Specifically, Figure 4 depicts the signaling communications conducted between an exemplary network node 410 (e.g., a base station, such as a gNB) and a UE 420 (e.g., any computing device associated with a mobile subscriber user).
  • an exemplary network node 410 e.g., a base station, such as a gNB
  • UE 420 e.g., any computing device associated with a mobile subscriber user.
  • step 401 involves the network node 410 and UE 420 coordinating with each other to determine the radio resources that will be used for the beam measurements.
  • the UE may be configured to utilize proprietary BPR.
  • proprietary BPR refers to receive beamforming weight data that is owned entirely by the user, operator, and/or the UE manufacturer.
  • the network node is using BPT to transmit a set of beam patterns to the UE.
  • Measurements from the UE are used by the network node and/or its SDM to determine the best Tx beam(s) (e.g., the best set of Tx beams) to serve the UE.
  • the UE proprietarily determines both the set size of receive beam weights the UE wants to apply as well as the specific Rx beam weight values.
  • step 401 may include the coordination between network node 410 and UE 420 to determine and/or define the configuration data (e.g., radio resources and/or conditions) to be used for measurements.
  • step 401 may include a number of sub-steps including, but not limited to: sub-step 401.1) coordination of a set of radio resources to measure on, sub-step 401.2) coordination of a set size of BPT(A ), wherein M refers to the number of Tx beam patterns, sub-step 401.3) coordination of a set size of BPR(X), wherein K refers to the number of Rx beam patterns, sub-step 401.4) coordination of information defining that each element of the BPT maps to time and frequency of the radio resources, sub-step 401.5) coordination of the conditions under which the base station is allowed to change and/or modify the BPT, sub-step 401.6) coordination of a measurement report configuration, sub-step 401.7) coordination of criteria on how elements in BPR should be selected for the transmission in Step 404 (
  • the set size for BPT(A ) may, for example, be included in and/or provided by the UE capability indication and/or a radio resource control (RRC) configuration.
  • the BPT(A ) can also be provided by the specification based on other UE capabilities (e.g., the support of the beam management procedure and/or an indication of an antenna configuration supported). It may alternatively be dynamically sent by the UE via uplink control information or a medium access control (MAC) control element (CE). This may be particularly useful when adapting the size of BPR over time (e.g., reducing the measurement time by a smaller size if the channel is seen as sparse in certain directions).
  • MAC medium access control
  • Knowing the set size(s) of the BPR at the base station will (apart from being required to determine the beam weight and/or element in the BPR for use by the UE) allow the base station to adapt the number of reference signal (RS) resources (e.g., SSB signals and/or CSI-RSs) scheduled for the UE.
  • RS reference signal
  • such conditions for sub-step 401.5 may, for example, be based on specification text where the configuration data can be related to slot boundaries, or multiples thereof (e.g. every x th number of slot, radio frame/super frame/hyper frame boundaries, etc.).
  • the conditions may be communicated by the network node to the UE through control signaling, (e.g., such as master information block (MIB)-system information block (SIB) signaling) or including the configuration conditions as part of the RRC measurement configuration or reference signal configuration.
  • MIB master information block
  • SIB system information block
  • sub-step 401.6 includes a measurement report configuration.
  • the criteria for sub-step 401.7 may include i) selecting the beam weights or element(s) in the BPR that correspond to the largest single RSRP measurement value across all BPT elements, or ii) selecting the element(s) in the BPR with the largest value computed after aggregating — for a given BPR element — all the RSRP measurements performed for the different BPT elements.
  • sub-step 401.8 includes a criteria on which beam elements in the BPR should be selected for reporting in the transmission in step 404, based on the measurements performed in step 403 (optional). Further, the criteria of selection can be the same as described above in sub-step 401.7.
  • the UE 420 determines the BPR, which includes both the set size (K) and the beam weights of each element in the set.
  • K set size
  • the BPR determination in this embodiment is proprietary and as such is not limited to, for example, simply identifying a set of distinct beam directions that are sequentially swept and/or a set of generic beam patterns.
  • Such generic beam patterns may, for example, be constructed based on historical data experienced by the UE. For example, if the UE 420 has experienced one or more beams concentrated in a certain direction, the UE 420 may focus the elements in the BPR on and/or toward those directions.
  • the UE 420 may perform M x K beam measurements.
  • the overhead associated with finding the best Tx-Rx beam pairs can be significantly reduced since M may be substantially smaller than the number of measurements performed in processes Pl and P2, and K may be substantially smaller than the number of measurements performed in P3.
  • each of M and K may be substantially smaller the aforementioned number of measurements because the disclosed method can exploit the sparsity in the channel conditions in a specific geographical area, which leads to a reduced number of measurements required.
  • the UE 420 reports the M x K beam measurements (e.g., all or a sub-set of the measurements) to the network node 410 via a measurement report.
  • the measurement report indicates to the network node 410 which of the measurements performed corresponds to which set of radio resources used (or alternatively, which element in the BPT that was measured) and/or which element in the BPR that was used for each respective measurement.
  • the indication of elements in BPT/BPR reported may be explicitly indicated in the measurement report (e.g., indicating which measurement value corresponds to which combination of elements in the BPT and BPR), or given by the measurement report configuration (sub-step 401.6).
  • the measurement report is sent using either LI control information (e.g., UCI), a MAC CE, or an RRC message.
  • a sub-set of measurements is reported, such a sub-set can be determined based on certain criteria defined by sub-step 401.8, or left to implementation (i.e., using the same criteria as in sub-step 401.8, but not necessarily communicated between the UE 420 and the network node 410).
  • the UE 420 may assume an omni-directional type of Tx beam for transmitting the measurement report, assuming there is no knowledge of appropriate directions for communication with the network node 410.
  • the beam directions of the Tx beam(s) may correspond to the strongest measured beams in the BPR (e.g., assuming beam correspondence exists between the Tx beams and Rx beams).
  • the UE 420 will indicate the beam element(s) in the BPR that is used to transmit the measurement report.
  • the selection of Rx beam(s) at the network node 410 may be based on an earlier communication between UE 420 and network node 410 (e.g., initial access), or based on earlier established Tx-Rx beam pairs that were identified and used for communication.
  • step 405 the network node 410 determines i) the set of Tx beams that will be used for communicating with UE 420 and ii) the beam element(s) in the BPR that correspond to the aforementioned determined/selected set of Tx beams.
  • sparse decoding is performed by the network node for each received set of measurement data (e.g., in measurement report of step 404) for a given beam element included in the BPR.
  • step 406 the beam element(s) in the BPR corresponding to the set of Tx beams that has been selected for use are transmitted to the UE 420. In some embodiments, such transmission will be performed only if the beam element(s) in the BPR correspond to the set of Tx beams that have been determined for use by the network node 410 are different from the beam element(s) in the BPR used to transmit the information in Step 404 (and/or in accordance with sub-step 401.7).
  • the preferred set of Tx beams may be transmitted via LI control signaling (e.g., downlink control information, DCI) where the indication can either be UE-specific or group-common (e.g., the same message addressing multiple UEs).
  • the indication may also be transmitted using a MAC CE or RRC message, or included in a system information message monitored by UEs operating in the RRC_CONNECTED mode.
  • the messages need to be associated with a (temporary) UE ID, such as a Radio Network Temporary Identifier (RNTI), to identify the UE 420.
  • RNTI Radio Network Temporary Identifier
  • Such a UE ID can be either i) implicitly communicated through a bitwise ‘XOR’ operation over the cyclic redundancy check (CRC) part of the information message (if the message is UE-specific) or ii) explicitly indicated in the message (e.g., for group-common DCI).
  • the messages can be periodically scheduled. This may be achieved through the abovementioned system information. In such an embodiment, this periodic scheduling may be associated with a monitoring requirement at the UE 420 (e.g., that the UE is required to monitor and/or receive the message at least every ‘x’ milliseconds).
  • the message may also be aperiodically triggered, as exemplified by the abovementioned DCI.
  • the indication of the element(s) in the BPR can be communicated through the use of a logical index (e.g., indicating one out of 0, ... , N-l, where N is the size of the BPR).
  • the Tx / Rx beam(s) to be used for this communication is determined as described in Step 404.
  • the UE 420 will know which element(s) of the BPR the UE should use for further communication with the network node 410.
  • the UE 420 may for sub-sequent measurements focus the BPR in such directions and/or lower the number of elements in the BPR (i.e., thereby impacting the amount of measurements required; see sub-step 401.3).
  • Figure 5 is a flow chart illustrating a method 500 depicting exemplary operations for performing reception beamforming according to a first embodiment.
  • the steps of method 500 may be implemented as a software program or algorithm that is executed by the processing circuitry of a UE.
  • the method 500 includes coordinating, with a network node, configurations and conditions to be utilized for reference signal measurements conducted between the UE and the network node.
  • the configurations include a set size of a number of beam weights applied to the BPR and/or a set size indicative of the plurality of beam pattern elements.
  • the configurations include conditions that specify instances when the network node is permitted to change the BPT.
  • the configurations include criteria that specify a manner in which beam pattern elements in the BPR are selected for transmission to the network node.
  • the configurations include criteria that specify which beam pattern elements in the BPR are selected for reporting in the transmission to the network node.
  • the method 500 includes performing, by a measurement module residing at the UE, transmission-reception beam pair measurements for combinations comprising pairings of i) beam pattern elements in a BPT transmitted to the UE and ii) beam pattern elements in a BPR determined by the UE.
  • the method 500 includes providing, to the network node, a measurement report including beam pair measurement values corresponding to combinations of pairings of a plurality of beam pattern elements in a BPT determined by the UE and a plurality of beam pattern elements in a BPR that is determined and transmitted by the UE.
  • the method 500 includes receiving, from the network node, one or more determined beam pattern elements in the BPR that respectively corresponds to one or more transmission beams selected by the network node based on the measurement report.
  • the network node includes a sparse decoding module, SDM, that is configured to utilize the measurement report to select i) the one or more transmission beams for establishing a communications link with the UE and ii) the one or more determined beam patterns elements in the BPR corresponding to the selected one or more transmission beams.
  • the network node is configured to perform a sparse decoding operation on each of the beam pair measurement values in the measurement report received from the UE.
  • the network node applies a compressed sensing operation to each of the beam pair measurement values to determine the one or more transmission beams selected by the network node.
  • the disclosed subject matter may involve conducting joint optimization of beam-pairs between a base station and the user equipment.
  • both the BPT and the BPR are used in the sparse decoding to determine a set of best Tx-Rx beam pairs from a small set of measurements.
  • FIG. 6 is an exemplary signaling diagram for conducting j oint optimization of beam-pairs between a base station and user equipment where the SDM resides at the UE according to a second embodiment.
  • the first three steps e.g., Steps 601-603
  • the first three steps depicted in Figure 6 are identical to the first three steps (e.g., steps 401-403) depicted in Figure 4.
  • network node 610 and UE 620 in Figure 6 are similar to and/or the same as network node 410 and UE 420 represented in Figure 4, respectively.
  • Figure 6 depicts a step 604 where the network node 610 sends the BPT to the UE 620.
  • step 604 may take place prior to step 601 and/or 602.
  • the BPT can be transmitted using an RRC message or MAC CE message.
  • the BPT may be communicated to the UE 620 using a system information message that is being monitored by one or more UEs operating in RRC CONNECTED mode. Any of these types of messages can be periodically scheduled by the network node 610. In some embodiments, this may be achieved through the abovementioned system information and sent to all UEs monitoring the system information.
  • the periodic scheduling can be associated with a monitoring requirement at the UE 620.
  • the UE 620 can be required to acquire the BPT not earlier than ‘x” milliseconds prior to performing Step 607.
  • the UE 620 may know/determine the validity of an earlier measured BPT and would not need to re-acquire such BPT, assuming the currently used BPT has already been acquired.
  • the BPT can be communicated as a two-dimensional structure where one dimension relates to the power allocation per beam direction, and the second dimension relates to the different elements in the BPT set (e.g., each containing a unique distribution of beam power allocation).
  • the Tx-Rx beam pair(s) to be used for this communication may be determined as described in step 404 as described above with respect to Figure 4.
  • step 605 the UE 620 determines the set of Tx-Rx beam pairs using the known BPT (previously received in step 604), the BPR (e.g., determined in step 602), and measurements performed (e.g., in step 603).
  • a preferred set of Tx beams are reported by UE 620 to the network node 610.
  • Such an indication may be transmitted through LI control signaling (e.g., UCI).
  • the indication may be transmitted using a MAC CE or RRC message.
  • the indication of the Tx beam(s) can also be communicated via the use of a logical index (e.g., indicating one out of 0,... , N-l where N is the number of beam directions in the BPT).
  • step 607 the network node 610 determines the set of Tx beams that will be used for communicating with the UE 620.
  • Figure 7 is a flow chart illustrating a method 700 that includes example operations for performing reception beamforming according to a second embodiment .
  • the steps of method 700 may be implemented as a software program or algorithm that is executed by the processing circuitry of a UE.
  • the method 700 includes coordinating, with a network node, configurations and conditions to be utilized for reference signal measurements conducted between the UE and the network node.
  • the configurations include a set size of a number of beam weights applied to the BPR and/or a set size indicative of the plurality of beam pattern elements.
  • the configurations include conditions that specify instances when the network node is permitted to change the BPT.
  • the configurations include criteria that specify a manner in which beam pattern elements in the BPR are selected for transmission to the network node.
  • the method 700 includes performing, by a measurement module at the UE, transmission-reception beam pair measurements for combinations comprising pairings of i) beam pattern elements in a BPT transmitted to the UE and ii) beam pattern elements in a BPR determined by the UE.
  • the method 700 includes utilizing, a SDM (residing in the UE) to perform a sparse decoding operation on each of a plurality of beam pair measurement values corresponding to the combinations of the pairings of the beam pattern elements in the BPT and the respective beam pattern elements in the BPR.
  • the UE is configured to utilize the measurement report to select i) the one or more transmission beams for establishing a communications link with the net and ii) the one or more determined beam patterns elements in the BPR corresponding to the selected one or more transmission beams.
  • the UE is configured to perform a sparse decoding operation on each of the beam pair measurement values in the measurement report received from the UE.
  • the UE applies a compressed sensing operation to each of the beam pair measurement values to determine the one or more transmission beams selected by the network node.
  • the method 700 includes providing, to the network node, an identification of one or more transmission beams designated as preferred transmission beams selected by the UE, wherein the network node is configured enabled to select at least one of the preferred transmission beams to establish a communication session with the UE.
  • Figure 8 is an exemplary signaling diagram for conducting j oint optimization of beam-pairs between the base station and user equipment where the sparse decoding module resides at the base station according to a third embodiment.
  • the first three steps e.g., Steps 801-803 depicted in Figure 8 are identical to the first three steps (e.g., steps 401-403) depicted in Figure 4.
  • network node 810 and UE 820 in Figure 8 are similar to and/or the same as network node 410 and UE 420 in Figure 4, respectively.
  • step 804 the UE 820 sends the BPR and a measurement report to the network node 810 (note: this step may take place prior to step 803 in some instances).
  • the BPR may be transmitted using a RRC message, an LI control message (e.g., UCI), or a MAC CE message.
  • the BPR may be communicated as a two- dimensional structure where one dimension relates to the power allocation per beam direction, and the second dimension relates to the different elements in the BPR set (e.g., each containing a unique distribution of beam power allocation).
  • the Tx-Rx beam pairs (s) to be used for this communication is determined as described in step 404 of Embodiment 1.
  • step 805 the network node 810 determines a set of Tx-Rx beam pairs from the known BPT, the received BPR, and the measurements performed by the UE 820.
  • the preferred set of Rx beams are reported to the UE 820.
  • Such an indication may be transmitted through LI control signaling (e.g., DCI) where the indication can either be UE-specific or through group-based (e.g., the same message addressing multiple UEs).
  • the indication may also be transmitted using a MAC CE or RRC message, or included in a system information message monitored by UEs in RRC_CONNECTED mode.
  • the messages need to be associated with a (temporary) UE ID, e.g. RNTI, to identify the UE 820.
  • Such UE ID may be implicitly communicated through a bit-wise XOR operation over the CRC part of the information message (e.g., if the message is UE-specific) or explicitly indicated in the message (e.g., for group-common DCI).
  • the messages can be periodically scheduled. For example, this can be achieved through the abovementioned system information.
  • the periodic scheduling can be associated with a monitoring requirement at the UE 820 (e.g., the UE 820 is required to monitor and/or receive the message at least every “x” milliseconds).
  • the message can also be aperiodically triggered, as exemplified by the abovementioned DCI.
  • the indication of the beam(s) may be communicated through the use of a logical index (e.g., indicating one out of 0,... ,N-1 where N is the number of beam directions in the BPR).
  • the indication may also be reported using a ‘no change’ indication, which implies that the same Rx beam(s) in a previous report to the UE should be used by the network (e.g., saving uplink overhead).
  • the Tx-Rx beam pairs(s) that are used for this communication is determined as described in Step 404 of Embodiment 1.
  • Figure 9A is a flow chart illustrating a method 900 that includes example operations for performing reception beamforming at a UE according to a third embodiment.
  • the steps of method 900 may be implemented as a software program or algorithm that is executed by the processing circuitry of a UE.
  • the method 900 includes coordinating, with a network node, a configuration to be utilized for reference signal measurements conducted by the UE.
  • the configuration includes a measurement report configuration and a number of elements in the set of reception beam patterns.
  • the configuration includes conditions that specify instances when the network node is permitted to change a set of transmission beam patterns, each element in the set of transmission beam patterns corresponding to an amplitude and phase weight for each of the network node transmitting antenna elements.
  • the configuration includes criteria that specifies how the UE is to select the indicated one or more of the elements in the set of reception beam patterns.
  • the method 900 includes performing reference signal measurements in accordance with the configuration, over elements in a set of reception beam patterns determined by the UE, each element in the set of reception beam patterns corresponding to an amplitude and phase weight for each of the UE receiving antenna elements.
  • step 905 the method 900 includes providing (905), to the network node, information indicating one or more of the elements in the set of reception beam patterns and respective reference signal measurement results.
  • the method 900 includes receiving, from the network node, information indicating a set of preferred reception (Rx) beams determined by the network node based on the provided information.
  • the set of preferred Rx beams is determined by the network node using a sparse decoding operation.
  • the network node is configured to utilize the measurement report to select i) the one or more transmission beams for establishing a communications link with the net and ii) the one or more determined beam patterns elements in the BPR corresponding to the selected one or more transmission beams.
  • the network node is configured to perform a sparse decoding operation on each of the beam pair measurement values in the measurement report received from the UE.
  • the network node applies a compressed sensing operation to each of the beam pair measurement values to determine the one or more transmission beams selected by the network node.
  • the method 900 includes selecting, by the UE, a set of Rx beams from among the indicated set of preferred Rx beams for establishing a communications session with the network node.
  • Figure 9B is a flow chart illustrating a method 910 that includes example operations for performing reception beamforming at a network node according to the third embodiment.
  • the steps of method 910 may be implemented as a software program or algorithm that is executed by the processing circuitry of a network node.
  • step 911 the method 910 includes coordinating, with a UE, a configuration to be utilized for reference signal measurements conducted by the UE.
  • the method 910 includes receiving, from the UE, in accordance with the configuration, information indicating one or more of elements in a set of reception beam patterns and respective reference signal measurement results, each element in the set of reception beam patterns corresponding to an amplitude and phase weight for each of the UE receiving antenna elements determined by the UE.
  • the method 910 includes determining, a set of transmission-reception, Tx-Rx, beam pairs based on the received information and a set of transmission beam patterns determined by the network node, each element in the set of transmission beam patterns corresponding to an amplitude and phase weight for each of the network node transmitting antenna elements.
  • the method 910 includes providing, to the UE, information indicating a set of preferred reception, Rx, beams for establishing a communications session with the UE, the set of preferred reception, Rx, beams being determined by the network node based on the determined set of Tx-Rx beam pairs.
  • FIG. 10 shows an example of a communication system 1000 in accordance with some embodiments.
  • the communication system 1000 includes a telecommunication network 1002 that includes an access network 1004, such as a radio access network (RAN), and a core network 1006, which includes one or more core network nodes 1008.
  • the access network 1004 includes one or more access network nodes, such as network nodes 1010A and 1010B (one or more of which may be generally referred to as network nodes 1010), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 1010 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1012A, 1012B, 1012C, and 1012D (one or more of which may be generally referred to as UEs 1012) to the core network 1006 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1000 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 1000 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1012 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1010 and other communication devices.
  • the network nodes 1010 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1012 and/or with other network nodes or equipment in the telecommunication network 1002 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1002.
  • the core network 1006 connects the network nodes 1010 to one or more hosts, such as host 1016. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1006 includes one more core network nodes (e.g., core network node 1008) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1008.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • UPF User Plane Function
  • the host 1016 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 1000 of Figure 10 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G
  • the telecommunication network 1002 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1002 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1002. For example, the telecommunications network 1002 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 1012 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1004.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. , being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012C and/or 1012D) and network nodes (e.g., network node 1010B).
  • the hub 1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1014 may be a broadband router enabling access to the core network 1006 for the UEs.
  • the hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1014 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1014 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1014 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
  • the hub 1014 may have a constant/persistent or intermittent connection to the network node 1010B.
  • the hub 1014 may also allow for a different communication scheme and/or schedule between the hub 1014 and UEs (e.g., UE 1012C and/or 1012D), and between the hub 1014 and the core network 1006.
  • the hub 1014 is connected to the core network 1006 and/or one or more UEs via a wired connection.
  • the hub 1014 may be configured to connect to an M2M service provider over the access network 1004 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1010 while still connected via the hub 1014 via a wired or wireless connection.
  • the hub 1014 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1010B.
  • the hub 1014 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1010B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Figure 11 shows a UE 1100 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle- to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale
  • the UE 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/ output interface 1106, a power source 1108, a memory 1110, a communication interface 1112, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 1102 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1110.
  • the processing circuitry 1102 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 1102 may include multiple central processing units (CPUs).
  • the input/output interface 1106 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 1100.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 1108 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1108 may further include power circuitry for delivering power from the power source 1108 itself, and/or an external power source, to the various parts of the UE 1100 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1108.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1108 to make the power suitable for the respective components of the UE 1100 to which power is supplied.
  • the memory 1110 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1110 includes one or more application programs 1114, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1116.
  • the memory 1110 may store, for use by the UE 1100, any of a variety of various operating systems or combinations of operating systems.
  • memory 1110 may also be configured to store a sparse decoding module (SDM) 1115 and/or a measurement module 1117.
  • SDM sparse decoding module
  • UE may utilize its SDM 1115 to perform the sparse decoding functions described herein (when executed by processing circuitry 1102).
  • measurement module 1117 is configured to perform the beam-related measurement functions described herein (when executed by processing circuitry 1102).
  • the memory 1110 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card. ’
  • the memory 1110 may allow the UE 1100 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1110, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1102 may be configured to communicate with an access network or other network using the communication interface 1112.
  • the communication interface 1112 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1122.
  • the communication interface 1112 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1118 and/or a receiver 1120 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1118 and receiver 1120 may be coupled to one or more antennas (e.g., antenna 1122) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1112 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 1112, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 10 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a triggering event e.g., when moisture is detected, an alert is sent
  • a request e.g., a user initiated request
  • a continuous stream e.g., a live video feed of a patient.
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal-
  • AR Augmented Reality
  • VR
  • a UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1100 shown in Figure 11.
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG 12 shows a network node 1200 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi -standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1200 includes a processing circuitry 1202, a memory 1204, a communication interface 1206, and a power source 1208.
  • the network node 1200 may be composed of multiple physically separate components (e.g., aNodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1200 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1200 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1204 for different RATs) and some components may be reused (e.g., a same antenna 1210 may be shared by different RATs).
  • the network node 1200 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1200, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1200.
  • RFID Radio Frequency Identification
  • the processing circuitry 1202 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1200 components, such as the memory 1204, to provide network node 1200 functionality.
  • the processing circuitry 1202 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1202 includes one or more of radio frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214. In some embodiments, the radio frequency (RF) transceiver circuitry 1212 and the baseband processing circuitry 1214 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1212 and baseband processing circuitry 1214 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 1202 includes one or more of radio frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214.
  • the radio frequency (RF) transceiver circuitry 1212 and the baseband processing circuitry 1214 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 1204 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1202.
  • volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or
  • the memory 1204 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1202 and utilized by the network node 1200.
  • the memory 1204 may be used to store any calculations made by the processing circuitry 1202 and/or any data received via the communication interface 1206.
  • the processing circuitry 1202 and memory 1204 is integrated.
  • memory 1204 may also be configured to store a sparse decoding module (SDM) 1250.
  • SDM sparse decoding module
  • network node 1200 may utilize its SDM 1250 to perform the sparse decoding functions performed at the network node as described herein (when executed by processing circuitry 1202).
  • the communication interface 1206 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1206 comprises port(s)/terminal(s) 1216 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1206 also includes radio front-end circuitry 1218 that may be coupled to, or in certain embodiments a part of, the antenna 1210. Radio front-end circuitry 1218 comprises filters 1220 and amplifiers 1222.
  • the radio front-end circuitry 1218 may be connected to an antenna 1210 and processing circuitry 1202.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1210 and processing circuitry 1202.
  • the radio front-end circuitry 1218 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1218 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1220 and/or amplifiers 1222.
  • the radio signal may then be transmitted via the antenna 1210.
  • the antenna 1210 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1218.
  • the digital data may be passed to the processing circuitry 1202.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1200 does not include separate radio front-end circuitry 1218, instead, the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210.
  • the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210.
  • all or some of the RF transceiver circuitry 1212 is part of the communication interface 1206.
  • the communication interface 1206 includes one or more ports or terminals 1216, the radio front-end circuitry 1218, and the RF transceiver circuitry 1212, as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuitry 1214, which is part of a digital unit (not shown).
  • the antenna 1210 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1210 may be coupled to the radio front-end circuitry 1218 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1210 is separate from the network node 1200 and connectable to the network node 1200 through an interface or port.
  • the antenna 1210, communication interface 1206, and/or the processing circuitry 1202 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1210, the communication interface 1206, and/or the processing circuitry 1202 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1208 provides power to the various components of network node 1200 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1208 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1200 with power for performing the functionality described herein.
  • the network node 1200 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1208.
  • the power source 1208 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 1200 may include additional components beyond those shown in Figure 12 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 1200 may include user interface equipment to allow input of information into the network node 1200 and to allow output of information from the network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1200.
  • FIG. 13 is a block diagram of a host 1300, which may be an embodiment of the host 1016 of Figure 10, in accordance with various aspects described herein.
  • the host 1300 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1300 may provide one or more services to one or more UEs.
  • the host 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a network interface 1308, a power source 1310, and a memory 1312.
  • processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a network interface 1308, a power source 1310, and a memory 1312.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 11 and 12, such that the descriptions thereof are generally applicable to the corresponding components of host 1300.
  • the memory 1312 may include one or more computer programs including one or more host application programs 1314 and data 1316, which may include user data, e.g., data generated by a UE for the host 1300 or data generated by the host 1300 for a UE.
  • Embodiments of the host 1300 may utilize only a subset or all of the components shown.
  • the host application programs 1314 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1314 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 1300 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1314 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1404 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1408A and 1408B (one or more of which may be generally referred to as VMs 1408), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to the VMs 1408.
  • the VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406.
  • a virtualization layer 1406 Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • a VM 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1408, and that part of hardware 1404 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1408 on top of the hardware 1404 and corresponds to the application 1402.
  • Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization.
  • hardware 1404 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1410, which, among others, oversees lifecycle management of applications 1402.
  • hardware 1404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1412 which may alternatively be used for communication between hardware nodes and radio units.
  • a control system 1412 which may alternatively be used for communication between hardware nodes and radio units.
  • Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computational
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé mis en œuvre par un équipement utilisateur (UE) dans un réseau. Le procédé comprend la coordination, avec un nœud de réseau, d'une configuration à utiliser pour les mesures de signaux de référence effectuées par l'UE, la réalisation de mesures de signaux de référence conformément à la configuration, sur des éléments d'un ensemble de faisceaux de réception déterminés par l'UE, chaque élément de l'ensemble de faisceaux de réception correspondant à un poids d'amplitude et de phase pour les éléments d'antenne de réception de l'UE, et la fourniture d'informations indiquant un ou plusieurs des éléments de l'ensemble de faisceaux de réception et les résultats respectifs de la mesure du signal de référence. Le procédé comprend en outre la réception d'informations indiquant un ensemble de faisceaux de réception (Rx) préférentiels déterminés par le nœud de réseau sur la base des informations fournies, et la sélection d'un ensemble de faisceaux Rx parmi l'ensemble indiqué de faisceaux Rx préférentiels pour l'établissement d'une session de communication avec le nœud de réseau.
PCT/SE2023/051221 2023-12-05 2023-12-05 Gestion combinée de faisceaux d'émission-réception Pending WO2025122036A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2023/051221 WO2025122036A1 (fr) 2023-12-05 2023-12-05 Gestion combinée de faisceaux d'émission-réception

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2023/051221 WO2025122036A1 (fr) 2023-12-05 2023-12-05 Gestion combinée de faisceaux d'émission-réception

Publications (1)

Publication Number Publication Date
WO2025122036A1 true WO2025122036A1 (fr) 2025-06-12

Family

ID=95979860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/051221 Pending WO2025122036A1 (fr) 2023-12-05 2023-12-05 Gestion combinée de faisceaux d'émission-réception

Country Status (1)

Country Link
WO (1) WO2025122036A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190159054A1 (en) * 2016-05-13 2019-05-23 Intel IP Corporation Beam measurement in a wireless communication network for identifying candidate beams for a handover
US20200195333A1 (en) * 2017-01-05 2020-06-18 Ntt Docomo, Inc. Beam selection method, mobile station, and base station
US11245456B2 (en) * 2016-05-11 2022-02-08 Idac Holdings, Inc. Systems and methods for beamformed uplink transmission

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11245456B2 (en) * 2016-05-11 2022-02-08 Idac Holdings, Inc. Systems and methods for beamformed uplink transmission
US20190159054A1 (en) * 2016-05-13 2019-05-23 Intel IP Corporation Beam measurement in a wireless communication network for identifying candidate beams for a handover
US20200195333A1 (en) * 2017-01-05 2020-06-18 Ntt Docomo, Inc. Beam selection method, mobile station, and base station

Similar Documents

Publication Publication Date Title
US20240364600A1 (en) Topology hiding in 5gc with roaming
WO2024033808A1 (fr) Mesures de csi pour mobilité intercellulaire
US20250293738A1 (en) Beam pairing prediction with assistance information
EP4569637A1 (fr) Rapport de faisceau basé sur un groupe pour une transmission et une réception simultanées à panneaux multiples
WO2024096765A1 (fr) Identification de faisceau basée sur une détection compressée évolutive
WO2025122036A1 (fr) Gestion combinée de faisceaux d'émission-réception
US20250063574A1 (en) Mac ce signaling for supporting both joint dl/ul tci and separate dl/ul tci operations
WO2024138619A1 (fr) Procédés et appareils de communication sans fil
WO2025050355A1 (fr) Nœud de réseau et procédé exécuté dans un réseau de communication sans fil
US20250286775A1 (en) Network configuration identifier signalling for enabling user equipment-based beam predictions
WO2025177165A1 (fr) Faisceau virtuel dans une gestion de faisceau basée sur l'ia
US20240364486A1 (en) Sounding Reference Signal Transmission in a Wireless Communication Network
WO2025178536A1 (fr) Structure de csi étendue pour prédiction de faisceau
WO2025178541A1 (fr) Procédé de sélection d'ensembles a-b assistée par ue pour prédiction de faisceau
WO2024242608A1 (fr) Procédés pour permettre une signalisation efficace d'informations d'assistance de configuration de réseau pour une gestion de faisceau
WO2023247657A2 (fr) Gestion de faisceau de liaison latérale
WO2025104488A1 (fr) Systèmes et procédés de formation de faisceau basée sur un canal d'accès aléatoire physique pendant une période de veille à entrées multiples et sorties multiples massives
WO2024237841A1 (fr) Configuration d'un équipement utilisateur pour effectuer un rapport de mesure
WO2025165271A1 (fr) Nœud de réseau, équipement utilisateur et procédés de compensation de fréquence entre points d'émission et de réception
WO2024231337A1 (fr) Procédure de faisceau de sondage
WO2024072307A1 (fr) Bwp et mobilité inter-cellules l1-l2
WO2024210787A1 (fr) Informations de capacité d'équipement utilisateur relatives à un temps de syntonisation de fréquence radio
KR20250168591A (ko) 다중 prach 송신을 위한 임계치 수정을 위한 방법
WO2024241179A1 (fr) Procédés de modification de seuil pour de multiples transmissions prach
WO2024068891A1 (fr) Surdébit de rapport de liaison montante d'équipement utilisateur réduit

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

Country of ref document: EP

Kind code of ref document: A1