Link adaptation without fine synchronization

By adjusting MIMO rank and MCS per codeword based on UE capabilities and channel conditions, the solution improves downlink throughput in communication systems where fine synchronization is not maintained, addressing throughput reduction issues.

WO2026238804A1PCT designated stage Publication Date: 2026-11-19TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/063914
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-16
Filing Date
2026-05-13
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing communication systems face challenges in maintaining high throughput when User Equipment (UE) lacks fine synchronization, leading to reduced throughput due to conservative rank and modulation and coding scheme constraints.

Method used

The proposed solution allows the network to adjust MIMO transmission rank and MCS per codeword based on UE capabilities and channel conditions, enabling link adaptation without relying on prior reference signals for synchronization.

Benefits of technology

This approach enhances downlink throughput by tailoring link parameters to UE capabilities and channel conditions, maximizing performance even when fine synchronization is not maintained.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026063914_19112026_PF_FP_ABST
    Figure EP2026063914_19112026_PF_FP_ABST
Patent Text Reader

Abstract

Various embodiments disclosed herein provide for a method performed by a User Equipment (UE) for data reception from a network node without having received prior reference signals to perform tracking or fine synchronization for data reception. The method can include transmitting, to the network node, a first indication that the UE supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization. The method can also include receiving, from the network node, signaling indicating data reception based on the link parameters, and performing data reception according to the signaling.
Need to check novelty before this filing date? Find Prior Art

Description

LINK ADAPTATION WITHOUT FINE SYNCHRONIZATION RELATED APPLICATIONS

[0001] This application claims the benefit of International Patent Application No. PCT / IB2025 / 000232, filed May 16, 2025, the disclosure of which is hereby incorporated herein by reference in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates to methods performed by a User Equipment (UE) for data reception without fine synchronization and a network node for performing link adaptation without fine synchronization and a UE and a network node to perform the methods.BACKGROUND

[0003] Reference signals (RSs) are a crucial component of communication systems. For instance, Fifth Generation (5G) New Radio (NR) defines a variety of RSs for different purposes such as phase tracking reference signals (PT-RSs) to track the phase of the local oscillator at the receiver and transmitter and mitigate phase errors, sounding reference signals (SRSs) for uplink channel estimation purposes and — typically — subsequent downlink precoding calculation, or demodulation reference signals (DMRSs) transmitted with the physical downlink and uplink shared channels (PDSCH / PUSCH) for channel estimation and coherent demodulation.

