Patent Application
20250167968
The present application relates generally to a communication network, and relates more particularly to configuration of an uplink channel or signal in such a communication network.
A transmission configuration indication (TCI) state contains quasi co-location (QCL) information between antenna ports of a communication device. In a spatial relation TCI state framework, a TCI state applies to an individual channel or signal. In a unified TCI state framework, by contrast, a TCI state applies to multiple channels or signals.
Challenges exist, however, in implementing the unified TCI state framework in a scheme where a communication device performs uplink transmissions towards multiple transmission reception points (TRPs). To support such a scheme, multiple unified TCI states would need to be activated for use by the communication device. Challenges in this case include how to associate the multi-TRP uplink transmissions with one or more of the unified TCI states that are activated, especially in a way that minimizes signaling overhead.
It may be an object of the present disclosure to provide methods and devices which may enable an association between multi-TRP uplink transmissions with one or more of unified TCI states that are activated in a way that may minimize signaling overhead.
According to some embodiments herein, a communication network configures with which of multiple activated unified TCI states each of one or more uplink channels or signals is associated. Some embodiments may thereby configure activated unified TCI state association per uplink channel or signal. In some embodiments, for example, the configuration for each uplink channel or signal exploits a TCI state pointer (e.g., a common beam index) that points to one or more of the activated unified TCI states with which the uplink channel or signal is associated. The TCI pointer may for instance point to one or more activated unified TCI states by pointing to one or more indices or identifiers that TCI state activation signaling associates with those one or more activated unified TCI states. These and other embodiments may advantageously configure activated unified TCI state association as needed for multi-TRP uplink transmission, while minimizing signaling overhead.
More particularly, embodiments herein include a method performed by a communication device configured for use in a communication network. The method comprises receiving, for each of one or more uplink channels or signals, a configuration that indicates with which of multiple activated unified transmission configuration indication, TCI, states the uplink channel or signal is associated.
In some embodiments, the configuration for each uplink channel or signal includes a TCI state pointer that points to one or more of the multiple activated unified TCI states with which the uplink channel or signal is associated. In one or more of these embodiments, the TCI state pointer is a common beam index. In one or more of these embodiments, activation signaling that activates the multiple unified TCI states associates the multiple unified TCI states with respective indices or identifiers. In some embodiments, the TCI state pointer included in the configuration for each uplink channel or signal points to one or more activated unified TCI states by pointing to the one or more indices or identifiers associated with the one or more activated unified TCI states. In one or more of these embodiments, the multiple activated unified TCI states includes first and second activated unified TCI states. In some embodiments, the activation signaling associates the first and second activated unified TCI states with first and second identifiers, respectively. In some embodiments, the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the first identifier, the second identifier, or both the first identifier and the second identifier. In one or more of these embodiments, the multiple activated unified TCI states includes first and second activated unified TCI states. In some embodiments, the activation signaling associates the first and second activated unified TCI states with first and second identifiers, respectively. In some embodiments, a field in downlink control signaling indicates whether the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the first identifier, the second identifier, or both the first identifier and the second identifier. Alternatively, a field in downlink control signaling indicates whether the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the second identifier, the first identifier, or both the second identifier and the first identifier. In one or more of these embodiments, the activation signaling includes a first field that activates the first activated unified TCI state and a second field that activates the second activated unified TCI state. In some embodiments, the first field occurs before the second field in the activation signaling. In one or more of these embodiments, the method further comprises receiving the activation signaling. In one or more of these embodiments, the activation signaling is received after receipt of the configuration for at least one of the one or more uplink channels or signals.
In some embodiments, the configuration for each uplink channel or signal explicitly indicates with which of the multiple activated unified TCI states the uplink channel or signal is associated.
In some embodiments, the multiple activated unified TCI states are associated with multiple respective transmission reception points, TRPs.
In some embodiments, said receiving comprises receiving, for each of one or more uplink channels, a configuration that indicates with which of multiple activated unified TCI states the uplink channel is associated. In one or more of these embodiments, the one or more uplink channels include an uplink data channel. In one or more of these embodiments, the uplink data channel is a Physical Uplink Shared Channel, PUSCH. In one or more of these embodiments, the configuration received for the PUSCH is a PUSCH configuration or a PUSCH serving cell configuration.
In some embodiments, the configuration for at least one uplink channel or signal includes a field that indicates whether a unified TCI framework or a spatial relation framework applies.
In some embodiments, said receiving comprises receiving, for each of one or more uplink signals, a configuration that indicates with which of multiple activated unified TCI states the uplink signal is associated. In one or more of these embodiments, the one or more uplink signals are one or more sounding reference signal, SRS, signals. In one or more of these embodiments, the one or more SRS signals are one or more SRS signals in one or more SRS resource sets. In one or more of these embodiments, the configuration for an SRS signal in an SRS resource set indicates with which of the multiple activated unified TCI states the SRS signal in that SRS resource set is associated by indicating with which of the multiple activated unified TCI states the SRS resource set is associated. In one or more of these embodiments, the configuration received for each of the one or more SRS signals in the one or more SRS resource sets is an SRS resource set configuration. In one or more of these embodiments, the one or more SRS signals are one or more SRS signals in one or more SRS resources of the same SRS resource set. In one or more of these embodiments, the configuration for an SRS signal in an SRS resource of the SRS resource set indicates with which of the multiple activated unified TCI states the SRS signal in that SRS resource is associated by indicating with which of the multiple activated unified TCI states the SRS resource is associated. In one or more of these embodiments, the configuration received for each of the one or more SRS signals in the one or more SRS resources of the SRS resource set is an SRS resource configuration.
In some embodiments, each activated unified TCI state contains quasi co-location, QCL, information between antenna ports of the communication device.
In some embodiments, each activated unified TCI state is applicable for multiple channels or signals.
In some embodiments, the multiple activated unified TCI states are joint uplink/downlink TCI states. In some embodiments, each joint TCI state is applicable for both downlink transmissions and uplink transmissions.
In some embodiments, the multiple activated unified TCI states are uplink TCI states. In some embodiments, each uplink TCI state is applicable only for uplink transmissions.
In some embodiments, the method further comprises determining, for each of the one or more uplink channels or signals, a spatial filter for the uplink channel or signal based on one or more activated unified TCI states that are associated with the uplink channel or signal according to the configuration received for that uplink channel or signal. In one or more of these embodiments, the method further comprises transmitting the one or more uplink channels or signals using the one or more spatial filters determined for the one or more uplink channels or signals.
In some embodiments, the multiple activated unified TCI states (16) are multiple unified TCI states that physical layer signaling indicates are to be used by the communication device (12) for determining one or more spatial filters for one or more uplink transmissions.
Other embodiments herein include a method performed by a network node configured for use in a communication network. The method comprises transmitting, to a communication device, for each of one or more uplink channels or signals, a configuration that indicates with which of multiple activated unified transmission configuration indication, TCI, states the uplink channel or signal is associated.
In some embodiments, the configuration for each uplink channel or signal includes a TCI state pointer that points to one or more of the multiple activated unified TCI states with which the uplink channel or signal is associated. In one or more of these embodiments, the TCI state pointer is a common beam index. In one or more of these embodiments, activation signaling that activates the multiple unified TCI states associates the multiple unified TCI states with respective indices or identifiers. In some embodiments, the TCI state pointer included in the configuration for each uplink channel or signal points to one or more activated unified TCI states by pointing to the one or more indices or identifiers associated with the one or more activated unified TCI states. In one or more of these embodiments, the multiple activated unified TCI states includes first and second activated unified TCI states. In some embodiments, the activation signaling associates the first and second activated unified TCI states with first and second identifiers, respectively. In some embodiments, the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the first identifier, the second identifier, or both the first identifier and the second identifier. In one or more of these embodiments, the multiple activated unified TCI states includes first and second activated unified TCI states. In some embodiments, the activation signaling associates the first and second activated unified TCI states with first and second identifiers, respectively. In some embodiments, a field in downlink control signaling indicates whether the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the first identifier, the second identifier, or both the first identifier and the second identifier. Alternatively, a field in downlink control signaling indicates whether the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the second identifier, the first identifier, or both the second identifier and the first identifier. In one or more of these embodiments, the activation signaling includes a first field that activates the first activated unified TCI state and a second field that activates the second activated unified TCI state. In some embodiments, the first field occurs before the second field in the activation signaling. In one or more of these embodiments, the method further comprises transmitting the activation signaling. In one or more of these embodiments, the activation signaling is transmitted after transmission of the configuration for at least one of the one or more uplink channels or signals.
In some embodiments, the configuration for each uplink channel or signal explicitly indicates with which of the multiple activated unified TCI states the uplink channel or signal is associated.
In some embodiments, the multiple activated unified TCI states are associated with multiple respective transmission reception points, TRPs.
In some embodiments, said transmitting comprises transmitting, for each of one or more uplink channels, a configuration that indicates with which of multiple activated unified TCI states the uplink channel is associated. In one or more of these embodiments, the one or more uplink channels include an uplink data channel. In one or more of these embodiments, the uplink data channel is a Physical Uplink Shared Channel, PUSCH. In one or more of these embodiments, the configuration transmitted for the PUSCH is a PUSCH configuration or a PUSCH serving cell configuration.
In some embodiments, the configuration for at least one uplink channel or signal includes a field that indicates whether a unified TCI framework or a spatial relation framework applies.
In some embodiments, said transmitting comprises transmitting, for each of one or more uplink signals, a configuration that indicates with which of multiple activated unified TCI states the uplink signal is associated. In one or more of these embodiments, the one or more uplink signals are one or more sounding reference signal, SRS, signals. In one or more of these embodiments, the one or more SRS signals are one or more SRS signals in one or more SRS resource sets. In one or more of these embodiments, the configuration for an SRS signal in an SRS resource set indicates with which of the multiple activated unified TCI states the SRS signal in that SRS resource set is associated by indicating with which of the multiple activated unified TCI states the SRS resource set is associated. In one or more of these embodiments, the configuration transmitted for each of the one or more SRS signals in the one or more SRS resource sets is an SRS resource set configuration. In one or more of these embodiments, the one or more SRS signals are one or more SRS signals in one or more SRS resources of the same SRS resource set. In one or more of these embodiments, the configuration for an SRS signal in an SRS resource of the SRS resource set indicates with which of the multiple activated unified TCI states the SRS signal in that SRS resource is associated by indicating with which of the multiple activated unified TCI states the SRS resource is associated. In one or more of these embodiments, the configuration transmitted for each of the one or more SRS signals in the one or more SRS resources of the SRS resource set is an SRS resource configuration.
In some embodiments, each activated unified TCI state contains quasi co-location, QCL, information between antenna ports of the communication device.
In some embodiments, each activated unified TCI state is applicable for multiple channels or signals.
In some embodiments, the multiple activated unified TCI states are joint uplink/downlink TCI states. In some embodiments, each joint TCI state is applicable for both downlink transmissions and uplink transmissions.
In some embodiments, the multiple activated unified TCI states are uplink TCI states. In some embodiments, each uplink TCI state is applicable only for uplink transmissions.
In some embodiments, the multiple activated unified TCI states (16) are multiple unified TCI states that physical layer signaling indicates are to be used by the communication device (12) for determining one or more spatial filters for one or more uplink transmissions.
Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs. For example, embodiments herein include a communication device configured for use in a communication network. The communication device is configured to receive, for each of one or more uplink channels or signals, a configuration that indicates with which of multiple activated unified transmission configuration indication, TCI, states the uplink channel or signal is associated. In some embodiments, the communication device is configured to determine, for each of the one or more uplink channels or signals, a spatial filter for the uplink channel or signal based on one or more activated unified TCI states that are associated with the uplink channel or signal according to the configuration received for that uplink channel or signal. In one or more of these embodiments, the communication device is further configured to transmit the one or more uplink channels or signals using the one or more spatial filters determined for the one or more uplink channels or signals.
Embodiments herein also include a network node configured for use in a communication network. The network node is configured to transmit, to a communication device, for each of one or more uplink channels or signals, a configuration that indicates with which of multiple activated unified transmission configuration indication, TCI, states the uplink channel or signal is associated.
As shown, the communication device 12 is configured to perform uplink transmission towards multiple transmission reception points (TRPs), shown as TRP-1 through TRP-N. These multiple TRPs may be distributed at different locations to cover different serving areas. Each TRP may include a set of antenna arrays and be under the control of the network node 14. In these and other embodiments, the communication device 12 may have multiple antenna panels (not shown), e.g., so that multiple uplinks can be established between the multi-TRPs of the network node 14 and the multi-panels of the communication device 12.
The communication device 12 in this regard may transmit one or more uplink channels or signals 20. As shown, for instance, the communication device 12 may transmit a first uplink channel or signal 20A, e.g., an uplink control channel such as a Physical Uplink Control Channel (PUCCH). In the example of
In this context, the communication device 12 is configured to employ a unified transmission configuration indication (TCI) state framework. A TCI state contains quasi co-location (QCL) information between antenna ports of the communication device 12. Two antenna ports are QCL if properties of the channel over which a transmission on one antenna port is conveyed can be inferred from the channel over which a transmission on the other antenna port is conveyed. That is, the communication device 12 can assume that properties of the channel over which a transmission on one antenna port is conveyed are the same as the properties of the channel over which a transmission on the other antenna port is conveyed. A TCI state therefore indicates a QCL relation or assumption between antenna ports, e.g., a source port and a target port. In a spatial relation TCI state framework, a TCI state applies to an individual channel or signal. In a unified TCI state framework, by contrast, a TCI state applies to multiple channels or signals.
Returning back to
As shown in
Radio Resource Control (RRC) signaling, and then selectively activate multiple ones of those configured unified TCI states via the activation signaling 18, e.g., in the form of MAC signaling or physical layer signaling. Unified TCI state configuration in this case may take place on a semi-static basis whereas unified TCI state activation may take place on a more dynamic basis.
Some embodiments herein facilitate use of the unified TCI state framework in this context where the communication device 12 performs uplink transmissions towards multiple TRPs TRP-1 . . . TRP-N. To support such a scheme, the network node 12 configures with which of the multiple activated unified TCI states 16 each of one or more uplink channels or signals is associated. Some embodiments may thereby configure activated unified TCI state association per uplink channel or signal.
More particularly, the network node 14 transmits, to the communication device 12, a configuration 24 for each of one or more uplink channels or signals 20. The configuration(s) 24 may for instance be RRC configurations. Regardless, the configuration 24 for each of the one or more uplink channels or signals 20 indicates with which of the multiple activated unified TCI states 16 the uplink channel or signal 20 is associated. In some embodiments, this is explicit such that the configuration 24 for each of the one or more uplink channels or signals 20 explicitly indicates with which of the multiple activated unified TCI states 16 the uplink channel or signal 20 is associated.
For example, the communication device 12 as shown may receive a configuration 24-1 for a first uplink channel or signal 20A. In this case, the configuration 24-1 (explicitly) indicates with which of the multiple activated unified TCI states 16 the first uplink channel or signal 20A is associated. The configuration 24-1 may for instance indicate that the first uplink channel or signal 20A is associated with both activated unified TCI states 16-1 and 16-N. As another example, the communication device 12 as shown may also receive a configuration 24-M for a second uplink channel or signal 20B. In this case, the configuration 24-2 (explicitly) indicates with which of the multiple activated unified TCI states 16 the second uplink channel or signal 20B is associated. The configuration 24-2 may for instance indicate that the second uplink channel or signal 20B is associated with either only activated unified TCI state 16-1 or only activated unified TCI state 16-N.
In some embodiments, the configuration 24 for each uplink channel or signal 20 exploits a TCI state pointer (e.g., a common beam index) that points to one or more of the activated unified TCI states 16 with which the uplink channel or signal 20 is associated. The TCI state pointer may for instance point to one or more activated unified TCI states 16 by pointing to one or more indices or identifiers that TCI state activation signaling 18 associates with those one or more activated unified TCI states 16. These and other embodiments may advantageously configure activated unified TCI state association as needed for multi-TRP uplink transmission, while minimizing signaling overhead.
As shown in
In this context, the configuration 24 for each uplink channel or signal 20 is shown as including a TCI state pointer 25 (e.g., a common beam index). The TCI state pointer 25 included in the configuration 24 for each uplink channel or signal 20 points to one or more activated unified TCI states 16 by pointing to the one or more indices or identifiers 19 associated with the one or more activated unified TCI states 16. As shown, for example, the TCI state pointer 25-1 in the configuration 24-1 for a first uplink channel or signal (to be transmitted towards both TRP-1 and TRP-N) points to both activated unified TCI states 16-1 and 16-N by pointing to both indexes/identifiers 19-1 and 19-N. The TCI state pointer 25-2 in the configuration 24-2 for a second uplink channel or signal (to be transmitted towards only TRP-1) points to only the activated unified TCI state 16-1 by pointing to only index/identifier 19-1. And the TCI state pointer 25-M in the configuration 24-M for an Mth uplink channel or signal (to be transmitted towards only TRP-N) points to only the activated unified TCI state 16-N by pointing to only index/identifier 19-N.
Some embodiments herein are applicable in the following context, where the communication device 12 is exemplified as a user equipment (UE).
In particular, some embodiments herein are applicable to the next generation mobile wireless communication system (5G) or new radio (NR), which will support a diverse set of use cases and a diverse set of deployment scenarios. The later includes deployment at both low frequencies (below 6 GHZ) and very high frequencies (up to 10's of GHZ).
NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in both downlink (i.e., from a network node, gNB, or base station, to a user equipment or UE) and uplink (i.e., from UE to gNB). Discrete Fourier Transform (DFT) spread OFDM is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equally-sized subframes of 1 ms each. A subframe is further divided into multiple slots of equal duration. The slot length depends on subcarrier spacing. For subcarrier spacing of Δf=15 kHz, there is only one slot per subframe and each slot consists of 14 OFDM symbols.
Data scheduling in NR is typically in slot basis, an example is shown in
Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values (also referred to as different numerologies) are given by Δf=(15×2μ) kHz where μ∈0,1,2,3,4. Δf=15 kHz is the basic subcarrier spacing. The slot durations at different subcarrier spacings is given by ½μ ms.
In the frequency domain, a system bandwidth is divided into resource blocks (RBs), each corresponding to 12 contiguous subcarriers. The RBs are numbered starting with 0 from one end of the system bandwidth. The basic NR physical time-frequency resource grid is illustrated in
Downlink and uplink transmissions can be either dynamically scheduled in which the gNB transmits a downlink (DL) assignment or an uplink grant via downlink control information (DCI) over PDCCH (Physical Downlink Control Channel) to a UE for each PDSCH or PUSCH transmission, or semi-persistent scheduled (SPS) in which one or more DL SPS or UL configured grants (CGs) are semi-statically configured and each can be activated or deactivated by a DCI.
In some embodiments, a UE monitors a set of PDCCH candidates for potential PDCCHs. A PDCCH candidate consists of L∈[1,2,4,8,16] control-channel elements (CCEs) in a Control Resource Set (CORESET). A CCE consists of 6 resource-element groups (REGs) where a REG equals one RB during one OFDM symbol. L is referred to as the CCE aggregation level.
The set of PDCCH candidates is defined in a PDCCH search space (SS) set. An SS set can be a Common Search Space (CSS) set or a UE Specific Search Space (USS) set. A UE can be configured with up to 10 SS sets per bandwidth part (BWP) for monitoring PDCCH candidates.
Each SS set is associated with a CORESET. A CORESET consists of NRBCORESET resource blocks in frequency domain and NsymbCORESET∈{1,2,3} consecutive OFDM symbols in time domain. In NR Rel-15, a UE can be configured with up to 3 CORESETs per BWP.
For each SS set, a UE is configured with the following parameters comprising:
A UE determines a PDCCH monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. For search space set s, the UE determines that a PDCCH monitoring occasion(s) exists in slot ns,fμ in frame nf if (nf·Nslotframe,μ+ns,fμ−os) mod ks=0, where Nslotframe,μ is the number of slots per radio frame. The UE monitors PDCCH candidates for search space set s for Ts consecutive slots, starting from slot ns,fμ, and does not monitor PDCCH candidates for search space set s for the next ks−Ts consecutive slots.
In some embodiments, a Transmission Configuration Indication (TCI) state contains Quasi Co-location (QCL) information between two antenna ports. Two antenna ports are said to be QCL if certain channel parameters associated with one of the two antenna ports can be inferred from the other antenna port. An antenna port is defined by a reference signal (RS). Therefore, a TCI state is used in NR to indicate the QCL relation between a source RS and a target RS. The source RS can be one of a NZP CSI-RS (Non-zero Power Channel State Information Reference Signal), tracking RS (TRS), and a SSB (Synchronization Signal Block), while the target RS can be a Demodulation Reference Signal (DMRS) for PDCCH or PDSCH, or a CSI-RS.
Some embodiments apply to the supported QCL information types in NR which include:
A list of TCI states can be RRC configured in a higher layer parameter PDSCH-Config information element (IE) (see 3GPP TS 38.331 v16.7.0 section 6.3.2 for details). In some embodiments, e.g., using a 3-stage approach, up to 8 TCI states from the list can be activated with a MAC Control Element (CE). In NR Rel-15, one TCI state is activated by a MAC CE for each TCI codepoint of a TCI field in DCI, where up to 8 TCI codepoints can be supported (see 3GPP TS 38.321 v15.12.0 section 6.1.3.14 for details). In NR Rel-16, up to two TCI states can be activated by a MAC CE for each TCI codepoint (see 3GPP TS 38.321 v16.7.0 section 6.1.3.24). For dynamically scheduled PDSCH, one of the TCI codepoints is indicated in the TCI field of the DCI (DCI format 1_1 or DCI format 1_2) scheduling the PDSCH for PDSCH reception. For example, if a SSB or CSI-RS is configured as the QCL-typeD source RS in an activated TCI state indicated to a PDSCH, the same receive beam (or spatial filter) for receiving the SSB or CSI-RS would be used by a UE to receive the PDSCH.
For each CORESET, a list of TCI states can be RRC configured, and one of the TCI states is activated by a MAC CE. For example, if an SSB is configured as the QCL-typeD source RS in an activated TCI state for a CORESET, the same receive beam for receiving the SSB can be used by a UE to receive PDCCHs transmitted in the CORESET.
Beam Management with Unified TCI Framework
In NR, downlink beam management is performed by conveying spatial QCL (‘Type D’) assumptions to the UE through TCI states. Without unified TCI states, such a framework allows great flexibility for the network to instruct the UE to receive signals from different spatial directions in DL with a cost of large signaling overhead and slow beam switch. These limitations are particularly noticeable and costly when UE movement is considered. 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 may cause extra overhead and latency. Furthermore, in a majority of cases, the network transmits to and receives from a UE in the same direction for both data and control. Hence, using separate frameworks (TCI state respective spatial relations) for different channels/signals complicates the implementations.
Some embodiments herein thereby exploit unified TCI states, e.g., as specified by 3GPP. In particular, some embodiments herein support unified TCI states as specified according to 3GPP Rel-17. In Rel-17, a unified TCI state based beam indicated framework was introduced to simplify beam management in frequency range 2 (FR2), in which a common beam represented by a TCI state may be activated/indicated to a UE, and the common beam is applicable for multiple channels/signals such as PDCCH and PDSCH. The common beam framework is also referred to a unified TCI state framework. A TCI state configured under the Rel-17 framework exemplifies a unified TCI state according to some embodiments herein.
In some embodiments, the unified TCI state framework can be RRC configured in one out of two modes of operation, i.e., Joint DL/UL TCI” or “Separate DL/UL TCI”. For “Joint DL/UL TCI”, one common Joint TCI state is used for both DL and UL signals/channels. For “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.
In some embodiments, a unified TCI state for separate DL/UL or Joint DL/UL comprises identifiers of two QCL source reference signals as shown below, where the first RS is a QCL source RS for one of {typeA, typeB, typeC} QCL types, while the second RS is a QCL source RS for QCL typeD. The second RS is used to indicate a spatial beam or filter associated with the unified TCI state. An example ASN.1 code for configuring separate UL/DL or Joint DL/UL TCI state is shown below.
In some embodiments, a unified TCI state can be updated in a similar way as the TCI state update for PDSCH in Rel-15/16, i.e., with one of two alternatives. In a “two-stage” alternative, RRC signaling is used to configure a number of unified TCI states in higher layer parameter PDSCH-config, and a MAC-CE is used to activate one of unified TCI states. In some embodiments, then, the activated unified TCI states 16 in
An activated or indicated unified TCI state will be used in subsequent PDCCH, PDSCH, and NZP CSI-RS transmissions until a new unified TCI state is activated or indicated.
In the following description, then, an “activated/indicated” unified TCI state (also referred to as an “activated or indicated” unified TCI state) exemplifies an “activated” unified TCI state as referred to in
In some embodiments, the existing DCI formats 1_1 and 1_2, as specified in 38.212 version 17.0.0 are reused for beam indication (i.e., TCI state indication/update), both with and without DL assignment. For DCI formats 1_1 and 1_2 with DL assignment, ACK/NACK of the PDSCH can be used as indication of successful reception of beam indication. For DCI formats 1_1 and 1_2 without DL assignment, a new ACK/NACK mechanism analogous to that for 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.
In some embodiments, for DCI-based beam indication, the first slot to apply the indicated TCI 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
Some embodiments herein are applicable for PDCCH repetition, e.g., as in NR Rel-17, which provides for more robust PDCCH reception in which a PDCCH is transmitted over two transmission and reception points (TRPs) on different time or frequency resources.
An example is shown in
Two linked SS sets need to be configured with the same set of parameters such as periodicity, slot offset, number of monitoring occasions within a slot, etc. For a given CCE aggregation level and two linked SS sets, the location of one PDCCH candidate in one SS set can be obtained from a PDCCH candidate in the other SS set. When performing PDCCH detection, a UE may detect PDCCH individually in each PDCCH candidate or jointly by soft combining of the two PDCCH candidates.
Some embodiments herein are applicable for single frequency network (SFN) based PDCCH, e.g., as in NR Rel-17, for more robust PDCCH reception in which a PDCCH is transmitted simultaneously from two TRPs in the same time and frequency resource. An example is shown in
Multi-TRP (mTRP) PDSCH Schemes
Some embodiments herein are applicable for PDSCH transmission over two TRPs, e.g., as introduced in NR Rel-16, including a non-coherent joint transmission (NC-JT) scheme, two frequency domain multiplexing (FDM) schemes, and two time domain multiplexing (TDM) schemes. In these multi-TRP PDSCH schemes, each TRP is represented by an indicated TCI state. In NC-JT, a PDSCH is transmitted over two TRPs in the same time and frequency resource with different multiple-input multiple-output (MIMO) layers of the PDSCH transmitted from different TRPs. For example, 2 layers can be transmitted from a first TRP and 1 layer can be transmitted from a second TRP for a total of 3 layers. For NC-JT based PDSCH scheduling, two TCI states are indicated in a TCI codepoint of DCI scheduling the PDSCH. The demodulation reference signal (DMRS) ports in a first and second code division multiplexing (CDM) groups are associated with the first and second TCI states, respectively.
In the FDM schemes, different frequency domain resources of a PDSCH are allocated to different TRPs. In FDM scheme A, a single PDSCH is transmitted and part of the PDSCH is sent from one TRP and the rest from the other TRP. In FDM scheme B, a PDSCH is repeated over two TRPs. For FDM based multi-TRP PDSCH scheduling, two TCI states are indicated in a TCI codepoint of DCI scheduling the PDSCH. The DMRS ports in a first and second set of scheduled resource blocks (RBs) are associated with the first and second TCI states, respectively.
In the TDM schemes, a PDSCH is repeated in multiple times, each over one of two TRPs. In TDM scheme A, a PDSCH is repeated two times within a slot, one from each TRP. While in TDM scheme B (or slot-based TDM scheme), a PDSCH is repeated in consecutive slots, either in a cyclic manner from two TRPs in which the PDSCH is transmitted alternatively from a first TRP in one slot and a second TRP in the next slot, or in a sequential manner in which PDSCH is transmitted alternatively from the first and second TRPs every two consecutive slots. For TDM based multi-TRP PDSCH scheduling, two TCI states are indicated in a TCI codepoint of DCI scheduling the PDSCH. The DMRS ports in a first and second set of PDSCH transmission occasions are associated with the first and second TCI states, respectively. The first and second set of PDSCH transmission occasions are determined according to the mapping type, i.e., cyclic or sequential mapping.
An example of TDM Scheme B is shown in
Some embodiments herein are applicable for PDSCH transmission with multiple transmission points, e.g., as has been introduced in 3GPP for NR Rel-16, in which a transport block may be transmitted over multiple TRPs to improve transmission reliability.
In some embodiments, UL enhancement with multiple TRPs is performed by transmitting a PUCCH or PUSCH towards to different TRPs as shown in
In one scenario, multiple PUCCH/PUSCH transmissions, each towards a different TRP, may be scheduled by a single DCI. For example, multiple spatial relations (i.e., spatial beams) may be activated for a PUCCH resource and the PUCCH resource may be signaled in a DCI scheduling a PDSCH. The hybrid automatic repeat request (HARQ) ack/nack (A/N) associated with the PDSCH is then carried by the PUCCH which is then repeated multiple times either within a slot or over multiple slots, each repetition is towards a different TRP. An example is shown in
An example of PUSCH repetitions is shown in
A Channel State Information Reference Signal (CSI-RS) according to some embodiments herein is used, e.g., as specified in NR, for channel state information, CSI, measurement in the downlink. A CSI-RS is transmitted on an antenna port at the gNB and is used by a UE to measure downlink channel associated with the antenna port. CSI-RS for this purpose is also referred to as Non-Zero Power (NZP) CSI-RS. The antenna port is also referred to as a CSI-RS port. In some embodiments, the supported number of CSI-RS ports in a CSI-RS resource in NR can be one of {1,2,4,8, 12,16,24,32}. Multiple CSI-RS resources can be configured. A CSI-RS resource set can contain one or more CSI-RS resources.
A CSI-RS resource can be aperiodic, periodic, or semi-persistent (SP). CSI-RS resources in a CSI-RS resource set are transmitted together and have the same time domain configuration, i.e., aperiodic, periodic or semi-persistent.
In some embodiments, aperiodic CSI-RS transmission is triggered by one of DCI format 0_1 or DCI format 0_2. SP CSI-RS transmission is activated and deactivated by a MAC CE.
In frequency range 2 (FR2), each CSI-RS resource is also associated with a beam which is specified by a QCL source reference signal (RS) with type D. For periodic, the QCL source RS is RRC configured. For Aperiodic CSI-RS, the QCL type D source RS is configured in an associated aperiodic CSI trigger state, where the index of the trigger state is indicated in the DCI triggering the aperiodic CSI-RS. For SP CSI-RS, the QCL source RS is indicated in the corresponding activation MAC CE. These are further explained below.
A “CSI-Aperiodic TriggerStateList” information element (IE) defined in 3GPP TS 38.331 is used in NR to configure a UE with a list of aperiodic CSI trigger states, each defined by the parameter “CSI-AperiodicTriggerState”, as shown below. Each codepoint of the “CSI request” field in DCI (DCI format 1_1, or DCI format 1_2) is associated with one of the trigger states in the list, e.g., as described in 3GPP TS 38.214 17.0.0 section 5.2.1.5.1. Upon reception of a DCI with a CSI request codepoint indicating a trigger state, the UE receives NZP CSI-RS resources in a NZP CSI-RS resource set indicated by the parameter “resourceset” in the trigger state according the QCL information configured by the parameter “qcl-info”. The QCL information contains a TCI state ID for each NZP CSI-RS resources in the NZP CSI-RS resource set.
In some embodiments, QCL information for a SP CSI-RS resource in a CSI-RS resource set is indicated in the corresponding MAC CE activating the CSI-RS resource set. The MAC CE may for example be as otherwise described in TS 38.321 v16.7.0 section 6.1.3.12 and FIG. 6.1.3.12-1, which is reproduced in
As shown in
A/D: This field indicates whether to activate or deactivate indicated SP CSI-RS and CSI-IM resource set(s). The field is set to 1 to indicate activation, otherwise it indicates deactivation.
Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits.
BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI bandwidth part indicator field as specified in TS 38.212 v17.0.0. The length of the BWP ID field is 2 bits.
SP CSI-RS resource set ID: This field contains an index of NZP-CSI-RS-ResourceSet containing Semi Persistent NZP CSI-RS resources, as specified in TS 38.331 v16.7.0, indicating the Semi Persistent NZP CSI-RS resource set, which shall be activated or deactivated. The length of the field is 6 bits.
Interference management (IM): This field indicates the presence of the octet containing SP CSI-IM resource set ID field. If the IM field is set to 1, the octet containing SP CSI-IM resource set ID field is present. If IM field is set to 0, the octet containing SP CSI-IM resource set ID field is not present.
SP CSI-IM resource set ID: This field contains an index of CSI-IM-ResourceSet containing Semi Persistent CSI-IM resources, as specified in TS 38.331 v16.7.0, indicating the Semi Persistent CSI-IM resource set, which shall be activated or deactivated. The length of the field is 6 bits.
TCI State IDi: This field contains TCI-StateId, as specified in TS 38.331 v16.7.0, of a TCI State, which is used as QCL source for the resource within the Semi Persistent NZP CSI-RS resource set indicated by SP CSI-RS resource set ID field. TCI State ID0 indicates TCI State for the first resource within the set, TCI State ID1 for the second one and so on. The length of the field is 7 bits. If the A/D field is set to 0, the octets containing TCI State ID field(s) are not present.
R: Reserved bit, set to 0.
Some embodiments herein address certain challenge(s) in this context. In particular, as of NR Rel-17, the unified TCI state framework supported activation or indication of only a single unified TCI state at each time. Thus, in NR Rel-17, it is only applicable to PUSCH data transmissions from a UE towards a single TRP. The mTRP PUSCH schemes supported in Rel-17 are not supported by the unified TCI framework introduced in Rel-17 (i.e., the mTRP PUSCH schemes introduced in Rel-17 rely on the Rel-15 spatial relation framework). NR Rel-18 extends the unified TCI state framework to support mTRP schemes. To support mTRP PUSCH schemes, multiple unified TCI states need to be activated/indicated to the UE. How to associate PUSCH transmission to one or more of the multiple unified TCI states is heretofore an open problem.
Some embodiments herein accordingly include solutions on how to determine spatial filters for PUSCH transmissions for mTRP operation for the unified TCI state framework using explicitly configured common beam indexes. In doing so, some embodiments advantageously provide a simple way to associate a PUSCH transmission to one or more common beams for multi-TRP based transmission under a unified TCI state framework.
In the following embodiments, the term ‘common beam index’ is used. A common beam index can be understood to be an identifier or ID of an activated/indicated Joint DL/UL TCI state. In some other cases, a common beam index can be understood to be an identifier or ID of an activated/indicated Separate UL TCI state (i.e., UL-only TCI state). Although most of the embodiments below are written with respect to Joint DL/UL TCI state, the embodiments are non-limiting and are equally valid when Separate UL TCI state is activated/indicated in place of Joint DL/UL TCI state. A common beam index may thereby generally exemplify a TCI state pointer according to some embodiments.
In one embodiment, one or two common beam indexes can be explicitly configured in PUSCH-config (as otherwise specified in TS 38.331 v16.7.0) as schematically illustrated below:
In one other embodiment, instead of configuring the explicit common beam index in PUSCH-config, it can be configured in PUSCH-ServingCellConfig.
PUSCH-config and/or PUSCH-ServingCellConfig serve as examples of configuration(s) 24 in
In one embodiment, in case the Common_beam_index is configured with commonBeam1 and the UE is indicated with two Joint DL/UL TCI states, the UE should determine the spatial filter for the PUSCH transmission based on a first indicated Joint DL/UL TCI state. In a similar way, in case the Common_beam_index is configured with commonBeam2 and the UE is indicated with two Joint DL/UL TCI states, the UE should determine the spatial filter for the PUSCH transmission based on a second indicated Joint DL/UL TCI state. And in case the Common_beam_index is configured with commonBeam1ANDcommonBeam2 and the UE is indicated with two Joint DL/UL TCI states, the UE should determine the spatial filter for a first PUSCH transmission based on a first indicated Joint DL/UL TCI state and a second PUSCH transmission based on a second Joint DL/UL TCI state.
In one embodiment, in case the UE is only indicated with one Joint DL/UL TCI state, the UE shall ignore this field, and follow the indicated Joint DL/UL TCI state.
In another embodiment, a common_beam_index may only be configured in one PUSCH-Config corresponding to a given UL dedicated BWP and a serving cell (i.e., a component carrier). This given UL dedicated BWP and serving cell may be referred to as the reference PUSCH-Config. For the other PUSCH-Config's that should follow the same common_beam_index as configured in the reference PUSCH-Config, at least one identifier may be configured in the other PUSCH-Config's.
Consider the following example. In this example, PUSCH-Config 0 in BWP 0 of Serving cell 1 is configured with a common_beam_index. And PUSCH-Config 1 in BWP 1 of Serving cell 2 is not configured with a common_beam_index, but configured with the identifiers of the reference PUSCH-Config which consists of IDs corresponding to BWP 0 and/or Serving cell 1
In the above example embodiment, if the Common_beam_index is configured with commonBeam1 in PUSCH-Config 0 and the UE is indicated with two Joint DL/UL TCI states, then for PUSCH transmission corresponding to PUSCH-Config 1, the UE should determine the spatial filter for the PUSCH transmission based on a first indicated Joint DL/UL TCI state (i.e., the same assumption as the reference PUSCH-Config).
Similarly, if the Common_beam_index is configured with commonBeam2 in PUSCH-Config 0 and the UE is indicated with two Joint DL/UL TCI states, then for PUSCH transmission corresponding to PUSCH-Config 1, the UE should determine the spatial filter for the PUSCH transmission based on a second indicated Joint DL/UL TCI state (i.e., the same assumption as the reference PUSCH-Config).
If the Common_beam_index is configured with commonBeam1ANDcommonBeam2 in PUSCH-Config 0 and the UE is indicated with two Joint DL/UL TCI states, then for PUSCH transmission corresponding to PUSCH-Config 1, the UE should determine the spatial filter for a first PUSCH transmission based on a first indicated Joint DL/UL TCI state and a second PUSCH transmission based on a second Joint DL/UL TCI state (i.e., the same assumption as the reference PUSCH-Config).
The benefit of the above embodiment is that when the common_beam_index needs to be updated, it is sufficient that the common_beam_index in the reference PUSCH-Config is updated via reconfiguration. No such update/reconfiguration is needed for the non-reference PUSCH-Config's (i.e., PUSCH-Config's that follow the same common_beam_index assumption as the reference PUSCH-Config).
A configuration example of the reference PUSCH-Config is shown below. In this example, the parameter ‘refCommon_beam_index’ provides the reference PUSCH-Config (i.e., the serving cell and the BWP ID corresponding to the PUSCH-Config that contains the configured Common_beam_index). Note that if a PUSCH-Config is configured with Common_beam_index, then refCommon_beam_index is not configured for that PUSCH-Config (i.e., that PUSCH-Config will be reference PUSCH-Config for other PUSCH-Config's). For a non-reference PUSCH-Config, only refCommon_beam_index will be configured, and Common_beam_index will not be configured).
When the UE is configured with commonBeam1ANDcommonBeam2, it must be decided which PUSCH transmissions and/or which parts of a PUSCH transmission should be associated with which common beam index, for different PUSCH transmission schemes (e.g., TDM repetition, FDM repetition, SFN, spatial multiplexing, simultaneous transmission etc.).
In one embodiment, in case PUSCH is scheduled for time division multiplexing (TDM) repetition (i.e., where the same payload is transmitted in two different PUSCH transmission occasions transmitted at two different time instances), the first PUSCH repetition (i.e., first PUSCH transmission occasion) is associated with a first common beam index (i.e., a first indicated Joint DL/UL TCI state), and the second PUSCH repetition (i.e., second PUSCH transmission occasion) is associated with a second common beam index (i.e., a second indicated Joint DL/UL TCI state). In one embodiment, a codepoint in DCI scheduling the PUSCH can be used to change the ordering of the association between common beam index and the PUSCH transmission occasion. For example, in case the codepoint is ‘0’, the UE should associate a first common beam index with the first PUSCH repetition and a second common beam index with the second PUSCH repetition. By contrast, in case the codepoint is ‘1’, the UE should associate a second common beam index with the first PUSCH repetition and a first common beam index with the second PUSCH repetition. Note that the codepoints could be included in another bitfield in the DCI used to indicate for example other things, like which PUSCH transmission mode that is triggered, etc.
In one embodiment, in case PUSCH is scheduled for frequency division multiplexing (FDM) repetition (i.e., where the same payload is transmitted in two different PUSCH transmissions transmitted at two different frequency allocations within the same time symbols), the first PUSCH repetition (i.e., first PUSCH transmission occasion) scheduled over a first frequency allocation is associated with a first common beam index (i.e., a first indicated Joint DL/UL TCI state), and the second PUSCH repetition (i.e., second PUSCH transmission occasion) scheduled over a second frequency allocation is associated with a second common beam index (i.e., a second indicated Joint DL/UL TCI state). In one embodiment, a codepoint in DCI scheduling the PUSCH can be used to change the order of the association between common beam index and the PUSCH transmission occasion. For example, in case the codepoint is ‘0’, the UE should associate a first common beam index with the first PUSCH repetition scheduled over a first frequency allocation and a second common beam index with the second PUSCH repetition scheduled over a second frequency allocation. By contrast, in case the codepoint is ‘1’, the UE should associate a second common beam index with the first PUSCH repetition scheduled over a first frequency allocation and a first common beam index with the second PUSCH repetition scheduled over a second frequency allocation. In one embodiment, the first frequency allocation is scheduled using a first set of bits in the DCI scheduling the PUSCH, and the second frequency allocation is scheduled using a second set of bits in the DCI scheduling the PUSCH (where the first set of bits and second set of bits are different bits).
In one embodiment, in case PUSCH is scheduled for spatial multiplexing (i.e., where different sets of PUSCH layers are transmitted in two different PUSCH transmissions transmitted in overlapping time/frequency resources), the first PUSCH transmission associated with a first set of layers is associated with a first common beam index (i.e., a first indicated Joint DL/UL TCI state), and the second PUSCH transmission associated with a second set of PUSCH layers is associated with a second common beam index (i.e., a second indicated Joint DL/UL TCI state). In one embodiment, the first set of layers is indicated with a first transmission precoder matrix indicator (TPMI)/SRI field in the DCI scheduling the PUSCH transmission and the second set of layers is indicated with a second TPMI/SRI field in the DCI scheduling the PUSCH transmission. In one embodiment, the first set of layers is associated with a first CDM group indicated with the Antenna port bitfield (as specified in 3GPP TS 38.212 v17.0.0) included in the in the DCI scheduling the PUSCH transmission and the second set of layers is associated with a second CDM group indicated with the Antenna port bitfield included in the in the DCI scheduling the PUSCH transmission. So for example, in case the Antenna port bitfield in DCI scheduling the PUSCH indicates antenna (DMRS) port 0 belonging to CDM group 0 and antenna (DMRS) port 2 belonging to CDM group 1, then the UE should associate the PUSCH layer transmitted on antenna port 0 with a first common beam index (i.e. a first indicated Joint DL/UL TCI state), and associate the PUSCH layer transmitted on antenna port 2 with a second common beam index (i.e. a second indicated Joint DL/UL TCI state).
In one embodiment, a flag parameter may be configured as part of PUSCH-Config along with multi-TRP PUSCH configuration parameters. This flag parameter enables the use of the unified Joint DL/UL TCI state to be used for multi-TRP PUSCH schemes. If the flag parameter is not configured, then the UE may assume the rel-15/16 based spatial relation framework for mTRP PUSCH transmission. For instance, if the flag parameter is configured, then the UE is instructed to assume unified Joint DL/UL TCI state for deriving spatial filters for multi-TRP PUSCH schemes. If the flag is not configured, the UE is instructed to use spatial relations as indicated by the SRI fields in DCI that schedules the PUSCH transmission to derive the spatial filter for multi-TRP PUSCH schemes.
In the following embodiments, it is assumed that a common beam index is explicitly configured per sounding reference signal (SRS) resource set (where SRS resource set is specified in TS 38.331 v16.7.0) with usage ‘codebook’ or ‘nonCodebook’, as schematically illustrated below:
SRS-ResourceSet is accordingly an example of configuration(s) 24 herein in
In one embodiment, the UE is configured with two SRS resource sets with usage ‘codebook’ or ‘nonCodebook’, where each of the two sets are explicitly configured with one common beam index. In one embodiment, when the UE is triggered for transmission of the two SRS resource sets with usage ‘codebook’ or ‘nonCodebook’ and has two indicated Joint DL/UL TCI states, the UE should associate the transmission of the first SRS resource set with the common beam index explicitly configured in that SRS resource set. When the UE is scheduled with PUSCH transmission and is indicated with two Joint DL/UL TCI states, a first PUSCH transmission that is associated with a first SRS resource set should be transmitted using the common beam index explicitly configured in the first SRS resource set, and a second PUSCH transmission that is associated with a second SRS resource set should be transmitted using the common beam index explicitly configured in the second SRS resource set. The association between an SRS resource set and a PUSCH transmission could for example be based on two SRI/TPMI fields included in the DCI scheduling the PUSCH, where a first SRI/TPMI field is associate with a first SRS resource set and a first PUSCH transmission, and a second SRI/TPMI field is associate with a second SRS resource set and a second PUSCH transmission.
In one embodiment, in case the UE is configured with two SRS resource sets with usage ‘codebook’ or ‘nonCodebook’, and where each SRS resource set is explicitly configured with a common beam index, in case the UE is indicated with a single Joint DL/UL TCI state, the UE should de-activate one of the SRS resource sets (i.e., even if the UE is triggered with SRS transmission of the both SRS resource set, the UE should only transmit one of them).
In another embodiment, a flag to enable using unified Joint DL/UL state for SRS ResourceSet's with usage set to ‘codebook’ based or ‘non codebook’ based PUSCH is configured inside the SRS ResourceSet as shown below:
This flag (denoted as ‘followUnifiedTCIstate’) indicates to the UE that when PUSCH is scheduled by indicating one or more SRS resources from this SRS resource set, then the transmit spatial filters to be used for PUSCH transmission is derived from the indicated/activated Joint DL/UL TCI state.
However, for the multi-TRP scenario, there will be multiple (e.g., 2) Joint DL/UL TCI states that are indicated/activated to the UE. In this case, multiple (e.g., 2) SRS resource sets are configured to the UE wherein each SRS resource set represents a transmission towards a TRP. To associate the SRS resource set with one of the Joint DL/UL TCI states, a ‘common_beam_index’ is configured per SRS resource set. In one embodiment, when the UE is triggered for transmission of the two SRS resource sets with usage ‘codebook’ or ‘nonCodebook’ and has two activated/indicated Joint DL/UL TCI states, the UE should associate the transmission of the first SRS resource set with the common beam index explicitly configured in that SRS resource set. Similarly, the UE should associate the transmission of the second SRS resource set with the common beam index explicitly configured in that SRS resource set. In this embodiment, the first SRS resource set and the second SRS resource set may be associated with different common beam indices.
In the following embodiments it is assumed that a common beam index is explicitly configured per SRS resource (as specified in TS 38.331 v16.7.0) in an SRS resource set with usage ‘codebook’ or ‘nonCodebook’, as schematically illustrated below:
SRS-Resource is accordingly an example of configuration(s) 24 herein in
In one embodiment, the UE is configured with one SRS resource set with usage ‘codebook’, where the SRS resource set consists of two SRS resources, and where each SRS resource is explicitly configured with one common beam index. In one embodiment, when the UE is triggered for transmission of the SRS resource set with usage ‘codebook and has two indicated Joint DL/UL TCI states, the UE should associate the transmission of the first SRS resource with the common beam index explicitly configured in the first SRS resource and the second SRS resource with the common beam index explicitly configured in the second SRS resource. When the UE is scheduled with PUSCH transmission and is indicated with two Joint DL/UL TCI states, a first PUSCH transmission that is associated with a first SRS resource, should be transmitted using the common beam index explicitly configured in the first SRS resource, and a second PUSCH transmission that is associated with a second SRS resource, should be transmitted using the common beam index explicitly configured in the second SRS resource. The association between an SRS resource and a PUSCH transmission could for example be based on one or more SRI and/or TPMI fields included in the DCI scheduling the PUSCH, where for example a first SRI and/or TPMI field (or codepoint(s) of a SRI/TPMI field) is associated with a first SRS resource and a first PUSCH transmission, and a second SRI and/or TPMI field (or codepoint(s) of a SRI/TPMI fields) is associated with a second SRS resource and a second PUSCH transmission.
The same embodiment can be applied for an SRS resource set with usage ‘nonCodebook’, where each of the SRS resources in the SRS resource set with usage ‘nonCodebook’ is configured with one out of two explicit common beam indexes.
In one embodiment, in case the UE is configured with two SRS resources in a SRS resource set with usage ‘codebook’, and where each SRS resource is explicitly configured with a common beam index, in case the UE is indicated with a single Joint DL/UL TCI state, the UE should de-activate one of the SRS resources (i.e. even if the UE is triggered with SRS transmission of the both SRS resources, the UE should only transmit one of them).
In another embodiment, a flag to enable using unified Joint DL/UL state for SRS Resource's configured in an SRS resource set with usage set to ‘codebook’ based or ‘non codebook’ based PUSCH is configured inside the SRS Resource as shown below:
This flag (denoted as ‘followUnifiedTCIstate’) indicates to the UE that when PUSCH is scheduled by indicating a specific SRS resource from an SRS resource set with usage set to ‘codebook’ based or ‘non codebook’ based PUSCH, then the transmit spatial filters to be used for PUSCH transmission associated with the indicated SRS resource is derived from the indicated/activated Joint DL/UL TCI state.
However, for the multi-TRP scenario, there will be multiple (e.g., 2) Joint DL/UL TCI states that are indicated/activated to the UE. In this case, multiple (e.g., 2) SRS resources belonging to the same SRS resource set are configured to the UE wherein each SRS resource represents a transmission towards a TRP. To associate the SRS resource with one of the Joint DL/UL TCI states, a ‘common_beam_index’ is configured per SRS resource. In one embodiment, when the UE is triggered for transmission of the two SRS resources belonging to a SRS resource set with usage ‘codebook’ or ‘nonCodebook’ and has two activated/indicated Joint DL/UL TCI states, the UE should associate the transmission of the first SRS resource with the common beam index explicitly configured in that SRS resource. Similarly, the UE should associate the transmission of the second SRS resource with the common beam index explicitly configured in that SRS resource. In this embodiment, the first SRS resource and the second SRS resource may be associated with different common beam indices.
In view of the modifications and variations herein,
In some embodiments, the configuration for each uplink channel or signal includes a TCI state pointer that points to one or more of the multiple activated unified TCI states with which the uplink channel or signal is associated. In one or more of these embodiments, the TCI state pointer is a common beam index. In one or more of these embodiments, activation signaling that activates the multiple unified TCI states associates the multiple unified TCI states with respective indices or identifiers. In some embodiments, the TCI state pointer included in the configuration for each uplink channel or signal points to one or more activated unified TCI states by pointing to the one or more indices or identifiers associated with the one or more activated unified TCI states. In one or more of these embodiments, the multiple activated unified TCI states includes first and second activated unified TCI states. In some embodiments, the activation signaling associates the first and second activated unified TCI states with first and second identifiers, respectively. In some embodiments, the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the first identifier, the second identifier, or both the first identifier and the second identifier. In one or more of these embodiments, the multiple activated unified TCI states includes first and second activated unified TCI states. In some embodiments, the activation signaling associates the first and second activated unified TCI states with first and second identifiers, respectively. In some embodiments, a field in downlink control signaling indicates whether the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the first identifier, the second identifier, or both the first identifier and the second identifier. Alternatively, a field in downlink control signaling indicates whether the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the second identifier, the first identifier, or both the second identifier and the first identifier. In one or more of these embodiments, the activation signaling includes a first field that activates the first activated unified TCI state and a second field that activates the second activated unified TCI state. In some embodiments, the first field occurs before the second field in the activation signaling. In one or more of these embodiments, the method further comprises receiving the activation signaling (Block 1410). In one or more of these embodiments, the activation signaling is received after receipt of the configuration for at least one of the one or more uplink channels or signals.
In some embodiments, the configuration for each uplink channel or signal explicitly indicates with which of the multiple activated unified TCI states the uplink channel or signal is associated.
In some embodiments, the multiple activated unified TCI states are associated with multiple respective transmission reception points, TRPs.
In some embodiments, said receiving comprises receiving, for each of one or more uplink channels, a configuration that indicates with which of multiple activated unified TCI states the uplink channel is associated. In one or more of these embodiments, the one or more uplink channels include an uplink data channel. In one or more of these embodiments, the uplink data channel is a Physical Uplink Shared Channel, PUSCH. In one or more of these embodiments, the configuration received for the PUSCH is a PUSCH configuration or a PUSCH serving cell configuration.
In some embodiments, the configuration for at least one uplink channel or signal includes a field that indicates whether a unified TCI framework or a spatial relation framework applies.
In some embodiments, said receiving comprises receiving, for each of one or more uplink signals, a configuration that indicates with which of multiple activated unified TCI states the uplink signal is associated. In one or more of these embodiments, the one or more uplink signals are one or more sounding reference signal, SRS, signals. In one or more of these embodiments, the one or more SRS signals are one or more SRS signals in one or more SRS resource sets. In one or more of these embodiments, the configuration for an SRS signal in an SRS resource set indicates with which of the multiple activated unified TCI states the SRS signal in that SRS resource set is associated by indicating with which of the multiple activated unified TCI states the SRS resource set is associated. In one or more of these embodiments, the configuration received for each of the one or more SRS signals in the one or more SRS resource sets is an SRS resource set configuration. In one or more of these embodiments, the one or more SRS signals are one or more SRS signals in one or more SRS resources of the same SRS resource set. In one or more of these embodiments, the configuration for an SRS signal in an SRS resource of the SRS resource set indicates with which of the multiple activated unified TCI states the SRS signal in that SRS resource is associated by indicating with which of the multiple activated unified TCI states the SRS resource is associated. In one or more of these embodiments, the configuration received for each of the one or more SRS signals in the one or more SRS resources of the SRS resource set is an SRS resource configuration.
In some embodiments, each activated unified TCI state contains quasi co-location, QCL, information between antenna ports of the communication device.
In some embodiments, each activated unified TCI state is applicable for multiple channels or signals.
In some embodiments, the multiple activated unified TCI states are joint uplink/downlink TCI states. In some embodiments, each joint TCI state is applicable for both downlink transmissions and uplink transmissions.
In some embodiments, the multiple activated unified TCI states are uplink TCI states. In some embodiments, each uplink TCI state is applicable only for uplink transmissions.
In some embodiments, the method further comprises determining, for each of the one or more uplink channels or signals, a spatial filter for the uplink channel or signal based on one or more activated unified TCI states that are associated with the uplink channel or signal according to the configuration received for that uplink channel or signal (Block 1420). In one or more of these embodiments, the method further comprises transmitting the one or more uplink channels or signals using the one or more spatial filters determined for the one or more uplink channels or signals (Block 1430).
In some embodiments, the configuration for each uplink channel or signal includes a TCI state pointer that points to one or more of the multiple activated unified TCI states with which the uplink channel or signal is associated. In one or more of these embodiments, the TCI state pointer is a common beam index. In one or more of these embodiments, activation signaling that activates the multiple unified TCI states associates the multiple unified TCI states with respective indices or identifiers. In some embodiments, the TCI state pointer included in the configuration for each uplink channel or signal points to one or more activated unified TCI states by pointing to the one or more indices or identifiers associated with the one or more activated unified TCI states. In one or more of these embodiments, the multiple activated unified TCI states includes first and second activated unified TCI states. In some embodiments, the activation signaling associates the first and second activated unified TCI states with first and second identifiers, respectively. In some embodiments, the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the first identifier, the second identifier, or both the first identifier and the second identifier. In one or more of these embodiments, the multiple activated unified TCI states includes first and second activated unified TCI states. In some embodiments, the activation signaling associates the first and second activated unified TCI states with first and second identifiers, respectively. In some embodiments, a field in downlink control signaling indicates whether the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the first identifier, the second identifier, or both the first identifier and the second identifier. Alternatively, a field in downlink control signaling indicates whether the TCI state pointer included in the configuration for at least one uplink channel or signal points to the first activated unified TCI state and/or the second activated unified TCI state by pointing to the second identifier, the first identifier, or both the second identifier and the first identifier. In one or more of these embodiments, the activation signaling includes a first field that activates the first activated unified TCI state and a second field that activates the second activated unified TCI state. In some embodiments, the first field occurs before the second field in the activation signaling. In one or more of these embodiments, the method further comprises transmitting the activation signaling (Block 1510). In one or more of these embodiments, the activation signaling is transmitted after transmission of the configuration for at least one of the one or more uplink channels or signals.
In some embodiments, the configuration for each uplink channel or signal explicitly indicates with which of the multiple activated unified TCI states the uplink channel or signal is associated.
In some embodiments, the multiple activated unified TCI states are associated with multiple respective transmission reception points, TRPs.
In some embodiments, said transmitting comprises transmitting, for each of one or more uplink channels, a configuration that indicates with which of multiple activated unified TCI states the uplink channel is associated. In one or more of these embodiments, the one or more uplink channels include an uplink data channel. In one or more of these embodiments, the uplink data channel is a Physical Uplink Shared Channel, PUSCH. In one or more of these embodiments, the configuration transmitted for the PUSCH is a PUSCH configuration or a PUSCH serving cell configuration.
In some embodiments, the configuration for at least one uplink channel or signal includes a field that indicates whether a unified TCI framework or a spatial relation framework applies.
In some embodiments, said transmitting comprises transmitting, for each of one or more uplink signals, a configuration that indicates with which of multiple activated unified TCI states the uplink signal is associated. In one or more of these embodiments, the one or more uplink signals are one or more sounding reference signal, SRS, signals. In one or more of these embodiments, the one or more SRS signals are one or more SRS signals in one or more SRS resource sets. In one or more of these embodiments, the configuration for an SRS signal in an SRS resource set indicates with which of the multiple activated unified TCI states the SRS signal in that SRS resource set is associated by indicating with which of the multiple activated unified TCI states the SRS resource set is associated. In one or more of these embodiments, the configuration transmitted for each of the one or more SRS signals in the one or more SRS resource sets is an SRS resource set configuration. In one or more of these embodiments, the one or more SRS signals are one or more SRS signals in one or more SRS resources of the same SRS resource set. In one or more of these embodiments, the configuration for an SRS signal in an SRS resource of the SRS resource set indicates with which of the multiple activated unified TCI states the SRS signal in that SRS resource is associated by indicating with which of the multiple activated unified TCI states the SRS resource is associated. In one or more of these embodiments, the configuration transmitted for each of the one or more SRS signals in the one or more SRS resources of the SRS resource set is an SRS resource configuration.
In some embodiments, each activated unified TCI state contains quasi co-location, QCL, information between antenna ports of the communication device.
In some embodiments, each activated unified TCI state is applicable for multiple channels or signals.
In some embodiments, the multiple activated unified TCI states are joint uplink/downlink TCI states. In some embodiments, each joint TCI state is applicable for both downlink transmissions and uplink transmissions.
In some embodiments, the multiple activated unified TCI states are uplink TCI states. In some embodiments, each uplink TCI state is applicable only for uplink transmissions.
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. In some embodiments, 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. In some embodiments, 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. In some embodiments, 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.
More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, 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. For instance, 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. 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. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.
Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.
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.
In this regard, 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.
In the example, the communication system 1800 includes a telecommunication network 1802 that includes an access network 1804, such as a radio access network (RAN), and a core network 1806, which includes one or more core network nodes 1808. The access network 1804 includes one or more access network nodes, such as network nodes 1810a and 1810b (one or more of which may be generally referred to as network nodes 1810), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1810 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1812a, 1812b, 1812c, and 1812d (one or more of which may be generally referred to as UEs 1812) to the core network 1806 over one or more wireless connections.
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. Moreover, in different embodiments, the communication system 1800 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 1800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
The UEs 1812 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 1810 and other communication devices. Similarly, the network nodes 1810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1812 and/or with other network nodes or equipment in the telecommunication network 1802 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 1802.
In the depicted example, the core network 1806 connects the network nodes 1810 to one or more hosts, such as host 1816. 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 1806 includes one more core network nodes (e.g., core network node 1808) 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 1808. 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).
The host 1816 may be under the ownership or control of a service provider other than an operator or provider of the access network 1804 and/or the telecommunication network 1802, and may be operated by the service provider or on behalf of the service provider. The host 1816 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.
As a whole, the communication system 1800 of
In some examples, the telecommunication network 1802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1802. For example, the telecommunications network 1802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs.
In some examples, the UEs 1812 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1804. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, 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).
In the example, the hub 1814 communicates with the access network 1804 to facilitate indirect communication between one or more UEs (e.g., UE 1812c and/or 1812d) and network nodes (e.g., network node 1810b). In some examples, the hub 1814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1814 may be a broadband router enabling access to the core network 1806 for the UEs. As another example, the hub 1814 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1810, or by executable code, script, process, or other instructions in the hub 1814. As another example, the hub 1814 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. As another example, the hub 1814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1814 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
The hub 1814 may have a constant/persistent or intermittent connection to the network node 1810b. The hub 1814 may also allow for a different communication scheme and/or schedule between the hub 1814 and UEs (e.g., UE 1812c and/or 1812d), and between the hub 1814 and the core network 1806. In other examples, the hub 1814 is connected to the core network 1806 and/or one or more UEs via a wired connection. Moreover, the hub 1814 may be configured to connect to an M2M service provider over the access network 1804 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1810 while still connected via the hub 1814 via a wired or wireless connection. In some embodiments, the hub 1814 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 1810b. In other embodiments, the hub 1814 may be a non-dedicated hub—that is, a device which is capable of operating to route communications between the UEs and network node 1810b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
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). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, 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). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
The UE 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input/output interface 1906, a power source 1908, a memory 1910, a communication interface 1912, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in
The processing circuitry 1902 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 1910. The processing circuitry 1902 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. For example, the processing circuitry 1902 may include multiple central processing units (CPUs).
In the example, the input/output interface 1906 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 1900. 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.
In some embodiments, the power source 1908 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 1908 may further include power circuitry for delivering power from the power source 1908 itself, and/or an external power source, to the various parts of the UE 1900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1908 to make the power suitable for the respective components of the UE 1900 to which power is supplied.
The memory 1910 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. In one example, the memory 1910 includes one or more application programs 1914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1916. The memory 1910 may store, for use by the UE 1900, any of a variety of various operating systems or combinations of operating systems.
The memory 1910 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. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1910 may allow the UE 1900 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 1910, which may be or comprise a device-readable storage medium.
The processing circuitry 1902 may be configured to communicate with an access network or other network using the communication interface 1912. The communication interface 1912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1922. The communication interface 1912 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 1918 and/or a receiver 1920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1918 and receiver 1920 may be coupled to one or more antennas (e.g., antenna 1922) and may share circuit components, software or firmware, or alternatively be implemented separately.
In the illustrated embodiment, communication functions of the communication interface 1912 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. 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.
Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1912, 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).
As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, 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 (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT 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-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1900 shown in
As yet another specific example, in an IoT scenario, 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. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, 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.
In practice, any number of UEs may be used together with respect to a single use case. For example, 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. When the user makes changes from the remote controller, 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. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
Other examples of 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).
The network node 2000 includes a processing circuitry 2002, a memory 2004, a communication interface 2006, and a power source 2008. The network node 2000 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. In certain scenarios in which the network node 2000 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 2000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 2004 for different RATs) and some components may be reused (e.g., a same antenna 2010 may be shared by different RATs). The network node 2000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2000, 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 2000.
The processing circuitry 2002 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 2000 components, such as the memory 2004, to provide network node 2000 functionality.
In some embodiments, the processing circuitry 2002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 2002 includes one or more of radio frequency (RF) transceiver circuitry 2012 and baseband processing circuitry 2014. In some embodiments, the radio frequency (RF) transceiver circuitry 2012 and the baseband processing circuitry 2014 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 2012 and baseband processing circuitry 2014 may be on the same chip or set of chips, boards, or units.
The memory 2004 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 2002. The memory 2004 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 2002 and utilized by the network node 2000. The memory 2004 may be used to store any calculations made by the processing circuitry 2002 and/or any data received via the communication interface 2006. In some embodiments, the processing circuitry 2002 and memory 2004 is integrated.
The communication interface 2006 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 2006 comprises port(s)/terminal(s) 2016 to send and receive data, for example to and from a network over a wired connection. The communication interface 2006 also includes radio front-end circuitry 2018 that may be coupled to, or in certain embodiments a part of, the antenna 2010. Radio front-end circuitry 2018 comprises filters 2020 and amplifiers 2022. The radio front-end circuitry 2018 may be connected to an antenna 2010 and processing circuitry 2002. The radio front-end circuitry may be configured to condition signals communicated between antenna 2010 and processing circuitry 2002. The radio front-end circuitry 2018 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 2018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2020 and/or amplifiers 2022. The radio signal may then be transmitted via the antenna 2010. Similarly, when receiving data, the antenna 2010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2018. The digital data may be passed to the processing circuitry 2002. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
In certain alternative embodiments, the network node 2000 does not include separate radio front-end circuitry 2018, instead, the processing circuitry 2002 includes radio front-end circuitry and is connected to the antenna 2010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2012 is part of the communication interface 2006. In still other embodiments, the communication interface 2006 includes one or more ports or terminals 2016, the radio front-end circuitry 2018, and the RF transceiver circuitry 2012, as part of a radio unit (not shown), and the communication interface 2006 communicates with the baseband processing circuitry 2014, which is part of a digital unit (not shown).
The antenna 2010 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 2010 may be coupled to the radio front-end circuitry 2018 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 2010 is separate from the network node 2000 and connectable to the network node 2000 through an interface or port.
The antenna 2010, communication interface 2006, and/or the processing circuitry 2002 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 2010, the communication interface 2006, and/or the processing circuitry 2002 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 2008 provides power to the various components of network node 2000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2000 with power for performing the functionality described herein. For example, the network node 2000 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 2008. As a further example, the power source 2008 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 2000 may include additional components beyond those shown in
The host 2100 includes processing circuitry 2102 that is operatively coupled via a bus 2104 to an input/output interface 2106, a network interface 2108, a power source 2110, and a memory 2112. 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
The memory 2112 may include one or more computer programs including one or more host application programs 2114 and data 2116, which may include user data, e.g., data generated by a UE for the host 2100 or data generated by the host 2100 for a UE. Embodiments of the host 2100 may utilize only a subset or all of the components shown. The host application programs 2114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 2114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 2100 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 2114 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.
Applications 2202 (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 2204 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 2206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2208a and 2208b (one or more of which may be generally referred to as VMs 2208), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 2206 may present a virtual operating platform that appears like networking hardware to the VMs 2208.
The VMs 2208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2206. Different embodiments of the instance of a virtual appliance 2202 may be implemented on one or more of VMs 2208, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
In the context of NFV, a VM 2208 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 2208, and that part of hardware 2204 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 2208 on top of the hardware 2204 and corresponds to the application 2202.
Hardware 2204 may be implemented in a standalone network node with generic or specific components. Hardware 2204 may implement some functions via virtualization. Alternatively, hardware 2204 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 2210, which, among others, oversees lifecycle management of applications 2202. In some embodiments, hardware 2204 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. In some embodiments, some signaling can be provided with the use of a control system 2212 which may alternatively be used for communication between hardware nodes and radio units.
Like host 2100, embodiments of host 2302 include hardware, such as a communication interface, processing circuitry, and memory. The host 2302 also includes software, which is stored in or accessible by the host 2302 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 2306 connecting via an over-the-top (OTT) connection 2350 extending between the UE 2306 and host 2302. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2350.
The network node 2304 includes hardware enabling it to communicate with the host 2302 and UE 2306. The connection 2360 may be direct or pass through a core network (like core network 1806 of
The UE 2306 includes hardware and software, which is stored in or accessible by UE 2306 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 2306 with the support of the host 2302. In the host 2302, an executing host application may communicate with the executing client application via the OTT connection 2350 terminating at the UE 2306 and host 2302. In providing the service to the user, 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 2350 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 2350.
The OTT connection 2350 may extend via a connection 2360 between the host 2302 and the network node 2304 and via a wireless connection 2370 between the network node 2304 and the UE 2306 to provide the connection between the host 2302 and the UE 2306. The connection 2360 and wireless connection 2370, over which the OTT connection 2350 may be provided, have been drawn abstractly to illustrate the communication between the host 2302 and the UE 2306 via the network node 2304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
As an example of transmitting data via the OTT connection 2350, in step 2308, the host 2302 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 2306. In other embodiments, the user data is associated with a UE 2306 that shares data with the host 2302 without explicit human interaction. In step 2310, the host 2302 initiates a transmission carrying the user data towards the UE 2306. The host 2302 may initiate the transmission responsive to a request transmitted by the UE 2306. The request may be caused by human interaction with the UE 2306 or by operation of the client application executing on the UE 2306. The transmission may pass via the network node 2304, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2312, the network node 2304 transmits to the UE 2306 the user data that was carried in the transmission that the host 2302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2314, the UE 2306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2306 associated with the host application executed by the host 2302.
In some examples, the UE 2306 executes a client application which provides user data to the host 2302. The user data may be provided in reaction or response to the data received from the host 2302. Accordingly, in step 2316, the UE 2306 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 2306. Regardless of the specific manner in which the user data was provided, the UE 2306 initiates, in step 2318, transmission of the user data towards the host 2302 via the network node 2304. In step 2320, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2304 receives user data from the UE 2306 and initiates transmission of the received user data towards the host 2302. In step 2322, the host 2302 receives the user data carried in the transmission initiated by the UE 2306.
One or more of the various embodiments improve the performance of OTT services provided to the UE 2306 using the OTT connection 2350, in which the wireless connection 2370 forms the last segment.
In an example scenario, factory status information may be collected and analyzed by the host 2302. As another example, the host 2302 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2302 may store surveillance video uploaded by a UE. As another example, the host 2302 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 2302 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.
In some examples, 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. There may further be an optional network functionality for reconfiguring the OTT connection 2350 between the host 2302 and UE 2306, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 2302 and/or UE 2306. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2350 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 2350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2304. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 2302. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2350 while monitoring propagation times, errors, etc.
Although the computing devices described herein (e.g., UEs, network nodes, hosts) 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, 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. In another example, 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.
In certain embodiments, some or all of the functionality described herein may be provided by 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. In alternative embodiments, 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. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, 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:
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2023/055280 | 3/2/2023 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63316962 | Mar 2022 | US |
