Positioning broadcast activation

Abstract

A communication device in a communications network can generate (1210) a message requesting positioning assistance data from a location management function ("LMF"). The communication device can further transmit (1220) the message to the LMF of the communications network. The communication device can further receive the positioning assistance data via broadcast from the LMF.

Description

P110433W001POSITIONING BROADCAST ACTIVATIONTECHNICAL FIELD

[0001] The present disclosure is related to communication systems, entities, network node, and host for positioning broadcast activation.BACKGROUND

[0002] FIG. 1 illustrates an example of a new radio (“NR”) network (e.g., a 5th Generation (“5G”) network) including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base station (“gNB”)), multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0003] FIG. 2 illustrates an example of an architecture for location services. In this example, a UE 110 can wireless connect to a radio access network (“RAN”) 120 and / or an access mobility and management function (“AMF”) 240 provided by a network node.

[0004] The AMF 240 can be communicatively coupled to a location management function (“LMF”) 250, a unified data management (“UDM”) 206, a network exposure function (“NEF”) 210, and a gateway mobile location center (“GMLC”) 260, which can be coupled to a location retrieval function (“LRF”) 262. Each of the GMLC 260 and LRF 262 can be communicatively coupled to a location services (“LCS”) Client 270. The UDM 206 can be communicatively coupled to each of the AMF 240, the NEF 210, and the GMLC 260. The NEF 210 can be communicatively coupled to each of the AMF 240, the UDM 206, the GMLC 260, and an application function (“AF”) 220.

[0005] A location management function (“LMF”) or UE can calculate a location of a target (e.g., a UE). In some examples, the UE needs assistance data from the network (e.g., the LMF) in order to improve accuracy of the location estimate. For example, a UE may trigger a mobile origination location request (“MO-LR”) via N1 (between UE 110 and AMF 240) and NL1 (between AMF 240 and LMF 250).SUMMARY

[0006] Various embodiments herein propose that a UE provide, for example as part of a mobile origination location request (“MO-LR”) or as part of an assistance data (“AD”) request, an indication that the UE supports broadcast of positioning assistance data and also if it has received ciphering keys. In some embodiments, the LMF can identify whether a specific regionP110433W001(e.g., a cell) is worth sending broadcast data instead of serving MO-LR requests based on a number of MO-LR requests received from the specific region.

[0007] According to some embodiments, a method of operating a communication device in a communications network is provided. The method includes generating a message requesting positioning assistance data from a location management function, LMF. The method further including transmitting the message to the LMF of the communications network. The method further includes receiving the positioning assistance data via broadcast from the LMF.

[0008] According to other embodiments, a method of operating a network node in a communications network is provided. The method includes receiving a message requesting positioning assistance data be provided to a communication device. The method further includes determining whether to broadcast the positioning assistance data based on the message requesting the positioning assistance data.

[0009] According to other embodiments, a method of operating a network node in a communications network is provided. The method includes receiving a first message from a communications device. The first message requests positioning assistance data and an indication of an identity of the communication device or an identity of an area that the communication device is located. The method further includes selecting a first location management function, LMF, from a plurality of LMFs based on the identity of the communication device or the identity of the area that the communication device is located. The method further including transmitting a second message to the first LMF requesting the positioning assistance data be provided to the communication device.

[0010] According to other embodiments, a communication device, a network node, a radio access network (“RAN”) node, a core network (“CN”) node, an access mobility and management function (“AMF”), a location management function (“LMF”), a computer program, a computer program product, a host, a system, or a non-transitory computer-readable medium is provided to perform one of the above methods.

[0011] Certain aspects of these embodiments may provide technical advantages. Some embodiments herein enable energy savings and radio resource usage when positioning assistance data shall be distributed. In additional or alternative embodiments, the LMF is able to analyze whether broadcast would be suitable in an area or not. In some examples, the LMF is aware of whether there are UEs which are capable of acquiring and decoding positioning SIBs. In additional or alternative examples, the innovations can work even if an operator has enabled or disabled ciphering. The LMF can identify if there are enough UEs which can receive encrypted content (e.g., broadcast of encrypted content can be enabled).P110433W001BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0013] FIG. 1 is a schematic diagram illustrating an example of a 5thgeneration (“5G”) network;

[0014] FIG. 2 is a block diagram illustrating an example of an architecture for location services;

[0015] FIG. 3 is a signal flow diagram illustrating an example of UE positioning operations to support an MO-LR;

[0016] FIG. 4 is a signal flow diagram illustrating an example of a LPP periodic assistance data transfer procedure;

[0017] FIG. 5 is a signal flow diagram illustrating an example of procedures to support broadcast of assistance data;

[0018] FIG. 6 is a signal flow diagram illustrating an example of a NAS signaling transport for MO-LR;

[0019] FIG. 7 is a diagram illustrating an example of single mobile originated location request;

[0020] FIG. 8 is a signal flow diagram illustrating an example of a 5GC -MO-LR procedure;

[0021] FIG. 9 is a diagram illustrating an example of an expanded single mobile originated location request in accordance with some embodiments;

[0022] FIGS. 10- 11 are signal flow diagrams illustrating examples of a LMF determining whether to broadcast positioning assistance data in accordance with some embodiments;

[0023] FIG. 12 is a flow chart illustrating an example of operations performed by a communication device in accordance with some embodiments;

[0024] FIG. 13 is a flow chart illustrating an example of operations performed by a LMF in accordance with some embodiments;

[0025] FIG. 14 is a flow chart illustrating an example of operations performed by an AMF in accordance with some embodiments;

[0026] FIG. 15 is a block diagram of a communication system in accordance with some embodiments;

[0027] FIG. 16 is a block diagram of a user equipment in accordance with some embodiments;P110433W001

[0028] FIG. 17 is a block diagram of a network node in accordance with some embodiments;

[0029] FIG. 18 is a block diagram of a host, which may be an embodiment of the host of FIG. 15, in accordance with some embodiments;

[0030] FIG. 19 is a block diagram of a virtualization environment in accordance with some embodiments; and

[0031] FIG. 20 shows a communication diagram of a host communicating via a network node with a user equipment over a partially wireless connection in accordance with some embodiments.DETAILED DESCRIPTION

[0032] 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, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.

[0033] Additional information may be found in the document provided in the Appendix.

[0034] FIG. 3 is a signal flow diagram illustrating an example of UE positioning operations to support an MO-LR. At block 310, the UE transmits a MO-LR request (including a long term evolution positioning protocol (“LPP”) packet data unit (“PDU”)) to an AMF. At block 320, the AMF transmits a location request (including the LPP PDU) to a LMF.

