Feedback message for broadcasted assistance information

The proposed solution improves the NRPPa Assistance Information Feedback by reporting failures per System Information message and per type of positioning system information message, enhancing broadcasting success and simplifying debugging in 3GPP networks.

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

Patent Information

Application Number
PCT/SE2025/050428
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The current NRPPa Assistance Information Feedback procedure in 3GPP standards lacks granularity in failure reporting, only indicating posSIB type failures without specifying the System Information message, leading to non-robust broadcasting and difficulty in debugging.

Method used

Implementing a new information element in the Assistance Information Feedback message to indicate failures per System Information message and per type of positioning system information message, allowing for more detailed feedback on broadcasting issues.

Benefits of technology

Enhances the success rate of positioning system information broadcasting by providing finer granularity in failure reporting, enabling the RAN node to handle posSIB types independently across different System Information messages and simplifying debugging for the LMF.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SE2025050428_12112026_PF_FP_ABST
    Figure SE2025050428_12112026_PF_FP_ABST
Patent Text Reader

Abstract

According to an aspect, there is provided a method performed by a radio access network, RAN, node in a communication network The method comprises sending (302), to a location management node in the communication network, a feedback message relating to broadcasted assistance information relating to one or more Global Navigation Satellite Systems, GNSSs. The broadcasted assistance information relates to one or more system information messages, and each system information message relates to one or more types of positioning system information message. The feedback message indicates a system information message or system information messages for which a broadcast failure has occurred.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] FEEDBACK MESSAGE FOR BROADCASTED ASSISTANCE INFORMATION

[0002] Technical Field

[0003] This disclosure relates to the broadcast of assistance information for Global Navigation Satellite System(s) in a communication network, and in particular to a feedback message relating to the broadcast of the assistance information.

[0004] Background

[0005] In 3rdGeneration Partnership Project (3GPP)-defined systems, a Location Management Function (LMF) may collect Global Navigation Satellite System (GNSS) assistance data, for example as described in 3GPP Technical Standard (TS) 23.273 “5G System (5GS) Location Services (LCS)”, v17.8.0. This is performed by reusing Data Collection from an Application Function (AF), for example as described in 3GPP TS 23.501 “System architecture for the 5G System (5GS)” v17.14.0. The collection of the GNSS assistance data may be performed periodically.

[0006] The LMF generates a mapping table of GNSS assistance data and area(s) in which the GNSS assistance data applies (these area(s) are referred to as “applicable area(s)”) (e.g. Tracking Area (TA) lists). The LMF may generate multiple sets of GNSS assistance data for the same location area, and each of them may have a corresponding location accuracy.

[0007] After the collection, the LMF may send the collected GNSS assistance data to gNB(s) via New Radio Positioning Protocol A (NRPPa) Assistance Information Transfer Procedures, for example as described in 3GPP TS 38.455 “NR Positioning Protocol A (NRPPa)” v17.6.0, and the gNB(s) broadcast the assistance data in System Information (SI) to target User Equipments (UEs) on cell(s) that may be indicated by the LMF.

[0008] The LMF supports the provision of broadcast assistance data to UEs via Next Generation-Radio Access Network (NG-RAN) in ciphered or un-ciphered form, and forwards any ciphering keys to subscribed UEs via an Access and Mobility Management Function (AMF).

[0009] Fig. 1 is a signalling diagram illustrating a procedure for broadcasting network assistance data. Fig. 1 shows the signalling between a UE, a NG-RAN, an AMF and a LMF. Fig. 1 and the below procedure is set out in 3GPP TS 23.273 v17.8.0, and is used by the LMF to support broadcasting of network assistance data to target UEs.

[0010] 1. The LMF triggers a Namf_Communication_NonUeN2MessageTransfer service operation which carries the Network Assistance Data to be sent to NG-RAN node via the AMF. The service operation includes the Network Assistance Data message and the target NG-RAN node identity.The Network Assistance Data message includes assistance data which may be optionally ciphered. The LMF may send one or multiple sets of GNSS assistance data to the target NG-RAN node.

[0011] 2. The AMF forwards the Network Assistance Data message to the target NG-RAN node indicated in step 1 in an N2 Transport message. The AMF includes a Routing identifier in the N2 Transport message that identifies the LMF.

[0012] 3. The NG-RAN node broadcasts the assistance data contained in the Network Assistance Data message.

[0013] 4. The target NG-RAN node may return feedback on assistance information broadcasting to the AMF in a Network Assistance Data Feedback message. The target NG-RAN node shall also include the Routing identifier in the N2 Transport message received in step 2.

[0014] 5. The AMF invokes the Namf_Communication_NonUeN2InfoNotify service operation towards the LMF indicated by the routing identifier received in step 4. The service operation includes the Network Assistance Data Feedback message received in step 4.

[0015] The NG-RAN positioning procedures related to LMF and NG-RAN node communication are specified in 3GPP TS 38.455 “NR Positioning Protocol A (NRPPa)” v17.6.0. The purpose of the Assistance Information Control procedure is to allow the LMF to signal positioning assistance information to the NG-RAN Node for assistance information broadcasting.

