Privacy handling in a communication network

Abstract

A communication device (12-1) receives a sidelink service request (18) that requests sidelink positioning or ranging of a target communication device (12T). The sidelink service request (18) identifies a client (14) to which information about a position or range (16) of the target communication device (12T) is to be provided according to the sidelink service request (18). The communication device (12-1) obtains a privacy profile (22) governing the communication device (12-1). The communication device (12-1) performs privacy verification to determine whether or not the privacy profile (22) allows information about a location (20) of the communication device (12-1) to be exposed to the client (14). The communication device (12-1) handles the sidelink service request (18) based on a result of the privacy verification.

Description

[0001] PRIVACY HANDLING IN A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] The present application relates generally to a communication network, and relates more particularly to privacy handling in such a network.

[0004] BACKGROUND

[0005] Positioning in a communication network aims to estimate the geographical position of a so-called target communication device that is the target of the positioning. Positioning traditionally relies on measurement of downlink and / or uplink signals transmitted between the target communication device and one or more radio network nodes. The introduction of a sidelink as a direct communication interface between communication devices, with a communication path that does not traverse any network node, not only improves performance by reducing communication latency but also provides an opportunity for another approach to positioning. Sidelink positioning in this regard exploits measurement of signals transmitted on a sidelink between peer communication devices in proximity. The position of the target communication device may for instance be determined relative to the position of one or more peer communication devices that serve as a reference for the positioning. In these and other cases, the location of one or more reference communication device may be used to deduce the position of the target communication device. Sidelink positioning may thereby extend positioning even to communication devices outside of network coverage and / or supplement traditional positioning so as to improve positioning reliability. Similarly, sidelink ranging aims to determine a distance or range between peer communication devices by measuring signals transmitted on the sidelink between those devices.

[0006] Challenges exist in exploiting the sidelink for positioning and / or ranging, though. The nature of sidelink positioning and / or ranging threatens the privacy of user’s information. For example, information about the location of a reference communication device may be indirectly or tangentially revealed when reporting the position and / or range of the target communication device to a client. And existing approaches tailored for the traditional positioning paradigm prove inadequate in safeguarding privacy for sidelink positioning and / or ranging. In these and other contexts, then, a need remains for improving privacy protection in a communication network.

[0007] SUMMARY

[0008] An object of some embodiments herein is to enable improvement to privacy protection in a communication network.

[0009] Some embodiments herein protect the privacy of information about the location of a communication device in a communication network. Some embodiments in this regard protect against this location information being exposed and / or used without the communication device owner’s consent, e.g., even in a context such as sidelink positioning and / or ranging where such exposure and / or use may be only indirect or tangential. One or more embodiments for example introduce, into a sidelink service request and / or location request, signaling that indicates a party (e.g., client) to which location information is to be exposed and / or indicates a purpose for which the location information is to be used. This way, the recipient of the request can verify that accepting the request complies with a governing privacy policy. These and other embodiments may thereby advantageously improve privacy protection in a communication network.

[0010] More particularly with regard to sidelink positioning and / or ranging, embodiments herein include a method performed by a communication device. The method comprises receiving a sidelink service request that requests sidelink positioning or ranging of a target communication device and that identifies a client to which information about a position or range of the target communication device is to be provided according to the sidelink service request. The method also includes obtaining a privacy profile governing the communication device. The method further comprises performing privacy verification to determine whether or not the privacy profile allows information about a location of the communication device to be exposed to the client. The method also comprises handling the sidelink service request based on a result of the privacy verification.

[0011] In some embodiments, said handling comprises, if the privacy verification fails based on the privacy profile not allowing information about a location of the communication device to be exposed to the client, rejecting the sidelink service request.

[0012] In some embodiments, said handling comprises, if the privacy verification passes based on the privacy profile allowing information about a location of the communication device to be exposed to the client, transmitting a response to the sidelink service request, wherein the response reveals information about the location of the communication device. In one embodiment, the response includes information about the position or range of the target communication device, wherein the information about the position or range of the target communication device reveals information about the location of the communication device.

[0013] In some embodiments, said handling comprises, if the privacy check passes based on the privacy profile allowing information about a location of the communication device to be exposed to the identified client, performing a sidelink positioning or ranging operation to determine, or assist with determining, information about a position or range of the target communication device.

[0014] In some embodiments, said handling comprises, if the privacy check passes based on the privacy profile allowing information about a location of the communication device to be exposed to the identified client, transmitting the sidelink service request to another communication device or to a network node in a communication network. In this case, the transmitted sidelink service request identifies the client to which the position or range of the target communication device is to be provided and / or to which the information about a location of the communication device is to be exposed. Alternatively or additionally, in some embodiments, said handling comprises, if the privacy check passes based on the privacy profile allowing information about a location of the communication device to be exposed to the identified client, transmitting a location request to a network node in a communication network. In this case, the location request requests a location of the communication device, wherein the location request identifies the client to which the position or range of the target communication device is to be provided and / or to which the information about a location of the communication device is to be exposed. In one embodiment, the transmitted sidelink service request and / or the location request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0015] In some embodiments, the received sidelink service request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0016] In some embodiments, the sidelink service request is received from the client, another communication device that selects the communication device as a positioning server for the sidelink service request, or a positioning server for the sidelink service request.

[0017] In some embodiments, the sidelink service request is received at a sidelink positioning or ranging layer of a protocol stack at the communication device and / or is handled as application layer traffic by the communication device.

[0018] In some embodiments, the sidelink service request is received over a sidelink with the client or with another communication device.

[0019] In some embodiments, the communication device is the target communication device. In one embodiment, the sidelink service request is received from a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0020] In some embodiments, the communication device is a reference communication device that is to support sidelink positioning or ranging of the target communication device. In one embodiment, the sidelink service request is received from the target communication device.

[0021] In some embodiments, the communication device serves as a sidelink positioning server for the sidelink service request.

[0022] In some embodiments, the client is a communication device and is a sidelink positioning client for the sidelink service request.

[0023] In some embodiments, the privacy profile comprises locally configured privacy verification information.

[0024] In some embodiments, the sidelink service request is received from the target communication device or from a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0025] In some embodiments, the network node implements an access and mobility function or a location management function.

[0026] Other embodiments herein include a method performed by a communication device. The method comprises receiving a sidelink service request that requests sidelink positioning or ranging of a target communication device and that identifies a client to which information about a position or range of the target communication device is to be provided according to the sidelink service request. The method also comprises transmitting a message to another communication device or to a network node in a communication network, wherein the message identifies the client to which the position or range of the target communication device is to be provided and / or to which information about a location of the communication device is to be exposed.

[0027] In some embodiments, the message is transmitted to another communication device.

[0028] In some embodiments, the message is a sidelink service request that requests sidelink positioning or ranging of the target communication device and / or of the communication device

[0029] In some embodiments, the communication device is the target communication device or a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0030] In some embodiments, the another communication device is the target communication device or a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0031] In some embodiments, the method further comprises selecting the another communication device to serve as a sidelink positioning server for sidelink service request.

[0032] In some embodiments, the message is transmitted to the network node.

[0033] In some embodiments, the message is a location request that requests a location of the communication device.

[0034] In some embodiments, wherein the sidelink service request and / or the message includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0035] In some embodiments, the sidelink service request is received from the client, another communication device that selects the communication device as a positioning server for the sidelink service request, or a positioning server for the sidelink service request.

[0036] In some embodiments, the sidelink service request is received at a sidelink positioning or ranging layer of a protocol stack at the communication device and / or is handled as application layer traffic by the communication device.

[0037] In some embodiments, the sidelink service request is received over a sidelink with the client or with another communication device.

[0038] In some embodiments, the client is a communication device and is a sidelink positioning client for the sidelink service request.

[0039] In some embodiments, the method further comprises obtaining a privacy profile governing the communication device and performing privacy verification to determine whether or not the privacy profile allows information about a location of the communication device to be exposed to the client, wherein the privacy verification passes based on the privacy profile allowing information about a location of the communication device to be exposed to the client, and wherein the message is transmitted based on the privacy verification passing.

[0040] In some embodiments, the method further comprises obtaining information about the position or range of the target communication device, wherein the information about the position or range of the target communication device reveals information about the location of the communication device. The method in this case also comprises transmitting the obtained information in a response to the sidelink service request. In one embodiment, said obtaining comprises performing a sidelink positioning or ranging operation to determine, or assist with determining, the information about a position or range of the target communication device.

[0041] In some embodiments, the communication device serves as a sidelink positioning server for the sidelink service request.

[0042] In some embodiments, the network node implements an access and mobility function or a location management function.

[0043] Other embodiments herein include a method performed by a communication device. The method includes receiving, from another communication device, a message that identifies a client to which information about a position or range of a target communication device is to be provided and / or to which information about a location of the communication device is to be exposed. The method also includes obtaining a privacy profile governing the communication device. The method further comprises performing privacy verification to determine whether or not the privacy profile allows information about a location of the communication device to be exposed to the client. The method also comprises handling the message based on a result of the privacy verification. Such handling may for example comprise transmitting a response to the message based on a result of the privacy verification, e.g., where the response indicates the result of the privacy verification.

[0044] In some embodiments, said handling comprises, if the privacy verification passes based on the privacy profile allowing information about a location of the communication device to be exposed to the client, performing a sidelink positioning or ranging operation to determine, or assist with determining, information about a position or range of the target communication device.

[0045] In some embodiments, the received message includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0046] In some embodiments, the message is received at a sidelink positioning or ranging layer of a protocol stack at the communication device and / or is handled as application layer traffic by the communication device.

[0047] In some embodiments, the message is received over a sidelink with the another communication device.

[0048] In some embodiments, the another communication device is a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0049] In some embodiments, the privacy profile comprises locally configured privacy verification information.

[0050] Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs.

[0051] BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 is a block diagram of communication devices and a communication network according to some embodiments.

[0053] Figure 2 is a block diagram of a non-roaming reference architecture for Location Services with ranging and Sidelink positioning in reference point representation.

[0054] Figure 3 is a call flow diagram for service exposure to SL Positioning Client UE via PC5 according to some embodiments.

[0055] Figure 4 shows block diagrams of interactions for Ranging / SL positioning service exposure through PC5 according to some embodiments.

[0056] Figure 5 is a call flow diagram for Ranging / SL positioning service exposure through PC5 according to some embodiments.

[0057] Figure 6 is a logic flow diagram of a method performed by a communication device according to some embodiments.

[0058] Figure 7A is a logic flow diagram of a method performed by a communication device according to other embodiments.

[0059] Figure 7B is a logic flow diagram of a method performed by a communication device according to still other embodiments.

[0060] Figure 8 is a logic flow diagram of a method performed by a network node according to some embodiments.

[0061] Figure 9 is a logic flow diagram of a method performed by a network node according to other embodiments.

[0062] Figure 10 is a block diagram of a communication device according to some embodiments. Figure 11 is a block diagram of a network node according to some embodiments.

[0063] Figure 12 is a block diagram of a communication system in accordance with some embodiments.

[0064] Figure 13 is a block diagram of a user equipment according to some embodiments. Figure 14 is a block diagram of a network node according to some embodiments. Figure 15 is a block diagram of a host according to some embodiments.

[0065] Figure 16 is a block diagram of a virtualization environment according to some embodiments.

[0066] Figure 17 is a block diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.

[0067] DETAILED DESCRIPTION

[0068] As shown in Figure 1 , a client 14 initiates a request for determining a position or range 16 of a target communication device 12T, e.g., on behalf of an application residing on the client 14 which may itself take the form of a communication device. The client 14 in particular initiates a sidelink (SL) service request 18 for determining the position or range of the target communication device 12T using sidelink positioning or ranging. The client 14 transmits this sidelink service request 18 to or towards communication device 12-1 , e.g., at a sidelink positioning or ranging layer of a protocol stack and / or as application layer traffic. In embodiments where the client 14 is itself a communication device, the sidelink service request 18 may be transmitted over a sidelink.