[0004] A core component of NR is the support of Multiple Input Multiple Output (MIMO) related techniques. NR supports up to 8-layer spatial multiplexing for up to 32 transmit antenna ports at the gNB with channel dependent precoding. Figure 1 shows an example of data transmission with spatial multiplexing where the information carrying symbol vector s = [s1(s2> ...,sr]Tis first multiplied (or precoded) by a precoding matrix W E CNrXrbefore being sent over AT antenna ports. Each symbol in s is associated with a data layer and r is the number of data layers or rank, which is a property of the wireless channel between the transmitter and the receiver. W serves to beamform each data layer towards the UE such that signal to interference plus noise ratio (SINR) is maximized and cross layer interference is minimized at the UE receiver. Spatial multiplexing is achieved since multiple symbols can be transmitted simultaneously in a same time and frequency resource element (RE).

[0005] In order to estimate the channel at the receiver and perform coherent demodulation, a broad framework for DMRS provision is established in NR, where DMRS symbols are multiplexed with PDSCH and PUSCH REs containing useful data in the time / frequency (T / F) grid. Examples of some DMRS framework aspects are depicted in Figure 2.

[0006] Figure 2 illustrates that:

[0007] Single-symbol and double-symbol based DMRS may be used.• Frequency mapping may be Type 1 (Comb based with 2 Code Division Multiplexing (CDM) groups) or Type 2 (Non-comb based with 3 CDM groups).• OFDM Symbol mapping may be Type A (for slot-based scheduling) where DMRS starts in symbol 2 or 3 from slot boundary (counting starts at 0) or Type B (non-slot based scheduling) where DMRS starts in PxSCH symbol 0 (counting starts at 0).

[0008] The 5G NR physical layer is based on a lean design principle, whereas little signalling as possible is transmitted when there is no ongoing data transmission. To enable 5G NR UEs to perform channel related measurements when they are not receiving data the 5G NR standard has introduced tracking reference signals (TRS) transmissions.

[0009] A TRS is normally configured to be a 1 port non-zero-power channel state information reference signal (NZP-CSI-RS) used by UEs for channel tracking purposes. One TRS transmission consists of two CSI-RS symbols separated by 3 non-CSI-RS symbols, e.g. symbols 2 and 6. In FR1 the same pattern is repeated across two consecutive slots, whereas in FR2 it can be in either one or two consecutive slots.

[0010] The TRS may be used by UEs in connected mode for several purposes, such as:• Fine time and frequency sync to the radio channel;• Estimation of channel variability (e.g. Doppler, Coherence bandwidth) for PDSCH processing; and• Time domain channel property (TDCP) feedback (Rel-18) for PUSCH processing.

[0011] TRS resources can be periodic (mandatory) or aperiodic (optional).

[0012] Reception of PDSCH without fine synchronization using a TRS but instead synchronization using the PDSCH DMRS has been previously disclosed where an explicit indication from the network (NW) to the User Equipment (UE) when to use the TRS for synchronization and when to not do that (enable / disable), i.e., a TRS-free state. The TRS-free operation (a.k.a. self-contained PDSCH operation) may enable, e.g.,• a leaner and more energy efficient NW by reducing the number of RS transmissions, • a more energy efficient UE operation by removing the need of performing downlink fine synchronization procedures prior to the PDSCH reception, and• reduce packet latency by allowing the transmission of information without a preceding TRS transmission,• increased flexibility on the network side to select a TRP for PDSCH transmission without the need to indicate to the UE which TRS to use for QCL.

[0013] Such TRS-free operation is suggested for Sixth Generation (6G), where the benefits of such solution to base fine sync on DMRS is much larger than in 5G, as there are no legacy UEs to support.SUMMARY

[0014] Various embodiments disclosed herein provide for a method performed by a User Equipment (UE) for data reception from a network node without receiving prior reference signals to perform tracking or fine synchronization for data reception. The method can include transmitting, to a network node, a first indication that the UE supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization. The method can also include receiving, from the network node, signaling indicating data reception based on the link parameters, and performing data reception according to the signaling.

[0015] In an embodiment, to perform tracking or fine synchronization for data reception the UE is configured with a downlink reference signal (RS) wherein the downlink RS is a Quasi CoLocation (QCL) source RS for Physical Downlink Shared Channel (PDSCH) Demodulation RS (DMRS) for at least one physical layer property, wherein the at least one physical layer property comprises one or more of a Doppler shift, a Doppler spread, average delay, or delay spread.

[0016] In an embodiment, the first indication transmitted to the network node comprises a first set of maximum number of spatial layers and / or Modulation and Coding Scheme (MCS) values beyond which the UE cannot be assumed to correctly decode data in subsequent data reception without receiving prior reference signals to perform tracking or fine synchronization for data receptions.

[0017] In an embodiment, the first indication transmitted to the network node comprises a first set of maximum number of spatial layers and / or MCS values with which the UE correctly decodes data with a target block error rate in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for data receptions.

[0018] In an embodiment, the UE informs the network node that the UE does not correctly decode data in subsequent data receptions.

[0019] In an embodiment, the first indication transmitted to the network node comprises a first set of maximum rank and / or Channel Quality Indicator (CQI) values beyond which the UE cannot be assumed to correctly decode data in subsequent data reception without receiving prior reference signals to perform tracking or fine synchronization for data receptions.

[0020] In an embodiment, the method further includes transmitting a second indication to the network node, wherein the second indication comprises information related to a second set of maximum rank and / or CQI values beyond which the UE cannot be assumed to correctly decode data in subsequent data reception without receiving prior reference signals to perform tracking or fine synchronization for such data receptions.

[0021] In an embodiment, the second set of maximum rank and / or CQI values supersedes a first set of maximum rank and / or CQI values.

[0022] In an embodiment, the first indication or the second indication comprises one or more link parameter offset values relative to a third set of link parameters that comprises a UE preference for data reception after receiving prior reference signals to perform tracking or fine synchronization for the data reception.

[0023] In an embodiment, the link parameter offset values comprise one or more of: a fixed offset for all MCS; separate offset values per modulation type; separate offset values per MCS or MCS subset; separate offset values per different Signal to Interference plus Noise Ratio (SINR) values or SINR ranges, optionally combined with above MCS-dependent differentiation; or separate offset values per different elapsed time values or elapsed time ranges, where the elapsed time refers to time since a previous sync-related signal reception.

[0024] In an embodiment, the first indication or second indication communicate that a network is free to autonomously decide one or more link parameters without constraint.

[0025] In an embodiment, the first indication is provided as UE capability information.

[0026] In an embodiment, the method further includes, prior to transmitting the first indication, receiving from the network node a request for UE capability information.

[0027] In an embodiment, the second indication is provided as part of a Channel State Information (CSI) report.

[0028] In an embodiment, the method further includes receiving a CSI-ReportConfig from the network node requesting the UE to transmit the second indication, wherein the CSI-ReportConfig is received prior to receiving the second indication.

[0029] In an embodiment, the first indication and second indications are signaled by providing one or more of: a UE type or capability index; an explicit parameter value; an indicator to a parameter set defined in a specification document; or an indicator to a parameter set defined in a previous configuration transmission.

[0030] In an embodiment, the second indication augments the first indication, wherein the first indication provides a static parameter and the second indication provides a dynamic parameter.

[0031] In an embodiment, the second indication overrides a part of the first indication.

[0032] In an embodiment, the first indication and / or the second indication specify a period of time in which information in the first indication and / or the second indication is valid.

[0033] In an embodiment, the period of time is counted from a time instant the first indication or the second indication is transmitted, and the period of time is applicable to all subsequent data receptions from the network node without receiving prior reference signals to perform tracking or fine synchronization.

[0034] In an embodiment, the period of time is applicable for one or more subsequent time instants and counted from a time instant the UE receives a reference signal to perform tracking or fine synchronization

[0035] In an embodiment, the period of time is applicable for one or more subsequent time instants and counted from a time instant the network determines the UE to have received a reference signal to perform tracking or fine synchronization

[0036] In an embodiment, the period of time coincides with a time required by the UE to perform tracking or fine synchronization.

[0037] In an embodiment, the UE performs data decoding if a subset of configured link parameters match the first indication or the second indication.

[0038] In an embodiment, the UE performs data decoding irrespective of configured link parameters.

[0039] In an embodiment, the UE determines values of one or more link parameters as specified by the standard specification, wherein: a value of a link parameter for data reception without fine synchronization is directly provided by the standard; or a value of a link parameter for data reception without fine synchronization is computed following a standard-specified method.

[0040] In an embodiment, a UE is provided that is configured to perform data reception from a network node without receiving prior reference signals to perform tracking or fine synchronization for data reception. The UE includes processing circuitry that is configured to transmit, to the network node, a first indication that the UE supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization. The processing circuitry is also configured to receive, from the network node, signaling indicating data reception based on the link parameters and perform data reception according to the signaling. The processing circuitry can also perform all the other embodiments described above.

[0041] In an embodiment, a method performed by a network node for facilitating data reception by a UE without having received prior reference signals to perform tracking or fine synchronization for data reception is provided, where the method includes receiving, from the UE, a first indication that the UE supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization, receiving, from the UE a second indication comprising information related to a second set of maximum rank and / or CQI values beyond which the UE cannot be assumed to correctly decode data in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for such data receptions, and performing a selection of link parameters based on the first indication and the second indication, and providing to the UE , a configuration indicating data reception based on the selected link parameters.

[0042] In an embodiment, the configuration indicates a time period for which the link parameters are applicable.

[0043] In an embodiment, the configuration is provided via one or more of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) Control Elements (MAC CE), or downlink control information (DCI).