[0035] At block 330, LPP procedures are performed. In some examples, the UE may request the assistance data via non-access stratum (“NAS”) signaling and the LMF sends the assistance data in a point-to-point manner (e.g., uni-cast), where the target is the UE and the server is the LMF. FIG. 4 illustrates an example of a LPP periodic assistance data transfer procedure.

[0036] At block 410, the UE transmits a RequestAssistanceData message to the LMF. At blocks 420, 430, and 440, the LMF transmits a series of ProvideAssistanceData messages to the UE. At block 450, the UE may transmit an abort message to the LMF. At block 460, the LMFP110433W001 may transmit an abort message to the UE. At block 470, the LMF transmits a ProvideAssistanceData message to the UE.

[0037] Returning to FIG. 3, at block 340, NRPPa procedures are performed. At block 350, the LMF transmits a location response to the AMF. At block 360, the AMF performs a transfer to a 3rdpart. At block 370, the AMF transmits a MO-LR response to the UE.

[0038] The 3rdGeneration Partnership Project (“3GPP”) has defined a mechanism to broadcast the assistance data via radio resource control (“RRC”) system information to all UEs in the cell. FIG. 5 illustrates an example of procedures to support broadcast of assistance data.

[0039] At blocks 510, 550, and 570, an LMF transmits NRPPa Assistance Information Control to a NG-RAN node. In some examples, the LMF sends encrypted or non-encrypted assistance data to RAN in NRPPa Assistance Information Control. At block 530, the LMF transmits a Nlmf_Broadcast_CipheringKeyData Notify message to the AMF. At block 540, the RAN can, in Assistance Information Failure List within NRPPa Assistance Information Feedback, indicate which assistance data it fails to broadcast.

[0040] In addition, with NRPPa Assistance Information Control, the LMF indicates the periodicity of the system information to broadcast.

[0041] At blocks 520 and 550, the RAN transmits the assistance data in posSIBs as system information (“SI”) messages radio resources for physical downlink shared channel (“PDSCH”) and physical downlink control channel (“PDCCH”) and energy in power amplifiers per symbol are consumed. These are the same resources used as for unicast. This means that if the broadcast feature is activated in a cell where no or few UEs use the assistance data, resource and energy consumption increase in the cell. But on the contrary, if there are many UEs using the assistance data, the resource and energy consumption decrease in the cell when activating the feature.

[0042] The supplementary services MO-LR operation enables the UE to launch MO positioning session or request location assistance data using NAS signaling. The NAS signaling are transported using the DL NAS Transport message and the Uplink NAS Transport message defined in 3GPP TS 24.501.

[0043] FIG. 6 illustrates an example of the NAS signaling transport for an MO-LR session.

[0044] At block 610, when a MO-LR location session is initiated at UE, the UE sets thePayload container type to “Location services message container” and includes an LCS-MOLR Invoke in Payload container in the UL NAS TRANSPORT message.

[0045] At block 620, transmits an UL NAS TRANSPORT message to the LMF.

[0046] At block 630, if AMF decides to request positioning from LMF, the AMF invokes the Nlmf Location DetermineLocation Request service operation towards LMF.P110433W001

[0047] At block 640, upon receipt of the Nlmf Location DetermineLocation Response service operation from LMF, the AMF sets the Payload container type to “Location services message container” and includes a MO-LR Response in Payload container in the DL NAS TRANSPORT.

[0048] At block 650, the LMF transmits a DL NAS TRANSPORT message to the UE.

[0049] The optional Additional Information IE of the UL / DL NAS TRANSPORT message is not used when the MO-LR signaling is transported in the Payload container.

[0050] The UE invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component. SS Version Indicator value 1 or above shall be used.

[0051] The receiving network entity shall initiate the handling of location request in the network. The network shall pass the result of the location procedure to the UE by sending a FACILITY message to the UE containing a LCS-MOLR return result component. When location estimate is kept in the network entity and this information satisfies the requested accuracy and the requested maximum age of location, then the network may reuse this information and the positioning measurement procedure may be skipped.

[0052] The network shall pass the result of the location procedure to the UE only if the location estimate is given in a format that the UE supports, as indicated by either the presence (and content) or the absence of the parameter supportedGADShapes, which may be sent by the UE in the LCS-MOLR operation.

[0053] The UE may terminate the dialogue by sending a RELEASE COMPLETE message in the case of single location request (as illustrated in FIG. 6). The UE may also initiate another location request operation by sending a FACILITY message to the network containing a LCS- MOLR invoke component (as illustrated in FIG. 7). After the last location request operation the UE shall terminate the dialogue by sending a RELEASE COMPLETE message.

[0054] If the network is unable to successfully fulfil the request received from the UE (e.g. to provide a location estimate or location assistance information), it shall clear the transaction by sending a RELEASE COMPLETE message containing a return error component. Error values are specified in 3GPP TS 24.080. If the network is unable to provide a location estimate due to lack of support in the UE for the type of shape of the location estimate, then it shall use the error Facility Not Supported.

[0055] If the network has returned a result to the UE in a FACILITY message but, after some PLMN administered time period has elapsed, has not received either a new locationP110433W001 request operation in a FACILITY message or a RELEASE COMPLETE message from the UE, the network may clear the transaction by sending a RELEASE COMPLETE message.

[0056] During the MO-LR operation the UE shall run a timer T(LCSL). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the UE shall assume that the operation has failed, and may terminate the dialogue by sending a RELEASE COMPLETE message, and shall inform the user of the failure.

[0057] FIG. 8 illustrates an example of a 5GC -MO-LR procedure.

[0058] At block 805, if the UE is in CM-IDLE state, the UE instigates the UE triggered Service Request as defined in clause 4.2.3.2 of TS 23.502 in order to establish a signaling connection with the AMF.

[0059] At block 810, the UE sends an MO-LR Request message included in a UL NAS TRANSPORT message. The MO-LR Request may optionally include up to three LPP positioning message(s). Different types of location services can be requested: location estimate of the UE, location estimate of the UE to be sent to an LCS client or AF, or location assistance data. If the UE is requesting its own location or that its own location be sent to an LCS client or AF, this message carries LCS requested QoS information (e.g. accuracy, response time, LCS QoS Class), the requested maximum age of location, the requested type of location (e.g. "current location", "current or last known location") and, optionally for a current location, a scheduled location time. If the UE is requesting that its location be sent to an LCS client, the message shall include the identity of the LCS client or the AF, and may include the address of the GMLC through which the LCS client or AF (via NEF) should be accessed. In addition, a Service Type indicates which MO-LR service of the LCS Client is requested by the UE may be included. The message also may include a pseudonym indicator to indicate a pseudonym should be assigned by the network and transferred to the LCS Client as the UE's identity. The message may also include integrity requirements including Time-to-Alert (“TTA”), Target Integrity Risk (“TIR”) and Alert Limit (“AL”). Definitions of these parameters are specified in TS 38.305.