[0016] Fig. 2 is a signalling diagram illustrating a procedure to support broadcast of assistance data. Fig. 2 shows the signalling between a UE, a NG-RAN node, an AMF and a LMF. Fig. 2 and the below procedure is set out in section 7.5.2 of 3GPP TS 38.305 v17.8.0 “NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN”.

[0017] 1. The LMF sends an NRPPa Assistance Information Control message to the NG-RAN node to start broadcasting assistance information, specified in 3GPP TS 38.455 “NR Positioning Protocol A (NRPPa)” v17.6.0.

[0018] The NRPPa message includes Broadcast information including start or stop, positioning broadcasts cell identity and Assistance Information.

[0019] Each Assistance information may include one or more System Information (SI) groups (so called System Information message(s)), where each group contains the broadcast periodicity and one or more posSIB types together with Assistance Information Meta Data to be scheduled in the same SI message. SI groups are described in 3GPP TS 38.305 V17.8.0.The Assistance Information Meta Data carries GNSS ID and Satellite Based Augmentation System (SBAS) ID to identify the network-assisted GNSS methods. Different GNSSs can be used separately or in combination to determine the location of the UE. Additionally, the metadata also includes information on whether positioning System Information Block (posSIB) types is ciphered or not.

[0020] Each posSIB type may be ciphered and / or segmented at the LMF and the payload of posSIB type is transparent to NG-RAN and only be decoded by UE, as specified in 3GPP TS 37.355 “LTE Positioning Protocol (LPP)” v17.9.0.

[0021] Tables 1-7 below are found in 3GPP TS 38.455 v17.6.0. Table 1 below shows the content of the Assistance Information Control message. Table 2 below shows the content of the Assistance Information Information Element (IE). Table 3 defines the maxNrOfPosSImessage and maxNrOfPosSIBs lEs. Table 4 defines the Positioning System Information Block (SIB) Type. Table 5 defines the PosSIB Segments. Table 6 defines the maxNrOfSegments IE. Table 7 defines the Assistance Information Meta Data.

[0022] ASSISTANCE INFORMATION CONTROL (LMF

[0023]

[0024] NG-RAN node):

[0025]

[0026] Table 1: Assistance Information Control

[0027] ASSISTANCE INFORMATION CONTROL:: ASSISTANCE INFORMATION

[0028]

[0029]

[0030] Table 2: Assistance Information

[0031]

[0032] Table 3: maxNrOfPosSImessage and maxNrOfPosSIBs ASSISTANCE INFORMATION CONTROL:: ASSISTANCE INFORMATION:: POSSIB-TYPE

[0033]

[0034] ASSISTANCE INFORMATION CONTROL: ASSISTANCE INFORMATION:: POSSIB

[0035] SEGMENT:

[0036]

[0037] Table 5: PosSIB Segments

[0038]

[0039] Table 6: maxNrOfSegments

[0040] ASSISTANCE INFORMATION CONTROL: ASSISTANCE INFORMATION:: ASSISTANCE INFORMATION META DATA:

[0041]

[0042]

[0043] Table 7: Assistance Information Meta Data

[0044] 2. The NG-RAN node includes the received System Information groups in Radio Resource Control (RRC) System Information Messages and corresponding scheduling information in System Information Block 1 (SIB1).

[0045] 3. If the posSIB types were ciphered by the LMF, the LMF invokes the Nlmf_Broadcast_CipheringKeyData Notify service operation towards the AMF carrying one or more ciphering keys (the Nlmf_Broadcast_CipheringKeyData Notify service operation is defined in section 6.14.2 of 3GPP TS 23.273 “Technical Specification Group Services and System Aspects; 5G System (5GS) Location Services (LCS); Stage 2 (Release 17)” V17.8.0).

[0046] 4. At any time after Step 1, the NG-RAN node may send a NRPPa Assistance Information Feedback message to the LMF providing feedback on assistance information broadcasting, as specified in 3GPP TS 38.455 “NR Positioning Protocol A (NRPPa)” v17.6.0. The message may include an assistance information failure list indicating that certain posSIB types could not be configured for broadcasting by the NG-RAN node.

[0047] Table 8 below defines the Assistance Information Feedback message, and Table 9 below defines the Assistance Information Failure List.

[0048]

[0049] Table 8: Assistance Information Feedback

[0050]

[0051] Table 9: Assistance Information Failure List

[0052] 5. If the assistance information in a System Information group changes, the LMF provides updated information in a NRPPa Assistance Information Control message.

[0053] 6. The NG-RAN node replaces the previously stored System Information groups with the new information received at Step 5 and includes the new System Information groups in RRC System Information Messages.

[0054] 7. If the LMF wants to abort the broadcast of a System Information Group, it sends a NRPPa Assistance Information Control message to the NG-RAN node including an indication to stop broadcasting the assistance information.

[0055] Summary

[0056] In the current NRPPa Assistance Information Feedback procedure, the Assistance Information Control is sent per one or multiple System Information messages, and each System Information message might include one or multiple posSIB types.

[0057] With this, the same posSIB type can be broadcast in different System Information messages, and this same posSIB type in different System Information messages can be differentiated by different Assistance Information Meta Data (i.e. different GNSS constellations like GNSS ID or SBAS ID).

