[go: up one dir, main page]

WO2025172940A1 - Rapport de faisceau initié par équipement utilisateur sur la base d'une prédiction de faisceau - Google Patents

Rapport de faisceau initié par équipement utilisateur sur la base d'une prédiction de faisceau

Info

Publication number
WO2025172940A1
WO2025172940A1 PCT/IB2025/051632 IB2025051632W WO2025172940A1 WO 2025172940 A1 WO2025172940 A1 WO 2025172940A1 IB 2025051632 W IB2025051632 W IB 2025051632W WO 2025172940 A1 WO2025172940 A1 WO 2025172940A1
Authority
WO
WIPO (PCT)
Prior art keywords
host
user data
processing circuitry
network node
previous
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/IB2025/051632
Other languages
English (en)
Inventor
Shiwei Gao
Claes Tidestav
Andreas Nilsson
Lei BAO
Behrooz MAKKI
Icaro Leonardo DA SILVA
Jianwei Zhang
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
Publication of WO2025172940A1 publication Critical patent/WO2025172940A1/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/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/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621—Feedback content
    • 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

Definitions

  • the present disclosure relates to a wireless communications system and, more particularly, to beam management in a wireless communications system.
  • Beam management was introduced in 3gpp Rel-15 for the 5th generation (5G) or new radio (NR) mobile network operating at frequency range two (FR2), i.e., above 24.250GHz, where multiple analog antenna beams are typically used for both transmitting and receiving at the network (NW) or gNB side as well as the user equipment (UE) side.
  • 5G 5th generation
  • NR new radio
  • the UE may be configured by the NW to measure and report Ll- RSRP (layer one reference received signal power) or Ll-SINR (layer one signal to interference plus noise ratio) for multiple SSB beams for beam maintenance purpose.
  • the report can be periodic, semi-persistent, or aperiodic.
  • the UE may be configured to report N best L1-RSRP/L1- SINR and the associated SSB indices. Based on the report, the NW can decide whether it is better to switch to a new SSB beam for serving the UE.
  • the NW may also be able to serve a UE with a set of narrower beams with higher antenna gains than the SSBs.
  • the NW may configure and transmit a set of CSLRS (channel state information reference signal) for the UE to measure and report Ll-RSRP or Ll-SINR.
  • the report can be periodic, semi-persistent, or aperiodic.
  • the UE may be requested to report N best L-l-RSRP/Ll-SINR and the associated CSLRS resource indices.
  • the NW can decide whether it is better to switch to a CSL RS beam for serving the UE, or if the current serving beam is a CSLRS beam, whether to switch to a new CSLRS beam.
  • CSI measurement configuration for beam management for beam management (BM)
  • a UE is configured by the network with a Channel State Information (CSI) measurement configuration e.g. IE (information element) CSI-MeasConfig received within an RRCReconfiguration message. That is configured per Serving Cell (within ServingCellConfig e.g. of an SpCell), to associate a serving cell in which CSI reports are to be transmitted, e.g., Uplink (UL) channels of that serving cell.
  • CSI Channel State Information
  • ServingCellConfig e.g. of an SpCell
  • UL Uplink
  • the signaling is defined in TS 38.331 https://www.3gpp.org/ftp/Specs/archive/38_series/38.331/38331-fh0.zip.
  • the network For each type of CSI report the UE needs to transmit, the network indicates an explicit list of CSI resources (also called CSI resource configuration(s)), comprising a list of reference signals to be measured, such as CSI-RSs sets (nzp-CSI-RS-ResourceSetList, IE SEQUENCE (SIZE (E.maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetld) and/or SSBs sets (csi-SSB-ResourceSetList, IE SEQUENCE (SIZE (E.maxNrofCSI-SSB- ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetld) for a given serving cell the UE is configured with e.g. the SpCell of a cell group, or an SCell. Notice that the UE may measure CSI resources of a first serving cell and report in another serving cell.
  • CSI-RSs sets nzp-CSI-RS-
  • the activation of a beam may be referred as the activation of a Transmission Configuration Indication (TCI) state, which is associated to a Quasi-Co-Location (QCL) source, corresponding to a Reference Signal (RS) such as an SSB and/or CSI-RS, transmitted in a spatial direction (beam) correlated to the same spatial direction (beam) in which the network may transmit a control (e.g., PDCCH) and/or data channel (e.g., PDSCH).
  • TCI Transmission Configuration Indication
  • QCL Quasi-Co-Location
  • RS Reference Signal
  • Beam a spatial direction correlated to the same spatial direction (beam) in which the network may transmit a control (e.g., PDCCH) and/or data channel (e.g., PDSCH).
  • a control e.g., PDCCH
  • PDSCH data channel
  • OPTIONAL Need R numberOfSingleTRP-CSI-Mode 1 -r 17 ENUMERATED ⁇ nO, nl, n2 ⁇
  • the field reportConfigType within CSI-ReportConfig indicates to the UE the UL channel to transmit the report and the time domain behavior for reporting the CSI measurements, which may also be called beam reporting in case it includes measurements used for beam management.
  • the configuration indicates whether the report is periodic, aperiodic or semi-persistent, and associated configurations such as periodicity.
  • a UE For aperiodic CSI reporting, a UE is also configured with a list of aperiodic CSI trigger states, each associated to one or more CSI report configurations. If multiple reference signal (NZP CSLRS or SSB) resource sets are configured in a CSI resource configuration in an associated CSI report configuration, one set is selected in the corresponding trigger state.
  • NZP CSLRS or SSB multiple reference signal
  • An aperiodic CSI report is triggered when the CSI request field in DCI indicating an aperiodic trigger state is associated to the corresponding aperiodic CSI report configuration.
  • the CSI/beam reporting is always NW-initiated.
  • the NW explicitly requests a certain report from the UE, by including a pointer to a certain CSI-ReportConfig in DCI.
  • UE initiated beam reporting will be supported to reduce beam reporting overhead and/or latency. This would imply that it is the UE that initiates the reporting.
  • a method performed by a User Equipment comprises any one or more of the following: receiving from the network (NW) a configuration of a plurality of DL RSs (or beams) for beam measurements and predictive beam reporting (Step 1), determining at least one candidate target beam among the plurality of DL RSs (or beams) based on measurements on the plurality of DL RSs (or beams) (Step 2), sending a message to the NW about the at least one candidate beam (and, its related measurement values) when one or more events occur (Step 3), receiving a beam switch indication from the NW to switch to one of the candidate beams (Step 4).
  • the plurality of DL RSs comprises at least a current serving beam.
  • the plurality of DL RSs are transmitted periodically or semi-persistently, and, optionally, a report is sent periodically or semi-persistently after an event is triggered a first time.
  • the beam measurements comprises Ll-RSRP and/or Ll-SINR measurement.
  • the configuration further comprises a reporting type indicating a UE initiated beam reporting of candidate beams for beam switching.
  • the configuration further indicates the number or the maximum number of candidate beams to be reported.
  • a UE initiated reporting configuration indicates the evaluation time period, for comparison between the current serving and the candidate beams.
  • a reporting type indicating the UE initiated beam reporting includes information about at least an event and one or more thresholds associated to the event (e.g., the Ll-RSRP, Ll-SINR thresholds).
  • a candidate beam at a given time is a beam with increasing Ll- RSRP and/or Ll-SINR values over a most recent evaluation time period prior to the given time, wherein, optionally, an evaluation time period comprises at least two consecutive Ll-RSRP or Ll- SINR measurements, wherein, optionally, the most recent evaluation time period comprises the most recent Ll-RSRP or Ll-SINR measurement prior to the given time.
  • the event can be a combination of one or more of the following sub-events:
  • Event Al The Ll-RSRP value of the current serving beam is decreasing and the most recent L 1 -RSRP of a candidate beam is greater than the most recent L 1 -RSRP of the current serving beam minus a XdB offset;
  • Event A2 The Ll-RSRP value of the current serving beam is decreasing over last N1 measurement occasions and, optionally, where N1 can be configured by network or determined by UE based on UE implementation;
  • Event B The L 1 -SINR value of the current serving beam is decreasing and the most recent Ll-SINR of a candidate beam is greater than the most recent respective Ll-SINR of the current serving beam minus aY dB offset;
  • the message can be carried in UL control information (UCI) in a physical uplink control channel (PUCCH) or in a Medium Access Control, MAC, control Element, CE, or, the message can contain just an indication or a flag indicating the occurrence of the one or more events, wherein optionally, the NW may request the UE to provide further information such as a beam report comprising one or more of an identifier of the event(s) occurred, an identifier of the best candidate beam and its L1-RSRP/L1-SINR, identifiers of multiple candidate beams and their most recent L1-RSRP/L1-SINR values, and most recent L1-RSRP/L1-SINR of the current serving beam
  • UCI UL control information
  • PUCCH physical uplink control channel
  • CE Medium Access Control
  • the NW may request the UE to provide further information such as a beam report comprising one or more of an identifier of the event(s) occurred, an identifier of the best candidate beam and its L1
  • the method further includes determining if an event for a UE initiated beam report has occurred based on one or more of the following criteria:
  • the method further includes providing user data; and forwarding the user data to a host via the transmission to the network node.
  • a UE is adapted to receive from the network (NW) a configuration of a plurality of DL RSs (or beams) for beam measurements and predictive beam reporting.
  • the UE is further adapted to determine at least one candidate target beam among the plurality of DL RSs (or beams) based on measurements on the plurality of DL RSs (or beams).
  • the UE is further adapted to send a message to the NW about the at least one candidate beam (and, its related measurement values) when one or more events occur.
  • the UE is further adapted to receive a beam switch indication from the NW to switch to one of the candidate beams.
  • a method performed by a network node comprises transmitting to a UE a configuration of a plurality of DL RSs (or beams) for beam measurements and UE initiated beam reporting. The method further comprises receiving information about at least one candidate target beam and its related measurements when one or more events have occurred. The method further comprises receiving information about at least one candidate target beam and its related measurements when one or more events have occurred.
  • a network node is adapted to transmitting to a UE a configuration of a plurality of DL RSs (or beams) for beam measurements and UE initiated beam reporting. The network node is further adapted receive information about at least one candidate target beam and its related measurements when one or more events have occurred. The network node is further adapted to receive information about at least one candidate target beam and its related measurements when one or more events have occurred.
  • Figure 3B illustrates an example of predictive beam reporting/switching with two beams where a beam switching occurs before the link performance of the current serving beam is worse than the other beam, in accordance with some embodiments of the present disclosure
  • Figure 8 is a block diagram of a host, which may be an embodiment of the host of Figure 5, in accordance with various aspects of the present disclosure described herein;
  • Figure 9 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized;
  • Figure 10 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure.
  • a serving beam’s performance is monitored/evaluated via beam measurement report.
  • a current serving beam is not switched until a new beam with better Ll-RSRP or Ll-SINR is identified.
  • the current beam is not switched until a new beam’s Ll-RSRP or Ll-SINR is XdB better than that of the current beam.
  • FIG. 1 An example is shown in Figure 1, where there are two beams and L1-RSRP/L1-SINR associated to the two beams observed at a UE over time is shown.
  • Beam #1 is the current serving beam.
  • the L1-RSRP/L1-SINR of beam #2 is XdB better than that of beam #1.
  • the NW will not switch to beam #2 until a beam report received after time t2.
  • the beam switching from beam #1 to beam #2 will occur at t3.
  • the wireless link over the serving beam (beam #1) is further degraded and the communication during this period may not be reliable.
  • the time period from t2 to t3 can be long if the configured reporting periodicity is large.
  • the time period from t2 to t3 could be reduced if there is frequent uplink resource available for sending the report or an indication indicating the condition. In any case, link degradation from tl to t3 is may not be avoidable and thus be a problem.
  • a UE initiated beam reporting method based on beam prediction is proposed in which a UE is configured to measure and store multiple L 1 -RSRP/L 1 -SINR values over a period time for each beam configured for beam measurement. Based on the measurements, if the Ll- RSRP/L1-SINR values of a beam (other than the current serving beam) is increasing over the period of time, then the beam becomes a candidate beam for beam switching.
  • the UE may initiate a beam report.
  • Embodiments of the present disclosure relate to methods comprising the following steps:
  • UE is configured with a plurality of beams or DL RSs for UE initiated beam reporting.
  • the plurality of beams can include the current serving beam.
  • UE determines at least one candidate beam among the configured beams for beam switching based on a recent history of measured L 1 -RSRP/L 1- SINR of each of the configured beams (rather than based on a single measurement of each beam). o A candidate beam is determined when the LI -RSRP/L 1 -SINR value of the candidate beam is increasing over time.
  • UE is further configured to send a message to the NW when one or more events occurs.
  • the one or more events can be one or more of
  • the Ll-RSRP value of the current serving beam is decreasing and the most recent Ll-RSRP of a candidate beam is equal to or greater than the most recent Ll-RSRP of the current serving beam minus a XdB offset, where the ‘X’dB can be configured.
  • Event C The most recent Ll-RSRP or Ll-SINR of the current serving beam is below a threshold, wherein the threshold can be configured by the NW. o the message can contain one or more of an identifier of the best candidate beam and optionally its most recent Ll- RSRP/L1-SINR.
  • Embodiments of the disclosure may reduce the beam switching transition period and thus, avoid large link degradation during a beam switch.
  • Step 1 receiving from the NW a configuration of a plurality of DL RSs (or beams) for beam measurements and predictive beam reporting.
  • Step 2 determining at least one candidate target beam among the plurality of DL RSs (or beams) based on measurements on the plurality of DL RSs (or beams).
  • Step 3 sending a message to the NW about the at least one candidate beam (and, its related measurement values) when one or more events occur.
  • Step 4 receiving a beam switch indication from the NW to switch to one of the candidate beams.
  • the plurality of DL RSs comprises at least a current serving beam.
  • Step 1 the plurality of DL RSs (or beams) are transmitted periodically or semi- persistently.
  • the report is sent periodically or semi-persistently after the event is triggered a first time.
  • the beam measurements comprises LI -RSRP and/or Ll-SINR measurement.
  • the configuration further comprises a reporting type indicating a UE initiated beam reporting of candidate beams for beam switching.
  • the configuration further indicates the number or the maximum number of candidate beams to be reported.
  • Step 1 and where the UE initiated reporting configuration indicates the evaluation time period, for comparison between the current serving and the candidate beams.
  • the reporting type indicating the UE initiated beam reporting includes information about at least an event and one or more thresholds associated to the event (e.g., the Ll-RSRP, Ll-SINR thresholds).
  • a candidate beam at a given time is a beam with increasing Ll-RSRP and/or Ll-SINR values over a most recent evaluation time period prior to the given time.
  • An evaluation time period may comprise at least two consecutive Ll-RSRP or Ll-SINR measurements.
  • the most recent evaluation time period may comprise the most recent Ll-RSRP or Ll-SINR measurement prior to the given time.
  • FIG. 3 A An example is illustrated in Figure 3 A, where beam#l is the current serving beam and beam#2 is determined to be a candidate beam sometime after three measurements at times tl, t2 and t3 ( tl’ ⁇ t2’ ⁇ t3’ ) because the LI -RSRP/L1-SINR of the serving beam P(t) is decreasing, i.e., P(t’ l)>P(t’2)>P(t’3), while the L1-RSRP/L1-SINR of beam #2 Q(t) is increasing, i.e., Q(t’ l) ⁇ Q(t’2) ⁇ Q(t’3).
  • each L1-RSRP/L1-SINR itself can be based on measurements over one or more periods of the DL RS.
  • a candidate beam is determined prior to the time when the link quality of the candidate beam is better than the serving beam. This is herein referred to as candidate beam prediction.
  • Event Al The Ll-RSRP value of the current serving beam is decreasing and the most recent L 1 -RSRP of a candidate beam is greater than the most recent L 1 -RSRP of the current serving beam minus a XdB offset.
  • Event A2 The Ll-RSRP value of the current serving beam is decreasing over last N1 measurement occasions.
  • N1 can be configured by network or determined by UE based on UE implementation.
  • Event B The L 1 -SINR value of the current serving beam is decreasing and the most recent Ll-SINR of a candidate beam is greater than the most recent respective Ll-SINR of the current serving beam minus aY dB offset.
  • Event C The most recent Ll-RSRP or Ll-SINR of the current serving beam is below a threshold, wherein the threshold can be configured by the NW.
  • the offset (i.e., XdB, Y dB, Z dB) can be predefined or configured by the NW as part of the configuration in Step 1.
  • the above events are just some examples, other events are also possible.
  • the UE can further perform a time-domain filtering on the beam measurements such as L1-RSRP/L1-SINR before the event evaluation, so that the filtered measurement value of a beam (e.g. current beam and possible candidate beam) is used as input to the event evaluation.
  • a filter parameter ‘a’ so that a filtered value at time instance (n) is defined as follows:
  • M(n) is the latest beam measurement results at Layer 1; F(n) is the updated filtered beam measurement result, to be used for evaluation of the event; F(n-l) is the old filtered beam measurement result (F(0) is initialized with M(l)); ‘a’ is a filter related parameter (e.g. configured by the network, or derived based on a filter coefficient configured by the network).
  • F(n) is the updated filtered beam measurement result, to be used for evaluation of the event;
  • F(n-l) is the old filtered beam measurement result (F(0) is initialized with M(l));
  • ‘a’ is a filter related parameter (e.g. configured by the network, or derived based on a filter coefficient configured by the network).
  • the parameter ‘a’ or a parameter used to derive ‘a’ is configured per serving cell and/or per frequency and/or per UE, per frequency range.
  • the time difference between the most recent measurement occasion of the serving beam and the most recent measurement occasion of the candidate beam is smaller than and/or equal to a preconfigured or predefined required time difference value in Step 1.
  • the message can contain one or more of
  • the best candidate beam can be, e.g., the candidate beam having the largest L1-RSRP/L1-SINR value among all the candidate beams in the most recently measurement period.
  • the message can be carried in UL control information (UCI) in a physical uplink control channel (PUCCH) or in a Medium Access Control, MAC, control Element, CE.
  • UCI UL control information
  • PUCCH physical uplink control channel
  • MAC Medium Access Control
  • CE control Element
  • a beam report comprising one or more of an identifier of the event(s) occurred, an identifier of the best candidate beam and its LI -RSRP/L 1 -SINR, identifiers of multiple candidate beams and their most recent L 1 -RSRP/L 1- SINR values, and most recent L1-RSRP/L1- SINR of the current serving beam
  • the UE starts a timer. While the timer is running, the UE does not send another message to the NW. Once the timer expires, the UE can send another message to the NW if the condition of one or more events is fulfilled.
  • a timer may be called a prohibit timer.
  • the UE may determine that the Ll-RSRP value of the current serving beam is decreasing and the most recent Ll-RSRP of a candidate beam is greater than the most recent Ll-RSRP of the current serving beam minus a XdB offset, send a message and start the timer. While the timer is running, the UE will not send another report, even if the condition is fulfilled. Once the timer expires, the UE would send another message to the NW, if the condition is still fulfilled.
  • a timer value may be configured for that purpose in the reporting configuration (e.g. in CSI-ReportConfig).
  • the beam switch indication can comprise a beam activation command to activate one or more of the candidate beams and/or a beam indication in DCI (Downlink Control Information) indicating a new beam for data transmission and/or reception.
  • DCI Downlink Control Information
  • Step 4 the UE can further receive an acknowledgement from the NW on whether the UE initiated beam report has been received. If the beam report has been received, the UE does not send another indication for the same event/events.
  • the UE measures L1-RSRP/L1-SINR at time instances t_l A ',t_2 A ',t_3 A ', resulting in three L1-RSRP/L1- SINR measurements values: P(t’ l),P(t’2), P(t’3) for beam #1 and Q(f 1), Q(t’2), Q(t’3) for beam #2.
  • Beam #2 is determined as a candidate beam.
  • An event is detected att’3 because the LI -RSRP/L1-SINR values P(t’ l)>P(t’2)>P(t’3) are decreasing and Q(t’3) + XdB > P(t’3).
  • the UE After the event detection, the UE sends an indication to the NW after f 3. A beam switch indication from beam #1 to beam #2 is received sometime later, hopefully before t’4. During the time period between t3’ and t4’, there is still a reliable communication link with the current serving beam #1 for carrying both the event indication in the UL and the beam switching indication in the DL, and therefore, a reliable beam switching is achieved.
  • an event is based (at least partly) on if the beam measurements (e.g., L1-RSRP/L1-SINR associated with a UE initiated beam report) have changed since the last transmitted UE initiated beam report.
  • the UE takes one or more of the following criteria into account when determining if an event for a UE initiated beam report has occurred:
  • the performance of the serving beam has changed (increase and/or decreased) more than a certain threshold since the last transmitted UE initiated beam report. • The same beam as included as best beam in the last UE initiated beam report is still the best beam, but the performance for this beam has changed (increase and/or decreased) with more than a threshold.
  • FIG 4 is a flow chart that illustrates a method performed by a network node (e.g., a gNB in this example embodiment) in accordance with an embodiment of the present disclosure. Note that this process is complementary to the process performed by the UE described above, e.g., with respect to Figure 1. As such, details above provided in relation to Figures 1-3 are equally applicable to Figure 4. As illustrated, the gNB performs one or more of the following steps: transmitting to a UE a configuration of a plurality of DL RSs (or beams) for beam measurements and UE initiated beam reporting. (Step A, 410); receiving information about at least one candidate target beam and its related measurements when one or more events have occurred. (Step B. 420); receiving information about at least one candidate target beam and its related measurements when one or more events have occurred. (Step C, 430).
  • a network node e.g., a gNB in this example embodiment
  • Figure 5 shows an example of a communication system 500 in which embodiments of the present disclosure may be implemented.
  • the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a Radio Access Network (RAN), and a core network 506, which includes one or more core network nodes 508.
  • the access network 504 includes one or more access network nodes, such as network nodes 510A and 510B (one or more of which may be generally referred to as network nodes 510), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs).
  • 3GPP Third Generation Partnership Project
  • APs non-3GPP Access Points
  • a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor.
  • Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • the network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.
  • the network nodes 510 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 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 500 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 500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 512 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 510 and other communication devices.
  • the network nodes 510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 512 and/or with other network nodes or equipment in the telecommunication network 502 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 502.
  • the functionality of the network node or gNB described above may be implemented in any one of the network nodes 510, and the functionality of the UE described above (e.g., with respect to Figures 1-4) may be implemented in any one of the UEs 512.
  • the network node 510 may be a multi-TRP network node (e.g., a gNB having multiple TRPs).
  • the core network 506 connects the network nodes 510 to one or more hosts, such as host 516. 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 506 includes one more core network nodes (e.g., core network node 508) 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 508.
  • 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 Access and Mobility Management Function
  • SMF 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
  • the host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and/or the telecommunication network 502, and may be operated by the service provider or on behalf of the service provider.
  • the host 516 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.
  • the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 500 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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
  • the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunication network 502 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 Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 512 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504.
  • a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multi -standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi -Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi -Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and/or 512D) and network nodes (e.g., network node 510B).
  • the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 514 may be a broadband router enabling access to the core network 506 for the UEs.
  • the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 514 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 514 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 514 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 514 may have a constant/persistent or intermittent connection to the network node 510B.
  • the hub 514 may also allow for a different communication scheme and/or schedule between the hub 514 and UEs (e.g., UE 512C and/or 512D), and between the hub 514 and the core network 506.
  • the hub 514 is connected to the core network 506 and/or one or more UEs via a wired connection.
  • the hub 514 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 504 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection.
  • the hub 514 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 510B.
  • the hub 514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 510B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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, vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3 GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT Narrowband Internet of Things
  • MTC Machine Type Communication
  • a UE may support Device-to-Device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehi cl e-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehi cl e-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
  • the UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, memory 610, a communication interface 612, and/or any other component, or any combination thereof.
  • processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, memory 610, a communication interface 612, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 6. 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 602 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 610.
  • the processing circuitry 602 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 602 may include multiple Central Processing Units (CPUs).
  • the input/output interface 606 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 600.
  • 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 608 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 608 may further include power circuitry for delivering power from the power source 608 itself, and/or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 608.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied.
  • the memory 610 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616.
  • the memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems.
  • the memory 610 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (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 Dual In-line Memory Module
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 610 may allow the UE 600 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 610, which may be or comprise a device-readable storage medium.
  • the processing circuitry 602 may be configured to communicate with an access network or other network using the communication interface 612.
  • the communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622.
  • the communication interface 612 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 618 and/or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., the antenna 622) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 612 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Intemet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband CDMA
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR Fifth Generation
  • UMTS Worldwide Interoperability for Mobile communications
  • Ethernet Transmission Control Protocol/Intemet Protocol
  • TCP/IP Transmission Control Protocol/Intemet Protocol
  • SONET Synchronous Optical Networking
  • ATM Asynchronous Transfer Mode
  • QUIC Quick User Datagram Protocol Internet Connection
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 612, 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 15 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 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. In response to the received wireless input 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 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.
  • Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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 VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device,
  • AR
  • 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 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • 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.
  • 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, distributed units (e.g., in an O-RAN access node), and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs 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 BS 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 Transmission Point
  • MSR Multi -Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • the network node 700 includes processing circuitry 702, memory 704, a communication interface 706, and a power source 708.
  • the network node 700 may be composed of multiple physically separate components (e.g., aNodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • aNodeB component and an RNC component e.g., a BTS component and a BSC component, etc.
  • 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 700 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 704 for different RATs) and some components may be reused (e.g., a same antenna 710 may be shared by different RATs).
  • the network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 700.
  • the processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 700 components, such as the memory 704, to provide network node 700 functionality.
  • the processing circuitry 702 includes a System on a Chip (SOC).
  • the processing circuitry 702 includes one or more of Radio Frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714.
  • RF Radio Frequency
  • the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.
  • the memory 704 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, RAM, 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 702.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, 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
  • the memory 704 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 702 and utilized by the network node 700.
  • the memory 704 may be used to store any calculations made by the processing circuitry 702 and/or any data received via the communication interface 706.
  • the processing circuitry 702 and the memory 704 are integrated.
  • the communication interface 706 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 706 comprises port(s)/terminal(s) 716 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 706 also includes radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710.
  • the radio front-end circuitry 718 comprises filters 720 and amplifiers 722.
  • the radio front-end circuitry 718 may be connected to the antenna 710 and the processing circuitry 702.
  • the radio front-end circuitry 718 may be configured to condition signals communicated between the antenna 710 and the processing circuitry 702.
  • the radio front-end circuitry 718 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 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 720 and/or the amplifiers 722.
  • the radio signal may then be transmitted via the antenna 710.
  • the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718.
  • the digital data may be passed to the processing circuitry 702.
  • the communication interface 706 may comprise different components and/or different combinations of components.
  • the network node 700 does not include separate radio front-end circuitry 718; instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes the one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712 as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).
  • the antenna 710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 710 is separate from the network node 700 and connectable to the network node 700 through an interface or port.
  • the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 700. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any transmitting operations described herein as being performed by the network node 700. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 708 provides power to the various components of the network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein.
  • the network node 700 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708.
  • the power source 708 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 700 may include additional components beyond those shown in Figure 7 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 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700.
  • FIG 8 is a block diagram of a host 800, which may be an embodiment of the host 516 of Figure 5, in accordance with various aspects described herein.
  • the host 800 may be or comprise various combinations of 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 800 may provide one or more services to one or more UEs.
  • the host 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and memory 812.
  • processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and memory 812.
  • 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 6 and 7, such that the descriptions thereof are generally applicable to the corresponding components of the host 800.
  • the memory 812 may include one or more computer programs including one or more host application programs 814 and data 816, which may include user data, e.g. data generated by a UE for the host 800 or data generated by the host 800 for a UE.
  • Embodiments of the host 800 may utilize only a subset or all of the components shown.
  • the host application programs 814 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), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (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, and heads-up display systems).
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG Moving Picture Experts Group
  • VP9 Moving Picture Experts Group
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • FLAC Free Lossless Audio Codec
  • AAC Advanced Audio Coding
  • the host application programs 814 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. Accordingly, the host 800 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 814 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 (DASH or MPEG-DASH), etc.
  • FIG. 9 is a block diagram illustrating a virtualization environment 900 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 900 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
  • the virtualization environment 900 includes components defined by the 0-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
  • Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 900 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 904 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 906 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 908A and 908B (one or more of which may be generally referred to as VMs 908), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.
  • the VMs 908 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of the VMs 908, 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 908 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 908, and that part of the hardware 904 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 908, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 908 on top of the hardware 904 and corresponds to the application 902.
  • the hardware 904 may be implemented in a standalone network node with generic or specific components.
  • the hardware 904 may implement some functions via virtualization.
  • the hardware 904 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 910, which, among others, oversees lifecycle management of the applications 902.
  • the hardware 904 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 RAN or a base station.
  • some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 10 shows a communication diagram of a host 1002 communicating via a network node 1004 with a UE 1006 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE (such as the UE 512A of Figure 5 and/or the UE 600 of Figure 6), the network node (such as the network node 510A of Figure 5 and/or the network node 700 of Figure 7), and the host (such as the host 516 of Figure 5 and/or the host 800 of Figure 8) discussed in the preceding paragraphs will now be described with reference to Figure 10.
  • embodiments of the host 1002 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1002 also includes software, which is stored in or is accessible by the host 1002 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1006 connecting via an OTT connection 1050 extending between the UE 1006 and the host 1002.
  • a host application may provide user data which is transmitted using the OTT connection 1050.
  • the network node 1004 includes hardware enabling it to communicate with the host 1002 and the UE 1006.
  • the connection 1060 may be direct or pass through a core network (like the core network 506 of Figure 5) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like the core network 506 of Figure 5
  • one or more other intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1006 includes hardware and software, which is stored in or accessible by the UE 1006 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1006 with the support of the host 1002.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1006 with the support of the host 1002.
  • an executing host application may communicate with the executing client application via the OTT connection 1050 terminating at the UE 1006 and the host 1002.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1050 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application
  • the OTT connection 1050 may extend via the connection 1060 between the host 1002 and the network node 1004 and via a wireless connection 1070 between the network node 1004 and the UE 1006 to provide the connection between the host 1002 and the UE 1006.
  • the connection 1060 and the wireless connection 1070, over which the OTT connection 1050 may be provided, have been drawn abstractly to illustrate the communication between the host 1002 and the UE 1006 via the network node 1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1002 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1006.
  • the user data is associated with a UE 1006 that shares data with the host 1002 without explicit human interaction.
  • the host 1002 initiates a transmission carrying the user data towards the UE 1006.
  • the host 1002 may initiate the transmission responsive to a request transmitted by the UE 1006.
  • the request may be caused by human interaction with the UE 1006 or by operation of the client application executing on the UE 1006.
  • the transmission may pass via the network node 1004 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1012, the network node 1004 transmits to the UE 1006 the user data that was carried in the transmission that the host 1002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1014, the UE 1006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1006 associated with the host application executed by the host 1002.
  • the UE 1006 executes a client application which provides user data to the host 1002.
  • the user data may be provided in reaction or response to the data received from the host 1002.
  • the UE 1006 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1006. Regardless of the specific manner in which the user data was provided, the UE 1006 initiates, in step 1018, transmission of the user data towards the host 1002 via the network node 1004.
  • the network node 1004 receives user data from the UE 1006 and initiates transmission of the received user data towards the host 1002.
  • the host 1002 receives the user data carried in the transmission initiated by the UE 1006.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1006 using the OTT connection 1050, in which the wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve, e.g., data rate, latency, and/or power consumption and thereby provide benefits such as, e.g., reduced user waiting time, related restriction on file size, improved content resolution, better responsiveness, and/or extended battery lifetime.
  • factory status information may be collected and analyzed by the host 1002.
  • the host 1002 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1002 may store surveillance video uploaded by a UE.
  • the host 1002 may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs.
  • the host 1002 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 1050 may be implemented in software and hardware of the host 1002 and/or the UE 1006.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1050 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1004. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1002.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1050 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components
  • 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 computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored 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 hardwired 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.
  • Embodiment 1 A method performed by a User Equipment, UE, the method comprising any one or more of the following: receiving (Step 1, 110) from the network (NW) a configuration of a plurality of DL RSs (or beams) for beam measurements and predictive beam reporting. determining (Step 2, 120) at least one candidate target beam among the plurality of DL RSs (or beams) based on measurements on the plurality of DL RSs (or beams). sending (Step 3, 130) a message to the NW about the at least one candidate beam (and, its related measurement values) when one or more events occur. receiving (Step 4, 140) a beam switch indication from the NW to switch to one of the candidate beams.
  • Embodiment 2 The method of embodiment 1, wherein the plurality of DL RSs (or beams) comprises at least a current serving beam.
  • Embodiment 3 The method of any of the previous embodiments, wherein the plurality of DL RSs (or beams) are transmitted periodically or semi-persistently, and, optionally, a report is sent periodically or semi-persistently after an event is triggered a first time.
  • Embodiment 4 The method of any of the previous embodiments, wherein the beam measurements comprises Ll-RSRP and/or Ll-SINR measurement.
  • Embodiment 5 The method of any of the previous embodiments, wherein the configuration further comprises a reporting type indicating a UE initiated beam reporting of candidate beams for beam switching.
  • Embodiment 6 The method of any of the previous embodiments, wherein the configuration further indicates the number or the maximum number of candidate beams to be reported.
  • Embodiment 7 The method of any of the previous embodiments, wherein a UE initiated reporting configuration indicates the evaluation time period, for comparison between the current serving and the candidate beams.
  • Embodiment 8 The method of any of the previous embodiments, wherein a reporting type indicating the UE initiated beam reporting includes information about at least an event and one or more thresholds associated to the event (e.g., the Ll-RSRP, Ll-SINR thresholds).
  • a reporting type indicating the UE initiated beam reporting includes information about at least an event and one or more thresholds associated to the event (e.g., the Ll-RSRP, Ll-SINR thresholds).
  • Embodiment 9 The method of any of the previous embodiments, wherein a candidate beam at a given time is a beam with increasing Ll-RSRP and/or Ll-SINR values over a most recent evaluation time period prior to the given time, wherein, optionally, an evaluation time period comprises at least two consecutive Ll-RSRP or Ll-SINR measurements, wherein, optionally, the most recent evaluation time period comprises the most recent Ll-RSRP or Ll-SINR measurement prior to the given time.
  • Embodiment 10 The method of any of the previous embodiments, wherein the event can be a combination of one or more of the following sub-events:
  • the Ll-RSRP value of the current serving beam is decreasing and the most recent Ll-RSRP of a candidate beam is greater than the most recent Ll-RSRP of the current serving beam minus a XdB offset;
  • Event A2 The Ll-RSRP value of the current serving beam is decreasing over last N1 measurement occasions and, optionally, where N1 can be configured by network or determined by UE based on UE implementation;
  • Event B The Ll-SINR value of the current serving beam is decreasing and the most recent Ll-SINR of a candidate beam is greater than the most recent respective Ll-SINR of the current serving beam minus aY dB offset;
  • the most recent Ll-RSRP or Ll-SINR of the current serving beam is below a threshold, wherein the threshold can be configured by the NW, wherein, optionally, The offset (i.e., XdB, Y dB, Z dB) can be predefined or configured by the NW as part of the configuration in Step 1.
  • Embodiment 11 The method of any of the previous embodiments, further comprising: performing a time-domain filtering on the beam measurements such as L1-RSRP/L1- SINR before the event evaluation, so that, optionally, the filtered measurement value of a beam (e.g. current beam and possible candidate beam) is used as input to the event evaluation, and, wherein, optionally, the UE considers a filter parameter ‘a’ so that a filtered value at time instance (n) is defined as follows:
  • M(n) is the latest beam measurement results at Layer 1; F(n) is the updated filtered beam measurement result, to be used for evaluation of the event; F(n-l) is the old filtered beam measurement result (F(0) is initialized with M(l)); ‘a’ is a filter related parameter (e.g. configured by the network, or derived based on a filter coefficient configured by the network), wherein, optionally, the parameter ‘a’ or a parameter used to derive ‘a’ is configured per serving cell and/or per frequency and/or per UE, per frequency range.
  • a filter related parameter e.g. configured by the network, or derived based on a filter coefficient configured by the network
  • Embodiment 12 The method of any of the previous embodiments, for some of the events, the time difference between the most recent measurement occasion of the serving beam and the most recent measurement occasion of the candidate beam is smaller than and/or equal to a preconfigured or predefined required time difference value in Step 1.
  • Embodiment 13 The method of any of the previous embodiments, wherein, optionally, the message can contain one or more of
  • the best candidate beam can be, e.g., the candidate beam having the largest LI -RSRP/L1-SINR value among all the candidate beams in the most recently measurement period.
  • the most recent L 1 -RSRP/L 1 -SINR values of the current serving beam wherein, optionally, the message can be carried in UL control information (UCI) in a physical uplink control channel (PUCCH) or in a Medium Access Control, MAC, control Element, CE, or, the message can contain just an indication or a flag indicating the occurrence of the one or more events, wherein optionally, the NW may request the UE to provide further information such as a beam report comprising one or more of an identifier of the event(s) occurred, an identifier of the best candidate beam and its L1-RSRP/L1-SINR, identifiers of multiple candidate beams and their most recent L1-RSRP/L1-SINR values, and most recent LI -RSRP/L1-SINR of the current serving beam
  • Embodiment 14 The method of any of previous embodiments, further comprising one or more of the following: once a message is sent to the NW, staring a timer; while the timer is running, refraining from sending another message to the NW; once the timer expires, sending another message to the NW if the condition of one or more events is fulfilled; upon determining that the Ll-RSRP value of the current serving beam is decreasing and the most recent LI -RSRP of a candidate beam is greater than the most recent Ll-RSRP of the current serving beam minus a XdB offset, sending a message and start the timer; while the timer is running, refraining from sending another report, even if the condition is fulfilled; once the timer expires, sending another message to the NW, if the condition is still fulfilled; and/or configuring a timer value in the reporting configuration (e.g. in CSI-ReportConfig).
  • a timer value in the reporting configuration e.g. in CSI-ReportConfig
  • Embodiment 15 The method of any of previous embodiments, wherein the beam switch indication comprises a beam activation command to activate one or more of the candidate beams and/or a beam indication in DCI (Downlink Control Information) indicating a new beam for data transmission and/or reception.
  • DCI Downlink Control Information
  • Embodiment 16 The method of any of previous embodiments, further comprising receiving an acknowledgement from the NW on whether the UE initiated beam report has been received, and, optionally, if the beam report has been received, refraining from sending another indication for the same event/events.
  • Embodiment 17 The method of any of previous embodiments, wherein an event is based (at least partly) on if the beam measurements (e.g., L1-RSRP/L1-SINR associated with a UE initiated beam report) have changed since the last transmitted UE initiated beam report.
  • Embodiment 18 The method of any of previous embodiments, wherein further comprising determining if an event for a UE initiated beam report has occurred based on one or more of the following criteria:
  • the difference in performance between the serving beam and the best beam reported in the last UE initiated beam report has changed (increase and/or decreased) more than a threshold.
  • Embodiment 19 The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Embodiment 20 A method performed by a network node, the method comprising one or more of the following: transmitting to a UE a configuration of a plurality of DL RSs (or beams) for beam measurements and UE initiated beam reporting. (Step A, 410); receiving information about at least one candidate target beam and its related measurements when one or more events have occurred. (Step B, 420); receiving information about at least one candidate target beam and its related measurements when one or more events have occurred. (Step C, 430).
  • Embodiment 21 The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • a user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 23 A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 24 A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • Embodiment 25 A host configured to operate in a communication system to provide an over- the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over- the-top
  • Embodiment 26 The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • Embodiment 27 A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • Embodiment 28 The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Embodiment 29 The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 30 A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • Embodiment 31 The communication system of the previous embodiment, further comprising: the network node; and/or the UE.
  • Embodiment 32 A host configured to operate in a communication system to provide an over- the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over- the-top
  • the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 34 The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Embodiment 35 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.
  • UE user equipment
  • Embodiment 36 The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.
  • Embodiment 37 A host configured to operate in a communication system to provide an over- the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host.
  • OTT over- the-top
  • Embodiment 38 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • Embodiment 39 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 40 A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.
  • UE user equipment
  • Embodiment 41 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.
  • Embodiment 42 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Embodiment 43 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • a host configured to operate in a communication system to provide an over- the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • OTT over- the-top
  • Embodiment 44 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • Embodiment 45 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 46 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • UE user equipment
  • Embodiment 47 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 48 The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Landscapes

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

Abstract

L'invention concerne des systèmes et des procédés qui se rapportent à un rapport de faisceau initié par un équipement utilisateur. Un procédé mis en œuvre par un équipement utilisateur (UE) comprend les étapes consistant à : recevoir du réseau (NW) une configuration d'une pluralité de RS DL (ou faisceaux) pour des mesures de faisceaux et un signalement prédictif de faisceaux, déterminer au moins un faisceau cible candidat parmi la pluralité de RS DL (ou faisceaux) sur la base de mesures sur la pluralité de RS DL (ou faisceaux), l'envoi d'un message au NW concernant le ou les faisceaux candidats (et ses valeurs de mesure associées) lorsqu'un ou plusieurs événements se produisent, la réception d'une indication de commutation de faisceau provenant du NW pour commuter vers l'un des faisceaux candidats. L'invention concerne également des modes de réalisation correspondants d'un UE et d'un nœud de réseau, ainsi qu'un procédé de nœud de réseau.
PCT/IB2025/051632 2024-02-16 2025-02-14 Rapport de faisceau initié par équipement utilisateur sur la base d'une prédiction de faisceau Pending WO2025172940A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463554474P 2024-02-16 2024-02-16
US63/554,474 2024-02-16

Publications (1)

Publication Number Publication Date
WO2025172940A1 true WO2025172940A1 (fr) 2025-08-21

Family

ID=94824045

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2025/051632 Pending WO2025172940A1 (fr) 2024-02-16 2025-02-14 Rapport de faisceau initié par équipement utilisateur sur la base d'une prédiction de faisceau

Country Status (1)

Country Link
WO (1) WO2025172940A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018232090A1 (fr) * 2017-06-14 2018-12-20 Idac Holdings, Inc. Gestion de faisceau unifié dans un réseau sans fil
US20190319686A1 (en) * 2016-07-20 2019-10-17 Wei CHEN, IV Mobility for radio devices using beamforming and selection
US20220338270A1 (en) * 2014-11-26 2022-10-20 Idac Holdings, Inc. Initial access in high frequency wireless systems
US20230025432A1 (en) * 2019-12-10 2023-01-26 Telefonaktiebolaget Lm Ericsson (Publ) Methods, ue and first network node for handling mobility information in a communications network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220338270A1 (en) * 2014-11-26 2022-10-20 Idac Holdings, Inc. Initial access in high frequency wireless systems
US20190319686A1 (en) * 2016-07-20 2019-10-17 Wei CHEN, IV Mobility for radio devices using beamforming and selection
WO2018232090A1 (fr) * 2017-06-14 2018-12-20 Idac Holdings, Inc. Gestion de faisceau unifié dans un réseau sans fil
US20230025432A1 (en) * 2019-12-10 2023-01-26 Telefonaktiebolaget Lm Ericsson (Publ) Methods, ue and first network node for handling mobility information in a communications network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 18)", 15 January 2024 (2024-01-15), XP052595208, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/Specifications/202312_final_specs_after_RAN_102/38331-i00.zip 38331-i00.docx> [retrieved on 20240115] *