[0069] Communication device 12-1 may be the target communication device 12T itself. Or, communication device 12-1 may instead be a so-called reference communication device that is to support sidelink positioning or ranging of the target communication device 12T, e.g., by transmitting and receiving reference signals for positioning, providing positioning-related information, or the like, using a sidelink between communication device 12-1 and another communication device. Communication device 12-1 may also be referred to herein as UE1 in embodiments where the communication device 12-1 is a user equipment (UE).

[0070] The SL service request 18 identifies the client 14, e.g., by including a client identity (ID) 14-ID in the SL service request 18. The SL service request 18 in particular identifies the client 14 as being the client to which information about the position or range 16 of the target communication device 12T is to be provided according to the sidelink service request 18. In one such embodiment, the SL service request 18 includes a user information field that indicates an application layer identifier of the client 14, where the application layer identifier identifies the client 14 as a sidelink positioning or ranging enabled communication device within a context of a specific application. The SL service request 18 may also include one or more other identities 19, such as an identity 19 of communication device 12-1 identifying a role of communication device 12-1 in sidelink positioning or ranging. No matter whether communication device 12-1 is the target communication device 12T or a reference communication device for sidelink positioning or ranging, accepting the SL service request 18 and thereby supporting sidelink positioning or ranging of the target communication device 12T risks exposing or revealing information about a location 20 of communication device 12-1 . Indeed, if communication device 12-1 is a reference communication device in sidelink positioning or ranging, the position or range 16 of the target communication device 12T is indicative or suggestive of the location 20 of communication device 12-1 , since communication device 12-1 must be located nearby to support sidelink positioning or ranging.

[0071] According to some embodiments, then, communication device 12-1 correspondingly obtains a privacy profile 22 governing communication device 12-1 . The privacy profile 22 may for example govern what information a user of the communication device 12-1 has consented to share, to whom the user has consented to share that information, and / or for what purpose the user has consented to share that information. In one embodiment, this privacy profile 22 is locally configured or stored at communication device 12-1 , e.g., as locally configured privacy verification information. Regardless, in possession of this privacy profile 22, communication device 12-1 performs privacy verification to determine whether or not the privacy profile 22 allows information about the location 20 of communication device 12-1 to be exposed to the client 14 identified in the SL service request 18. Communication device 12-1 handles the SL service request 18 based on the result of this privacy verification.

[0072] For example, if the privacy verification fails based on the privacy profile 22 not allowing information about the location 20 of communication device 12-1 to be exposed to the client 14, communication device 12-1 rejects the sidelink service request 18. By contrast, if the privacy verification passes based on the privacy profile 22 allowing information about the location 20 of communication device 12-1 to be exposed to the client 14, communication device 12-1 may accept the SL service request 18 (assuming no other reason for rejecting applies). This may for example involve performing a sidelink positioning or ranging operation to determine, or assist with determining, information about the position or range 16 of the target communication device 12T. Alternatively or additionally, this may involve transmitting a response (not shown) to the sidelink service request 18, with the response revealing information about the location 20 of communication device 12-1 . For instance, the response may include information about the position or range 16 of the target communication device 12T, but that information about the position or range 16 of the target communication device 12T indirectly reveals information about the location 20 of the communication device 12-1 .

[0073] In some embodiments, though, communication device 12-1 cooperates with another communication device 12-2 in order to respond to the SL service request 18. In these and other embodiments, communication device 12-1 may transmit a message to communication device 12-2. Figure 1 for example shows that communication device 12-1 may transmit a SL service request 26 to communication device 12-2, e.g., over a sidelink 21 with communication device 12-2, requesting sidelink positioning or ranging of communication device 12-1 and / or target communication device 12T. In some embodiments, however, communication device 12-1 conditions its transmitting of SL service request 26 to communication device 12-2 on its own privacy verification passing, as described above.

[0074] Regardless, the SL service request 26 notably identifies the client 14 to which the position or range of the target communication device 12T is to be provided and / or to which information about a location of communication device 12-1 is to be exposed. As shown in Figure 1 , for instance, the SL service request 26 includes the client ID 14-ID from the SL service request 18 received from the client 14. The SL service request 26 may more particularly include a user information field that indicates an application layer identifier of the client 14, wherein the application layer identifier identifies the client 14 as a sidelink positioning or ranging enabled communication device within a context of a specific application. The SL service request 26 may also include the one or more IDs 19 from the SL service request 18 received from the client 14.

[0075] Identification of the client 14 in the SL service request 26 advantageously equips communication device 12-2 to be able to perform privacy verification, to protect the privacy of information about a location 30 of communication device 12-2. Indeed, in receipt of SL service request 26, communication device 12-2 may perform privacy verification in a similar way as described above for communication device 12-1. That is, communication device 12-2 obtains a privacy profile 32 governing communication device 12-2. The privacy profile 32 may for example govern what information a user of the communication device 12-2 has consented to share, to whom the user has consented to share that information, and / or for what purpose the user has consented to share that information. In one embodiment, this privacy profile 32 is locally configured or stored at communication device 12-2, e.g., as locally configured privacy verification information. Regardless, in possession of this privacy profile 32, communication device 12-2 performs privacy verification to determine whether or not the privacy profile 32 allows information about the location 30 of communication device 12-2 to be exposed to the client 14 identified in the SL service request 26. Communication device 12-2 handles the SL service request 26 based on the result of this privacy verification.

[0076] For example, if the privacy verification fails based on the privacy profile 32 not allowing information about the location 30 of communication device 12-2 to be exposed to the client 14, communication device 12-2 rejects the sidelink service request 26. By contrast, if the privacy verification passes based on the privacy profile 32 allowing information about the location 30 of communication device 12-2 to be exposed to the client 14, communication device 12-2 may accept the SL service request 26 (assuming no other reason for rejecting applies). This may for example involve performing a sidelink positioning or ranging operation to determine, or assist with determining, information about the position or range 16 of the target communication device 12T and / or the position or range 16 of communication device 12-1 . Alternatively or additionally, this may involve transmitting a response (not shown) to the sidelink service request 26, with the response revealing information about the location 30 of communication device 12-2. For instance, the response may include information about the position or range 16 of the target communication device 12T and / or communication device 12-1 , but that information indirectly reveals information about the location 30 of the communication device 12-2.

[0077] Some embodiments accordingly protect against information about the location 30 of communication device 12-2 being exposed and / or used by the client 14 without the communication device owner’s consent. This is true even in a context such as this where such exposure and / or use may be only indirect since communication device 12-1 is the entity from which communication device 12-2 receives the SL service request 26 rather than communication device 12-2 receiving a SL service request directly from the client 14 itself.

[0078] In other embodiments, communication device 12-1 alternatively or additionally cooperates with a network node 15 in a communication network 10 in order to respond to the SL service request 18 from the client 14. The network node 15 may for instance implement an access and mobility function (AMF) or a location management function (LMF), e.g., in a 5G network. In these and other embodiments, communication device 12-1 may transmit a message to the network node 15. Figure 1 for example shows that communication device 12-1 may transmit a location request 36 to network node 15, requesting a location of target communication device 12T and / or communication device 12-1. The communication device 12-1 may for example transmit the location request 36 over an uplink 23 with the network node 15 and / or in uplink non-access stratum (NAS) transport message.

[0079] Regardless, the location request 36 notably identifies the client 14 to which the position or range of the target communication device 12T is to be provided and / or to which information about a location of communication device 12-1 is to be exposed. As shown in Figure 1 , for instance, the location request 36 includes the client ID 14-ID from the SL service request 18 received from the client 14. The location request 36 may more particularly include a user information field that indicates an application layer identifier of the client 14, wherein the application layer identifier identifies the client 14 as a sidelink positioning or ranging enabled communication device within a context of a specific application. The location request 36 may also include the one or more IDs 19 from the SL service request 18 received from the client 14.

[0080] Identification of the client 14 in the location request 36 advantageously equips the network node 15 to be able to trigger and / or perform privacy verification on behalf of communication device 12-1 , to protect the privacy of information about the location 20 of communication device 12-1 . Indeed, in receipt of location request 36, the network node 15 may itself perform privacy verification in a similar way as described above for communication device 12-1. Or, the network node 15 may trigger another network node 17 (e.g., a gateway mobile location center, GMLC) to perform that privacy verification, e.g., by transmitting a request to the other network node 17 to perform the privacy verification and receiving the result of the privacy verification in a response to the request. Either way, such privacy verification may involve verifying whether or not a privacy profile 22 governing communication device 12-1 allows information about the location 20 of the communication device 12-1 to be exposed to the client 14. The privacy profile 22 may for example govern what information a user of the communication device 12-1 has consented to share, to whom the user has consented to share that information, and / or for what purpose the user has consented to share that information. The network node 15 may then handle the location request 36 based on the result of this privacy verification.

[0081] For example, if the privacy verification fails based on the privacy profile 22 not allowing information about the location 20 of communication device 12-1 to be exposed to the client 14, the network node 15 rejects the location request 36. By contrast, if the privacy verification passes based on the privacy profile 22 allowing information about the location 20 of communication device 12-1 to be exposed to the client 14, the network node 15 may accept the location request 36 (assuming no other reason for rejecting applies). This may involve transmitting a response (not shown) to the location request 36, with the response revealing information about the location 20 of communication device 12-1 .

[0082] Some embodiments accordingly protect against information about the location 20 of communication device 12-1 being exposed and / or used by the client 14 without the communication device owner’s consent. This is true even in a context such as this where such exposure and / or use may be only indirect since communication device 12-1 is the entity from which the network node 15 receives the location request 36 rather than the network node 15 receiving a location request directly from the client 14 itself.

[0083] Consider now an example of some embodiments herein as applicable for 3GPP Rel-18 Sidelink Positioing and Ranging, e.g., based on the non-roaming reference architecture shown in Figure 2 for Location Services with ranging and Sidelink positioning in reference point representation. In this example, communication device 12T is exemplified as a target user equipment (UE), communication device 12-1 is exemplified as UE1 , communication device 12-2 is exemplified as UE2, client 14 is exemplified as a Sidelink Positioning Client UE, network node 15 is exemplified as AMF or LMF, and network node 17 is exemplified as GMLC.

[0084] Some embodiments herein are exemplified using the following terminology.

[0085] Located UE: A SL Reference UE of which the location is known or is able to be known using Uu based positioning. A Located UE can be used to determine the location of a Target UE using Sidelink Positioning.

[0086] Network-based Operation: Operation of Ranging / Sidelink Positioning with the involvement of 5GC NFs for the service request handling and result calculation.

[0087] Positioning: A functionality, which detects a geographical location and optionally, velocity (of e.g., a mobile terminal).

[0088] Ranging: Refers to the determination of the distance between two UEs or more UEs and / or the direction of one UE (i.e. , Target UE) from another UE (i.e., SL Reference UE) via PC5 interface.

[0089] Ranging / SL Positioning Application Identifier: A globally unique identifier identifying a specific Ranging / SL Positioning application, which can be mapped to a V2X service type or a ProSe identifier.

[0090] Relative position: An estimate of the UE position relative to other network elements or relative to other UEs.

[0091] Relative velocity: An estimate of the UE velocity relative to another UE.

[0092] SL Reference UE: A UE supporting positioning of target UE, e.g., by transmitting and / or receiving reference signals for positioning, providing positioning-related information, etc., using Sidelink.

[0093] Sidelink Positioning: Positioning UE using PC5 to obtain absolute position, relative position, or ranging information.

[0094] SL Positioning Client UE: A third-party UE, other than SL Reference UE and Target UE, which initiates Ranging / Sidelink positioning service request on behalf of the application residing on it. Note that the SL Positioning Client UE does not have to support Ranging / Sidelink positioning capability, but a communication between the SL Positioning Client UE and SL Reference UE / Target UE has to be established, either via PC5 or via 5GC, for the transmission of the service request and the result.

[0095] SL Positioning Server UE: A UE offering method determination, assistant data distribution and / or location calculation functionalities for Sidelink Positioning and Ranging based service. It interacts with other UEs over PC5 as necessary in order to determine Ranging / SL Position method, distribute assistant data, and calculate the location of the Target UE. Target UE or SL Reference UE can act as SL Positioning Server UE if any of the functionalities is supported.