[0058] However, in the Assistance Information Feedback which can be sent at any time, it only includes the Assistance Information Failure List. In this list, only the posSIB type is listed without the reference to any System Information message. This means that if the same posSIB type is presented in different System Information messages and one message fails to broadcast a particular posSIB type, then that particular posSIB type is indicated in the Assistance Information Failure List, and that posSIB type is not broadcast in other System Information messages.

[0059] This leads to a non-robust manner of broadcasting the same posSIB type in more than one System Information message due to the limitation in the information structure in the NRPPa Assistance Information Feedback.Furthermore, the current procedure also limits the possibility to send feedback per System Information message.

[0060] Finally, in the current Assistance information Failure List, the outcome only shows whether the posSIB failed or not. It does not indicate the reason for the failure (for example: exceeding the number of System Information messages supported by NG-RAN, exceeding the max Transport Block Size (TBS), exceeding the payload in llu interface to UE, posSIB type is not supported, etc.), and it could lead to the difficulty on the LMF’s side to debug.

[0061] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. These solutions may be applied to 5thGeneration (5G) / New Radio (NR) networks and the associated 3GPP standards. It will also be appreciated that these solutions can be implemented in similar or corresponding procedures for broadcasting GNSS assistance information in so-called 6thGeneration (6G) networks. Briefly, rather than only being able to send a failure per type of positioning system information message (e.g. per type of positioning SIB, or per posSlBType), the solutions enable the sending of a failure per System Information message, or per type of positioning system information message (e.g. posSlBType) per System Information message.

[0062] In some embodiments, a new information element or indication for the System Information message(s) can be added to a feedback or response message (e.g. an Assistance Information Feedback message) which is sent at any time from a RAN node (e.g. NG-RAN) to a location management node (e.g. LMF). This new information element or indication can be sent in addition to a message or information indicating a failure in broadcasting assistance information (e.g. an Assistance Information Failure List). This reflects the same manner in which a control message for broadcasting assistance information (e.g. an Assistance Information Control message) is sent from LMF to NG-RAN.

[0063] With these solutions, it is possible to send an indication of failure per type of positioning system information message (e.g. posSlBType) per System Information message, and / or an indication of a failure for the entire System Information message.

[0064] If the same type of positioning system information message (e.g. posSlBType) fails in one System Information message, it is still able to broadcast with different Assistance Information Meta Data information in (an)other System Information message(s). Additionally, this can allow the feedback to be sent per System Information message.

[0065] In some solutions, a failure cause per type of positioning system information message (e.g. posSlBType) or per System Information message can be added to indicate the cause of the failure to the location management node (e.g. LMF).According to a first aspect, there is provided a method performed by a radio access network, RAN, node in a communication network. The method comprises sending, to a location management node in the communication network, a feedback message relating to broadcasted assistance information relating to one or more Global Navigation Satellite Systems, GNSSs. The broadcasted assistance information relates to one or more system information messages, and each message relates to one or more types of positioning system information message. The feedback message indicates a system information message or system information messages for which a broadcast failure has occurred.

[0066] According to a second aspect, there is provided a core network node in a communication network. The method comprises receiving, from a Radio Access Network, RAN, node in the communication network, a feedback message relating to broadcasted assistance information relating to one or more Global Navigation Satellite Systems, GNSSs. The broadcasted assistance information relates to one or more system information messages, and each message relates to one or more types of positioning system information message. The feedback message indicates a system information message or system information messages for which a broadcast failure has occurred.

[0067] According to a third aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method according to the first aspect, the second aspect, or any embodiments thereof.

[0068] According to a fourth aspect, there is provided a radio access network (RAN) node, configured to perform the method according to the first aspect, or any embodiments thereof.

[0069] According to a fifth aspect, there is provided a radio access network (RAN) node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said RAN node is operative to perform the method according to the first aspect, or any embodiments thereof.

[0070] According to a sixth aspect, there is provided a location management node, configured to perform the method according to the second aspect, or any embodiments thereof.

[0071] According to a seventh aspect, there is provided a location management node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said location management node is operative to perform the method according to the second aspect, or any embodiments thereof.

[0072] Certain embodiments may provide one or more of the following technical advantage(s). In particular, the disclosed solutions enable the possibility to increase the success rate for thebroadcast of positioning system information, since failures are indicated with a finer granularity (i.e. per system information message(s), or per system information message(s) and per type(s) of positioning system information message). There is an advantage in being able to handle the same type of positioning system information message (e.g. posSIB Type) used for different GNSS / SBAS IDs in different positioning System Information message(s) specified in 3GPP TS 38.455 “NR Positioning Protocol A (NRPPa)” v17.6.0, independently of each other.

[0073] Embodiments of this disclosure provide that the RAN node (e.g. NG-RAN) shall have the ability to send a message or information indicating a failure in broadcasting assistance information (e.g. an Assistance Information Failure List) per System Information message, which can help to mitigate the possibility of a high broadcasting failure of particular type(s) of positioning system information message(s) (e.g. posSIB Type(s)).