[0044] In an embodiment, a network node is provided that facilitates data reception by a UE without having received prior reference signals to perform tracking or fine synchronization for data reception. The network node include processing circuitry configured to receive, from the UE, a first indication that the UE supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization. The processing circuitry is also configured to receive from the UE a second indication comprising information related to a second set of maximum rank and / or CQI values beyond which the UE cannot be assumed to correctly decode data in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for such data receptions, perform a selection of link parameters based on the first indication and the second indication, and provide to the UE, a configuration indicating data reception based on the selected link parameters.

[0045] In an embodiment, a system comprising a user equipment described above and a network node described above is provided.BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0047] Figure 1 shows an example of data transmission with spatial multiplexing in accordance with some embodiments of the present disclosure;

[0048] Figure 2 shows an example of Fifth Generation (5G) NR Demodulation Reference Signals (DMRS) resource mapping in accordance with some embodiments of the present disclosure;

[0049] Figure 3 shows an example of self-contained Physical Downlink Shared Channel (PDSCH) operation in accordance with some embodiments of the present disclosure;

[0050] Figure 4 shows a message sequence chart of a method for data reception from a network node without receiving prior reference signals to perform tracking or fine synchronization for data reception in accordance with some embodiments of the present disclosure;

[0051] Figure 5 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0052] Figure 6 is another example of a communication system according to some embodiments of the present disclosure;

[0053] Figure 7 shows a wireless device, which may be configured to operate in the communication system of Figure 5 or in the communication system of Figure 6;

[0054] Figure 8 shows a network node in accordance with some embodiments of the present disclosure; and

[0055] Figure 9 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.DETAILED DESCRIPTION

[0056] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0057] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0058] There currently exist certain challenge(s). As illustrated in Figure 3, in Tracking Reference Signal (TRS) free operation (i.e., where periodic TRS is not present, or the User Equipment (UE) has not been configured a periodic TRS or the UE has been configured with oneor more periodic TRS but is not allowed to use such TRS for synchronization purposes), the network (NW) may have to limit the rank and modulation and coding scheme (MCS) prior to the UE acquiring fine synchronization by other means. Prior art considers a worst-case fixed rank & MCS constraint (typically rank = 1 and Quadrature Phase-Shift Keying (QPSK) modulation order), which substantially reduces the overall throughput for those slots where the UE does not have fine synchronization.

[0059] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The proposed solution allows increasing the throughput in the slots where the NW cannot assume UE downlink fine sync via an adequate and potentially more aggressive link adaptation. While downlink communication performance can be degraded when UEs do not perform an accurate downlink fine synchronization, such degradation is MCS-dependent and may not be major (how severe may be depending on the reported UE capabilities from the UE to the NW). In practice, this degradation depends on a variety of factors such as:• the residual synchronization error after coarse synchronization (i.e., based on the primary synchronization signal - PSS),• the UE signal processing capabilities to compensate for hardware- and channel -related impairments, or• the wireless channel conditions.

[0060] The proposed approach describes methods and associated signaling, enabling the NW to adjust link parameters such as Multiple Input, Multiple Output (MIMO) transmission rank and / or MCS per codeword for transmissions where the UE cannot be assumed to have performed downlink fine sync.

[0061] The information provided by the UE to the network (e.g., max scheduled MIMO rank and MCS per codeword) allow the network to perform a link adaptation decision based on the UE capability and dynamic / instantaneous information and then signal the link parameters to the UE. (e.g., scheduled MIMO rank and MCS per codeword) tailored to the UE capability / preference, which maximizes link throughput when communicating downlink data without fine synchronization.

[0062] Certain embodiments may provide one or more of the following technical advantage(s). The disclosed techniques herein enable the network to adapt its behavior depending on the UE capabilities and channel-related conditions. As a result, the presented solution allows an increased downlink throughput when receiving data in situations where the network cannot assume the UE to have performed fine synchronization.