[0096] Target UE: A UE whose distance, direction, and / or position is measured with the support from one or multiple SL Reference UEs using Sidelink in the Ranging based service and Sidelink positioning.

[0097] UE-only Operation: Operation of Ranging / Sidelink Positioning in which the service request handling and result calculation are performed by UE. Note that, for UE-only Operation, the communication among UEs are over PC5.

[0098] User Info ID: The User Info ID is configured for Ranging / SL Positioning UE Discovery based on the policy of the HPLMN or via the Ranging / SL Positioning application server that allocates it.

[0099] Application Layer ID: An identifier identifying a Ranging / Sidelink Positioning-enabled UE within the context of a specific application.

[0100] Procedures for Ranging / SL Positioning service exposure through PC5

[0101] The Ranging / SL Positioning service may be exposed to an authorized SL Positioning Client UE. The Client UE can initiate the Ranging / SL Positioning service through PC5 or through the 5GC network, e.g., based on PC5 or Uu availability.

[0102] For Ranging / SL Positioning service exposure to a UE through PC5 in the following way. SL Positioning Client UE discovers one of the two or more UEs, e.g., the SL Reference UE(s) or Target UE(s), using the Ranging / SL Positioning application specific Application Layer IDs.

[0103] SL Positioning Client UE invokes the Ranging / SL Positioning service request to the discovered UE, e.g., SL Reference UE / Target UE. This is an example of SL service request 18. This request includes in the User Info field the Application Layer ID of the SL Positioning Client UE, as an example of client ID 14-ID, as well as the SL Reference UE(s) and Target UE(s), as an example of ID(s) 19. The Ranging / SL Positioning service request / response is conveyed by PC5-U and handled in the Ranging / SL Positioning layer. The signalling is handled as application layer traffic by V2X layer or 5G ProSe layer.

[0104] The UE providing the exposure service triggers the authorization of SL Positioning Client UE for the Ranging / SL Positioning service invocation, performs the Ranging / SL positioning control between SL Reference UE and Target UE, and returns the Ranging / SL positioning result to SL Positioning Client UE.

[0105] Figure 3 more particularly shows service exposure to SL Positioning Client UE via PC5 according to some embodiments.

[0106] 1. When a Ranging / SL Positioning service is triggered, SL Positioning Client UE 14 may perform discovery procedure for the Ranging / SL Positioning service. When SL positioning service is triggered, the client UE 14 tries to discover the target UE and / or a SL Reference UE. When Model B discovery used, in the Solicitation message, target UE's user info is included and role of target UE and role of SL Reference UE are indicated in the RSPP metadata. When Ranging service is triggered, the client UE tries to discover UE1 and / or UE2. When Model B discovery used, in the Solicitation message, UE1's user info and UE2's user info are included and role of target UE is indicated in the RSPP metadata. During discovery for SL positioning service, the information of SL Reference UE is acquired.

[0107] 2. If discovery procedure succeeds, the SL Positioning Client UE 14 establishes a PC5 connection with the discovered UE. 3. The SL Positioning Client UE 14 is informed of UE's status information indicating that UE has NAS connection or no NAS connection from the discovered UE(s). The SL Positioning Client UE 14 may receive list of SL Reference UE(s) from target UE over the PC5 connection.

[0108] 4. Based on UE's status information, the SL Positioning Client UE 14 down selects UE(s) to perform SL Positioning operation and select a UE (here UE1 12-1) to receive SL Positioning Service Request. The SL Positioning Client UE 14 sends a SL Positioning Service Request which includes info of SL Positioning Client UE, info of Target UE and info of SL Reference UE for SL positioning, and info of SL Positioning Client UE, info of UE1 , and info of UE2 for Ranging.

[0109] 5. Authorization check of the client UE 14 for the service request may be performed via SL Positioning Server UE or 5GC or internally by UE1 or target UE.

[0110] 6. The UE which received SL Positioning Service Request (here UE1) selects LMF or SL Positioning Server UE based on its status whether UE has NAS connection. Ranging / SL Positioning operation is performed among target UE, SL Reference UE and SL Positioning Server UE or LMF.

[0111] 7. The Ranging / SL Positioning result is provided to the SL Positioning client UE by UE1.

[0112] UE-i and Network based

[0113] For Ranging / SL Positioning service exposure to Client UE through PC5, the Ranging / SL positioning result can be obtained either with UE-only Operation or Network based Operation.

[0114] SL Positioning Client UE discovers one of the UEs, e.g., the SL Reference UE(s) or Target UE(s) and establishes PC5 connection with the discovered UE, see e.g., TS 23.586 V18.1 .0. The SL Positioning Client UE 14 then invokes the Ranging / SL Positioning service request (e.g., requesting absolute location, relative location, or ranging information) to the discovered UE. Either UE-only Operation or Network-based Operation for the Ranging / Sidelink Positioning can be then triggered based on the status whether the UE is served by NG-RAN, as described in clause 6.8 of TS 23.586 V18.1 .0.

[0115] UE-only Operation flow is otherwise defined in TS 23.586 V18.1 .0 clause 5.11 and clause 6.8. Network based Operation flow is otherwise defined in TS 23.273 V18.3.0 clause 6.20.1 SL-MO-LR or 6.20.2 5GC-MO-LR

[0116] Illustrated in Figure 4 is the simplified interactions for Ranging / SL positioning service exposure through PC5.

[0117] The Ranging / SL Positioning service can be exposed only to an authorized SL Positioning Client UE.

[0118] Privacy handling is performed to check that privacy criteria of Reference UEs and Target UE, which are involved in Ranging / SL Positioning result calculation, are met so that the Location relation information of Reference UEs and Target UEs can be shared to the Client UE. However, it is heretofore unclear when and how the privacy profile check of the Reference / Target UE is performed during procedure of Ranging / SL Positioning service exposure to Client UE through PC5.

[0119] For Ranging / SL Positioning service exposure through PC5 (i.e. clause 6.7.1 .1 of TS 23.586), the SL Positioning Client UE authorization is triggered by the Reference / Target UE during PC5 link establishment. The authorization can be performed by the network via the SLPKMF for ProSe capable UEs or by the Reference / Target UE if the authorization information is available in the UE.

[0120] However, it is heretofore unclear when and how the privacy profile check of the Reference / Target UE is performed in this case.

[0121] For example, according to clause 5.6.2.2 and 6.7.1 .1 of TS 23.586, SL Positioning Client UE discovers one of the UEs, e.g. the SL Reference UE(s) or Target UE(s) and establishes PC5 connection with the discovered UE. SL Positioning Client UE then invokes the Ranging / SL Positioning service request (e.g. requesting absolute location, relative location or ranging information) to the discovered UE. Either UE-only Operation or Network-based Operation for the Ranging / Sidelink Positioning can be then triggered based on the status whether the UE is served by NG-RAN, as described in clause 6.8 of TS 23.586.

[0122] Since Client UE triggers PC5 link establishment between Client UE and UE1 , privacy handling of UE1 for Ranging / SL Positioning to Client UE may be covered either as part of the authorization procedure of PC5 establishment or upon receiving SL service request. However, privacy handling of UE2 for Ranging / SL Positioning to Client UE cannot be covered in PC5 establishment procedure.

[0123] For UE-only Operation, the network is not involved in Ranging / Sidelink positioning. The authorization for UE privacy can be based on the local configured privacy verification information. On the other hand, PC5 link establishment between UE1 and UE2 is not necessarily associated with PC5 link establishment between Client UE and UE1 (e.g. this link could have existed). Some embodiments therefore perform UE privacy check for UE2 upon SL service request.

[0124] More particularly, for UE-only Operation, the UE1 12-1 includes in the SL service request towards UE2 12-2 with the Client UE’s user info that is received in the Ranging / SL Positioning service request from the Client UE 14. UE2 triggers UE privacy check based on the local configured privacy verification information to determine whether its location related information can be exposed to Client UE. Accordingly, the Reference UE and Target UE may each trigger UE privacy verification based on the local configuration data to determine whether its location related information can be exposed to Client UE 14. Similarly, for Network-based Operations, the Reference / Target UE includes in the SL- MO-LR towards LMF with the Client UE’s user info that is received in the Ranging / SL Positioning service request from the Client UE 14. LMF triggers a privacy check of Reference UE and Target UE towards GMLC when the SL-MO-LR is requested for Ranging / SL Positioning service exposure to the Client UE 14. The GMLC interacts with the UDM to check the UE privacy profile.

[0125] In terms of UE1 and UE2, then, for Network based Operation, upon receiving SL service request from Client UE, UE1 triggers SL-MO-LR procedure to towards LMF to obtain Ranging / SL Positioning location results of UE1 and UE2. Since SL-MO-LR is transparent NAS container information transferred between UE and LMF, the privacy check of UE1 and UE2 is then be triggered at LMF and performed by the GMLC. Thus, according to some embodiments, for Network based Operation, UE1 includes in the SL-MO-LR towards LMF with the information of Ranging / SL Positioning service exposure to Client UE 14. And LMF triggers UE privacy check to GMLC to check privacy of target UEs (UE1 and UE2).

[0126] Generally, then, in some embodiments, UE1 12-1 receives SL service request from the Client UE 14 and include the information of Ranging / SL Positioning service exposure to Client UE 14 (e.g., Client UEs user info) in (i) the SL service request towards UE2 12-2 for UE-only Operation; or (ii) the SL-MO-LR request towards AMF / LMF for Network-based Operation. In the first case, based on receiving the SL service request with the information of Ranging / SL Positioning service exposure to Client UE 14 from UE1 12-1 for UE-only Operation, UE2 12-2 performs privacy verification based on the local configuration data to determine whether its location related information can be exposed to Client UE 14. In the second case, based on receiving the SL-MO-LR (or 5GC-MO-LR) request with the information of Ranging / SL Positioning service exposure to Client UE 14 from UE1 12-1 for Network-based Operation, LMF (or AMF) 15 triggers privacy check of Reference UE and Target UE towards GMLC 17.

[0127] Based on the result of the privacy check, UE1 12-1 continues the procedure of Ranging / SL Positioning service exposure to Client UE 14.

[0128] Certain embodiments may advantageously provide solutions for missing privacy handling of target / reference UEs for Ranging / SL Positioning service exposure to the Client UE 14.

[0129] Figure 5 shows additional details for Ranging / SL positioning service exposure through PC5 according to some embodiments.

[0130] Stepl . Client UE 14 sends SL Positioning Service Request which includes info of SL Positioning Client UE 14, info of Target UE, and info of SL Reference UE (e.g., User info or UE ID of Client UE / UE1 / UE2) to request Ranging / SL positioning result, e.g., absolute location, relative location, or ranging information of UE1 / UE2. Note: Target / Reference UEs are shown as UE1 and UE2 in the flow; more UEs can be included in the request e.g., UE1 / ... / UEn. These UEs perform similarly as UE2 is omitted for brevity.

[0131] Either UE-only Operation or Network-based Operation for the Ranging / Sidelink Positioning can be then triggered e.g., based on the status whether the UE is served by NG- RAN.

[0132] Option A, UE-Only operation

[0133] Step2a. UE1 12-1 triggers UE a privacy check based on the local configured privacy verification information to determine whether its location related information can be exposed to the Client UE 14.

[0134] Step3a. When UE1 12-1 is as SL Positioning Server UE, UE1 12-1 sends SL service request to UE2 12-2, as an example of SL service request 26 in Figure 1 . UE1 12-1 includes in the SL service request towards UE2 12-2 with the information of Ranging / SL Positioning service exposure to Client UE 14 (e.g., info of SL Positioning Client UE as received in stepl).

[0135] In some embodiments, the SL Service request is transmitted over SR5 as the non-SLPP messages. Embodiment should anyway allow SL Service request as PC5 message or SLPP message. SLPP is used among UEs in order to obtain location related measurements / location estimates, to transfer assistance data, or to exchange of capabilities, e.g., Sidelink Positioning assistant data related procedure or SL-PRS measurement related procedure as otherwise described in clause 6.8 of TS 23.586 V18.1.0.

