Method and node for failure handling for TEG reporting

By introducing new signaling mechanisms and information elements into the wireless communication system, the failure reporting problem of UE Tx timing error processing in UL TDOA or multi-RTT positioning is solved, and the power consumption optimization and positioning of UE under low power consumption state is realized. Improved accuracy.

CN119072978APending Publication Date: 2024-12-03TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380035236.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-21
Filing Date
2023-04-21
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In the prior art, UE Tx timing error processing for UL TDOA or multi-RTT positioning has a missing failure reporting mechanism, resulting in reduced positioning accuracy and increased network load, and the positioning operation of the UE in a low power consumption state cannot be effectively handled.

Method used

Provides a signaling mechanism that allows UE and network nodes to send failure messages when TEG information is not available, ensures that network nodes understand the UE's status, and reduce power consumption in low power consumption states, by defining new information elements (IE) and signaling process failure.

Benefits of technology

Effectively handle UE Tx timing error failure reports for UL TDOA or multi-RTT positioning, reduce network load, improve positioning accuracy, and optimize power consumption management in UE low power state.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072978A_ABST
    Figure CN119072978A_ABST
Patent Text Reader

Abstract

A method performed by a radio node is provided. The method includes receiving a request for timing error group (TEG) information from a network node; and in response to failing to provide the TEG information, transmitting to the network node a message including an indication that the TEG information fails to be reported. A method performed by a network node is also provided. The method comprises: transmitting a request for timing error group (TEG) information to a radio node; and receiving, from the radio node, a message comprising an indication that the TEG information is not provided.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 333,196, entitled “FAILURE HANDLING FOR TEG REPORTING,” filed with the U.S. Patent and Trademark Office on April 21, 2022, the contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communication systems, and more particularly to methods and nodes for failure handling of time error group (TEG) reports. Background Art

[0004] New Radio (NR) Positioning Architecture

[0005] Since the introduction of Release (Rel)-15 and NR, the Long Term Evolution (LTE) Positioning Protocol (LPP), which is a point-to-point communication protocol between a Location Management Function (LMF) and a target device, has been agreed to be reused for User Equipment (UE) positioning in both NR and Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA), see, for example, Third Generation Partnership Project (3GPP) Technical Specification (TS) 37.355.

[0006] At the core network, a new logical node called LMF is the main server responsible for calculating the UE position based on NR-specific positioning methods, E-UTRA-specific positioning methods, or based on both Radio Access Technology (RAT)-specific positioning methods in a hybrid manner. The NR Positioning Protocol Annex (NRPPa) is a communication protocol between the Next Generation (NG) Radio Access Network (RAN) and the LMF specified in TS 38.455.

[0007] NR positioning architecture Figure 1 As defined in TS 38.305.

[0008] In Rel-16, new enhanced positioning methods have been defined in NR to help calculate UE positioning, such as:

[0009] -NR Enhanced Cell ID (E-CID);

[0010] -Multiple round trip time (RTT) positioning;

[0011] - Downlink Angle of Departure (DL-AoD);

[0012] - Downlink Time Difference of Arrival (DL-TDOA);

[0013] - Uplink Time Difference of Arrival (UL-TDOA);

[0014] - Uplink angle of arrival (UL AoA), including azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA).

[0015] An example of a signaling exchange for UL-TDOA positioning (also applicable to UL-AOA) is given in Figure 2 Shown in.

[0016] In Rel-16, the multi-RTT positioning method is specified as a part of "UE performing UE receive (Rx)-transmit (Tx) measurements".

[0017] Mitigation of timing errors in positioning

[0018] In Rel-17, precision enhancement for time-based methods (Multi-RTT, DL TDOA, UL TDOA) has been proposed to mitigate timing errors, which led to the introduction of the concept of Timing Error Group (TEG). This principle stems from the observation that signals transmitted or received on different beams may be carried on different Radio Frequency (RF) chains or different antenna panels. Even after calibration in the UE / Transmission Reception Point (TRP) implementation, there will always be residual timing errors in the transmission and reception timing between the signals transmitted on these different RF chains / antenna panels.

[0019] Due to such residual timing error (hereinafter referred to as timing error), the UE may not be able to accurately know when a signal such as a sounding reference signal (SRS) is transmitted from the UE antenna, resulting in an unknown transmit (TX) delay τ TX ,like Figure 3 As shown. Note that τ TX is the residual error after the UE performs any compensation for the known delay, and τ TX Can be positive or negative.

[0020] If the UE has only one antenna panel, this TX timing error will cancel out when forming the TDOA measurement from the gNB (base station) uplink receive time of arrival (UL-RTOA) measurement. When the UE has multiple antenna panels, the TX timing error may be different for different UE antenna panels, so the TX timing errors do not always cancel out when forming the gNB TDOA measurement, e.g. Figure 4 For example, Figure 4 It is shown that when the same UE antenna panel is used for both the target TRP (e.g., TRP-2) and the reference TRP, the TX timing error cancels out when the reference signal time difference (RSTD) (e.g., RSTD2) is formed. However, when different UE antenna panels are used for the target TRP (e.g., TRP-1) and the reference TRP, the TX timing error does not cancel out when the RSTD (e.g., RSTD1) is formed.