[0060] If the UE is instead requesting location assistance data, the embedded LPP message specifies the type of assistance data and the positioning method for which the assistance data applies.

[0061] For an LCS 5GC -MO-LR requesting location transfer to an LCS Client or AF, the AMF shall assign a GMLC address, i.e. VGMLC address, which is stored in the AMF. If a VGMLC address is not available, the AMF may reject the location request. The AMF verifies the subscription profile of the UE and decides if the requested service is allowed or not byP110433W001 checking the Mobile Originated data retrieved from UDM during the UE Registration Procedure, as defined in TS 23.502 clause 4.2.2.2.2.

[0062] If the requested type of location is "current or last known location" and the requested maximum age of location information is available, the AMF verifies whether it stores the previously obtained location estimate and related timestamp (if available) of the target UE. If the AMF stores the location estimate and the related timestamp (if available) and the location estimate satisfies the requested accuracy and the requested maximum age of the location, the AMF skips blocks 815, 820, 825, and 830.

[0063] At block 815, the AMF selects an LMF as described in clause 5.1.

[0064] At block 820, the AMF invokes the Nlmf Location DetermineLocation service operation towards the LMF. The service operation includes an LCS Correlation identifier, the serving cell identity, the client type, an indication whether a location estimate, or location assistance data is requested, UE Positioning Capability if available, a list of MO-LR subscribed assistance data and any embedded LPP message(s) in the MO-LR Request. If the UE's location is requested, the service request may include an indication if UE supports LPP, the requested QoS, Supported GAD shapes and any scheduled location time. If location assistance data is requested, the embedded LPP message(s) will convey the requested types of location assistance data. If any of the procedures in clause 6.11.1 or 6.11.2 are used the service operation includes the AMF identity. Once an AMF has selected an LMF it must continue to use that LMF for the duration of the session.

[0065] If the UE is requesting its own location, AMF does not indicate support of a GAD shape for local co-ordinates, see TS 23.032.

[0066] At block 825, if the UE is requesting its own location, the actions described in clause 6.11 are performed together with the actions described for block 880 in clause 6.1.2 if a scheduled location time is present. If the UE is instead requesting location assistance data, the LMF transfers this data to the UE as described in clause 6.11.1. The LMF determines the exact location assistance data to transfer according to the type of data specified by the UE, the UE location capabilities, the MO-LR subscribed assistance data and the current cell.

[0067] At block 830, the LMF transmits a Nmlf Location determineLocation Response message to the AMF.

[0068] At block 835, the AMF transmits a Ngmlc Location LocationUpdate Request to the VGMLC.

[0069] At block 840, the VGMLC transmits a Ngmlc Location LocationUpdate Request message to a HGMLC.P110433W001

[0070] In some examples, one of: 1) blocks 845 and 860; 2) blocks 850, 855, 865, and 870 are performed. In the first example, at block 845, the HGMLC may transmit the location information to an external client. At block 860, the external client transmits a Location Information acknowledgement to the HGMLC.

[0071] In the second example, at block 850, the HGMLC transmits a Ngmlc_Location_LocationUpdateNotify message to a NEF. At block 855, the NEF transmits a Nnef Location LocationUpdateNotify message to an AF. At block 865, the AF transmits a Nnef_Location_LocationUpdateNotify Response to the NEF. At block 870, the NEF transmits a Ngmlc Location LocationUpdateNotify Response to the HGMLC.

[0072] At block 875, the HGMLC transmits a Ngmlc Location LocationUpdate Response to the VGMLC.

[0073] At block 880, the VGMLC transmits a Ngmlc Location LocationUpdate Response to the AMF.

[0074] At block 885, the AMF transmits a DL NAS TRANSMPORT (including a MO-LR Response) to the UE.

[0075] There currently exist certain challenges. In some examples, the LMF can start broadcast of positioning assistance data at any time in a cell but LMF is not aware of if any UEs that use unicast also supports broadcast (can decode positioning SIB or has keys to decipher the encrypted positioning SIBs), which means that LMF may start broadcast that is not used by any or only few UEs, which in turn means that energy and resource consumption increase. The problem is primarily for real time kinematics (“RTK”) assistance data (“AD”) which provides correction information for assisted global navigation satellite system (“A-GNSS”) assistance data to improve the positioning accuracy and RTK assistance data must be updated and delivered to UE more frequently, approximately every 30 seconds. It is expected that there would be demand from UEs to obtain the AD to improve positioning accuracy however LMF needs to understand whether UE has the right capability / subscription to obtain AD using broadcast.

[0076] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In some embodiments, the UE can indicated to a LMF whether it supports broadcast of positioning assistance data.

[0077] In some examples, the UE includes in a MO-LR whether it supports the broadcast (decode positioning SIBs and / or has ciphering keys). Upon receiving such information, the LMF can count how many users have such capability and if the number of requests is “N” within a time period T, then the LMF may decide to enable broadcast for duration “D”. The N, T, and DP110433W001 may be configurable by the NW Operator using operation and maintenance (“0AM”) node / mechanism.

[0078] FIG. 9 illustrates an example of a single mobile originated location request according to some embodiments. It can be observed by comparing FIGS. 7 and 9 that a change can include adding an indication of whether the UE is capable of broadcast support.

[0079] In additional or alternative examples, instead of including an indication of broadcast support (e.g., as a flag or a capability bit) in a LCS message, which is transparent to an AMF, it is included as part of a NAS message which can be read by the AMF and forwarded by AMF to LMF.

[0080] In additional or alternative examples, the indication of broadcast support is included in a LTE positioning protocol (“LPP”) as a capability bit or using UL NAS (TS 24.501).

[0081] In additional or alternative examples, the LMF can obtain multiple bits from the UE where the UE capability or indication is separated in different information elements (“IES”). A first IE can indicate a capability of the UE to acquire and decode cipher posSIB. The first IE can imply that the UE has the right subscription to obtain the ciphering keys. A second IE can indicate a capability to acquire and decode only non-cipher keys. The second IE can imply that the UE is only able to retrieve non-ciphered posSIBs.