[0063] As used herein, The term “network” may refer to one of a generic network node, a gNB (or the corresponding node in a Sixth Generation (6G) network), a base station, a unit within the base station to handle at least some Machine Learning (ML) operation, a relay node, a core network node, a core network node that handle at least some ML operations, or a device supporting Device to Device (D2D) communication. Likewise, the phrase “for reception without fine synchronization” refers to data communication where the NW cannot assume that the UE has acquired, or has been able to maintain, valid downlink fine synchronization. Additionally or alternatively, the phrase may also refer to the fact that the UE does not actually have acquired, or has been able to maintain, valid downlink fine synchronization.

[0064] According to some embodiments, the UE may have received reference signals and has performed tracking or fine synchronization but may have not been able to maintain tracking or fine synchronization. According to some other embodiments, the UE may have never received reference signals to perform tracking or fine synchronization. In both cases, the UE and / or the network node may perform the method described in the following for a new data reception.

[0065] Figure 4 shows a message sequence chart of a method for data reception from a network node without receiving prior reference signals to perform tracking or fine synchronization for data reception in accordance with some embodiments of the present disclosure.

[0066] The method can begin at step 406, where the network node 404 can send a request to UE 402 for UE capability information that may relate to the ability to receive data without receiving prior reference signals to perform tracking or fine synchronization. The request can be in the form of a UECapabilityEnquiry message.

[0067] In an embodiment, to perform tracking or fine synchronization for data reception implies that the UE (402) is configured with a downlink reference signal (RS) and received the downlink RS, wherein the downlink RS is a Quasi Co-Location (QCL) source RS for Physical Downlink Shared Channel (PDSCH) Demodulation RS (DMRS) for at least one physical layer property, wherein the at least one physical layer property comprises one or more of a Doppler shift, a Doppler spread, average delay, or delay spread.

[0068] At step 408, the UE 402 transmits a first indication to the network node 404 that the UE (402) supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization.

[0069] In an embodiment, the first indication transmitted to the network node 404 comprises a first set of maximum number of spatial layers and / or MCS values beyond which the UE 402 cannot be assumed to correctly decode data in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for such data receptions.

[0070] In an embodiment, the first indication transmitted to the network node 404 comprises a first set of maximum number of spatial layers and / or MCS values with which the UE 402 can correctly decode data with a target block error rate in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for such data receptions.

[0071] In an embodiment, the first indication transmitted to the network node (404) comprises a first set of maximum rank and / or Channel Quality Indicator (CQI) values beyond which the UE (402) cannot be assumed to correctly decode data in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for such data receptions.

[0072] At 410, the network node 404 can send a request to the UE 402 comprising a Channel State Information (CSI) CSI-ReportConfig that requests the UE 402 to send a second indication.

[0073] At 412, the UE 402 can send to the network node 404 a second indication that comprises information related to a second set of maximum rank and / or CQI values beyond which the UE 402 cannot be assumed to correctly decode data in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for such data receptions.

[0074] At step 414, the network node performs a link adaptation decision based on the capability information and the dynamic / instantaneous information provided in the first and second indications, and selects link parameters. At step 416, the network node 404 provides the selected link parameters to the UE as a configuration indicating data reception without fine synchronization based on the selected link parameters.

[0075] At step 418, the network node 404 sends to the UE 402 the downlink data transmission according to the link configuration.

[0076] In an embodiment, the configuration indicates the time resources for which the link parameters are applicable. In some embodiments, the time resources will be applicable from:• the instant the configuration is received and until indicated otherwise,• for one or more subsequent time instants and counted from the instant the UE receives a reference signal enabling fine synchronization (e.g., from the first / last slot / OFDM symbol with such a reference signal),• for one or more subsequent time instants and counted from the instant the network can assume the UE to be finely synchronized (e.g., from the first / last slot / OFDM symbol where the UE receives PDSCH).

[0077] In an embodiment, the configuration is received as part of one or more of radio resource control (RRC) signaling, medium access control elements (MAC CEs), downlink control information (DCI).

[0078] In an embodiment, the second set of maximum rank and / or CQI values supersedes a first set of maximum rank and / or CQI values from the first indication.

[0079] In an embodiment, the first or second indication comprises one or more link parameter offset values relative to a third set of link parameters that comprises a UE preference for data reception after receiving prior reference signals to perform tracking or fine synchronization for the data receptions.

[0080] In 5G NR, the third set of link parameters may be, e.g., one or more of the existing reporting parameters of the reportQuantity field within the CSI-ReportConfig (e.g., CQI, Rank Indicator (RI)).

[0081] Intuitively, the offset values capture the UE-specific performance degradation that the network should assume the UE to suffer due to the lack of fine synchronization.

[0082] In an embodiment, wherein the parameter offset values comprise one or more of • A fixed offset for all MCS• Separate offset values per modulation type• Separate offset values per MCS or MCS subset• Separate offset values per different SINR values or SINR ranges, optionally combined with above MCS-dependent differentiation• Separate offset values per different elapsed time values or elapsed time ranges, where the elapsed time refers to time since a previous sync-related signal reception [latest SDMRS, SSB, ...], optionally combined with above MCS-dependent differentiation.