[0021] Due to the difference in Tx timing error (i.e., when the Tx timing error is Figure 4 The accuracy of UL TDOA positioning will be reduced if the RSTD1 in the signal is not offset.

[0022] However, if one reference TRP is used for each UE antenna panel when forming the RSTD measurement, then Figure 5 As shown, TX timing errors are cancelled. In the figure, TRP-1 is added as the reference TRP for antenna panel a, while the standard REF-TRP is maintained as the reference TRP for antenna panel b. For example, when RSTD measurements are made in the usual manner using only one reference TRP, TX timing errors are not normally cancelled (e.g., RSTD1 and RSTD3). However, if one reference TRP is used for each antenna panel when making RSTD measurements, TX timing errors are cancelled. Figure 5 In the example, TRP-1 is added as the reference TRP for antenna panel a, while the standard REF-TRP is kept as the reference TRP for antenna panel b, resulting in two RSTD measurements without TX timing errors (e.g., RSTD2 and RSTD 3-1 ).

[0023] In order to make it possible for the LMF to know which measurements can be combined so that the associated TX / RX timing errors are offset, the TEG concept was introduced in 3GPP NR Rel-17. When the LMF uses the TEG concept to know which measurements can be grouped, the TX / RX timing errors can be mitigated and the positioning performance can be greatly improved. Different types of TEGs at both the UE and the TRP have been introduced in NR Rel-17. These include the following:

[0024] - UE Tx "Timing Error Group" (UE Tx TEG): A UE Tx TEG is associated with transmissions of one or more UL SRS resources for positioning purposes that have a Tx timing error within a certain margin.

[0025] - TRP Tx "Timing Error Group" (TRP Tx TEG): A TRP Tx TEG is associated with transmissions of one or more DL PRS resources that have a Tx timing error within a certain margin.

[0026] - UE Rx "Timing Error Group" (UE Rx TEG): A UE Rx TEG is associated with one or more DL measurements that have an Rx timing error within a certain margin.

[0027] - TRP Rx "Timing Error Group" (TRP Rx TEG): TRP Rx TEG is associated with one or more UL measurements that have Rx timing error within margin.

[0028] -TRP RxTx “Timing Error Group” (TRP RxTx TEG): Rx timing error and Tx timing error associated with a TRP report of one or more gNB Rx-Tx time difference measurements with a “Rx timing error + Tx timing error” difference within a specific margin.

[0029] - UE RxTx "Timing Error Group" (UE RxTx TEG): Rx timing error and Tx timing error associated with UE reports of one or more UE Rx-Tx time difference measurements having a "Rx timing error + Tx timing error" difference within a certain margin.

[0030] Figure 6 An example of association of UL SRS TEG Tx with an SRS resource set and SRS resources is shown.

[0031] In NR Rel-17, TEG can be used to mitigate the impact of UE TX timing error on UL TDOA / multi-RTT positioning. To achieve this, the UE needs to report the association between SRS (sent in SRS resources) and UE Tx TEG (i.e., the associated UE TxTEG ID).

[0032] Inactive mode targeting

[0033] 3GPP Rel-17 defines a process by which a UE can perform positioning in a low power state such as a radio resource control (RRC) inactive state. The UE can obtain necessary assistance data via positioning system information broadcast in the inactive mode, perform RSTD measurement in the inactive mode, and also send a positioning measurement report to the network (NW) in the inactive mode.

[0034] Small Data Transfer (SDT) is a process of transmitting UL data from a UE in RRC_INACTIVE state. SDT is performed using random access or configuration grant (CG).

[0035] Small data solutions have been introduced earlier in LTE, with a focus on machine type communications (MTC). For example, Rel-15 Early Data Transfer (EDT) and Rel-16 Preconfigured Uplink Resources (PUR) have been standardized for LTE-M and Narrowband Internet of Things (NB-IoT). Unlike these features, Rel-17 Small Data for NR does not directly target MTC use cases, and the Work Item Description (WID) for Small Data Transfer includes smartphone background traffic as a reason.

[0036] Sections 5.7.14 and 5.7.15 of TS 38.331v17.0.0 describe UE positioning information. Summary of the invention

[0037] There are some challenges. To mitigate UE Tx timing error for UL TDOA or multi-RTT, the UE sends TEG association information of UL SRS resources for positioning and Tx TEG ID to the serving gNB, and the serving gNB should forward the association information provided by the UE to the LMF. Different interfaces are affected: Uu, RRC, F1 and NRPPa. However, the signaling of the association information adds load to the network. The signaling mechanism for sending the association information of UL SRS resources for positioning and Tx TEG should be well designed / optimized, and the process should be robust enough so that the UE can handle and report errors.

[0038] Similarly, the LMF may request the TRP to measure the same SRS resources of a UE with different TRP Rx TEGs for UL-TDOA or multiple RxTx TEGs for multi-RTT (where the RxTx TEGs are as defined in TS 38.214 V17.1.0), and report the corresponding measurements to the LMF.

[0039] However, the current standard does not provide provisions for handling failures of the above reports, so how to handle failures of the above reports is an unresolved issue.

[0040] The same applies to the association of UE Rx TEG with DL-Positioning Reference Signal (PRS).

[0041] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges.

[0042] For example, the present disclosure provides a signaling mechanism for signaling any failure message / information element (IE) when the UE fails to report the association of the UE Tx TEG with the SRS or the TEG ID.

[0043] The present disclosure also provides a signaling mechanism for indicating failure when the LMF requests TRP to measure the same SRS resources of UEs with different TRP Rx TEGs for UL-TDOA.

[0044] The present disclosure also provides a signaling mechanism for indicating failure when the LMF requests TRP measurement of the same SRS resources of a UE with different TRP RxTx for gNB Rx-Tx time difference measurement.

[0045] The present disclosure also provides a mechanism for the NW to understand whether the UE is performing positioning operations in a low power consumption state to reduce power consumption, and therefore it may not be able to provide results that may result in higher power consumption.

[0046] More specifically, a method performed by a radio node (e.g., a gNB) is provided. The method includes: receiving a request for timing error group (TEG) information from a network node; and in response to failing to provide the TEG information, sending a message to the network node including an indication that the TEG information failed to be reported. A radio node for performing the method is also provided.

[0047] A method performed by a network node (eg, LMF) is also provided. The method comprises: sending a request for timing error group (TEG) information to a radio node; and receiving a message from the radio node including an indication that the TEG information could not be provided. A network node for performing the method is also provided.

[0048] Certain embodiments may provide one or more of the following technical advantages.

[0049] - The UE has the opportunity to inform the NW that it is unable to provide UE reports.

[0050] - The gNB-Distributed Unit (DU) has the opportunity to inform the gNB-Central Unit (CU) that it is unable to provide TRP reports.

[0051] - The gNB-CU has the opportunity to inform the positioning server that it cannot provide TRP reports.

[0052] - NW (LMF) has the opportunity to be aware that the UE is operating in a low power state and power saving is critical. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Exemplary embodiments will be described in more detail with reference to the following drawings, in which:

[0054] Figure 1 An example of a positioning architecture in NR is shown.

[0055] Figure 2An example of a flow chart for the UL-TDOA method as specified in TS 38.305 is shown.

[0056] Figure 3 Shows an example of transmission delay caused by timing error.

[0057] Figure 4 Examples of different transmit timing errors are shown.

[0058] Figure 5 An example of RSTD measurements is shown in which some timing errors cancel and some other timing errors do not cancel.

[0059] Figure 6 An example of association of UL SRS TEG Tx with an SRS resource set and SRS resources is shown.

[0060] Figure 7 An example of a sequence flow / signaling diagram for association of UE Tx TEG with SRS according to an embodiment is shown.

[0061] Figure 8 An example of a sequence flow / signaling diagram between a UE and an LMF for reporting a failure of association of a TEG with a reference signal is shown according to an embodiment.

[0062] Fig. 9 An example of a sequence flow / signaling diagram between a gNB and LMF for reporting a failure of association of a TEG with a reference signal is shown according to an embodiment.

[0063] Fig.10 An example of a positioning information exchange process in case of an unsuccessful operation according to an embodiment is shown.

[0064] Fig.11 An example of a positioning measurement process in an unsuccessful operation situation according to an embodiment is shown.

[0065] Fig.12 An example of a positioning information exchange process in case of an unsuccessful operation according to an embodiment is shown.

[0066] Fig.13 An example of a measurement process in the case of an unsuccessful operation according to an embodiment is shown.

[0067] Fig.14 An example of a flow chart of a method in a radio node according to an embodiment is shown.

[0068] Fig.15 An example of a flow chart of a method in a network node according to an embodiment is shown.

[0069] Fig.16An example of a communication system according to the embodiment is shown.

[0070] Fig.17 A schematic diagram of a UE according to an embodiment is shown.

[0071] Fig.18 A schematic diagram showing a network node according to an embodiment is shown.

[0072] Fig.19 A block diagram of a host computer is shown.

[0073] Fig. 20 A block diagram illustrating a virtualized environment is shown.

[0074] Fig.21 A communication diagram showing the host. DETAILED DESCRIPTION

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

[0076] Embodiments herein provide a method of defining a new IE (or information) in signaling for association of UE Tx TEG with UL-SRS, wherein the signaling includes sending a failure indicator to the NW.

[0077] Embodiments also provide a method of defining a new IE (or information) in signaling for association of UE Rx TEG with measurements performed on DL-PRS, wherein the signaling includes sending a failure indicator to the NW.

[0078] For example, Figure 7 A sequence flow of a method 100 for signaling an association of a UE Tx TEG with an SRS (or an associated TEG ID) and for sending a failure indicator to the NW is shown.

[0079] In step 102, the LMF sends a request to the gNB through the NRPPa interface to configure SRS.

[0080] In step 104, the gNB sends an RRC signal to the UE, which indicates / includes the configuration of the SRS and a request (periodic or one-time) for the association of SRS resources with the TEG ID (or associated TEG ID).

[0081] In step 106, the UE provides the association of SRS resources with the TED ID (or associated TEG ID) to the gNB via RRC (e.g., the UE is able to determine the association).

[0082] In step 108, the gNB forwards the association of the SRS resources with the TED ID (or the associated TEG ID) to the LMF, for example via NRPPa.

[0083] Later, for another transmission, in step 110, the UE may detect / experience a failure to determine the association between the Tx TED and the SRS, and therefore may not be able to provide an association of the TX TEG to the SRS (or an associated TEG ID). The reason / reason for the failure to determine the association is, for example: a change in the state of the UE such that the UE cannot support the reference signal, or the UE is operating at low battery. Other reasons are provided below.

[0084] In this case, in step 112, the UE reports an indication of the failure (of failing to report the association / TEG ID) to the gNB, for example via RRC.

[0085] In step 114, the gNB reports an indication of failure (of failing to report the association / TEG ID) to the LMF, for example via NRPPa.

[0086] This method can also be applied to UL-TDOA.

[0087] Now, the steps of method 100 will be described in more detail.

[0088] For example, more details are provided regarding step 112, in which the UE provides an indication of the failure of Tx TEG to SRS association reporting to the serving gNB using RRC.

[0089] An example of Abstract Syntax Notation One (ASN.1) is shown below (for UEPositioningAssistanceInfo IE), where a failure indication and possible reasons for failure are indicated in bold text in RRC. As shown in the bold text in the ASN.1 below, one of the reasons or causes for failure, represented by "state-transition", may be when the RRC state transitions to an RRC state where SRS cannot be transmitted (e.g., transitions to RRC_IDLE, or transitions to RRC_INACTIVE when the UE does not have the ability to support SRS transmission in RRC_INACTIVE). The reason represented by "lowpowerstate" is when the UE performs positioning operations in a low power state and is unable to provide an association of the UE Tx TEG to the SRS in order to reduce power consumption. In some embodiments, the UE may also provide the cause of failure as "unknown". However, it should be noted that the cause of failure is not limited to the example shown in the ASN.1 text below. Other failure reasons may be as follows:

[0090] -The cause of failure may be communicated as a collision of the SRS used for positioning with the physical uplink shared channel (PUSCH). For example, if the SRS used for the serving cell collides completely or partially with the PUSCH, the SRS used for positioning may be dropped in the symbol where the collision occurs (see TS 38.214 V17.1.0 Section 6.2.1). As a result, the SRS cannot be transmitted in all symbols allocated for the SRS, and such information may be sent to the serving cell gNB as the cause of failure.

[0091] -The cause of the failure may be communicated as a change in the UE Tx TEG due to a temporal variation in the timing error. For example, in one case, when an SRS is transmitted, the timing error difference between that SRS transmission and a previous SRS transmission (e.g., a previous SRS transmitted from the same UE antenna panel) may have been within the margin used to define the UE Tx TEG. However, when the association of the SRS to the TEG ID is sent to the serving gNB, the timing error difference corresponding to the same UE antenna panel may have exceeded the margin. Therefore, the cause of “failureIndication-r17” may be indicated as a change in the UE Tx TEG since the SRS was transmitted.

[0092] In some examples, if the UE cannot provide at least one UE Tx TEG to SRS association as part of the list ue-TxTEG-AssociationList-r17, the "failureIndication-r17" field is only included in the UEPositioningAssistanceInfo message. If the UE is able to provide at least one UE TxTEG to SRS association as part of the list ue-TxTEG-AssociationList-r17, the "failureIndication-r17" field is not included in the UEPositioningAssistanceInfo message.

[0093] ASN.1 example for UEPositioningAssistanceInfo IE:

[0094] The UEPositioningAssistanceInfo message is used to provide positioning assistance information requested by the network.

[0095] Signaling Radio Bearer: SRB1

[0096] RLC-SAP:AM

[0097] Logical channel: DCCH

[0098] Direction: UE to network

[0099] UEPositioningAssistanceInfo message

[0100]

[0101]

[0102]

[0103] Now, more details are provided regarding step 114, where the gNB (e.g., gNB CU) provides the LMF with a failure of Tx TEG to SRS association / TEG ID reporting using, for example, NRPPa.

[0104] In one example, an indication of failure to report UE Tx TEG indication is signaled to the positioning server (i.e., LMF) via NRPPa positioning signaling from the gNB CU that terminates the NRPPa protocol.

[0105] In one example, the reporting failure of the UE Tx TEG may indicate whether it is due to the UE moving to an RRC_INACTIVE state, being in a low power state, or due to an unknown reason or other reasons.

[0106] In one example, the failure indication may be signaled during a NRPPA POSITIONING INFORMATION FAILURE message, such as Fig.12 For example, Fig.12 The following example from TS 38.455 v17.0.0 is provided below with the added text in bold:

[0107] If the Requested SRS Transmission Characteristics IE was included in the POSITIONING INFORMATION REQUEST message and the NG-RAN node was unable to configure any SRS transmission for the UE, it shall respond with a POSITIONING INFORMATION FAILURE message. If handover of the target UE has been triggered, the NG-RAN node shall send a POSITIONING INFORMATION FAILURE message with an appropriate cause value. If the UE TEG ID Information Request IE was included in the POSITIONING INFORMATION REQUEST message and the NG-RAN node was unable to report any UE Tx TEG associated information for the UE, the NG-RAN node shall respond with a POSITIONING INFORMATION FAILURE message with an appropriate cause value.

[0108] In one example, the gNB-CU responds / sends in NRPPA POSITIONING INFORMATION FAILURE, reusing existing cause values ​​from TS 38.455 section 9.2.1 to indicate reported incapability and failure (e.g., “measurement temporarily unavailable” or “requested item not supported in time”).

[0109] In one example, failure of UE Tx TEG association / TEG ID reporting is indicated in the NRPPa Error Indication message with an appropriate cause value. This can occur in case of periodic or aperiodic update of UE Tx TEG association from gNB-CU to LMF.

[0110] In another example, a new cause value may be defined in section 9.2.1 of TS 38.455 to indicate in the NRPPA POSITIONING INFORMATION FAILURE or NRPPA ERROR INDICATION message the inability or failure reason for the gNB-CU to report UE Tx TEG information, such as "UE Tx TEG not available" or "UE is in low power state" or "UE is in RRC_INACTIVE state".

[0111] The present disclosure also provides a method for signaling an indication of UL-RTOA measurement failure (for UL-TDOA) when an LMF requests TRP to measure the same SRS resources of UEs with different TRP Rx TEGs.

[0112] The present disclosure also provides a method for signaling a failure of gNB Rx-Tx time difference measurement (for multi-RTT) when the LMF requests TRP measurement of the same SRS resources of UEs with different TRP RxTx TEGs.

[0113] F1 positioning embodiment for UE Tx TEG reporting failure

[0114] Reference again Figure 7 , the gNB may have a split architecture including a gNB-DU and a gNB-CU. In step 112 of method 100, the gNB-DU receives an indication from the UE that a UE Tx TEG (e.g., association of SRS with the UE Tx TEG) cannot be reported. Then, the gNB-DU hosting the lower layers (e.g., PHY) sends a message to the gNB-CU terminating the NRPPa protocol, the message including an indication that an SRS association with the UE Tx TEG cannot be reported. For example, the message is signaled via F1AP positioning signaling.

[0115] In one example, failure to report UE Tx TEG may indicate that it is due to the UE being in a low power state, or due to an unknown reason. As mentioned above, other reasons may also be indicated.

[0116] In one example, the failure indication may be signaled during an F1 POSITIONING INFORMATION FAILURE message, such as Fig.10 For example, Fig.10 A case of the positioning information exchange process is shown in the case of an unsuccessful operation. An example from TS 38.473 v17.0.0 is shown below, with some text added in bold:

[0117] If the Requested SRS Transmission Characteristics IE is included in the POSITIONING INFORMATION REQUEST message and the gNB-DU is unable to configure any SRS transmission for the UE, the gNB-DU shall respond with a POSITIONING INFORMATION FAILURE message. If the UE TEG ID Information Request IE is included in the POSITIONING INFORMATION REQUEST message and the gNB-DU is unable to report any UE Tx TEG associated information for the UE, the gNB-DU shall respond with a POSITIONING INFORMATION FAILURE message with an appropriate cause value.

[0118] 9.2.12.13 Positioning Information Request

[0119] This message is sent by the gNB-CU to indicate to the gNB-DU the need to configure the UE to send SRS signals for uplink positioning measurements.

[0120] Direction: gNB-CU→gNB-DU.

[0121]

[0122] 9.2.12.15 Positioning information failed

[0123] This message is sent by the gNB-DU to indicate that SRS transmission cannot be configured for uplink positioning measurements for the UE.

[0124] Direction: gNB-DU→gNB-CU.

[0125]

[0126] In one example, the gNB-DU reuses existing cause values ​​from TS 38.473 section 9.3.1.2 to respond / send an indication of reported inability and failure in F1 POSITIONING INFORMATION FAILURE (e.g., “measurement temporarily unavailable” or “requested item not supported in time”).

[0127] In one example, failure of UE Tx TEG associated reporting is indicated in the F1 Error Indication message with an appropriate cause value. This may occur in the case of periodic or aperiodic updating of UE Tx TEG associated reporting from the gNB-DU to the gNB-CU.

[0128] In another example, a new cause value is defined in section 9.3.1.2 of TS 38.473 to indicate in the F1 POSITIONING INFORMATION FAILURE or ERROR INDICATION message the inability or failure reason for the gNB-DU to report UE Tx TEG information, such as “UE Tx TEG not available” or “UE is in low power state”.

[0129] Figure 8 FIG. 2 shows an exemplary sequence flow of a method 200 for signaling an indication of a failure to report a TEG association from a UE to a LMF, for example, for multiple RTTs. Figure 8 As shown, for example, the UE reports the failure directly to the LMF via LPP.

[0130] More specifically, the method 200 includes step 202, in which the LMF sends a signaling / message to the UE via, for example, LPP, the signaling including the configuration of the DL-PRS and a request for association of the DL-PRS with the Rx TEG ID.

[0131] In step 204 of method 200, the LMF also sends a request for association of UL-SRS with UE Tx TEG, such as association between UL SRS and UE Tx TEG ID. For example, the request is sent via LPP.

[0132] The method 200 also includes step 206, in which the UE detects / experiences a failure to determine an association between a reference signal (DL-PRS or UL-SRS) and a TEG ID (Rx TEG ID or Tx TEG ID), and therefore is unable to report the association. As such, in step 208, the UE sends a report to the LMF, the report including an indication of a failure to report an association of a reference signal with a TEG (such as an association of a DL-PRS with an Rx TEG ID or an association of a UL-SRS with a Tx TEG ID). For example, the report is sent via LPP.

[0133] For multi-RTT, the UE may report the UE capability of supporting UE Tx-TEG to the LMF. For multi-RTT, the associated information may be reported to the LMF together with the UE Rx / Tx measurements.

[0134] Now, more details will be described with respect to step 208 of method 200, in which the UE provides an indication of a failure of Tx TEG to SRS association reporting to the LMF, for example via LPP.

[0135] The addition / indication for failure indication in LPP is provided below as an example in bold text in the ASN.1 of NR-Multi-RTT-SignalMeasurementInformation. The UE uses tegTxReportingfailureIndication-r17 to indicate the failure cause corresponding to the association of SRS to the UE Tx TEG, and the UE uses failureCase-r17 to indicate the failure cause corresponding to the UE RxTx TEG report. One of the failure causes, represented by "state-transition", can be when the RRC state transitions to an RRC state where SRS cannot be transmitted (e.g., transitions to RRC_IDLE or transitions to RRC_INACTIVE when the UE does not have the capability to support SRS transmission in RRC_INACTIVE). The reason represented by "lowpowerstate" is when the UE performs positioning operations in a low power state and cannot provide UE Tx TEG to SRS association or UE RxTx TEG report in order to reduce power consumption. In some embodiments, the UE may also provide the cause of the failure as "unknown". However, it should be noted that the reasons for failure are not limited to the examples shown in bold text. Other reasons for failure may be as follows:

[0136] -The cause of failure may be communicated as a collision of the SRS used for positioning with the physical uplink shared channel (PUSCH). For example, if the SRS used for the serving cell collides completely or partially with the PUSCH, the SRS used for positioning may be dropped in the symbol where the collision occurs (see TS 38.214 V17.1.0 Section 6.2.1). As a result, the SRS cannot be transmitted in all symbols allocated for the SRS, and such information may be sent to the serving cell gNB as the cause of failure.

[0137] -The cause of the failure may be communicated as a change in the UE Tx TEG due to a temporal variation in the timing error. For example, in one case, when an SRS is transmitted, the timing error difference between that SRS transmission and a previous SRS transmission (e.g., a previous SRS transmitted from the same UE antenna panel) may have been within the margin used to define the UE Tx TEG. However, when the association of the SRS to the TEG ID is sent to the serving gNB, the timing error difference corresponding to the same UE antenna panel may have exceeded the margin. In such a case, the UE may indicate the cause of the failure as a change in the UE Tx TEG since the SRS was transmitted.

[0138] In some examples, the "tegTxReportingfailureIndication-r17" field is reported only when the UE cannot provide at least one UE Tx TEG to SRS association. If the UE is able to provide at least one UE Tx TEG to SRS association, the "tegTxReportingfailureIndication-r17" field is not reported to the LMF.

[0139] As an example, the target device may provide NR multi-RTT measurements to the location server using the IE NR-Multi-RTT-SignalMeasurementInformation. The measurements may be provided as a list of TRPs, where the first TRP in the list is used as a reference TRP.

[0140] and Figure 8 similar, Fig. 9 A sequence diagram of a method 300 is shown for signaling an indication of a failure of association of a reference signal with a TEG from a gNB (which may be considered a TRP) to an LMF.

[0141] The method 300 includes step 302, in which the LMF sends a message / signaling to the gNB (e.g., TRP) via NRPPa, for example. The message may include a configuration / request for UL SRS measurement or DL-PRS transmission with a corresponding TEG (Rx TEG or Tx TEG, respectively).

[0142] In step 304, the gNB may experience / determine a failure to associate a DL-PRS transmission with a corresponding TRP Tx TEG or a failure to associate a UL SRS measurement with a corresponding TRP Rx TEG. Some examples of causes of this failure are described above.

[0143] In step 306, the gNB reports an indication of the failure of the association of the DL-PRS / UL measurements with the TEG to the LMF, for example via NRPPa.

[0144] F1 Positioning Example for TRP Rx or RxTx TEG Report Failure

[0145] Fig. 9 The gNB may have a split architecture that includes a gNB-DU and a gNB-CU. In one example, an indication of failure to report TRP Rx TEG or TRP RxTx is sent from the gNB-DU (which hosts lower layers (e.g., PHY)) to the gNB-CU (which terminates the NRPPA protocol). For example, the indication may be signaled via F1AP positioning signaling.

[0146] In one example, the failure indication is signaled during an F1 POSITIONING MEASUREMENT FAILURE message, such as Fig.11 For example, Fig.11 The following example from TS 38.473 v17.0.0 is provided, with some text added in bold:

[0147] If the gNB-DU is unable to configure any of the requested positioning measurements for any of the TRPs in the TRPMeasurement Request List IE of the POSITIONING MEASUREMENT REQUEST message, it shall respond with a POSITIONING MEASUREMENT FAILURE message. If the gNB-DU is unable to report any TRP Rx TEG or TRP RxTx TEG-ID information, it shall respond with a POSITIONING MEASUREMENT FAILURE message with an appropriate cause value.

[0148] In one example, the gNB-DU reuses existing cause values ​​from TS 38.473 section 9.3.1.2 to respond / send an indication of reported inability and failure in F1 POSITIONING MEASUREMENT FAILURE (e.g., “measurement temporarily unavailable” or “requested item not supported in time”).

[0149] In one example, failure of a TRP Rx TEG or a TRP RxTx TEG report is indicated in the F1 Error Indication message with an appropriate cause value.

[0150] In another example, a new cause value is defined in section 9.3.1.2 of TS 38.473 to indicate in the F1POSITIONING MEASUREMENT FAILURE or ERROR INDICATION message the inability or failure reason for the gNB-DU to report the TRP Rx TEG or TRP RxTx information, such as "TRP Rx TEG / TRP RxTx TEG unavailable".

[0151] NRPPA Positioning Example for TRP Rx or RxTx TEG Report Failure

[0152] use Fig. 9 In the case of a segmented architecture of a gNB, in step 306 of the method 300, an indication of failure to report TRP Rx TEG or TRP RxTx TEG is sent from the gNB-CU that terminates the NRPPA protocol to the LMF. For example, the indication may be signaled via NRPPa signaling.

[0153] In one example, the failure indication may be signaled during a MEASUREMENT FAILURE message, such as Fig.13 For example, Fig.13 The following example from TS 38.455 v17.0.0 is provided below, with the added text in bold:

[0154] If the NG-RAN node is unable to configure any of the requested measurements for any of the TRPs in the TRP Measurement RequestList IE of the MEASUREMENT REQUEST message, it shall respond with a MEASUREMENT FAILURE message with an appropriate cause value. If the NG-RAN node is unable to report any TRP Rx TEG or TRP RxTxTEG ID information, it shall respond with a MEASUREMENT FAILURE message with an appropriate cause value.

[0155] In one example, the gNB-CU reuses existing cause values ​​from TS 38.455 section 9.2.1 to respond / send an indication of reported inability and failure in MEASUREMENT FAILURE (e.g., “measurement temporarily unavailable” or “requested item not supported in time”).

[0156] In one example, failure of a TRP Rx TEG or TRP RxTx TEG report is indicated in the NRPPA Error Indication message with an appropriate cause value.

[0157] In another example, a new cause value is defined in section 9.2.1 of TS 38.455 to indicate the inability or failure reason for the gNB to report TRP Rx TEG or TRP RxTx ID information in a MEASUREMENT FAILURE or ERROR INDICATION message, such as "TRP Rx TEG / TRP RxTx TEG unavailable".

[0158] Now go to Fig.14 , a flow chart of a method 400 for indicating a failure of reporting an association between a reference signal and a timing error group (TEG) will be described. The method may be performed by a radio node (e.g. Fig.16 The method 400 may include:

[0159] Step 410: receiving a request for association between a reference signal and a timing error group (TEG) from a network node; and

[0160] Step 420: In response to failing to determine the association, sending a message to the network node including an indication that the association could not be reported.

[0161] In one example, the message may also include an indication of the reason for failure to determine an association or failure to report an association. Some reasons have been described above.

[0162] In the first case, the radio node may be a UE and the network node may be a gNB (which includes a gNB-DU and a gNB-CU). In this case, the association between the reference signal and the TEG may be an association between a downlink reference signal and a receive TEG (e.g., UE Rx TEG) or an association between an uplink reference signal and a transmit TEG (e.g., UE Tx TEG). The request may be received from the network node (e.g., gNB) via RRC. And the message may be sent to the network node (e.g., gNB) via RRC.

[0163] In the second case, the radio node may be a UE and the network node may be a location management function (LMF). In this case, the request may be received from the network node (e.g., LMF) via the LTE Positioning Protocol (LPP). And the message may be sent to the network node (e.g., LMF) via the LPP.

[0164] In the third case, the wireless node may be a transmission reception point (TRP) and the network node may be a LMF. In this case, the request may be received from the network node (e.g., LMF) via NRPPa. And the message may be sent to the network node (e.g., LMF) via NRPPa.

[0165] UE Behavior

[0166] It should be clarified that even when the UE fails to report (periodically) TEG association for any reason, the UE may still continue to send UL SRS. The UE should be able to handle the failure, i.e. provide a failure report on TEG association reporting, and continue to send UL-SRS or perform DL-PRS measurements.

[0167] In one embodiment, if the positioning quality of service (QoS) for high accuracy must be achieved, based on receiving such a failure report, the positioning calculation entity (such as the LPP layer in the LMF) and the UE or any location consuming entity (such as the location service client (LCS client)) can decide whether to continue or abandon / abort the positioning process. In order to achieve high accuracy, obtaining the TEG report may be very critical, and therefore for situations where high accuracy may not be achieved, the positioning calculation entity or the location consuming entity (such as the LCS client) may decide to abandon / abort the process.

[0168] As a note, the LCS Client is an entity that interacts with the Gateway Mobile Location Center (GMLC) to obtain location information of one or more UEs. The LCS Client may reside in the UE.

[0169] In addition, the standard specification of 3GPP TS 38.455 may be changed to "add a failure description for the NRPPA POSITIONING INFORMATION FAILURE message when the NG-RAN fails to report the UE Tx TEG association."

[0170] This change is due to the fact that the current procedure text specifies the behavior of the NG-RAN node when it is unable to configure any SRS transmission for the UE by responding with a POSITIONING INFORMATION FAILURE message. A description of the failure handling is also needed when the NG-RAN node is unable to report any UE Tx TEG associated information if the LMF has requested it.

[0171] Fig.15 A flow chart showing a method 500 for requesting a report of an association between a reference signal and a timing error group (TEG). The method may be performed at a network node such as Fig.161610A or core network node 1608). The method 500 may include:

[0172] Step 510: Sending a request for association between a reference signal and a timing error group (TEG) to a radio node; and

[0173] Step 520: Receive a message from a radio node including an indication of a failure to associate a reference signal with a TEG.

[0174] In one example, the message may also include an indication of the reason for failure to determine an association or failure to report an association. Some reasons have been described above.

[0175] In a first case, the radio node may be a UE and the network node may be a gNB. In this case, a request may be sent to the UE via RRC and a message may be received from the UE via RRC. In another example, the gNB may forward / send a message including an indication of failure to a core network node (e.g., LMF) via NRPPa. The gNB may receive a request to configure the radio node with a reference signal from a core network node (e.g., LMF) via NRPPa. In addition, the gNB may have a gNB-DU and a gNB-CU. The gNB-DU may then send a message including an indication of failure to the gNB-CU via F1. The message may be a positioning information failure message or an error indication message.

[0176] In the second case, the radio node may be a UE and the network node may be a LMF. In this case, the request may be sent from the network node (eg, LMF) to the UE via the LTE Positioning Protocol (LPP). And the message may be received from the UE via the LPP.

[0177] In the third case, the radio node may be a TRP and the network node may be a LMF. In this case, the request may be sent from the network node (eg, LMF) via NRPPa. And the message may be received at the network node (eg, LMF) via NRPPa.

[0178] Fig.16 An example of a communication system 1600 is shown in accordance with some embodiments.

[0179] In this example, the communication system 1600 includes a telecommunications network 1602 including an access network 1604 such as a radio access network (RAN) and a core network 1606 including one or more core network nodes 1608. The access network 1604 includes one or more access network nodes, such as network nodes 1610a and 1610b (one or more of which may be generally referred to as network nodes 1610), or any other similar 3GPP access nodes or non-3GPP access points. The network nodes 1610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1612a, 1612b, 1612c, and 1612d (one or more of which may be generally referred to as UEs 1612) to the core network 1606 via one or more wireless connections.

[0180] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transferring information without the use of wires, cables, or other material conductors. In addition, in different embodiments, the communication system 1600 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 a wired connection or a wireless connection. The communication system 1600 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0181] UE 1612 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to communicate wirelessly with network node 1610 and other communication devices. Similarly, network node 1610 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 1612 and / or with other network nodes or devices in telecommunication network 1602 to enable and / or provide network access (such as wireless network access) and / or perform other functions (such as management in telecommunication network 1602).