Similar Documents

Publication Publication Date Title
WO2023211356A1 (fr) Surveillance de fonctionnalité d&#39;apprentissage automatique d&#39;équipement utilisateur
WO2023191682A1 (fr) Gestion de modèles d&#39;intelligence artificielle/d&#39;apprentissage machine entre des nœuds radio sans fil
EP4569902A1 (fr) Mesures de csi pour mobilité intercellulaire
US12171014B2 (en) Machine learning assisted user prioritization method for asynchronous resource allocation problems
US20250274346A1 (en) Network slicing fixed wireless access (fwa) use case
EP4566355A1 (fr) Économie d&#39;énergie de réseau dans un ng-ran scindé
EP4569854A1 (fr) Signalisation de réseau de rapport de pscell réussie
WO2025172940A1 (fr) Rapport de faisceau initié par équipement utilisateur sur la base d&#39;une prédiction de faisceau
WO2024138619A1 (fr) Procédés et appareils de communication sans fil
US20240334226A1 (en) Early radio measurement relaxation reporting
WO2024040388A1 (fr) Procédé et appareil de transmission de données
US20250047393A1 (en) Efficient inter-cell l1-rsrp measurement and reporting
US20240259921A1 (en) Signalling Approaches for Disaster PLMNS
US20240333621A1 (en) Boost enhanced active measurement
WO2024176189A1 (fr) Configuration pour déclencher un rapport de qoe visible de ran
WO2024241178A1 (fr) Fonction d&#39;identification de tâche de gestion de réseau
WO2023211347A1 (fr) États de déclenchement apériodiques inactifs pour économie d&#39;énergie
WO2025172756A1 (fr) Configuration et rapport améliorés de mesures de mode de veille/inactif
WO2024210795A1 (fr) Procédure de mobilité d&#39;inactivité/inactif pour résilience temporelle
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2025105998A1 (fr) Gestion de collecte de données
WO2024210805A1 (fr) Systèmes et procédés de négociation d&#39;informations de communication sensible au temps
WO2024210787A1 (fr) Informations de capacité d&#39;équipement utilisateur relatives à un temps de syntonisation de fréquence radio
WO2024144446A1 (fr) Optimisation de plan de commande pendant un changement d&#39;amf
WO2025178538A1 (fr) Procédés de sélection et de configuration de ressources de mesure sur la base de ressources de prédiction configurées pour des prédictions de mesure radio aiml

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

Country of ref document: EP

Kind code of ref document: A1