[0074] Embodiments that indicate a cause of failure (e.g. a Failure Cause) per type of positioning system information message (e.g. posSIB Type) and / or per System Information message can help the location management node (LMF) to be aware of what is happening in the RAN (e.g. in the NG-RAN). Additionally, it can simplify the difficulty to handle the packing of posSIB type for each System Information message in the RAN (e.g. in the NG-RAN).

[0075] Brief Description of the Drawings

[0076] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:

[0077] Fig. 1 is a signalling diagram illustrating a procedure for the broadcasting of network assistance data;

[0078] Fig. 2 is a signalling diagram illustrating procedures to support broadcast of assistance data; Fig. 3 is a flow chart illustrating a method performed by a Radio Access Network (RAN) network node in accordance with some embodiments;

[0079] Fig. 4 is a flow chart illustrating a method performed by a location management node in accordance with some embodiments;

[0080] Fig. 5 shows an example of a communication system in accordance with some embodiments;

[0081] Fig. 6 shows another example of a communication system in accordance with some embodiments;

[0082] Fig. 7 shows a RAN node in accordance with some embodiments;

[0083] Fig. 8 shows a core network node, such as a location management node, in accordance with some embodiments; and

[0084] Fig. 9 is a block diagram illustrating a virtualization environment in which functionsimplemented by some embodiments may be virtualized.

[0085] Detailed Description

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

[0087] As noted above, the solutions and embodiments presented in this disclosure may be applied to 5G / NR networks and the associated 3GPP standards, and / or applied to similar or corresponding procedures for broadcasting GNSS assistance information in 6G networks.

[0088] The techniques described herein provide that, rather than only being able to send a failure per type of positioning system information message (e.g. positioning SIB, or posSlBType), the solutions enable the sending of a failure per System Information message, or per type of positioning system information message (e.g. posSlBType) per System Information message.

[0089] In some embodiments, a new information element or indication for the System Information groups message(s) can be added to a feedback or response message (e.g. an Assistance Information Feedback message) which is sent at any time from a RAN node (e.g. NG-RAN) to a location management node (e.g. LMF). This new information element or indication can be sent in addition to a message or information indicating a failure in broadcasting assistance information (e.g. an Assistance Information Failure List). This reflects the same manner in which a control message for broadcasting assistance information (e.g. an Assistance Information Control message) is sent from LMF to NG-RAN.

[0090] With these solutions, it is possible to send an indication of failure per type of positioning system information message (e.g. posSlBType) per System Information message, and / or an indication of a failure for the entire System Information message.

[0091] If the same type of positioning system information message (e.g. posSlBType) fails in one System Information message, it is still able to broadcast with different Assistance Information Meta Data information in (an)other System Information message(s). Additionally, this can allow the feedback to be sent per System Information message.

[0092] In some solutions, a failure cause per type of positioning system information message (e.g. posSlBType) or per System Information message can be added to indicate the cause of the failure to the location management node (e.g. LMF).

[0093] Several different embodiments are envisaged for how to indicate failed posSIB types per System Information message. Likewise, different embodiments are envisaged for indicating a failure for the entire System Information message.

[0094] Four specific embodiments are described below as improvements to the operationsaccording to the current 3GPP standards (e.g. 3GPP TS 38.455 “NR Positioning Protocol A (NRPPa)” V17.6.0).

[0095] While the embodiments are described and illustrated with reference to a non-distributed RAN node arrangement, it will be appreciated that the techniques described herein can also be applied to distributed RAN nodes, i.e. RAN nodes that include a Central Unit (CU) and one or more Distributed Units (DUs), that exchange information using the F1AP signalling protocol. The Assistance Information Transfer procedures over NRPPa are the same as over F1AP, as defined in 3GPP TS 38 473 “F1 Application Protocol (F1AP)” 17.7.0. The Assistance Information Feedback over F1AP also follows the same scheme as in NRPPa procedures.

[0096] Embodiment 1: In Embodiment 1, an Information Element (IE) is added to / included in the ASSISTANCE INFORMATION CONTROL message that identifies the system information message. A new IE is added to the ASSISTANCE INFORMATION FEEDBACK message that indicates System Information message(s) together with failed posSIB types (i.e. the posSIB types for which broadcast failed). In this embodiment, only SI messages with failed posSIBs need to be included in the feedback message.

[0097] Embodiment 2: In Embodiment2, an IE is added to / included in the ASSISTANCE INFORMATION CONTROL message that identifies the system information message. In the ASSISTANCE INFORMATION FEEDBACK message, the Assistance Information Failure List is updated to indicate failed SI message. In this embodiment, only SI messages with failed posSIBs need to be included in the feedback message.

[0098] Embodiments: In Embodiments, an IE is added to / included in the ASSISTANCE INFORMATION FEEDBACK message per SI message with failed posSIB types. In this embodiment, all SI messages, in the order in which they appear in the ASSISTANCE INFORMATION CONTROL message, must be included in the ASSISTANCE INFORMATION FEEDBACK message. In this embodiment, only failed posSIB types need to be sent in the feedback message.