[0182] In the depicted example, the core network 1606 connects the network node 1610 to one or more hosts, such as the host 1616. These connections may be direct or indirect connections via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 1606 includes one or more core network nodes (e.g., core network node 1608) constructed with hardware and software components. The features of these components may be substantially similar to those described with respect to the UE, network nodes, and / or hosts, so that their descriptions are generally applicable to the corresponding components of the core network node 1608. The example core network node includes the functions of one or more of a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network open function (NEF), and / or a user plane function (UPF).

[0183] The host 1616 may be under the ownership or control of a service provider other than the operator or provider of the access network 1604 and / or the telecommunications network 1602, and may be operated by or on behalf of the service provider. The host 1616 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (such as retrieving and editing data about various environmental conditions detected by multiple UEs), analysis functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0184] As a whole, Fig.16 The communication system 1600 implements the connection between the UE, the network node and the host. In this sense, the communication system can be configured to operate according to predefined rules or procedures such as specific standards, including but 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 standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other appropriate wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi and / or any low power wide area network (LPWAN) standards such as LoRa and Sigfox.

[0185] In some examples, telecommunication network 1602 is a cellular network implementing 3GPP standardized features. Thus, telecommunication network 1602 can support network slicing to provide different logical networks to different devices connected to telecommunication network 1602. For example, telecommunication network 1602 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive IoT services to additional UEs.

