WO2023209135A1 - Indication de configuration de transmission dans un réseau de communication - Google Patents

Indication de configuration de transmission dans un réseau de communication Download PDF

Info

Publication number
WO2023209135A1
WO2023209135A1 PCT/EP2023/061201 EP2023061201W WO2023209135A1 WO 2023209135 A1 WO2023209135 A1 WO 2023209135A1 EP 2023061201 W EP2023061201 W EP 2023061201W WO 2023209135 A1 WO2023209135 A1 WO 2023209135A1
Authority
WO
WIPO (PCT)
Prior art keywords
report
communication device
apply
message
tci state
Prior art date
Application number
PCT/EP2023/061201
Other languages
English (en)
Inventor
Daniele DAVOLI
Andreas Nilsson
Claes Tidestav
Siva Muruganathan
Pradeepa Ramachandra
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023209135A1 publication Critical patent/WO2023209135A1/fr

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/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection

Definitions

  • the present application relates generally to a communication network, and relates more particularly to a transmission configuration indication in such a network.
  • a communication network may configure a communication device to provide a report to the communication network, e.g., reporting a beam on which the communication device prefers to transmit and/or receive.
  • the communication network may configure the communication device to provide such a report periodically, or may instead request the report aperiodically.
  • the communication network may send a beam update signal to the communication device, e.g., via a so-called transmission configuration indication (TCI) field in a downlink control information (DCI) message.
  • TCI transmission configuration indication
  • DCI downlink control information
  • Some embodiments herein facilitate device-initiated beam reporting in order to mitigate the problems mentioned above.
  • the communication network may exploit a previously sent beam report for indicating on which beam the communication device should perform subsequent transmission and/or reception. These and other embodiments may thereby provide beam update with reduced delay and/or reduced signaling overhead.
  • embodiments herein include a method performed by a communication device configured for use in a communication network.
  • the method comprises transmitting a report to a network node in the communication network.
  • the method also comprises receiving, from the network node, a message that refers to the report to indicate which transmission configuration indication, TCI, state the communication device is to apply for subsequent transmission and/or reception.
  • the report reports a reference signal, RS, or a synchronization signal block, SSB.
  • the reported RS or SSB is transmitted or received on a beam.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting a result of a measurement performed on the RS or SSB. Additionally or alternatively, the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting a selection or preference of the RS or SSB by the communication device.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting occurrence of an event associated with the RS or SSB.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating that the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating an RS or SSB reported by the report is associated with a TCI state that the communication device is to apply.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • the report reports multiple RSs or multiple SSBs.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple RSs, or which of the multiple SSBs, reported by the report is associated with the TCI state that the communication device is to apply.
  • the method further comprises making a decision as to whether or not to apply the TCI state indicated by the message based on whether or not the RS or SSB indicated by the message is activated.
  • the method further comprises making a decision as to whether or not to apply the TCI state indicated by the message based on whether or not the RS or SSB indicated by the message has been triggered within a defined interval of time.
  • the method further comprises applying or not applying the TCI state indicated by the message in accordance with the decision.
  • the report reports a beam. In one or more of these embodiments, the report reports a beam by reporting an identifier of the beam and reporting a result of a measurement performed on the beam. Additionally or alternatively, the report reports a beam by reporting an identifier of the beam and reporting a selection or preference of the beam by the communication device. Additionally or alternatively, the report reports a beam by reporting occurrence of an event associated with the beam. In one or more of these embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating that the communication device is to apply a TCI state associated with a beam reported by the report.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating a beam reported by the report is associated with a TCI state that the communication device is to apply. In one or more of these embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with a beam reported by the report. In one or more of these embodiments, the report reports multiple beams. In some embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple beams reported by the report is associated with the TCI state that the communication device is to apply.
  • the message indicates whether the communication device is to apply the TCI state for a downlink beam pair, an uplink beam pair, or both the downlink beam pair and the uplink beam pair.
  • the message indicates whether the communication device is to apply the TCI state for reception of one or more downlink signals or channels, for transmission of one or more uplink signals or channels, or both for reception of one or more downlink signals or channels and for transmission of one or more uplink signals or channels.
  • the TCI state indicated by the message is associated with a cell that is different from a cell with which the report is associated.
  • the message indicates which type of report the message is for. In some embodiments, the message indicates which serving cell, which bandwidth part, or which report configuration the message is for.
  • the message is or is included in a downlink control information, DCI, message.
  • the message is or is included in a medium access control, MAC, message.
  • the message is a single bit field.
  • the message is indicated by a TCI field.
  • the method further comprises receiving signaling indicating whether or not the TCI field refers to the report to indicate which TCI state the communication device is to apply.
  • the report is a device-initiated report and/or an event-triggered report.
  • the method further comprises autonomously initiating or triggering the report.
  • the method further comprises detecting occurrence of an event based on a result of a measurement performed by the communication device.
  • the report is transmitted responsive to detecting the occurrence of the event.
  • the message indicates when the communication device is to apply the TCI state. In some embodiments, the method further comprises receiving signaling indicating when the communication device is to apply the TCI state. In one or more of these embodiments, the signaling is RRC signaling.
  • the method further comprises applying the TCI state for subsequent transmission and/or reception.
  • the method further comprises making a decision as to whether or not to apply the TCI state indicated by the message, based on an amount of delay between transmitting the report and receiving the message.
  • the method further comprises applying or not applying the TCI state indicated by the message in accordance with the decision.
  • making the decision comprises, if the amount of the delay is less than a threshold, deciding not to apply the TCI state.
  • making the decision comprises, if the amount of the delay is more than the threshold, deciding to apply the TCI state.
  • the method further comprises determining the threshold based on whether or not the message indicates a downlink reference signal or beam associated with a serving cell.
  • the method further comprises determining the threshold based on whether or not the message indicates a downlink reference signal or beam that has been explicitly configured for beam reporting. In one or more of these embodiments, the method further comprises transmitting capability signaling that indicates different thresholds according to which the decision is to be made for downlink reference signals or beams that are or are not associated with a serving cell, respectively.
  • the message is a response to the report.
  • the message indicates to which report, or to which type of report, the message refers for indicating which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • the report is the last report transmitted.
  • the message refers to the last report to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • the report is the last report of a certain type transmitted.
  • the message refers to the last report of the certain type to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • the method further comprises providing user data and forwarding the user data to a host computer via the transmission to a base station.
  • inventions herein include a method performed by a network node configured for use in a communication network.
  • the method comprises receiving a report from a communication device.
  • the method also comprises transmitting, to the communication device, a message that refers to the report to indicate which transmission configuration indication, TCI, state the communication device is to apply for subsequent transmission and/or reception.
  • the report reports a reference signal, RS, or a synchronization signal block, SSB.
  • the reported RS or SSB is transmitted or received on a beam.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting a result of a measurement performed on the RS or SSB.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting a selection or preference of the RS or SSB by the communication device. Additionally or alternatively, the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting occurrence of an event associated with the RS or SSB.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating that the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating an RS or SSB reported by the report is associated with a TCI state that the communication device is to apply.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • the report reports multiple RSs or multiple SSBs.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple RSs, or which of the multiple SSBs, reported by the report is associated with the TCI state that the communication device is to apply.
  • up to N RSs or SSBs are reportable by the report, and wherein the message comprises a bitfield with a length of ceil(log 2 (N+1)).
  • the report reports a beam. In one or more of these embodiments, the report reports a beam by reporting an identifier of the beam and reporting a result of a measurement performed on the beam. Additionally or alternatively, the report reports a beam by reporting an identifier of the beam and reporting a selection or preference of the beam by the communication device. Additionally or alternatively, the report reports a beam by reporting an identifier of the beam and reporting occurrence of an event associated with the beam.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating that the communication device is to apply a TCI state associated with a beam reported by the report.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating a beam reported by the report is associated with a TCI state that the communication device is to apply. In one or more of these embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with a beam reported by the report. In one or more of these embodiments, the report reports multiple beams. In some embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple beams reported by the report is associated with the TCI state that the communication device is to apply.
  • the message indicates whether the communication device is to apply the TCI state for a downlink beam pair, an uplink beam pair, or both the downlink beam pair and the uplink beam pair.
  • the message indicates whether the communication device is to apply the TCI state for reception of one or more downlink signals or channels, for transmission of one or more uplink signals or channels, or both for reception of one or more downlink signals or channels and for transmission of one or more uplink signals or channels.
  • the TCI state indicated by the message is associated with a cell that is different from a cell with which the report is associated.
  • the message indicates which type of report the message is for.
  • the message indicates which serving cell, which bandwidth part, or which report configuration the message is for.
  • the message is or is included in a downlink control information, DCI, message.
  • the message is or is included in a medium access control, MAC, message
  • the message is a single bit field.
  • the message is indicated by a TCI field.
  • the method further comprises receiving signaling indicating whether or not the TCI field refers to the report to indicate which TCI state the communication device is to apply.
  • the report is a device-initiated report and/or an event-triggered report.
  • the message indicates when the communication device is to apply the TCI state.
  • the method further comprises transmitting, to the communication device, signaling indicating when the communication device is to apply the TCI state.
  • the signaling is RRC signaling.
  • the message indicates to which report, or to which type of report, the message refers for indicating which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • the report is the last report received from the communication device. In this case, the message refers to the last report to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception. In some embodiments, the report is the last report of a certain type received from the communication device. In this case, the message refers to the last report of the certain type to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs.
  • embodiments herein include a communication device configured for use in a communication network.
  • the communication device is configured to transmit a report to a network node in the communication network.
  • the communication device is also configured to receive, from the network node, a message that refers to the report to indicate which transmission configuration indication, TCI, state the communication device is to apply for subsequent transmission and/or reception.
  • a network node configured for use in a communication network.
  • the network node is configured to receive a report from a communication device.
  • the network node is also configured to transmit, to the communication device, a message that refers to the report to indicate which transmission configuration indication, TCI, state the communication device is to apply for subsequent transmission and/or reception.
  • Figure 1 is a block diagram of a communication network in accordance with some embodiments.
  • Figure 2 is a logic flow diagram of a two-step procedure related to TCI state update according to some embodiments.
  • FIG. 3 is a block diagram of a structure of a Medium Access Control (MAC) Control Element (CE) for activating/deactivating TCI states for user equipment (UE) specific Physical Downlink Shared Channel (PDSCH) according to some embodiments.
  • MAC Medium Access Control
  • CE Control Element
  • FIG. 4 is a block diagram of a Downlink Control Information (DCI) indication according to some embodiments.
  • DCI Downlink Control Information
  • FIG. 5 is a block diagram of a TCI codepoint for joint TCI states according to some embodiments.
  • FIG. 6 is a block diagram of a TCI codepoints for separate downlink I uplink TCI states according to other embodiments.
  • Figure 7 is a call flow diagram of a UE-initiated beam reporting procedure and the corresponding beam report response procedure according to some embodiments.
  • Figure 8 is a block diagram of a beam report response signaled in a MAC CE according to some embodiments.
  • Figure 9 is a block diagram of a beam report response signaled in a MAC CE according to other embodiments.
  • Figure 10 is a logic flow diagram of a method performed by a communication device according to some embodiments.
  • Figure 11 is a logic flow diagram of a method performed by a network node according to some embodiments.
  • Figure 12 is a block diagram of a communication device according to some embodiments.
  • Figure 13 is a block diagram of a network node according to some embodiments.
  • Figure 14 is a block diagram of a communication system in accordance with some embodiments.
  • Figure 15 is a block diagram of a user equipment according to some embodiments.
  • Figure 16 is a block diagram of a network node according to some embodiments.
  • Figure 17 is a block diagram of a host according to some embodiments.
  • Figure 18 is a block diagram of a virtualization environment according to some embodiments.
  • Figure 19 is a block diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • FIG. 1 shows a communication network 10 according to some embodiments.
  • the communication network 10 includes a network node 14 that provides communication service to a communication device 12, e.g., a user equipment (UE).
  • the network node 14 may for instance be a radio network node, such as a base station, or be, control, or otherwise be associated with a transmission reception point (TRP).
  • TRP transmission reception point
  • the network node 14 may provide such communication service to the communication device 12 in the capacity as a serving network node, e.g., that provides one or more serving cells of the communication device 12.
  • the communication device 12 transmits a report 18 to the network node 14.
  • the report 18 reports a reference signal (RS) or a synchronization signal block (SSB), e.g., as received by the communication device 12.
  • the report 18 may for example include an identity (ID) 19 that identifies a RS or SSB being reported.
  • the RS or SSB reported is reported as being preferred or selected by the communication device 12 from among multiple candidate RS or SSB.
  • the RS or SSB is reported in the sense that the report 18 reports the result of a measurement performed on the RS or SSB, e.g., a signal measurement such as a signal strength measurement or a signal quality measurement.
  • the report 18 in these and other cases may be referred to as a measurement report.
  • the RS or SSB is reported in the sense that the report 18 reports the occurrence of an event associated with the RS or SSB, e.g., where the event may be that the result of a measurement on the RS or SSB has exceeded a threshold.
  • the report 18 may be a device-initiated report and/or an event-triggered report. That is, rather than being triggered or initiated periodically according to a defined period, the report 18 may be initiated or triggered autonomously (at any time) by the communication device 12. Moreover, rather than being requested aperiodically by the network node 14, the report 18 may be sent by the communication device 12 in an unsolicited manner, i.e., not in response to a specific request for the report 18 from the network node 14. In one embodiment, for example, the communication device 12 detects occurrence of an event based on the result of a measurement performed by the communication device 12, and transmits the report 18 responsive to detecting the occurrence of that event.
  • the report 18 is in some sense a beam report.
  • Figure 1 for example shows that the network node 14 may transmit different RS or SSB on different beams.
  • network node 14 transmits RS or SSB 15-1 on beam 17-1 , transmits RS or SSB 15-2 on beam 17-2, and transmits RS or SSB 15-3 on beam 17-3.
  • the report 18 reports one of the RSs or SSBs 15-1 , 15-2, or 15-3, as received and/or measured by the communication device 12 on a respective one of the beams 17-1 , 17-2, or 17-3.
  • the ID 19 in this case explicitly identifies a certain one of the RSs or SSBs 15-1 , 15-2, or 15-3, but implicitly reports a certain one of the beams 17-1 , 17-2, or 17-3 by way of the association between the RSs/SSBs and the beams.
  • the ID 19 explicitly identifies a certain one of the beams 17-1 , 17-2, or 17-3, e.g., via a beam identity.
  • the report 18 may effectively report a result of a measurement performed on the beam, a selection or preference of the beam by the communication device 12, and/or occurrence of an event associated with the beam.
  • TCI states 16 may be configured and/or activated for communication between the communication device 12 and the network node 14.
  • the network node 14 may for example transmit signaling, e.g., radio resource control (RRC) signaling, configuring the TCI state(s) 16.
  • RRC radio resource control
  • each TCI state 16-1 ...16-N contains quasi co-location (QCL) information related to one or more RSs, e.g., as defined in 3GPP TS 38.331 v17.0.0.
  • QCL quasi co-location
  • the QCL information may for example be for configuring a QCL relationship between the one or more RSs and the demodulation reference signal (DMRS) ports of a downlink data channel, the DMRS ports of a downlink control channel, or the channel state information (CSI) RS ports of a CSI-RS resource.
  • DMRS demodulation reference signal
  • CSI channel state information
  • the communication device 12 may apply one of the TCI state(s) 16 for transmission and/or reception, e.g., of one or more physical channels or signals.
  • Application of a TCI state for transmission and/or reception may mean performing the transmission and/or reception on the basis of the QCL relationship associated with that TCI state.
  • the network node 14 indicates which of the TCI state(s) 16 the communication device 12 is to apply for subsequent transmission and/or reception.
  • the network node 14 may do so via a TCI state field, e.g., of a downlink control information (DCI) message, that explicitly indicates an index for whichever of the TCI state(s) 16 the communication device 12 is to apply.
  • the TCI state field may be sized to indicate any of the possible indices of the TCI state(s) 16 that are configured and/or activated.
  • the network node 14 is additionally or alternatively configured to refer to the report 18 to indicate which TCI state the communication device 12 is to apply for subsequent transmission and/or reception.
  • the network node 14 transmits a message 20 to the communication device 12, e.g., after receiving the report 18.
  • This message 20 refers to the report 18 to indicate which TCI state 16 the communication device 12 is to apply for subsequent transmission and/or reception.
  • some embodiments herein indicate the TCI state to apply in an efficient way, e.g., so as to reduce signaling overhead.
  • some embodiments herein reduce the amount of delay for the network node 14 to update the TCI state in which the communication device 12 is to apply.
  • the message 18 refers to the report 18 because the report 18 is the last report that the communication device 12 transmitted, e.g., of any type or of a certain type. In this case, the message 18 refers to the last report that the communication device 12 transmitted, e.g., of any type or of a certain type. In other embodiments, the message 18 refers to the report 18 because the message 18 indicates an identifier or index associated with that report 18. In these and other embodiments, the message 18 in some sense may be viewed as being a response to the report 18.
  • the message 20 refers to the report 18 to indicate which TCI state the communication device 12 is to apply by indicating that the communication device 12 is to apply a TCI state associated with an RS or SSB reported by the report 18. In other embodiments, the message 20 refers to the report 18 to indicate which TCI state the communication device 12 is to apply by indicating an RS or SSB reported by the report 18 is associated with a TCI state that the communication device 12 is to apply.
  • the message 20 refers to the report 18 to indicate which TCI state the communication device 12 is to apply by indicating whether or not the communication device 12 is to apply a TCI state associated with an RS or SSB reported by the report 18.
  • the report 18 reports multiple RSs or multiple SSBs
  • the message 20 refers to the report 18 to indicate which TCI state the communication device 12 is to apply by indicating which of the multiple RSs, or which of the multiple SSBs, reported by the report 18 is associated with the TCI state that the communication device 12 is to apply.
  • the message 20 may refer to the report 18 to indicate which TCI state the communication device 12 is to apply by indicating that the communication device 12 is to apply a TCI state associated with a beam reported by the report 18.
  • the message 20 may refer to the report 18 to indicate which TCI state the communication device 12 is to apply by indicating a beam reported by the report 18 is associated with a TCI state that the communication device 12 is to apply.
  • the message 20 refers to the report 18 to indicate which TCI state the communication device 12 is to apply by indicating whether or not the communication device 12 is to apply a TCI state associated with a beam reported by the report 18.
  • the message 20 may refer to the report 18 to indicate which TCI state the communication device 12 is to apply by indicating which of the multiple beams reported by the report 18 is associated with the TCI state that the communication device 12 is to apply.
  • a TCI state is a TCI state of an NR network
  • the communication device 12 is a user equipment (UE)
  • the network node 14 is a base station in the form of a gNB
  • the report 18 is a beam report
  • the message 20 is a beam report response.
  • Some embodiments herein are applicable in an NR network where several signals can be transmitted from different antenna ports of the same base station. These signals can have the same large-scale properties such as Doppler shift/spread, average delay spread, or average delay. These antenna ports are then said to be quasi co-located (QCL).
  • QCL quasi co-located
  • the UE can estimate that parameter based on one of the antenna ports and apply that estimate for receiving signals on the other antenna port.
  • a certain parameter e.g., Doppler spread
  • CSI-RS for a tracking RS (TRS) and the Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS).
  • TRS tracking RS
  • PDSCH Physical Downlink Shared Channel
  • DMRS Physical Downlink Shared Channel
  • QCL QCL relations between a transmitted source RS and transmitted target reference signal (RS) are defined:
  • Type A ⁇ Doppler shift, Doppler spread, average delay, delay spread ⁇
  • Type B ⁇ Doppler shift, Doppler spread ⁇
  • Type C ⁇ average delay, Doppler shift ⁇
  • Type D ⁇ Spatial Rx parameter ⁇ QCL type D facilitates beam management with analog beamforming and is known as spatial QCL. If two transmitted antenna ports are spatially QCL, the UE can use the same receive (Rx) beam to receive them. This is helpful for a UE that uses analog beamforming to receive signals, since the UE needs to adjust its RX beam in some direction prior to receiving a certain signal. If the UE knows that the signal is spatially QCL with some other signal it has received earlier, then it can safely use the same RX beam to receive also this signal. Note that for beam management, the discussion mostly revolves around QCL Type D, but it is also necessary to convey a Type A QCL relation for the RSs to the UE, so that it can estimate all the relevant large-scale parameters.
  • this is achieved by configuring the UE with a channel state information (CSI) reference signal (RS), CSI-RS, for tracking (TRS) for time/frequency offset estimation.
  • CSI channel state information
  • RS reference signal
  • TRS tracking
  • the UE would have to receive it with a sufficiently good signal-to-interference-noise-ratio (SINR). In some cases, this means that the TRS must be transmitted in a suitable beam to a certain UE.
  • SINR signal-to-interference-noise-ratio
  • the UE in some embodiments can be configured (e.g., through radio resource control (RRC) signaling) with TCI (Transmission Configuration Indicator) states, e.g., up to 128 TCI states.
  • RRC radio resource control
  • TCI state information element is shown below, e.g., consistent with 3GPP TS 38.331 V17.0.0.
  • TCI-State :: SEQUENCE ⁇ tci-Stateld TCI-Stateld, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info
  • QCL-Info :: SEQUENCE ⁇ cell ServCelllndex bwp-ld BWP-ld referencesignal CHOICE ⁇ csi-rs NZP-CSI-RS-Resourceld, ssb SSB-lndex
  • each TCI state contains QCL information related to one or two RSs.
  • a TCI state may contain CSI-RS1 associated with QCL Type A and CSI-RS2 associated with QCL TypeD.
  • a third RS e.g., the Physical Downlink Control Channel (PDCCH) DMRS
  • PDCCH Physical Downlink Control Channel
  • a first list of available TCI states is configured for PDSCH
  • a second list of TCI states is configured for PDCCH.
  • Each TCI state contains a pointer, known as TCI State ID, which points to the TCI state.
  • the network in some embodiments may activate, via a Medium Access Control (MAC) Control Element (CE), one TCI state for PDCCH (i.e., provides a TCI for PDCCH) and up to eight TCI states for PDSCH.
  • the number of active TCI states the UE supports may be a UE capability, e.g., with a maximum of 8.
  • a UE has 4 activated TCI states (from a list of totally 64 configured TCI states). Hence, 60 TCI states are inactive for this particular UE and the UE need not be prepared to have large scale parameters estimated for those inactive TCI states. But the UE continuously tracks and updates the large scale parameters for the RSs in the 4 active TCI states.
  • the DCI contains a pointer to one of the activated TCI states. The UE then knows which large scale parameter estimate to use when performing PDSCH DMRS channel estimation and thus PDSCH demodulation.
  • the UE can use any of the currently activated TCI states, it is sufficient to use DCI signaling.
  • none of the source RSs in the currently activated TCI states can be received by the UE, i.e., when the UE moves out of the beams in which the source RSs in the activated TCI states are transmitted.
  • the gNB may have to activate new TCI states. If the number of activated TCI states is fixed, the gNB may also have to deactivate one or more of the currently activated TCI states.
  • a two-step procedure related to TCI state update in this regard is depicted in Figure 2.
  • the gNB determines whether or not there is a need to update a current TCI state of the UE (Block 30). If so (YES at Block 30), the gNB selects a new TCI state to be updated with DCI (Block 32). The gNB next determines whether there is a need to activate a new set of TCI states, e.g., given the new TCI state selected (Block 34). If so (YES at Block 34), the gNB activates a new set of TCI states using a MAC CE (Block 36).
  • the structure of the MAC CE for activating/deactivating TCI states for UE specific PDSCH is given in Figure 3, as one example.
  • the MAC CE contains the following fields (i) Serving Cell ID; (ii) bandwidth part (BWP) ID; and (iii) a variable number of fields Ti.
  • the Serving Cell ID field indicates the identity of the Serving Cell for which the MAC CE applies.
  • the length of the field is 5 bits.
  • the BWP ID field contains the ID corresponding to a downlink bandwidth part for which the MAC CE applies.
  • the BWP ID is given by the higher layer parameter BWP- ⁇ d, e.g., as specified in 3GPP TS 38.331 v17.0.0.
  • the length of the BWP ID field is 2 bits since a UE can be configured with up to 4 BWPs for DL.
  • the field 7 ⁇ indicates the activation/deactivation status of the TCI state with TCI State ID /. If the UE is not configured with a TCI state with TCI State ID /, the MAC entity shall ignore the field.
  • the 7 ⁇ field is set to "1" to indicate that the TCI state with TCI State ID / shall be activated and mapped to a codepoint of the DCI Transmission Configuration Indication field, e.g., as specified in 3GPP TS 38.214 v17.1 .0 /38.321 v17.0.0.
  • the field is set to "0" to indicate that the TCI state with TCI State ID / shall be deactivated and is not mapped to any codepoint of the DCI Transmission Configuration Indication field.
  • the codepoint to which the TCI State is mapped is determined by the ordinal position among all the TCI States with field set to "1 ". That is, the first TCI State with field set to "1” shall be mapped to the codepoint value 0 of DCI Transmission Configuration Indication field, the second TCI State with field set to "1" shall be mapped to the codepoint value 1 of DCI Transmission Configuration Indication field, and so on.
  • the maximum number of activated TCI states is 8.
  • the MAC-CE also includes a Reserved bit R. This bit is set to ‘O’ in NR Rel-15.
  • the TCI States Activation/Deactivation for UE- specific PDSCH MAC CE is identified by a MAC PDU subheader with logical channel ID (LCID), e.g., as specified in Table 6.2.1-1 of 3GPP TS 38.321 V17.0.0 (this table is reproduced below in Table 1).
  • LCID logical channel ID
  • the MAC CE for Activation/Deactivation of TCI States for UE- specific PDSCH has variable size.
  • the gNB can use DCI format 1_1 or 1_2 to indicate to the UE that it shall use one of the activated TCI states for the subsequent PDSCH reception.
  • the field being used in the DCI is Transmission configuration indication (TCI), which is 3 bits if tci- PresentlnDCI is “enabled”or tci-PresentForDCI-Format1-2-r16 is present respectively for DCI format 1_1 and DCI 1_2 by higher layer.
  • TCI Transmission configuration indication
  • a DCI code point 4 corresponds to TCI state 25
  • DCI code point 0 indicates the first TCI state index in the list of TCI states
  • DCI code point 1 indicates the second TCI state index in the list, and so on.
  • the TCI state framework is as specified for NR Rel-15/Rel-16.
  • the NR Rel-15/16 framework for beam management is based on the framework of spatial QCL assumptions and spatial relations in order to support, e.g., analog beamforming implementations at the UE and/or the network.
  • the framework allows great flexibility for the network (i.e., the gNB) to instruct the UE to receive signals from several directions and to transmit signals in several directions.
  • the uplink and downlink configurations are decoupled, e.g., there is no direct relation between the configured spatial QCL assumptions and the spatial relations.
  • downlink beam management is performed by conveying spatial QCL (‘Type D’) assumptions to the UE, which are conveyed in TCI states.
  • One TCI state contains one or two RSs, and each RS is associated with a QCL type.
  • the network configures the UE with a set of PDCCH TCI states by radio resource control (RRC), and then activates one TCI state per CORESET using a MAC CE.
  • RRC radio resource control
  • the network configures the UE with a set of PDSCH TCI states by RRC, and then activates up to 8 TCI states by MAC CE. After activation, the network dynamically indicates one of these activated TCI states using a TCI field in DCI when scheduling PDSCH.
  • the network may simplify the beam management by not setting the RRC parameter tci-PresentlnDCI (which is configured per ORESET) to enabled. In this case, the UE uses the same TCI state for PDSCH as for PDCCH.
  • uplink beam management is performed using configuration of spatial relations.
  • a spatial relation is defined at the UE side between a source RS and a target RS.
  • the source RS can be a received DL RS (SSB or CSI-RS) or an SRS.
  • the target RS can be a transmitted PUCCH DMRS or an SRS. Note that there is no direct configuration of the spatial relation for a PUSCH: the PUSCH follows the spatial relation of a PUCCH or an SRS.
  • the network configures the UE with a set of 8 spatial relations using RRC, and subsequently activates one of these spatial relations using MAC CE.
  • the spatial relation is defined per PUCCH resource.
  • Rel-16 enhancements were made such that spatial relation could be updated for a group of PUCCH resources using a single MAC-CE.
  • default spatial relation for PUCCH was introduced in Rel-16, such that when no spatial relation is configured/activated for a PUCCH resource, the UE uses the TCI state/QCL assumption of the CORESET with lowest ID, both to derive spatial relation and to derive path loss reference signal.
  • a PUSCH scheduled by DCI Format 0_1 is transmitted over the ports where a configured SRS resource may also be transmitted.
  • Either two (codebook-based) or four (non-codebook-based) SRS resources can be defined in the SRS resource set.
  • the network selects which SRS resource in the set should correspond to the PUSCH transmission (i.e., PUSCH is transmitted on the same ports as the selected SRS and using the spatial relation of the selected SRS) using the SRS resource indicator (SRI) field in DCI.
  • the spatial relation for the SRS resources in the set is provided either by RRC (for periodic or aperiodic SRS) or MAC-CE (for aperiodic or semi-persistent SRS).
  • SRS sounding reference signal
  • RRC for periodic SRS and aperiodic SRS
  • MAC CE aperiodic SRS or semi-persistent SRS
  • the Rel-15/Rel-16 framework provides the network (NW) with great flexibility in some areas, at the cost of quite some signalling overhead. These limitations are particularly noticeable and costly when UE movement is considered.
  • NW network
  • One example is that beam update using DCI can only be performed for PDSCH, and MAC-CE and/or RRC is required to update the beam for other reference signals/channels, which causes extra overhead and latency.
  • the specified beam management flexibility is not really needed, since the network will transmit to and receive from the UE using the same beam for both data and control.
  • TCI state for DL signals/channels and spatial relations for UL signals/channels complicates the implementations.
  • path loss reference signal used for UL power control.
  • NR only up to four path loss reference signals can be configured for a UE, which typically is significantly less than the number of beams a TRP at FR2 uses to cover the cell.
  • the path loss reference signal needs to be updated using MAC-CE and/or RRC, which introduces extra latency and overhead.
  • a new unified TCI state framework is specified, which aims to streamline the indication of transmit/receive spatial filter (and other QCL properties) to the UE by letting a single TCI state indicate QCL properties for multiple different DL and/or UL signals/channels.
  • the unified TCI state framework of Rel-17 can be RRC configured in one out of two modes of operation “Joint DL/UL TCI” or “Separate DL/UL TCI”.
  • Joint DL/UL TCI one common Joint TCI state is used for both DL and UL signals/channels.
  • Separate DL/UL TCI one common DL-only TCI state is used for DL channels/signals, and one common UL-only TCI state is used for UL signals/channels.
  • the common TCI state ID can be updated in a similar way as the TCI state ID is update for PDSCH in Rel-15/16, i.e., with one of two alternatives.
  • Two-stage is a first alternative. In two stage, RRC signaling is used to configure a number of TCI states in PDSCH-config, and MAC- CE is used to activate a single TCI state (that TCI state will then be applied).
  • Three-stage is a second alternative.
  • RRC signaling is used to configure a number of TCI state in PDSCH-config
  • MAC-CE is used to activate up to 8 TCI states
  • a 3-bit TCI state bitfield (consisting of up to 8 codepoints) in DCI is used to indicate one of the activate TCI states (that TCI state will then be applied)
  • a maximum of one Joint TCI state can be activated per TCI codepoint.
  • TCI codepoint is “1”
  • the UE should apply “Joint TCI state 7” as common QCL source for both DL and UL signals/channels.
  • up to two TCI states can be activated per TCI codepoint, one for DL signals/channels (DL-only TCI state) and one for UL signals/channels (UL-only TCI state).
  • TCI codepoint is “0”
  • the UE should apply “DL-only TCI state 3” as common QCL source for DL signals/channels, and not update the QCL source for UL signals channel.
  • the TCI codepoint is “7”
  • the UE should apply “UL-only TCI state 57” as QCL source for UL signals/channels, and not update the QCL source for DL signals/channel.
  • the TCI codepoint is “2”
  • Another the UE should apply “DL-only TCI state 9” as QCL source for DL signals/channels and apply “UL-only TCI state 1” as QCL source for UL signals/channels.
  • the existing DCI formats 1_1 and 1_2 in NR are reused (as in Rel-15/16 beam management framework) for beam indication, both with and without DL assignment.
  • ACK/NACK of the PDSCH can be used as indication of successful reception of beam indication.
  • a new ACK/NACK mechanism analogous to that for Semi-Persistent Scheduling (SPS) PDSCH release with both type-1 and type-2 HARQ-ACK codebook is used, where upon a successful reception of the beam indication DCI, the UE reports an ACK.
  • SPS Semi-Persistent Scheduling
  • the first slot to apply the indicated TCI state is at least Y symbols after the last symbol of the acknowledgment of the joint or separate DL/UL beam indication.
  • the Y symbols are configured by the gNB based on UE capability, which is also reported in units of symbols.
  • the large scale QCL properties are inferred from one source RS (qcl-Type1 only) or two source RSs (qcl-Type1 and qcl-Type2) analogous to Rel-15/16 beam management framework.
  • the UL spatial filter is derived from the spatial filter used to receive the source RS of DL QCL Type D.
  • the Joint/DL-only TCI state can provide common QCL information at least for UE-dedicated PDCCH, PDSCH, Aperiodic CSI-RS for CSI, and Aperiodic CSI-RS for beam management.
  • RRC configuration is used to indicate if a non-UE dedicated PDCCH/PDSCH, AP CSI- RS for CSI and beam management (BM) should follow the common beam or not.
  • Common beam here means that the same beam is used for receiving DL signals/channels that are indicated to follow the common beam.
  • a Rel-17 TCI state can be indicated as QCL source in a similar way as for Rel-15/16 beam management framework.
  • a Rel-17 TCI state can be configured in the parameter “qcl-InfoPeriodicCSI-RS” in “NZP-CSI-RS-Resource information element” as specified in 3GPP TS 38.331 V16.7.0.
  • the possible target and source RSs and corresponding QCL properties for that are supported for Joint/DL-only TCI state indication are summarized in Table 1.
  • Table 1 Possible configurations of target and source RSs and corresponding QCL properties for Joint/DL-only TCI state indication
  • the Joint/UL-only TCI state can provide common QCL information at least for (i) All or a subset of all PUCCH resources; (ii) Dynamic-grant/configured-grant PUSCH; and (iii) SRS for all usages (except for usage ‘positioning’).
  • RRC configuration is used to indicate if a SRS and PUCCH resource should follow the common beam or not.
  • Common beam here means that the same beam is used for transmitting UL signals/channels that are indicated to follow the common beam.
  • a Rel-17 TCI state can be used to indicate spatial relation instead of a DL/UL-RS which is used to indicate spatial relation for Rel-15/16 beam management framework.
  • a new RRC parameter in an SRS resource can be configured with a Rel-17 TCI state, and the UE will use that Rel-17 TCI state to determine the spatial relation for that SRS resource.
  • Any of the following reference signals can be used to indicate spatial relation for a UL signal/channel in Rel-17 TCI state framework: SSB, TRS (tracking reference signal), CSI-RS for beam management, and SRS with usage set to beam management.
  • inter-cell beam management is included in the Rel-17 TCI state framework to facilitate L1/L2 inter-cell mobility (to be specified for higher layers in NR Rel-18) as well as inter-cell multi-TRP (mTRP) operation.
  • L1/L2 inter-cell mobility to be specified for higher layers in NR Rel-18
  • mTRP inter-cell multi-TRP
  • a UE can be configured to measure and report Rel-15 L1-RSRP for synchronization signal block(s) (SSB(s)) associated with non-serving cells. Which serving cell an SSB is associated with is indicated by RRC signaling, where each SSB is paired with a Physical Cell ID (PCI). The maximum number of PCIs different from the serving cell that could be used for SSB measurement/reporting is up to UE capability and can be one of 0,1 ,2,3 and 7.
  • the beam indication for inter-cell beam management will work in the same way as for intra-cell Rel-17 unified TCI state framework, as described herein.
  • the DL QCL and UL spatial relation rules for inter-cell beam management will work in the same way as for intra-cell Rel-17 unified TCI state framework, as described herein.
  • L1- RSRP Layer 1 Reference Signal Received Power
  • Some embodiments herein implement Layer 1 Reference Signal Received Power (L1- RSRP) multi-beam measurement/reporting enhancements for inter-cell beam management and inter-cell mTRP.
  • Some embodiments for example support L1 -based event-driven beam reporting for inter-cell beam management and inter-cell mTRP.
  • Other embodiments herein support MAC CE based event-driven beam reporting for inter-cell beam management and intercell mTRP.
  • event-driven beam reporting is not supported for intercell beam management and inter-cell mTRP
  • Some embodiments herein provide beam management with reduced DL signaling to reduce latency.
  • UE-initiated beam selection/activation based on beam measurement and/or reporting (without beam indication or activation from NW) is supported, e.g., where such reporting of a selected or activated beam is an example of what the report 18 in Figure 1 reports in some embodiments.
  • Other embodiments herein support beam measurement/reporting/refinement/selection triggered by beam indication (without CSI request).
  • Yet other embodiments support aperiodic beam measurement/reporting based on multiple resource sets for reducing beam measurement latency.
  • UE-initiated beam selection such selection may be based on, e.g., contention-free random access (CFRA), contention-based random access (CBRA), UL configured grant (CG), MAC-CE or uplink control information (UCI).
  • CFRA contention-free random access
  • CBRA contention-based random access
  • CG UL configured grant
  • UCI uplink control information
  • the selected beam DL-only or DL/UL
  • an event-triggered UE beam report e.g., as an example of the report 18 in Figure 1.
  • the UE sends a CBRA to gNB and after CBRA, all the channels that a unified TCI is applied for should be based on the SSB/CSI-RS associated with the Physical Random Access Channel (PRACH).
  • UE initiated beam reporting may be based on the Physical Random Access Channel (PRACH) or UL CG, and DL beam selection.
  • a MAC CE on PUSCH is sent by UE to inform the appropriate DL/UL beam to gNB, where the MAC-CE may be analogous to a beam failure report (BFR) MAC-CE.
  • BFR beam failure report
  • the selected beam is reported by a NW-initialized beam report.
  • Rel-17 UE reporting (e.g., reporting layer 1 RSRP, L1-RSRP; layer 1 SINR, L1-SINR, etc.) is heretofore either configured periodically with a certain periodicity from the gNB or requested a-periodically from the gNB; once the gNB receives a report from the UE, the gNB then sends a beam update signal to the UE (e.g., via the TCI field in DCI which is used to update the TCI state). This can cause, especially in high mobility FR2 scenarios, either a delay in reporting with a loss in performance due to non-updated measurements or a high overhead.
  • Some embodiments herein facilitate UE-initiated beam reporting in order to mitigate the problems mentioned above.
  • Some embodiments for example provide signaling methods for indicating, based on a previous beam report, which beam a UE should apply for further communication, where the previous beam report was previously signaled from the UE to the network.
  • the beam report may be an example of the report 18 in Figure 1.
  • Some embodiments herein use DCI and/or MAC-CE signaling to convey the beam indication. Note here that indicating which beam the UE should apply may also be referred to as indicating which TCI state the UE should apply.
  • Certain embodiments may provide one or more of the following technical advantage(s). Some embodiments herein provide beam indication using pointer to a report (e.g., a measurement report). Some embodiments in doing so speeds up beam selections in an overhead efficient way.
  • a UE initiated beam reporting procedure and the corresponding beam report response procedure is specified as schematically illustrated in Figure 7.
  • the UE initiates a beam report, as an example of the report 18 in Figure 1.
  • the UE transmits the UE initiated beam report to the gNB.
  • the gNB signals the corresponding beam report response to the UE.
  • This beam report response is an example of the message 20 in Figure 1 .
  • the UE then performs actions according to the received beam reporting response.
  • a UE has reported a beam report to a transmission reception point (TRP) or gNB (where the beam report e.g., can be a UE initiated event-driven beam report or a beam report explicitly triggered by the gNB).
  • TRP transmission reception point
  • gNB gNode B
  • the response is signaled in a DCI.
  • a new bitfield is included in DCI format 1_0, 1_1 , and/or 1_2 which is used to carry the beam report response (BRR).
  • the new bitfield is a single-bit bitfield, and in case the bit is a 1 , the UE should apply, for subsequent transmissions and/or receptions of physical channels or reference signals, the TCI state associated with a DLRS indicated in the last transmitted beam report.
  • the UE in case the single-bit bitfield is toggled (i.e., has changed value from “0” to “1” or from “1” to “0”) compared to previous transmission of the same DCI format, the UE should apply the TCI state associated with a DL-RS indicated in the last beam report (where the beam report can be either UE initiated or triggered explicitly by the gNB).
  • the TCI (transmission configuration indication) field in DCI formats 1_1 or 1_2 may be reused for indicating the beam report response by reinterpreting the TCI field.
  • an indication e.g., a bit
  • the indication may be done by RRC signaling, MAC CE signaling, or DCI signaling (e.g., the indication is a new field in any one of the DCI formats 0_1 , 0_2, 1_1 , 1_2).
  • the TCI field is used to indicate the beam response. For instance, each bit in the TCI field may be used to indicate one of the DL-RSs indicated in the last beam report which indicates to the UE that the UE should apply the TCI state of the one of the DL-RSs indicated for subsequent transmissions and/or reception of physical channels or reference signals. For instance, if TCI field indicates 001 wherein the least significant bit set to 1 indicates that the UE should apply the TCI state of the 1 st DL-RS indicated in the last beam report.
  • TCI field indicates 010 wherein the second bit set to 1 indicates that the UE should apply the TCI state of the 2 nd DLRS indicated in the last beam report. If TCI field indicates 100 wherein the most significant bit set to 1 indicates that the UE should apply the TCI state of the 3 rd DL-RS indicated in the last beam report. On the other hand, if the indication is set to a second value or if the indication is not configured (e.g., the bit is set to 0), then the TCI field is not used to indicate the beam response. In this case, the TCI field directly indicates one or more TCI states to be applied without referring to any DL-RS indicated in the last beam report.
  • the bitfield in DCI consists of multiple bits, and where different codepoints are used to indicate which of the DL-RSs that should be used to determine the applied TCI state.
  • a first codepoint “0” could indicate to the UE to not apply any new TCI state
  • a codepoint “1” could indicate to apply a TCI state associated with the a first DL-RS from the report (DL-RS1)
  • a codepoint “2” could indicate to apply a TCI state associated with the a second DL-RS from the report (DL-RS2)
  • a codepoint “3” could indicate to apply a TCI state associated with the a third DL-RS from the report (DL-RS3).
  • the size of the bitfield varies depending on the configured maximum number of DL-RS that can be included in the beam report.
  • the length of the bitfield is equal to cel(log2(N+1)), where N is equal to the configured maximum number of DL-RS that a UE can include in a beam report.
  • the UE in case the beam report includes one or more semi- persistent DL-RSs, and the gNB/TRP indicates one of the semi-persistent DL-RSs that is not activated, then the UE shall not apply the TCI state corresponding to the one semi-persistent DL-RS that is not activated. Instead, if the semi-persistent DL-RS is activated then the UE shall apply the TCI state corresponding to the semi-persistent DL-RS.
  • the UE behavior may be specified such that the UE expects the gNB/TRP to only indicate the semi-persistent DL-RSs that are currently activated in the beam report response.
  • the UE may not apply the TCI state corresponding to those DL-RSs that haven’t been triggered in the last X symbols/slots.
  • X serves the purpose of controlling how recently the aperiodic DL-RS was triggered in order for the DL-RS to be considered for TCI state update. For instance, if an aperiodic DL-RS was triggered more than X symbols/slots, the UE shall not apply the TCI state corresponding to that aperiodic DL-RS.
  • the UE behavior may be specified such that the UE expects the gNB/TRP to only indicate the aperiodic DL-RSs that were triggered within X symbols/slots in the beam report response.
  • the bitfield could include additional codepoints related to whether the UE only should update the TCI state associated with the DL beam pair link (i.e., only update the applied DL TCI state), or if the UE only should update the TCI state associated with the UL beam pair link (i.e., only update the applied UL TCI state), or if the UE should update the TCI states associated with both the DL and UL beam pair link (i.e., update the applied DL TCI state and UL TCI state).
  • multiple different kinds of beam reports might be configured for the UE.
  • the UE might be configured with gNB triggered beam reports, UE initiated beam reports, beam failure recovery reports, etc.
  • the beam report response also may include information about what kind of report the beam report response is associated with.
  • a single bit in the DCI is used to indicate if the beam report response is associated with a UE initiated beam report or a gNB triggered beam report.
  • the UE may be configured with one or more different UE initiated beam reports, and one or more gNB triggered beam reports.
  • a bitfield with multiple different codepoints may be used to indicate which of the one or more UE initiated beam reports and/or one or more gNB triggered beam reports, the beam report response is associated with.
  • the beam report response is signaled in MAC-CE instead of DCI.
  • the MAC-CE could be used to convey similar information as was described for DCI.
  • Figure 8 illustrates one schematic example of such a MAC-CE.
  • the field Sx indicates which of the up to N reported DL-RS that the UE should use for determining the new applied TCI state. For example, if SO is equal to 1 , it means that the UE should use the first DLRS in the beam report for determining the TCI state, if S1 is equal to 1 , it means that the UE should use the second DL-RS in the beam report for determining the TCI state, and so on. If all the SO to S4 is equal to 0 it means that the UE should not apply any new TCI state.
  • one or two of the R bitfields is used to indicate if the UE should update the TCI state for only a DL beam pair link (i.e., update a DL TCI state), or if the UE should update the TCI state only for an UL beam pair link (i.e., update an UL TCI state), or if the UE should update the TCI state for both a DL and UL beam pair link (i.e., update both a DL and an UL TCI state).
  • the UE may apply more than one TCI state (e.g., two TCI states).
  • the two of the S, fields may be indicated with values equal to 1 .
  • S1 and S2 are equal to 1 , it means that the UE should use the second and the third DL-RSs in the beam report for determining the two TCI states (i.e., TCI states corresponding to the second and third DL-RSs in the beam report).
  • the MAC-CE includes other information, like for example one or more of serving cell ID, report config ID, BWP ID. For instance, if there are beam reports for two or more serving cells, then including the serving cell ID in the beam report response helps tell the UE which serving cell the beam report response corresponds to.
  • the report configuration ID in the beam report response helps tell the UE which report configuration the beam report response corresponds to. If there are beam reports for two or more BWP, then including the BWP ID in the beam report response helps tell the UE which BWP the beam report response corresponds to.
  • Figure 9 illustrates another example of such a MAC-CE.
  • the field Sx indicates which of the up to N reported DL-RS for the DL beam pair link that the UE should use for determining a DL TCI state.
  • the field Tx indicates which of the up to N reported DL-RS for the UL beam pair link that the UE should use for determining a UL TCI state.
  • the MAC-CE includes other information, like for example one or more of serving cell ID, report config ID, BWP ID. For instance, if there are beam reports for two or more serving cells, then including the serving cell ID in the beam report response helps tell the UE which serving cell the beam report response corresponds to. If there are beam reports configured in two or more report configurations, then including the report configuration ID in the beam report response helps tell the UE which report configuration the beam report response corresponds to. If there are beam reports for two or more BWP, then including the BWP ID in the beam report response helps tell the UE which BWP the beam report response corresponds to.
  • the delay is pre-configured (for example included in the standards specification, or configured using RRC signaling). In one embodiment, the delay can be dynamically indicated, for example in a DCI and/or MAC-CE carrying the beam report response.
  • a timeline may be defined for when the UE can expect to receive a beam report response from the gNB/TRP.
  • ti time at which the UE sends the beam report
  • f 2 the time at which the UE receives the beam report response.
  • the motivation for introducing a timeline here is to give the gNB/TRP to give some time to receive and process the UE initiated beam report from the UE and then generate the beam report response.
  • This timeline can be referred to as beam report processing time. If the beam report processing time is denoted at To, then the associated UE behavior can be defined as follows.
  • the UE ignores the beam report response. This may correspond to no change in the TCI state to apply since the UE essentially ignores the beam report response as the timeline To is not met.
  • the UE receives the beam report response and follows the UE behavior defined according to the different embodiments above (i.e., applies a TCI state of a DL-RS in the beam report response).
  • different kinds of beam indexes are associated with different delays. For example, in case beam report response indicates a beam index (i.e., a DL.RS index) associated with a non-serving cell (e.g., a cell with different PCI compared to serving cell), then the delay should be longer compared to when the indicated beam index is associated with the serving cell. In one embodiment the delay depends on if the DL-RS has been explicitly configured for beam reporting or not, and if the DL-RS is not explicitly configured for beam reporting, then the UE applies a longer delay.
  • a beam index i.e., a DL.RS index
  • a non-serving cell e.g., a cell with different PCI compared to serving cell
  • the UE signals in UE capability signaling different delays for different kind of DL-RS indexes, for example one delay is related to beam indexes associated with serving cell, and another delay is related to beam indexes for non-serving cells.
  • the delay can for example be indicated in number of Orthogonal Frequency Division Multiplexing (OFDM) symbols or number of slots.
  • OFDM Orthogonal Frequency Division Multiplexing
  • Figure 10 depicts a method in accordance with particular embodiments.
  • the method is performed by a communication device 12 configured for use in a communication network 10.
  • the method includes transmitting a report 18 to a network node 14 in the communication network 10 (Block 1000).
  • the method further comprises autonomously initiating or triggering this report (Block 1005).
  • the method also includes receiving, from the network node 14, a message 20 that refers to the report 18 to indicate which transmission configuration indication (TCI) state 16-1 ...16-N the communication device 12 is to apply for subsequent transmission and/or reception (Block 1005).
  • TCI transmission configuration indication
  • the method also includes applying the TCI state for subsequent transmission and/or reception (Block 1020).
  • the report reports a reference signal, RS, or a synchronization signal block, SSB.
  • the reported RS or SSB is transmitted or received on a beam.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting a result of a measurement performed on the RS or SSB. Additionally or alternatively, the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting a selection or preference of the RS or SSB by the communication device.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting occurrence of an event associated with the RS or SSB.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating that the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating an RS or SSB reported by the report is associated with a TCI state that the communication device is to apply.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • the report reports multiple RSs or multiple SSBs.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple RSs, or which of the multiple SSBs, reported by the report is associated with the TCI state that the communication device is to apply.
  • the method further comprises making a decision as to whether or not to apply the TCI state indicated by the message based on whether or not the RS or SSB indicated by the message is activated.
  • the method further comprises making a decision as to whether or not to apply the TCI state indicated by the message based on whether or not the RS or SSB indicated by the message has been triggered within a defined interval of time.
  • the method further comprises applying or not applying the TCI state indicated by the message in accordance with the decision.
  • the report reports a beam. In one or more of these embodiments, the report reports a beam by reporting an identifier of the beam and reporting a result of a measurement performed on the beam. Additionally or alternatively, the report reports a beam by reporting an identifier of the beam and reporting a selection or preference of the beam by the communication device. Additionally or alternatively, the report reports a beam by reporting occurrence of an event associated with the beam. In one or more of these embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating that the communication device is to apply a TCI state associated with a beam reported by the report.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating a beam reported by the report is associated with a TCI state that the communication device is to apply. In one or more of these embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with a beam reported by the report. In one or more of these embodiments, the report reports multiple beams. In some embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple beams reported by the report is associated with the TCI state that the communication device is to apply. In some embodiments, the message indicates whether the communication device is to apply the TCI state for a downlink beam pair, an uplink beam pair, or both the downlink beam pair and the uplink beam pair.
  • the message indicates which type of report the message is for.
  • the message indicates which serving cell, which bandwidth part, or which report configuration the message is for.
  • the message is or is included in a downlink control information, DCI, message.
  • the message is or is included in a medium access control, MAC, message.
  • the message is a single bit field.
  • the message is indicated by a TCI field.
  • the method further comprises receiving signaling indicating whether or not the TCI field refers to the report to indicate which TCI state the communication device is to apply.
  • the report is a device-initiated report and/or an event-triggered report.
  • the method further comprises autonomously initiating or triggering the report.
  • the method further comprises detecting occurrence of an event based on a result of a measurement performed by the communication device.
  • the report is transmitted responsive to detecting the occurrence of the event.
  • the message indicates when the communication device is to apply the TCI state.
  • the method further comprises receiving signaling indicating when the communication device is to apply the TCI state.
  • the signaling is RRC signaling.
  • the method further comprises applying the TCI state for subsequent transmission and/or reception.
  • the method further comprises making a decision as to whether or not to apply the TCI state indicated by the message, based on an amount of delay between transmitting the report and receiving the message.
  • the method further comprises applying or not applying the TCI state indicated by the message in accordance with the decision.
  • making the decision comprises, if the amount of the delay is less than a threshold, deciding not to apply the TCI state.
  • making the decision comprises, if the amount of the delay is more than the threshold, deciding to apply the TCI state.
  • the method further comprises determining the threshold based on whether or not the message indicates a downlink reference signal or beam associated with a serving cell.
  • the method further comprises determining the threshold based on whether or not the message indicates a downlink reference signal or beam that has been explicitly configured for beam reporting. In one or more of these embodiments, the method further comprises transmitting capability signaling that indicates different thresholds according to which the decision is to be made for downlink reference signals or beams that are or are not associated with a serving cell, respectively.
  • the message is a response to the report.
  • the message indicates to which report, or to which type of report, the message refers for indicating which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • the report is the last report transmitted.
  • the message refers to the last report to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • the report is the last report of a certain type transmitted.
  • the message refers to the last report of the certain type to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • Figure 11 depicts a method in accordance with other particular embodiments.
  • the method is performed by a network node 14 configured for use in a communication network 10.
  • the method includes receiving a report 18 from a communication device 12 (Block 1100).
  • the method also includes transmitting, to the communication device 12, a message 20 that refers to the report 18 to indicate which transmission configuration indication (TCI) state 16-1 ...16-N the communication device 12 is to apply for subsequent transmission and/or reception (Block 1110).
  • TCI transmission configuration indication
  • the method also includes transmitting, to the communication device 12, signaling indicating when the communication device 12 is to apply the TCI state (Block 1120).
  • the report reports a reference signal, RS, or a synchronization signal block, SSB.
  • the reported RS or SSB is transmitted or received on a beam.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting a result of a measurement performed on the RS or SSB. Additionally or alternatively, the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting a selection or preference of the RS or SSB by the communication device.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting occurrence of an event associated with the RS or SSB.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating that the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating an RS or SSB reported by the report is associated with a TCI state that the communication device is to apply.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • the report reports multiple RSs or multiple SSBs.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple RSs, or which of the multiple SSBs, reported by the report is associated with the TCI state that the communication device is to apply.
  • up to N RSs or SSBs are reportable by the report, and wherein the message comprises a bitfield with a length of ceil(log 2 (N+1)).
  • the report reports a beam. In one or more of these embodiments, the report reports a beam by reporting an identifier of the beam and reporting a result of a measurement performed on the beam. Additionally or alternatively, the report reports a beam by reporting an identifier of the beam and reporting a selection or preference of the beam by the communication device. Additionally or alternatively, the report reports a beam by reporting an identifier of the beam and reporting occurrence of an event associated with the beam.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating that the communication device is to apply a TCI state associated with a beam reported by the report.
  • the message refers to the report to indicate which TCI state the communication device is to apply by indicating a beam reported by the report is associated with a TCI state that the communication device is to apply. In one or more of these embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with a beam reported by the report. In one or more of these embodiments, the report reports multiple beams. In some embodiments, the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple beams reported by the report is associated with the TCI state that the communication device is to apply.
  • the message indicates whether the communication device is to apply the TCI state for a downlink beam pair, an uplink beam pair, or both the downlink beam pair and the uplink beam pair.
  • the message indicates which type of report the message is for.
  • the message indicates which serving cell, which bandwidth part, or which report configuration the message is for.
  • the message is or is included in a downlink control information, DCI, message.
  • the message is or is included in a medium access control, MAC, message
  • the message is a single bit field.
  • the message is indicated by a TCI field.
  • the method further comprises receiving signaling indicating whether or not the TCI field refers to the report to indicate which TCI state the communication device is to apply.
  • the report is a device-initiated report and/or an event-triggered report.
  • the message indicates when the communication device is to apply the TCI state.
  • the method further comprises transmitting, to the communication device, signaling indicating when the communication device is to apply the TCI state.
  • the signaling is RRC signaling.
  • the message is a response to the report.
  • the message indicates to which report, or to which type of report, the message refers for indicating which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • the report is the last report received from the communication device.
  • the message refers to the last report to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • the report is the last report of a certain type received from the communication device.
  • the message refers to the last report of the certain type to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • Embodiments herein also include corresponding apparatuses.
  • Embodiments herein for instance include a communication device 12 configured to perform any of the steps of any of the embodiments described above for the communication device 12.
  • Embodiments also include a communication device 12 comprising processing circuitry and power supply circuitry.
  • the processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12.
  • the power supply circuitry is configured to supply power to the communication device 12.
  • Embodiments further include a communication device 12 comprising processing circuitry.
  • the processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12.
  • the communication device 12 further comprises communication circuitry.
  • Embodiments further include a communication device 12 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication device 12 is configured to perform any of the steps of any of the embodiments described above for the communication device 12.
  • Embodiments moreover include a user equipment (UE).
  • the UE comprises an antenna configured to send and receive wireless signals.
  • the UE also comprises 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 is configured to perform any of the steps of any of the embodiments described above for the communication device 12.
  • the UE also comprises 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.
  • the UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry.
  • the UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.
  • Embodiments herein also include a network node 14 configured to perform any of the steps of any of the embodiments described above for the network node 14.
  • Embodiments also include a network node 14 comprising processing circuitry and power supply circuitry.
  • the processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 14.
  • the power supply circuitry is configured to supply power to the network node 14.
  • Embodiments further include a network node 14 comprising processing circuitry.
  • the processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 14.
  • the network node 14 further comprises communication circuitry.
  • Embodiments further include a network node 14 comprising processing circuitry and memory.
  • the memory contains instructions executable by the processing circuitry whereby the network node 14 is configured to perform any of the steps of any of the embodiments described above for the network node 14.
  • the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry.
  • the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures.
  • the circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory.
  • the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • DSPs digital signal processors
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.
  • Figure 12 for example illustrates a communication device 12 as implemented in accordance with one or more embodiments.
  • the communication device 12 includes processing circuitry 1210 and communication circuitry 1220.
  • the communication circuitry 1220 e.g., radio circuitry
  • the processing circuitry 1210 is configured to perform processing described above, e.g., in Figure 10, such as by executing instructions stored in memory 1230.
  • the processing circuitry 1210 in this regard may implement certain functional means, units, or modules.
  • Figure 13 illustrates a network node 14 as implemented in accordance with one or more embodiments.
  • the network node 14 includes processing circuitry 1310 and communication circuitry 1320.
  • the communication circuitry 1320 is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology.
  • the processing circuitry 1310 is configured to perform processing described above, e.g., in Figure 11 , such as by executing instructions stored in memory 1330.
  • the processing circuitry 1310 in this regard may implement certain functional means, units, or modules.
  • a computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above.
  • a computer program in this regard may comprise one or more code modules corresponding to the means or units described above.
  • Embodiments further include a carrier containing such a computer program.
  • This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.
  • Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device.
  • This computer program product may be stored on a computer readable recording medium.
  • Figure 14 shows an example of a communication system 1400 in accordance with some embodiments.
  • the communication system 1400 includes a telecommunication network 1402 that includes an access network 1404, such as a radio access network (RAN), and a core network 1406, which includes one or more core network nodes 1408.
  • the access network 1404 includes one or more access network nodes, such as network nodes 1410a and 1410b (one or more of which may be generally referred to as network nodes 1410), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes 1410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1412a, 1412b, 1412c, and 1412d (one or more of which may be generally referred to as UEs 1412) to the core network 1406 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 1400 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 1400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1412 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 1410 and other communication devices.
  • the network nodes 1410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1412 and/or with other network nodes or equipment in the telecommunication network 1402 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 1402.
  • the core network 1406 connects the network nodes 1410 to one or more hosts, such as host 1416. 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 1406 includes one more core network nodes (e.g., core network node 1408) 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 1408.
  • 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 1416 may be under the ownership or control of a service provider other than an operator or provider of the access network 1404 and/or the telecommunication network 1402, and may be operated by the service provider or on behalf of the service provider.
  • the host 1416 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 1400 of Figure 14 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 1402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1402. For example, the telecommunications network 1402 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)ZMassive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 1412 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1404.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE 1412c and/or 1412d) and network nodes (e.g., network node 1410b).
  • the hub 1414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1414 may be a broadband router enabling access to the core network 1406 for the UEs.
  • the hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1414 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 1414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 1414 may have a constant/persistent or intermittent connection to the network node 1410b.
  • the hub 1414 may also allow for a different communication scheme and/or schedule between the hub 1414 and UEs (e.g., UE 1412c and/or 1412d) , and between the hub 1414 and the core network 1406.
  • the hub 1414 is connected to the core network 1406 and/or one or more UEs via a wired connection.
  • the hub 1414 may be configured to connect to an M2M service provider over the access network 1404 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1410 while still connected via the hub 1414 via a wired or wireless connection.
  • the hub 1414 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 1410b.
  • the hub 1414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Figure 15 shows a UE 1500 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-loT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale
  • the UE 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a power source 1508, a memory 1510, a communication interface 1512, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 15. 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 1502 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 1510.
  • the processing circuitry 1502 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 1502 may include multiple central processing units (CPUs).
  • the input/output interface 1506 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 1500.
  • 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 1508 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 1508 may further include power circuitry for delivering power from the power source 1508 itself, and/or an external power source, to the various parts of the UE 1500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1508.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1508 to make the power suitable for the respective components of the UE 1500 to which power is supplied.
  • the memory 1510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1510 includes one or more application programs 1514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1516.
  • the memory 1510 may store, for use by the UE 1500, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 1510 may allow the UE 1500 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 1510, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1502 may be configured to communicate with an access network or other network using the communication interface 1512.
  • the communication interface 1512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1522.
  • the communication interface 1512 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 1518 and/or a receiver 1520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1518 and receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/internet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 1512, 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.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-t
  • AR Augmented
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-loT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG 16 shows a network node 1600 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1600 includes a processing circuitry 1602, a memory 1604, a communication interface 1606, and a power source 1608.
  • the network node 1600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1600 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1600 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1604 for different RATs) and some components may be reused (e.g., a same antenna 1610 may be shared by different RATs).
  • the network node 1600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1600.
  • RFID Radio Frequency Identification
  • the processing circuitry 1602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1600 components, such as the memory 1604, to provide network node 1600 functionality.
  • the processing circuitry 1602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614. In some embodiments, the radio frequency (RF) transceiver circuitry 1612 and the baseband processing circuitry 1614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1612 and baseband processing circuitry 1614 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614.
  • the radio frequency (RF) transceiver circuitry 1612 and the baseband processing circuitry 1614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 1604 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1602.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-
  • the memory 1604 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 1602 and utilized by the network node 1600.
  • the memory 1604 may be used to store any calculations made by the processing circuitry 1602 and/or any data received via the communication interface 1606.
  • the processing circuitry 1602 and memory 1604 is integrated.
  • the communication interface 1606 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 1606 comprises port(s)/terminal(s) 1616 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1606 also includes radio front-end circuitry 1618 that may be coupled to, or in certain embodiments a part of, the antenna 1610. Radio front-end circuitry 1618 comprises filters 1620 and amplifiers 1622.
  • the radio front-end circuitry 1618 may be connected to an antenna 1610 and processing circuitry 1602.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1610 and processing circuitry 1602.
  • the radio front-end circuitry 1618 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 1618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1620 and/or amplifiers 1622.
  • the radio signal may then be transmitted via the antenna 1610.
  • the antenna 1610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1618.
  • the digital data may be passed to the processing circuitry 1602.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1600 does not include separate radio front-end circuitry 1618, instead, the processing circuitry 1602 includes radio front-end circuitry and is connected to the antenna 1610.
  • the processing circuitry 1602 includes radio front-end circuitry and is connected to the antenna 1610.
  • all or some of the RF transceiver circuitry 1612 is part of the communication interface 1606.
  • the communication interface 1606 includes one or more ports or terminals 1616, the radio front-end circuitry 1618, and the RF transceiver circuitry 1612, as part of a radio unit (not shown), and the communication interface 1606 communicates with the baseband processing circuitry 1614, which is part of a digital unit (not shown).
  • the antenna 1610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1610 may be coupled to the radio front-end circuitry 1618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1610 is separate from the network node 1600 and connectable to the network node 1600 through an interface or port.
  • the antenna 1610, communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1610, the communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1608 provides power to the various components of network node 1600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1600 with power for performing the functionality described herein.
  • the network node 1600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1608.
  • the power source 1608 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 1600 may include additional components beyond those shown in Figure 16 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 1600 may include user interface equipment to allow input of information into the network node 1600 and to allow output of information from the network node 1600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1600.
  • FIG 17 is a block diagram of a host 1700, which may be an embodiment of the host 1416 of Figure 14, in accordance with various aspects described herein.
  • the host 1700 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1700 may provide one or more services to one or more UEs.
  • the host 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a network interface 1708, a power source 1710, and a memory 1712.
  • processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a network interface 1708, a power source 1710, and a memory 1712.
  • 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 15 and 16, such that the descriptions thereof are generally applicable to the corresponding components of host 1700.
  • the memory 1712 may include one or more computer programs including one or more host application programs 1714 and data 1716, which may include user data, e.g., data generated by a UE for the host 1700 or data generated by the host 1700 for a UE.
  • Embodiments of the host 1700 may utilize only a subset or all of the components shown.
  • the host application programs 1714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 1700 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 18 is a block diagram illustrating a virtualization environment 1800 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 1800 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 virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1804 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 1806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1808a and 1808b (one or more of which may be generally referred to as VMs 1808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1806 may present a virtual operating platform that appears like networking hardware to the VMs 1808.
  • the VMs 1808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1806.
  • a virtualization layer 1806 may be implemented on one or more of VMs 1808, 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 network function virtualization
  • 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.
  • a VM 1808 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 1808, and that part of hardware 1804 that executes that VM forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1808 on top of the hardware 1804 and corresponds to the application 1802.
  • Hardware 1804 may be implemented in a standalone network node with generic or specific components. Hardware 1804 may implement some functions via virtualization. Alternatively, hardware 1804 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 1810, which, among others, oversees lifecycle management of applications 1802.
  • hardware 1804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1812 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 19 shows a communication diagram of a host 1902 communicating via a network node 1904 with a UE 1906 over a partially wireless connection in accordance with some embodiments.
  • host 1902 Like host 1700, embodiments of host 1902 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1902 also includes software, which is stored in or accessible by the host 1902 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 1906 connecting via an over-the-top (OTT) connection 1950 extending between the UE 1906 and host 1902.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 1950.
  • the network node 1904 includes hardware enabling it to communicate with the host 1902 and UE 1906.
  • the connection 1960 may be direct or pass through a core network (like core network 1406 of Figure 14) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 1406 of Figure 14
  • 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 1906 includes hardware and software, which is stored in or accessible by UE 1906 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 UE 1906 with the support of the host 1902.
  • 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 UE 1906 with the support of the host 1902.
  • an executing host application may communicate with the executing client application via the OTT connection 1950 terminating at the UE 1906 and host 1902.
  • 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 1950 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 through the OTT connection 1950.
  • the OTT connection 1950 may extend via a connection 1960 between the host 1902 and the network node 1904 and via a wireless connection 1970 between the network node 1904 and the UE 1906 to provide the connection between the host 1902 and the UE 1906.
  • the connection 1960 and wireless connection 1970, over which the OTT connection 1950 may be provided, have been drawn abstractly to illustrate the communication between the host 1902 and the UE 1906 via the network node 1904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1902 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 1906.
  • the user data is associated with a UE 1906 that shares data with the host 1902 without explicit human interaction.
  • the host 1902 initiates a transmission carrying the user data towards the UE 1906.
  • the host 1902 may initiate the transmission responsive to a request transmitted by the UE 1906.
  • the request may be caused by human interaction with the UE 1906 or by operation of the client application executing on the UE 1906.
  • the transmission may pass via the network node 1904, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the network node 1904 transmits to the UE 1906 the user data that was carried in the transmission that the host 1902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 1906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1906 associated with the host application executed by the host 1902.
  • the UE 1906 executes a client application which provides user data to the host 1902.
  • the user data may be provided in reaction or response to the data received from the host 1902.
  • the UE 1906 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 1906.
  • the UE 1906 initiates, in step 1918, transmission of the user data towards the host 1902 via the network node 1904.
  • the network node 1904 receives user data from the UE 1906 and initiates transmission of the received user data towards the host 1902.
  • the host 1902 receives the user data carried in the transmission initiated by the UE 1906.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1906 using the OTT connection 1950, in which the wireless connection 1970 forms the last segment.
  • factory status information may be collected and analyzed by the host 1902.
  • the host 1902 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1902 may store surveillance video uploaded by a UE.
  • the host 1902 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 1902 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 may be implemented in software and hardware of the host 1902 and/or UE 1906.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1904. 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 1902.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1950 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated examples: Group A Embodiments A1 .
  • a method performed by a communication device configured for use in a communication network comprising: transmitting a report to a network node in the communication network; and receiving, from the network node, a message that refers to the report to indicate which transmission configuration indication, TCI, state the communication device is to apply for subsequent transmission and/or reception.
  • the report reports an RS or SSB by reporting an identifier of the RS or SSB and reporting one or more of: a result of a measurement performed on the RS or SSB; a selection or preference of the RS or SSB by the communication device; or occurrence of an event associated with the RS or SSB.
  • A5. The method of any of embodiments A2-A4, wherein the message refers to the report to indicate which TCI state the communication device is to apply by: indicating that the communication device is to apply a TCI state associated with an RS or SSB reported by the report; or indicating an RS or SSB reported by the report is associated with a TCI state that the communication device is to apply.
  • A6 The method of any of embodiments A2-A4, wherein the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with an RS or SSB reported by the report.
  • A7 The method of any of embodiments A2-A4, wherein the report reports multiple RSs or multiple SSBs, wherein the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple RSs, or which of the multiple SSBs, reported by the report is associated with the TCI state that the communication device is to apply.
  • A8 The method of embodiment A7, wherein up to N RSs or SSBs are reportable by the report, and wherein the message comprises a bitfield with a length of ceil(log 2 (N+1)).
  • A9 The method of any of embodiments A5-A8, further comprising: making a decision as to whether or not to apply the TCI state indicated by the message based on: whether or not the RS or SSB indicated by the message is activated; or whether or not the RS or SSB indicated by the message has been triggered within a defined interval of time; and applying or not applying the TCI state indicated by the message in accordance with the decision.
  • the report reports a beam by reporting an identifier of the beam and reporting one or more of: a result of a measurement performed on the beam; a selection or preference of the beam by the communication device; or occurrence of an event associated with the beam.
  • A12 The method of any of embodiments A10-A11 , wherein the message refers to the report to indicate which TCI state the communication device is to apply by: indicating that the communication device is to apply a TCI state associated with a beam reported by the report; or indicating a beam reported by the report is associated with a TCI state that the communication device is to apply.
  • A13 The method of any of embodiments A10-A11 , wherein the message refers to the report to indicate which TCI state the communication device is to apply by indicating whether or not the communication device is to apply a TCI state associated with a beam reported by the report.
  • A14 The method of any of embodiments A10-A11 , wherein the report reports multiple beams, wherein the message refers to the report to indicate which TCI state the communication device is to apply by indicating which of the multiple beams reported by the report is associated with the TCI state that the communication device is to apply.
  • A15 The method of any of embodiments A1 -A14, wherein the message indicates whether the communication device is to apply the TCI state for a downlink beam pair, an uplink beam pair, or both the downlink beam pair and the uplink beam pair.
  • A16 The method of any of embodiments A1-A15, wherein the message indicates which type of report the message is for.
  • A17 The method of any of embodiments A1-A16, wherein the message indicates which serving cell, which bandwidth part, or which report configuration the message is for.
  • A18 The method of any of embodiments A1 -A17, wherein the message is or is included in: a downlink control information, DCI, message; or a medium access control, MAC, message.
  • A20 The method of any of embodiments A1-A19, wherein the message is indicated by a TCI field, wherein the method further comprises receiving signaling indicating whether or not the TCI field refers to the report to indicate which TCI state the communication device is to apply.
  • A21 The method of any of embodiments A1-A20, wherein the report is a device-initiated report and/or an event-triggered report.
  • A23 The method of any of embodiments A1-A22, further comprising detecting occurrence of an event based on a result of a measurement performed by the communication device, wherein the report is transmitted responsive to detecting the occurrence of the event.
  • A24 The method of any of embodiments A1-A23, wherein the message indicates when the communication device is to apply the TCI state.
  • A25 The method of any of embodiments A1-A23, further comprising receiving signaling indicating when the communication device is to apply the TCI state.
  • A26 The method of embodiment A25, wherein the signaling is RRC signaling. 27. The method of any of embodiments A1-A26, further comprising applying the TCI state for subsequent transmission and/or reception.
  • A28 The method of any of embodiments A1-A25, further comprising: making a decision as to whether or not to apply the TCI state indicated by the message, based on an amount of delay between transmitting the report and receiving the message; and applying or not applying the TCI state indicated by the message in accordance with the decision.
  • A29 The method of embodiment A28, wherein making the decision comprises: if the amount of the delay is less than a threshold, deciding not to apply the TCI state; and if the amount of the delay is more than the threshold, deciding to apply the TCI state.
  • A31 The method of any of embodiments A29-A30, further comprising determining the threshold based on whether or not the message indicates a downlink reference signal or beam that has been explicitly configured for beam reporting.
  • A32 The method of any of embodiments A29-A31 , further comprising transmitting capability signaling that indicates different thresholds according to which the decision is to be made for downlink reference signals or beams that are or are not associated with a serving cell, respectively.
  • A34 The method of any of embodiments A1-A33, wherein the message indicates to which report, or to which type of report, the message refers for indicating which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • A35 The method of any of embodiments A1-A34, wherein the report is the last report transmitted, wherein the message refers to the last report to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • A36 The method of any of embodiments A1-A34, wherein the report is the last report of a certain type transmitted, wherein the message refers to the last report of the certain type to indicate which TCI state the communication device is to apply for subsequent transmission and/or reception.
  • AA The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to a base station.
  • a method performed by a network node configured for use in a communication network comprising: receiving a report from a communication device; and transmitting, to the communication device, a message that refers to the report to indicate which transmission configuration indication, TCI, state the communication device is to apply for subsequent transmission and/or reception.
  • B25 The method of any of embodiments B1-B23, further comprising transmitting, to the communication device, signaling indicating when the communication device is to apply the TCI state.
  • B26 The method of embodiment B25, wherein the signaling is RRC signaling.
  • BB The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a communication device.
  • a communication device configured to perform any of the steps of any of the Group A embodiments.
  • a communication device comprising processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • a communication device comprising: communication circuitry; and processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • a communication device 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 communication device.
  • a communication device comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the communication device is configured to perform any of the steps of any of the Group A embodiments.
  • a user equipment 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
  • a computer program comprising instructions which, when executed by at least one processor of a communication device, causes the communication device to carry out the steps of any of the Group A embodiments.
  • a network node configured to perform any of the steps of any of the Group B embodiments.
  • a network node comprising processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • C12 A network node comprising: communication circuitry; and processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • a network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the network node.
  • a network node comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the network node is configured to perform any of the steps of any of the Group B embodiments.
  • a computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to carry out the steps of any of the Group B embodiments.
  • a communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • D2 The communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • UE user equipment
  • a user equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments.
  • a communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • UE user equipment
  • D10 The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
  • D11 The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
  • UE user equipment
  • a communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • UE user equipment
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • D17 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • D18 The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • UE user equipment
  • the method of the previous 3 embodiments further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • D24 The communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • D26 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

Landscapes

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

Abstract

L'invention concerne un dispositif de communication (12) qui est configuré pour être utilisé dans un réseau de communication (10). Le dispositif de communication (12) transmet un rapport (18) à un nœud de réseau (14) dans le réseau de communication (10). Le dispositif de communication (12) reçoit également, en provenance du nœud de réseau (14), un message (20) qui se réfère au rapport (18) pour indiquer quel état d'indication de configuration de transmission, TCI, (16) le dispositif de communication (12) doit appliquer pour une transmission et/ou une réception ultérieures.
PCT/EP2023/061201 2022-04-29 2023-04-28 Indication de configuration de transmission dans un réseau de communication WO2023209135A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263336423P 2022-04-29 2022-04-29
US63/336,423 2022-04-29

Publications (1)

Publication Number Publication Date
WO2023209135A1 true WO2023209135A1 (fr) 2023-11-02

Family

ID=86330599

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/061201 WO2023209135A1 (fr) 2022-04-29 2023-04-28 Indication de configuration de transmission dans un réseau de communication

Country Status (1)

Country Link
WO (1) WO2023209135A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220022180A1 (en) * 2020-07-17 2022-01-20 Samsung Electronics Co., Ltd. Method and apparatus for beam management and training

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021029138A1 (fr) * 2019-08-14 2021-02-18 Nec Corporation Procédé de rapport d'informations d'état de canal, système de communication et procédé de planification de tci
US20210337525A1 (en) * 2020-04-23 2021-10-28 Samsung Electronics Co., Ltd. Method and apparatus for dynamic beam indication mechanism
US20220007299A1 (en) * 2020-07-06 2022-01-06 Samsung Electronics Co., Ltd. Method and apparatus for uplink transmit beam selection procedures

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021029138A1 (fr) * 2019-08-14 2021-02-18 Nec Corporation Procédé de rapport d'informations d'état de canal, système de communication et procédé de planification de tci
US20210337525A1 (en) * 2020-04-23 2021-10-28 Samsung Electronics Co., Ltd. Method and apparatus for dynamic beam indication mechanism
US20220007299A1 (en) * 2020-07-06 2022-01-06 Samsung Electronics Co., Ltd. Method and apparatus for uplink transmit beam selection procedures

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.214
3GPP TS 38.321
3GPP TS 38.331

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220022180A1 (en) * 2020-07-17 2022-01-20 Samsung Electronics Co., Ltd. Method and apparatus for beam management and training

Similar Documents

Publication Publication Date Title
WO2022264106A1 (fr) Procédés et nœuds de réseau pour suspension-reprise pour une ou plusieurs configurations de mobilité intercellulaire centrée l1/l2
US20240224135A1 (en) L1/l2 centric mobility for scell(s)
WO2023209135A1 (fr) Indication de configuration de transmission dans un réseau de communication
WO2024033480A1 (fr) Planification de canal de données physique
WO2023095093A1 (fr) Signalisation mac ce destinée à supporter des fonctionnements à la fois conjoints et séparés de tci dl/ul
WO2024028838A1 (fr) Économie d'énergie de réseau dans un ng-ran scindé
WO2024157177A1 (fr) Procédés et nœuds pour indication de puissance de sortie srs
WO2023211347A1 (fr) États de déclenchement apériodiques inactifs pour économie d'énergie
WO2024072307A1 (fr) Bwp et mobilité inter-cellules l1-l2
WO2023083882A1 (fr) Autorisation configurée pour une transmission de liaison montante multi-panneau
WO2023062509A1 (fr) Activation de cellule secondaire basée sur un signal de référence temporaire par l'intermédiaire d'une commande de ressources radio
WO2024035312A1 (fr) Dispositifs et procédés de commutation de transmission de liaison montante dynamique
WO2024033731A1 (fr) Rapport de faisceau basé sur un groupe pour une transmission et une réception simultanées à panneaux multiples
WO2024033808A1 (fr) Mesures de csi pour mobilité intercellulaire
WO2023132773A1 (fr) Association de groupes d'erreurs de synchronisation de transmission de dispositif de communication de signalisation pour une différence de temps d'arrivée de liaison montante
WO2023073677A2 (fr) Mesures dans un réseau de communication
WO2024171148A1 (fr) Retard de tampon ul rapporté par un ue
WO2024172747A1 (fr) Signalisation d'occasions de transmission d'autorisation configurées inutilisées
WO2024033844A1 (fr) Conditions de déclenchement pour rapport de faisceau ue commandé par événement
WO2023166498A1 (fr) Systèmes et procédés d'association implicite entre une transmission pusch à trp multiples et des états tci unifiés
WO2024172741A1 (fr) Procédures de couche physique pour indiquer des occasions de transmission de canal pusch d'autorisation configurées inutilisées
WO2023247657A2 (fr) Gestion de faisceau de liaison latérale
WO2023011942A1 (fr) Rapport de relaxation de mesure radio précoce
WO2024035305A1 (fr) Rapport de réussite de changement ou d'ajout de pscell
CN117280753A (zh) 针对(多个)scell的以l1/l2为中心的移动性

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

Country of ref document: EP

Kind code of ref document: A1