[0082] In some embodiments, UE broadcast capability and encryption status is included in a MO-LR indication (e.g., the MO-LR sequence described in 23.273). The information can be included either in the MO-LR supplementary service message or embedded in LPP capability, assistance data request message or part of UL NAS message. In some examples, the MO-LR is carried over NAS and MO-LR message can embed up to 3 LPP message.

[0083] In some embodiments, LMF determines the UE broadcast subscription capability from the existing broadcast subscription information that may be available in MO-LR message. The LMF may count such request for a certain time duration and if it is above certain threshold, LMF may determine to enable broadcast instead of unicast. The LMF may further determine the LPP signaling load (the processing load) and consider this as well while enabling / disabling the broadcast service. The LMF may enable / disable broadcast service by sending to RAN nodes start / stop indication using NRPPa protocol.

[0084] FIG. 10 illustrates an example of UE broadcast capabilities being communicated to a LMF according to some embodiments.

[0085] At block 1030, the LMF determines whether the number of UEs supporting broadcast in a cell is above a threshold. If so, at block 1040, the LMF starts to send positioningP110433W001 assistance data to a gNB in Assistance Information Control. At block 1050, the gNB provides the positioning assistance data to the UE via broadcasted system information.

[0086] FIG. 11 illustrates a second example of UE broadcast capabilities being communicated to the LMF. In this example, the UE broadcast capability and encryption status is send in LPP RequestAssistanceData.

[0087] In some embodiments, the MO-LR requests can be served by different LMFs in the same area since LMF selection happens at AMF. There must be a solution when dedicated LMF responsible broadcast aware of all MO-LR requests in the same tracking area. In some examples, in such case one LMF may be assigned to pull the number of MO-LR request for RTK assistance data. The Network repository function (NRF) may inform to the LMF which other LMFs are available / operational in the same area. Such LMF (pulling the numbers) may poll other LMF and retrieve the number and when the number reaches “N” within certain time T, this LMF may decide to enable broadcast for duration “D” and inform other LMFs. In additional or alternative examples, Network can be configured by operator using NF profiles by the way AMF select dedicated LMFs which responsible for MO-LRs requesting assisted data only and responsible for broadcasting assisted data. In this way always dedicated LMF would be responsible for broadcasting AD and serving MO-LR requests which required only ADs.

[0088] In additional or alternative embodiments, it is also possible that LMF retrieves the UE subscription about the support of broadcast information via UDM / AMF whenever UE requests RTK AD.

[0089] In additional or alternative embodiments, “N”, “D”, “T” can be determined by AI / ML model NWDAF (Network Data Analytics Function).

[0090] In additional or alternative embodiments, the legacy MOLR-Type is extended below to include “capableOfReceivingBroadcastRTK (13) and rtk(6).MOLR-Type: := ENUMERATED { locationEstimate (0), assistanceData (1), deCipheringKeys (2),• • • 5 deferredMo-lrTTTPInitiation (3), deferredMo-lrSelfLocationlnitiation (4), deferredMt-lrOrmo-lrTTTPLocationEstimate (5), deferredMt-lrOrmo-lrCancellation (6), periodicEvent (7),P110433W001 enteringAreaEvent (8), leavingAreaEvent (9), beinglnsideAreaEvent (10), motionEvent (11), maximumlntervalExpirationEvent (12), capableOfReceivingBroadcastRTK (13) }— exception handling:— an unrecognized value shall be rejected by the receiver with a return error cause of— unexpected data value.— For E-UTRAN access, only locationEstimate, assistanceData, periodicEvent, deferredMt-lrOrmo-lrCancellation, enteringAreaEvent, leavingAreaEvent, beinglnsideAreaEvent,— motionEvent or maximumlntervalExpirationEvent shall be includedLocationMethod::= ENUMERATED { msBasedEOTD (0), msAssistedEOTD (1), assistedGPS (2), msBasedOTDOA (3), assistedGANSS (4), assistedGPSandGANSS (5), rtk(6) }

[0091] Operations of the communication device 1600 (implemented using the structure of FIG. 16) will now be discussed with reference to the flow chart of FIG. 12 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1610 of FIG. 16, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 1602, communication device 1600 performs respective operations of the flow chart.

[0092] FIG. 12 illustrates an example of operations performed by a communication device.

[0093] At block 1210, processing circuitry 1602 generates a message including an indication of whether the communication device requests the positioning assistance data broadcast by the communications network. In some examples, the indication of whether theP110433W001 communication device requests the positioning assistance data comprises an indication that the communication device requires the positioning assistance data. In additional or alternative examples, the indication of whether the communication device requests the positioning assistance data comprises an indication that the communication device has a subscription to receive the positioning assistance data from the LMF.

[0094] In some embodiments, generating the message includes generating a location service, LCS, message including an information element indicating whether the communication device requests the positioning assistance data broadcast by the communications network. In some examples, the LCS message includes a mobile origination location request, MO-LR.

[0095] In additional or alternative embodiments, generating the message includes generating a non-access stratum, NAS, message including the indication of whether the communication device requests the positioning assistance data broadcast by the communications network.

[0096] In additional or alternative embodiments, generating the message includes a long term evolution positioning protocol, LPP, including the indication of whether the communication device requests the positioning assistance data broadcast by the communications network.

[0097] In additional or alternative embodiments, generating the message further includes generating the message including an indication of whether the communication device supports (or requests) ciphered positioning assistance data.

[0098] At block 1220, processing circuitry 1602 transmits, via communication interface 1612, the message to a LMF of the communications network.

[0099] In some embodiments, transmitting the message to the LMF includes transmitting the message to the LMF via an access and mobility management function, AMF.

[0100] At block 1230, processing circuitry 1602 receives, via communication interface 1612, the positioning assistance data via system information broadcast by the communications network. In some embodiments, the indication of whether the communication device requests the positioning assistance data via broadcast from the communications network includes an indication that the communication device requests the positioning assistance data via broadcast.

[0101] Various operations from the flow chart of FIG. 12 may be optional with respect to some embodiments of communication devices and related methods.

[0102] Operations of the network node 1700 (implemented using the structure of FIG. 17) will now be discussed with reference to the flow charts of FIGS. 13-14 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1704 ofP110433W001FIG. 17, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1702, network node 1700 performs respective operations of the flow charts.