[0136] Step4a. UE2 12-2 triggers UE privacy check. It can be based on the local configured privacy verification information, e.g., as an example of privacy profile 32 in Figure 1 , to determine whether its location related information can be exposed to the Client UE 14.

[0137] UE2 12-2 may trigger a MO-LR (e.g., 5GC-MO-LR) to its serving AMF / LMF to retrieve its location. As part of this MO-LR, it includes the information of Ranging / SL Positioning service exposure to the Client UE 14 (e.g., info of SL Positioning Client UE as received in stepl) in the location request. LMF / AMF may check the UE2’s privacy as depicted in Option B.

[0138] Step5a. UE2 12-2 sends SL service response to UE1 12-1.

[0139] Step6a. If privacy check of UE1 / UE2 is OK, UE1 12-1 continues SL Positioning operation. UE1 12-1 performs / obtains SL Positioning result as otherwise described in clause 6.8 of TS 23.586 V18.1.0.

[0140] Variant

[0141] When UE1 is not as SL Positioning Server UE, UE1 selects one SL Positioning Server UE and sends the SL service request to the SL Positioning Server UE. UE1 includes in the SL service request with the information of Ranging / SL Positioning service exposure to the Client UE (e.g., info of SL Positioning Client UE as received in stepl ). The SL Positioning Server UE performs as UE1 towards UE2 in step 3a-6a and provides obtained SL Positioning result to UE1.

[0142] Option B, Network-based operation

[0143] Step2b. UE1 12-1 sends location request (e.g., SL-MO-LR, 5GC-MO-LR) to the serving AMF (not shown in the flow) in a UL NAS TRANSPORT message to request to location information of UE1 12-1 or location information of UE1 12-1 and UE2 12-2; the location information can be e.g. absolute location, relative location or ranging information. The serving AMF further sends Nlmf_Location_DetermineLocation request towards the LMF 15 with the information from the location request from UE1 , as otherwise described in clause 6.20.1 of TS 23.273 V18.3.0. Either the location request to the serving AMF or the Nlmf_Location_DetermineLocation request may exemplify the location request 32 in Figure 1 .

[0144] UE1 12-1 1 includes the information of Ranging / SL Positioning service exposure to the Client UE 14 (e.g., info of SL Positioning Client UE as received in stepl) in the location request.

[0145] Step3b. LMF 15 triggers privacy check of Ranging / SL Positioning service exposure to the Client UE 14 for UE1 / UE2 towards GMLC 17 when the location request received in step2b is for Ranging / SL Positioning service exposure to Client UE 14. LMF 15 includes info of the Client UE 14, info of UE1 , and / or UE2 in the request. If UE1 / UE2 belongs to different PLMNs or managed by different GMLCs, LMF 15 may trigger a privacy check towards different GMLCs of UE1 / UE2, one by one.

[0146] Optionally, it could be the AMF to trigger privacy check.

[0147] Step4b. The GMLC 17 interacts with UDM to check the UE privacy profile of UE1 / UE2 accordingly as otherwise described in clause 6.3.5 of TS 33.533 V18.0.0.

[0148] Step5b. The GMLC 17 returns privacy check response to LMF 15.

[0149] Step6b. If the privacy check of UE1 / UE2 is OK, LMF 15 continues SL Positioning operation. LMF performs / obtains MO-LR result, as otherwise described in clause 6.20.1 of TS 23.273 V18.3.0.

[0150] Step7b. The LMF 15 returns MO-LR check response to UE1 12-1 via the AMF.

[0151] Variant

[0152] When UE1 is not performing MO-LR towards its AMF / LMF (e.g., UE1 is a Reference UE) as in step 2b.

[0153] UE1 then sends the SL service request to UE2. UE1 includes in the SL service request with the information of Ranging / SL Positioning service exposure to Client UE (e.g., info of SL Positioning Client UE as received in stepl).

[0154] UE2 triggers a MO-LR (e.g., SL-MO-LR) to its serving AMF / LMF to retrieve UE1 and UE2 location. As part of this MO-LR, it includes the information of Ranging / SL Positioning service exposure to Client UE (e.g., info of SL Positioning Client UE as received in stepl) in the location request. LMF / AMF may check the UE1 ’s and UE2’s privacy as depicted in steps 2b-7b and returns MO-LR check response to UE2 via the AMF.

[0155] UE2 provides obtained SL Positioning result to UE1 .

[0156] Step8. The Ranging / SL Positioning result is provided to the Client UE by UE1 .

[0157] Consider a concrete example of UE Privacy handling for service exposure through PC5. Some embodiments propose the following changes to 3GPP TS 33.533 v18.0.0.

[0158] In some embodiments, these proposed changes solve the privacy handling of UEs for Ranging / SL positioning service exposure through PC5. Some embodiments avoid missing privacy handling of target / reference UEs for Ranging / SL Positioning service exposure to Client UE.

[0159] 6.3.6.3 Authorization procedure for Ranging / SL positioning service exposure through

[0160] PC5

[0161] For Ranging / SL Positioning service exposure through PC5 (i.e. clause 6.7.1 .1 of TS 23.586), the SL Positioning Client UE authorization is triggered by the Reference / Target UE during PC5 link establishment. The authorization can be performed by the network via the SLPKMF for ProSe capable UEs or by the Reference / Target UE if the authorization information is available in the UE.

[0162] For UE-only Operation, the UE1 includes in the SL service request towards UE2 with Client UE's user info that is received in the Ranging / SL Positioning service request from the Client UE. The Reference EU and Target UE (i.e. UE1 and UE2) trigger UE privacy verification as described in clause 6.3.7 to determine whether its location related information can be exposed to Client UE.

[0163] For Network based Operation, the Reference / Target UE includes in the SL-MO-LR towards LMF with Client UE's user info that is received in the Ranging / SL Positioning service request from the Client UE. LMF triggers privacy check of Reference UE and Target UE towards GMLC when the SL-MO-LR is requested for Ranging / SL Positioning service exposure to Client UE. The GMLC interacts with UDM to check the UE privacy profile as described in clause 6.3.5.

[0164] If the Client UE is not authorized, the Ranging / SL Positioning service request shall be rejected.

[0165] Note that LMF can trigger privacy check of UE1 / UE2 also in case the location is not exposed to Client UE. In one example, a network function (NF) collects location info of UE1 and triggers location request to GMLC. The location request eventually reaches LMF. Or UE1 may require location of its own and trigger location request to LMF. Then, LMF may determine to use positioning method assisted with SL positioning technology to get location info of UE1 and by that LMF may select UE2 to assist location request. One variant solution is that UE2 is selected in the middle of signaling path and LMF receives the request with UE1 and UE2. Either way, privacy check of UE2 can be also required. LMF may trigger privacy check towards GMLC for UE2 in such case.

[0166] In view of the modifications and variations herein, Figure 6 depicts a method performed by a communication device 12-1 , 12-2 in accordance with particular embodiments. The method includes receiving a sidelink service request 18, 26 that requests sidelink positioning or ranging of a target communication device 12T and that identifies a client 14 to which information about a position or range 16 of the target communication device 12T is to be provided according to the sidelink service request 18, 26 (Block 600).

[0167] In some embodiments, the communication device 12-1 , 12-2 that performs the method is communication device 12-1 and the received sidelink service request 18, 26 is the sidelink service request 18 received from the client 14. In other embodiments, the communication device 12-1 , 12-2 that performs the method is communication device 12-2 and the received sidelink service request 18, 26 is the sidelink service request 26 that communication device 12-2 receives from communication device 12-1 . In one such embodiment, communication device 12- 1 may select communication device 12-2 as a positioning server for the sidelink service request 26. In still other embodiments, the received sidelink service request 18, 26 is a sidelink service request 18 received from a positioning server for the sidelink service request.

[0168] Regardless, the method also includes obtaining a privacy profile 22, 32 governing the communication device 12-1 , 12-2 (Block 610). The method further comprises performing privacy verification to determine whether or not the privacy profile 22, 32 allows information about a location 20, 30 of the communication device 12-1 , 12-2 to be exposed to the client 14 (Block 620). The method also comprises handling the sidelink service request 18, 26 based on a result of the privacy verification (Block 630).

[0169] In some embodiments, said handling comprises, if the privacy verification fails based on the privacy profile 22, 32 not allowing information about a location 20, 30 of the communication device 12-1 , 12-2 to be exposed to the client 14, rejecting the sidelink service request 18, 26.

[0170] In some embodiments, said handling comprises, if the privacy verification passes based on the privacy profile 22, 32 allowing information about a location 20, 30 of the communication device 12-1 , 12-2 to be exposed to the client 14, transmitting a response to the sidelink service request 18, 26, wherein the response reveals information about the location 20, 30 of the communication device 12-1 , 12-2. In one embodiment, the response includes information about the position or range 16 of the target communication device 12T, where the information about the position or range 16 of the target communication device 12T reveals information about the location 20, 30 of the communication device 12-1 , 12-2.

[0171] In some embodiments, said handling comprises, if the privacy check passes based on the privacy profile 22, 32 allowing information about a location 20, 30 of the communication device 12-1 , 12-2 to be exposed to the identified client 14, performing a sidelink positioning or ranging operation to determine, or assist with determining, information about a position or range of the target communication device 12T.

[0172] In some embodiments, said handling comprises, if the privacy check passes based on the privacy profile 22 allowing information about a location 20 of the communication device 12-1 to be exposed to the identified client 14, transmitting the sidelink service request 26 to another communication device 12-2 or to a network node 15 in a communication network 10. In this case, the transmitted sidelink service request 26 identifies the client 14 to which the position or range 16 of the target communication device 12T is to be provided and / or to which the information about a location 20 of the communication device 12-1 is to be exposed. Alternatively or additionally, in some embodiments, said handling comprises, if the privacy check passes based on the privacy profile 22 allowing information about a location 20 of the communication device 12-1 to be exposed to the identified client 14, transmitting a location request 36 to a network node 15 in a communication network 10. In this case, the location request 36 requests a location 20 of the communication device 12-1 , wherein the location request 36 identifies the client 14 to which the position or range 16 of the target communication device 12T is to be provided and / or to which the information about a location 20 of the communication device 12-1 is to be exposed. In one embodiment, the transmitted sidelink service request 26 and / or the location request 36 includes a user information field that indicates an application layer identifier of the client 14, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0173] In some embodiments, the received sidelink service request 18, 26 includes a user information field that indicates an application layer identifier of the client 14, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0174] In some embodiments, the sidelink service request 18, 26 is received at a sidelink positioning or ranging layer of a protocol stack at the communication device 12-1 , 12-2 and / or is handled as application layer traffic by the communication device 12-1 , 12-2.

[0175] In some embodiments, the sidelink service request 18, 26 is received over a sidelink with the client 14 or with another communication device.

[0176] In some embodiments, the communication device 12-1 , 12-2 is the target communication device 12T. In one embodiment, the sidelink service request 18, 26 is a sidelink service request 26 received from a reference communication device that is to support sidelink positioning or ranging of the target communication device 12T.

[0177] In some embodiments, the communication device 12-1 , 12-2 is a reference communication device that is to support sidelink positioning or ranging of the target communication device 12T. In one embodiment, the sidelink service request is received from the target communication device 12T.

[0178] In some embodiments, the communication device 12-1 , 12-2 serves as a sidelink positioning server for the sidelink service request.

[0179] In some embodiments, the client 14 is a communication device and is a sidelink positioning client for the sidelink service request.

[0180] In some embodiments, the privacy profile 22, 32 comprises locally configured privacy verification information.

[0181] In some embodiments, the sidelink service request is received from the target communication device 12T or from a reference communication device that is to support sidelink positioning or ranging of the target communication device 12T.

[0182] In some embodiments, the network node 15 implements an access and mobility function or a location management function.

[0183] Figure 7A shows a method performed by a communication device 12-1 according to other embodiments. The method comprises receiving a sidelink service request 18 that requests sidelink positioning or ranging of a target communication device 12T and that identifies a client