[0186] In some examples, UE 1612 is configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from access network 1604, the UE can be designed to send information to access network 1604 according to a predetermined schedule. Additionally, the UE can be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE can operate using any one or a combination of Wi-Fi, NR and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0187] In this example, the hub 1614 communicates with the access network 1604 to facilitate indirect communication between one or more UEs (e.g., UE 1612c and / or 1612d) and a network node (e.g., network node 1610b). In some examples, the hub 1614 may be a controller, a router, a content source, and analysis, or any of the other communication devices described herein with respect to the UE. For example, the hub 1614 may be a broadband router that enables the UE to access the core network 1606. As another example, the hub 1614 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 1610, or received by an executable code, script, process, or other instruction in the hub 1614. As another example, the hub 1614 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data may be performed. As another example, the hub 1614 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 1614 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then the hub 1614 provides it to the UE directly, after performing local processing, and / or after adding additional local content. In another example, the hub 1614 acts as a proxy server or coordinator for the UE, especially when one or more of the UEs are low-energy IoT devices.

[0188] Hub 1614 can have constant / persistent or intermittent connection to network node 1610b. Hub 1614 can also allow different communication schemes and / or scheduling between hub 1614 and UE (e.g., UE 1612c and / or 1612d) and hub 1614 and core network 1606. In other examples, hub 1614 is connected to core network 1606 and / or one or more UE via wired connection. In addition, hub 1614 can be configured to be connected to M2M service provider and / or connected to another UE via direct connection through access network 1604. In some scenes, UE can establish wireless connection with network node 1610, while still connected via hub 1614 via wired or wireless connection. In some embodiments, hub 1614 can be a dedicated hub, that is, its main function is to route communication from network node 1610b to UE / route from UE to network node 1610b. In other embodiments, the hub 1614 may be a non-dedicated hub, that is, a device that is operable to route communications between UEs and network node 1610b, but is also capable of operating as a communications origin and / or endpoint for certain data channels.