[0083] In an embodiment, the first indication or second indication communicate that the network is free to autonomously decide one or more link parameters without constraint.

[0084] In an embodiment, the first indication is provided as UE 402 capability information.

[0085] In an embodiment, the second indication is provided as part of a CSI report.

[0086] In an embodiment, the first and / or second indications are signaled by providing a UE type or capability index, explicit parameter values, an indicator to parameter sets defined in a specification document, or an indicator to parameter sets defined in a previous configuration transmission, (e.g. an Radio Resource Control (RRC) transmission).

[0087] In an embodiment, the second indication augments the first indication [the first provides static parameters, the second provides dynamically varying ones], e.g.:• the UE may dynamically and continually provide valid offsets for the current SINR value, and / or• the UE may dynamically transmit the second indication according to the activation / deactivation of a sync-related capability (which may also be explicitly indicated), e.g., if a more advanced algorithm is not available due to a resource limitation or reduced power mode, and / or• the UE may dynamically transmit the second indication according to UE power consumption mode and which LO quality / stability is currently activated.

[0088] In an embodiment, the second indication overrides parts of the first indication (updates dynamically varying parameters).

[0089] In an embodiment, the first and / or the second indications specify the period of time during which the indications are valid. The period of time may be signaled for example in a field timeValidityForSyncReport in the second indication.

[0090] In an embodiment, the period of time is counted from the time instant the indication is transmitted and applies to all subsequent data receptions from the network node without receiving prior reference signals to perform tracking or fine synchronization.

[0091] In an embodiment, the period of time is applicable for one or more subsequent time instants and counted from the instant the UE receives a reference signal to perform tracking or fine synchronization, e.g., from the first / last slot / OFDM symbol with a downlink reference signal expected by the network to be used for fine synchronization purposes.

[0092] In an embodiment, the period of time is applicable for one or more subsequent time instants and counted from the instant the network can assume the UE to have received a reference signal to perform tracking or fine synchronization, e.g., from the first / last slot / Orthogonal Frequency Division Multiplexing (OFDM) symbol where the UE receives PDSCH.

[0093] In an embodiment, the period of time coincides (i.e., also indicates) the time required by the UE to perform tracking or fine synchronization.

[0094] In other words, the UE indicates that the link parameters are only applicable for the UE-required time duration of the reference signals enabling fine synchronization.

[0095] In some embodiments, this period of time will correspond the number of slots with TRSs / DMRSs used for synchronization purposes plus an optional offset accounting for the signal processing delay required to start compensating for the synchronization-related impairments.

[0096] In an embodiment, the network node 404 uses one or more of the UE-indicated link parameters, e.g., as mandated by the standard specification.

[0097] In an embodiment, the network node 404 decides that one or more of the link parameters for the subsequent data receptions where the UE cannot assume the UE to be finely synchronized are reduced / backed off by a value not smaller than the indicated offset value, compared to those decided for the subsequent data receptions where the UE can be assumed to be finely synchronized.

[0098] In some embodiments, the offset value of a link parameter for data reception without fine synchronization will be computed following a standard- specified method (e.g., as an offset of the UE-indicated value for the same link parameter for data reception with fine synchronization MCSsync).

[0099] For instance, the standard may specify the MCS-dependent offset value AMCS- that the network should use to compute the MCS for the subsequent data reception without fine synchronization, i.e., MCSno sync= MCSsync— &MCS■

[0100] In some embodiments, the MCS-dependent offset value AMCS- is further a function of one or more of: MCSsync, modulation order, SNR, SINR, reported CQI, time since last fine sync opportunity, UE implementation / capability category, etc.

[0101] In an embodiment, the UE 402 only performs data decoding if a (sub)set of configured link parameters match the UE indications.

[0102] In an embodiment, the NACK from the UE includes a corresponding flag for failure data decoding reason to inform the NW. In an embodiment, the UE receives an indication in the scheduling DCI that the gNB has [or has not] applied a backoff according to the UE preference [so the UE does not need to guess from the scheduling info],

[0103] In an embodiment, UE always perform data decoding irrespective of the configured link parameters.

[0104] In an embodiment, the UE determines the value of one or more link parameters as specified by the standard specification.

[0105] In some embodiments, the value of a link parameter for data reception without fine synchronization will be directly provided by the standard,

[0106] In other embodiments, the value of a link parameter for data reception without fine synchronization will be computed following a standard-specified method (e.g., as an offset of the network-indicated value for the same link parameter for data reception with fine synchronization MCSsync).

[0107] For instance, the standard may specify the MCS-dependent offset value that the UE should use to compute the MCS for data reception without fine synchronization AMCS-, i.e., MCSnosync MCSsync^MCS •

[0108] In some embodiments, the MCS-dependent offset valueMcs is further a function of one or more of: MCSsync, modulation order, SNR, SINR, reported CQI, time since last fine sync opportunity, UE implementation / capability category, etc.

[0109] Figure 5 shows an example of a communication system 500 in accordance with some embodiments.

[0110] In the example, the communication system 500 includes a telecommunications network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes or base stations of various types, access network nodes 510A and 510B are depicted (which may be collectively referred to as network nodes 510), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 504 may include more than one access network technology. The network nodes 510 of access network 504 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections. The UEs 512 can perform the functionality of UE 402 as described herein. The network nodes 510 can perform the functionality of network node 404 as described herein.[OHl] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 502, including one or more access network nodes 510 and / or core network nodes 508.