[0099] Embodiment 4: In Embodiment 4, the Outcome in the Assistance Information Failure List in the ASSISTANCE INFORMATION FEEDBACK message is updated to also include posSlBtypes that did not have a broadcast failure (i.e. the broadcast was okay / successful). In this embodiment, each posSIB type and SI message must be reported in the feedback message in the same order as they appeared in the ASSISTANCE INFORMATION CONTROL message.Exemplary modifications to 3GPP TS 38.455 “NR Positioning Protocol A (NRPPa)” v17.6.0 are provided below that illustrate how the standard can be modified to implement the various embodiments. Additions / modifications to the standard are shown in bold and underline.

[0100] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * **** 9.1.3.1 ASSISTANCE INFORMATION CONTROL (applicable to Embodiment 1 and Embodiment 2)

[0101] ASSISTANCE INFORMATION CONTROL:: ASSISTANCE INFORMATION

[0102]

[0103] Table 10: Assistance Information

[0104] *************************************************************************************************************

[0105] 9.1.3.2 ASSISTANCE INFORMATION FEEDBACK (applicable to Embodiment 1)

[0106] This message is sent by the NG-RAN Node to give feedback on assistance information broadcasting.Direction: NG-RAN Node LMF.

[0107]

[0108] Table 11: Assistance Information Feedback

[0109]

[0110] *************************************************************************************************************

[0111] ************************************************************************************************************* 9.1.3.2 ASSISTANCE INFORMATION FEEDBACK (applicable to Embodiment 2)

[0112] This message is sent by the NG-RAN Node to give feedback on assistance information broadcasting.

[0113] Direction: NG-RAN Node

[0114]

[0115]

[0116] Table 13: Assistance Information Feedback

[0117]

[0118] Table 14: Assistance Information Failure List

[0119] *************************************************************************************************************

[0120] 9.1.3.2 ASSISTANCE INFORMATION FEEDBACK (applicable to Embodiment 3)

[0121] This message is sent by the NG-RAN Node to give feedback on assistance information broadcasting.

[0122] Direction: NG-RAN Node

[0123]

[0124]

[0125]

[0126] Table 15: Assistance Information Feedback

[0127]

[0128] Table 16: Assistance Information Message Failure List

[0129] 9.1.3.2 ASSISTANCE INFORMATION FEEDBACK (applicable to Embodiment 4)

[0130] This message is sent by the NG-RAN Node to give feedback on assistance information broadcasting.

[0131] Direction: NG-RAN Node

[0132]

[0133]

[0134]

[0135] Table 17: Assistance Information Feedback

[0136]

[0137] *************************************************************************************************************

[0138] Fig. 3 is a flow chart depicting a method performed by a RAN node in accordance with particular embodiments. The RAN network node may be the RAN network node 510 as described later with reference to Fig. 5, or the Access Point (AP) 610 described later with reference to Fig.

[0139] 6. The RAN node may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product.

[0140] The method begins at step 302 with the RAN node sending a feedback message to a location management node in the communication network. The location management node may be a LMF. The feedback message relates to broadcasted assistance information relating to one or more GNSSs. The broadcasted assistance information relates to one or more system information (SI) messages, and each message relates to one or more types of positioning system information message (e.g. one or more posSlBTypes). The feedback message indicates a SI message or SI messages for which a broadcast failure has occurred.

[0141] The feedback message can be an Assistance Information Feedback message, such as aNRPPa Assistance Information Feedback message, as shown in Fig. 2.

[0142] In some embodiments, the broadcast failure indication relates to the SI message(s) that have failed. That is, the feedback message may comprise at least one broadcast failure indication for indicating a SI message or SI messages for which a broadcast failure has occurred, or at least one broadcast failure indication for each SI message for which a broadcast failure has occurred, or a respective broadcast failure indication for each SI message for which a broadcast failure has occurred.

[0143] In alternative embodiments, separate failure indications can be provided for SI message(s) and types of positioning SI message for which a broadcast failure has occurred. That is, the feedback message can further indicate one or more types of positioning SI message for which a broadcast failure has occurred, or the feedback message can comprise at least one broadcast failure indication for indicating one or more types of positioning SI message for which a broadcast failure has occurred, or the feedback message can comprise a respective broadcast failure indication for each type of positioning SI message for which a broadcast failure has occurred.

[0144] In other alternative embodiments, the feedback message can indicate one or more types of positioning SI message per SI message for which a broadcast failure has occurred. In these embodiments, the feedback message can comprise at least one broadcast failure indication for indicating one or more types of positioning SI message per SI message for which a broadcast failure has occurred, or the feedback message can comprise a respective broadcast failure indication for each type of positioning SI message per SI message for which a broadcast failure has occurred.

[0145] In any of the above embodiments, the feedback message may comprise a broadcast failure indication that indicates a failure has occurred for all types of positioning SI message for a SI message.

[0146] In some embodiments, the feedback message can include indications of whether broadcast was successful. For example, the feedback message may further indicate a SI message or SI messages for which broadcast was successful, or one or more types of positioning SI message for which broadcast was successful, or one or more types of positioning SI message per SI message for which broadcast was successful.

[0147] The feedback message may indicate broadcast failure using a list, such as an Assistance Information Failure List.

