Title - METHODS PERFORMED BY A WIRELESS DEVICE AND THROUGH A NETWORK NODE, AND SAID WIRELESS DEVICE AND NETWORK NODE

Abstract

According to some embodiments, a method performed by a wireless device comprises obtaining (512) a Tracking Reference Signal (TRS) / Channel Status Information Reference Signal (CSI-RS) resource configuration and an underlying beam association for a plurality of TRS / CSI-RS instances and obtaining (514) an availability indicator. The availability indicator indicates an association of one or more of the plurality of TRS / CSI-RS instances and underlying beam association. The method further comprises receiving (518) layer one signaling on a beam. The layer one signaling indicates that a TRS / CSI-RS instance is available on at least one TRS / CSI-RS instance out of the plurality of TRS / CSI-RS instances.The method further comprises determining (520) that one or more of the plurality of TRS / CSI-RS occasions have TRS / CSI-RS available based on the availability indicator and layer one signaling; and receiving (522) TRS / CSI-RS on at least one of the determined TRS / CSI-RS occasions.

Description

REFERENCE SIGNAL AVAILABILITY SIGNALING BEAM-RELATED TRACKING TECHNICAL FIELD The methods of implementation of this disclosure relate to wireless communications and, more particularly, to beam-related tracking reference signal (TRS) availability signaling. BACKGROUND In general, all terms used herein shall be interpreted according to their current meaning in the relevant technical field, unless a different meaning is clearly given and / or implied from the context in which they are used. All references to an element, apparatus, component, means, stage, etc., shall be clearly interpreted as referring to at least one instance of the element, apparatus, component, means, stage, etc., unless explicitly stated otherwise. The steps of any of the methods disclosed herein need not be carried out in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or it is implied that one step must follow or precede another. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, where appropriate.Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, where appropriate. Other objectives, features, and advantages of the appended embodiments will become apparent from the following description. Third-generation (3GPP), fifth-generation (5G), New Radio (NR), and Long-Term Evolution (LTE) wireless networks generally use paging to inform a user device (UD) that the network has signaling or data to send to the UD. Usulent-mode UDs receive information about the paging configuration through upper-layer signaling (such as system information signaling). For each free discontinuous receive (I-DRX) cycle (or free-mode DRX cycle), a UE begins processing (e.g., activation operations) before its paging occasion, e.g., to receive one or more synchronization signal blocks (SSB) for functions such as automatic gain control (AGC). 1810720 of 47 and time frequency synchronization. On the paging occasion, the UE attempts to decode a paging downlink control information (DCI) (e.g., DCI 1-0 with cyclic redundancy check (CRC) encoded by a paging radio time network identifier (P-RNTI)), and if the paging DCI is detected, the UE can also decode the paging physical downlink shared channel (PDSCH) assigned by the paging DCI to identify if it has been sought (e.g., if the paging message contains the UE's 5GS-TMSI). The paging DCI includes the modulation and coding scheme (MCS), resource allocation, transport block (TB) scaling field, redundancy version, etc., associated with the programmed PDSCH. The paging DCI can also be used to indicate a system information change (SI), in which case the UE may not need to decode the corresponding PDSCH. The content of the DCI paging format, as mentioned in TS 38.212, is shown below. The following information is transmitted in DCI format 1_0 with CRC encrypted by P-RNTI: • Short Message Indicator - 2 bits according to Table 7.3.1.2.1-1. • Short Messages - 8 bits in accordance with Clause 6.5 of TS38.331. If only programming information for Paging is carried, this bit field is reserved. • Resource allocation in the frequency domain |)ο£2(.¥^'B1'^ + 1) / 2)] bits. If only the short message is carried, this bit field is reserved. is the size of CORESET 0 • Time domain resource allocation: 4 bits, as defined in clause 5.1.2.1 of TS38.214. If only the short message is carried, this bit field is reserved. • VRB to PRB mapping - 1 bit according to Table 7.3.1.2.2-5. If only the short message is carried, this bit field is reserved. • Modulation and coding scheme - 5 bits as defined in Clause 5.1.3 of TS38.214, using Table 5.1.3.1-1. If only the short message is carried, this bit field is reserved. TB scaling: 2 bits as defined in Clause 5.1.3.2 of TS38.214. If only the short message is carried, this bit field 1810720 of 47 is reserved. • Reserved bits: 8 bits to operate in a cell with access to the shared spectrum channel; otherwise 6 bits. If additional reference signals, such as a Tracking Reference Signal (TRS), are provided to a free / idle UE, the UE can reduce its wake-up time and continue receiving sufficient signals (SSB, TRS, etc.) before its paging and paging PDSCH decoding event, thereby reducing the UE's power consumption. However, sending additional TRS to a free / idle UE increases network power consumption. Therefore, sending additional TRS only to a connected-mode UE allows a free UE to benefit from the UE's power savings without increasing network power consumption. A current design allows a network to indicate configured potential TRS / CSI-RS occasions through system information signaling to idle / free UEs, while whether or not a TRS / CSI-RS is transmitted on a potential TRS / CSI-RS occasion (or TRS / CSI-RS occasion, for brevity) is left to the network implementation. Proposals are also being considered that provide an explicit / implicit indication of the availability of TRS / CSI-RS on a TRS / CSI-RS occasion, such as: 1) reporting via SIB that TRS is always present on the TRS / CSI-RS occasion, 2) using L1 signaling, such as a paging DCI, to indicate that TRS / CSI-RS is available on a TRS / CSI-RS occasion, 3) the UE implementation can blindly detect whether TRS / CSI-RS is available on a TRS / CSI-RS occasion, and / or 4) TRS / CSI-RS is always present on a TRS / CSI-RS occasion if there is a corresponding paging message (paging PDSCH) on a next PO (paging occasion). Currently, there are some challenges. For example, when L1-based availability signaling is used to inform a free UE (i.e., a UE in the RRC_Idle / Inactive state) of the actual TRS transmission, it can be implemented in a paging DCI or another signal, such as an early paging indicator, which can also be a DCI. For a paging DCI, reserved bits are typically used to indicate TRS availability. Currently, there are 6 reserved bits in a paging DCI. Furthermore, because the network can enable / disable TRS in different beams depending on whether at least one connected UE is using TRS, it is beneficial for a free UE to know the TRS availability at each beam level. 1810720 of 47 An NR UE can be configured with TRS resources on up to 8 beams in FR1 and 64 beams in FR2. If per-beam availability based on bitmap / code point is used within the paging DCI, the number of reserved bits cannot be adapted to the per-beam availability signaling, and therefore, selective beam availability signaling must be optimized. In one proposal, a UE is aware of TRS availability based solely on the availability indication in the paging DCI, which is received in a specific beam. The paging DCI is swept over SSB beams configured in free mode, and therefore, for example, if the UE receives an indication that TRS is available via the paging DCI received in the first beam, it only applies to the TRS associated with that beam, and not to any other potential TRS for which its availability is shared with the free UE. While this approach significantly reduces the overhead of beam availability signaling, it has its own drawbacks. For example, if the UE is configured with eight beams in free mode, the UE typically monitors the paging DCI on the strongest beam and ignores the others, thus only becoming aware of TRS availability on the strongest beam. If this beam changes, for example, in the next DRX cycle, the UE will not know whether the TRS associated with the second strongest beam is available, which can impact its performance. Therefore, there is a need for flexible beam selective TRS availability signaling that allows the network to configure availability signaling in the paging DCI or a paging early indicator (PEI) in a way that fits within the bits reserved for the paging DCI, or reduces overhead for PEI, while also not impacting UE performance in free mode, particularly from a power consumption perspective. SYNTHESIS Based on the description above, certain challenges currently exist with beam-related Tracking Reference Signal (TRS) availability signaling. Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. Specific embodiments include an efficient mechanism whereby a UE obtains TRS availability by using L1-based signaling on a beam-selective basis. The UE receives an upper-layer configuration based on which it can determine an association of the availability bit field in a DCI and the applicability of that information to one or more 1810720 of 47 bundles. Some implementations include an explicit field in the upper-layer signaling (e.g., System Information Base (SIB)) to indicate one or more field values ​​related to beam-related availability information. For example, the field can be set to 'individual,' meaning that L1 availability on a DCI detected in beam X applies to TRS availability in beam X, or 'all,' meaning that L1 availability on a DCI detected in any beam X applies to TRS availability in all beams configured by upper layers. The field can also be set to 'group availability,' meaning that L1 availability on a DCI detected in any beam within a group of beams applies to TRS availability in all beams belonging to that group. The following is an example with up to four beam groups, where the upper layers can explicitly configure the groups. { 'Group1' - 1st group of beams configured by upper layers, 'Group2' - 2nd group of beams configured by upper layers, 'Group3' - 3rd group of beams configured by upper layers, 'Group4' - 4th group of beams configured by upper layers,} In general, specific implementations include an explicit upper-layer configuration of L1 TRS availability in a DCI detected in a first beam and its applicability to TRS availability in one or more beams. Some implementations support code points in the upper-layer configuration that explicitly indicate at least one individual TRS availability. Additionally, some implementations include upper-layer indication of beam groups for association with availability indication. According to some embodiments, a method implemented by a wireless device comprises obtaining a TRS / Channel Status Information Reference Signal (CSI-RS) and an underlying beam association for a plurality of TRS / CSI-RS instances and obtaining an availability indicator. The availability indicator indicates the association of one or more of the plurality of TRS / CSI-RS instances and underlying beam associations. The method further comprises receiving Layer One signaling on a beam. The Layer One signaling indicates that a TRS / CSI-RS instance is available on at least one of the plurality of TRS / CSI-RS instances. 1810720 of 47 TRS / CSI-RS instances (e.g., bitmap availability). The method further comprises determining one or more of the plurality of TRS / CSI-RS instances have TRS / CSI-RS available based on the availability indicator and layer one signaling; and receiving TRS / CSI-RS on at least one of the determined TRS / CSI-RS instances. In particular embodiments, the reception of layer one signaling indicating that a TRS / CSI-RS is available at least one TRS / CSI-RS occasion out of the plurality of TRS / CSI-RS occasions comprises receiving at least one of a paging downlink control indication (DCI) and an early paging indicator (PEI). In particular embodiments, the availability indicator associates a TRS / CSI-RS occasion with an individual beam, and the determination that one or more of the plurality of TRS / CSI-RS occasions have TRS / CSI-RS available comprises determining that TRS / CSI-RS is available on one of the TRS / CSI-RS occasions associated with the beam in which the layer one signaling is received. In particular embodiments, the availability indicator associates a TRS / CSI-RS occasion with all beams, and the determination that one or more of the plurality of TRS / CSI-RS occasions have TRS / CSI-RS available comprises determining that TRS / CSI-RS is available on all TRS / CSI-RS occasions associated with the underlying beams of the entire plurality of TRS / CSI-RS occasions. In particular embodiments, the availability indicator associates a TRS / CSI-RS occasion with a group of beams, and the determination that one or more of the plurality of TRS / CSI-RS occasions have TRS / CSI-RS available comprises determining that TRS / CSI-RS is available on all TRS / CSI-RS occasions associated with the underlying beams in the group of beams. In particular embodiments, the method further comprises obtaining an indication that associates a subset of the underlying beams from the plurality of TRS / CSI-RS instances into a group of beams. In particular embodiments, the availability indicator is associated with one or more validity durations. According to some embodiments, a wireless device comprises processing circuitry operable to carry out any of the wireless device methods described above. Also disclosed is a software product comprising a non-transient, computer-readable medium that stores program code 1810720 of 47 computer-readable, wherein the computer-readable program code is operable when executed by processing circuitry to perform any of the methods performed by the wireless device described above. According to some embodiments, a method performed by a network node comprises: transmitting a TRS / CSI-RS resource configuration and an underlying beam association for a plurality of TRS / CSI-RS instances to a wireless device and transmitting an availability indicator to the wireless device. The availability indicator indicates an association of one or more of the plurality of TRS / CSI-RS instances and underlying beam association. In particular embodiments, the method further comprises transmitting layer one signaling in a beam to the wireless device. The layer one signaling indicates that a TRS / CSI-RS instance is available at least once out of a plurality of TRS / CSI-RS instances (e.g., bitmap availability). In particular embodiments, the transmission of layer one signaling indicating that a TRS / CSI-RS is available on at least one TRS / CSI-RS occasion out of the plurality of TRS / CSI-RS occasions comprises transmitting at least one of a paging DCI and a PEI. In particular embodiments, the availability indicator associates a TRS / CSI-RS occasion with an individual beam, associates a TRS / CSI-RS occasion with all beams, or associates a TRS / CSI-RS occasion with a group of beams. In particular embodiments, the method further comprises transmitting an indication that associates a subset of the underlying beams of the plurality of TRS / CSI-RS instances into a group of beams. In particular embodiments, the availability indicator is associated with one or more validity durations. According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above. Also disclosed is a computer program product comprising a non-transient, computer-readable medium that stores computer-readable program code, wherein the computer-readable program code is operable when executed by processing circuitry to perform any of the methods performed by the network node described above. 1810720 of 47 Certain embodiments can provide one or more of the following technical advantages. For example, some embodiments increase the UE's energy savings by using TRS / CSI-RS before a paging occasion (PO), and the UE learns about TRS / CSI-RS availability through L1-based and beam-based signaling. A UE can choose to decode only one or more DCIs, allowing it to learn about TRS transmission on a beam-by-beam basis more efficiently. Network signaling for beam availability is efficient and has low overhead. BRIEF DESCRIPTION OF THE DRAWINGS For a more complete understanding of the disclosed embodiments and their characteristics and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: Figure 1 is a slot diagram illustrating a TDD PCell and an FDD SCell; Figure 2 illustrates an example of downlink processing times for a PCell at 30 kHz and an SCell at 15 kHz; Figure 3 is a block diagram illustrating an example of a wireless network; Figure 4 illustrates an example of user equipment, according to certain forms of implementation; Figure 5 is a flowchart illustrating an example method in a wireless device, according to certain embodiments; Figure 6 is a flowchart illustrating an example method on a network node, according to certain forms of implementation; Figure 7 illustrates a schematic block diagram of a wireless device and a network node in a wireless network, according to certain embodiments; Figure 8 illustrates an example virtualization environment, according to certain forms of implementation; Figure 9 illustrates an example of a telecommunications network connected through an intermediate network to a host computer, according to certain embodiments; Figure 10 illustrates an example of a host computer communicating via a base station with a user computer through a partially wireless connection, according to certain embodiments; 1810720 of 47 Figure 11 is a flowchart illustrating an implemented method, according to certain forms of realization; Figure 12 is a flowchart illustrating a method implemented in a communication system, according to certain forms of realization; Figure 13 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments; and Figure 14 is a flowchart illustrating a method implemented in a communication system, according to certain forms of realization. DETAILED DESCRIPTION As described above, certain challenges currently exist with beam-related Tracking Reference Signal (TRS) availability signaling. Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. Specific embodiments include an efficient mechanism whereby a user equipment (UE) obtains tracking reference signal (TRS) availability by using L1-based signaling on a beam-selective basis. The UE receives a higher-layer configuration based on which it can determine an association of the availability bit field in downlink control information (DCI) and the applicability of that information to one or more beams. The specific embodiments are described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be interpreted as being limited solely to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to persons of intermediate skill. In some implementations, a free UE (i.e., a UE in RRC_Idle / Inactive states) receives one or more TRS / CSI-RS resource configurations via system information (SI) or other upper-layer mechanisms, for example, as part of an existing system information block (SIB), a dedicated SIB, or dedicated signaling. The UE is also explicitly notified of the availability of TRS / CSI-RS resources on the provided configured occasions. The UE knows whether the TRS / CSI-RS is currently being transmitted on one or more occasions. 1810720 of 47 Explicit indication may include L1-based signaling, such as a paging DCI or an early paging indicator (PEI). For example, an availability bit field can be configured in the reserved bits of the paging DCI for this purpose. Explicit indication may be independent for each TRS / CSI-RS configuration, a subset of them, or all of them. For example, availability signaling may indicate whether or not a TRS associated with a specific beam is being transmitted. A beam, as referred to herein, is equivalent to a transmit configuration indication (TCI) status for a connected UE, or a synchronization signal block index (SSB) for an unconnected UE. Specific embodiments include a flexible configuration mechanism where the network configures availability signaling within the DCI so that the UE can know whether TRS is available on specific beams, a specific group of beams, or all beams. In the example embodiments below, when the network is described as configuring an availability bit field, it means that the network uses upper-layer signaling, such as system information or dedicated signaling, to configure the availability bit field. In some implementations, the network configures the availability bit field in the DCI so that any DCI received in different beams indicates TRS availability in all beams. The UE receives the DCI in the first beam and, therefore, the underlying TRS availability information in the DCI, thus knowing the TRS availability in all other beams. The network can configure the availability bit field as in this example implementation, for instance, because the number of configured TRS beams is limited—for example, there are only two TRS beams—and therefore the availability per beam can be handled by two bits in the DCI. Alternatively, the network can disable TRS on all beams if it chooses to do so, or not at all, and therefore the availability indication applies to all beams. In this case, even a single bit is sufficient to indicate whether TRS is available or not, and additional bits can be used for other purposes, for example, to indicate the validity of TRS availability. In some implementations, the network configures the availability bit field in the DCI so that TRS availability signaling in each beam is only applicable to that beam; i.e., a selective beam approach 1810720 of 47 individual. The UE receives a DCI in a first beam where the TRS availability is only applicable in that beam; that is, if the indication is that the TRS is available, then the UE knows that the TRS associated with the first beam is available and can be used. If the UE wants to know if the TRS is available, for example, in a second beam, then the UE decodes the DCI in the second beam. The network may configure the UE by definition, for example, because TRS availability changes frequently by beam level. For instance, if no UE is connected within a specific beam (i.e., a TCI state for a connected UE or an SSB index for a free UE), the network disables TRS for that beam. Additionally, the network may decide to do so because the number of bits available in the DCI is limited to cover availability signaling per beam (for example, as in paging DCI) or because overhead must be reduced (for example, as in PEI). For instance, the network may configure the UE with 8 beams, and only 1 bit is available for availability signaling; therefore, the network configures the availability bit field in the single-beam selective approach. In some implementations, upper layers can configure multiple validity periods for TRS availability. If a UE detects a DCI in a first beam indicating that TRS is available, the UE can infer that TRS is available in the first beam for a first validity period, and that TRS is available for a second validity period in other beams belonging to the same group as the first beam. The first and second validity periods can be explicitly configured by upper layers and can have different values. For example, the first validity period can be longer than the second validity period. In some implementations, the network configures the availability bit field in the DCI so that TRS availability signaling in a beam group (i.e., at least one beam group is associated with two or more beams) is applicable to that beam group. By definition, this method is a compromise between the All approach of the first example implementation and the Individual approach of the second implementation. For example, the UE receives a TRS resource availability indication configuration from the upper layers that indicates a first group associated with a specific first group of TRS beams, where each beam is determined by quasi-location information (QCL) associated with an SSB index, and a second group associated with a specific second group of beams. The UE then receives a DCI 1810720 of 47 which includes the TRS availability bit field in at least one beam in the first group and therefore the UE knows the TRS availability status in all beams associated with the first group but not the beams associated with the second group. The network may decide to do this to balance selective beam availability (particularly if the network wants to activate / deactivate individual beams or beams associated with a group) with the UE's flexibility to choose which beam to decode the DCI. By definition, the UE does not need to decode all beams associated with a group of beams to know the TRS availability. The network may further decide to configure the availability indication in each group to apply to all beams or individual beams. For example, the network can configure one bit in each group to indicate whether TRS is available in all beams associated with the group, or, for example, two bits in any DCI received in any beam to indicate, for example, whether TRS is available in either the first or second beam of the group. In a more specific example, the network can configure the TRS availability indication for DCIs received only in some, and not all (for example, one), beams of the group. For example, the UE might be configured with a first group consisting of a first beam and a second beam, and the TRS availability indication is configured to be present only in the DCI received in the first beam, indicating TRS availability for the entire first group of beams. In a generic implementation, the network can configure availability signaling with a 'beam association-related configuration' that defines how the UE should interpret the availability signaling received in a DCI associated with a beam. For example, the network can configure availability signaling with the 'All' condition, which indicates that any DCI received in any beam indicates TRS availability in all beams; the 'Individual' condition, which indicates that a DCI received in a specific beam only indicates TRS availability in that specific beam; or a 'Group-based' condition, meaning that any DCI received within a group of beams associated with a specific group indicates TRS availability only in the beams associated with that group. A UE in free mode waits in a cell. The UE receives upper-layer signaling indicating a plurality of non-zero power CSI-RS resource sets (NZP-CSI-RS resource set) corresponding to the signal of 1810720 of 47 tracking reference (for example, the trs-Info parameter is explicitly set or is assumed to be implicitly set), where the NZP-CSI resource set is associated with (or includes) at least one TCI status identifier. The TCI status identifier indicates a QCL source for the resources in that resource set. The UE receives information via upper layers indicating a DCI format (e.g., paging DCI, i.e., including the Radio Network Temporary Identifier (RNTI)) and a field within the DCI that carries RS availability / unavailability information in an NZP-CSI-RS resource pool. The UE also receives information via upper layers, an explicit parameter indicating an association between a first TCI status identifier and at least one second TCI status identifier (or a first NZPCSI-RS resource pool and a second NZP-CSI-RS resource pool). If the UE detects a DCI corresponding to the DCI format (e.g., paging DCI, including RNTI) within a PDCCH associated with a first set of NZP-CSI-RS resources (e.g., the PDCCH's QCL source is the same as that of the first set of NZP-CSI-RS resources), the UE infers TRS availability / non-availability for the second set of NZP-CSI-RS resources based on the field in the detected DCI format. If the explicit parameter specifies a first value (for example, 'all'), the UE can infer TRS availability for the plurality of non-zero power CSIRS resource sets. If the explicit parameter specifies a second value (for example, 'individual'), the UE can infer TRS availability only for the first non-zero power CSI-RS resource set. The UE can also receive information from higher layers about the grouping of NZP-CSI-RS resource sets. For example, a first set of NZP-CSI-RS resource sets belongs to a first group, and a second set of NZP-CSI-RS resource sets belongs to a second group. If the explicit parameter indicates a third value (e.g., 'group'), the UE can infer TRS availability only for a group of NZP-CSI-RS resource sets, where the group is the group containing the first non-zero power CSI-RS resource set. Figure 1 illustrates an example method at a network node, according to particular embodiments. In particular embodiments, one or more steps of Figure 3 can be performed by the network node 160 described with 1810720 of 47 with respect to Figure 3. The method begins at stage 100, where the network node (e.g., network node 160) provides a TRS / CSI-RS configuration with its configurations related to the underlying beam associations through a higher layer, such as transmission on a SIMB. In stage 110, the network node provides TRS / CSI-RS availability with L1-based signaling, for example, a paging DCI or PEI, and in accordance with the configured beam associations. Figure 2 illustrates an example method in a wireless device, according to particular embodiments. In particular embodiments, one or more steps of Figure 3 can be performed by the wireless device 110 described with respect to Figure 3. The method begins at stage 200, where the wireless device receives a TRS / CSI-RS configuration along with its underlying beam association-related configurations from a higher layer, e.g., transmission via SIB. In stage 210, the wireless device receives TRS / CSIRS availability from L1-based signaling, for example, a paging DCI or PEI. In stage 220, the wireless device detects a DCI based on a first beam index, where the DCI indicates that TRS resources are available and determines that TRS resources are available for one or more beams based on the beam association-related configuration. Figure 3 illustrates an example wireless network, according to certain embodiments. The wireless network may comprise and / or interact with any type of communication, telecommunications, data, cellular, and / or radio network, or other similar system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Therefore, particular embodiments of the wireless network may implement communication standards, such as the Global System for Mobile Communications (GSM), the Universal System for Mobile Telecommunications (UMTS), Long Term Evolution (LTE), and / or other 2G, 3G, 4G, or 5G standards; or wireless local area network (WLAN) standards, such as the IEEE 802 standards.11; and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and / or ZigBee standards. 1810720 of 47 The 106 network may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices. The 160 network node and the WD 110 comprise several components, which are described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connections in a wireless network. In various embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other component or system that can facilitate or participate in the communication of data and / or signals, whether through wired or wireless connections. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or equipment on the wireless network to enable and / or provide wireless access to the wireless device and / or to perform other functions (e.g., management) on the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node B, evolved Node B (eNB), and gNB). Base stations can be classified according to the amount of coverage they provide (or, in other words, their transmit power level) and may also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node can 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 called remote radio heads (RRHs). Such remote radio units may or may not be integrated with an antenna, such as an integrated radio antenna. The parts of a distributed radio base station can also be called nodes in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio equipment (MSR) such as MSR BS, controllers of 1810720 of 47 network such as Radio Network Controllers (RNC) or Base Station Controllers (BSC), Base Transceiver Stations (BTS), Transmission Points, Transmission Nodes, Multi-Transmit / Multi-Cell Coordination Entities (MCE), Core Network Nodes (e.g., MSC, MME), O&M Nodes, OSS Nodes, SON Nodes, Positioning Nodes (e.g., E-SMLC) and / or MDT. As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, network nodes can represent any suitable device (or group of devices) capable, configured, arranged, and / or operable to enable and / or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network. In Figure 3, network node 160 includes processing circuitry 170, device read medium 180, interface 190, auxiliary equipment 184, power supply 186, power circuitry 187, and antenna 162. Although the network node 160 illustrated in the example wireless network in Figure 3 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It should be understood that a network node comprises any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 160 are depicted as individual boxes located within a larger box, or nested within several boxes, in practice, a network node may comprise multiple different physical components that form a single illustrated component (for example, the read-only medium of device 180 may comprise several independent hard drives, as well as several RAM modules). Similarly, network node 160 can be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In certain scenarios where network node 160 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 pair of NodeB and RNC 1810720 of 47 can, in some cases, be considered a single separate network node. In some embodiments, the network node 160 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (for example, a separate device-readable medium 180 for the different RATs), and some components may be reused (for example, the RATs may share the same antenna 162). The network node 160 may also include multiple sets of the various components illustrated for different wireless technologies integrated into the network node 160, such as GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies. These wireless technologies may be integrated on the same chip, on different chipsets, or on other components within the network node 160. The processing circuitry 170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as provided by a network node. These operations, carried out by the processing circuitry 170, may include processing the information acquired by the processing circuitry 170, for example, by converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information and, as a result of such processing, performing a determination. The processing circuitry 170 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 computing device, resource, or combination of hardware, software, and / or coded logic suitable and operable to provide, either alone or in conjunction with other network node components 160, such as the device-readable medium 180, the functionality of the network node 160. For example, the processing circuitry 170 can execute instructions stored on device-readable medium 180 or in memory within the processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 170 may include a system-on-a-chip (SoC). 1810720 of 47 In some embodiments, the processing circuitry 170 may include one or more of the radio frequency (RF) transceiver circuitry 172 and the baseband processing circuitry 174. In some embodiments, the radio frequency (RF) transceiver circuitry 172 and the baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units, such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuitry 172 and the baseband processing circuitry 174 may be on the same chip or chipset, board, or unit. In certain embodiments, some or all of the functionality described herein as provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 170 by executing instructions stored on device-readable medium 180 or in memory within the processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 170 without executing instructions stored on a separate or discrete device-readable medium, such as in a hardwired manner. In either embodiment, whether by executing instructions stored on device-readable storage medium or not, the processing circuitry 170 may be configured to perform the described functionality.The benefits provided by such functionality are not limited to the processing circuitry 170 alone or to other components of the network node 160, but are utilized by the network node 160 in its entirety, and / or by end users and the wireless network in general. Device-readable medium 180 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent solid-state storage memory, remotely mounted memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk drive), removable storage media (e.g., a flash disk drive, a compact disc (CD), or a digital video disc (DVD)), and / or any other non-transient, volatile or non-volatile, computer-executable and / or device-readable memory device that stores information, data, and / or instructions that can be used by processing circuitry 170. Device-readable medium 180 may store any suitable instruction, data, or information, including a 1810720 of 47 Computer program, software, an application that includes one or more logic, rules, code, tables, etc. and / or other instructions that the processing circuitry 170 can execute and that the network node 160 can use. The device-readable medium 180 can be used to store any calculations made by the processing circuitry 170 and / or any data received through the interface 190. In some embodiments, the processing circuitry 170 and the device-readable medium 180 can be considered integrated. Interface 190 is used for wired or wireless communication of signals and / or data between network node 160, network 106, and / or WD 110. As illustrated, interface 190 comprises ports / terminals 194 for sending and receiving data, for example, to and from network 106 via a wired connection. Interface 190 also includes radio front-end circuitry 192 that can be coupled to antenna 162 or, in certain embodiments, to a portion thereof. The radio front-end circuitry 192 comprises filters 198 and amplifiers 196. The radio front-end circuitry 192 can be connected to the antenna 162 and the processing circuitry 170. The radio front-end circuitry can be configured to condition the signals communicated between the antenna 162 and the processing circuitry 170. The radio front-end circuitry 192 can receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuitry 192 can convert the digital data into a radio signal with the appropriate bandwidth and channel parameters using a combination of filters 198 and / or amplifiers 196. The radio signal can then be transmitted via the antenna 162.Similarly, when receiving data, antenna 162 can collect radio signals, which are then converted into digital data by the radio front-end circuitry 192. The digital data can then be passed to the processing circuitry 170. In other embodiments, the interface may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node 160 may not include the separate radio front-end circuitry 192. Instead, the processing circuitry 170 may comprise the radio front-end circuitry and may be connected to the antenna 162 without the separate radio front-end circuitry 192. Similarly, in some embodiments, all or part of the RF transceiver circuitry 172 may be considered part of the interface. 1810720 of 47 190. In other embodiments, interface 190 may include one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown). Antenna 162 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, Antenna 162 may comprise one or more omnidirectional, sector, and panel antennas operable for transmitting / receiving radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna may be used to transmit / receive radio signals in any direction, a sector antenna may be used to transmit / receive radio signals from devices in a particular area, and a panel antenna may be a line-of-sight antenna used to transmit / receive radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO.In certain embodiments, antenna 162 may be separate from network node 160 and may be connected to network node 160 via an interface or port. Antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any receive operation and / or certain acquisition operations described herein as performed by a network node. Any information, data, and / or signal can be received from a wireless device, another network node, and / or any other network equipment. Similarly, antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any transmit operation described herein as performed by a network node. Any information, data, and / or signal can be transmitted to a wireless device, another network node, and / or any other network equipment. Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply power to the network node components 160 to perform the functionality described herein. Power circuitry 187 may receive power from power supply 186. Power supply 186 and / or power circuitry 187 may be configured to provide power to the various components of the node. 1810720 of 47 of network 160 in a manner suitable for the respective components (for example, at a voltage and current level required for each respective component). The power supply 186 may be included in, or external to, the power circuitry 187 and / or network node 160. For example, network node 160 can be connected to an external power source (e.g., a wall outlet) via an input interface or circuitry, such as an electrical cable, through which the external power source supplies power to the power circuitry 187. As a further example, the power source 186 can comprise a power supply in the form of a battery or battery pack that is connected to or integrated within the power circuitry 187. The battery can provide backup power in the event of a failure of the external power source. Other types of power sources, such as photovoltaic devices, can also be used. Alternative embodiments of network node 160 may include additional components beyond those shown in Figure 3 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionalities described herein and / or any functionality necessary to support the object described herein. For example, network node 160 may include user interface equipment to allow information input to network node 160 and to allow information output from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160. As used herein, wireless device (WD) refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information through the air. In some implementations, a WD can be configured to transmit and / or receive information without direct human interaction. For example, a WD might be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to 1810720 of 47 network requests. Examples of a wireless device include, but are not limited to, a smartphone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, video game device or console, music storage device, player, handheld terminal device, wireless endpoint, mobile station, tablet, laptop, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart device, wireless customer premises equipment (CPE), wireless vehicle mounted terminal device, etc.A WD can support device-to-device (D2D) communication, for example, by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), and in this case, it can be called a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, a WD (Digital Device) can represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another WD and / or a network node. In this case, the WD can be a machine-to-machine (M2M) device, which, in a 3GPP context, can be called an MTC (Machine-to-Center) device. For example, the WD could be a UE (Unit Enabled) implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Examples of such machines or devices include sensors, measuring devices such as power meters, industrial machinery, household appliances or personal devices (e.g., refrigerators, televisions, etc.), and personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, a WD may represent a vehicle or other equipment capable of monitoring and / or reporting its operational status and other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be called a wireless terminal. Additionally, a WD as described above may be mobile, in which case it may also be called a mobile device or mobile terminal. As illustrated, the wireless device 110 includes the antenna 111, the interface 114, the processing circuitry 120, the device-readable medium 130, the user interface equipment 132, the auxiliary equipment 134, the power supply 136, and the 1810720 of 47 Power Supply Circuitry 137. The WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by the WD 110, such as GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few. These wireless technologies may be integrated on the same chips or chipset or on different components within the WD 110. Antenna 111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and connected to WD 110 via an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 may be configured to perform any receive or transmit operation described herein as performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the radio front-end circuitry and / or antenna 111 may be considered an interface. As illustrated, interface 114 comprises radio front-end circuitry 112 and antenna 111. Radio front-end circuitry 112 comprises one or more filters 118 and amplifiers 116. Radio front-end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition the signals communicated between antenna 111 and processing circuitry 120. Radio front-end circuitry 112 may be coupled to antenna 111 or be a part of it. In some embodiments, WD 110 may not include separate radio front-end circuitry 112. Instead, the processing circuitry 120 may comprise the radio front-end circuitry and may be connected to the antenna 111. Similarly, in some embodiments, part or all of the RF transceiver circuitry 122 may be considered part of the interface 114. The radio front-end circuitry 112 can receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuitry 112 can convert the digital data into a radio signal with the appropriate bandwidth and channel parameters using a combination of filters 118 and / or amplifiers 116. The radio signal can then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 can collect radio signals, which are then... 1810720 of 47 converted into digital data by the radio front-end circuitry 112. The digital data can be passed to the processing circuitry 120. In other embodiments, the interface may comprise different components and / or different combinations of components. The processing circuitry 120 may comprise a combination of one or more microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or any computing device, resource, or combination of hardware, software, and / or coded logic suitable and operable to provide, either alone or in conjunction with other components of WD 110, such as the device-readable medium 130, the functionality of the WD 110. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuitry 120 may execute instructions stored on the device-readable medium 130 or in memory within the processing circuitry 120 to provide the functionality disclosed herein. As illustrated, the processing circuitry 120 includes one or more of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and / or different combinations of components. In certain embodiments, the processing circuitry 120 of the WD 110 may comprise a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be on separate chips or chipsets. In alternative embodiments, some or all of the baseband processing circuitry 124 and the application processing circuitry 126 may be combined on one chip or chipset, and the RF transceiver circuitry 122 may be on a separate chip or chipset. Also in alternative embodiments, some or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 may be on the same chip or chipset, and the application processing circuitry 126 may be on a separate chip or chipset. Still in other alternative embodiments, some or all of the RF transceiver circuitry 122, the circuitry of The baseband processing circuitry 124 and the application processing circuitry 126 can be combined on the same chip or chipset. In some embodiments, the RF transceiver circuitry 122 can be part of the interface 114. The RF transceiver circuitry 122 can condition the RF signals for the processing circuitry 120. In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by the processing circuitry 120 by executing instructions stored on the device-readable medium 130, which, in certain embodiments, may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 120 without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these implementations, whether executing instructions stored on a device-readable storage medium or not, the 120 processing circuitry can be configured to perform the described functionality. The benefits provided by this functionality are not limited to the 120 processing circuitry alone or to other components of the WD 110, but are also utilized by the WD 110, and / or by end users and the wireless network in general. The processing circuitry 120 may be configured to perform any determination, calculation, or similar operation (for example, certain extraction operations) described herein as being performed by a WD. These operations, as performed by the processing circuitry 120, may include processing the information extracted by the processing circuitry 120, for example, by converting the extracted information into other information, comparing the extracted or converted information with information stored by the WD 110, and / or performing one or more operations based on the extracted or converted information and, as a result of such processing, performing a determination. Device-readable medium 130 can be used to store a computer program, software, or application that includes one or more logic, rules, code, tables, etc., and / or other instructions that the processing circuitry 120 can execute. Device-readable medium 130 may include computer memory (e.g., random-access memory (RAM), read-only memory). 1810720 of 47 (ROM)), mass storage media (for example, a hard disk drive), removable storage media (for example, a compact disc (CD) or a digital video disc (DVD)), and / or any other computer executable and / or device-readable volatile or non-volatile and non-transient memory device that stores information, data and / or instructions that can be used by the processing circuitry 120. In some embodiments, the processing circuitry 120 and the device-readable medium 130 may be integrated. User interface equipment (UIE) 132 can provide components that allow a human user to interact with the WD 110. Such interaction can take many forms, such as visual, auditory, tactile, etc. UIE 132 can be operated to produce output for the user and to allow the user to provide input to the WD 110. The type of interaction can vary depending on the type of UIE 132 installed in the WD 110. For example, if the WD 110 is a smartphone, interaction can be performed via a touchscreen; if the WD 110 is a smart meter, interaction can be performed via a display that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 132 may include input interfaces, devices, and circuitry, and output interfaces, devices, and circuitry. User interface equipment 132 is configured to allow input of information into the WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys / buttons, a touchscreen, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from the WD 110 and to allow processing circuitry 120 to output information from the WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibration circuitry, a USB port, a headphone interface, or other output circuitry.By using one or more interfaces, devices, and input / output circuitry of the user interface equipment 132, the WD 110 can communicate with end users and / or the wireless network and allow them to benefit from the functionality described herein. Auxiliary equipment 134 is operable to provide more functionality 1810720 of 47 specific, which cannot generally be carried out by the WD. This may include specialized sensors for performing measurements for various purposes and interfaces for additional types of communication, such as wired communications, etc. The inclusion and type of auxiliary equipment components 134 may vary depending on the embodiment and / or the case. In certain embodiments, the power supply 136 may be in the form of a battery or battery pack. Other types of power supplies, such as an external power source (e.g., a wall outlet), photovoltaic devices, or energy cells, may also be used. The WD 110 may further comprise power circuitry 137 for supplying power from the power supply 136 to the various parts of the WD 110 that require power from the power supply 136 to perform any functionality described or indicated herein. In certain embodiments, the power circuitry 137 may comprise power management circuitry. Power circuitry 137 can be operated additionally or alternatively to receive power from an external power source; in which case the WD 110 can be connected to the external power source (such as a wall outlet) via an input circuit or interface, such as an electrical cable. In certain embodiments, power circuitry 137 can also be operated to supply power from an external power source to power supply 136. This may be, for example, to charge power supply 136. Power circuitry 137 can perform any formatting, conversion, or other modification to the power from power supply 136 to make the power suitable for the respective components of the WD 110 to which it is supplied. Although the object described herein can be implemented in any suitable type of system using any suitable component, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 3. For simplicity, the wireless network in Figure 3 shows only network 106, network nodes 160 and 160b, and WD 110, 110b, and 110c. In practice, a wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the components illustrated, network node 160 and the 1810720 of 47 wireless devices (WD) 110 are represented with additional details. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access by the wireless devices and / or the use of the services provided by, or through, the wireless network. Figure 4 illustrates an example of a user equipment, according to certain embodiments. As used herein, a user equipment or UE does 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 intended for sale to and operation by a human user, which may or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device not intended for sale to or operation by a human user, which may be associated with or operated for the benefit of a user (e.g., a smart energy meter). UE 200 may be any UE identified by the Third Generation Partnership Project (3GPP), which includes an NB-IoT UE, a machine-type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.The UE 200, as illustrated in Figure 4, is an example of a WD configured to communicate according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP GSM, UMTS, LTE, and / or 5G standards. As mentioned earlier, the terms WD and UE can be used interchangeably. Consequently, while Figure 4 is a UE, the components analyzed herein can be applied equally to a WD and vice versa. In Figure 4, the UE 200 includes the processing circuitry 201 operatively coupled to the input / output interface 205, the radio frequency (RF) interface 209, the network connection interface 211, memory 215, random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, the communication subsystem 231, the power supply 213, and / or any other component or any combination thereof. The storage medium 221 includes the operating system 223, the application program 225, and the data 227. In other embodiments, the storage medium 221 may include other similar types of information. Certain UEs may use all the components shown in Figure 4 or only a subset of them. The level of integration among the components may vary from one UE to another. Furthermore, certain UEs may contain multiple instances of a 1810720 of 47 components, such as multiple processors, memories, transceivers, transmitters, receivers, etc. In Figure 4, processing circuitry 201 can be configured to process data and computer instructions. Processing circuitry 201 can be configured to implement any sequential state machine for executing machine instructions stored in machine-readable computer programs in memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more general-purpose stored-program processors, such as a microprocessor or a digital signal processor (DSP), together with appropriate software; or any combination thereof. For example, processing circuitry 201 could include two central processing units (CPUs). Data can be information in a form suitable for use by a computer. In the embodiment shown, the I / O interface 205 can be configured to provide a communication interface to an input device, an output device, or an I / O device. The UE 200 can be configured to use an output device via the I / O interface 205. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from a UE 200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 200 can be configured to use an input device via the I / O interface 205 to allow a user to capture information on the UE 200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital video camera, webcam, etc.), a microphone, a sensor, a mouse, a scroll wheel, a directional pad, a touchpad, a smart card, and similar devices. The presence-sensitive display can include a capacitive or resistive touch sensor to detect user input. For example, a sensor can be an accelerometer, gyroscope, tilt sensor, force sensor, magnetometer, optical sensor, proximity sensor, or other similar sensor. 1810720 of 47 any combination of these. For example, the input device could be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor. In Figure 4, RF interface 209 can be configured to provide a communication interface to RF components, such as a transmitter, receiver, and antenna. Network connection interface 211 can be configured to provide a communication interface to network 243a. Network 243a can encompass wired and / or wireless networks, such as a local area network (LAN), wide area network (WAN), computer network, wireless network, telecommunications network, other similar networks, and any combination thereof. For example, network 243a could comprise a Wi-Fi network. Network connection interface 211 can be configured to include a receiver and a transmit interface used to communicate with one or more different devices on a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, or similar protocols.The 211 network connection interface can implement receive and transmit functionality suitable for communication network links (e.g., optical, electrical, and similar). The receive and transmit functions can share circuit components, software, or firmware, or alternatively, they can be implemented separately. RAM 217 can be configured to interface via bus 202 with processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs, such as the operating system, application programs, and device drivers. ROM 219 can be configured to provide data or computer instructions to processing circuitry 201. For example, ROM 219 can be configured to store data or low-level system code that is invariant for basic system functions, such as basic input / output (I / O), startup, or receiving keystrokes from a keyboard, which are stored in non-volatile memory. Storage medium 221 can be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash disk drives. For example, storage medium 221 can be configured to include the operating system 223 and the application program 225, such as a browser application. 1810720 of 47 web, a widget or gadget engine or other application, and the data file 227. The storage medium 221 can store, for use by UE 200, any of a variety of different operating systems or combinations of operating systems. The 221 storage medium can be configured to include a number of physical disk drives, such as a redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, miniature storage drive, pen drive, small pen drive, high-density digital versatile disk (HD-DVD) optical disk drive, internal hard disk drive, Blu-ray optical disk drive, holographic digital data storage (HDDS) optical disk drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random-access memory (SDRAM), external microDIMM SDRAM, smart card memory such as a subscriber identity module or removable user identity module (SIM / RUIM), other memory, or any combination thereof.Storage medium 221 may allow the UE 200 to access computer-executable instructions, application programs, or the like, stored on transient or non-transient memory media to load or unload data. A manufactured item, such as one that uses a communication system, may be tangibly incorporated into storage medium 221, which may comprise a device-readable medium. In Figure 4, the processing circuitry 201 can be configured to communicate with network 243b using the communication subsystem 231. Network 243a and network 243b can be the same network or networks, or different networks. The communication subsystem 231 can be configured to include one or more transceivers used to communicate with network 243b. For example, the communication subsystem 231 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMAX, or similar protocols.Each transceiver may include transmitter 233 and / or receiver 235 to implement the transmit and receive functionality, respectively, appropriate for the RAN links (e.g., frequency allocations and the like). Furthermore, transmitter 233 and receiver 235 of each transceiver may share circuit components, software, or firmware, or alternatively, they may be separate. 1810720 of 47 to be implemented separately. In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, other similar communication functions, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, other similar networks, and any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network.The 213 power supply can be configured to provide alternating current (AC) or direct current (DC) power to the UE 200 components. The features, benefits, and / or functions described herein may be implemented in one of the UE 200 components or partitioned across multiple UE 200 components. Furthermore, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. For example, the communication subsystem 231 may be configured to include any of the components described herein. Additionally, the processing circuitry 201 may be configured to communicate with any of these components via bus 202. In another example, any of these components may be represented by computer instructions stored in memory which, when executed by the processing circuitry 201, perform the corresponding functions described herein.In another example, the functionality of any such component can be partitioned between the processing circuitry 201 and the communication subsystem 231. In another example, the non-computationally intensive functions of any such component can be implemented in software or firmware, and the computationally intensive functions can be implemented in hardware. Figure 5 is a flowchart illustrating an example method for a wireless device, according to certain embodiments. In particular embodiments, one or more steps of Figure 5 may be carried out. 1810720 of 47 by the wireless device 110 described with respect to Figure 3. The method begins at step 512, where the wireless device (e.g., wireless device 110) obtains a TRS / CSI-RS resource configuration and an underlying beam association for a plurality of TRS / CSI-RS instances. For example, a wireless device might receive a TRS / CSI-RS resource configuration through system information. In step 514, the wireless device obtains an availability indicator. The availability indicator indicates an association of one or more of the plurality of TRS / CSI-RS instances and underlying beam association. For example, the availability indicator can associate an indicator with a single beam, all beams, or a group of beams. In particular embodiments, the availability indicator associates a TRS / CSI-RS occasion with an individual beam, and the determination that one or more of the plurality of TRS / CSI-RS occasions have TRS / CSI-RS available comprises determining that TRS / CSI-RS is available on one of the TRS / CSI-RS occasions associated with the beam in which the layer one signaling is received. In particular embodiments, the availability indicator associates a TRS / CSI-RS occasion with all beams, and the determination that one or more of the plurality of TRS / CSI-RS occasions have TRS / CSI-RS available comprises determining that TRS / CSI-RS is available on all TRS / CSI-RS occasions associated with the underlying beams of the entire plurality of TRS / CSI-RS occasions. In particular embodiments, the availability indicator associates a TRS / CSI-RS occasion with a group of beams, and the determination that one or more of the plurality of TRS / CSI-RS occasions have TRS / CSI-RS available comprises determining that TRS / CSI-RS is available on all TRS / CSI-RS occasions associated with the underlying beams in the group of beams. In particular embodiments, the availability indicator is associated with one or more validity durations as described above. For embodiments where the availability indicator indicates a beam group, the method may include step 516, where the wireless device obtains an indication by associating a subset of the underlying beams from the plurality of TRS / CSI-RS instances into a beam group. In stage 518, the wireless device receives layer one signaling in a beam. The layer one signaling indicates that a TRS / CSI-RS instance is available at least once out of the plurality of TRS / CSI-RS instances (by 1810720 of 47 example, bitmap availability). For example, receiving layer one signaling that indicates that a TRS / CSI-RS is available on at least one occasion TRS / CSI-RS of the plurality of occasions TRS / CSI-RS comprises receiving at least one of a paging DCI and a PEI. In stage 520, the wireless device determines one or more of the plurality of TRS / CSI-RS instances that TRS / CSI-RS is available based on the availability indicator and Layer 1 signaling. For example, the wireless device can determine TRS / CSI-RS availability according to any of the embodiments and examples described herein. In step 522, the wireless device receives TRS / CSI-RS on at least one of the specified TRS / CSI-RS occasions. Modifications, additions, or omissions can be made to the 500 method in Figure 5. In addition, one or more steps of the method in Figure 5 can be carried out in parallel or in any suitable order. Figure 6 is a flowchart illustrating an example method at a network node, according to certain embodiments. In particular embodiments, one or more steps of Figure 6 may be carried out by the network node 160 described with respect to Figure 3. The method begins at step 612, where the network node (e.g., network node 160) transmits a TRS / CSI-RS resource configuration and an underlying beam association for a plurality of TRS / CSI-RS instances to a wireless device. For example, the network node might transmit a TRS / CSI-RS resource configuration via system information. In step 614, the network node transmits an availability indicator to the wireless device. The availability indicator indicates the association of one or more of the plurality of TRS / CSI-RS instances and the underlying beam association. In particular embodiments, the availability indicator associates a TRS / CSI-RS occasion with an individual beam, associates a TRS / CSI-RS occasion with all beams, or associates a TRS / CSI-RS occasion with a group of beams. In particular embodiments, the availability indicator is associated with one or more validity durations as described above. For embodiments where the availability indicator indicates a group of beams, the method may include step 616, where the network node transmits an indication by associating a subset of the underlying beams from the plurality of TRS / CSI-RS instances into a group of beams. 1810720 of 47 In step 618, the network node transmits Layer 1 signaling in a beam toward the wireless device. Layer 1 signaling indicates that a TRS / CSI-RS instance is available at least once out of the plurality of TRS / CSI-RS instances (e.g., bitmap availability). In particular embodiments, the transmission of layer one signaling indicating that a TRS / CSI-RS is available on at least one TRS / CSI-RS occasion out of the plurality of TRS / CSI-RS occasions comprises transmitting at least one of a paging DCI and a PEI. Modifications, additions, or omissions can be made to the 600 method in Figure 6. In addition, one or more steps of the method in Figure 6 can be carried out in parallel or in any suitable order. Figure 7 illustrates a schematic block diagram of two devices in a wireless network (e.g., the wireless network illustrated in Figure 3). The devices include a wireless device and a network node (e.g., wireless device 110 and network node 160 illustrated in Figure 3). Devices 1600 and 1700 are operable to carry out the example methods described with reference to Figures 5 and 6, respectively, and possibly any other process or method disclosed herein. It should also be understood that the methods in Figures 5 and 6 are not necessarily carried out solely by devices 1600 and / or 1700. At least some operations of the methods may be carried out by one or more entities. Virtual appliances 1600 and 1700 may comprise processing circuitry, which may include one or more microprocessors 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 more types of memory, such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, as well as instructions for carrying out one or more of the techniques described herein, in various embodiments. In some implementations, the processing circuitry can be used to make the 1602 acquisition module, the 1604 determination module, the 1810720 of 47 transmission module 1606 and any other suitable unit of apparatus 1600 perform the corresponding functions in accordance with one or more embodiments of this disclosure. Similarly, the processing circuitry described above may be used to enable the receiving module 1702, the determining module 1704, the transmitting module 1706, and any other suitable unit of apparatus 1700 to perform the corresponding functions in accordance with one or more embodiments of this disclosure. As illustrated in Figure 7, the 1600 apparatus includes the acquisition module 1602 configured to obtain the TRS / CSI-RS resource configuration and underlying beam association according to any of the embodiments and examples described herein. The determination module 1604 is configured to determine TRS / CSI-RS availability according to any of the embodiments and examples described herein. As illustrated in Figure 7, the 1700 apparatus includes the 1706 transmission module configured to transmit the TRS / CSI-RS resource configuration and underlying beam association in accordance with any of the embodiments and examples described herein. Figure 8 is a schematic block diagram illustrating a virtualization environment in which the functions implemented by certain embodiments can be virtualized. In this context, virtualization means creating virtual versions of appliances or devices, which may include the virtualization of hardware platforms, storage devices, and network resources.As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device, or any other type of communication device) or components thereof and refers to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes on one or more networks). In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines deployed in one or more virtual environments hosted by one or more of the hardware nodes. Furthermore, in the embodiments 1810720 of 47 implementation in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be fully virtualized. The functions may be implemented by means of one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) that operate to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 320 run in the virtualization environment 300, which provides hardware 330 comprising processing circuitry 360 and memory 390. The memory 390 contains instructions 395 executable by the processing circuitry 360 by means of which the application 320 is operational to provide one or more of the features, benefits, and / or functions disclosed herein. The virtualization environment 300 comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be off-the-shelf (COTS) processors, dedicated application-specific integrated circuits (ASICs), or any other type of processing circuitry that includes digital or analog hardware components or special-purpose processors. Each hardware device may comprise memory 390-1, which may be non-persistent memory for temporarily storing instructions 395 or software executed by the processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include a physical network interface 380.Each hardware device may also include non-transient, persistent, machine-readable storage media 390-2 that have stored therein the software 395 and / or instructions executable by the processing circuitry 360. The software 395 may include any type of software, including software for creating instances of one or more virtualization layers 350 (also called hypervisors), software for running virtual machines 340, in addition to software that enables the execution of functions, features, and / or benefits described in connection with some embodiments described herein. Virtual machines 340 comprise virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run using 1810720 of 47 a corresponding virtualization layer 350 or hypervisor. The different ways of realizing the virtual appliance instance 320 can be implemented on one or more of the virtual machines 340, and the implementations can be done in different ways. During operation, the processing circuitry 360 runs the software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be called the virtual machine monitor (VMM). The virtualization layer 350 may present a virtual operating platform that appears as network hardware to the virtual machine 340. As shown in Figure 8, hardware 330 can be a standalone network node with generic or specific components. Hardware 330 can include antenna 3225 and can implement some functions through virtualization. Alternatively, hardware 330 can be part of a larger hardware group (for example, in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed through management and orchestration (MANO) 3100, which, among other functions, oversees the application lifecycle management 320. Hardware virtualization is sometimes called network function virtualization (NFV). NFV can be used to consolidate many types of network equipment onto industry-standard, high-volume server hardware, physical switches, and physical storage, which can be located in data centers and on-premises at the customer's site. In the context of NFV, a 340 virtual machine can be a software implementation of a physical machine that runs programs as if they were running on a non-virtualized physical machine. Each 340 virtual machine, and the portion of the 330 hardware that runs that virtual machine—whether dedicated hardware and / or hardware shared with other 340 virtual machines—forms a separate virtual network element (VNE). Even within the context of an NFV, the virtual network function (VNF) is responsible for handling specific network functions that run on one or more virtual machines 340 on top of the hardware network infrastructure 330 and corresponds to application 320 in Figure 18. In some embodiments, one or more 3200 radio units, each including one or more 3220 transmitters and one or more 3210 receivers, may be coupled to one or more 3225 antennas. The 3200 radio units may 1810720 of 47 communicate directly with the hardware nodes 330 through one or more suitable network interfaces and can 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 signals can be carried out using the 3230 control system which can be used alternatively for communication between the 330 hardware nodes and the 3200 radio units. With reference to Figure 9, according to one embodiment, a communication system includes a telecommunications network 410, such as a 3GPP-type cellular network, comprising an access network 411, such as a radio access network, and a core network 414. The access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NB, eNB, gNB, or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c can be connected to the core network 414 by a wired or wireless connection 415. A first UE 491 located in the coverage area 413c is configured to wirelessly connect to, or be sought by, the corresponding base station 412c. A second UE 492 in the 413a coverage area can be wirelessly connected to the corresponding 412a base station.When a plurality of UE 491, 492 is illustrated in this example, the disclosed embodiments are equally applicable to a case in which a single UE is in the coverage area or in which a single UE connects to the corresponding base station 412. The telecommunications network 410 is connected to a host computer 430, which may be incorporated into the hardware and / or software of a standalone server, a cloud-deployed server, a distributed server, or as processing resources in a server tower. The host computer 430 may be owned or controlled by a service provider, or the service provider may operate it on its own behalf or on its behalf. The connections 421 and 422 between the telecommunications network 410 and the host computer 430 may extend directly from the core network 414 to the host computer 430 or may pass through an optional intermediate network 420. The intermediate network 420 may be one of, or a combination of more than one, public, private, or hosted network; the intermediate network 420, if any, may be a backbone network or the Internet; in particular, the intermediate network 420 may comprise two or more subnets (not shown). The communication system in Figure 9 as a whole enables connectivity 1810720 of 47 between the connected UEs 491, 492 and the host computer 430. The connectivity can be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491, 492 are configured to communicate data and / or signal through the OTT connection 450, by using the access network 411, the core network 414, any intermediate networks 420, and possible additional infrastructure (not shown) as an intermediary. The OTT connection 450 can be transparent in the sense that the participating communication devices through which the OTT connection 450 passes do not have uplink and downlink communications routed. For example, base station 412 may or may not need to be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., transferred) to a connected UE 491.Similarly, base station 412 does not need to know about the future routing of an outgoing uplink communication originating from UE 491 to host computer 430. Figure 10 illustrates an example of a host computer communicating with a user computer via a base station through a partially wireless connection, according to certain embodiments. Example implementations of the UE, base station, and host computer discussed in the preceding paragraphs, according to one embodiment, will be described below with reference to Figure 10. In communication system 500, the host computer 510 comprises hardware 515, including a communication interface 516 configured to establish and maintain a wired or wireless connection with a communication device interface other than that of communication system 500. The host computer 510 further comprises processing circuitry 518, which may have storage and / or processing capabilities.In particular, the processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 510 further comprises software 511, which is stored on or accessible by the host computer 510 and is executable by the processing circuitry 518. Software 511 includes host application 512. Host application 512 can be operated to provide a service to a remote user, such as a UE 530 connected via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 can provide transmitted user data. 1810720 of 47 using the OTT connection 550. The communication system 500 further includes a base station 520 provided within a telecommunications system, comprising hardware 525 that enables it to communicate with the host computer 510 and the UE 530. Hardware 525 may include communication interface 526 for establishing and maintaining a wired or wireless connection with a communication device interface other than that of the communication system 500, as well as radio interface 527 for establishing and maintaining at least one wireless connection 570 with the UE 530 located within a coverage area (not shown in Figure 10) served by base station 520. Communication interface 526 may be configured to facilitate connection 560 to the host computer 510. Connection 560 may be direct or may pass through a core network (not shown in Figure 10) of the telecommunications system and / or through one or more intermediate networks outside the telecommunications system.In the embodiment shown, the base station hardware 525 further includes the processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 520 further has software 521 stored internally or accessible via an external connection. The communication system 500 also includes the previously mentioned UE 530. Its hardware 535 may include the radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving a coverage area in which the UE 530 is currently located. The UE 530 hardware 535 further includes the processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 530 further comprises the software 531, which is stored in or accessible from the UE 530 and is executable by the processing circuitry 538. The software 531 includes the client application 532. The client application 532 can be operated to provide service to a human or non-human user through the UE 530, with support from the host computer 510.On host computer 510, a host application running 512 can communicate with the client application running 532 through the OTT connection 550 that terminates on UE 530 and host computer 510. 1810720 of 47 To provide the service to the user, client application 532 can receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 can transfer both the request data and the user data. Client application 532 can interact with the user to generate the user data it provides. It can be observed that the host computer 510, base station 520, and UE 530 illustrated in Figure 10 may be similar or identical to the host computer 430, one of the base stations 412a, 412b, or 412c, and one of the UEs 491 or 492 in Figure 8, respectively. That is, the internal workings of these entities may be as shown in Figure 10, and, regardless, the surrounding network topology may be that of Figure 8. In Figure 10, the OTT connection 550 is drawn abstractly to illustrate communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages through these devices. The network infrastructure can determine the routing, which can be configured to be hidden from UE 530, the service provider operating host computer 510, or both. While the OTT connection 550 is active, the network infrastructure can also make decisions that dynamically change the routing (for example, based on load balancing considerations or network reconfiguration). The 570 wireless connection between the UE 530 and the 520 base station is in accordance with the implementation methods described throughout this disclosure. One or more of these implementation methods enhance the performance of OTT services provided to the UE 530 by utilizing the 550 OTT connection, where the 570 wireless connection forms the final segment. More specifically, these implementation methods can improve signaling overhead and reduce latency, potentially providing faster internet access for users. A measurement procedure can be provided to monitor data rate, latency, and other factors improved by one or more implementations. An optional network function can also be provided to reconfigure the OTT 550 connection between the host computer 510 and the UE 530 in response to variations in measurement results. The measurement procedure and / or the network function to reconfigure the OTT 550 connection can be implemented in 1810720 of 47 the software 511 and hardware 515 of the host computer 510 or the software 531 and hardware 535 of the UE 530, or both. In embodiments, sensors (not shown) may be deployed on or in association with communication devices through which the OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified above, or by supplying values ​​of other physical quantities from which the software 511, 531 may compute or estimate the monitored quantities. Reconfiguration of the OTT connection 550 may include message format, relay configuration, preferred routing, etc.; the reconfiguration may not affect the base station 520 and may be unknown or imperceptible to the base station 520. Such procedures and functionalities may be known and implemented in the art.In certain implementations, the measurements may involve UE's proprietary signaling, which facilitates measurements of performance, propagation times, latency, and the like from the host computer 510. The measurements can be implemented so that the software 511, 531 causes messages, particularly empty or dummy messages, to be transmitted using the OTT connection 550 while monitoring propagation times, errors, etc. Figure 11 is a flowchart illustrating a method implemented in a communication system, according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to Figures 9 and 10. For the sake of simplicity in this disclosure, only references to Figure 11 in drawings in this section will be included. In step 610, the host computer provides user data. In a sub-step 611 (which may be optional) of step 610, the host computer provides the user data by running a host application. In step 620, the host computer initiates a transmission by sending the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data that was carried in the transmission initiated by the host computer, in accordance with the embodiments described throughout this disclosure. In step 640 (which may be optional), the UE runs a client application associated with the host application running on the host computer. Figure 12 is a flowchart illustrating a method implemented in 1810720 of 47 a communication system, according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to Figures 9 and 10. For the sake of simplicity in this disclosure, only references to Figure 12 will be included in drawings in this section. In step 710 of the method, the host computer provides user data. In an optional substep (not shown), the host computer provides the user data by running a host application. In step 720, the computer initiates a transmission by sending the user data to the UE. The transmission may pass through the base station, in accordance with the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission. Figure 13 is a flowchart illustrating a method implemented in a communication system, according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to Figures 9 and 10. For the sake of simplicity in this disclosure, only references to Figure 13 in drawings in this section will be included. In step 810 (which may be optional), the UE receives input data from the host computer. Alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by running a client application. In substep 811 (which may be optional) of step 810, the UE runs a client application that provides the user data in response to input data received from the host computer. When providing the user data, the running client application may also consider user input received from the user. Regardless of the specific method used to provide the user data, the UE initiates, in substep 830 (which may be optional), the transmission of the user data to the host computer.In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. Figure 14 is a flowchart illustrating a method implemented in a communication system, according to one embodiment. The system of 1810720 of 47 communication includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For the purposes of simplicity of this disclosure, only references to Figure 14 will be included in drawings in this section. In step 910 (which may be optional), in accordance with the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data transmitted by the base station. The term unit may have a conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, solid-state and / or discrete logic devices, computer programs or instructions to carry out the respective tasks, procedures, calculations, outputs and / or display functions, etc., such as those described herein. Modifications, additions, or omissions may be made to the systems and apparatus disclosed herein without departing from the scope of the invention. The components of the systems and apparatus may be integrated or separate. Furthermore, the operations of the systems and apparatus may be carried out through additional, additional, or other components. Additionally, the operations of the systems and apparatus may be carried out by means of any suitable logic comprising software, hardware, and / or other logic. As used herein, "each" refers to each member of a set or each member of a subset of a set. Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Furthermore, the steps may be carried out in any suitable order. The preceding description contains numerous specific details. It is understood, however, that the implementation methods can be put into practice without these specific details. In other cases, known circuits, structures, and techniques have not been shown in detail so as not to obscure the understanding of this description. Those of intermediate skill, with the included descriptions, will be able to implement the appropriate functionality without unnecessary experimentation. 1810720 of 47 References in the descriptive report to a form of embodiment, an example form of embodiment, etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but each embodiment may not necessarily include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in relation to one embodiment, it is stated that it is within the knowledge of a person of the mid-level trade to implement that feature, structure, or characteristic in relation to other embodiments, whether or not they are explicitly described. Although this disclosure has been described in terms of certain embodiments, alterations and permutations of those embodiments will be obvious to persons of average skill. Accordingly, the foregoing description of embodiments does not limit this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined in the claims below.

Claims

1. A method carried out by a wireless device, characterized in that it comprises: obtaining (512) a tracking reference signal (TRS) / channel status information reference signal (CSI-RS) resource configuration and an underlying beam association for a plurality of TRS / CSI-RS instances; obtaining (514) an availability indicator, wherein the availability indicator indicates an association of one or more of the plurality of TRS / CSI-RS instances and underlying beam association; receiving (518) a layer one signaling in a beam, wherein the layer one signaling indicates that a TRS / CSI-RS is available in at least one TRS / CSI-RS instance of the plurality of TRS / CSI-RS instances; determining (520) whether one or more of the plurality of TRS / CSI-RS instances have TRS / CSI-RS available based on the availability indicator and the layer one signaling;and receiving (522) TRS / CSI-RS on at least one of the determined TRS / CSI-RS occasions, wherein the availability indicator associates a TRS / CSI-RS occasion with an individual beam, and determining that one or more of the plurality of TRS / CSI-RS occasions have TRS / CSI-RS available comprises determining that TRS / CSI-RS is available on one of the TRS / CSI-RS occasions associated with the beam on which the layer one signaling is received. 14 Claims follow;