[0184] 14 to which information about a position or range 16 of the target communication device 12T is to be provided according to the sidelink service request 18 (Block 700). The method also comprises transmitting a message to another communication device 12-2 or to a network node

[0185] 15 in a communication network 10, wherein the message identifies the client 14 to which the position or range 16 of the target communication device 12T is to be provided and / or to which information about a location 20 of the communication device 12-1 is to be exposed (Block 710).

[0186] In some embodiments, the message is transmitted to another communication device 12- 2.

[0187] In some embodiments, the message is or includes the sidelink service request 18.

[0188] In some embodiments, the communication device 12-1 is the target communication device 12T or a reference communication device that is to support sidelink positioning or ranging of the target communication device 12T.

[0189] In some embodiments, the another communication device 12-2 is the target communication device 12T or a reference communication device that is to support sidelink positioning or ranging of the target communication device 12T.

[0190] In some embodiments, the method further comprises selecting the another communication device 12-2 to serve as a sidelink positioning server for sidelink service request 26.

[0191] In some embodiments, the message is transmitted to the network node 15.

[0192] In some embodiments, the message is a location request 36 that requests a location of the communication device 12-1 . In some embodiments, wherein the sidelink service request 18 and / or the message includes a user information field that indicates an application layer identifier of the client 14, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0193] In some embodiments, the sidelink service request 18 is received from the client 14, another communication device that selects the communication device as a positioning server for the sidelink service request, or a positioning server for the sidelink service request.

[0194] In some embodiments, the sidelink service request 18 is received at a sidelink positioning or ranging layer of a protocol stack at the communication device 12-1 and / or is handled as application layer traffic by the communication device 12-1 .

[0195] In some embodiments, the sidelink service request 18 is received over a sidelink with the client or with another communication device.

[0196] In some embodiments, the client 14 is a communication device and is a sidelink positioning client for the sidelink service request.

[0197] In some embodiments, the method further comprises obtaining a privacy profile 22 governing the communication device 12-1 and performing privacy verification to determine whether or not the privacy profile 22 allows information about a location 20 of the communication device 12-1 to be exposed to the client 14, wherein the privacy verification passes based on the privacy profile 22 allowing information about a location 20 of the communication device 12-1 to be exposed to the client 14, and wherein the message is transmitted based on the privacy verification passing.

[0198] In some embodiments, the method further comprises obtaining information about the position or range 16 of the target communication device 12T, wherein the information about the position or range 16 of the target communication device 12T reveals information about the location 20 of the communication device 12-1 . The method in this case also comprises transmitting the obtained information in a response to the sidelink service request 18. In one embodiment, said obtaining comprises performing a sidelink positioning or ranging operation to determine, or assist with determining, the information about a position or range 16 of the target communication device 12T.

[0199] In some embodiments, the communication device 12-1 serves as a sidelink positioning server for the sidelink service request 18.

[0200] In some embodiments, the network node 15 implements an access and mobility function or a location management function.

[0201] Figure 7B depicts a method performed by a communication device 12-2 in accordance with particular embodiments. The method includes receiving, from another communication device 12-1 , a message that identifies a client 14 to which information about a position or range 16 of a target communication device 12T is to be provided and / or to which information about a location 30 of the communication device 12-2 is to be exposed (Block 750).

[0202] The method also includes obtaining a privacy profile 32 governing the communication device 12-2 (Block 760). The method further comprises performing privacy verification to determine whether or not the privacy profile 32 allows information about a location 30 of the communication device 12-2 to be exposed to the client 14 (Block 770). The method also comprises handling the message based on a result of the privacy verification (Block 780). Such handling may for example comprise transmitting a response to the message based on a result of the privacy verification, e.g., where the response indicates the result of the privacy verification.

[0203] In some embodiments, said handling comprises, if the privacy verification passes based on the privacy profile 32 allowing information about a location 30 of the communication device 12-2 to be exposed to the client 14, performing a sidelink positioning or ranging operation to determine, or assist with determining, information about a position or range of the target communication device 12T.

[0204] In some embodiments, the received message includes a user information field that indicates an application layer identifier of the client 14, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0205] In some embodiments, the message is received at a sidelink positioning or ranging layer of a protocol stack at the communication device 12-2 and / or is handled as application layer traffic by the communication device 12-2.

[0206] In some embodiments, the message is received over a sidelink with the another communication device 12-1 .

[0207] In some embodiments, the another communication device 12-1 is a reference communication device that is to support sidelink positioning or ranging of the target communication device 12T.

[0208] In some embodiments, the privacy profile 32 comprises locally configured privacy verification information.

[0209] Figure 8 shows a method performed by a network node 15 in a communication network 10. According to some embodiments. The method comprises receiving a location request 36 that requests a location of a communication device 12-1 , 12-2, wherein the location request 36 identifies a client 14 to which information about a position or range 16 of a target communication device 12T is to be provided and / or to which information about the location 20, 30 of the communication device 12-1 , 12-2 is to be exposed (Block 800). The method also comprises performing, or triggering performance of, privacy verification to determine whether or not a privacy profile 22, 32 governing the communication device 12-1 , 12-2 allows information about the location 20, 30 of the communication device 12-1 , 12-2 to be exposed to the client 14 (Block 810). The method further comprises handling the location request 36 based on a result of the privacy verification (Block 820).

[0210] In some embodiments, said handling comprises, if the privacy verification fails based on the privacy profile 22, 32 not allowing information about the location 20, 30 of the communication device 12-1 , 12-2 to be exposed to the client 14, rejecting the location request 36.

[0211] In some embodiments, said handling comprises, if the privacy verification passes based on the privacy profile 22, 32 allowing information about the location 20, 30 of the communication device 12-1 , 12-2 to be exposed to the client 14, transmitting a response to the location request 36 that indicates the location 20, 30 of the communication device 12-1 , 12-2.

[0212] In some embodiments, the said performing or triggering comprises triggering performance of the privacy verification by transmitting, to another network node, a request to perform the privacy verification; and receiving a result of the privacy verification in response to the request. In one embodiment, the another network node implements a gateway mobile location center, GMLC.

[0213] In some embodiments, the location request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0214] In some embodiments, the location request also requests a location of another communication device. In this case, the method in some embodiments further comprises performing, or triggering performance of, another privacy verification to determine whether or not another privacy profile governing the another communication device allows information about the location of the another communication device to be exposed to the client. The method in this case may further comprise handling the location request based on a result of the another privacy verification.

[0215] In some embodiments, the communication device is the target communication device.

[0216] In some embodiments, the communication device is a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0217] In some embodiments, the client is a communication device and is a sidelink positioning client for the sidelink service request.

[0218] In some embodiments, the network node implements an access and mobility function or a location management function.

[0219] In some embodiments, the location request is received in an uplink non-access stratum, NAS, transport message.

[0220] In some embodiments, the location request is received from the communication device. Figure 9 shows a method performed by a network node 17 in a communication network 10 according to other embodiments. The method comprises receiving a request to perform privacy verification to determine whether or not a privacy profile 22, 32 governing a communication device 12-1 , 12-2 allows information about a location 20, 30 of the communication device 12-1 , 12-2 to be exposed to a client 14 (Block 900). The method further comprises performing the privacy verification to determine whether or not the privacy profile 22, 32 governing the communication device 12-1 , 12-2 allows information about the location 20, 30 of the communication device 12-1 , 12-2 to be exposed to the client 14 (Block 910). The method also comprises transmitting a result of the privacy verification in a response to the request (Block 920).

[0221] In some embodiments, the network node 17 implements a gateway mobile location center, GMLC.

[0222] In some embodiments, the request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0223] In some embodiments, the request also requests privacy verification for another communication device. In one such embodiment, the method further comprises performing another privacy verification to determine whether or not another privacy profile governing the another communication device allows information about the location of the another communication device to be exposed to the client. The method may also comprise transmitting a result of the another privacy verification in a response to the request.

[0224] In some embodiments, the communication device is the target communication device.

[0225] In some embodiments, the communication device is a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0226] In some embodiments, the client is a sidelink positioning client.

[0227] Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication device configured to perform any of the steps of any of the embodiments described above for the communication device.

[0228] Embodiments also include a communication device 12-1 , 12-2 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12-1 , 12-2. The power supply circuitry is configured to supply power to the communication device 12-1 , 12-2.

[0229] Embodiments further include a communication device 12-1 , 12-2 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12-1 , 12-2. In some embodiments, the communication device 12-1 , 12-2 further comprises communication circuitry. Embodiments further include a communication device 12-1 , 12-2 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication device 12-1 , 12-2 is configured to perform any of the steps of any of the embodiments described above for the communication device 12-1 , 12-2.

[0230] Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12-1 , 12-2. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

[0231] Embodiments herein also include a network node 15, 17 configured to perform any of the steps of any of the embodiments described above for the network node 15, 17.

[0232] Embodiments also include a network node 15, 17 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 15, 17. The power supply circuitry is configured to supply power to the network node 15, 17.

[0233] Embodiments further include a network node 15, 17 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 15, 17. In some embodiments, the network node 15, 17 further comprises communication circuitry.

[0234] Embodiments further include a network node 15, 17 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the network node 15, 17 is configured to perform any of the steps of any of the embodiments described above for the network node 15, 17.

[0235] More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

[0236] Figure 10 for example illustrates a communication device 12-1 , 12-2 as implemented in accordance with one or more embodiments. As shown, the communication device 12-1 , 12-2 includes processing circuitry 1010 and communication circuitry 1020. The communication circuitry 1020 (e.g., radio circuitry) is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the communication device 12-1 , 12-2. The processing circuitry 1010 is configured to perform processing described above, e.g., in Figure 6 and / or Figure 7A and / or Figure 7B, such as by executing instructions stored in memory 1030. The processing circuitry 1010 in this regard may implement certain functional means, units, or modules.

[0237] Figure 11 illustrates a network node 15, 17 as implemented in accordance with one or more embodiments. As shown, the network node 15, 17 includes processing circuitry 1110 and communication circuitry 1120. The communication circuitry 1120 is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. The processing circuitry 1110 is configured to perform processing described above, e.g., in Figure 8 and / or 9, such as by executing instructions stored in memory 1130. The processing circuitry 1110 in this regard may implement certain functional means, units, or modules.

[0238] Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

[0239] A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

[0240] Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0241] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

[0242] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

[0243] Figure 12 shows an example of a communication system 1200 in accordance with some embodiments.

[0244] In the example, the communication system 1200 includes a telecommunication network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208. The access network 1204 includes one or more access network nodes, such as network nodes 1210a and 1210b (one or more of which may be generally referred to as network nodes 1210), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1202 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 1202, including one or more network nodes 1210 and / or core network nodes 1208.

[0245] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212a, 1212b, 1212c, and 1212d (one or more of which may be generally referred to as UEs 1212) to the core network 1206 over one or more wireless connections.

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

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

[0248] In the depicted example, the core network 1206 connects the network nodes 1210 to one or more hosts, such as host 1216. 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 1206 includes one more core network nodes (e.g., core network node 1208) 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 1208. 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).

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

[0250] As a whole, the communication system 1200 of Figure 12 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.

[0251] In some examples, the telecommunication network 1202 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1202. For example, the telecommunications network 1202 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)ZMassive loT services to yet further UEs.

[0252] In some examples, the UEs 1212 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 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204. 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).

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

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

[0255] Figure 13 shows a UE 1300 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, 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- loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP 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).

[0256] The UE 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input / output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 13. 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.

[0257] The processing circuitry 1302 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 1310. The processing circuitry 1302 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 1302 may include multiple central processing units (CPUs).

[0258] In the example, the input / output interface 1306 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 1300. 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.

[0259] In some embodiments, the power source 1308 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 1308 may further include power circuitry for delivering power from the power source 1308 itself, and / or an external power source, to the various parts of the UE 1300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1308. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1308 to make the power suitable for the respective components of the UE 1300 to which power is supplied.

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