[0103] FIG. 13 illustrates an example of operations performed by a network node (e.g., a network node configured to provide a LMF). In some embodiments, the network node is a core network, CN, node configured to provide a location management function, LMF.

[0104] At block 1310, processing circuitry 1702 receives, via communication interface 1706, an indication of whether a communication device requests the positioning assistance data via broadcast from the communications network. In some examples, the indication of whether the communication device requests the positioning assistance data comprises an indication that the communication device requires the positioning assistance data. In additional or alternative examples, the indication of whether the communication device requests the positioning assistance data comprises an indication that the communication device has a subscription to receive the positioning assistance data from the LMF. In additional or alternative examples, the indication of whether the communication device requests the positioning assistance data comprises an indication of whether the communication device is capable of receiving the positioning assistance data via broadcast from the communications network.

[0105] In some embodiments, the communication device further receives an indication of whether the UE supports ciphered positioning assistance data.

[0106] In additional or alternative embodiments, the network node is a first LMF. Receiving the indication of whether the communication device requests the positioning assistance data via broadcast from the communications network includes receiving a message from a second LMF, the message including the indication of whether the communication device requests the positioning assistance data via broadcast from the communications network.

[0107] In additional or alternative embodiments, receiving the indication of whether the communication device requests the positioning assistance data via broadcast from the communications network includes receiving a location services, LCS, message from the communication device via an access mobility and management, AMF, the LCS message.

[0108] In additional or alternative embodiments, receiving the indication of whether the communication device requests the positioning assistance data via broadcast from the communications network includes receiving a long term evolution positioning protocol, LPP, including an indication of whether the communication device requests the positioning assistance data via a broadcast signal from the communication network.P110433W001

[0109] At block 1320, processing circuitry 1702 determines whether to broadcast the positioning assistance data based on the indication of whether the communication device requests the positioning assistance data via broadcast from the communications network. In some embodiments, the communication device is a first communication device of a plurality of communication devices in a specific region. Receiving the indication includes receiving a plurality of indications that each indicate whether a communication device of the plurality of communication devices requests the positioning assistance data via broadcast from the communications network and / or an indication of whether a communication device of the plurality of communication devices is capable of receiving (or requests) ciphered positioning assistance data. Determining whether to broadcast the positioning assistance data includes: determining a number of communication devices of the plurality of communication devices that requests the positioning assistance data via broadcast from the communications network and / or are capable of receiving ciphered positioning assistance data; and determining whether to broadcast the positioning assistance data based on the number of communication devices that requests the positioning assistance data via broadcast from the communications network and / or are capable of receiving ciphered positioning assistance data.

[0110] In some examples, determining the number of communication devices of the plurality of communication devices that requests the positioning assistance data via broadcast from the communications network includes determining a number of indications that a communication device requests the positioning assistance data via broadcast from the communications network received within a predetermined period of time.

[0111] In additional or alternative embodiments, the network node is a first LMF. The number of communication devices of the plurality of communication devices that requests the positioning assistance data via broadcast from the communications network is a first number of communication devices of the plurality of communication devices determined by the first LMF to request the positioning assistance data via broadcast from the communications network. Receiving the indication of whether the communication device requests the positioning assistance data via broadcast from the communications network comprises receiving a message from a second LMF, the message including an indication of a second number of communication devices of the plurality of communication devices determined by the second LMF that request the positioning assistance data via broadcast from the communications network. Determining the first number of communication devices of the plurality of communication devices determined by the first LMF that request the positioning assistance data via broadcast from the communications network comprises determining the first number of communication devices ofP110433W001 the plurality of communication devices that request the receiving positioning assistance data via broadcast from the communications network based on the second number of communication devices of the plurality of communication devices determined by the second LMF that request the positioning assistance data via broadcast from the communications network.

[0112] At block 1330, processing circuitry 1702 transmits, via communication interface 1706, an assistance information control message to a radio access network, RAN, node associated with the communication device, the assistance information control message including an indication of the positioning assistance data and instructions to broadcast system information including the positioning assistance data. In some embodiments, determining whether to broadcast the positioning assistance data includes determining to broadcast the positioning assistance data,

[0113] FIG. 14 illustrates an example of operations performed by a network node (e.g., a network node configured to provide an AMF).

[0114] At block 1410, processing circuitry 1702 receives, via communication interface 1706, a first message from a communications device, the message including an indication of whether the communication device requests the positioning assistance data via a broadcast signal from the communications network. In some examples, the indication of whether the communication device requests the positioning assistance data comprises an indication that the communication device requires the positioning assistance data. In additional or alternative examples, the indication of whether the communication device requests the positioning assistance data comprises an indication that the communication device has a subscription to receive the positioning assistance data.

[0115] At block 1420, processing circuitry 1702 selects the first LMF from the plurality of LMFs based on the identity of the communication device or the identity of the area that the communication device is located. In some embodiments, the LMF includes a first LMF of a plurality of LMFs. The first message further includes an indication of an identity of the communication device or an identity of an area that the communication device is located.

[0116] In additional or alternative embodiments, the first message is a mobile origination location request, MO-LR, including a flag indicating whether the communication device requests (or is capable of receiving) the positioning assistance data via a broadcast signal from the communications network. In additional or alternative embodiments, the first message is a non-access stratum, NAS, message.

[0117] In additional or alternative embodiments, the first message further includes a long term evolution positioning protocol, LPP, including an indication of whether the communicationP110433W001 device requests the positioning assistance data via a broadcast signal from the communication network.

[0118] At block 1430, processing circuitry 1702 transmits, via communication interface 1706, a second message to a location management function, LMF, including an indication of whether the communication device requests the positioning assistance data via a broadcast signal from the communications network. In some embodiments, transmitting the second message includes determining a type of the first message and forwarding the first message to the LMF based on the type of the first message.

[0119] Various operations from the flow charts of FIGS. 13-14 may be optional with respect to some embodiments of network nodes and related methods.

[0120] FIG. 15 shows an example of a communication system 1500 in accordance with some embodiments.

[0121] In the example, the communication system 1500 includes a telecommunication network 1502 that includes an access network 1504, such as a radio access network (RAN), and a core network 1506, which includes one or more core network nodes 1508. The access network 1504 includes one or more access network nodes, such as network nodes 1510a and 1510b (one or more of which may be generally referred to as network nodes 1510), or any other similar 3rd Generation Partnership Project (3 GPP) access node or non-3GPP access point. Moreover, as will be appreciated by those of skill in the art, the network nodes 1510 are 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 the network nodes 1510 may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1502 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 1502, including one or more network nodes 1510 and / or core network nodes 1508.