[0112] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support aspecification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0113] The network nodes 510 facilitate direct or indirect connection of one or more UEs 512 to the core network 506 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0114] The UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 510 and other communication devices. Similarly, the network nodes 508, 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 502) with the UEs 512 and / or with other network nodes or equipment in the telecommunications network 502 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 502. More specifically, UEs 512 may send messages, data, and / or other signals to network nodes 508, 510 or other elements of the telecommunications network 502 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 508, 510 may send messages, data, and other signals to UEs 5122, other network nodes 508, 510, and other devices in telecommunications network 502 directly or indirectly. As one specific example, a core network node 508 may transmit a particularmessage to a UE 512 by transmitting the message to an access network node 510 that will then transmit the message to the intended UE 512. Similarly, a core network node 508 may receive a particular message from a UE 512 by receiving the message from an access network node 510 that itself received the message from the UE 512.

[0115] In the depicted example, the core network 506 connects elements of the access network 504 (e.g., one or more of the network nodes 510) to one or more host computing systems, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 506 includes one or more core network nodes (e.g., core network node 508) of various types, one or more of which may be generally referred to as network nodes 508. Network nodes 508 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0116] The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunications network 502. The host 516 may be operated by the service provider or on behalf of the service provider. The host 516 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0117] As a whole, the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 500 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless localarea network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 500 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 500 supporting different standards, protocols, or rule sets.

[0118] As one example, in certain embodiments, access network 504 may contain some access network nodes 510 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 510 support (or the same access network nodes 510 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 502 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 504 and / or a core network 506 that supports multiple different standard generations or may include multiple access networks 504 and / or multiple core networks 506 with individual networks 504, 506 supporting different standard generations.

[0119] Telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0120] In some examples, one or more of the UEs 512 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0121] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and / or 512D) and network nodes (e.g., network node 510B). In some examples, the hub 514 may be a controller, router, contentsource and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514.

[0122] As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0123] The hub 514 may have a constant / persistent or intermittent connection to the network node 510B. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g., UE 512C and / or 512D), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to an M2M service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 510B. In other embodiments, the hub 514 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 510B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0124] Figure 6 is another example of a communication system 600 according to some embodiments. As used herein, the communication system 600 includes multiple access points (APs) 610 (with four exemplary APs 610A, 610B, 610C, and 610D being depicted) and multiple wireless devices, referred to in the context of communication system 600 as stations (STAs) 612 (referred to individually as STA 612A, STA 612B, STA 612C, STA 612D, and STA 612E). STA 612Ais served by AP 610A in a first basic service set (BSS) 620A. STA 610B and STA 610C are served by AP 610B in a second BSS, BSS 620B. STA 612D is served by AP 610C in a third BSS, BSS 620C. STA 612E is served by AP 610D in a fourth BSS, BSS 620D. Stations 612 may benon-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 612 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0125] Each of STAs 612 may connect through a radio link to one of APs 610. For example, depending on location or channel conditions experienced by a given STA 612, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0126] Each AP 610 may provide data connectivity to STAs 612 connected to a particular AP 610. As illustrated, APs 610 may be connected to a data network 630. In this way, APs 610 may also provide data connectivity between STAs 612 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 612 and its serving AP 610 may be used for providing various kinds of services to STA 612, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 612 and / or on a device linked to STA 612. By way of example, Figure 6 illustrates an application service platform 632 provided in data network 630. The application(s) executed on STA 612 and / or on one or more other devices linked to STA 612 may use the radio link for data communication with one or more other STA 612 and / or the application service platform 632, thereby enabling utilization of the corresponding service(s) at STA 612.

[0127] Figure 7 shows a wireless device 700, which may be configured to operate in communication system 500 of Figure 5 or in communication system 600 of Figure 6. The wireless device 700 may be alternatively referred to as a UE 700, like a UE 512 within the context of communication system 500, or like UE 402 within the context of Figure 4 or as a station (STA) 700 or as a non-access-point station (non-AP STA) 700, like a STA 612 within the context of the communication system 600, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP)phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0128] A wireless device 700 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 700 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 700 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 700 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0129] In particular embodiments, wireless device 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain embodiments of wireless device 700 may include all or a subset of the components shown in Figure 7. The level of integration between the components may vary from one embodiment of wireless device 700 to another. In general, in a particular embodiment of wireless device 700, processing circuitry 702, input / output interface 706, power source 708, memory 710, and communication interface 712 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 700. Further, certain embodiments of wireless devices 700 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0130] The processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 710. The processing circuitry 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.);programmable logic together with appropriate firmware; one or more stored computer programs, general -purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 702 may include multiple central processing units (CPUs).

[0131] In the example, the input / output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0132] In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of wireless device 700 via input circuitry or an interface such as an electrical power cable. Power source 708 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 700 to which power is supplied.

[0133] The memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 710 includes one or more programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716. The memory 710 may store, for use by wireless device 700, any of a variety of various operating systems or combinations of operating systems.

[0134] The memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 710 may allow wireless device 700 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.