[0261] The memory 1310 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 (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1310 may allow the UE 1300 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 1310, which may be or comprise a device-readable storage medium.

[0262] The processing circuitry 1302 may be configured to communicate with an access network or other network using the communication interface 1312. The communication interface 1312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1322. The communication interface 1312 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 a network node in an access network). Each transceiver may include a transmitter 1318 and / or a receiver 1320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1318 and receiver 1320 may be coupled to one or more antennas (e.g., antenna 1322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0263] In the illustrated embodiment, communication functions of the communication interface 1312 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.

[0264] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1312, 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).

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

[0266] 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 or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a 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 1300 shown in Figure 13.

[0267] 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 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT 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.

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

[0269] Figure 14 shows a network node 1400 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, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0270] 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, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such 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).

[0271] 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).

[0272] The network node 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408. The network node 1400 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 1400 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 1400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs). The network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1400.

[0273] The processing circuitry 1402 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 1400 components, such as the memory 1404, to provide network node 1400 functionality.

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

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

[0276] The communication interface 1406 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 1406 comprises port(s) / terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection. The communication interface 1406 also includes radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, the antenna 1410. Radio front-end circuitry 1418 comprises filters 1420 and amplifiers 1422. The radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402. The radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402. The radio front-end circuitry 1418 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 1418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1420 and / or amplifiers 1422. The radio signal may then be transmitted via the antenna 1410. Similarly, when receiving data, the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418. The digital data may be passed to the processing circuitry 1402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0277] In certain alternative embodiments, the network node 1400 does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406. In still other embodiments, the communication interface 1406 includes one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).

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

[0279] The antenna 1410, communication interface 1406, and / or the processing circuitry 1402 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 1410, the communication interface 1406, and / or the processing circuitry 1402 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.

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

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

[0282] Figure 15 is a block diagram of a host 1500, which may be an embodiment of the host 1216 of Figure 12, in accordance with various aspects described herein. As used herein, the host 1500 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 1500 may provide one or more services to one or more UEs.

[0283] The host 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input / output interface 1506, a network interface 1508, a power source 1510, and a memory 1512. 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 Figures 13 and 14, such that the descriptions thereof are generally applicable to the corresponding components of host 1500.

[0284] The memory 1512 may include one or more computer programs including one or more host application programs 1514 and data 1516, which may include user data, e.g., data generated by a UE for the host 1500 or data generated by the host 1500 for a UE. Embodiments of the host 1500 may utilize only a subset or all of the components shown. The host application programs 1514 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), Advanced 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 1514 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 1500 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1514 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0285] Figure 16 is a block diagram illustrating a virtualization environment 1600 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 1600 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 1600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0286] Applications 1602 (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.

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

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

[0289] In the context of NFV, a VM 1608 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 1608, and that part of hardware 1604 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 1608 on top of the hardware 1604 and corresponds to the application 1602.

[0290] Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization. Alternatively, hardware 1604 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 1610, which, among others, oversees lifecycle management of applications 1602. In some embodiments, hardware 1604 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 1612 which may alternatively be used for communication between hardware nodes and radio units.

[0291] Figure 17 shows a communication diagram of a host 1702 communicating via a network node 1704 with a UE 1706 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1212a of Figure 12 and / or UE 1300 of Figure 13), network node (such as network node 1210a of Figure 12 and / or network node 1400 of Figure 14), and host (such as host 1216 of Figure 12 and / or host 1500 of Figure 15) discussed in the preceding paragraphs will now be described with reference to Figure 17.

[0292] Like host 1500, embodiments of host 1702 include hardware, such as a communication interface, processing circuitry, and memory. The host 1702 also includes software, which is stored in or accessible by the host 1702 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 1706 connecting via an over-the-top (OTT) connection 1750 extending between the UE 1706 and host 1702. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1750.

[0293] The network node 1704 includes hardware enabling it to communicate with the host 1702 and UE 1706. The connection 1760 may be direct or pass through a core network (like core network 1206 of Figure 12) 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.

[0294] The UE 1706 includes hardware and software, which is stored in or accessible by UE 1706 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 1706 with the support of the host 1702. In the host 1702, an executing host application may communicate with the executing client application via the OTT connection 1750 terminating at the UE 1706 and host 1702. 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 1750 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 1750.

[0295] The OTT connection 1750 may extend via a connection 1760 between the host 1702 and the network node 1704 and via a wireless connection 1770 between the network node 1704 and the UE 1706 to provide the connection between the host 1702 and the UE 1706. The connection 1760 and wireless connection 1770, over which the OTT connection 1750 may be provided, have been drawn abstractly to illustrate the communication between the host 1702 and the UE 1706 via the network node 1704, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0296] As an example of transmitting data via the OTT connection 1750, in step 1708, the host 1702 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 1706. In other embodiments, the user data is associated with a UE 1706 that shares data with the host 1702 without explicit human interaction. In step 1710, the host 1702 initiates a transmission carrying the user data towards the UE 1706. The host 1702 may initiate the transmission responsive to a request transmitted by the UE 1706. The request may be caused by human interaction with the UE 1706 or by operation of the client application executing on the UE 1706. The transmission may pass via the network node 1704, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1712, the network node 1704 transmits to the UE 1706 the user data that was carried in the transmission that the host 1702 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1714, the UE 1706 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1706 associated with the host application executed by the host 1702.

[0297] In some examples, the UE 1706 executes a client application which provides user data to the host 1702. The user data may be provided in reaction or response to the data received from the host 1702. Accordingly, in step 1716, the UE 1706 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 1706. Regardless of the specific manner in which the user data was provided, the UE 1706 initiates, in step 1718, transmission of the user data towards the host 1702 via the network node 1704. In step 1720, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1704 receives user data from the UE 1706 and initiates transmission of the received user data towards the host 1702. In step 1722, the host 1702 receives the user data carried in the transmission initiated by the UE 1706.

[0298] One or more of the various embodiments improve the performance of OTT services provided to the UE 1706 using the OTT connection 1750, in which the wireless connection 1770 forms the last segment.

[0299] In an example scenario, factory status information may be collected and analyzed by the host 1702. As another example, the host 1702 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1702 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1702 may store surveillance video uploaded by a UE. As another example, the host 1702 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 1702 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.

[0300] 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 1750 between the host 1702 and UE 1706, 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 1702 and / or UE 1706. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1750 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 1750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1704. 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 1702. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1750 while monitoring propagation times, errors, etc.

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

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

[0303] Some embodiments herein are enumerated below:

[0304] Group A Embodiments

[0305] A1 . A method performed by a communication device, the method comprising: receiving a sidelink service request that requests sidelink positioning or ranging of a target communication device and that identifies a client to which information about a position or range of the target communication device is to be provided according to the sidelink service request; obtaining a privacy profile governing the communication device; performing privacy verification to determine whether or not the privacy profile allows information about a location of the communication device to be exposed to the client; and handling the sidelink service request based on a result of the privacy verification.

[0306] A2. The method of embodiment A1 , wherein said handling comprises, if the privacy verification fails based on the privacy profile not allowing information about a location of the communication device to be exposed to the client, rejecting the sidelink service request.

[0307] A3. The method of embodiment A1 , wherein said handling comprises, if the privacy verification passes based on the privacy profile allowing information about a location of the communication device to be exposed to the client, transmitting a response to the sidelink service request, wherein the response reveals information about the location of the communication device.

[0308] A4. The method of embodiment A3, wherein the response includes information about the position or range of the target communication device, wherein the information about the position or range of the target communication device reveals information about the location of the communication device.

[0309] A5. The method of any of embodiments A1 and A3-A4, wherein said handling comprises, if the privacy check passes based on the privacy profile allowing information about a location of the communication device to be exposed to the identified client, performing a sidelink positioning or ranging operation to determine, or assist with determining, information about a position or range of the target communication device.

[0310] A6. The method of any of embodiments A1 and A3-A5, wherein said handling comprises, if the privacy check passes based on the privacy profile allowing information about a location of the communication device to be exposed to the identified client: transmitting the sidelink service request to another communication device or to a network node in a communication network, wherein the transmitted sidelink service request identifies the client to which the position or range of the target communication device is to be provided and / or to which the information about a location of the communication device is to be exposed; and / or transmitting a location request to a network node in a communication network, wherein the location request requests a location of the communication device, wherein the location request identifies the client to which the position or range of the target communication device is to be provided and / or to which the information about a location of the communication device is to be exposed.

[0311] A7. The method of embodiment A6, wherein the transmitted sidelink service request and / or the location request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0312] A8. The method of any of embodiments A1 -A7, wherein the received sidelink service request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0313] A9. The method of any of embodiments A1 -A8, wherein the sidelink service request is received from: the client; another communication device that selects the communication device as a positioning server for the sidelink service request; or a positioning server for the sidelink service request.

[0314] A10. The method of any of embodiments A1 -A9, wherein the sidelink service request is received at a sidelink positioning or ranging layer of a protocol stack at the communication device and / or is handled as application layer traffic by the communication device.

[0315] A11 . The method of any of embodiments A1 -A10, wherein the sidelink service request is received over a sidelink with the client or with another communication device.

[0316] A12. The method of any of embodiments A1 -A11 , wherein the communication device is the target communication device.

[0317] A13. The method of embodiment A12, wherein the sidelink service request is received from a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0318] A14. The method of any of embodiments A1 -A11 , wherein the communication device is a reference communication device that is to support sidelink positioning or ranging of the target communication device. A15. The method of embodiment A14, wherein the sidelink service request is received from the target communication device.

[0319] A16. The method of any of embodiments A1 -A15, wherein the communication device serves as a sidelink positioning server for the sidelink service request.

[0320] A17. The method of any of embodiments A1 -A16, wherein the client is a communication device and is a sidelink positioning client for the sidelink service request.

[0321] A18. The method of any of embodiments A1 -A17, wherein the privacy profile comprises locally configured privacy verification information.

[0322] A19. The method of any of embodiments A1 -A18, wherein the sidelink service request is received from the target communication device or from a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0323] A20. The method of any of embodiments A6-A7, wherein the network node implements an access and mobility function or a location management function.

[0324] AA1 . A method performed by a communication device, the method comprising: receiving a sidelink service request that requests sidelink positioning or ranging of a target communication device and that identifies a client to which information about a position or range of the target communication device is to be provided according to the sidelink service request; and transmitting a message to another communication device or to a network node in a communication network, wherein the message identifies the client to which the position or range of the target communication device is to be provided and / or to which information about a location of the communication device is to be exposed.

[0325] AA2. The method of embodiment AA1 , wherein the message is transmitted to another communication device.

[0326] AA3. The method of any of embodiments AA1-AA2, wherein the message is a sidelink service request that requests sidelink positioning or ranging of the target communication device and / or of the communication device.

[0327] AA4. The method of any of embodiments AA1-AA3, wherein the communication device is the target communication device or a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0328] AA5. The method of any of embodiments AA1-AA4, wherein the another communication device is the target communication device or a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0329] AA6. The method of any of embodiments AA1-AA5, further comprising selecting the another communication device to serve as a sidelink positioning server for sidelink service request.

[0330] AA7. The method of any of embodiments AA1 and AA3-AA6, wherein the message is transmitted to the network node.

[0331] AA8. The method of any of embodiments AA1 , AA4, and AA7, wherein the message is a location request that requests a location of the communication device.

[0332] AA9. The method of any of embodiments AA1-AA8, wherein the sidelink service request and / or the message includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0333] AA10. The method of any of embodiments AA1 -AA9, wherein the sidelink service request is received from: the client; another communication device that selects the communication device as a positioning server for the sidelink service request; or a positioning server for the sidelink service request.

[0334] AA11 . The method of any of embodiments AA1 -AA10, wherein the sidelink service request is received at a sidelink positioning or ranging layer of a protocol stack at the communication device and / or is handled as application layer traffic by the communication device.

[0335] AA12. The method of any of embodiments AA1 -AA11 , wherein the sidelink service request is received over a sidelink with the client or with another communication device.

[0336] AA13. The method of any of embodiments AA1 -AA12, wherein the client is a communication device and is a sidelink positioning client for the sidelink service request. AA14. The method of any of embodiments AA1 -AA13, further comprising obtaining a privacy profile governing the communication device and performing privacy verification to determine whether or not the privacy profile allows information about a location of the communication device to be exposed to the client, wherein the privacy verification passes based on the privacy profile allowing information about a location of the communication device to be exposed to the client, and wherein the message is transmitted based on the privacy verification passing.