[0189] Fig.17 UE 1700 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted or vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0190] The UE may support device-to-device (D2D) communication, for example by implementing 3GPP standards for sidelink communication, dedicated short range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).

[0191] UE 1700 includes a processing circuit 1702, which is operably coupled to an input / output interface 1706, a power supply 1708, a memory 1710, a communication interface 1712, and / or any other components, or any combination thereof, via a bus 1704. Some UEs may utilize Fig.17 All or a subset of the components shown in . The level of integration between components may vary from one UE to another UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0192] The processing circuit 1702 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 1710 as a machine-readable computer program. The processing circuit 1702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.); programmable logic and appropriate firmware; one or more stored computer programs, general-purpose processors such as a microprocessor or a digital signal processor (DSP), and appropriate software; or any combination of the above. For example, the processing circuit 1702 may include multiple central processing units (CPUs). For example, the processing circuit 1702 may be configured to execute, for example Fig.14 Any step / operation / box of method 400.

[0193] In this example, the input / output interface 1706 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1700. Examples of input devices include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc.

[0194] In some embodiments, the power supply 1708 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., an electrical socket), a photovoltaic device, or a power battery. The power supply 1708 may also include a power circuit for delivering power from the power supply 1708 itself and / or an external power supply to various parts of the UE 1700 via an input circuit or an interface such as a power cable. The delivered power may be used, for example, to charge the power supply 1708. The power circuit may perform any formatting, conversion, or other modification to the power from the power supply 1708 so that the power is suitable for various components of the UE 1700 to which the power is supplied.