[0148] The feedback message may further indicate a cause of failure for any broadcast failure that has occurred. The feedback message may indicate a respective cause of failure for each broadcast failure that has occurred.

[0149] The method performed by the RAN node may further comprise the RAN node broadcasting,or attempting to broadcast, assistance information relating to the one or more SI messages for the related one or more types of positioning SI message. The feedback message sent in step 302 can be based on an outcome of this broadcasting or attempt(s) to broadcast the assistance information.

[0150] The method shown in Fig. 3 may further comprise the RAN node receiving a control message from the location management node. The control message can relate to broadcast of the assistance information relating to the one or more GNSS. The control message can comprise identifiers for one or more system information messages to be broadcast. Based on the received control message, the RAN node can broadcast, or attempt to broadcast, assistance information relating to the one or more SI messages for the related one or more types of positioning SI message. The control message may be an Assistance Information Control message, such as a NRPPa Assistance Information Control message.

[0151] Fig. 4 depicts a method performed by a core network node, such as a location management node (e.g. LMF), in accordance with particular embodiments. The method may be performed by a core network node such as the core network node 508 or core network node 800 as described later with reference to Fig. 5 and 8 respectively.

[0152] The method begins at step 402 with location management node receiving a feedback message from a RAN node in the communication network. The feedback message relates to broadcasted assistance information relating to one or more GNSSs. The broadcasted assistance information relates to one or more system information messages, and each message relates to one or more types of positioning system information message (e.g. one or more posSlBTypes). The feedback message indicates a system information message or system information messages for which a broadcast failure has occurred.

[0153] The feedback message can be an Assistance Information Feedback message, such as a NRPPa Assistance Information Feedback message.

[0154] In some embodiments, the broadcast failure indication relates to the SI message(s) that have failed. That is, the feedback message may comprise at least one broadcast failure indication for indicating a SI message or SI messages for which a broadcast failure has occurred, or at least one broadcast failure indication for each SI message for which a broadcast failure has occurred, or a respective broadcast failure indication for each SI message for which a broadcast failure has occurred.

[0155] In alternative embodiments, separate failure indications can be provided for SI message(s) and types of positioning SI message for which a broadcast failure has occurred. That is, the feedback message can further indicate one or more types of positioning SI message for which abroadcast failure has occurred, or the feedback message can comprise at least one broadcast failure indication for indicating one or more types of positioning SI message for which a broadcast failure has occurred, or the feedback message can comprise a respective broadcast failure indication for each type of positioning SI message for which a broadcast failure has occurred.

[0156] In other alternative embodiments, the feedback message can indicate one or more types of positioning SI message per SI message for which a broadcast failure has occurred. In these embodiments, the feedback message can comprise at least one broadcast failure indication for indicating one or more types of positioning SI message per SI message for which a broadcast failure has occurred, or the feedback message can comprise a respective broadcast failure indication for each type of positioning SI message per SI message for which a broadcast failure has occurred.

[0157] In any of the above embodiments, the feedback message may comprise a broadcast failure indication that indicates a failure has occurred for all types of positioning SI message for a SI message.

[0158] In some embodiments, the feedback message can include indications of whether broadcast was successful. For example, the feedback message may further indicate a SI message or SI messages for which broadcast was successful, or one or more types of positioning SI message for which broadcast was successful, or one or more types of positioning SI message per SI message for which broadcast was successful.

[0159] The feedback message may indicate broadcast failure using a list, such as an Assistance Information Failure List.

[0160] The feedback message may further indicate a cause of failure for any broadcast failure that has occurred. The feedback message may indicate a respective cause of failure for each broadcast failure that has occurred.

[0161] The method shown in Fig. 4 may further comprise the location management node sending a control message to the RAN node. The control message can relate to broadcast of the assistance information relating to the one or more GNSS. The control message may be an Assistance Information Control message, such as a NRPPa Assistance Information Control message.

[0162] Fig. 5 shows an example of a communication system 500 in accordance with some embodiments. In the example, the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes or base stations of various types, such as accessnetwork nodes 510a and 510b (one or more of which are also referred to as RAN network nodes or RAN nodes 510 herein), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (AP). Some embodiments of the access network 504 may include more than one access network technology. The network nodes 510 of access network 504 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.

[0163] Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 502, including one or more access network nodes 510 and / or core network nodes 508.

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

[0165] The network nodes 510 facilitate direct or indirect connection of wireless devices / UEs 512, such as by connecting UEs 512a, 512b, 512c, and 512d (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections. The access network nodes 510 may be, for example, access points (APs) (e.g. radio access points),base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and New Radio (NR) NodeBs (gNBs)).

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

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

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

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

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

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

[0172] In some examples, the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

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

[0174] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512c and / or 512d) and network nodes (e.g., network node 510b). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514. As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 514 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 514 may retrieve VRassets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy Internet of Things (loT) devices.

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

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

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

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

[0179] Fig. 7 shows a Radio Access Network (RAN) node 700 in accordance with some embodiments. As used herein, RAN node, or more generally “network node”, refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 700 may be configured to operate in communication system 500 of Fig. 5, like network nodes 508 or 510, or in communication system 600 of Fig. 6, like an AP 610 or a station 612. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

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

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