[0122] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time RAN control application (e.g., xApp) or a non-real time RAN automation application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network nodeP110433W001 may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Intents and content-aware notifications described herein may be communicated from a 3 GPP network node or an ORAN network node over 3GPP-defined interfaces (e.g., N2, N3) and / or ORAN Alliance-defined interfaces (e.g., Al, 01). Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance. The network nodes 1510 facilitate direct or indirect connection of user equipment (UE), such as by connecting wireless devices 1512a, 1512b, 1512c, and 1512d (one or more of which may be generally referred to as UEs 1512) to the core network 1506 over one or more wireless connections. The network nodes 1510 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1512a, 1512b, 1512c, and 1512d (one or more of which may be generally referred to as UEs 1512) to the core network 1506 over one or more wireless connections.

[0123] 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 1500 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 1500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0124] The UEs 1512 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 1510 and other communication devices. Similarly, the network nodes 1510 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1512 and / or with other network nodes or equipment in the telecommunication network 1502 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 1502.P110433W001

[0125] In the depicted example, the core network 1506 connects the network nodes 1510 to one or more hosts, such as host 1516. 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 1506 includes one more core network nodes (e.g., core network node 1508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1508. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0126] The host 1516 may be under the ownership or control of a service provider other than an operator or provider of the access network 1504 and / or the telecommunication network 1502, and may be operated by the service provider or on behalf of the service provider. The host 1516 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.

[0127] As a whole, the communication system 1500 of FIG. 15 enables connectivity between the 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 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 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.P110433W001

[0128] In some examples, the telecommunication network 1502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1502. For example, the telecommunications network 1502 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.

[0129] In some examples, the UEs 1512 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 1504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1504. Additionally, a UE may be configured for operating in single- or multi -RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0130] In the example, the hub 1514 communicates with the access network 1504 to facilitate indirect communication between one or more UEs (e.g., UE 1512c and / or 1512d) and network nodes (e.g., network node 1510b). In some examples, the hub 1514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1514 may be a broadband router enabling access to the core network 1506 for the UEs. As another example, the hub 1514 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 1510, or by executable code, script, process, or other instructions in the hub 1514. As another example, the hub 1514 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 1514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1514 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0131] The hub 1514 may have a constant / persistent or intermittent connection to the network node 1510b. The hub 1514 may also allow for a different communication schemeP110433W001 and / or schedule between the hub 1514 and UEs (e.g., UE 1512c and / or 1512d), and between the hub 1514 and the core network 1506. In other examples, the hub 1514 is connected to the core network 1506 and / or one or more UEs via a wired connection. Moreover, the hub 1514 may be configured to connect to an M2M service provider over the access network 1504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1510 while still connected via the hub 1514 via a wired or wireless connection. In some embodiments, the hub 1514 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 1510b. In other embodiments, the hub 1514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1510b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0132] FIG. 16 shows a UE 1600 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0134] The UE 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input / output interface 1606, a power source 1608, a memory 1610, a communication interface 1612, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 16. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

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

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

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

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

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

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

[0142] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1612, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

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

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

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

[0147] FIG. 17 shows a network node 1700 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs,P110433W001 evolved Node Bs (eNBs), NR NodeBs (gNBs)), O-RAN nodes, or components of an O-RAN node (e.g., intelligent controller, O-RU, O-DU, O-CU).

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

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

[0150] The network node 1700 includes a processing circuitry 1702, a memory 1704, a communication interface 1706, and a power source 1708. The network node 1700 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1700 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1704 for different RATs) and some components may be reused (e.g., a same antenna 1710 may be shared by different RATs). The network node 1700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) orP110433W001Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1700.

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

[0152] In some embodiments, the processing circuitry 1702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1702 includes one or more of radio frequency (RF) transceiver circuitry 1712 and baseband processing circuitry 1714. In some embodiments, the radio frequency (RF) transceiver circuitry 1712 and the baseband processing circuitry 1714 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 1712 and baseband processing circuitry 1714 may be on the same chip or set of chips, boards, or units.

[0153] The memory 1704 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 1702. The memory 1704 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 1702 and utilized by the network node 1700. The memory 1704 may be used to store any calculations made by the processing circuitry 1702 and / or any data received via the communication interface 1706. In some embodiments, the processing circuitry 1702 and memory 1704 is integrated.

[0154] The communication interface 1706 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1706 comprises port(s) / terminal(s) 1716 to send and receive data, for example to and from a network over a wired connection. The communication interface 1706 also includes radio front-end circuitry 1718 that may be coupled to, or in certain embodiments a part of, the antenna 1710. Radio front-end circuitry 1718 comprises filters 1720 and amplifiers 1722.P110433W001The radio front-end circuitry 1718 may be connected to an antenna 1710 and processing circuitry 1702. The radio front-end circuitry may be configured to condition signals communicated between antenna 1710 and processing circuitry 1702. The radio front-end circuitry 1718 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 1718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1720 and / or amplifiers 1722. The radio signal may then be transmitted via the antenna 1710. Similarly, when receiving data, the antenna 1710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1718. The digital data may be passed to the processing circuitry 1702. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0155] In certain alternative embodiments, the network node 1700 does not include separate radio front-end circuitry 1718, instead, the processing circuitry 1702 includes radio front-end circuitry and is connected to the antenna 1710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1712 is part of the communication interface 1706. In still other embodiments, the communication interface 1706 includes one or more ports or terminals 1716, the radio front-end circuitry 1718, and the RF transceiver circuitry 1712, as part of a radio unit (not shown), and the communication interface 1706 communicates with the baseband processing circuitry 1714, which is part of a digital unit (not shown).

[0156] The antenna 1710 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1710 may be coupled to the radio front-end circuitry 1718 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1710 is separate from the network node 1700 and connectable to the network node 1700 through an interface or port.

[0157] The antenna 1710, communication interface 1706, and / or the processing circuitry 1702 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1710, the communication interface 1706, and / or the processing circuitry 1702 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0158] The power source 1708 provides power to the various components of network node 1700 in a form suitable for the respective components (e.g., at a voltage and current level neededP110433W001 for each respective component). The power source 1708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1700 with power for performing the functionality described herein. For example, the network node 1700 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 1708. As a further example, the power source 1708 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.

[0159] Embodiments of the network node 1700 may include additional components beyond those shown in FIG. 17 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 1700 may include user interface equipment to allow input of information into the network node 1700 and to allow output of information from the network node 1700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1700.