[0135] The processing circuitry 702 may be configured to communicate with an access network or other network via or using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0136] In the illustrated embodiment, communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax,Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0137] In particular embodiments, wireless device 700 may provide an output of data captured via a sensor, through its communication interface 712, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 700 can be communicated through a wireless connection to a network node via another wireless device 700. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0138] As another example, wireless device 700 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 700 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0139] Wireless device 700, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item -tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 700 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 700 shown in Figure 7.

[0140] As yet another specific example, in an loT scenario, wireless device 700 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 700 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 700 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 700 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0141] In practice, any number of wireless devices 700 may be used together with respect to a single use case. For example, a first wireless device 700 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 700 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 700 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 700 can also include more than one of the functionalities described above. For example, wireless device 700 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0142] Figure 8 shows a network node 800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 800 may be configured to operate in communication system 500 of Figure 5, like network nodes 508 or 510, or as network node 404 as in Figure 4 or in communication system 600 of Figure 6, like an AP 610 or a station 612. 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 Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0143] Network nodes 800 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 800 may be a relay node or a relay donor node controlling a relay. Network nodes 800 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remoteradio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0144] Other examples of network nodes 800 include multiple transmission point (multi -TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0145] In particular embodiments, network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. In general, in a particular embodiment of network node 800, processing circuitry 802, memory 804, communication interface 806, and power source 808 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 800.

[0146] The network node 800 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 800 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 804 or portions of memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 800.

[0147] The processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitablecomputing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 804, to provide network node 800 functionality.

[0148] In some embodiments, the processing circuitry 802 includes a system on a chip (SOC).In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.

[0149] The memory 804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 802. The memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804 is integrated.

[0150] The communication interface 806 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 700 may be capable of wireless communication and communication interface 806 may also include radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, an antenna 810. Particular embodiments of radio front-end circuitry 818 include filter(s) 820 and amplifier(s) 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio front-end circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes orUEs via a wireless connection. The radio front-end circuitry 818 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal(s) may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0151] In certain alternative embodiments, network node 800 may be capable of wireless communication but does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

[0152] The antenna 810 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through one or more interfaces or ports.

[0153] The antenna 810, communication interface 806, and / or the processing circuitry 802 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 800. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuitry 802 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 800. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0154] The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an inputcircuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808. As a further example, the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0155] Embodiments of the network node 800 may include additional components beyond those shown in Figure 8 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.

[0156] Figure 9 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0157] Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 800 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0158] Hardware 904 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (alsoreferred to as hypervisors or virtual machine monitors (VMMs)), provide VM 908A and VM 908B (which may be collectively referred to as VMs 908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 908.

[0159] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0160] In the context of NFV, each of the VMs 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 908, and that part of hardware 904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 908 on top of the hardware 904 and corresponds to an application 902.

[0161] Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.

[0162] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments maycomprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0163] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0164] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A method performed by a User Equipment, UE, (402) for data reception from a network node (404) without receiving prior reference signals to perform tracking or fine synchronization for data reception, the method comprising:transmitting (408), to the network node (404), a first indication that the UE (402) supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization;receiving (416), from the network node (404), signaling indicating data reception based on the link parameters; andperforming (418) data reception according to the signaling.

2. The method of claim 1, wherein to perform tracking or fine synchronization for data reception the UE (402) is configured with a downlink reference signal, RS, wherein the downlink RS is a Quasi Co-Location, QCL, source RS for Physical Downlink Shared Channel, PDSCH, Demodulation RS, DMRS, for at least one physical layer property, wherein the at least one physical layer property comprises one or more of a Doppler shift, a Doppler spread, average delay, or delay spread.

3. The method of any of claims 1 to 2, wherein the first indication transmitted to the network node (404) comprises a first set of maximum number of spatial layers and / or Modulation and Coding Scheme, MCS, values beyond which the UE (402) cannot be assumed to correctly decode data in subsequent data reception without receiving prior reference signals to perform tracking or fine synchronization for data receptions.

4. The method of any of claims 1 to 2, wherein the first indication transmitted to the network node (404) comprises a first set of maximum number of spatial layers and / or Modulation and Coding Scheme, MCS, values with which the UE (402) correctly decodes data with a target block error rate in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for data receptions.

5. The method of any of claim 4, wherein the UE (402) informs the network node (404) thatthe UE (402) does not correctly decode data in subsequent data receptions.

6. The method of any of claims 1 to 2, wherein the first indication transmitted to the network node (404) comprises a first set of maximum rank and / or Channel Quality Indicator, CQI, values beyond which the UE (402) cannot be assumed to correctly decode data in subsequent data reception without receiving prior reference signals to perform tracking or fine synchronization for data receptions.

7. The method of any of claims 1 to 6, further comprising:transmitting (412) a second indication to the network node (404), wherein the second indication comprises information related to a second set of maximum rank and / or Channel Quality Indicator, CQI, values beyond which the UE (402) cannot be assumed to correctly decode data in subsequent data reception without receiving prior reference signals to perform tracking or fine synchronization for such data receptions.

8. The method of claim 7, wherein the second set of maximum rank and / or CQI values supersedes a first set of maximum rank and / or CQI values.

9. The method of claim 7, wherein the first indication or the second indication comprises one or more link parameter offset values relative to a third set of link parameters that comprises a UE preference for data reception after receiving prior reference signals to perform tracking or fine synchronization for the data reception.