[0182] In particular embodiments, network node 700 includes a processing circuitry 702, a memory 704, a communication interface 706, and a power source 708. In general, in a particular embodiment of network node 700, processing circuitry 702, memory 704, communication interface 706, and power source 708 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 700.

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

[0184] The processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 704, toprovide network node 700 functionality. The processing circuitry 702 may be configured to cause the network node 700 to perform the methods as described with reference to Fig. 3.

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

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

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

[0188] In certain alternative embodiments, network node 700 may be capable of wireless communication but does not include separate radio front-end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).

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

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

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

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

[0193] Fig. 8 shows a core network node 800 in accordance with some embodiments. As used herein, core network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other core network nodes or equipment or RAN network nodes, in a telecommunication network. The core network node 800 may be operable as a core network node, a core network function or, more generally, a core network entity, such as the core network node 508 described above with respect to Fig. 5). In particular embodiments, the core network node 800 a location management node, such as a Location Management Function (LMF) in a 5G / NR network, or an equivalent or similar node / function in a 6G network.

[0194] The core network node 800 includes processing circuitry 802, a memory 804, a communication interface 806, and a power source 808, and / or any other component, or any combination thereof. The core network node 800 may be composed of multiple physically separate components, which may each have their own respective components. In certain scenarios in which the core network node 800 comprises multiple separate components, one or more of the separate components may be shared among several core network nodes.

[0195] The processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other core network node 800 components, such as the memory 804, core network node 800 functionality. For example, the processing circuitry 802 may be configured to cause the network node to perform the methods as described with reference to Fig. 4.

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

[0197] The communication interface 806 is used in wired or wireless communication of signalling and / or data between a core network node, access network node(s), and / or UE.

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

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

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

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

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

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

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

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

[0206] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

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

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

[0209] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.

Claims

Claims1. A method performed by a radio access network, RAN, node in a communication network, the method comprising:sending (302), to a location management node in the communication network, a feedback message relating to broadcasted assistance information relating to one or more Global Navigation Satellite Systems, GNSSs;wherein the broadcasted assistance information relates to one or more system information messages, and wherein each system information message relates to one or more types of positioning system information message, wherein the feedback message indicates a system information message or system information messages for which a broadcast failure has occurred.

2. The method as claimed in claim 1, wherein the feedback message comprises at least one broadcast failure indication for indicating a system information message or system information messages for which a broadcast failure has occurred.

3. The method as claimed in claim 1 or 2, wherein the feedback message comprises at least one broadcast failure indication for each system information message for which a broadcast failure has occurred.

4. The method as claimed in any of claims 1-3, wherein the feedback message comprises a respective broadcast failure indication for each system information message for which a broadcast failure has occurred.

5. The method as claimed in claim 1, wherein the feedback message further indicates one or more types of positioning system information message for which a broadcast failure has occurred.

6. The method as claimed in claim 1 or 5, wherein the feedback message comprises at least one broadcast failure indication for indicating one or more types of positioning system information message for which a broadcast failure has occurred.

7. The method as claimed in any of claims 1, 5 or 6, wherein the feedback message comprises a respective broadcast failure indication for each type of positioning system information message for which a broadcast failure has occurred.

8. The method as claimed in claim 1, wherein the feedback message indicates one or more types of positioning system information message per system information message for which a broadcast failure has occurred.

9. The method as claimed in claim 1 or 8, wherein the feedback message comprises at least one broadcast failure indication for indicating one or more types of positioning system information message per system information message for which a broadcast failure has occurred.

10. The method as claimed in any of claims 1, 8 or 9, wherein the feedback message comprises a respective broadcast failure indication for each type of positioning system information message per system information message for which a broadcast failure has occurred.

11. The method as claimed in any of claims 1-10, wherein the feedback message comprises a broadcast failure indication that indicates a failure has occurred for all types of positioning system information message for a system information message.

12. The method as claimed in any of claims 1-11, wherein the feedback message further indicates a system information message or system information messages for which broadcast was successful.

13. The method as claimed in any of claims 1-12, wherein the feedback message further indicates one or more types of positioning system information message for which broadcast was successful.

14. The method as claimed in any of claims 1-13, wherein the feedback message further indicates one or more types of positioning system information message per system information message for which broadcast was successful.

15. The method as claimed in any of claims 1-14, wherein the feedback message indicates broadcast failure using a list.

16. The method as claimed in claim 15, wherein the list is an Assistance Information Failure List.

17. The method as claimed in any of claims 1-16, wherein the feedback message further indicates a cause of failure for any broadcast failure that has occurred.

18. The method as claimed in any of claims 1-16, wherein the feedback message further indicates a respective cause of failure for each broadcast failure that has occurred.

19. The method as claimed in any of claims 1-18, wherein the method further comprises: broadcasting, or attempting to broadcast, assistance information relating to the one or more system information messages for the related one or more types of positioning system information message.

20. The method as claimed in claim 19, wherein the feedback message is sent based on an outcome of the broadcasting or attempt to broadcast the assistance information.