[0160] FIG. 18 is a block diagram of a host 1800, which may be an embodiment of the host 1516 of FIG. 15, in accordance with various aspects described herein. As used herein, the host 1800 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1800 may provide one or more services to one or more UEs.

[0161] The host 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input / output interface 1806, a network interface 1808, a power source 1810, and a memory 1812. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGS. 16 and 17, such that the descriptions thereof are generally applicable to the corresponding components of host 1800.

[0162] The memory 1812 may include one or more computer programs including one or more host application programs 1814 and data 1816, which may include user data, e.g., data generated by a UE for the host 1800 or data generated by the host 1800 for a UE. Embodiments of the host 1800 may utilize only a subset or all of the components shown. The host application programs 1814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC),P110433W001Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1814 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1800 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1814 may support various protocols, such as the HTTP Live Streaming (EILS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0163] FIG. 19 is a block diagram illustrating a virtualization environment 1900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the 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 1900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

[0165] Hardware 1904 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 1906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1908a and 1908bP110433W001(one or more of which may be generally referred to as VMs 1908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1906 may present a virtual operating platform that appears like networking hardware to the VMs 1908.

[0166] The VMs 1908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1906. Different embodiments of the instance of a virtual appliance 1902 may be implemented on one or more of VMs 1908, 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.

[0167] In the context of NFV, a VM 1908 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 1908, and that part of hardware 1904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1908 on top of the hardware 1904 and corresponds to the application 1902.

[0168] Hardware 1904 may be implemented in a standalone network node with generic or specific components. Hardware 1904 may implement some functions via virtualization.Alternatively, hardware 1904 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 1910, which, among others, oversees lifecycle management of applications 1902. In some embodiments, hardware 1904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1912 which may alternatively be used for communication between hardware nodes and radio units.

[0169] FIG. 20 shows a communication diagram of a host 2002 communicating via a network node 2004 with a UE 2006 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of theP110433W001UE (such as a UE 1512a of FIG. 15 and / or UE 1600 of FIG. 16), network node (such as network node 1510a of FIG. 15 and / or network node 1700 of FIG. 17), and host (such as host 1516 of FIG. 15 and / or host 1800 of FIG. 18) discussed in the preceding paragraphs will now be described with reference to FIG. 20.

[0170] Like host 1800, embodiments of host 2002 include hardware, such as a communication interface, processing circuitry, and memory. The host 2002 also includes software, which is stored in or accessible by the host 2002 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 2006 connecting via an over-the-top (OTT) connection 2050 extending between the UE 2006 and host 2002. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2050.

[0171] The network node 2004 includes hardware enabling it to communicate with the host 2002 and UE 2006. The connection 2060 may be direct or pass through a core network (like core network 1506 of FIG. 15) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0172] The UE 2006 includes hardware and software, which is stored in or accessible by UE 2006 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2006 with the support of the host 2002. In the host 2002, an executing host application may communicate with the executing client application via the OTT connection 2050 terminating at the UE 2006 and host 2002. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 2050 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 2050.

[0173] The OTT connection 2050 may extend via a connection 2060 between the host 2002 and the network node 2004 and via a wireless connection 2070 between the network node 2004 and the UE 2006 to provide the connection between the host 2002 and the UE 2006. The connection 2060 and wireless connection 2070, over which the OTT connection 2050 may be provided, have been drawn abstractly to illustrate the communication between the host 2002 and the UE 2006 via the network node 2004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.P110433W001

[0174] As an example of transmitting data via the OTT connection 2050, in step 2008, the host 2002 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 2006. In other embodiments, the user data is associated with a UE 2006 that shares data with the host 2002 without explicit human interaction. In step 2010, the host 2002 initiates a transmission carrying the user data towards the UE 2006. The host 2002 may initiate the transmission responsive to a request transmitted by the UE 2006. The request may be caused by human interaction with the UE 2006 or by operation of the client application executing on the UE 2006. The transmission may pass via the network node 2004, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2012, the network node 2004 transmits to the UE 2006 the user data that was carried in the transmission that the host 2002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2014, the UE 2006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2006 associated with the host application executed by the host 2002.

[0175] In some examples, the UE 2006 executes a client application which provides user data to the host 2002. The user data may be provided in reaction or response to the data received from the host 2002. Accordingly, in step 2016, the UE 2006 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 2006. Regardless of the specific manner in which the user data was provided, the UE 2006 initiates, in step 2018, transmission of the user data towards the host 2002 via the network node 2004. In step 2020, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2004 receives user data from the UE 2006 and initiates transmission of the received user data towards the host 2002. In step 2022, the host 2002 receives the user data carried in the transmission initiated by the UE 2006.

[0176] One or more of the various embodiments improve the performance of OTT services provided to the UE 2006 using the OTT connection 2050, in which the wireless connection 2070 forms the last segment. More precisely, the teachings of these embodiments may enable energy savings and radio resource usage when positioning assistance data shall be distributed. In additional or alternative embodiments, the LMF is able to analyze whether broadcast would be suitable in an area or not. In some examples, the LMF is aware of whether there are UEs which are capable of acquiring and decoding positioning SIBs. In additional or alternative examples, the innovations can work even if an operator has enabled or disabled ciphering. The LMF canP110433W001 identify if there are enough UEs which can receive encrypted content (e.g., broadcast of encrypted content can be enabled).

[0177] In an example scenario, factory status information may be collected and analyzed by the host 2002. As another example, the host 2002 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2002 may store surveillance video uploaded by a UE. As another example, the host 2002 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 2002 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0178] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2050 between the host 2002 and UE 2006, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 2002 and / or UE 2006. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2004. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 2002. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2050 while monitoring propagation times, errors, etc.

[0179] 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 understoodP110433W001 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.

[0180] 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.

Claims

P110433W001CLAIMSWhat is claimed is:

1. A method of operating a communication device (1600) in a communications network, the method comprising: generating (1210) a message requesting positioning assistance data from a location management function, LMF; and transmitting (1220) the message to the LMF of the communications network; and receiving (1230) the positioning assistance data via broadcast from the LMF.

2. The method of Claim 1, wherein generating the message comprises generating a location service, LCS, message including an information element requesting positioning assistance data, the LCS message including a mobile origination location request, MO-LR.

3. The method of Claim 1, wherein generating the message comprises generating a non- access stratum, NAS, message requesting the positioning assistance data.

4. The method of Claim 1, wherein generating the message comprises a long term evolution positioning protocol, LPP, requesting the positioning assistance data.