[0337] AA15. The method of any of embodiments AA1 -AA14, further comprising: obtaining information about the position or range of the target communication device, wherein the information about the position or range of the target communication device reveals information about the location of the communication device; and transmitting the obtained information in a response to the sidelink service request.

[0338] AA16. The method of embodiment AA15, wherein said obtaining comprises performing a sidelink positioning or ranging operation to determine, or assist with determining, the information about a position or range of the target communication device.

[0339] AA17. The method of any of embodiments AA1 -AA16, wherein the communication device serves as a sidelink positioning server for the sidelink service request.

[0340] AA18. The method of any of embodiments AA1 -AA17, wherein the network node implements an access and mobility function or a location management function.

[0341] AA. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to a base station.

[0342] Group B Embodiments

[0343] B1 . A method performed by a network node in a communication network, the method comprising: receiving a location request that requests a location of a communication device, wherein the location request identifies a client to which information about a position or range of a target communication device is to be provided and / or to which information about the location of the communication device is to be exposed; performing, or triggering performance of, privacy verification to determine whether or not a privacy profile governing the communication device allows information about the location of the communication device to be exposed to the client; and handling the location request based on a result of the privacy verification.

[0344] B2. The method of embodiment B1 , wherein said handling comprises, if the privacy verification fails based on the privacy profile not allowing information about the location of the communication device to be exposed to the client, rejecting the location request.

[0345] B3. The method of embodiment B1 , wherein said handling comprises, if the privacy verification passes based on the privacy profile allowing information about the location of the communication device to be exposed to the client, transmitting a response to the location request that indicates the location of the communication device.

[0346] B4. The method of any of embodiments B1 -B3, wherein the said performing or triggering comprises triggering performance of the privacy verification by: transmitting, to another network node, a request to perform the privacy verification; and receiving a result of the privacy verification in response to the request.

[0347] B5. The method of embodiment B4, wherein the another network node implements a gateway mobile location center, GMLC.

[0348] B6. The method of any of embodiments B1 -B5 wherein the location request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0349] B7. Reserved.

[0350] B8. The method of any of embodiments B1 -B7, wherein the location request also requests a location of another communication device, and wherein the method further comprises: performing, or triggering performance of, another privacy verification to determine whether or not another privacy profile governing the another communication device allows information about the location of the another communication device to be exposed to the client; and handling the location request based on a result of the another privacy verification.

[0351] B9. The method of any of embodiments B1 -B8, wherein the communication device is the target communication device. B1O. The method of any of embodiments B1 -B8, wherein the communication device is a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0352] B11 . The method of any of embodiments B1 -B10, wherein the client is a communication device and is a sidelink positioning client for the sidelink service request.

[0353] B12. The method of any of embodiments B1-B11 , wherein the network node implements an access and mobility function or a location management function.

[0354] B13. The method of any of embodiments B1 -B12, wherein the location request is received in an uplink non-access stratum, NAS, transport message.

[0355] B14. The method of any of embodiments B1 -B13, wherein the location request is received from the communication device.

[0356] BB1 . A method performed by a network node in a communication network, the method comprising: receiving a request to perform privacy verification to determine whether or not a privacy profile governing a communication device allows information about a location of the communication device to be exposed to a client; performing the privacy verification to determine whether or not the privacy profile governing the communication device allows information about the location of the communication device to be exposed to the client; and transmitting a result of the privacy verification in a response to the request.

[0357] BB2. The method of embodiment BB1 , wherein the network node implements a gateway mobile location center, GMLC.

[0358] BB3. The method of any of embodiments BB1-BB2 wherein the request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0359] BB4. The method of any of embodiments BB1-BB3, wherein the request also requests privacy verification for another communication device, and wherein the method further comprises: performing another privacy verification to determine whether or not another privacy profile governing the another communication device allows information about the location of the another communication device to be exposed to the client; and transmitting a result of the another privacy verification in a response to the request.

[0360] BB5. The method of any of embodiments BB1-BB4, wherein the communication device is the target communication device.

[0361] BB6. The method of any of embodiments BB1-BB4, wherein the communication device is a reference communication device that is to support sidelink positioning or ranging of the target communication device.

[0362] BB7. The method of any of embodiments BB1-BB6, wherein the client is a sidelink positioning client.

[0363] BBB1 . A method performed by a network node in a communication network, the method comprising: receiving a location request that requests a location of a communication device; performing, or triggering performance of, privacy verification to determine whether or not a privacy profile governing the communication device allows the location request; and handling the location request based on a result of the privacy verification.

[0364] BBB2. The method of embodiment BBB1 , wherein said handling comprises, if the privacy verification fails based on the privacy profile not allowing the location request, rejecting the location request.

[0365] BBB3. The method of embodiment BBB1 , wherein said handling comprises, if the privacy verification passes based on the privacy profile allowing the location request, transmitting a response to the location request that indicates the location of the communication device.

[0366] BBB4. The method of any of embodiments BBB1-BBB3, wherein the said performing or triggering comprises triggering performance of the privacy verification by: transmitting, to another network node, a request to perform the privacy verification; and receiving a result of the privacy verification in response to the request.

[0367] BBB5. The method of embodiment BBB4, wherein the another network node implements a gateway mobile location center, GMLC.

[0368] BBB6. The method of any of embodiments BBB1-BBB5, wherein the location request identifies a client to which information about the location of the communication device is to be exposed, and wherein the location request includes a user information field that indicates an application layer identifier of the client, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0369] BBB7. The method of any of embodiments BBB1-BBB6, wherein the location request indicates a party to which information about the location of the communication device is to be exposed and / or indicates a purpose for which the location of the communication device is to be used, and wherein the privacy verification determines whether or not the privacy profile allows information about the location of the communication device to be exposed and / or used as indicated in the location request.

[0370] BBB8. The method of embodiment BBB7, wherein the party is a communication network or a network node in a communication network.

[0371] BBB9. The method of embodiment BBB7, wherein the party is a communication device and is a client for sidelink positioning or ranging of a target communication device.

[0372] BBB10. The method of any of embodiments BBB1-BBB9, wherein the location request also requests a location of another communication device, and wherein the method further comprises: performing, or triggering performance of, another privacy verification to determine whether or not another privacy profile governing the another communication device allows the location request; and handling the location request based on a result of the another privacy verification.

[0373] BBB11 . The method of any of embodiments BBB1 -BBB10, wherein the communication device is a target communication device of sidelink positioning or ranging.

[0374] BBB12. The method of any of embodiments BBB1-BBB10, wherein the communication device is a reference communication device that is to support sidelink positioning or ranging of a target communication device. BBB13. The method of any of embodiments BBB1-BBB12, wherein the network node implements an access and mobility function or a location management function.

[0375] BBB14. The method of any of embodiments BBB1-BBB13, wherein the location request is received in an uplink non-access stratum, NAS, transport message.

[0376] BBB15. The method of any of embodiments BBB1-BBB14, wherein the location request is received from the communication device.

[0377] BBBB1 . A method performed by a network node in a communication network, the method comprising: receiving a request to perform privacy verification to determine whether or not a privacy profile governing a communication device allows information about a location of the communication device to be exposed and / or used in a certain way; performing the privacy verification; and transmitting a result of the privacy verification in a response to the request.

[0378] BBBB2. The method of embodiment BBBB1 , wherein the network node implements a gateway mobile location center, GMLC.

[0379] BBBB3. The method of any of embodiments BBBB1-BBBB2 wherein the request includes a user information field that indicates an application layer identifier of a client to which the information about the location of the communication device is to be exposed, wherein the application layer identifier identifies the client as a sidelink positioning or ranging enabled communication device within a context of a specific application.

[0380] BBBB4. The method of any of embodiments BBBB1-BBBB3, wherein the request also requests privacy verification for another communication device, and wherein the method further comprises: performing another privacy verification to determine whether or not another privacy profile governing the another communication device allows information about the location of the another communication device to be used and / or exposed in the certain way; and transmitting a result of the another privacy verification in a response to the request.

[0381] BBBB5. The method of any of embodiments BBBB1-BBBB4, wherein the communication device is a target communication device of sidelink positioning or ranging. BBBB6. The method of any of embodiments BBBB1-BBBB4, wherein the communication device is a reference communication device that is to support sidelink positioning or ranging of a target communication device.

[0382] BBBB7. The method of any of embodiments BBBB1-BBBB6, wherein the location request indicates that the information about the location of the communication device is to be exposed to and / or used by a certain party.

[0383] BBB8. The method of embodiment BBBB7, wherein the certain party is a client for sidelink positioning or ranging of a target communication device.

[0384] BBB9. The method of embodiment BBBB8, wherein the certain party is a communication network or a network node of a communication network.

[0385] BB. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a communication device.

[0386] Group C Embodiments

[0387] C1 . A communication device configured to perform the method of any of the Group A embodiments.

[0388] C2. A communication device comprising processing circuitry configured to perform the method of any of the Group A embodiments.

[0389] C3. A communication device comprising: communication circuitry; and processing circuitry configured to perform the method of any of the Group A embodiments.

[0390] C4. A communication device comprising: processing circuitry configured to perform the method of any of the Group A embodiments; and power supply circuitry configured to supply power to the communication device.

[0391] C5. A communication device comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the communication device is configured to perform the method of any of the Group A embodiments.

[0392] C6. The communication device of any of embodiments C1-C5, wherein the communication device is a wireless communication device.

[0393] C7. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform the method of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the

[0394] UE.

[0395] C8. A computer program comprising instructions which, when executed by at least one processor of a communication device, causes the communication device to perform the method of any of the Group A embodiments.

[0396] C9. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0397] C10. A network node configured to perform the method of any of the Group B embodiments.

[0398] C11 . A network node comprising processing circuitry configured to perform the method of any of the Group B embodiments.

[0399] C12. A network node comprising: communication circuitry; and processing circuitry configured to perform the method of any of the Group B embodiments. C13. A network node comprising: processing circuitry configured to perform the method of any of the Group B embodiments; power supply circuitry configured to supply power to the network node.

[0400] C14. A network node comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the network node is configured to perform the method of any of the Group B embodiments.

[0401] C15. The network node of any of embodiments C10-C14, wherein the network node is a base station.

[0402] C16. A computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to perform the method of any of the Group B embodiments.

[0403] C17. The computer program of embodiment C16, wherein the network node is a base station.

[0404] C18. A carrier containing the computer program of any of embodiments C16-C17, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0405] Group D Embodiments

[0406] D1 . A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0407] D2. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0408] D3. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0409] D4. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0410] D5. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0411] D6. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0412] D7. The communication system of the previous embodiment, further comprising: the network node; and / or the UE.

[0413] D8. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

[0414] D9. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0415] D10. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

[0416] D11 . A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.

[0417] D12. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

[0418] D13. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host. D14. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

[0419] D15. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0420] D16. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

[0421] D17. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.

[0422] D18. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0423] D19. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host. D20. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0424] D21 . The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0425] D22. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0426] D23. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0427] D24. The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0428] ABBREVIATIONS

[0429] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

[0430] 1x RTT CDMA2000 1x Radio Transmission Technology

[0431] 3GPP 3rd Generation Partnership Project

[0432] 5G 5th Generation

[0433] 6G 6thGeneration

[0434] ABS Almost Blank Subframe

[0435] ARQ Automatic Repeat Request

[0436] AWGN Additive White Gaussian Noise

[0437] BCCH Broadcast Control Channel

[0438] BCH Broadcast Channel CA Carrier Aggregation CC Carrier Component CCCH SDU Common Control Channel SDU CDMA Code Division Multiplexing Access CGI Cell Global Identifier CIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CPICH Ec / No CPICH Received energy per chip divided by the power density in the band