[0195] The memory 1710 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable tape cartridge, a flash drive, etc. In one example, the memory 1710 includes one or more application programs 1714, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 1716. The memory 1710 may store any of a variety of operating systems or a combination of operating systems for use by the UE 1700.

[0196] The memory 1710 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (such as a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more user identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a “SIM card”. The memory 1710 may allow the UE 1700 to access instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in memory 1710, which may be or include a device-readable storage medium.

[0197] The processing circuit 1702 may be configured to communicate with an access network or other network using a communication interface 1712. The communication interface 1712 may include one or more communication subsystems and may include an antenna 1722 or be communicatively coupled to the antenna 1722. The communication interface 1712 may include one or more transceivers for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 1718 and / or a receiver 1720 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1718 and the receiver 1720 may be coupled to one or more antennas (e.g., antenna 1722) and may share circuit components, software or firmware, or may be implemented separately alternatively.

[0198] In the illustrated embodiment, the communication functionality of the communication interface 1712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, code division multiple access (CDMA), wideband code division multiple access (WCDMA), GSM, LTE, 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 the like.

[0199] Regardless of the type of sensor, the UE may provide an output of data captured by its sensor via a wireless connection to a network node through its communication interface 1712. The data captured by the UE's sensor may be transmitted to the network node via another UE via a wireless connection. The output may be periodic (e.g., every 15 minutes if it reports a sensed temperature), random (e.g., in order to load balance reports from multiple sensors), in response to a trigger event (e.g., sending an alarm when moisture is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0200] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0201] When in the form of an Internet of Things (IoT) device, a UE may be a device used in one or more application areas including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are or are embedded in: a connected refrigerator or freezer, a television, connected lighting, an electric meter, a robotic vacuum cleaner, etc. Fig.17 In addition to the other components described for the UE 1700 shown in FIG. 1 , a UE in the form of an IoT device includes circuitry and / or software depending on the intended application of the IoT device.

[0202] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other device that is capable of monitoring and / or reporting its operating status or capable of performing other functions associated with its operation.

[0203] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be or be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller for operating the drone.

[0204] Fig.18 A network node 1800 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, NBs, evolved NBs (eNBs), and NR NBs (gNBs)).

[0205] Base stations may be classified based on the amount of coverage they provide (or, stated differently, based on their transmit power level), and thus may be referred to as a femto base station, a pico base station, a micro base station, or a macro base station, depending on the amount of coverage provided. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), which is sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0206] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio (MSR) device such as an MSR BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)) and / or a minimization of drive tests (MDT).