5. The method of any of Claims 1-4, wherein the message requesting the positioning assistance data comprises at least one of: an indication that the communication device requires the positioning assistance data; and an indication that the communication device has a subscription to receive the positioning assistance data from the LMF.

6. The method of any of Claims 1-5, wherein transmitting the message to the LMF comprises transmitting the message to the LMF via an access and mobility management function, AMF.P110433W0017. The method of any of Claims 1-6, wherein generating the message further comprises generating the message including an indication of whether the communication device supports ciphered positioning assistance data.

8. The method of any of Claims 1-7, wherein the message requesting the positioning assistance comprises an indication that the communication device is capable of receiving the positioning assistance data via broadcast, and wherein receiving the positioning assistance data comprises receiving the positioning assistance data via system information broadcast by the communications network.

9. A method of operating a network node (1700) in a communications network, the method comprising: receiving (1310) a message requesting positioning assistance data be provided to a communication device; and determining (1320) whether to broadcast the positioning assistance data based on the message requesting the positioning assistance data.

10. The method of Claim 9, wherein the message requesting the positioning assistance data comprises at least one of: an indication that the communication device requires the positioning assistance data; and an indication that the communication device has a subscription to receive the positioning assistance data from the communications network.

11. The method of any of Claims 9-10, further comprising: receiving (1310) an indication of whether the communication device is capable of using ciphered positioning assistance data.

12. The method of any of Claims 9-11, wherein the network node is a core network, CN, node configured to provide a location management function, LMF.

13. The method of Claim 12, wherein the LMF is a first LMF, and wherein receiving the message requesting the positioning assistance data comprises receiving the message from a second LMF indicating that the communication device requests the positioning assistance data.P110433W00114. The method of any of Claims 9-13, wherein the communication device is a first communication device of a plurality of communication devices in a specific region, wherein receiving the message comprises receiving one or more indications that each indicate whether one or more communication devices of the plurality of communication devices request the positioning assistance data from the communications network and / or whether one or more communication devices of the plurality of communication devices are capable of receiving ciphered positioning assistance data, and wherein determining whether to broadcast the positioning assistance data comprises: determining a number of communication devices of the plurality of communication devices that request the positioning assistance data and / or are capable of receiving ciphered positioning assistance data; and determining whether to broadcast the positioning assistance data based on the number of communication devices that request the positioning assistance data via broadcast from the communications network and / or are capable of receiving the ciphered positioning assistance data.

15. The method of Claim 14, wherein determining the number of communication devices of the plurality of communication devices that request the positioning assistance data comprises determining a number of the communication devices that request the positioning assistance data within a predetermined period of time.

16. The method of any of Claims 14-15, wherein the message is a first message, wherein the LMF is a first LMF, wherein the number of communication devices of the plurality of communication devices that request the positioning assistance data is a first number of communication devices of the plurality of communication devices that request the positioning assistance data as determined by the first LMF, wherein receiving the message comprises receiving a second message from a second LMF, the second message including an indication of a second number of communication devices of the plurality of communication devices that request the positioning assistance data as determined by the second LMF, and wherein determining the first number of communication devices of the plurality of communication devices that request the positioning assistance data as determined by the firstP110433W001LMF comprises determining the first number of communication devices of the plurality of communication devices that request the positioning assistance data based on the second number of communication devices of the plurality of communication devices that request the positioning assistance data as determined by the second LMF.

17. The method of any of Claims 9-16, wherein receiving the message requesting the positioning assistance data comprises receiving a location services, LCS, message from the communication device, the LCS message including a mobile origination location request, MO- LR.

18. The method of any of Claims 9-16, wherein receiving the message requesting the positioning assistance data comprises receiving a long term evolution positioning protocol, LPP, message including a request for the positioning assistance data.

18. The method of any of Claims 9-17, wherein determining whether to broadcast the positioning assistance data comprises determining to broadcast the positioning assistance data, the method further comprising: transmitting (1330) an assistance information control message to a radio access network, RAN, node associated with the communication device, the assistance information control message including an indication of the positioning assistance data and instructions to broadcast system information including the positioning assistance data.

19. The method of Claim 18, wherein transmitting the assistance information control message comprises determining the positioning assistance data based on each communication device requesting the positioning assistance data.

20. A method of operating a network node (1700) in a communications network, the method comprising: receiving (1410) a first message from a communications device, the first message requesting positioning assistance data and an indication of an identity of the communication device or an identity of an area that the communication device is located; selecting (1420) a first location management function, LMF, from a plurality of LMFs based on the identity of the communication device or the identity of the area that the communication device is located; andP110433W001 transmitting (1430) a second message to the first LMF requesting the positioning assistance data be provided to the communication device.

21. The method of Claim 20, wherein the network node is configured to provide an access mobility and management function, AMF.

22. The method of any of Claims 20-21, further comprising: determining a type of the first message, wherein transmitting the second message comprises forwarding the first message to the first LMF based on the type of the first message.

23. The method of any of Claims 20-22, wherein the first message is a mobile origination location request, MO-LR, including a flag indicating that the communication device requests the positioning assistance data via a broadcast signal from the communications network.

24. The method of Claim 23, wherein the first message comprises at least one of an indication that the communication device requires the positioning assistance data; and an indication that the communication device has a subscription to receive the positioning assistance data from the communications network.

25. The method of any of Claims 20-23, wherein the first message is a non-access stratum, NAS, message.

26. The method of any of Claims 20-23, wherein the first message further includes a long term evolution positioning protocol, LPP, requesting the positioning assistance data via a broadcast signal from the communication network.

27. A communication device (1600), configured to perform any of the operations of Claims 1- 8.

28. A computer program comprising program code to be executed by processing circuitry (1602) of a communication device (1600), whereby execution of the program code causes the communication device to perform any of the operations of Claims 1-8.P110433W00129. A computer program product comprising a non-transitory storage medium (1610) including program code to be executed by processing circuitry (1602) of a communication device (1600), whereby execution of the program code causes the communication device to perform any of the operations of Claims 1-8.

30. A network node (1700) configured to perform any of the operations of Claims 9-26.

31. A computer program comprising program code to be executed by processing circuitry (1702) of a network node (1700), whereby execution of the program code causes the network node to perform any of the operations of Claims 9-26.

32. A computer program product comprising a non-transitory storage medium (1706) including program code to be executed by processing circuitry (1702) of a network node (1700), whereby execution of the program code causes the network node to perform any of the operations of Claims 9-26.

Images