10. The method of claim 8, wherein the link parameter offset values comprise one or more of:a fixed offset for all MCS;separate offset values per modulation type;separate offset values per MCS or MCS subset;separate offset values per different Signal to Interference plus Noise Ratio, SINR, values or SINR ranges, optionally combined with above MCS-dependent differentiation; or separate offset values per different elapsed time values or elapsed time ranges, where the elapsed time refers to time since a previous sync-related signal reception.

11. The method of any of claims 7 to 10, wherein the first indication or second indication communicate that a network is free to autonomously decide one or more link parameters withoutconstraint.

12. The method of any of claims 1 to 11, wherein the first indication is provided as UE capability information.

13. The method of any claims 1 to 12, further comprising, prior to the transmitting the first indication:receiving (406), from the network node (404), a request for UE capability information.

14. The method of claim 7, wherein the second indication is provided as part of a Channel State Information, CSI, report.

15. The method of claim 7, further comprising:receiving, (410) a CSI-ReportConfig from the network node (404) requesting the UE (402) to transmit the second indication, wherein the CSI-ReportConfig is received prior to receiving the second indication.

16. The method of claim 7, wherein the first indication and second indications are signaled by providing one or more of:a UE type or capability index;an explicit parameter value;an indicator to a parameter set defined in a specification document; oran indicator to a parameter set defined in a previous configuration transmission.

17. The method of claim 7, wherein the second indication augments the first indication, wherein the first indication provides a static parameter and the second indication provides a dynamic parameter.

18. The method of claim 7, wherein the second indication overrides a part of the first indication.

19. The method of claim 7, wherein the first indication and / or the second indication specify a period of time in which information in the first indication and / or the second indication is valid.

20. The method of claim 19, wherein the period of time is counted from a time instant the first indication or the second indication is transmitted, and the period of time is applicable to all subsequent data receptions from the network node (404) without receiving prior reference signals to perform tracking or fine synchronization.

21. The method of any of claims 19 to 20, wherein the period of time is applicable for one or more subsequent time instants and counted from a time instant the UE (402) receives a reference signal to perform tracking or fine synchronization.

22. The method of any of claims 19 to 21, wherein the period of time is applicable for one or more subsequent time instants and counted from a time instant the network determines the UE (402) to have received a reference signal to perform tracking or fine synchronization.

23. The method of any of claims 19 to 22, wherein the period of time coincides with a time required by the UE (402) to perform tracking or fine synchronization.

24. The method of any of claims 1 to 23, wherein the UE (402) performs data decoding if a subset of configured link parameters match the first indication or the second indication.

25. The method of any of claims 1 to 23, wherein the UE performs data decoding irrespective of configured link parameters.

26. The method of any of claims 1 to 25, wherein the UE determines values of one or more link parameters as specified by the standard specification, wherein:a value of a link parameter for data reception without fine synchronization is directly provided by the standard; ora value of a link parameter for data reception without fine synchronization is computed following a standard-specified method.

27. A User Equipment, UE, (402) that is configured to perform data reception from a network node (404) without receiving prior reference signals to perform tracking or fine synchronization for data reception , the UE (402) comprising processing circuitry that is configured to:transmit (408), to the network node (404), a first indication that the UE (402) supports or has a preference on link parameters related to data reception without receiving prior referencesignals to perform tracking or fine synchronization;receive (416), from the network node (404), signaling indicating data reception based on the link parameters; andperform (418) data reception according to the signaling.

28. The UE (402) of claim 27, wherein the processing circuitry is further configured to perform any of claims 2 to 26.

29. A method performed by a network node (404) for facilitating data reception by a User Equipment, UE, (402) without having received prior reference signals to perform tracking or fine synchronization for data reception, the method comprising:receiving (408), from the UE (402), a first indication that the UE (402) supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization;receiving (412), from the UE (402) a second indication comprising information related to a second set of maximum rank and / or Channel Quality Indicator, CQI, values beyond which the UE (402) cannot be assumed to correctly decode data in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for such data receptions;performing (414) a selection of link parameters based on the first indication and the second indication; andproviding (416) to the UE (402), a configuration indicating data reception based on the selected link parameters.

30. The method of claim 29, wherein the configuration indicates a time period for which the link parameters are applicable.

31. The method of any of claims 29 to 30, wherein the configuration is provided via one or more of Radio Resource Control, RRC, signaling, Medium Access Control, MAC, Control Elements, MAC CE, or downlink control information, DCI.

32. A network node (404) that facilitates data reception by a User Equipment, UE, (402) without having received prior reference signals to perform tracking or fine synchronization for data reception, the network node (404) comprising processing circuitry that is configured to:receive (408), from the UE (402), a first indication that the UE (402) supports or has a preference on link parameters related to data reception without receiving prior reference signals to perform tracking or fine synchronization;receive (412), from the UE (402) a second indication comprising information related to a second set of maximum rank and / or Channel Quality Indicator, CQI, values beyond which the UE (402) cannot be assumed to correctly decode data in subsequent data receptions without receiving prior reference signals to perform tracking or fine synchronization for such data receptions; perform (414) a selection of link parameters based on the first indication and the second indication; andprovide (416) to the UE (402), a configuration indicating data reception based on the selected link parameters.

33. The network node (404) of claim 32, wherein the processing circuitry is further configured to perform any of claims 30 to 31.

34. A system comprising a user equipment (402) of claim 27 or 28 and a network node (404) of claim 32 or 33.