[0207] The network node 1800 includes a processing circuit 1802, a memory 1804, a communication interface 1806, and a power supply 1808. The network node 1800 may be composed of multiple physically separated components (e.g., NB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 1800 includes multiple separated components (e.g., BTS and BSC components), one or more of the separated components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered as a single separated network node in some cases. In some embodiments, the network node 1800 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be repeated (e.g., separate memories 1804 for different RATs), and some components may be reused (e.g., the same antenna 1810 may be shared by different RATs). The network node 1800 may also include multiple sets of various illustrated components for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies, integrated into the network node 1800. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1800.

[0208] The processing circuit 1802 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic, which is operable to provide the functionality of the network node 1800 alone or in conjunction with other network node 1800 components (such as the memory 1804). For example, the processing circuit 1802 is configured to execute when the network node is a core network node. Fig.15 Any action / operation / block of method 500, or when the network node is a gNB / TRP Fig.14 Any action / operation / box of method 400.

[0209] In some embodiments, processing circuitry 1802 includes a system on a chip (SOC). In some embodiments, processing circuitry 1802 includes one or more of radio frequency (RF) transceiver circuitry 1812 and baseband processing circuitry 1814. In some embodiments, radio frequency (RF) transceiver circuitry 1812 and baseband processing circuitry 1814 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, part or all of RF transceiver circuitry 1812 and baseband processing circuitry 1814 may be on the same chip or chipset, board, or unit.

[0210] The memory 1804 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data and / or instructions that can be used by the processing circuit 1802. The memory 1804 may store any suitable instructions, data or information, including computer programs, software, applications, including one or more of logic, rules, codes, tables and / or other instructions that can be executed by the processing circuit 1802 and utilized by the network node 1800. The memory 1804 may be used to store any calculations made by the processing circuit 1802 and / or any data received via the communication interface 1806. In some embodiments, the processing circuit 1802 and the memory 1804 are integrated.

[0211] The communication interface 1806 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown in the figure, the communication interface 1806 includes one or more ports / terminals 1816, for example, sending data to the network and receiving data from the network through a wired connection. The communication interface 1806 also includes a radio front-end circuit 1818, which can be coupled to the antenna 1810, or is a part of the antenna 1810 in some embodiments. The radio front-end circuit 1818 includes a filter 1820 and an amplifier 1822. The radio front-end circuit 1818 can be connected to the antenna 1810 and the processing circuit 1802. The radio front-end circuit can be configured to adjust the signal transmitted between the antenna 1810 and the processing circuit 1802. The radio front-end circuit 1818 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1818 can use a combination of a filter 1820 and / or an amplifier 1822 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be sent via the antenna 1810. Similarly, when receiving data, antenna 1810 may collect radio signals, which are then converted into digital data by radio front end circuit 1818. The digital data may be passed to processing circuit 1802. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0212] In certain alternative embodiments, the network node 1800 does not include a separate radio front end circuit 1818, but rather the processing circuit 1802 includes the radio front end circuit and is connected to the antenna 1810. Similarly, in some embodiments, all or part of the RF transceiver circuit 1812 is part of the communication interface 1806. In other embodiments, the communication interface 1806 includes one or more ports or terminals 1816, the radio front end circuit 1818, and the RF transceiver circuit 1812 as part of a radio unit (not shown), and the communication interface 1806 communicates with the baseband processing circuit 1814 as part of a digital unit (not shown).

[0213] Antenna 1810 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1810 may be coupled to radio front end circuit 1818 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1810 is separate from network node 1800 and may be connected to network node 1800 via an interface or port.

[0214] Antenna 1810, communication interface 1806 and / or processing circuit 1802 may be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, antenna 1810, communication interface 1806 and / or processing circuit 1802 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.

[0215] The power supply 1808 provides power to the various components of the network node 1800 in a form suitable for the various components (e.g., at the voltage and current levels required by each corresponding component). The power supply 1808 may further include or be coupled to a power management circuit to supply power to the components of the network node 1800 for performing the functions described herein. For example, the network node 1800 may be connected to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as a cable, whereby the external power source supplies power to the power circuit of the power supply 1808. As another example, the power supply 1808 may include a power source in the form of a battery or battery pack, which is connected to the power circuit or integrated in the power circuit. If the external power source fails, the battery can provide backup power.

[0216] An embodiment of the network node 1800 may include Fig.18 Additional components beyond those shown are used to provide certain aspects of the network node functionality, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1800 may include a user interface device to allow information to be input into the network node 1800 and to allow information to be output from the network node 1800. This may allow a user to perform diagnostics, maintenance, repair, and other management functions of the network node 1800.

[0217] Fig.19 is a block diagram of a host 1900 according to various aspects described herein, and the host 1900 may be Fig.16 1616 of the embodiment of the host. As used herein, the host 1900 can be or include various combinations of hardware and / or software, including processing resources in a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server farm. The host 1900 can provide one or more services to one or more UEs.

[0218] Host 1900 includes processing circuitry 1902, which is operably coupled to input / output interface 1906, network interface 1908, power supply 1910, and memory 1912 via bus 1904. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (such as Fig.17 and Fig.18 ) describes features of the device so that its description is generally applicable to corresponding components of the host 1900.

[0219] Memory 1912 may include one or more computer programs, including one or more host applications 1914 and data 1916, which may include user data (e.g., data generated by a UE for the host 1900 or data generated by the host 1900 for the UE). An embodiment of the host 1900 may utilize only a subset or all of the components shown. The host application 1914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., generic video coding (VVC), high efficiency video coding (HEVC), advanced video coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, advanced audio coding (AAC), MPEG, and G.711), including code conversion for multiple different categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application 1914 may also provide user authentication and license checks, and may periodically report health status, routing, and content availability to a central node (such as a device in a core network or on the edge). Thus, the host 1900 can select and / or indicate different hosts for over-the-top services for the UE. The host application 1914 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0220] Fig. 202000, in which the functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which may include virtualizing a hardware platform, a storage device, and a network resource. As used herein, virtualization may be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of a function 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), which are implemented in one or more virtual environments 2000 hosted by one or more hardware nodes (such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). In addition, in an embodiment in which a virtual node does not require a radio connection (e.g., a core network node or a host), the node may be fully virtualized.

[0221] Application 2002 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment Q400 to implement some features, functions and / or benefits of some embodiments disclosed herein.

[0222] Hardware 2004 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 2006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2008a and 2008b (one or more of which may be generally referred to as VMs 2008), and / or perform any functions, features, and / or benefits described in conjunction with some of the embodiments described herein. Virtualization layer 2006 may present a virtual operating platform that looks like network hardware to VMs 2008.

[0223] VM 2008 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 2006. Different embodiments of instances of virtual devices 2002 can be implemented on one or more of VM 2008 and can be implemented in different ways. Virtualization of hardware is referred to as network function virtualization (NFV) in some contexts. NFV can be used to integrate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises equipment.

[0224] In the context of NFV, VM 2008 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each of VM 2008 and the portion of hardware 2004 on which the VM is executed, whether hardware dedicated to the VM and / or hardware shared by the VM with other VMs in the VM, form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 2008 on hardware 2004 and corresponds to application 2002.

[0225] Hardware 2004 can be implemented in an independent network node with general or specific components. Hardware 2004 can implement some functions via virtualization. Alternatively, hardware 2004 can be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed via management and coordination 2010, where management and coordination 2010 especially supervises the life cycle management of application 2002. In some embodiments, hardware 2004 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio unit can communicate directly with other hardware nodes via one or more appropriate network interfaces, and can be used in combination with virtual components to provide radio capabilities to virtual nodes such as radio access nodes or base stations. In some embodiments, a control system 2012 can be used to provide some signaling, which can be alternatively used for communication between hardware nodes and radio units.

[0226] Fig.21 A communication diagram showing a host 2102 communicating with a UE 2106 via a network node 2104 over a partial wireless connection according to some embodiments. Fig.21 Describes the UE (such as Fig.16 UE 1612a and / or Fig.17 UE 1700), network nodes (such as Fig.16 The network node 1610a and / or Fig.18 network nodes 1800) and hosts (such as Fig.16 Host 1616 and / or Fig.19 An example implementation of host 1900).

[0227] Similar to the host 1900, an embodiment of the host 2102 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 2102 also includes software stored in or accessible by the host 2102 and executable by the processing circuit. The software includes a host application that is operable to provide services to a remote user, such as a UE 2106 connected via an over-the-top delivery (OTT) connection 2150 extending between the UE 2106 and the host 2102. In providing services to the remote user, the host application can provide user data sent using the OTT connection 2150.