[0439] CQI Channel Quality information C-RNTI Cell RNTI CSI Channel State Information DCCH Dedicated Control Channel DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell-1 D (positioning method) eMBMS evolved Multimedia Broadcast Multicast Services E-SMLC Evolved-Serving Mobile Location Centre ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control Channel E-SMLC Evolved Serving Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS For Further Study gNB Base station in NR GNSS Global Navigation Satellite System HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Medium Access Control MAC Message Authentication Code MBSFN Multimedia Broadcast multicast service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDP Power Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network PMI Precoder Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLC Radio Link Control RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS Reference Signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power OR Reference Signal Received Power

[0440] RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

[0441] RSSI Received Signal Strength Indicator RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDAP Service Data Adaptation Protocol SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self Optimized Network SS Synchronization Signal SSS Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TSS Tertiary Synchronization Signal TTI Transmission Time Interval UE User Equipment UL Uplink USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival WCDMA Wide CDMA WLAN Wide Local Area Network MO-LR Mobile Originated Location Request MT-LR Mobile Terminated Location Request

[0442] SL-MO-LR Sidelink Mobile Originating Location Request SL-MT-LR Sidelink Mobile Terminating Location Request

Claims

CLAIMS1 . A method performed by a communication device (12-1), the method comprising: receiving (600) a sidelink service request (18) that requests sidelink positioning or ranging of a target communication device (12T) and that identifies a client (14) to which information about a position or range (16) of the target communication device (12T) is to be provided according to the sidelink service request (18); obtaining (610) a privacy profile (22) governing the communication device (12-1 ); performing (620) privacy verification to determine whether or not the privacy profile (22) allows information about a location (20) of the communication device (12-1 ) to be exposed to the client (14); and handling (630) the sidelink service request (18) based on a result of the privacy verification.

2. The method of claim 1 , wherein said handling comprises, responsive to the privacy verification failing based on the privacy profile (22) not allowing information about a location (20) of the communication device (12-1) to be exposed to the client (14), rejecting the sidelink service request (18).

3. The method of claim 1 , wherein said handling comprises, responsive to the privacy verification passing based on the privacy profile (22) allowing information about a location (20) of the communication device (12-1) to be exposed to the client (14): transmitting a response to the sidelink service request (18), wherein the response reveals information about the location (20) of the communication device (12-1); and / or performing a sidelink positioning or ranging operation to determine, or assist with determining, information about a position or range (16) of the target communication device (12T).

4. The method of any of claims 1 or 3, wherein said handling comprises, responsive to the privacy check passing based on the privacy profile (22) allowing information about a location (20) of the communication device (12-1) to be exposed to the identified client (14), transmitting a sidelink service request (26) to another communication device (12-2), wherein the transmitted sidelink service request (26) identifies the client (14) to which the position or range (16) of the target communication device (12T) is to be provided and / or to which information about a location (30) of the another communication device (12-2) is to be exposed.

5. The method of claim 4, wherein the transmitted sidelink service request (26) includes auser information field that indicates an application layer identifier of the client (14), wherein the application layer identifier identifies the client (14) as a sidelink positioning or ranging enabled communication device (12-1 ) within a context of a specific application.

6. The method of any of claims 1-5, wherein the received sidelink service request (18) includes a user information field that indicates an application layer identifier of the client (14), wherein the application layer identifier identifies the client (14) as a sidelink positioning or ranging enabled communication device (12-1) within a context of a specific application.

7. The method of any of claims 1-6, wherein the received sidelink service request (18): is received at a sidelink positioning or ranging layer of a protocol stack at the communication device (12-1) and / or is handled as application layer traffic by the communication device (12-1); and / or is received over a sidelink with the client (14).

8. The method of any of claims 1-7, wherein: the communication device (12-1 ) is the target communication device (12T), wherein the sidelink service request (18) is received from a reference communication device that is to support sidelink positioning or ranging of the target communication device (12T); or the communication device (12-1 ) is a reference communication device that is to support sidelink positioning or ranging of the target communication device (12T), wherein the sidelink service request (18) is received from the target communication device (12T); or the communication device (12-1 ) serves as a sidelink positioning server for the sidelink service request (18).

9. The method of any of claims 1-8, wherein the client (14) is a communication device (12- 1) and is a sidelink positioning client for the sidelink service request (18).

10. The method of any of claims 1-9, wherein the privacy profile (22) comprises locally configured privacy verification information.

11. A method performed by a communication device (12-1), the method comprising: receiving (700) a sidelink service request (18) that requests sidelink positioning or ranging of a target communication device (12T) and that identifies a client (14) to which information about a position or range (16) of the target communicationdevice (12T) is to be provided according to the sidelink service request (18); and transmitting (710), to another communication device (12-2), a message that identifies the client (14) to which the position or range (16) of the target communication device (12T) is to be provided and / or to which information about a location (30) of the another communication device (12-2) is to be exposed.

12. The method of claim 11 , wherein the communication device (12-1): is the target communication device (12T); is a reference communication device (12-1) that is to support sidelink positioning or ranging of the target communication device (12T); or serves as a sidelink positioning server for the sidelink service request (18).

13. The method of any of claims 11 -12, wherein the another communication device (12-2) is the target communication device (12T) or a reference communication device that is to support sidelink positioning or ranging of the target communication device (12T).

14. The method of any of claims 11 -13, wherein the sidelink service request (18) and / or the message includes a user information field that indicates an application layer identifier of the client (14), wherein the application layer identifier identifies the client (14) as a sidelink positioning or ranging enabled communication device within a context of a specific application.

15. The method of any of claims 11 -14, wherein the sidelink service request (18) is received from: the client (14); or a positioning server for the sidelink service request (18).

16. The method of any of claims 11 -15, wherein the sidelink service request (18): is received at a sidelink positioning or ranging layer of a protocol stack at the communication device (12-1) and / or is handled as application layer traffic by the communication device (12-1); and / or is received over a sidelink (21) with the client (14).

17. The method of any of claims 11 -16, wherein the client (14) is a communication device and is a sidelink positioning client for the sidelink service request (18).

18. The method of any of claims 11 -17, further comprising obtaining a privacy profile (22) governing the communication device (12-1) and performing privacy verification to determinewhether or not the privacy profile (22) allows information about a location (20) of the communication device (12-1 ) to be exposed to the client (14), wherein the privacy verification passes based on the privacy profile (22) allowing information about a location (20) of the communication device (12-1 ) to be exposed to the client (14), and wherein the message is transmitted based on the privacy verification passing.

19. The method of any of claims 11 -18, further comprising: obtaining information about the position or range (16) of the target communication device (12T), wherein the information about the position or range (16) of the target communication device (12T) reveals information about the location (20) of the communication device (12-1); and transmitting the obtained information in a response to the sidelink service request (18).

20. The method of claim 19, wherein said obtaining comprises performing a sidelink positioning or ranging operation to determine, or assist with determining, the information about a position or range (16) of the target communication device (12T).21 . A method performed by a communication device (12-2), the method comprising: receiving (600), from another communication device (12-1 ), a message that identifies a client (14) to which information about a position or range (16) of a target communication device (12T) is to be provided and / or to which information about a location (30) of the communication device (12-2) is to be exposed; obtaining (610) a privacy profile (32) governing the communication device (12-2); performing (620) privacy verification to determine whether or not the privacy profile (32) allows information about the location (30) of the communication device (12-2) to be exposed to the client (14); and handling (630) the message based on a result of the privacy verification.

22. The method of claim 21 , wherein said handling comprises transmitting a response to the message based on a result of the privacy verification.

23. The method of claim 22, wherein the response indicates the result of the privacy verification.

24. The method of any of claims 21 -23, wherein said handling comprises, responsive to the privacy verification passing based on the privacy profile (22) allowing information about the location (30) of the communication device (12-2) to be exposed to the client (14), performing asidelink positioning or ranging operation to determine, or assist with determining, information about a position or range (16) of the target communication device (12T).

25. The method of any of claims 21 -24, wherein the received message includes a user information field that indicates an application layer identifier of the client (14), wherein the application layer identifier identifies the client (14) as a sidelink positioning or ranging enabled communication device within a context of a specific application.

26. The method of any of claims 21 -25, wherein the received message: is received at a sidelink positioning or ranging layer of a protocol stack at the communication device (12-2) and / or is handled as application layer traffic by the communication device (12-2); and / or is received over a sidelink with a reference communication device (12-1 ) that is to support sidelink positioning or ranging of the target communication device (12T).

27. The method of any of claims 21 -26, wherein the privacy profile (22) comprises locally configured privacy verification information.

28. A communication device (12-1 ) configured to: receive a sidelink service request (18) that requests sidelink positioning or ranging of a target communication device (12T) and that identifies a client (14) to which information about a position or range (16) of the target communication device (12T) is to be provided according to the sidelink service request (18); obtain a privacy profile (22) governing the communication device (12-1); perform privacy verification to determine whether or not the privacy profile (22) allows information about a location (20) of the communication device (12-1) to be exposed to the client (14); and handle the sidelink service request (18) based on a result of the privacy verification.

29. The communication device (12-1) of claim 28, configured to perform the method of any of claims 2-10.

30. A communication device (12-1 ) configured to: receive a sidelink service request (18) that requests sidelink positioning or ranging of a target communication device (12T) and that identifies a client (14) to which information about a position or range (16) of the target communication device (12T) is to be provided according to the sidelink service request (18); andtransmit, to another communication device (12-2), a message that identifies the client (14) to which the position or range (16) of the target communication device (12T) is to be provided and / or to which information about a location (30) of the another communication device (12-2) is to be exposed.31 . The communication device (12-1 ) of claim 30, configured to perform the method of any of claims 12-20.

32. A communication device (12-2) configured to: receive, from another communication device (12-1), a message that identifies a client (14) to which information about a position or range (16) of a target communication device (12T) is to be provided and / or to which information about a location (30) of the communication device (12-2) is to be exposed; obtain a privacy profile (32) governing the communication device (12-2); perform privacy verification to determine whether or not the privacy profile (32) allows information about the location (30) of the communication device (12-2) to be exposed to the client (14); and handle the message based on a result of the privacy verification.

33. The communication device (12-2) of claim 32, configured to perform the method of any of claims 22-27.

34. A computer program comprising instructions which, when executed by at least one processor of a communication device (12-1 , 12-2), causes the communication device (12-1 , 12- 2) to perform the method of any of claims 1-27.

35. A carrier containing the computer program of claim 34, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

36. A communication device (12-1 ) comprising: communication circuitry; and processing circuitry configured to: receive a sidelink service request (18) that requests sidelink positioning or ranging of a target communication device (12T) and that identifies a client (14) to which information about a position or range (16) of the target communication device (12T) is to be provided according to the sidelink service request (18); obtain a privacy profile (22) governing the communication device (12-1);perform privacy verification to determine whether or not the privacy profile (22) allows information about a location (20) of the communication device (12-1) to be exposed to the client (14); and handle the sidelink service request (18) based on a result of the privacy verification.

37. The communication device (12-1) of claim 36, the processing circuitry configured to perform the method of any of claims 2-10.

38. A communication device (12-1 ) comprising: communication circuitry; and processing circuitry configured to: receive a sidelink service request (18) that requests sidelink positioning or ranging of a target communication device (12T) and that identifies a client (14) to which information about a position or range (16) of the target communication device (12T) is to be provided according to the sidelink service request (18); and transmit, to another communication device (12-2), a message that identifies the client (14) to which the position or range (16) of the target communication device (12T) is to be provided and / or to which information about a location (30) of the another communication device (12-2) is to be exposed.

39. The communication device (12-1 ) of claim 38, the processing circuitry configured to perform the method of any of claims 12-20.

40. A communication device (12-2) comprising: communication circuitry; and processing circuitry configured to: receive, from another communication device (12-1 ), a message that identifies a client (14) to which information about a position or range (16) of a target communication device (12T) is to be provided and / or to which information about a location (30) of the communication device (12-2) is to be exposed; obtain a privacy profile (32) governing the communication device (12-2); perform privacy verification to determine whether or not the privacy profile (32) allows information about the location (30) of the communication device (12-2) to be exposed to the client (14); and handle the message based on a result of the privacy verification.41 . The communication device (12-2) of claim 40, the processing circuitry configured toperform the method of any of claims 22-27.

Images