21. The method as claimed in any of claims 1-20, wherein the method further comprises: receiving, from the location management node, a control message relating to broadcast of the assistance information relating to the one or more GNSS.

22. The method as claimed in claim 21, wherein the method further comprises:based on the received control message, broadcasting, or attempting to broadcast, assistance information relating to the one or more system information messages for the related one or more types of positioning system information message.

23. The method as claimed in claim 21 or 22, wherein the control message is an Assistance Information Control message.

24. The method as claimed in any of claims 21-23, wherein the control message is a New Radio Positioning Protocol A, NRPPa, Assistance Information Control message.

25. The method as claimed in any of claims 1-24, wherein the types of positioning system information message are posSlBType.

26. The method as claimed in any of claims 1-25, wherein the feedback message is an Assistance Information Feedback message.

27. The method as claimed in any of claims 1-26, wherein the feedback message is a New Radio Positioning Protocol A, NRPPa, Assistance Information Feedback message.

28. The method as claimed in any of claims 1-27, wherein the location management node is a Location Management Function, LMF.

29. A method performed by a core network node in a communication network, the method comprising:receiving (402), from a Radio Access Network, RAN, node in the communication network, a feedback message relating to broadcasted assistance information relating to one or more Global Navigation Satellite Systems, GNSSs;wherein the broadcasted assistance information relates to one or more system information messages, and wherein each system information message relates to one or more types of positioning system information message, wherein the feedback message indicates a system information message or system information messages for which a broadcast failure has occurred.

30. The method as claimed in claim 29, wherein the feedback message comprises at least one broadcast failure indication for indicating a system information message or system information messages for which a broadcast failure has occurred.

31. The method as claimed in claim 29 or 30, wherein the feedback message comprises at least one broadcast failure indication for each system information message for which a broadcast failure has occurred.

32. The method as claimed in any of claims 29-31, wherein the feedback message comprises a respective broadcast failure indication for each system information message for which a broadcast failure has occurred.

33. The method as claimed in claim 29, wherein the feedback message further indicates one or more types of positioning system information message for which a broadcast failure has occurred.

34. The method as claimed in claim 29 or 33, wherein the feedback message comprises at least one broadcast failure indication for indicating one or more types of positioning system information message for which a broadcast failure has occurred.

35. The method as claimed in any of claims 29, 33 or 34, wherein the feedback message comprises a respective broadcast failure indication for each type of positioning system information message for which a broadcast failure has occurred.

36. The method as claimed in claim 29, wherein the feedback message indicates one or more types of positioning system information message per system information message for which a broadcast failure has occurred.

37. The method as claimed in claim 29 or 36, wherein the feedback message comprises at least one broadcast failure indication for indicating one or more types of positioning system information message per system information message for which a broadcast failure has occurred.

38. The method as claimed in any of claims 29, 36 or 37, wherein the feedback message comprises a respective broadcast failure indication for each type of positioning system information message per system information message for which a broadcast failure has occurred.

39. The method as claimed in any of claims 29-38, wherein the feedback message comprises a broadcast failure indication that indicates a failure has occurred for all types of positioning system information message for a system information message.

40. The method as claimed in any of claims 29-39, wherein the feedback message further indicates a system information message or system information messages for which broadcast was successful.

41. The method as claimed in any of claims 29-40, wherein the feedback message further indicates one or more types of positioning system information message for which broadcast was successful.

42. The method as claimed in any of claims 29-41, wherein the feedback message further indicates one or more types of positioning system information message per system information message for which broadcast was successful.

43. The method as claimed in any of claims 29-42, wherein the feedback message indicates broadcast failure using a list.

44. The method as claimed in claim 43, wherein the list is an Assistance Information Failure List.

45. The method as claimed in any of claims 29-44, wherein the feedback message further indicates a cause of failure for any broadcast failure that has occurred.

46. The method as claimed in any of claims 29-44, wherein the feedback message further indicates a respective cause of failure for each broadcast failure that has occurred.

47. The method as claimed in any of claims 29-46, wherein the method further comprises: sending, to the RAN node, a control message relating to broadcast of the assistance information relating to the one or more GNSS.

48. The method as claimed in claim 47, wherein the control message is an Assistance Information Control message.

49. The method as claimed in claim 47 or 48, wherein the control message is a New Radio Positioning Protocol A, NRPPa, Assistance Information Control message.

50. The method as claimed in any of claims 29-49, wherein the types of positioning system information message are posSlBType.

51. The method as claimed in any of claims 29-50, wherein the feedback message is an Assistance Information Feedback message.

52. The method as claimed in any of claims 29-51, wherein the feedback message is a New Radio Positioning Protocol A, NRPPa, Assistance Information Feedback message.

53. The method as claimed in any of claims 29-52, wherein the core network node is a location management node54. The method as claimed in claim 53, wherein the location management node is a Location Management Function, LMF.

55. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of claims 1-54.

56. A radio access network, RAN, node, configured to perform the method of any of claims 1-28.

57. A radio access network, RAN, node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said RAN node is operative to perform the method of any of claims 1-28.

58. A core network node, configured to perform the method of any of claims 29-54.

59. A core network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said core network node is operative to perform the method of any of claims 29-54.