[0228] The network node 2104 includes hardware that enables it to communicate with the host 2102 and the UE 2106. The connection 2160 can be direct or through a core network (such as Fig.16 The core network 1606 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.

[0229] UE 2106 includes hardware and software that is stored in or accessible by UE 2106 and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "application", which is operable to provide services to human or non-human users via UE 2106 with the support of host 2102. In host 2102, the executing host application can communicate with the executing client application via an OTT connection 2150 terminated at UE 2106 and host 2102. In the process of providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 2150 can transmit the request data and the user data. The client application of the UE can interact with the user to generate the user data that it provides to the host application via the OTT connection 2150.

[0230] The OTT connection 2150 may extend via a connection 2160 between the host 2102 and the network node 2104 and via a wireless connection 2170 between the network node 2104 and the UE 2106 to provide connectivity between the host 2102 and the UE 2106. The connection 2160 and the wireless connection 2170 over which the OTT connection 2150 may be provided are drawn abstractly to illustrate communications between the host 2102 and the UE 2106 via the network node 2104 without explicit reference to any intermediate devices and the precise routing of messages via those devices.

[0231] As an example of sending data via the OTT connection 2150, in step 2108, the host 2102 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 2106. In other embodiments, the user data is associated with the UE 2106, which shares data with the host 2102 without explicit human interaction. In step 2110, the host 2102 initiates a transmission carrying the user data to the UE 2106. The host 2102 may initiate the transmission in response to a request sent by the UE 2106. The request may be caused by human interaction with the UE 2106 or by the operation of a client application executed on the UE 2106. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through the network node 2104. Therefore, according to the teachings of the embodiments described throughout the present disclosure, in step 2112, the network node 2104 sends the user data carried in the transmission initiated by the host 2102 to the UE 2106. In step 2114 , UE 2106 receives the user data carried in the transmission, which may be performed by a client application executing on UE 2106 that is associated with a host application executed by host 2102 .

[0232] In some examples, UE 2106 executes a client application that provides user data to host 2102. The user data may be provided in reaction to or in response to data received from host 2102. Thus, in step 2116, UE 2106 may provide the user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via the input / output interface of UE 2106. Regardless of the specific manner of providing the user data, in step 2118, UE 2106 initiates transmission of the user data to host 2102 via network node 2104. In step 2120, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 2104 receives user data from UE 2106 and initiates transmission of the received user data to host 2102. In step 2122, host 2102 receives the user data carried in the transmission initiated by UE 2106.

[0233] One or more of the various embodiments improves the performance of OTT services provided to UE 2106 using OTT connection 2150 in which wireless connection 2170 forms the last leg. More precisely, the teachings of these embodiments can improve, for example, data rate, latency, power consumption, and thereby provide benefits such as reduced user waiting time, better responsiveness, and extended battery life.

[0234] In an example scenario, host 2102 may collect and analyze plant status information. As another example, host 2102 may process audio and video data that may have been retrieved from UE for use in creating a map. As another example, host 2102 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic lights). As another example, host 2102 may store surveillance videos uploaded by UE. As another example, host 2102 may store media content (such as video, audio, VR, or AR) that it may broadcast, multicast, or unicast to UE, or control access to the media content. As other examples, host 2102 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, positioning services, presentation services (such as compiling charts based on data collected from remote devices, etc.), or any other function of collecting, retrieving, storing, analyzing, and / or sending data.

[0235] In some examples, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 2150 between the host 2102 and the UE 2106 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host 2102 and / or the UE 2106. In some embodiments, a sensor (not shown) may be deployed in or associated with other devices through which the OTT connection 2150 passes; the sensor may participate in the measurement process by supplying the values ​​of the monitored quantities illustrated above or supplying the values ​​of other physical quantities according to which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 2150 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 2104. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve dedicated UE signaling, which facilitates the host 2102 to measure throughput, propagation time, delay, etc. Measurements can be made by software enabling messages, particularly empty or "dummy" messages, to be sent using the OTT connection 2150, while monitoring propagation times, errors, etc.

[0236] Although the computing devices described herein (e.g., UE, network node, host) may include the illustrated combination of hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. The determination, calculation, acquisition or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as being located in a larger box or a single box nested in multiple boxes, in practice, the computing device may include multiple different physical components that make up a single illustrated component, and the functions may be divided between separate components. For example, a communication interface may be configured to include any one of the components described herein, and / or the functions of the components may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0237] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some 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 functions may be provided by a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these specific embodiments, the processing circuit may be configured to perform the described functions, regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuit itself or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.

[0238] The above described embodiments are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those skilled in the art without departing from the scope of the description which is limited only by the appended claims.

Claims

1. A method performed by a radio node, the method include: - receiving a request for timing error group TEG information from a network node; as well as - In response to a failure to provide the TEG information, sending a message to the network node including an indication that the TEG information could not be reported.

2. The method according to claim 1, in, The message also includes an indication of the reason for failure to report the TEG information.

3. The method according to claim 1 or 2, in, The TEG information is user equipment UE TEG information.

4. The method according to any one of claims 1 to 3, in, The TEG information is associated with one or more reference signals.

5. The method according to claim 4, in, The association between the one or more reference signals and the TEG information includes an association between an uplink reference signal and a receiving Rx TEG.

6. The method according to any one of claims 1 to 5, in, The radio node is a gNodeB, i.e. gNB, and the network node is a location management function, LMF.

7. The method according to any one of claims 1 to 6, in, The request is received from the network node via NRPPa.

8. The method according to any one of claims 1 to 7, in, The message is sent to the network node via NRPPa.

9. The method according to any one of claims 1 to 8, in, The request is a location information request.

10. The method according to any one of claims 1 to 9, in, The message is that positioning information failed.

11. The method according to any one of claims 1 to 5, in, The radio node is a gNB-DU and the network node is a gNB-CU.

12. The method according to claim 11, in, The request is a location information request.

13. The method according to claim 11 or 12, in, The message is that positioning information failed.

14. The method according to any one of claims 11 to 13, in, The request is received via F1AP signaling.

15. The method according to any one of claims 11 to 14, in, The message is sent via F1AP signaling.

16. A method performed by a network node, the method include: - Sending a request for timing error group TEG information to the radio node; as well as - receiving a message from the radio node comprising an indication that the TEG information could not be provided.

17. The method of claim 16, in, The message also includes an indication of the reason for failure to report the TEG information.

18. The method according to claim 16 or 17, in, The TEG information is user equipment UE TEG information.

19. The method according to any one of claims 16 to 18, in, The TEG information is associated with one or more reference signals.

20. The method of claim 19, in, The association between the one or more reference signals and the TEG information includes an association between an uplink reference signal and a receiving Rx TEG.

21. The method according to any one of claims 16 to 20, in, The radio node is a gNodeB, i.e. gNB, and the network node is a location management function, LMF.

22. The method according to any one of claims 16 to 21, in, The request is sent from the network node via NRPPa.

23. The method according to any one of claims 16 to 22, in, The message is received by the network node via NRPPa.

24. The method according to any one of claims 16 to 23, in, The request is a location information request.

25. The method according to any one of claims 16 to 24, in, The message is that positioning information failed.

26. The method according to any one of claims 16 to 20, in, The radio node is a gNB-DU and the network node is a gNB-CU.

27. The method of claim 26, in, The request is a location information request.

28. The method of claim 26 or 27, in, The message is that positioning information failed.

29. The method according to any one of claims 26 to 28, in, The request is sent via F1AP signaling.

30. The method according to any one of claims 26 to 29, in, The message is received via F1AP signaling.

31. A radio node, include: Communication interface; as well as Processing circuitry associated with the communication interface, the processing circuitry being configured to cause the radio node to perform any of the steps of the method of any one of claims 1 to 15.

32. A network node, include: Communication interface; as well as Processing circuitry associated with the communications interface, the processing circuitry being configured to cause the radio node to perform any of the steps of the method of any of claims 16 to 30.

33. A computer program product comprising a computer readable memory having computer executable instructions stored thereon, the computer executable instructions performing the steps of any one of claims 1 to 30 when executed by a computer.