Authorization communications for positioning or sensing procedures

Abstract

Some examples of the techniques described herein may provide approaches for managing positioning or sensing procedures. For instance, a network entity may manage authorization or consent for positioning or sensing procedures. In some scenarios, a network node may request that a wireless device collect positioning or sensing measurements. The wireless device may query the network entity to determine whether the request from the network node is authorized. In some scenarios, a network node may seek authorization from the network entity for the network node to request that a wireless device collect positioning or sensing measurements. The network entity may obtain information regarding consent or one or more restrictions for positioning or sensing procedures. For instance, the network entity may obtain information indicating that a user equipment (UE) in an area does not authorize positioning or sensing, or one or more parameters for positioning or sensing.

Description

Qualcomm Ref. No. 2408019 WO1AUTHORIZATION COMMUNICATIONS FOR POSITIONING OR SENSING PROCEDURES CROSS REFERENCE

[0001] The present Application for Patent claims priority to Greek Patent Application No. 20250100057 by MANOLAKOS et al., entitled “ AUTHORIZATION COMMUNICATIONS FOR POSITIONING OR SENSING PROCEDURES,” filed January 27, 2025, assigned to the assignee hereof, and expressly incorporated by reference in its entirety herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including authorization communications for positioning or sensing procedures.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various ty pes of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transfomi spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO2SUMMARY

[0004] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0005] A method by a wireless device is described. The method may include obtaining a request to collect information that is based on a measurement for a positioning or sensing procedure, outputting, to a network entity, a request authorization query' associated with the request, where the request authorization query' indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof, and obtaining, from the network entity7, an indication of whether the request is authorized.

[0006] A wireless device is described. The wireless device may include one or more transceivers, one or more memory, and one or more processors coupled to the one or more memory and the one or more transceivers. The one or more processors may be configured to obtain a request to collect information that is based on a measurement for a positioning or sensing procedure, output, to a network entity7, a request authorization query associated with the request, where the request authorization query indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a ty pe of the information, an area corresponding to the request, a condition for the request, or any combination thereof, and obtain, from the network entity, an indication of whether the request is authorized.

[0007] Another wireless device is described. The wireless device may include means for obtaining a request to collect information that is based on a measurement for a positioning or sensing procedure, means for outputting, to a network entity7, a request authorization query7associated with the request, where the request authorization query indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a conditionAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO3for the request, or any combination thereof, and means for obtaining, from the network entity, an indication of whether the request is authorized.

[0008] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to obtain a request to collect information that is based on a measurement for a positioning or sensing procedure, output, to a network entity, a request authorization query associated with the request, where the request authorization query indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof, and obtain, from the network entity, an indication of whether the request is authorized.

[0009] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the indication of whether the request may be authorized indicates that the request may be not authorized and indicates one or more permitted responses to the request.

[0010] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining a second request to collect second information that may be based on a second measurement for a second positioning or sensing procedure, w here the second request includes an authorization message and performing a validation procedure based on the authorization message.

[0011] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, from the network entity, configuration information indicating one or more candidate attributes for a second positioning or sensing procedure, the one or more candidate attributes including a candidate area, a candidate device that may be authorized to request a start or end of the second positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity' timer, a candidate invalidity' event, or any combination thereof.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO4

[0012] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the netw ork entity, an indication of a selection of the one or more candidate attributes for the second positioning or sensing procedure and obtaining, from the net ork entity, an acceptance or a denial of the selection of the one or more candidate attributes.

[0013] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, from the network entity, an indication of a second selection of the one or more candidate attributes, where the indication of the second selection may be based on the denial of the selection of the one or more candidate attributes.

[0014] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the network entity, an indication of a rejection of at least one of the one or more candidate attributes for the second positioning or sensing procedure and outputting, to the netw ork entity, an indication of one or more second candidate attributes for the second positioning or sensing procedure.

[0015] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for communicating information indicating that a second positioning or sensing procedure may be unauthorized, or indicating one or more unauthorized attributes for a second positioning or sensing procedure, the one or more unauthorized attributes including an unauthorized area, an unauthorized device for the positioning or sensing procedure, an unauthorized type of measurement information, an unauthorized information granularity, an unauthorized duration, an unauthorized purpose, or any combination thereof.

[0016] A method by a network node is described. The method may include outputting, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or moreAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO5parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a ty pe of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof and obtaining, from the network entity, an indication of whether the authorization request is accepted.

[0017] A network node is described. The network node may include one or more transceivers, one or more memory, and one or more processors coupled to the one or more memory and the one or more transceivers. The one or more processors may be configured to output, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the netw ork node, an area corresponding to the authorization request, or any combination thereof and obtain, from the network entity', an indication of whether the authorization request is accepted.

[0018] Another network node is described. The network node may include means for outputting, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a ty pe of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof and means for obtaining, from the network entity, an indication of whether the authorization request is accepted.

[0019] A non-transitoiy computer-readable medium storing code is described. The code may include instructions executable by one or more processors to output, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO6authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof and obtain, from the network entity, an indication of whether the authorization request is accepted.

[0020] In some examples of the method, network nodes, and non-transitory computer-readable medium described herein, the indication of whether the authorization request may be accepted indicates that the authorization request may be not accepted and indicates one or more permitted parameters.

[0021] In some examples of the method, network nodes, and non-transitory computer-readable medium described herein, the indication of whether the authorization request may be accepted indicates a prioritization or a different positioning or sensing procedure.

[0022] Some examples of the method, network nodes, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the wireless device, a request to collect the information, where the request includes an authorization message from the network entity.

[0023] Some examples of the method, network nodes, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, from the network entity, configuration information indicating one or more candidate parameters for the positioning or sensing procedure, the one or more candidate parameters including a candidate area, a candidate device that may be authorized to request a start or end of the positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

[0024] In some examples of the method, network nodes, and non-transitory computer-readable medium described herein, a session of the positioning or sensing procedure begins or expires by an expiration of a timer from a time of the authorization request.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO7

[0025] A method by a network entity is described. The method may include obtaining an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure, determining whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry, and outputting an indication of whether the authorization inquiry is validated.

[0026] A network entity7is described. The network entity may include one or more transceivers, one or more memory, and one or more processors coupled to the one or more memory and the one or more transceivers. The one or more processors may be configured to obtain an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure, determine whether to validate the authorization inquiry7based on one or more attributes or parameters of the authorization inquiry, and output an indication of whether the authorization inquiry is validated.

[0027] Another network entity is described. The network entity may include means for obtaining an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure, means for determining whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry, and means for outputting an indication of whether the authorization inquiry is validated.

[0028] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to obtain an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure, determine whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry', and output an indication of whether the authorization inquiry' is validated.

[0029] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the authorization inquiry may be a request authorization query7associated with a request from a source to the wireless device to collect the information, the one or more attributes of the request including an identifierAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO8of the source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof, and the determination whether to validate the authorization inquiry may be based on a satisfaction of a validation criterion by the one or more attributes.

[0030] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the indication of whether the authorization inquiry may be validated indicates that the request may be not authorized and indicates one or more permitted responses to the request.

[0031] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the indication of whether the authorization inquiry' may be validated may include operations, features, means, or instructions for outputting, to a network node, an authorization message for inclusion in a request from the network node to the wireless device to collect the information that may be based on the measurement at the wireless device for the positioning or sensing procedure.

[0032] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the wireless device, configuration information indicating one or more candidate attributes for a second positioning or sensing procedure, the one or more candidate attributes including a candidate area, a candidate device that may be authorized to request a start or end of the second positioning or sensing procedure, a candidate t pe of measurement information, a candidate information granularity, a candidate validity area, a candidate validity' timer, a candidate invalidity7event, or any combination thereof.

[0033] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, from the wireless device, an indication of a selection of the one or more candidate attributes for the second positioning or sensing procedure and outputting, to the wireless device, an acceptance or a denial of the selection of the one or more candidate attributes.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO9

[0034] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the wireless device, an indication of a second selection of the one or more candidate attributes, where the denial of the selection of the one or more candidate attributes may be output.

[0035] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, from the wireless device, an indication of a rejection of at least one of the one or more candidate attributes for the second positioning or sensing procedure and obtaining, from the wireless device, an indication of one or more second candidate attributes for the second positioning or sensing procedure.

[0036] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for communicating information indicating that a second positioning or sensing procedure may be unauthorized, or indicating one or more unauthorized attributes for a second positioning or sensing procedure, the one or more unauthorized attributes including an unauthorized area, an unauthorized device for the positioning or sensing procedure, an unauthorized type of measurement information, an unauthorized information granularity, an unauthorized duration, an unauthorized purpose, or any combination thereof.

[0037] In some examples of the method, netw ork entities, and non-transitory computer-readable medium described herein, the authorization inquiry may be an authorization request from a network node for obtaining the information that may be based on a measurement at the wireless device for the positioning or sensing procedure and the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from w hich the information may be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the netw ork node, an area corresponding to the authorization request, or any combination thereof.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO10

[0038] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the indication of whether the authorization inquiry may be validated indicates that the authorization inquiry may be not validated and indicates one or more permitted parameters.

[0039] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the indication of whether the authorization inquiry7may be validated indicates a prioritization or a different positioning or sensing procedure.

[0040] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to a network node, configuration information indicating one or more candidate parameters for the positioning or sensing procedure, the one or more candidate parameters including a candidate area, a candidate device that may be authorized to request a start or end of the positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

[0041] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for initiating a timer based on a time of the authorization inquiry, obtaining, from a location server, identification information of the wireless device, outputting, to the wireless device based on the identification information, an inquiry7of whether the wireless device accepts the positioning or sensing procedure, and obtaining, from the wireless device, an indication of whether the wireless device accepts the positioning or sensing procedure, where a session of the positioning or sensing procedure begins or expires by an expiration of the timer from the time of the authorization inquiry.

[0042] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the descnption below. Other features, aspects, and advantages will become apparent from the description, theAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO11drawings, and the claims. Note that the relative dimensions of the following figures may not be draw n to scale.BRIEF DESCRIPTION OF THE DRAWINGS

[0043] FIG. 1 shows an example of a wireless communications system that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0044] FIG. 2 show s an example of a netw ork structure that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0045] FIG. 3 shows an example of a network architecture that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0046] FIG. 4 shows an example of a wireless communications system that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0047] FIG. 5 shows an example of a wireless communications system that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0048] FIG. 6 shows an example of a process flow that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0049] FIG. 7 shows an example of a process flow that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0050] FIG. 8 shows an example of a process flow that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO12

[0051] FIGs. 9 and 10 show block diagrams of devices that support authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0052] FIG. 11 shows a block diagram of a communications manager that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0053] FIG. 12 show s a diagram of a system including a device that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0054] FIGs. 13 and 14 show block diagrams of devices that support authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0055] FIG. 15 show s a block diagram of a communications manager that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0056] FIG. 16 shows a diagram of a system including a device that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0057] FIGs. 17 through 22 show flowcharts illustrating methods that support authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0058] FIG. 23 shows examples of wireless communications systems that support authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.

[0059] FIG. 24 shows examples of sensing modes that support authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO13DETAILED DESCRIPTION

[0060] Some wireless communications systems perform positioning or sensing procedures to locate or sense one or more objects. Examples of objects may include humans (e.g.. users), non-human objects, static objects, or moving objects. Some scenarios for positioning or sensing procedures may relate to potential confidentiality issues, such as users with user equipments (UEs) that are connected to a mobile network operator (MNO), UEs without human users that are connected to an MNO, human users (with or without UEs) that are not connected to the MNO, or a selected area as a whole. Consent or transparency may be challenges for when UEs are positioned, sensed, or involved in positioning or sensing for public or restricted places (e.g., restricted from governments, concerned authorities, or other parties). Consent or transparency may be significant aspects for one or more scenarios (e.g., scenarios with data involving personally identifiable information (PII)).

[0061] Some examples of the techniques described herein may provide approaches for managing positioning or sensing procedures. For instance, a network entity may manage authorization or consent for positioning or sensing procedures. In some scenarios, a network node may request that a wireless device collect positioning or sensing measurements. The wireless device may query the network entity to determine whether the request from the network node is authorized. In some scenarios, a network node may seek authorization from the network entity for the network node to request that a wireless device collect positioning or sensing measurements. The network entity may obtain information regarding consent or one or more restrictions for positioning or sensing procedures. For instance, the network entity may obtain information indicating that a UE in an area does not authorize positioning or sensing, or one or more parameters for positioning or sensing. The network entity may respond to the communications from the UEs or network node(s) to manage authorization (e.g., to validate, accept, or deny authorization) for collecting positioning or sensing measurements. Some examples of the techniques described herein may provide approaches for managing authorization or consent to improve information (e.g., sensing or positioning measurement(s)) security7, to reduce network or device susceptibility to imposter devices, or to improve consent procedures for information collection.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO14

[0062] Aspects of the disclosure are described in the context of wireless communications systems. Aspects of the disclosure are also described in the context of a wireless network structure. Aspects of the disclosure are further described in the context of a network architecture. Aspects of the disclosure are additionally described in the context of process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, flowcharts, and diagrams that relate to authorization communications for positioning or sensing procedures.

[0063] FIG. 1 shows an example of a wireless communications system 100 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network nodes 105), one or more UEs 115. and a core network 130. In some examples, the wireless communications system 100 may be an LTE network, an LTE- Advanced (LTE- A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0064] The network nodes 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network node 105 may be referred to as a network element, a network entity, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network nodes 105 and UEs 115 may wirelessly communicate via communication link(s) 125 (e.g., a radio frequency (RF) access link). For example, a network node 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network node 105 may establish the communication link(s) 125. The coverage area 110 may be an example of a geographic area over which a network node 105 and a UE 115 may support the communication of signals according to one or more RATs.

[0065] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO15both at different times. The UEs 115 may be devices in different forms or have different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network nodes 105), as shown in FIG. 1.

[0066] As described herein, anode of the wireless communications system 100, which may be referred to as a network entity or a wireless node, may be a network node 105 (e.g., any network node described herein), aUE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network node 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network node 105, and the third node may be another UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network node 105, and the third node may be another network node 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network node 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network node 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network node 105 also discloses that a first node is configured to receive information from a second node.

[0067] In some examples, network nodes 105 may communicate with a core network 130, or with one another, or both. For example, network nodes 105 may communicate with the core network 130 via wired or wireless backhaul communication link(s) 120 (e.g., in accordance with an SI, N2, N3, or other interface protocol). In some examples, network nodes 105 may communicate with one another via backhaul communication link(s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network nodes 105) or indirectly (e.g., via the core network 130). In some examples, network nodes 105 may communicate with one another via a midhaul communication link 162 (e.g.. in accordance with aAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO16midhaul interface protocol) or a fronthaul communication link 1 8 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication link(s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0068] One or more of the network nodes 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point (AP), a radio transceiver, aNodeB, an eNodeB (eNB), a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network node 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network node (e.g., a network node 105 or a single RAN node, such as a base station 140).

[0069] In some examples, a network node 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network nodes 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network node 105 may include one or more of a central unit (CU), such as a CU 160, a distributed unit (DU), such as a DU 165. a radio unit (RU), such as an RU 170, a RAN Intelligent Controller (RIC), such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission-reception point (TRP). One or more components ofAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO17the network nodes 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network nodes 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the network nodes 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0070] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g.. Radio Resource Control (RRC), service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 1 0 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs). or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170). In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g. , F 1 interface, F 1 -c interface, or F 1 -u, among other examples), and a DU 165Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO18may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network nodes 105) that are in communication via such communication links.

[0071] In some wireless communications systems (e.g., the wireless communications system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more of the network nodes 105 (e.g., network nodes 105 or IAB node(s) 104) may be partially controlled by each other. The IAB node(s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network node 105 or base station 140 (such as a donor network node or a donor base station). The one or more donor entities (e g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node(s) 104) via supported access and backhaul links (e.g., backhaul communication link(s) 120). IAB node(s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node(s) 104 used for access via the DU 165 of the IAB node(s) 104 (e g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB node(s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node(s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node(s) 104 or components of the IAB node(s) 104) may be configured to operate according to the techniques described herein.

[0072] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB node(s) 104, and one or more UEs 115. The IAB donor may facilitate connection betw een the core netw ork 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donorAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO19may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node(s) 104 may communicate via an Fl interface according to a protocol that defines signaling messages (e.g., an Fl AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g.. including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.

[0073] IAB node(s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node(s) 104, and the 1AB-MT may act as a scheduled node towards parent nodes associated with IAB node(s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node(s) 104). Additionally, or alternatively, IAB node(s) 104 may also be referred to as parent nodes or child nodes to other IAB node(s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node(s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node(s) 104) to receive signaling from a parent IAB node (e.g., the IAB node(s) 104), and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.

[0074] For example, IAB node(s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link(s) 120) to the core network 130 and may act as a parent node to IAB node(s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node(s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an Fl interface to IAB node(s) 104, and the IAB node(s) 104 may schedule transmissions (e.g., transmissions to the UEs 115Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO20relayed from the TAB donor) through one or more DUs (e.g., DUs 165). That is, data may be relayed to and from IAB node(s) 104 via signaling via an NR Uu interface to MT of IAB node(s) 104 (e.g., other IAB node(s)). Communications with IAB node(s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node(s) 104.

[0075] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support testing as described herein. For example, some operations described as being performed by a UE 115 or a network node 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

[0076] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the "‘device"’ may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

[0077] The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network nodes 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as show n in FIG. 1.

[0078] The UEs 115 and the netw ork nodes 105 may wirelessly communicate with one another via the communication link(s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link(s) 125. For example, a carrier used for the communication link(s)Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO21125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a netw ork node 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity ) of a network node 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network node 105, may refer to any portion of a network node 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network nodes 105).

[0079] In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT).

[0080] The communication link(s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network node 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from aUE 115 to a network node 105, or both, among other configurations of transmissions.Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may¬ be configured to carry downlink and uplink communications (e.g., in a TDD mode).Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO22

[0081] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth"’ of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system 100 (e.g., the network nodes 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network nodes 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

[0082] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

[0083] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Af ) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for aAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO23carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.

[0084] The time intervals for the network nodes 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / ^fmax’ Nf) seconds, for which fmaxmay represent a supported subcarrier spacing, and N may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0085] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g.. in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0086] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity’ of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0087] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexingAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO24(FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g.. one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE).

[0088] A network node 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell'’ may refer to a logical communication entity used for communication with a network node 105 (e.g.. using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network node 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

[0089] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network node 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g.. licensed, unlicensed) frequency bands as macro cells. SmallAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO25cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network node 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.

[0090] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband loT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

[0091] In some examples, a network node 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network node (e.g., a network node 105). In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network nodes 105). The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network nodes 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0092] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network nodes 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network nodes 105) may be approximately aligned in time. For asynchronous operation, network nodes 105 may have different frame timings, and transmissions from different network entities (e g., different ones of network nodes 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

[0093] Some UEs 115, such as MTC or loT devices, may be relatively low cost or low complexity' devices and may provide for automated communication betweenAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO26machines (e g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network node 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0094] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol t pe that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

[0095] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and suchAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO27services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0096] In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network node 105 (e.g.. a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network node 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network node 105 or may be otherwise unable to or not configured to receive transmissions from a network node 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1:M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network node 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network node 105.

[0097] In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network entities (e.g., network nodes 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.

[0098] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO28(5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network nodes 105 (e.g.. base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0099] The wireless communications system 100 may include a location server 185 (e.g., LMF). The location server 185 may provide positioning, location, or tracking functions. For instance, the location server 185 may participate in one or more positioning procedures to determine a location of (e.g., coordinates of, relative distance(s) to, or an address of) one or more of the UEs 115. Examples of positioning procedures may include one or more operations of assisted global navigation satellite system (A-GNSS), observed time difference of arrival (OTDOA), enhanced cell identifier (E-CID), sensor-based positioning, wireless local area network (WLAN)-based positioning, Bluetooth-based positioning, terrestrial beacon systems (TBS) positioning, downlink time difference of arrival (DL-TDOA), downlink angle of departure (DL-AOD), multi-round-trip time (Multi-RTT), New Radio enhanced cell identifier (NR E-CID), uplink time difference of arrival (UL-TDOA), and uplink angle of arrival (UL-AOA), among other examples. Some examples of the positioning procedures may be managed by. assisted by. or performed with the location server 185. For instance, measurements associated with reference signaling may be provided to the location server 185, which may estimate a location of a UE 115 based on the measurements. In some aspects, the location server 185 may track or store location information corresponding to one or more UEs 115. Some examples of the positioning procedures may be performed without the location server 185.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO29

[0100] The location server 185 may be included in the core network 130 or may be separate from the core network 130. In some examples, a location server 185 may be a standalone device or may be included in (e.g., integrated with) a network node 105, a base station 140, a UE 115, a satellite 190, a server, or another device. For instance, the location server 185 may be (or may be included in) a secure user plane location (SUPL) location platform (SLP) device, a third-party server, or another device. The location server 185 may generally refer to a positioning device, a location device, a computing device, or a server, among other examples.

[0101] A UE 115 may communicate with the location server 185 directly or indirectly. For example, a UE 115 may communicate with the location server 185 via a network node 105 that is serving the UE 115 and via the core network 130.Additionally, or alternatively, a UE 115 may communicate with the location server 185 through another path (e.g., via an application server (not shown)) or via another network (e.g., via a WLAN AP), among other examples. Communication between a UE 115 and the location server 185 may be represented via an indirect connection (e g., through a communication link 125, a network node 105, a communication link 155, a backhaul communication link 120, or the core network 130) or as a direct connection, with one or more intervening nodes (if any) omitted for concision or convenience.

[0102] A satellite 190 may be an aerial or space vehicle with signaling capability. In some examples, the wireless communications system 100 may include or communicate with one or more satellites 190. The satellite(s) 190 may be included in one or more satellite positioning systems (e.g., GNSS(s)). A satellite positioning system may include any combination of one or more global or regional navigation satellites associated with one or more satellite positioning systems (e.g., global positioning system (GPS), global navigation satellite system (GLONASS), BeiDou navigation satellite system (BDS), or Galileo, among other examples). A satellite positioning system may include satellites 190 or other transmitters positioned to enable receivers (e.g., UEs 115) to determine a location on or above the Earth based on signals (e.g., the signals 195) received from the satellites 190. For instance, each satellite 190 may transmit a signal 195 marked with a repeating pseudo-random noise (PN) code of a set quantity of chips. In some cases, one or more transmitters located on ground-based control stations, network nodes 105, or UEs 115 may transmit signals for enabling a UE 115 to determine a location.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO30

[0103] A UE 115 may include one or more receivers designed to receive the signal(s) 195 from the satellite(s) 190 for determining location information (e.g., a geographic location of the UE 115). For instance, the UE 115 may receive one or more signals 195 from the satellite(s) 190. which may be utilized to determine a location of the UE 115.

[0104] In a satellite positioning system, the use of signals 195 may be augmented with one or more satellite-based augmentation systems (SBAS) that may be associated with or enabled for use with one or more global or regional navigation satellite systems. An SBAS may provide integrity information, differential corrections, or other information for use in conjunction with a satellite positioning system. An SBAS may include one or more augmentation systems, such as the Wide Area Augmentation System (WAAS), the European Geostationary' Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS). or the GPS Aided Geo Augmented Navigation (GAGAN) system, among other examples.

[0105] In some aspects, the satellite(s) 190 may be included in one or more nonterrestrial networks (NTNs). In an NTN, a satellite 190 may communicate with one or more devices (e.g., network entities, ground stations, NTN gateways, or gateways) located on or above the Earth. For example, the satellite 190 may send or receive one or more communications 192 with a network node 105. In some aspects, the communication(s) 192 may include one or more signals relayed to or from a UE 115. Additionally, or alternatively, the satellite 190 may communicate with another terrestrial device that is connected to one or more elements of the wireless communications system 100. For instance, the satellite 190 may communicate with a ground station or NTN gateway, which may provide access to the wireless communications system 100 or one or more other entities (e.g., Internet web servers or one or more other user devices) external to the wireless communications system 100. In some examples, aUE 115 may receive communication signals 195 from the satellite 190 instead of, or in addition to, communication signals from a terrestrial network entity.

[0106] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO31approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very7high frequency (VHF) portion of the spectrum below 300 MHz.

[0107] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network nodes 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

[0108] The wireless communications system 100 may utilize licensed or unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network nodes 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.Attorney Docket No. PB0022GR.WO (.114958.TBD)Qualcomm Ref. No. 2408019 WO32

[0109] A network node 105 (e.g., a base station 140, an RU 170) or a UE 1 15 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity', multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network node 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network node 105 may be located at diverse geographic locations. A network node 105 may include an antenna array with a set of rows and columns of antenna ports that the network node 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0110] The network nodes 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas.Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO). for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO). for which multiple spatial layers are transmitted to multiple devices.[OHl] Beamforming, which may also be referred to as spatial fdtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network node 105, aUE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatialAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO33path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0112] A network node 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, anetwork node 105 (e.g., abase station 140. an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with aUE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by anetwork node 105 multiple times along different directions. For example, the network node 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network node 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network node 105.

[0113] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a network node 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network node 105 or UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network node 105 along different directions and may report to the network node 105 anAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO34indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.

[0114] In some examples, transmissions by a device (e.g., by a network node 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network node 105 to a UE 115). The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network node 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network node 105 (e.g., a base station 140, an RU 170), a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

[0115] A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network node 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g.. different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as ‘‘listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receiveAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO35configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal -to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0116] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network node 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0117] The UEs 115 and the network nodes 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link(s) 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC). and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0118] Some wireless communications systems perform positioning or sensing procedures to locate or sense one or more objects. Examples of objects (e.g., categorizations of sensing targets) may include humans (e.g., users), non-human Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO36objects, static objects, or moving objects. Some scenarios for positioning or sensing procedures may include users with UEs 115 that are connected to an MNO (e.g., with use cases such as sleep or health monitoring, or use cases where biometric PII may be utilized, where confidentiality may be an issue). UEs 115 without human users that are connected to an MNO (e.g., where confidentiality may be an issue), human users (with or without UEs 115) that are not connected to the MNO (e.g., where confidentiality may be an issue), or a selected area as a whole (e g., an area of an organization or other area including human or non-human objects, where confidentiality may be an issue).Consent or transparency may be challenges for when UEs 115 are positioned, sensed, or involved in positioning or sensing for public or restricted places (e.g., restricted from governments, concerned authorities, or other parties). Consent or transparency may be significant aspects for one or more scenarios (e.g., scenarios with data involving PII).

[0119] Some examples of the techniques described herein may provide approaches for managing positioning or sensing procedures. For instance, a network entity (e.g., a location server 185, a sensing management entity, a security entity, or another network entity) may manage authorization or consent for positioning or sensing procedures. In some scenarios, a network node 105 may request that a wireless device (e.g., a UE 115) collect positioning or sensing measurements. The wireless device may query the network entity to determine whether the request from the network node 105 is authorized. In some scenarios, a network node 105 may seek authorization from the network entity for the network node 105 to request that a wireless device collect positioning or sensing measurements. The network entity may obtain information regarding consent or one or more restrictions for positioning or sensing procedures. For instance, the network entity may obtain information indicating that a UE 115 in an area does not authorize positioning or sensing, or one or more parameters for positioning or sensing. The network entity may respond to the communications from the UEs 115 or network node(s) 105 to manage authorization (e.g., to validate, accept, or deny authorization) for collecting positioning or sensing measurements. Some examples of the techniques described herein may provide approaches for managing authorization or consent to improve information (e.g., sensing or positioning measurement(s)) security, to reduce network or device susceptibility to imposter devices, or to improve consent procedures for information collection.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO37

[0120] As used herein, the terms “Al,” “AI / ML,” “Al-based,” or “ML-based” may refer to Al or machine learning techniques. The term “Al model” may refer to one or more Al models (with or without machine learning) or to one or more machine learning models. As used herein, an Al model may be referred to as an “Al-based model,” an “ML model,” or an “ML-based model.”

[0121] FIG. 2 shows an example of a network structure 200 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The wireless network structure 200 may include a core network 130-a, a RAN 225. a UE 115-a, an LMF 265, an external device 230 (e.g., third-party device or server), or an SLP 235. In some examples, the wireless network structure 200 may be included in the wireless communications system 100 described with reference to FIG. 1. The core network 130-a may be an example of the core network 130, the UE 115-a may be an example of the UEs 115, or the LMF 265 may be an example of the location server 185, as described with reference to FIG. 1.

[0122] The core network 130-a may provide one or more control plane (C-plane) functions (e.g., UE registration, authentication, network access, or gateway selection, among other examples) or one or more user plane (U-plane) functions (e.g., UE gateway function, data network access, or IP routing, among other examples). One or more of the functions of the core network 130-a may be implemented in one or more devices (e.g., one or more electronic devices, computing devices, servers, among other examples) in hardware (e.g., circuitry) or a combination of hardware and instructions (e.g., a processor with instructions). The core network 130-a may be an EPC, 5GC, or a Next Generation Core (NGC). among other examples.

[0123] The core network 130-a may provide an AMF 210, a session management function (SMF) 220, or a user plane function (UPF) 215. The AMF 210 may provide one or more C-plane functions, such as registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 115-a and the SMF 220, transparent proxy sendees for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 115-a and the short message service function (SMSF) (not shown in FIG. 2), or security anchor functionality (SEAF) (not shown in FIG. 2). among Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO38other examples. In some aspects, the AMF 210 may interact with an authentication server function (AUSF) (not shown in FIG. 2) and the UE 115-a, and may receive an intermediate key established as a result of a UE 115-a authentication process. In a case of authentication based on a universal mobile telecommunications system (UMTS) subscriber identity module (USIM), the AMF 210 may retrieve security information from the AUSF. In some examples, the AMF 210 may provide a security context management (SCM) function. The SCM function may receive a key from the SEAF that may be utilized to derive access-network specific keys. The AMF 210 may provide location services management for regulatory services, transport for location services messages between the UE 115-a and an LMF 265, transport for location services messages between the RAN 225 and the LMF 265, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, or UE 115-a mobility event notification. In some approaches, the AMF 210 may support one or more functionalities for Third Generation Partnership Project (3GPP) access networks or non-3GPP access networks.

[0124] The UPF 215 may provide one or more U-plane functions, such as acting as an anchor point for intra / inter-RAT mobility, acting as an external protocol data unit (PDU) session point of interconnection to a data network (not shown in FIG. 2), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, or traffic steering), user plane collection (e.g., interception), traffic usage reporting, quality of service (QoS) handling for the U-plane (e.g., uplink or downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (e.g., service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink or downlink, downlink packet buffering, downlink data notification triggering, or sending or forw arding one or more indications of an end of a transmission (e.g., “end markers’") to a source RAN node, among other examples. In some examples, the UPF 215 may support the transfer of location services messages over a U-plane between the UE 115-a and another device (e.g., the SLP 235 or the external device 230.

[0125] The SMF 220 may provide one or more functions, such as session management. UE IP address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 215 to route traffic to aAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO39destination, control (e.g., partial control) of policy enforcement or QoS, or dow nlink data notification. In some aspects, the SMF 220 may communicate with the AMF 210 over an N11 interface 240.

[0126] The RAN 225 may include one or more gNBs 255 or one or more ng-eNBs 260. The gNB(s) 255 or the ng-eNB(s) 260 may be examples of the network nodes 105 described with reference to FIG. 1. For instance, a next generation RAN (NG-RAN) may include one or more gNBs 255, or other examples of the RAN 225 may include one or more ng-eNBs 260 or gNBs 255.

[0127] The core network 130-a may communicate with the RAN 225 via a C-plane interface 245 (e.g.. NG-C or N2 interface) or a U-plane interface 250 (e.g., NG-U or N3 interface). The C-plane interface 245 or the U-plane interface 250 may connect the gNB 255 or the ng-eNB 260 to the core network 130-a (e.g., to one or more control plane functions or one or more user plane functions). For instance, the C-plane interface 245 may connect the AMF 210 to one or more gNBs 255 or ng-eNBs 260 in the RAN 225, or the U-plane interface 250 may connect the UPF 215 to one or more gNBs 255 or ng-eNBs 260 in the RAN 225. The gNB(s) 255 or ng-eNB(s) 260 of the RAN 225 may communicate w ith each other via one or more backhaul communication links 120-a (e.g., Xn-C interface). The backhaul communication link(s) 120-a may be examples of the backhaul communication links 120 described with reference to FIG. 1. One or more of the gNBs 255 or ng-eNBs 260 may communicate with one or more UEs 115-a over one or more communication links 125 -a (e.g., the Uu interface). The communication link(s) 125-amay be examples of the communication links 125 described with reference to FIG. 1.

[0128] The LMF 265 may communicate with the core network 130-a to provide location functionality (e.g., to participate in one or more positioning procedures) for the UE(s) 115-a. The LMF 265 may be an example of the location server 185 described with reference to FIG. 1. The LMF 265 may be implemented as one or more devices (e.g., one or more servers, such as physically separate servers, one or more instruction sets on a single server, or instruction sets distributed across multiple physical servers, among other examples). The LMF 265 may support one or more location services for one or more UEs 115-a that may connect to the LMF 265 via the RAN 225, via the core network 130-a. or via another connection (e.g., the Internet). In some examples, the Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO40LMF 265 may communicate with a UE 115-a or another device via a C-plane connection (e.g., using one or more interfaces or protocols for signaling control information, or separate from voice or payload data). In some aspects, the LMF 265 may be integrated into a component of the core network 130-a or may be external to the core network 130-a (e.g., on an external device 230, such as an original equipment manufacturer (OEM) server or other server).

[0129] In some examples, the SLP 235 may provide location functionality (e.g., may participate in one or more positioning procedures) for the UE(s) 115-a. The SLP 235 may be an example of the location server 185 described with reference to FIG. 1. The SLP 235 may be implemented as one or more devices (e.g., one or more servers, such as physically separate servers, one or more instruction sets on a single server, or instruction sets distributed across multiple physical servers, among other examples). The SLP 235 may support one or more location services for one or more UEs 115-a that may connect to the SLP 235 via the RAN 225, via the core network 130-a, or via another connection (e.g., the Internet). In some examples, the SLP 235 may communicate with a UE 115-a or another device via a U-plane connection (e.g., using one or more interfaces or protocols for signaling voice or payload data, such as a transmission control protocol (TCP) or IP).

[0130] In some examples, the external device 230 may communicate with the LMF 265, the SLP 235, the core network 130-a (e.g., via the AMF 210 or the UPF 215), the RAN 225, or the UE 115-a to obtain location information (e.g., a location estimate) for the UE 115-a. The external device 230 may be referred to as a location services (LCS) client or an external client. The external device 230 may be implemented as one or more devices (e.g., one or more servers, such as physically separate servers, one or more instruction sets on a single server, or instruction sets distributed across multiple physical servers, among other examples). The external device 230 may support one or more location services for one or more UEs 115-a that may connect to the external device 230 via the RAN 225, via the core network 130-a, or via another connection (e.g., the Internet). In some examples,

[0131] In some approaches, the functionality of a gNB 255 may be divided between a CU 160-a, one or more DUs 165-a, or one or more RUs 170-a. The CU 160-a may be an example of the CU 160 described with reference to FIG. 1. the one or more DUs Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO41165-a may be examples of the DU 165 described with reference to FIG. 1 , or the one or more RUs 170-a may be examples of the RU 170 described with reference to FIG. 1. In some examples, the CU 160-a may provide one or more functions, such as transferring user data, mobility control, radio access network sharing, positioning, session management, or others, except for one or more functions allocated exclusively to the DU(s) 165-a. A DU 165-a may support one or more cells. The DUs 165-a may communicate with the CU 160-a via midhaul communication links 162-a (e.g., via the Fl interface). The midhaul communication links 162-a may be examples of the midhaul communication links 162 described with reference to F1G.1. The RUs 170-a may perform one or more functions such as power amplification, signal transmission, or signal reception. The RUs 170-a may communicate with the DUs 165-a via fronthaul communication links 168-a (e.g., via the Fx interface). The fronthaul communication links 168-a may be examples of the fronthaul communication links 168 described with reference to FIG.l. The UE 115-amay communicate with the gNB 255, RU 170-a, or ng-eNB 260 a via communication links 125-a. The communication links 125-a may be examples of the communication links 125 described with reference to FIG.l. The UE 115-a may communicate with the CU 160-a via the RRC, SDAP, and PDCP layers, with a DU 165-a via the RLC and MAC layers, or with an RU 170-a via the PHY layer.

[0132] FIG. 3 shows an example of a network architecture 300 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The network architecture 300 may illustrate an example for implementing one or more aspects of the wireless communications system 100. The network architecture 300 may include one or more CUs 160-b that may communicate directly with a core network 130-b via a backhaul communication link 120-b, or indirectly with the core network 130-b through one or more disaggregated network nodes 105 (e.g., aNear-RT RIC 175-b via an E2 link, or a Non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO Framework), or both). A CU 160-b may communicate with one or more DUs 165-b via respective midhaul communication links 162-b (e.g., an Fl interface). The DUs 165-b may communicate with one or more RUs 170-b via respective fronthaul communication links 168-b. The RUs 170-b may be associated with respective coverage areas 110-a and mayAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO42communicate with UEs 115-b via one or more communication links 125-b. Tn some implementations, aUE 115-b may be simultaneously served by multiple RUs 170-b.

[0133] Each of the network nodes 105 of the network architecture 300 (e.g., CUs 160-b, DUs 165-b, RUs 170-b. Non-RT RICs 175-a, Near-RT RICs 175-b, SMOs 180-a, Open Clouds (O-Clouds) 305, Open eNBs (O-eNBs) 310) may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network node 105, or an associated processor (e.g., controller) providing instructions to an interface of the network node 105, may be configured to communicate with one or more of the other network nodes 105 via the transmission medium. For example, the network nodes 105 may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other network nodes 105. Additionally, or alternatively, the network nodes 105 may include a wireless interface, which may include a receiver, a transmitter, or transceiver (e.g., an RF transceiver) configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other network nodes 105.

[0134] In some examples, a CU 160-b may host one or more higher layer control functions. Such control functions may include RRC, PDCP. SDAP. or the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 160-b. A CU 160-b may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or any combination thereof. In some examples, a CU 160-b may be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an El interface when implemented in an O-RAN configuration. A CU 160-b may be implemented to communicate with a DU 165-b, as necessary7, for network control and signaling.

[0135] A DU 165-b may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) to control the operation of one or more RUs 170-b. In some examples, a DU 165-b may host, at least partially, one or more of an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO43modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, a DU 165-b may further host one or more low PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by the DU 165-b, or with control functions hosted by a CU 160-b.

[0136] In some examples, lower-layer functionality may be implemented by one or more RUs 170-b. For example, an RU 170-b, controlled by a DU 165-b, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower-layer functional split. In such an architecture, an RU 170-b may be implemented to handle over the air (OTA) communication with one or more UEs 115-b. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 170-b may be controlled by the corresponding DU 165-b. In some examples, such a configuration may enable a DU 165-b and a CU 160-b to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0137] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network nodes 105. For non-virtualized network nodes 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (e.g., an 01 interface). For virtualized network nodes 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., an O-Cloud 305) to perform network node life cycle management (e.g., to instantiate virtualized network nodes 105) via a cloud computing platform interface (e.g., an 02 interface). Such virtualized network nodes 105 can include, but are not limited to, CUs 160-b. DUs 165-b, RUs 170-b, and Near-RT RICs 175-b. In some implementations, the SMO 180-a may communicate with components configured in accordance with a 4G RAN (e.g., via an 01 interface). Additionally, or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-b via an 01 interface. The SMO 180-a also may include aNon-RT RIC 175 -a configured to support functionality of the SMO 180-a.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO44

[0138] The Non-RT RIC 175-a may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (Al) or machine learning (ML) workflows including model training and updates, or policy -based guidance of applications / features in the Near-RT RIC 175-b. The Non-RT RIC 175-a may be coupled with or communicate with (e.g., via an Al interface) the Near-RT RIC 175-b. The Near-RT RIC 175-b may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (e.g.. via an E2 interface) connecting one or more CUs 160-b, one or more DUs 165-b, or both, as well as an O-eNB 310, with the Near-RT RIC 175-b.

[0139] In some examples, to generate AI / ML models to be deployed in the Near-RT RIC 175-b, the Non-RT RIC 175-a may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 175-b and may be received at the SMO 180-a or the Non-RT RIC 175-a from nonnetwork data sources or from network functions. In some examples, the Non-RT RIC 175-a or the Near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 175-a may monitor long-term trends and patterns for performance and employ Al or ML models to perform corrective actions through the SMO 180-a (e.g., reconfiguration via 01) or via generation of RAN management policies (e.g., Al policies).

[0140] FIG. 4 shows an example of a wireless communications system 400 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The wireless communications system 400 may implement aspects of or may be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 400 includes a wireless device 410, which may be an example of a UE 115, network node 105, RU 170, DU 165, or CU 160 described with reference to FIG. 1, a UE 115-a, gNB 255, RU 170-a, DU 165-a, CU 160-a, or ng-eNB 260 described with reference to FIG. 2, or a UE 115-b, RU 170-b, DU 165-b, or CU 160-b described with reference to FIG. 3. The wireless communications system 400 also includes one or more network device(s) 420, one or more of which may be an example of anetwork node 105. location server 185, RU 170, DU 165. or CU 160 described withAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO45reference to FIG. 1, an LMF 265, external device 230, SLP 235, AMF 210, SMF 220, UPF 215, gNB 255, RU 170-a, DU 165-a, CU 160-a, or ng-eNB 260 described with reference to FIG. 2, an RU 170-b, DU 165-b, or CU 160-b described with reference to FIG. 3, a sensing management entity, a sensing, policy, consent, and transparency management (SPCTM) entity, a sensing control function (SCF), a sensing processing function (SPF), a network exposure function (NEF), a network data analytics function (NWDAF), an over-the-top (OTT) server, a sensing management function (SnMF), an operations, administration, and maintenance (0AM) entity, a server, a core network entity, another entity, or any combination thereof, among other examples. For example, the network device(s) 420 may include one or more network entities, one or more network nodes, or one or more other devices associated with one or more networks. In some cases, some network devices 420 may communicate (e.g., transmit or receive) information or signals with each other, or some network devices 420 may not communicate directly with each other. One or more of the network devices 420 may be included in a same network, in separate networks, in overlapping netw orks, or in separate netw orks.

[0141] The wireless device 410 may communicate with the network device(s) 420 using one or more links 425. one or more of which may be an example of a communication link 125, a backhaul communication link 120, or a communication link 155 described with reference to FIG. 1, a communication link 125-a, a backhaul communication link 120-a, a C-plane interface 245, or a U-plane interface 250 described with reference to FIG. 2, a communication link 125-b or a backhaul communication link 120-b described with reference to FIG. 3, or another link. The link(s) 425 may include one or more uni-directional or bi-directional links, one or more of which may enable uplink, downlink, or other communications. For example, the wireless device 410 may communicate (e.g.. transmit or receive) one or more signals 415, such as control signals or data signals, to or from the network device(s) 420 using the link(s) 425, or the network device(s) 420 may communicate (e.g., transmit or receive) one or more signals 415, such as control signals or data signals, to or from the wireless device 410 using the link 425(s). The signal(s) 415 may include one or more uplink transmissions, downlink transmissions, or other transmissions. One or more ofAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO46the signal(s) 415 may be communicated via a same link, via separate links, or via different links.

[0142] In some approaches, the wireless device 410 (e.g., a UE or network entity ) or the network device(s) 420 may be capable of performing one or more positioning or sensing procedures to generate position or sensing information. A positioning or sensing procedure may be one or more operations for estimating a position of an object or sensing an object (e.g., a device such as the wireless device 410 or a UE, or a passive object that does not provide signals for positioning). As used herein, a “positioning or sensing procedure” may include one or more operations for estimating a position of an object or for sensing an object.

[0143] For instance, a positioning or sensing procedure may include one or more operations of A-GNSS positioning, OTDOA positioning, E-CID positioning, sensorbased positioning (e.g., monostatic mode(s), bi-static mode(s), or multi-static mode(s)), WLAN-based positioning, Bluetooth-based positioning, TBS positioning, DL-TDOA positioning, DL-AOD positioning, Multi-RTT positioning, NR E-CID positioning, UL-TDOA positioning, or UL-AOA positioning, among other examples. Position information may include an estimated position (e.g., estimated location) or one or more measurements associated with a positioning procedure (e.g., AI / ML-based positioning procedure or non-Al / ML-based positioning procedure). For instance, position information may include a position or measurement determined based on one or more positioning procedures, such as A-GNSS positioning, OTDOA positioning, E-CID positioning, sensor-based positioning (e.g., monostatic mode(s), bi-static mode(s), or multi-static mode(s)), WLAN-based positioning, Bluetooth-based positioning, TBS positioning, DL-TDOA positioning, DL-AOD positioning, Multi-RTT positioning, NR E-CID positioning, UL-TDOA positioning, or UL-A positioning, among other examples. Examples of positioning or sensing procedures are described with reference to FIG. 23 or FIG. 24.

[0144] A position may be information or data indicating a point, area, or region where an object (e.g., the wireless device 410) is located. A location may be expressed as coordinates (e.g., latitude, longitude, or altitude of a geographic coordinate system (GCS), universal transverse mercator (UTM) coordinates, state plane coordinate systemAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO47(SPCS) coordinates, or Earth-centered Earth-fixed (ECEF) coordinates, among other examples), an address, or a location relative to another location, among other examples.

[0145] A measurement may be measured, sensed, generated, calculated, inferred, or predicted based on one or more samples, sensor data, information, or characteristics of a reference signal. Examples of measurements may include signal strength, reference signal received power (RSRP), reference signal received path power (RSRPP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), signal-to-interference plus noise ratio (SINR), SNR, channel frequency response (CFR), channel impulse response (CIR), power delay profile (PDP). delay profile (DP), channel quality indicator (CQI), CSI, line-of-sight (LOS) indicator, time of arrival (TOA), angle of arrival (AO A), angle of departure (AOD), round-trip time (RTT), reference signal time difference (RSTD), time difference of arrival (TDOA), reference signal carrier phase (RSCP), reference signal carrier phase difference (RSCPD), reception-to-transmission (Rx-Tx) time difference, range, distance, image data, temperature data, or motion data, among other examples. In some examples, a measurement may be data or an indicator that indicates one or more of the aforementioned values.

[0146] In some examples, a network node may output (e.g., transmit), or the wireless device 410 may obtain (e.g., receive), a reference signal. Additionally, or alternatively, the wireless device 410 may output (e.g., transmit), or a network node may obtain (e.g., receive) a reference signal. The reference signal may be a signal (e.g., electromagnetic signal, RF signal) with one or more established characteristics (e.g., signaling pattern, strength, amplitude, magnitude, frequency, timing, modulation, phase, or data, among other examples). For instance, the wireless device 410 or a network node may store information indicating one or more of the characteristics of the reference signal, which may allow for comparison of one or more stored characteristics and one or more characteristics of the received reference signal. The reference signal (e.g., the comparison) may enable channel estimation (e.g., channel attenuation, phase, frequency shift, or Doppler effects, among other examples), positioning, or tracking. Examples of the reference signal may include a reference signal of a synchronization signal block (SSB), a CSI-RS, a PRS, an SRS, a demodulation reference signal (DMRS), or a tracking reference signal (TRS), among other examples.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO48

[0147] In some examples, the wireless device 410 may obtain, receive, sense, capture, or generate one or more measurements. For instance, the wireless device 410 may include, may communicate with, or may be coupled with one or more sensors to obtain one or more measurements. Examples of a sensor may include an image sensor(s), infrared (IR) sensor(s), light sensor(s), depth sensor(s) (e.g., light detection and ranging (LIDAR), stereoscopic camera(s), or time-of-flight (TOF) sensor(s)), microphone(s), or RF sensor(s), among other examples. Examples of one or more measurements may include a range map (e.g., depth map), Doppler map, space map, angle map, light spectrum data, pixel(s), image(s) (e.g., red-green- blue-depth (RGBD) image(s)), audio signal(s), temperature map, TOF measurement(s), RF measurement(s), or other information (e.g., information regarding one or more objects). In some approaches to sensing, the wireless device 410 may sense or receive one or more signals originating from another device (e.g., another wireless device, UE, network node, network entity, or another signal source), where the one or more signals may be reflected by a target object for sensing or may be transmitted by the target object (e.g., the device) for sensing.

[0148] The wireless device 410 may obtain (e g., receive) a request 430 to collect information that is based on a measurement for a positioning or sensing procedure. For instance, the wireless device 410 may receive the request 430 from a network device 420 (e.g., from a network node, a network entity, a gNB, an LMF, an SnMF, a sensing function, or another entity, among other examples) to perform positioning or sensing measurements and report the measurements to the network (e.g., RAN) or to another device.

[0149] The wireless device 410 may output (e.g., transmit), to a network entity, a request authorization query 435 associated with the request 430. For example, the request authorization query 435 may be output to a network entity included in the network device(s) 420. The request authorization query 435 may be a query to determine whether the request 430 is authorized (e.g., whether the request 430 comes from an authorized source). For instance, the wireless device 410 may output (e.g., transmit) the request authorization query 435 to a privacy or consent-responsible core network entity to inform the network entity regarding the request the wireless deviceAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO49410 has received, or to query whether the request 430 is an authorized request for positioning or sensing purposes.

[0150] In some approaches, the request authorization query7435 may include information regarding one or more details of the request 430 (e.g., the request 430 from a network node or gNB). For instance, the request authorization query 435 may be associated with the request 430 from a source (e.g., network node) to the wireless device 410, or may indicate one or more attributes of the request 430. The one or more attributes may include an identifier of a source (e.g., an identifier of a network node or gNB) of the request 430. a period of the request 430, a reporting target for the information (e.g., a device to which the information is to be reported), a type of the information, an area corresponding to the request 430, a condition for the request 430, or any combination thereof. For example, the attributes may include an identifier of a device that sent the request, a time period for which the request 430 corresponds (or is active, for example), a reporting target (e.g., an identifier of a device to which the information is to be reported), the type of information requested, an area that is requested to be sensed, under which condition(s) (e.g., a trigger event(s)) for which the request 430 is to be triggered, or any combination thereof.

[0151] The wireless device 410 may obtain (e g., receive), from the network entity, an indication 440 of whether the request 430 is authorized. For instance, the privacyresponsible or consent-responsible core network entity may respond to the wireless device 410 regarding whether the request 430 is an authorized request. The network entity may manage authorization of requests from network nodes. In some cases, an unauthorized network node (e.g., gNB) may send the request 430 without first seeking authorization from the network entity. In this case, the network entity may detect that the request 430 is unauthorized due to an identifier of the source of the request 430 not matching the authorization records of the network entity7. In this case, the indication 440 may indicate that the request 430 is not authorized.

[0152] In some examples, the indication 440 of whether the request 430 is authorized may indicate that the request 430 is authorized, is authorized in part, or is not authorized. The indication 440 may indicate one or more permitted responses, if any, to the request 430. For instance, if the request 430 is not authorized, the indication 440 may indicate what the wireless device 410 is unauthorized to output any information to Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO50the source or that the wireless device 410 is authorized to output some information (e.g., measurements that all wireless devices in an area have indicated consent). If the request 430 is authorized in part or in full, the indication 440 may indicate that the wireless device 410 is authorized to output (e.g., transmit or send) some or all of the requested information to the source (e.g., network node or gNB) of the request 430. In some approaches, the indication 440 may indicate a t pe of information, a duration for sensing, measuring, or reporting that is authorized, a quantity or type of measurement that is authorized for reporting, or a time period for which an authorization is provided, or other information.

[0153] In some approaches, a network node may output (e.g., transmit), or a network entity may obtain (e.g., receive), an authorization request for collection of information related to a measurement at a wireless device 410 for a positioning or sensing procedure. For instance, a network node (e.g.. gNB) may request a privacy authorization from a privacy-responsible or consent-responsible core network entity. In some aspects, the network node (e g., a source of the request 430, gNB, or network entity, among other examples) may send an authorization request to a network entity to obtain authorization to request that the wireless device 410 provide sensing or positioning information. The network node may output (e.g., transmit), or the network entity (of the network device(s) 420, for instance) may obtain (e.g., receive), an authorization request previous to outputting the request 430, concurrently with outputting the request 430, or after outputting the request 430. In a case that the network entity grants the request, the network entity may provide the indication 440 to the wireless device 410 indicating that the request 430 is authorized in part or in full.

[0154] In some examples, the authorization request may indicate one or more parameters. The one or more parameters may include an identifier of the wireless device 410 from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof. For instance, the authorization request (e.g., privacy or consent authorization request) may include information related to which device(s) (e.g., wireless device 410) is to be requested to perform the measurement(s), one or more areas that are targeted for positioning or sensing, a duration of the requested positioningAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO51or sensing session, what measurements or signals are to be requested to be gathered or measured by the network node (e.g., gNBs), or what measurements are to be requested to be reported to the network node (e.g., gNB), among other examples.

[0155] In some approaches, one, some, or all of the one or more parameters of the authorization request may be the same as one. some, or all of the one or more attributes of the request 430, or one, some, or all of the one or more parameters may differ from one, some, or all of the one or more attributes of the request 430.

[0156] The network entity may output (e.g., transmit), or the network node may obtain (e.g., receive), an indication of whether the authorization request is accepted. For instance, the privacy -responsible or consent-responsible core network entity may respond with the indication (e.g., related answers to the requested questions, such as the authorization request or to the authorization request authorization query ). In some approaches, the indication of whether the authorization request is accepted may indicate that the authorization request is not accepted (e.g., is partially accepted or is not accepted in full) or may indicate one or more permitted parameters. Additionally, or alternatively, the indication of whether the authorization request is accepted may indicate a prioritization or a different positioning or sensing procedure. For example, if an authorization request is not accepted in full, the network entity may provide one or more options for one or parameters that may be authorized. The network entity may additionally, or alternatively, provide prioritizations or different options of positioning or sensing procedures that may be permitted or available.

[0157] In some approaches, the indication of whether the authorization request is accepted may include an authorization message for inclusion in the request 430 from the network node to the wireless device 410 to collect the information that is based on the measurement at the wireless device 410 for the positioning or sensing procedure. The network node may output the request 430 to the wireless device 410 to collect the information, where the request 430 may include the authorization message from the network entity. For instance, the wireless device 410 (e.g., a UE) may obtain the request 430 from the network node (e.g., gNB) to report positioning or sensing measurements to the RAN, or to another device, where the request 430 may include the authorization message that comes from a privacy-responsible or consent-responsible core network entity. The wireless device 410 may perform a validation procedure based on the Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO52authorization message. For instance, wireless device 410 may checks or validates the authenticity of the authorization message. In some approaches, the validation procedure may include checking a digital signature of the authorization message. For instance, the network entity may sign the authorization message utilizing a private key, and the wireless device 410 may utilize a public key to validate (e.g., decrypt and check) the signature of the authorization message. Additionally, or alternatively, the validation procedure may include sending the authorization message to another device (e.g., validation server), which may indicate to the wireless device 410 whether the authorization message is authentic.

[0158] In some aspects, a network node (e.g., a gNB), the wireless device 410 (e.g., UE), or another device (e.g., a sensing transmitter or receiver), may be configured with one or more privacy or consent-aware positioning or sensing configurations. For example, the network entity may output (e.g., transmit), or the wireless device 410 may obtain (e.g., receive), configuration information indicating one or more candidate attributes for a positioning or sensing procedure. The one or more candidate attributes may include a candidate area, a candidate device that is authorized to request a start or end of the second positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

[0159] Additionally, or alternatively, the network entity may output (e.g., transmit), or the network node may obtain (e.g., receive), configuration information indicating one or more candidate parameters for the positioning or sensing procedure, the one or more candidate parameters comprising a candidate area, a candidate device that is authorized to request a start or end of the positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity' area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

[0160] For instance, the candidate attribute(s) or the candidate parameter(s) (e.g., positioning or sensing session information or a positioning or sensing configuration) may indicate an area for the sensing, one or more devices that are allowed or authorized to request that the positioning or sensing start or end, what measurements may be gathered or measured, a granularity of the gathered information in time, frequency, or space, a validity area of the sensing configuration, a validity timer of the sensing Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO53configuration, or one or more invalidity events (e.g., one or more events that may occur during the positioning or sensing session that may result to making the positioning or sensing session invalid). The configuration information (e.g., privacy or consent-aware positioning or sensing session configuration(s), candidate attribute(s), or candidate parameter(s)) may be broadcasted or multicasted in an area (e.g., before the positioning or sensing session(s) begin).

[0161] In some approaches, the wireless device 410 (e.g., a UE) or the network node (e.g., gNB) may request (e.g., through a UE or gNB-initiated on-demand positioning or sensing procedure) one or more configurations, candidate attributes, or candidate parameters. For example, the wireless device 410 or the network node may request one or more privacy or consent-aware positioning sensing configurations from the privacy-responsible network entity or the consent-responsible network entity7. In some examples, the wireless device 410 or the network node may output (e.g., transmit), or the network entity may obtain (e.g., receive), an indication of a selection of the one or more candidate attributes or candidate parameters for the positioning or sensing procedure.

[0162] The network entity7may output (e.g., transmit), or the wireless device 410 or network node may obtain (e.g., receive), an acceptance or a denial of the selection of the one or more candidate attributes or the selection of the one or more candidate parameters. For example, the network entity may respond with an acceptance (e.g., an acknowledgment) or a denial (e.g., a negative acknowledgment) of the selection of the candidate attributes or candidate parameters. In some cases, if the network entity indicates a denial (e.g.. negative acknowledgment), the network entity may indicate a different privacy or consent-aware procedure that may be utilized (e.g., started). The privacy function may correspond to (e.g., may be collocated with) the wireless device 410 (e.g., one UE), or with a network node (e.g., one gNB).

[0163] For instance, the network entity may output (e.g., transmit), or the wireless device 410 or the network node may obtain (e.g., receive), an indication of a second selection of the one or more candidate attributes or candidate parameters, where the indication of the second selection may be based on the denial of the selection of the one or more candidate attributes or candidate parameters.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO54

[0164] In some examples, the wireless device 410 or a network node, based on obtaining the configuration information, may respond that the wireless device 410 or the network node does not authorize one or more of the positioning or sensing procedures (e.g., sessions). For example, the wireless device 410 or a network node may output (e.g., transmit) or the network entity may obtain (e.g., receive), an indication of a rejection of at least one of the one or more candidate attributes or one or more candidate parameters for the positioning or sensing procedure. The wireless device 410 or the network node may output (e.g., transmit), or the network entity may obtain (e.g., receive), an indication of one or more second candidate attributes or parameters for the positioning or sensing procedure. For instance, the wireless device 410 or the network node may respond with one or more suggested changes in the positioning or sensing session configurations (e.g., a different attribute(s), a different parameter(s), a different measurement granularity(ies), a different measurement(s) to be gathered, or a different duration of the session(s), among other examples), to authorize the correspond positioning or sensing configuration(s) (e.g., session(s)).

[0165] In some examples, the wireless device 410 or the network device(s) 420 (e.g., a network node or a network entity ) may communicate (e.g., output, transmit, obtain, or receive) information indicating that a positioning or sensing procedure is unauthorized, or indicating one or more unauthorized attributes or one or more unauthorized parameters for a positioning or sensing procedure. The one or more unauthorized attributes or one or more unauthorized parameters may indicate an unauthorized area, an unauthorized device for the positioning or sensing procedure, an unauthorized ty pe of measurement information, an unauthorized information granularity, an unauthorized duration, an unauthorized purpose, or any combination thereof. For instance, the wireless device 410, another wireless device, a network node, or a network entity may communicate, via one or more links (e.g., device-to-device (D2D) link(s), sidelink(s), wireless local area network (WLAN) link(s), personal area network (PAN) (e g., Bluetooth Low Energy' (BLE)) link(s), ultra wideband (UWB) link(s), a broadcast link(s), or a multicast link(s), among other examples), one or more messages in an area to indicate that no positioning or sensing is authorized, or that no positioning or sensing is authorized with one or more positioning or sensing characteristics (e.g., attributes or parameters). In some approaches, the wireless deviceAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO55410, another wireless device, or a network node may configure or indicate to the network entity (e.g., privacy-aware or consent-aware server) that no positioning or sensing is authorized with one or more positioning or sensing characteristics (e g., attribute(s) or parameter(s)). The characteristics (e.g., attribute(s) or parameter(s) may include, or may correspond to, a positioning or sensing duration, a positioning or sensing area, a granularity of the positioning or sensing, one or more collected measurements, a reporting duration of one or more collected measurements, an identifier(s) of a device(s) gathering the data, or a purpose (e.g., to improve communication performance or positioning or sensing-aware communications) for which the data is gathered.

[0166] From a perspective of a network entity (of the network device(s) 420, for instance), the network entity may obtain (e.g., receive) an authorization inquiry' related to collection of information that is based on a measurement at a wireless device 410 for a positioning or sensing procedure. As used herein, an “authorization inquiry7’ may refer to a request authorization query from the wireless device 410, an authorization request from a network node, or another message relating to authorization for a positioning or sensing procedure (e.g., session(s)). Validation of an authorization inquiry may include authorizing a request authentication query (or authorizing one or more attributes thereof) or may include permitting an authorization request (or permitting one or more parameters thereof). For example, the network entity may determine whether to validate (e.g., authorize, accept, authenticate, approve, or permit, among other examples) the authorization inquiry based on one or more attributes or parameters of the authorization inquiry. For instance, the network entity may determine whether information from one or more wireless devices or network nodes (in an area, for instance) indicates authorization (e.g., consent or permission) to perform a positioning or sensing procedure with the attribute(s) or parameter(s) indicated by the authorization inquiry'. The network entity may output (e.g., transmit) an indication of whether the authorization inquiry is validated. For instance, the network entity may output an indication of whether the request authorization query (or one or more corresponding attributes, for example) is authorized or the authorization request (or one or more corresponding parameters) is permitted.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO56

[0167] In some examples, the determination whether to validate the authorization inquiry may be based on a satisfaction of a validation criterion by the one or more attributes or parameters. The validation criterion may be a condition(s) for consent, authorization, or trust related to the attribute(s) or parameter(s). Examples of a validation criterion may be whether a wireless device or a network node has a trusted status (e.g., the identifier of the wireless device or network node corresponds to a record of one or more trusted wireless devices or network nodes), whether a positioning or sensing duration satisfies a consent duration (e.g., is less than or equal to a consent duration) for one or more wireless devices or network nodes, whether the positioning or sensing area corresponds to an area in which consent is indicated from present wireless devices or network nodes or corresponds to an area in which positioning or sensing is allowed by law or regulation, whether the positioning or sensing granularity' (e.g., positioning or sensing accuracy, range) satisfies consent from present wireless devices or network nodes or is allowed by law or regulation, whether a type of measurement (e.g., position, object type, identity, facial recognition, speed, direction, size, color, or textual information, among other examples) satisfies consent from present wireless devices or network nodes or is allowed by law or regulation, whether a measurement reporting duration satisfies consent from present wireless devices or network nodes or is allowed by law or regulation, whether a device (or associated company, entity, or government) gathering the data satisfies consent from present wireless devices or network nodes or is allowed by law or regulation, or whether a purpose for which data is gathered satisfies consent from present wireless devices or network nodes or is allowed by law or regulation, among other examples.

[0168] In some examples, the wireless device 410 or a network device(s) 420 (e.g., network node(s) or network entity(ies)) may initiating a timer based on a time of the authorization inquiry. For instance, when a request to perform positioning or sensing is received by the network entity (e.g.. a privacy-aware or consent-aware server), a timer may start until the request can be triggered (e.g., until information collection or reporting may be performed). While the timer is running (or during a time period), the network entity (e.g., privacy-aware or consent-aware server) may gathering information regarding whether there is a device for which consent or authorization is denied for positioning or sensing (according to a positioning or sensing configuration, forAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO57instance). The network entity may obtain (e.g., receive, from a location server, another network entity, or another device), identification information of the wireless device 410. For example, the network entity (e.g., privacy-aware or consent-aware server) may request a report or information from a location server (e.g., an LMF) of which device or devices have been active in an area (e.g., positioning or sensing area). The network entity' may output (e.g., transmit), or the wireless device 410 may obtain (e.g., receive), based on the identification information, an inquiry of whether the wireless device 410 accepts the positioning or sensing procedure. For instance, the network entity may check with one or more devices (e.g., wireless devices) in the area regarding whether the device(s) are accept the positioning or sensing procedures (e g., a positioning or sensing session). The wireless device 410 may output (e.g., transmit), or the network entity may obtain (e.g., receive), an indication of whether the wireless device 410 accepts the positioning or sensing procedure.

[0169] A session of the positioning or sensing procedure may begin or expire by an expiration of the timer from the time of the authorization inquiry (e.g., authorization request or request authorization query, among other examples). For example, a request to start a session may be obtained (e.g., received) by the network entity, based on which the timer may be activated. The session may start (or may be aborted, for instance) by a time that the timer expires. In some approaches, if the timer expires without the network entity' receiving an indication of consent from one or more devices in the area, the network entity may abort the session. In some approaches, if the timer expires without the network entity receiving an indication of consent from one or more devices in the area, the network entity may allow or begin the session.

[0170] In some examples, the wireless device 410 may collect information in accordance with the configuration information, authorized attribute(s), permitted parameter(s), consent information, or other conditions for collecting information. For instance, the wireless device 410, if allowed, may receive one or more signals (e.g., reference signals or other signals) or may measure one or more signals to determine information (e.g., position information, object information, identity information, facial recognition information, object speed information, object movement direction information, object size, object color, object type information, or detected textual information, among other examples). In some examples, the information mayAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO58correspond to one or objects (e.g., wireless device(s), vehicle(s), road(s), sign(s), person(s), or building(s), among other information). In some aspects, the wireless device 410 may output (e.g., transmit) at least a portion of the information to one or more devices (e.g.. one or more of the network device(s) 420 or another device(s)) in accordance with the configuration information, authorized attribute(s), permitted parameter(s), consent information, or other conditions for collecting information.

[0171] Some of the techniques described herein may relate to privacy or consent considerations and reporting of RAN positioning or sensing measurements. In some examples of the techniques described herein, a wireless device 410 may output (e.g., transmit) a request (e.g., a request authorization query 435) to the network device(s) 420 (e.g., privacy or consent core network entity) to determine whether the wireless device 410 (or another device) is allowed to perform one or more positioning or sensing operations. In some examples, the request may indicate or include an indication of an identifier of a source or device that sent the request, a quantity of time for the request (e.g., for how long the positioning or sensing operation(s) are requested to be performed), an identifier of a device to which information (e.g., measurements) associated with the request may be reported, the information being requested, an area being requested to be sensed, or one or more conditions or trigger events associated with the positioning or sensing operation(s), among other examples. The network device(s) 420 (e.g., network entity) may respond with a message or indication (e.g., indication 440) regarding whether the wireless device 410 or the positioning or sensing operations may be authorized or not. In some approaches, the network device(s) 420 may modify one or more of the parameters. The wireless device 410 may be a gNB or UE, among other examples. In some aspects, the request or the message in response may include or indicate a granularity of information for gathering in time, frequency, or space, or one or more invalidity events that may cause measurements to be stop being reported, among other examples.

[0172] In some examples of the techniques described herein, one or more signals, indications, or information (e.g., configuration information, requests, indications, measurement information, or capability information, among other examples) described herein may be communicated (e.g., transmitted or received) as part of a protocol or signaling procedure. For instance, the wireless device 410 (e.g.. UE) or the networkAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO59device(s) 420 (e.g., network node(s), LMF, or other network entity(ies)) may communicate in accordance with an LTE positioning protocol (LPP), in accordance with an NR positioning protocol A (NRPP A), via LPP signaling, or via NRPPA signaling.

[0173] In some approaches, the wireless device 410 or the network device(s) 420 may participate in a capability exchange that may include one or more signals or messages communicated between the wireless device 410 and the network device(s) 420. The capability exchange may be performed via a network node in some approaches. Additionally, or alternatively, the capability exchange may be based on, or may be performed in accordance with, a protocol (e.g., LPP, NRPPA, via LPP signaling, or via NRPPA signaling, among other examples). In some aspects, a capability exchange may include request signaling (e.g., a request message(s) indicating a request from the network device(s) 420 for capability information of the wireless device 410) or capability information signaling (e.g., message(s) indicating capability information or one or more capabilities of the wireless device 410). The capability information may be communicated based on a request (e.g., in response to a request from the network device(s) 420), independent of a request, or without a request.

[0174] Some examples of capability information that may be communicated (e g., in accordance with LPP, NRPPA, via LPP signaling, or via NRPPA signaling, among other examples) may include capability information indicating whether the wireless device 410 supports one or more positioning or sensing procedures, authorization information signaling, consent information signaling, signaling of one or more parameters, signaling of one or more attributes, signaling of one or more indications, or signaling other information described herein, among other examples.

[0175] In some approaches, one or more network devices 420 may communicate or store capability information associated with the wireless device 410 (or one or more other wireless devices). For instance, the wireless device 410 may output (e.g., transmit) capability information to an LMF. The LMF may store the capability information or may communicate the capability information to an AMF (or other entity) for storage. A network device(s) 420 (e.g., LMF, AMF, other network entity7, or any combination thereof) may access the stored capability information associated with the wireless device 410, which may reduce repeated capability exchanges or signaling of the Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO60capability information between the wireless device 410 and the network device(s) 420. For instance, a network device(s) 420 may store or access capability information associated with the wireless device 410 that may indicate whether the wireless device 410 supports one or more positioning or sensing procedures, authorization information signaling, consent information signaling, signaling of one or more parameters, signaling of one or more attributes, signaling of one or more indications, or signaling other information described herein, among other examples.

[0176] In some approaches, the network device(s) 420 or the wireless device 410 may communicate (e.g., transmit or receive) configuration information (e.g., via a network node). Additionally, or alternatively, the communication of configuration information may be based on, or may be performed in accordance with, a protocol (e.g., LPP, NRPPA, via LPP signaling, or via NRPPA signaling, among other examples). In some aspects, communicating the configuration information may be performed as part of a capability exchange or separate from a capability exchange. In some approaches, configuration information may be communicated based on request signaling (e g., a request message(s) indicating a request from the wireless device 410 for configuration information of the network device(s) 420). The configuration information may be communicated based on a request (e.g., in response to a request from the wireless device 410), independent of a request, or without a request.

[0177] Some examples of configuration information that may be communicated (e.g., in accordance with LPP, NRPPA, via LPP signaling, or via NRPPA signaling, among other examples) may include configuration information indicating resources for reference signal measurement, one or more candidate attributes for a positioning or sensing procedure, one or more candidate attributes comprising a candidate area, one or more candidate parameters for the positioning or sensing procedure, the one or more candidate parameters including a candidate area, a candidate device that is authorized to request a start or end of a positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity’ event, request information, attribute information, parameter information, request authorization query information, authorization request information, indication information, authorization message information, authorization inquiry information, measurement information, validationAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO61information, authorization information, acceptance information, permission information, rejection information, denial information, or other information described herein.

[0178] In some approaches, one or more network devices 420 may determine or communicate configuration information based on (e.g., in accordance with) the capability information. For instance, the network device(s) 420 (e.g., LMF) may configure the wireless device 410 to perform PRS measurement in accordance with one or more of the capabilities of the wireless device 410.

[0179] FIG. 5 shows an example of a wireless communications system 500 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The wireless communications system 500 may include a first wireless device 410-a, a second wireless device 410-b, and one or more network devices 420-a. An object 505 may be included in the wireless communications system 500, or may be separate from the wireless communications system 500. The first wireless device 410-a, the second wireless device 410-b, or the object 505 may be examples of the wireless device 410 described with reference to FIG. 4. In some examples, the first wireless device 410-a, the second wireless device 410-b, or the object 505 may include one or more sensors, one or more transmitters, or one or more receivers for outputting (e.g., transmitting), reflecting, or obtaining (e.g., receiving) one or more signals for positioning or sensing. In some examples, the first wireless device 410-a, the second wireless device 410-b, or the network device(s) 420-a may be capable of performing, or participating in, one or more positioning or sensing procedures as described herein.

[0180] The network device(s) 420-a may be an example(s) of the network device(s) 420 described with reference to FIG. 4. For instance, the network device(s) 420-a may include one or more network entities or one or more netw ork nodes. For example, the network device(s) 420-a may include one or more network nodes, location servers, RUs, DUs, CUs, LMFs, external devices, SLPs, AMFs, SMFs, UPFs, gNBs, ng-eNBs, sensing management entities, SPCTM entities, SCFs, SPFs. NEFs, NWDAFs, OTT servers, SnMFs, 0AM entities, servers, core network entities, a third-party device, another entity, or any combination thereof, among other examples. In some examples, the network device(s) 420-a (e.g., network entity(ies)) may include, or may have access to, storage for positioning or sensing information (e.g., integrated or independent Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO62storage for positioning or sensing information). Some architectural structures may be utilized to help preserve privacy.

[0181] The first wireless device 410-a may communicate (e.g., output, transmit, obtain, or receive) first information 510-a with the network device(s) 420-a. The first information 510-a may include control information or data. The second wireless device 410-b may communicate (e.g., output, transmit, obtain, or receive) second information 510-b with the network device(s) 420-a. The first information 510-a or the second information 510-b may include control information or data. For instance, the first information 510-a or the second information 510-b may include request information, configuration information, attribute information, parameter information, request authorization query information, authorization request information, indication information, authorization message information, authorization inquiry information, measurement information, validation information, authorization information, acceptance information, permission information, rejection information, denial information, or other information.

[0182] In some examples, the first wireless device 410-a may communicate first signaling 515-a with the object 505, or the second wireless device 410-b may communicate second signaling 515-b with the object 505. For instance, the object 505 may be wireless device (e.g., UE) that may may transmit or receive the first signaling 515-a or the second signaling 515-b, which may enable the first wireless device 410-a, the second wireless device 410-b, or the object 505 to perform, or participate in, a positioning or sensing procedure. For example, the first signaling 515-a or the second signaling 515-b may be measured. In some approaches, an indication of the measurement(s) may be communicated to the network device(s) 420-a. The first signaling 515-a or the second signaling 515-b may enable the first wireless device 410-a, the second wireless device 410-b, or the network device(s) 420-a to determine a position or other information about the object 505.

[0183] In some examples, the object 505 may be a passive object that does not transmit or receive signals. The first wireless device 410-a may communicate a first sensing signal 520-a or the second wireless device 410-b may communicate a second sensing signal 520-b. For instance, the first wireless device 410-a may transmit the first sensing signal 520-a. which may reflect from the object, and which may be received by Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO63the second wireless device 410-b as the second sensing signal 520-b. For example, the first sensing signal 520-a or the second sensing signal 520-b may be measured. In some approaches, an indication of the measurement(s) may be communicated to the network device(s) 420-a. The first sensing signal 520-a or the second sensing signal 520-b may enable the first wireless device 410-a, the second wireless device 410-b, or the network device(s) 420-a to determine a position or other information about the object 505.

[0184] In some examples of the techniques described herein, information may be utilized to control positioning or sensing procedures (e.g., sessions). Information may be communicated (e.g., output, transmitted, obtained, or received) or stored (e.g., stored in sensing storage). In some examples, the information may include one or more positioning or sensing policies, positioning or sensing session policies, persistent data, consent information, positioning or sensing disclosure logs, or transparency information. Positioning or sensing session policies may indicate one or more policies for authorization, disclosure, control, or processing in positioning or sensing sessions. Positioning or sensing policies may manage one or more permitted positioning or sensing information types, area (e.g., geographic) restrictions, disclosure conditions, granularity information, or privacy information. Persistent data may be data for one or more use cases, such as environment maps or historical records. Consent information may include information indicating consent (or no consent) corresponding to one or more objects (e.g., the object 505). Consent may allow for the collection of information (e.g., positioning or sensing information) of an object. Positioning or sensing disclosure logs may include records of data disclosure detail recipient identities, data descriptions, disclosure purposes, obligations, timestamps, or the policies enforced during a positioning or sensing procedure. Transparency information may indicate one or more policies regarding the collection or processing of positioning or sensing data, or regarding the communication of positioning or sensing information to one or more people or entities (e.g.. policies regarding how disclosure is logged or shared with relevant parties).

[0185] Some examples of the techniques described herein may relate to the collection or signaling of information that may be utilized to control positioning or sensing procedures (e.g., sessions). For instance, authorization or consent information corresponding to one or more objects (e.g., object 505) may be collected orAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO64communicated as described with reference to FIG. 4. Additionally, or alternatively, authorization may be granted or denied based on consent information or other information as described with reference to FIG. 4.

[0186] FIG. 6 shows an example of a process flow 600 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The process flow 600 may include a wireless device 410-c, which may be an example of a UE 115, UE 115-a, UE 115-b, or the wireless device 410, as described herein. The process flow 600 may also include a network node 675, which may be an example of a network node 105, gNB 255, CU 160-a, DU 165-a, RU 170-a, TRP, the wireless device 410, or a network device(s) 420 (e.g., network node) as described herein. The process flow 600 may additionally include a network entity7670, which may be an example of a network entity', location server 185, LMF 265, external device 230, SLP 235, NWDAF, OTT server, 0AM entity, SnMF. network device(s) 420 (e.g.. network entity), AMF, SMF, UPF, sensing management entity, SPCTM entity, SCF, SPF, NEF, server, core network entity, a third-party7device, another entity7, or any combination thereof, as described herein. In some approaches, the network entity 670 may communicate with the wireless device 410-c via one or more network nodes (e.g., base station(s), TRP(s). CU(s). DU(s), RU(s), or the network node 675, among other examples).

[0187] In the following description of the process flow 600, the communications between the wireless device 410-c, the network node 675, or the network entity' 670 may be transmitted in the same order or in a different order than the example order shown, or the operations performed by the wireless device 410-c. the network node 675, or the network entity 670 may be performed in different orders or at different times. One or more operations may be omitted from the process flow 600, or one or more other operations may be added to the process flow 600. Although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time or in overlapping time periods in some examples.

[0188] In some examples, the wireless device 410-c and the network entity7670 may communicate information (e.g., request information, configuration information, attribute information, parameter information, request authorization query7information.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO65authorization request information, indication information, authorization message information, authorization inquiry information, measurement information, validation information, authorization information, acceptance information, permission information, rejection information, denial information, or other information) via the network node 675 or independent of the network node 675. In some examples, the wireless device 410-c and the network node 675 may communicate information (e.g., request information, configuration information, attribute information, parameter information, request authorization query information, authorization request information, indication information, authorization message information, authorization inquiry information, measurement information, validation information, authorization information, acceptance information, permission information, rejection information, denial information, or other information), where the information may be relayed transparently via the network node 675, may be processed by the network node 675 before communication to the network entity^ 670 or the wireless device 410-c, or may not be transmitted to the network entity7670 or the wireless device 410-c.

[0189] At 605, the network node 675 may output (e.g., transmit), or the wireless device 410-c may obtain (e.g., receive), a request to collect information that is based at least in part on a measurement for a positioning or sensing procedure. For instance, the request may be communicated to the wireless device 410-c as described with reference to FIG. 4.

[0190] At 610, the wireless device 410-c may output (e.g., transmit), or the network entity 670 may obtain (e.g., receive), a request authorization query. For instance, the wireless device 410-c may transmit the request authorization query to the network entity 670 as described with reference to FIG. 4. The request authorization query may request that the network entity 670 indicate whether the request from the network node 675 is authorized.

[0191] At 615, the network entity 670 may output (e.g., transmit), or the wireless device 410-c may obtain (e.g., receive), an indication of whether the request is authorized. For instance, the indication may be communicated to the wireless device 410-c as described with reference to FIG. 4. In a case that the indication indicates that the request is authorized, the wireless device 410-c may collect information inAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO66accordance with the request. For example, the wireless device 410-c may receive or measure one or more signals (e.g., signal(s) for positioning or sensing).

[0192] At 620, the wireless device 410-c may output (e.g., transmit), or the network node 675, the network entity 670, or another device may obtain (e.g., receive), an indication of at least a portion of the information. For instance, the wireless device 410-c may transmit the indication of the information (e.g., measurements or other information, such as a position, a detected object, or object motion, or object type, among other examples) to the network entity 670 as described with reference to FIG. 4.

[0193] FIG. 7 shows an example of a process flow 700 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The process flow 700 may include a wireless device 410-d, which may be an example of a UE 115, UE 115-a, UE 115-b, or the wireless device 410, as described herein. The process flow 700 may also include a network node 775, which may be an example of a network node 105, gNB 255, CU 160-a, DU 165-a, RU 170-a, TRP, the wireless device 410, or a network device(s) 420 (e.g., network node) as described herein. The process flow 700 may additionally include a network entity 770, which may be an example of a network entity7, location server 185, LMF 265, external device 230, SLP 235, NWDAF, OTT server, 0AM entity, SnMF. network device(s) 420 (e.g.. network entity), AMF, SMF, UPF, sensing management entity, SPCTM entity, SCF, SPF, NEF, server, core network entity, a third-party device, another entity', or any combination thereof, as described herein. In some approaches, the network entity 770 may communicate with the wireless device 410-d via one or more network nodes (e.g., base station(s), TRP(s). CU(s). DU(s), RU(s), or the network node 775, among other examples).

[0194] In the following description of the process flow 700, the communications between the wireless device 410-d, the network node 775, or the network entity' 770 may be transmitted in the same order or in a different order than the example order shown, or the operations performed by the wireless device 410-d. the network node 775, or the network entity 770 may be performed in different orders or at different times. One or more operations may be omitted from the process flow 700, or one or more other operations may be added to the process flow 700. Although some operations or signaling may be shown to occur at different times for discussion purposes, these Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO67operations may actually occur at the same time or in overlapping time periods in some examples.

[0195] In some examples, the wireless device 410-d and the network entity' 770 may communicate information (e.g., request information, configuration information, attribute information, parameter information, request authorization query’ information, authorization request information, indication information, authorization message information, authorization inquiry information, measurement information, validation information, authorization information, acceptance information, permission information, rejection information, denial information, or other information) via the network node 775 or independent of the network node 775. In some examples, the wireless device 410-d and the network node 775 may communicate information (e.g., request information, configuration information, attribute information, parameter information, request authorization query’ information, authorization request information, indication information, authorization message information, authorization inquiry information, measurement information, validation information, authorization information, acceptance information, permission information, rejection information, denial information, or other information), where the information may be relayed transparently via the network node 775, may be processed by the network node 775 before communication to the network entity^ 770 or the wireless device 410-d, or may not be transmitted to the network entity 770 or the wireless device 410-d.

[0196] At 705, the network node 775 may output (e.g., transmit), or the network entity 770 may obtain (e.g., receive), an authorization for collection of information related to a measurement for a positioning or sensing procedure. For instance, the authorization request may be communicated to the network entity 770 as described with reference to FIG. 4.

[0197] At 710, the network entity' 770 may output (e.g., transmit), or the network node 775 may obtain (e.g., receive), an indication of whether the authorization request is accepted. For instance, the indication may be communicated to the network node 775 as described with reference to FIG. 4. In some examples, the indication may be, or may include, an authorization message as described with reference to FIG. 4.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO68

[0198] At 715, the network node 775 may output (e.g., transmit), or the wireless device 410-d may obtain (e.g., receive), a request to collect information that is based at least in part on a measurement for a positioning or sensing procedure. For instance, the request may be communicated to the wireless device 410-d as described with reference to FIG. 4. In some examples, the request may include the authorization message from the network entity 770.

[0199] At 720, the wireless device 410-d may perform a validation procedure. For instance, the wireless device 410-d may perform the validation procedure based on the authorization message as described with reference to FIG. 4. In a case that the validation procedure is successful, the wireless device 410-d may collect information (e.g., positioning or sensing information) in accordance with the request.

[0200] At 725, the wireless device 410-d may output (e.g., transmit), or the network node 775, the network entity 770, or another device may obtain (e.g., receive), an indication of at least a portion of the information. For instance, the wireless device 410-d may transmit the indication of the information (e.g., measurements or other information, such as a position, a detected object, or object motion, or object type, among other examples) to the network entity 770 as described with reference to FIG. 4.

[0201] FIG. 8 shows an example of a process flow 800 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The process flow 800 may include a first wireless device 410-e and a second wireless device 410-f, one or more of which may be an example of aUE 115, UE 115-a, UE 115-b, or the wireless device 410, as described herein. The process flow 800 may additionally include a network entity 870, which may be an example of a network entity, location server 185, LMF 265, external device 230, SLP 235, NWDAF, OTT server, 0AM entity, SnMF, network device(s) 420 (e.g., network entity), AMF, SMF, UPF, sensing management entity, SPCTM entity, SCF, SPF, NEF, server, core network entity, a third-party device, another entity, or any combination thereof, as described herein. In some approaches, the network entity 870 may communicate with the first wireless device 410-e via one or more network nodes (e.g., base station(s), TRP(s), CU(s), DU(s), or RU(s), among other examples).Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO69

[0202] In the following description of the process flow 800, the communications between the first wireless device 410-e, the second wireless device 410-f, or the network entity 870 may be transmitted in the same order or in a different order than the example order shown, or the operations performed by the first wireless device 410-e. the second wireless device 410-f, or the network entity 870 may be performed in different orders or at different times. One or more operations may be omitted from the process flow 800, or one or more other operations may be added to the process flow 800. Although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time or in overlapping time periods in some examples.

[0203] In some examples, the first wireless device 410-e and the network entity 870 may communicate information (e.g., request information, configuration information, attribute information, parameter information, request authorization query information, authorization request information, indication information, authorization message information, authorization inquiry information, measurement information, validation information, authorization information, acceptance information, permission information, rejection information, denial information, or other information) via a network node or independent of a network node. In some examples, the first wireless device 410-e and the network node may communicate information (e.g., request information, configuration information, attribute information, parameter information, request authorization query' information, authorization request information, indication information, authorization message information, authorization inquiry’ information, measurement information, validation information, authorization information, acceptance information, permission information, rejection information, denial information, or other information), where the information may be relayed transparently via the network node, may be processed by the network node before communication to the netw ork entity' 870 or the first wireless device 410-e, or may not be transmitted to the network entity 870 or the first wireless device 410-e.

[0204] At 805, the second wireless device 410-f may output (e.g., transmit), or the first wireless device 410-e may obtain (e.g., receive), information indicating one or more unauthorized attributes for a positioning or sensing procedure. For instance, the information may be communicated to the first wireless device 410-e as described withAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO70reference to FIG. 4. For instance, the information indicating the one or more unauthorized attributes may be communicated via a D2D link, sidelink, broadcast, or multicast, among other examples.

[0205] At 810, the first wireless device 410-e may output (e.g., transmit), or the network entity 870 may obtain (e.g.. receive), information indicating the one or more unauthorized attributes. For instance, the first wireless device 410-e may transmit the information indicating the one or more unauthorized attributes to the network entity 870 as described with reference to FIG. 4. The one or more unauthorized attributes may indicate one or more attributes (e.g., area, device that is authorized to request a start or end of the second positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event) for a positioning or sensing procedure for which the second wireless device 410-f indicates no consent, no authorization, or partial consent or authorization (e.g., consent or authorization with less than full scope).

[0206] At 815, the network entity 870 may output (e.g., transmit), or the first wireless device 410-e may obtain (e.g., receive), configuration information. For instance, the configuration information may be communicated to the first wireless device 410-e as described with reference to FIG. 4. For instance, the configuration information may indicate a selection of one or more attributes for which a positioning or sensing procedure may be allowed (e.g., for which the second wireless device provides consent or authorization).

[0207] At 820, the first wireless device 410-e may perform, or may participate in, a positioning or sensing procedure. For instance, the first wireless device 410-e may collect information (e.g., positioning or sensing information) in accordance with the configuration information (e.g., one or more attributes with reduced collection or reporting scope).

[0208] At 825, the first wireless device 410-e may output (e.g., transmit), or the network entity 870 may obtain (e.g., receive), an indication of at least a portion of the information. For instance, the first wireless device 410-e may transmit the indication of the information (e.g., measurements or other information, such as a position, a detectedAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO71object, or object motion, or object type, among other examples) to the network entity 870 as described with reference to FIG. 4.

[0209] FIG. 9 shows a block diagram 900 of a device 905 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a wireless device as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, the communications manager 920), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0210] The receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to authorization communications for positioning or sensing procedures). Information may be passed on to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

[0211] The transmitter 915 may provide a means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to authorization communications for positioning or sensing procedures). In some examples, the transmitter 915 may be co-located with a receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.

[0212] The communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be examples of means for performing various aspects of authorization communications for positioning or sensing procedures as described herein. For example, the communications manager 920, the receiver 910,Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO72the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0213] In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g.. in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0214] Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0215] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO73

[0216] For example, the communications manager 920 is capable of, configured to, or operable to support a means for obtaining a request to collect information that is based on a measurement for a positioning or sensing procedure. The communications manager 920 is capable of. configured to, or operable to support a means for outputting, to a network entity, a request authorization query associated with the request, where the request authorization query indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof. The communications manager 920 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an indication of whether the request is authorized.

[0217] By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or any combination thereof) may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources, or increased data security’.

[0218] FIG. 10 shows a block diagram 1000 of a device 1005 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a device 905 or a wireless device as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one or more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, the communications manager 1020), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0219] The receiver 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to authorization communications for positioning or sensing Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO74procedures). Information may be passed on to other components of the device 1005. The receiver 1010 may utilize a single antenna or a set of multiple antennas.

[0220] The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to authorization communications for positioning or sensing procedures). In some examples, the transmitter 1015 may be co-located with a receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a set of multiple antennas.

[0221] The device 1005, or various components thereof, may be an example of means for performing various aspects of authorization communications for positioning or sensing procedures as described herein. For example, the communications manager 1020 may include a request component 1025, a query component 1030. an indication component 1035, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0222] The request component 1025 is capable of, configured to, or operable to support a means for obtaining a request to collect information that is based on a measurement for a positioning or sensing procedure. The query component 1030 is capable of, configured to, or operable to support a means for outputting, to a network entity, a request authorization query associated with the request, where the request authorization query' indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO75the request, a condition for the request, or any combination thereof. The indication component 1035 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an indication of whether the request is authorized.

[0223] FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of authorization communications for positioning or sensing procedures as described herein. For example, the communications manager 1120 may include a request component 1125, a query component 1130, an indication component 1135. a validation component 1140, a configuration component 1145, an authorization component 1150, an attribute component 1155, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0224] The request component 1125 is capable of, configured to, or operable to support a means for obtaining a request to collect information that is based on a measurement for a positioning or sensing procedure. The query component 1130 is capable of, configured to, or operable to support a means for outputting, to a network entity, a request authorization query associated with the request, where the request authorization query indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof. The indication component 1135 is capable of. configured to, or operable to support a means for obtaining, from the network entity, an indication of whether the request is authorized.

[0225] In some examples, the indication of whether the request is authorized indicates that the request is not authorized and indicates one or more permitted responses to the request.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO76

[0226] In some examples, the request component 1125 is capable of, configured to, or operable to support a means for obtaining a second request to collect second information that is based on a second measurement for a second positioning or sensing procedure, where the second request includes an authorization message. In some examples, the validation component 1140 is capable of, configured to, or operable to support a means for performing a validation procedure based on the authorization message.

[0227] In some examples, the configuration component 1145 is capable of, configured to, or operable to support a means for obtaining, from the network entity, configuration information indicating one or more candidate attributes for a second positioning or sensing procedure, the one or more candidate attributes including a candidate area, a candidate device that is authorized to request a start or end of the second positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

[0228] In some examples, the attribute component 1155 is capable of, configured to, or operable to support a means for outputting, to the network entity, an indication of a selection of the one or more candidate attributes for the second positioning or sensing procedure. In some examples, the attribute component 1155 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an acceptance or a denial of the selection of the one or more candidate attributes.

[0229] In some examples, the attribute component 1155 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an indication of a second selection of the one or more candidate attributes, where the indication of the second selection is based on the denial of the selection of the one or more candidate attributes.

[0230] In some examples, the attribute component 1155 is capable of, configured to, or operable to support a means for outputting, to the network entity, an indication of a rejection of at least one of the one or more candidate attributes for the second positioning or sensing procedure. In some examples, the attribute component 1155 is capable of, configured to, or operable to support a means for outputting, to the networkAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO77entity, an indication of one or more second candidate attributes for the second positioning or sensing procedure.

[0231] In some examples, the authorization component 1150 is capable of, configured to, or operable to support a means for communicating information indicating that a second positioning or sensing procedure is unauthorized, or indicating one or more unauthorized attributes for a second positioning or sensing procedure, the one or more unauthorized attributes including an unauthorized area, an unauthorized device for the positioning or sensing procedure, an unauthorized type of measurement information, an unauthorized information granularity, an unauthorized duration, an unauthorized purpose, or any combination thereof.

[0232] FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include components of a device 905, a device 1005. or a wireless device 410 as described herein. The device 1205 may include components for bidirectional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1220, an I / O controller, such as an I / O controller 1210. one or more transceivers 1215, one or more antennas 1225, at least one memory 1230, code 1235, and at least one processor 1240. The device 1205 may include one or more sensors 1250. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245). The I / O controller 1210 may manage input and output signals for the device 1205. The I / O controller 1210 may also manage peripherals not integrated into the device 1205. In some cases, the I / O controller 1210 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 1210 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the I / O controller 1210 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 1210 may be implemented as part of one or more processors, such as the at least one processor 1240. In some cases, a user mayAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO78interact with the device 1205 via the I / O controller 1210 or via hardware components controlled by the I / O controller 1210.

[0233] In some cases, the device 1205 may include a single antenna. However, in some other cases, the device 1205 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver(s) 1215 may communicate bi-directionally via the one or more antennas 1225 using wired or wireless links as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1215 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1225 for transmission, and to demodulate packets received from the one or more antennas 1225. The transceiver 1215, or the transceiver 1215 and one or more antennas 1225, may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, or any combination thereof or component thereof, as described herein.

[0234] The one or more transceivers 1215 may include one or more wireless wide area network (WWAN) transceivers, one or more short-range wireless transceivers, or one or more satellite transceivers. The WWAN transceiver(s) may communicate with (e.g., transmit one or more signals to, or receive one or more signals from) one or more wireless communication networks, such as an NR network, an LTE network, or a GSM network, among other examples. The WWAN transceiver(s) may be connected to one or more of the antenna(s) 1225 for communicating with other devices, such as one or more UEs 115, network nodes 105, access points, base stations (e.g., eNBs, gNBs), or another device(s), via at least one RAT (e.g.. NR, LTE, or GSM, among other examples) over a wireless communication medium (e.g., time or frequency resources of a frequency spectrum). The WWAN transceiver(s) may be configured for transmitting and encoding signals (e.g., messages, indications, or information, among other examples) or for receiving and decoding signals (e.g.. messages, indications, information, or pilots, among other examples), in accordance with the RAT. For instance, the WWAN transceiver(s) may include one or more transmitters for transmitting and encoding signals, or one or more receivers for receiving and decoding signals.

[0235] The short-range wireless transceivers may be connected to one or more of the antenna(s) 1225 to communicate with (e.g., transmit one or more signals to, or Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO79receive one or more signals from) one or more network entities, such as one or more UEs 115, network nodes 105, access points, base stations, or another device(s), via at least one RAT (e.g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), or ultra- wideband (UWB), among other examples) over a wireless communication medium. The short-range wireless transceiver(s) may be configured for transmitting and encoding signals (e.g., messages, indications, or information, among other examples), or for receiving and decoding signals (e.g., messages, indications, information, or pilots, among other examples), in accordance with the RAT. For instance, the short-range wireless transceiver(s) may include one or more transmitters for transmitting and encoding signals, or one or more receivers for receiving and decoding signals. In some examples, the short-range wireless transceiver(s) may be one or more Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® transceivers, Z-WAVE® transceivers, NFC transceivers, UWB transceivers, vehicle-to-vehicle (V2V) transceivers, or vehicle-to-every thing (V2X) transceivers, among other examples.

[0236] The satellite transceiver(s) may include one or more satellite signal receivers, or one or more satellite signal transmitters. In some cases, the device 1205 may be a terrestrial device that may communicate one or more satellites via the satellite transceiver(s). In other cases, device 1205 may be a satellite (or other non-terrestrial entity) that uses the satellite trans ceiver(s) to communicate with one or more terrestrial networks or other satellites.

[0237] The satellite signal receiver(s) may be connected to one or more of the antenna(s) 1225 for receiving or measuring satellite positioning or communication signals. In some examples, the satellite signal receiver(s) may include one or more satellite positioning system receivers, where the satellite positioning or communication signals may be GPS signals, GLONASS signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), or Quasi-Zemth Satellite System (QZSS) signals, among other examples. In some examples, the satellite signal receiver(s) may include one or more NTN receivers, where the satellite positioning or communication signals may be communication signals (e.g., carry ing control or user data) originating from a device or network. The satellite signal receiver(s) may includeAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO80hardware or a combination of hardware and instructions for receiving and processing satellite positioning or communication signals. The satellite signal receiver(s) or the processor 1240 may perform calculations to determine a location of the device 1205, the UE 115, the network node 105, or another device using measurements obtained from one or more satellite signals.

[0238] The one or more satellite signal transmitters may be connected to one or more of the antennas 1225 for transmitting satellite positioning communication signals. In some examples, the satellite signal transmitter(s) may be satellite positioning system transmitters, and the satellite positioning or communication signals may be GPS signals, GLONASS® signals, Galileo signals, BeiDou signals, NAVIC, or QZSS signals, among other examples. In some examples, the satellite signal transmitter(s) include one or more NTN transmitters, and the satellite positioning or communication signals may be communication signals (e.g.. carrying control or user data). The satellite signal transmitter(s) may comprise hardware or a combination of hardware and instructions for transmitting satellite positioning or communication signals.

[0239] The device 1205 may include one or more sensors 1250 coupled with the one or more processors 1240 for obtaining sensor data (e.g., image data, RF data, motion data, orientation data, or audio data, among other examples). For example, the one or more sensors 1250 may sense or detect movement or orientation information. In some aspects, the movement or orientation information may be independent from motion data derived from signals received by the one or more WWAN transceivers, the one or more short-range wireless transceivers, or the satellite signal interface. In some examples, the sensor(s) 1250 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), or any other type of movement detection sensor. Additionally, or alternatively, the one or more sensors 1250 may include an image sensor, camera, microphone, light detector, or pressure sensor, among other examples. In some aspects, the sensor(s) 1250 may include a plurality of different types of devices, and the device 1205 (e.g., sensor(s) or 1250 processor(s) 1240) may combine the outputs of the different types of devices to provide motion information. For example, the sensor(s) 1250 may use a combination of a multi-axis accelerometer sensors, orientation sensors, or image sensors to provide the ability toAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO81compute positions in two-dimensional (2D) or three-dimensional (3D) coordinate systems.

[0240] The at least one memory 1230 may include RAM and ROM. The at least one memory 1230 may store computer-readable, computer-executable, or processorexecutable code, such as the code 1235. The code 1235 may include instructions that, when executed by the at least one processor 1240, cause the device 1205 to perform various functions described herein. The code 1235 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory . In some cases, the code 1235 may not be directly executable by the at least one processor 1240 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1230 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0241] The at least one processor 1240 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1240 may be configured to operate a memory' array using a memory' controller. In some other cases, a memory' controller may be integrated into the at least one processor 1240. The at least one processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting authorization communications for positioning or sensing procedures). For example, the device 1205 or a component of the device 1205 may include at least one processor 1240 and at least one memory 1230 coupled with or to the at least one processor 1240, the at least one processor 1240 and the at least one memory 1230 configured to perform various functions described herein.

[0242] In some examples, the at least one processor 1240 may include multiple processors and the at least one memory 1230 may include multiple memories. One or Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO82more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 1240 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1240) and memory circuitry (which may include the at least one memory 1230)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1240 or a processing system including the at least one processor 1240 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1235 (e.g., processor-executable code) stored in the at least one memory 1230 or otherwise, to perform one or more of the functions described herein.

[0243] For example, the communications manager 1220 is capable of, configured to, or operable to support a means for obtaining a request to collect information that is based on a measurement for a positioning or sensing procedure. The communications manager 1220 is capable of, configured to, or operable to support a means for outputting, to a network entity, a request authorization query associated with the request, where the request authorization query indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof. The communications manager 1220 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an indication of whether the request is authorized.

[0244] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for enhanced positioning accuracy, improved communication reliability, reduced latency, reduced power consumption, more efficient utilization of communicationAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO83resources, improved coordination between devices, longer battery life, improved utilization of processing capability, or improved data security.

[0245] In some examples, the communications manager 1220 may be configured to perform various operations (e.g.. receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1215, the one or more antennas 1225. or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the at least one processor 1240, the at least one memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions executable by the at least one processor 1240 to cause the device 1205 to perform various aspects of authorization communications for positioning or sensing procedures as described herein, or the at least one processor 1240 and the at least one memory 1230 may be otherwise configured to, individually or collectively, perform or support such operations.

[0246] FIG. 13 shows a block diagram 1300 of a device 1305 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of aspects of a network device as described herein. The device 1305 may include a receiver 1310, atransmitter 1315, and a communications manager 1320. The device 1305, or one or more components of the device 1305 (e.g., the receiver 1310, the transmitter 1315, the communications manager 1320), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0247] The receiver 1310 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1305. In some examples, the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1310 may support obtaining information by Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO84receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0248] The transmitter 1315 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1305. For example, the transmitter 1315 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled with a modem.

[0249] The communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be examples of means for performing various aspects of authorization communications for positioning or sensing procedures as described herein. For example, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0250] In some examples, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardw are components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO85

[0251] Additionally, or alternatively, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0252] In some examples, the communications manager 1320 may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both. For example, the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0253] For example, the communications manager 1320 is capable of, configured to, or operable to support a means for outputting, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a ty pe of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof. The communications manager 1320 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an indication of whether the authorization request is accepted.

[0254] For example, the communications manager 1320 is capable of, configured to, or operable to support a means for obtaining an authorization inquiry related to Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO86collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure. The communications manager 1320 is capable of, configured to, or operable to support a means for determining whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry. The communications manager 1320 is capable of, configured to, or operable to support a means for outputting an indication of whether the authorization inquiry is validated.

[0255] By including or configuring the communications manager 1320 in accordance with examples as described herein, the device 1305 (e.g., at least one processor controlling or otherwise coupled with the receiver 1310, the transmitter 1315, the communications manager 1320, or any combination thereof) may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources, or increased data security.

[0256] FIG. 14 shows a block diagram 1400 of a device 1405 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The device 1405 may be an example of aspects of a device 1305 or a network device as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communications manager 1420. The device 1405, or one or more components of the device 1405 (e.g.. the receiver 1410, the transmitter 1415, the communications manager 1420), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0257] The receiver 1410 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1405. In some examples, the receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1410 may support obtaining information byAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO87receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0258] The transmitter 1415 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1405. For example, the transmitter 1415 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1415 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1415 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include or be coupled with a modem.

[0259] The device 1405, or various components thereof, may be an example of means for performing various aspects of authorization communications for positioning or sensing procedures as described herein. For example, the communications manager 1420 may include an authorization request manager 1425, an indication manager 1430, an authorization inquiry manager 1435, or any combination thereof. The communications manager 1420 may be an example of aspects of a communications manager 1320 as described herein. In some examples, the communications manager 1420. or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1410, the transmitter 1415, or both. For example, the communications manager 1420 may receive information from the receiver 1410, send information to the transmitter 1415, or be integrated in combination with the receiver 1410, the transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.

[0260] The authorization request manager 1425 is capable of, configured to, or operable to support a means for outputting, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO88positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof. The indication manager 1430 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an indication of whether the authorization request is accepted.

[0261] The authorization inquiry manager 1435 is capable of. configured to, or operable to support a means for obtaining an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure. The authorization inquiry manager 1435 is capable of, configured to, or operable to support a means for determining whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry. The authorization inquiry manager 1435 is capable of, configured to, or operable to support a means for outputting an indication of whether the authorization inquiry is validated.

[0262] FIG. 15 shows a block diagram 1500 of a communications manager 1520 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The communications manager 1520 may be an example of aspects of a communications manager 1320, a communications manager 1420, or both, as described herein. The communications manager 1520, or various components thereof, may be an example of means for performing various aspects of authorization communications for positioning or sensing procedures as described herein. For example, the communications manager 1520 may include an authorization request manager 1525, an indication manager 1530, an authorization inquiry manager 1535, a request manager 1540, a configuration manager 1545. an authorization manager 1550, a time manager 1555, an identification manager 1560, an inquiry manager 1565, an attribute manager 1570, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO89

[0263] The authorization request manager 1525 is capable of, configured to, or operable to support a means for outputting, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a ty pe of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof. The indication manager 1530 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an indication of whether the authorization request is accepted.

[0264] In some examples, the indication of whether the authorization request is accepted indicates that the authorization request is not accepted and indicates one or more permitted parameters.

[0265] In some examples, the indication of whether the authorization request is accepted indicates a prioritization or a different positioning or sensing procedure.

[0266] In some examples, the request manager 1540 is capable of, configured to, or operable to support a means for outputting, to the wireless device, a request to collect the information, where the request includes an authorization message from the network entity.

[0267] In some examples, the configuration manager 1545 is capable of, configured to, or operable to support a means for obtaining, from the network entity, configuration information indicating one or more candidate parameters for the positioning or sensing procedure, the one or more candidate parameters including a candidate area, a candidate device that is authorized to request a start or end of the positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

[0268] In some examples, a session of the positioning or sensing procedure begins or expires by an expiration of a timer from a time of the authorization request.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO90

[0269] The authorization inquiry manager 1535 is capable of, configured to, or operable to support a means for obtaining an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure. In some examples, the authorization inquiry manager 1535 is capable of, configured to, or operable to support a means for determining whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry . In some examples, the authorization inquiry' manager 1535 is capable of, configured to, or operable to support a means for outputting an indication of whether the authorization inquiry is validated.

[0270] In some examples, the authorization inquiry is a request authorization query' associated with a request from a source to the wireless device to collect the information, the one or more attributes of the request including an identifier of the source of the request, a period of the request, a reporting target for the information, a t pe of the information, an area corresponding to the request, a condition for the request, or any combination thereof. In some examples, the determination whether to validate the authorization inquiry is based on a satisfaction of a validation criterion by the one or more attributes.

[0271] In some examples, the indication of yvhether the authorization inquiry is validated indicates that the request is not authorized and indicates one or more permitted responses to the request.

[0272] In some examples, to support outputting the indication of whether the authorization inquiry' is validated, the authorization inquiry' manager 1535 is capable of, configured to, or operable to support a means for outputting, to a network node, an authorization message for inclusion in a request from the network node to the wireless device to collect the information that is based on the measurement at the wireless device for the positioning or sensing procedure.

[0273] In some examples, the configuration manager 1545 is capable of, configured to, or operable to support a means for outputting, to the wireless device, configuration information indicating one or more candidate attributes for a second positioning or sensing procedure, the one or more candidate attributes including a candidate area, a candidate device that is authorized to request a start or end of the second positioning orAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO91sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity' area, a candidate validity' timer, a candidate invalidity event, or any combination thereof.

[0274] In some examples, the attribute manager 1570 is capable of, configured to, or operable to support a means for obtaining, from the wireless device, an indication of a selection of the one or more candidate attributes for the second positioning or sensing procedure. In some examples, the attribute manager 1570 is capable of, configured to, or operable to support a means for outputting, to the wireless device, an acceptance or a denial of the selection of the one or more candidate attributes.

[0275] In some examples, the attribute manager 1570 is capable of. configured to, or operable to support a means for outputting, to the wireless device, an indication of a second selection of the one or more candidate attributes, where the denial of the selection of the one or more candidate attributes is output.

[0276] In some examples, the attribute manager 1570 is capable of, configured to, or operable to support a means for obtaining, from the wireless device, an indication of a rejection of at least one of the one or more candidate attributes for the second positioning or sensing procedure. In some examples, the attribute manager 1570 is capable of, configured to, or operable to support a means for obtaining, from the wireless device, an indication of one or more second candidate attributes for the second positioning or sensing procedure.

[0277] In some examples, the authorization manager 1550 is capable of, configured to, or operable to support a means for communicating information indicating that a second positioning or sensing procedure is unauthorized, or indicating one or more unauthorized attributes for a second positioning or sensing procedure, the one or more unauthorized attributes including an unauthorized area, an unauthorized device for the positioning or sensing procedure, an unauthorized type of measurement information, an unauthorized information granularity, an unauthorized duration, an unauthorized purpose, or any combination thereof.

[0278] In some examples, the authorization inquiry is an authorization request from a network node for obtaining the information that is based on a measurement at the wireless device for the positioning or sensing procedure. In some examples, theAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO92authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof.

[0279] In some examples, the indication of whether the authorization inquiry is validated indicates that the authorization inquiry' is not validated and indicates one or more permitted parameters.

[0280] In some examples, the indication of whether the authorization inquiry is validated indicates a prioritization or a different positioning or sensing procedure.

[0281] In some examples, the configuration manager 1545 is capable of, configured to, or operable to support a means for outputting, to a network node, configuration information indicating one or more candidate parameters for the positioning or sensing procedure, the one or more candidate parameters including a candidate area, a candidate device that is authorized to request a start or end of the positioning or sensing procedure, a candidate t pe of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

[0282] In some examples, the time manager 1555 is capable of, configured to, or operable to support a means for initiating a timer based on a time of the authorization inquiry. In some examples, the identification manager 1560 is capable of, configured to, or operable to support a means for obtaining, from a location server, identification information of the wireless device. In some examples, the inquiry manager 1565 is capable of, configured to, or operable to support a means for outputting, to the wireless device based on the identification information, an inquiry of whether the wireless device accepts the positioning or sensing procedure. In some examples, the time manager 1555 is capable of, configured to, or operable to support a means for obtaining, from the wireless device, an indication of whether the wireless device accepts the positioning or sensing procedure, where a session of the positioning or sensing procedure begins or expires by an expiration of the timer from the time of the authorization inquiry.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO93

[0283] FIG. 16 shows a diagram of a system 1600 including a device 1605 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The device 1605 may be an example of or include components of a device 1305, a device 1405, or network device(s) 420 as described herein. The device 1605 may include components for bidirectional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1620, one or more transceivers 1610, one or more antennas 1615, at least one memory 1625, code 1630, and at least one processor 1635. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1640).

[0284] The transceiver 1610 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1610 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1610 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1605 may include one or more antennas 1615, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1610 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1615, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1615, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1610 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1615 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1615 that are configured to support various transmitting or outputting operations, or any combination thereof. In some implementations, the transceiver 1610 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1610, or the transceiver 1610 and the one or moreAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO94antennas 1615, or the transceiver 1 10 and the one or more antennas 1615 and one or more processors or one or more memory7components (e.g., the at least one processor 1635. the at least one memory 1625, or both), may be included in a chip or chip assembly that is installed in the device 1605. In some examples, the transceiver 1610 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).

[0285] The one or more transceivers 1610 may include one or more WWAN transceivers, one or more short-range wireless transceivers, or one or more satellite transceivers. The WWAN transceiver(s) may communicate with (e.g., transmit one or more signals to, or receive one or more signals from) one or more wireless devices, such as the network node 105 or the UE 115, among other examples. The WWAN transceiver(s) may be connected to one or more of the antenna(s) 1615 for communicating with other devices, such as one or more UEs 115, network nodes 105, access points, base stations (e g., eNBs, gNBs), or another device(s), via at least one RAT (e.g., NR, LTE, or GSM, among other examples) over a wireless communication medium (e.g., time or frequency resources of a frequency spectrum). The WWAN transceiver(s) may be configured for transmitting and encoding signals (e.g., messages, indications, or information, among other examples) or for receiving and decoding signals (e.g., messages, indications, information, or pilots, among other examples), in accordance with the RAT. For instance, the WWAN transceiver(s) may include one or more transmitters for transmitting and encoding signals, or one or more receivers for receiving and decoding signals.

[0286] The short-range wireless transceivers may be connected to one or more of the antenna(s) 1615 to communicate with (e.g., transmit one or more signals to, or receive one or more signals from) one or more network entities, such as one or more UEs 115. network nodes 105, access points, base stations, or another device(s). via at least one RAT (e g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, DSRC, WAVE, NFC, or UWB, among other examples) over a wireless communication medium. The short-range wireless transceiver(s) may be configured for transmitting and encoding signals (e.g., messages, indications, or information, among other examples), or for receiving and decoding signals (e.g., messages, indications.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO95information, or pilots, among other examples), in accordance with the RAT. For instance, the short-range wireless trans ceiver(s) may include one or more transmitters for transmitting and encoding signals, or one or more receivers for receiving and decoding signals. In some examples, the short-range wireless transceiver(s) may be one or more Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® transceivers, Z-WAVE® transceivers, NFC transceivers, UWB transceivers, V2V transceivers, or V2X transceivers, among other examples.

[0287] The satellite transceiver(s) may include one or more satellite signal receivers, or one or more satellite signal transmitters. In some cases, the device 1605 may be a terrestrial device that may communicate one or more satellites via the satellite transceiver(s). In other cases, device 1 05 may be a satellite (or other non-terrestrial entity ) that uses the satellite trans ceiver(s) to communicate with one or more terrestrial networks or other satellites.

[0288] The satellite signal receiver(s) may be connected to one or more of the antenna(s) 1615 for receiving or measuring satellite positioning or communication signals. In some examples, the satellite signal receiver(s) may include one or more satellite positioning system receivers, where the satellite positioning or communication signals may be GPS signals, GLONASS signals, Galileo signals, BeiDou signals, NAVIC, or QZSS signals, among other examples. In some examples, the satellite signal receiver(s) may include one or more NTN receivers, where the satellite positioning or communication signals may be communication signals (e.g., carrying control or user data) originating from a device or network. The satellite signal receiver(s) may include hardware or a combination of hardware and instructions for receiving and processing satellite positioning or communication signals. The satellite signal receiver(s) or the processor 1635 may perform calculations to determine a location of the device 1605, the UE 115, the network node 105, or another device using measurements obtained from one or more satellite signals.

[0289] The one or more satellite signal transmitters may be connected to one or more of the antennas 1615 for transmitting satellite positioning communication signals. In some examples, the satellite signal transmitter(s) may be satellite positioning system transmitters, and the satellite positioning or communication signals may be GPS signals, GLONASS® signals, Galileo signals, BeiDou signals, NAVIC. or QZSS signals, among Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO96other examples. In some examples, the satellite signal transmitter(s) include one or more NTN transmitters, and the satellite positioning or communication signals may be communication signals (e.g., carrying control or user data). The satellite signal transmitter(s) may comprise hardware or a combination of hardware and instructions for transmitting satellite positioning or communication signals.

[0290] The at least one memory 1625 may include RAM, ROM, or any combination thereof. The at least one memory 1625 may store computer-readable, computerexecutable, or processor-executable code, such as the code 1630. The code 1630 may include instructions that, when executed by one or more of the at least one processor 1635, cause the device 1605 to perform various functions described herein. The code 1 30 may be stored in a non-transitory computer-readable medium such as system memory7or another ty pe of memory7. In some cases, the code 1630 may not be directly executable by a processor of the at least one processor 1635 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1625 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1635 may include multiple processors and the at least one memory 1625 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0291] The at least one processor 1635 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1635 may be configured to operate a memory7array using a memory7controller. In some other cases, a memory7controller may be integrated into one or more of the at least one processor 1635. The at least one processor 1635 may be configured to execute computer-readable instructions stored in a memory (e.g.. one orAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO97more of the at least one memory 1625) to cause the device 1 05 to perform various functions (e.g., functions or tasks supporting authorization communications for positioning or sensing procedures). For example, the device 1605 or a component of the device 1605 may include at least one processor 1635 and at least one memory 1625 coupled with one or more of the at least one processor 1635, the at least one processor 1635 and the at least one memory 1625 configured to perform various functions described herein. The at least one processor 1635 may be an example of a cloudcomputing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1630) to perform the functions of the device 1605. The at least one processor 1635 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1605 (such as within one or more of the at least one memory 1625).

[0292] In some examples, the at least one processor 1635 may include multiple processors and the at least one memory 1625 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1635 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1635) and memory circuitry (which may include the at least one memory 1625)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1635 or a processing system including the at least one processor 1635 may be configured to, configurable to, or operable to cause the device 1605 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory' 1625 or otherwise, to perform one or more of the functions described herein.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO98

[0293] In some examples, a bus 1640 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1640 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1605, or between different components of the device 1605 that may be co-located or located in different locations (e.g., where the device 1605 may refer to a system in which one or more of the communications manager 1620, the transceiver 1610, the at least one memory 1625, the code 1630, and the at least one processor 1635 may be located in one of the different components or divided between different components).

[0294] In some examples, the communications manager 1620 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1620 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1 20 may manage communications with one or more other network nodes 105, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices). In some examples, the communications manager 1620 may support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network nodes 105.

[0295] In some examples, the communications manager 1620 is capable of, configured to, or operable to support a means for outputting, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof. The communications manager 1620 is capable of, configured to, or operable to support a means for obtaining, from the network entity, an indication of whether the authorization request is accepted.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO99

[0296] In some examples, the communications manager 1620 is capable of, configured to, or operable to support a means for obtaining an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure. The communications manager 1620 is capable of, configured to, or operable to support a means for determining whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry. The communications manager 1620 is capable of, configured to, or operable to support a means for outputting an indication of whether the authorization inquiry is validated.

[0297] By including or configuring the communications manager 1620 in accordance with examples as described herein, the device 1605 may support techniques for increased positioning accuracy, improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, or increased data security.

[0298] In some examples, the communications manager 1620 may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1610, the one or more antennas 1615 (e g., where applicable), or any combination thereof. Although the communications manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1620 may be supported by or performed by the transceiver 1610, one or more of the at least one processor 1635, one or more of the at least one memory 1625, the code 1630, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1635, the at least one memory 1625, the code 1630, or any combination thereof). For example, the code 1630 may include instructions executable by one or more of the at least one processor 1635 to cause the device 1605 to perform various aspects of authorization communications for positioning or sensing procedures as described herein, or the at least one processor 1635 and the at least one memory 1625 may be otherw ise configured to, individually or collectively, perform or support such operations.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO100

[0299] FIG. 17 shows a flowchart illustrating a method 1700 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a wireless device or its components as described herein. For example, the operations of the method 1700 may be performed by a wireless device as described with reference to FIGs. 1 through 12. In some examples, a wireless device may execute a set of instructions to control the functional elements of the wireless device to perform the described functions. Additionally, or alternatively, the wireless device may perform aspects of the described functions using special-purpose hardware.

[0300] At 1705, the method may include obtaining a request to collect information that is based on a measurement for a positioning or sensing procedure. The operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a request component 1125 as described with reference to FIG. 11.

[0301] At 1710, the method may include outputting, to a network entity, a request authorization query associated with the request, where the request authorization query indicates one or more attributes of the request, the one or more attributes including an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof. The operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a query' component 1130 as described with reference to FIG. 11.

[0302] At 1715, the method may include obtaining, from the network entity, an indication of whether the request is authorized. The operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by an indication component 1135 as described with reference to FIG. 11.

[0303] FIG. 18 shows a flowchart illustrating a method 1800 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The operations of the method 1800 mayAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO101be implemented by a wireless device or its components as described herein. For example, the operations of the method 1800 may be performed by a wireless device as described with reference to FIGs. 1 through 12. In some examples, a wireless device may execute a set of instructions to control the functional elements of the wireless device to perform the described functions. Additionally, or alternatively, the wireless device may perform aspects of the described functions using special-purpose hardware.

[0304] At 1805, the method may include obtaining, from a network entity, configuration information indicating one or more candidate attributes for a positioning or sensing procedure, the one or more candidate attributes including a candidate area, a candidate device that is authorized to request a start or end of the positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity7, a candidate validity area, a candidate validity' timer, a candidate invalidity event, or any combination thereof. The operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a configuration component 1145 as described with reference to FIG. 11.

[0305] At 1810, the method may include outputting, to the network entity', an indication of a selection of the one or more candidate attributes for the positioning or sensing procedure. The operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by an attribute component 1155 as described with reference to FIG. 11.

[0306] At 1815, the method may include obtaining, from the network entity, an acceptance or a denial of the selection of the one or more candidate attributes. The operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by an attribute component 1155 as described with reference to FIG. 11.

[0307] FIG. 19 shows a flowchart illustrating a method 1900 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a network device or its components as described herein. For example, the operations of the method 1900 may be performed by a network device asAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO102described with reference to FIGs. 1 through 24 and 13 through 16. In some examples, a network device may execute a set of instructions to control the functional elements of the network device to perform the described functions. Additionally, or alternatively, the network device may perform aspects of the described functions using specialpurpose hardware.

[0308] At 1905, the method may include outputting, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof. The operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by an authorization request manager 1525 as described with reference to FIG. 15.

[0309] At 1910, the method may include obtaining, from the netw ork entity, an indication of whether the authorization request is accepted. The operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by an indication manager 1530 as described with reference to FIG. 15.

[0310] FIG. 20 show s a flow chart illustrating a method 2000 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a network device or its components as described herein. For example, the operations of the method 2000 may be performed by a netw ork device as described with reference to FIGs. 1 through 24 and 13 through 16. In some examples, a network device may execute a set of instructions to control the functional elements of the network device to perform the described functions. Additionally, or alternatively, the network device may perform aspects of the described functions using specialpurpose hardware.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO103

[0311] At 2005, the method may include outputting, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, where the authorization request indicates one or more parameters, the one or more parameters including an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof. The operations of 2005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed by an authorization request manager 1525 as described with reference to FIG. 15.

[0312] At 2010, the method may include obtaining, from the netw ork entity, an indication of whether the authorization request is accepted. The operations of 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by an indication manager 1530 as described with reference to FIG. 15.

[0313] At 2015, the method may include outputting, to the wireless device, a request to collect the information, where the request includes an authorization message from the network entity. The operations of 2015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a request manager 1540 as described with reference to FIG. 15.

[0314] FIG. 21 show s a flow chart illustrating a method 2100 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The operations of the method 2100 may be implemented by a network device or its components as described herein. For example, the operations of the method 2100 may be performed by a netw ork device as described with reference to FIGs. 1 through 8 and 13 through 16. In some examples, a network device may execute a set of instructions to control the functional elements of the network device to perform the described functions. Additionally, or alternatively, the network device may perform aspects of the described functions using specialpurpose hardware.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO104

[0315] At 2105, the method may include obtaining an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure. The operations of 2105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed by an authorization inquiry manager 1535 as described with reference to FIG. 15.

[0316] At 2110, the method may include determining whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry. The operations of 2110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed by an authorization inquiry manager 1535 as described with reference to FIG. 15.

[0317] At 2115, the method may include outputting an indication of whether the authorization inquiry is validated. The operations of 2115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed by an authorization inquiry manager 1535 as described with reference to FIG. 15.

[0318] FIG. 22 shows a flowchart illustrating a method 2200 that supports authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. The operations of the method 2200 may be implemented by a network device or its components as described herein. For example, the operations of the method 2200 may be performed by a network device as described with reference to FIGs. 1 through 8 and 13 through 16. In some examples, a network device may execute a set of instructions to control the functional elements of the network device to perform the described functions. Additionally, or alternatively, the network device may perform aspects of the described functions using specialpurpose hardware.

[0319] At 2205, the method may include obtaining an authorization inquiry related to collection of information that is based on a measurement at a wireless device for a positioning or sensing procedure. The operations of 2205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of theAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO105operations of 2205 may be performed by an authorization inquiry manager 1535 as described with reference to FIG. 15.

[0320] At 2210, the method may include initiating a timer based on a time of the authorization inquiry. The operations of 2210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2210 may¬ be performed by a time manager 1555 as described with reference to FIG. 15.

[0321] At 2215, the method may include obtaining, from a location server, identification information of the wireless device. The operations of 2215 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed by an identification manager 1560 as described with reference to FIG. 15.

[0322] At 2220, the method may include outputting, to the wireless device based on the identification information, an inquiry- of whether the wireless device accepts the positioning or sensing procedure. The operations of 2220 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2220 may be performed by an inquiry manager 1565 as described with reference to FIG. 15.

[0323] At 2225, the method may include obtaining, from the wireless device, an indication of whether the wireless device accepts the positioning or sensing procedure, where a session of the positioning or sensing procedure begins or expires by an expiration of the timer from the time of the authorization inquiry. The operations of 2225 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2225 may be performed by a time manager 1555 as described with reference to FIG. 15.

[0324] At 2230, the method may include determining whether to validate the authorization inquiry based on one or more attributes or parameters of the authorization inquiry-. The operations of 2230 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2230 may be performed by an authorization inquiry manager 1535 as described with reference to FIG. 15.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO106

[0325] At 2235, the method may include outputting an indication of whether the authorization inquiry' is validated. The operations of 2235 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2235 may be performed by an authorization inquiry manager 1535 as described with reference to FIG. 15.

[0326] FIG. 23 shows examples of wireless communications systems 2300 that support authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. Various positioning or sensing techniques are illustrated in the context of the wireless communications systems 2300. Some examples of the positioning or sensing procedures described herein may be performed in accordance with one or more aspects of the positioning or sensing techniques. While TRPs and UEs are provided in the examples illustrated in FIG. 23, other devices (e.g., network entities, base stations. RRHs, RUs, APs, wireless devices, or stations, among other examples) may be similarly utilized in other examples. The examples of positioning or sensing techniques include downlink-based positioning or sensing techniques, uplink-based positioning or sensing techniques, and downlink-and-uplink-based positioning or sensing techniques.

[0327] Examples of OTDOA or DL-TDOA 2305 are illustrated in FIG. 23. One or more of the OTDOA or DL-TDOA 2305 positioning or sensing techniques may be included in a downlink-based positioning or sensing procedure. In OTDOA or DL-TDOA 2305 positioning or sensing techniques, a UE may measure a difference between TOAs of reference signals (e.g., PRSs) received from one or more pairs of TRPs (e.g., TRP2 and TRP3). In some approaches, a difference in TOAs may be referred to as an RSTD or aTDOA measurement. A positioning or sensing device (e.g., the UE, a location server, an LMF, an SLP, or another device) may utilize the differences in TOAs to determine (e.g., estimate) a location of the UE.

[0328] In some aspects, the UE may receive an identifier (ID) associated with a reference TRP (e.g., a serving base station) and one or more IDs associated with one or more non-reference TRPs in received data (e.g., assistance data). The UE may measure the difference of TOAs between the reference TRP and each of the non-reference TRPs to produce RSTDs or TDOAs. In some aspects, the UE may report an indication of the RSTDs or TDOAs to the positioning or sensing device (e.g., a location server, LMF, an Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO107SLP, or another device). Based on established locations of the base stations and the RSTD measurements, the positioning or sensing device (e.g., the UE for UE-based positioning or sensing or a location server for UE-assisted positioning or sensing) may estimate the UE’s location.

[0329] An example of UL-TDOA 2310 is illustrated in FIG. 23. One or more of the UL-TDOA 2310 positioning or sensing techniques may be included in an uplink-based positioning or sensing procedure. UL-TDOA 2310 may have some similarities to DL-TDOA 2305. The UL-TDOA 2310 positioning or sensing techniques may be based on uplink reference signals (e.g., SRS) transmitted from the UE to multiple TRPs. For example, the UE transmits one or more uplink reference signals that are measured by a reference TRP (e.g., TRP3) and non-reference TRPs (e g., TRP1 and TRP2). Each TRP then reports the reception time (which may be referred to as a RTOA) of the reference signal(s) to a positioning or sensing device (e.g., a location server, LMF, SLP, or UE) that has information about the locations and relative timing of the TRPs. Based on the reception-to-reception (Rx-Rx) time differences between the reported RTOA of the reference TRP and the reported RTOA of each non-reference TRP, the locations of the TRPs, and the corresponding timing offsets, the positioning or sensing device may estimate the location of the UE using TDOA.

[0330] An example of DL-AOD 2315 is illustrated in FIG. 23. One or more of the DL-AOD 2315 positioning or sensing techniques may be included in a downlink-based positioning or sensing procedure. In DL-AOD 2315, a UE may obtain received signal strength measurements corresponding to multiple downlink transmit beams for one or more TRPs (e.g.. TRP1 and TRP2). In some approaches, the UE reports the measurements to a positioning or sensing device. The positioning or sensing device may use the signal strength measurements of the multiple downlink transmit beams to determine the angle(s) (e.g., AOD1 and AOD2) between the UE and the transmitting TRP(s). The positioning or sensing device (e.g., location server, LMF, SLP, UE, or another device) may estimate the location of the UE based on the determined angle(s) and the established location(s) of the transmitting TRP(s).

[0331] An example of UL-AOA 2320 is illustrated in FIG. 23. One or more of the UL-AOA 2320 positioning or sensing techniques may be included in an uplink positioning or sensing procedure. In UL-AOA 2320, one or more TRPs (e.g., TRP1 and Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO108TRP2) measure the received signal strength of one or more uplink reference signals (e.g., SRSs) received from aUE on one or more uplink receive beams. In some aspects, the signal strength measurements may be reported to a positioning or sensing device. A positioning or sensing device (e.g., LFM, SLP, UE, or another device) may use the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the TRP(s). Based on the determined angle(s) and the established location(s) of the TRP(s), the positioning or sensing device may estimate the location of the UE.

[0332] Some positioning or sensing techniques or procedures may include a combination downlink-based and uplink-based positioning or sensing techniques.Examples of downlink -based and uplink-based positioning or sensing techniques may include E-CID positioning or sensing and multi-round-trip-time (RTT) positioning or sensing (which may be referred to as “multi-RTT” or “multi-cell RTT " when multiple cells are utilized).

[0333] In multi -RTT, a first device (e.g., a TRP or UE) may transmit a first RTT-related signal (e.g., aPRS or SRS) to a second device (e.g., the UE or TRP). The second device may transmit a second RTT-related signal (e.g., an SRS or PRS) back to the first device. Each device may measure a time difference between the TOA of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. The time difference may be referred to as a reception-to-transmission (Rx-Tx) time difference. In some aspects, the Rx-Tx time difference measurement may be obtained or adjusted to include (e.g., include only) a time difference between nearest slot boundaries for the received and transmitted signals. The first device or the second device may send the corresponding Rx-Tx time difference measurements to a positioning or sensing device (e.g., a location server, LMF, SLP, UE, or other device), which may calculate a round trip propagation time (or RTT) betw een the two device based on the tw o Rx-Tx time difference measurements (e.g., as a sum of the two Rx-Tx time difference measurements). Additionally, or alternatively, one device may send a corresponding Rx-Tx time difference measurement to the other device, which may calculate the RTT. The distance betw een the two devices may be determined from the RTT and a signal speed (e.g., the speed of light).Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO109

[0334] An example of multi-cell RTT 2325 is illustrated in FIG. 23. One or more of the multi-RTT or multi-cell RTT techniques described may be included in an uplinkbased or downlink-based positioning or sensing procedure. In multi-cell RTT 2325, a first device (e.g., a UE or TRP) may perform an RTT positioning or sensing procedure with multiple second devices (e.g., multiple TRPs or UEs) to enable the location of the first device to be determined (e.g., using multilateration) based on distances to, and the established locations of, the second devices.

[0335] In some examples, RTT or multi-RTT techniques may be combined with one or more other positioning or sensing techniques (e.g., UL-AOA, DL-AOD, or other positioning or sensing techniques), to enhance location accuracy. Examples of combined DL-AOD and RTT 2330 positioning or sensing techniques are illustrated in FIG. 23.

[0336] E-CID positioning or sensing techniques (not show n in FIG. 23) may be based on radio resource management (RRM) measurements. In E-CID, a UE may obtain or report a serving cell ID, a timing advance (TA), identifiers of one or more detected neighbor TRPs, estimated timing of one or more detected neighbor TRPs, or a signal strength measurement of one or more detected neighbor TRPs. A positioning or sensing device (e g., an LFM, SLP, UE, or another device) may utilize the serving cell ID, TA, identifiers, estimated timing, or signal strength measurements with one or more established locations of one or more TRPs to estimate the location of the UE.

[0337] In some approaches, a positioning or sensing device (e.g., location server, LMF, SLP, or another device) may provide assistance data to the UE. Assistance data is data to assist with one or more positioning or sensing operations (e.g., to detect one or more neighboring TRPs or to receive reference signaling). For instance, the assistance data may indicate IDs of the TRPs (e.g., IDs of one or more cells or TRPs corresponding to a network node) from which reference signals may be measured. In some examples, a positioning or sensing device may transmit assistance data or other information indicating one or more reference signal configuration parameters. The reference signal configuration parameter(s) may include or indicate a quantity of consecutive slots including PRS, a periodicity of consecutive slots including PRS, a muting sequence, a frequency hopping sequence, a reference signal identifier, a reference signal bandwidth, or one or more other parameters applicable to a positioning Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO110or sensing technique or procedure. Additionally, or alternatively, the assistance data may be sent from one or more TRPs (e.g., in periodically broadcasted overhead messages, a scheduled message, a unicast message, or a multicast message, among other examples). In some examples, a UE may be able to detect one or more neighboring TRPs (e.g., network entities) without the use of assistance data.

[0338] For OTDOA positioning or sensing techniques or DL-TDOA positioning or sensing techniques, the assistance data may indicate an expected RSTD value and an associated uncertainty or search window around the expected RSTD. For example, an expected RSTD value may have an associated uncertainty or search window with a range of ±500 microseconds (ps). In another example, when any of the resources used for the positioning or sensing measurement(s) are in frequency range 1 (FR1), an expected RSTD value may have an associated uncertainty or search window with a range of ±32 ps. In another example, when all of the resources used for the positioning or sensing measurement(s) are in frequency range 2 (FR2), an expected RSTD value may have an associated uncertainty or search window with a range of ±8 ps.

[0339] In some examples, a location may be referred to as a position estimate, location estimate, position, position fix, or fix, among other examples. A location may be geodetic and include coordinates (e.g., latitude, longitude, or altitude) or may be civic and include a street address, postal address, or another description of a location. In some aspects, a location may be defined relative to another location or may be defined in absolute terms (e.g., latitude, longitude, or altitude). A location may include an indication of error or uncertainty (e.g., by including an area or volume within which the location may be included with a specified or default level of confidence).

[0340] Various examples of sidelink positioning or sensing techniques are illustrated in FIG. 23. Sidelink positioning or sensing techniques may include positioning or sensing techniques that are based on sidelink communication (e.g., based exclusively on sidelink communication or based on sidelink communication jointly with other communication(s), such as Uu interface communication).

[0341] A first example of sidelink positioning or sensing 2335 is illustrated in FIG. 23. In the first example of sidelink positioning or sensing 2335, at least one peer UE with an established location may improve location estimation (e.g., Uu-basedAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WOI llpositioning or sensing, multi-cell RTT, DL-TDOA, or UL-TDOA, among other examples) for a target UE by providing an additional anchor (e.g., sidelink RTT (SL-RTT)).

[0342] A second example of sidelink positioning or sensing 2340 is illustrated in FIG. 23. In the second example of sidelink positioning or sensing 2340, different types (e.g., categories, classes, or capabilities) of UEs may be utilized. For example, first UEs and a second UE may be utilized. Relative to the second UE, the first UEs may have one or more increased capabilities, such as one or more additional sensors, a faster processor, greater memory capacity, one or more additional antenna elements, a higher transmit power capability, access to one or more additional frequency bands, or any combination thereof. In some aspects, the second UE may be a reduced capacity or “RedCap” UE. The second UE may be assisted by the first UEs to determine the location of the second UE. For instance, sidelink-based positioning or sensing or ranging procedures may be performed with the first UEs, which may enhance the location accuracy of the second UE.

[0343] A third example of sidelink positioning or sensing 2345 is illustrated in FIG. 23. The third example of sidelink positioning or sensing 2345 may be performed via one or more sidelink connections (e.g., via sidelink connections exclusively or jointly with one or more Uu-based connections). In the third example of sidelink positioning or sensing 2345, the UEs may perform peer-to-peer (P2P) positioning or sensing or ranging. Sidelink positioning or sensing may be helpful for out-of-coverage or public safety scenarios. For instance, the UEs may be out of coverage of a network and may determine a location or a relative distance and a relative position among the UEs using sidelink positioning or sensing techniques. In some examples, sidelink positioning or sensing may be performed by UEs in public safety scenarios (e.g., for police, firefighters, search-and-rescue, or paramedics, among other examples).

[0344] A fourth example of sidelink positioning or sensing 2350 is illustrated in FIG. 23. The fourth example of sidelink positioning or sensing 2350 may be performed via one or more sidelink connections (e.g., via sidelink connections exclusively or jointly with one or more Uu-based connections). In the fourth example of sidelink positioning or sensing 2350, one or more of the UEs may determine a location or a relative distance and a relative position using sidelink positioning or sensing techniques, Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO112such as SL-RTT. For instance, one or more of the UEs may be out of coverage of a network and may determine a location or a relative distance and a relative position among the UEs using sidelink positioning or sensing techniques.

[0345] An example of relay positioning or sensing 2355 is illustrated in FIG. 23. In the example of relay positioning or sensing 2355, a relay UE (e.g., with an established location) may participate in the location estimation of a remote UE (without performing uplink reference signal transmission over the Uu interface, for instance). For example, the relay UE may receive a downlink PRS from a TRP and may relay an SL-PRS to the remote UE. In some cases, the remote UE may also receive another downlink PRS from the TRP. A positioning or sensing device (e.g., location server, LMF, SLP, UE, or other device) may utilize a downlink PRS measurement and an SL-PRS measurement with the established location of the relay UE to estimate the location of the remote UE.

[0346] An example of joint positioning or sensing 2360 is illustrated in FIG. 23. In the example of joint positioning or sensing 2360, multiple peer UEs (without established locations, for instance) may be located. In some approaches, multiple peer UEs may be jointly located in NLOS conditions by utilizing one or more constraints from one or more peer (e.g., neighboring or nearby) UEs. As illustrated in FIG. 23, RTT or TDOA techniques may be performed between TRP 1 and each of the peer UEs, may be performed between TRP2 and each of the peer UEs, and may be performed between the peer UEs. In some examples, one or more of the peer UEs may report measurements from the RTT or TDOA technique(s) to a positioning or sensing device. The positioning or sensing device (e.g., location server, LMF, SLP, UE, or other device) may utilize the measurements from the RTT or TDOA technique(s) to estimate the locations of the peer UEs.

[0347] Some aspects of the techniques described herein may be performed in conjunction with one or more of the positioning or sensing techniques described with reference to FIG. 23. For instance, one or more samples of a reference signal (e.g., PRS, SRS, or other reference signal) may be measured or transmitted in accordance with one or more of the techniques described with reference to FIG. 4 for one or more of the positioning or sensing techniques. For instance, data collection may be performed based on one or more probabilistic triggers as described herein. Some examples of the positioning or sensing techniques may be performed in one or more wireless Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO113communications systems 2300, such as LTE and NR, where NR may support sidelink communications.

[0348] FIG. 24 shows examples of sensing modes 2400 that support authorization communications for positioning or sensing procedures in accordance with one or more aspects of the present disclosure. Various sensing modes are illustrated in the context of one or more devices (e.g., TRPs and UEs). While TRPs are illustrated in FIG. 24, a TRP may instead be abase station (e.g., gNB) in some examples. The objects illustrated in FIG. 24 may be devices (e.g., UEs, AGVs, or vehicles, among other examples) or passive objects (e.g., roads, signs, barriers, or rocks, among other examples).

[0349] One or more sensing operations may be performed in accordance with one or more of the techniques described herein. Sensing operations may include monostatic sensing (e.g., radar-like sensing, where a sensing transmitter and a sensing receiver may be co-located in the same entity) or bistatic sensing (e.g., where a sensing receiver and sensing transmitter are located in different entities). Multi-static sensing may be performed in some examples, where multiple sensing transmitters or receivers may be utilized.

[0350] In some approaches, one or more reflections of a sensing signal sent from a sensing transmitter may be received by a sensing receiver and processed to determine one or more characteristics of the sensed object or an environment (e.g., location). In sensing operations, one or more sensing signal reflections may be received. The sensing signal reflections may be processed locally (e.g., in a device that received the sensing signal reflections) or may be communicated to another device for processing. For instance, a device may execute one or more AI / ML models to determine a position of the object based on the sensing signal reflections.

[0351] An example of monostatic TRP sensing 2405 is given in FIG. 24. For example, a TRP (e.g., gNB) may transmit a signal and receive a signal reflection from the object.

[0352] An example of monostatic UE sensing 2410 is given in FIG. 24. For example, a UE may transmit a signal and receive a signal reflection from the object.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO114

[0353] An example of bistatic TRP-to-TRP sensing 2415 is given in FIG. 24. For example, a first TRP (e.g., a first gNB) may transmit a signal, and a second TRP may receive a signal reflection from the object.

[0354] An example of bistatic TRP-to-UE sensing 2420 is given in FIG. 24. For example, a TRP (e.g., a gNB) may transmit a signal, and a UE may receive a signal reflection from the object.

[0355] An example of bistatic UE-to-TRP sensing 2425 is given in FIG. 24. For example, a UE may transmit a signal, and a TRP may receive a signal reflection from the object.

[0356] An example of bistatic UE-to-UE sensing 2430 is given in FIG. 24. For example, a first UE may transmit a signal, and a second UE may receive a signal reflection from the object.

[0357] In some aspects, one or more of the AI / ML-based positioning or sensing procedures or communications (e.g., capability information, request information, indications, or meaning information, among other examples) described herein may be utilized for one or more sensing use cases. For instance, sensing may be performed to determine a position or motion of an object (e g., a wireless device or other object). Examples of sensing use cases may include one or more of transportation, unmanned aerial vehicles (UAVs), smart cities, smart homes, smart factories, or health monitoring. For instance, a transportation use case may include intrusion detection on a highway, sensing assisted automotive maneuvering or navigation, smart parking, or other assistance, among other examples. A UAV use case may include UAV flight trajectory' tracing or sensing for UAV intrusion detection, among other examples. A smart city use case may include rainfall monitoring, tourist spot traffic management, flooding awareness, weather forecasting, or public safety search and rescue, among other examples. A smart home use case may include intruder detection in a smart home, gesture recognition, or extended reality' (XR) streaming, among other examples. A smart factory use case may include automated guided vehicle (AGV) detection and tracking in factories or inventory tracking, among other examples. A health monitoring use case may include monitoring vital signs and health related measures, sleep monitoring, or health monitoring, among other examples. Examples of sensing modes that may beAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO115employed in some examples of the techniques may be implemented in the wireless communications system described with reference to FIG. 4.

[0358] In some examples, one or more of the AI / ML models described herein may correspond to one or more sensing key performance indicators (KPIs) (with equivalent A-AI / ML sensing or D- AI / ML sensing). Some examples of sensing KPIs may include an accuracy of positioning (e.g., horizontal or vertical), an accuracy of range or crossrange of target, an accuracy of AO A of a target (e.g., azimuth or elevation), an accuracy of velocity (e.g., horizontal or vertical), a sensing range or cross-range resolutions, a sensing velocity resolution, a sensing angle resolution, a sensing latency, a sensing refreshing rate, a receiver operating characteristics (ROC) (e.g., misdetection or false alarm probabilities), a confidence interval or level of sensing, or target discrimination.

[0359] Some examples of the techniques described herein may utilize one or more terms relating to sensing. Sensing data may include data derived from one or more radio signals impacted (e.g., reflected, refracted, diffracted) by an object or environment of interest for sensing purposes, and optionally processed. 5G Wireless sensing (5GS) may be a feature providing one or more capabilities to obtain information about characteristics of the environment or objects within the environment (e.g., shape, size, orientation, speed, location, distances or relative motion between objects, among other examples) using radio frequency signals. Non-3GPP sensing data may be data provided by non-3GPP sensors (e.g., video, LIDAR, sonar) about an object or environment of interest for sensing purposes. Sensing assistance information may be information that is provided to a wireless system from a third-party and may be used to support the derivation of a sensing result. Examples of sensing assistance information may include map information, area information, a UE ID attached to or in the proximity of the sensing target, UE position information, or UE velocity information, among other examples.

[0360] Sensing contextual information may be information that is exposed with the sensing results by a wireless system to a third-party which provides context to the conditions under which the sensing results were derived. Examples may include map information, area information, time of capture, UE location, or an identifier. This contextual information may be demanded in scenarios where the sensing result is to be combined with data from other sources outside the 5GS. A sensing group may be a set Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO116of sensing transmiters and sensing receivers whose location is known and whose sensing data can be collected synchronously. A sensing receiver may be an entity that receives a sensing signal which a sensing service may use in operation. A sensing receiver may be part of a RAN node or a UE. A sensing receiver may be located in the same or different entity' as the sensing transmiter. A sensing result may be processed sensing data requested by a service consumer. Sensing signals may be transmissions on a radio interface that can be used for sensing purposes. Some approaches may refer to NR radio frequency signals which, in some cases.

[0361] A sensing transmitter may be an entity that sends out a sensing signal which the sensing service will use in its operation. A sensing transmiter may be part of a RAN node or a UE. A sensing transmiter may be located in the same or different entity as the sensing receiver. A target sensing service area may be a cartesian location area to be sensed by deriving characteristics of the environment or objects within the environment with a sensing service quality from the impacted (e.g., reflected, refracted, diffracted) radio signals. This may include indoor or outdoor environments.

[0362] RF sensing may extend positioning capabilities to one or more applications. Factors affecting sensing performance may include RCS, mobility, or cluter / scatering paterns. One or more channel modeling aspects may be utilized to support object detection or tracking. A modeling framework may be capable of detecting or tracking one or more objects and to enable them to be distinguished from unintended objects. Some examples of objects may include UAVs, humans (indoors or outdoors), automotive vehicles (at least outdoors), automated guided vehicles (e g., in indoor factories), or objects creating hazards on roads / railways (e.g.. with a minimum size dependent on frequency). In some examples, one or more frequencies from 0.5 to 52.6 GHz may be utilized, with scalability to 100 GHz.

[0363] For one or more use cases, sensing modes and frequencies, deployment scenarios may be identified corresponding to one or more use cases. Channel modeling may be utilized for sensing. One or more measurements may be utilized for modeling of sensing targets or a background environment, including, for example, radar crosssection (RCS), mobility, cluter / scatering paterns, or spatial reliability.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO117

[0364] In some examples, a sensing data signal processing flow may be performed from Analog-to-Digital Converter (ADC) samples to progressively higher-level data representations. From low levels to high levels, the data types may include raw data, a range-angle-Doppler (RAD) tensor, a point cloud, or grid map. Learning-based frameworks may be utilized, which may support the encoding and decoding of different representation types, and additional quantization can be adopted to reduced data size. For integrated sensing and communication, for instance, one or more types of data representations may be utilized, which may include data quantization, range fast Fourier transform (FFT), Doppler FFT, angle FFT, RAD tensor, point cloud, voxel grids, neural network (NN)-based representations, or parametric objects. In some examples, an ADC signal may be utilized to obtain one or more of the types of representations. In some aspects, a deep learning framework or quantization may be applied for one or more (e.g., all) types of representations. One or more types of representations may be provided to an SnMF for one or more sensing operations.

[0365] One or more of the data representations are described as follows. Data quantization: at a relatively low (e.g., lowest) level, sampling and quantization of the sensing signal may be initial operations. To reduce the volume of data that needs to be processed, various techniques may be utilized. Some approaches, such as compressed sensing, may exploit the sparsity of the signal to acquire the signal at a lower sampling rate. Other approaches may use relatively low-bit quantization to reduce complexity and power consumption at the TRP. In particular, the power consumption of ADCs in hybrid architectures may grow exponentially to the quantity of quantization levels, thus elevating the significance of ADC quantization. In some cases, sampling may be performed with one bit per sample, significantly reducing the data volume to be transmitted by the TRP. Data quantization may be combined with other representations, such as RAD tensors or point clouds, among other examples. Data quantization may be used as the format of data to be exchanged in a case of signal-level fusion where the sensing data is sent directly to a fusion center without performing any further local processing.

[0366] RAD tensors: range-angle and range-Doppler maps may be data representations in radar signal processing. The maps may provide a structured way to visualize or analyze spatial or velocity information of detected targets. In the context ofAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO118integrated sensing and communication, the maps may be useful fortasks like target detection, localization, and tracking.

[0367] Point clouds: point clouds may be versatile data ...

Claims

Qualcomm Ref. No. 2408019 WO130CLAIMSWhat is claimed is:

1. A wireless device, comprising:one or more transceivers;one or more memory; andone or more processors electronically coupled to the one or more memory and the one or more transceivers, the one or more processors configured to:obtain a request to collect information that is based at least in part on a measurement for a positioning or sensing procedure;output, to a network entity, a request authorization query associated with the request, wherein the request authorization query indicates one or more attributes of the request, the one or more attributes comprising an identifier of a source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof; andobtain, from the network entity, an indication of whether the request is authorized.

2. The wireless device of claim 1. wherein the indication of whether the request is authorized indicates that the request is not authorized and indicates one or more permitted responses to the request.

3. The wireless device of claim 1, wherein the one or more processors are further configured to:obtain a second request to collect second information that is based at least in part on a second measurement for a second positioning or sensing procedure, wherein the second request comprises an authorization message; andperform a validation procedure based at least in part on the authorization message.

4. The wireless device of claim 1, wherein the one or more processors are further configured to:obtain, from the network entity, configuration information indicating one or more candidate attributes for a second positioning or sensing procedure, the one orAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO131more candidate attributes comprising a candidate area, a candidate device that is authorized to request a start or end of the second positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

5. The wireless device of claim 4, wherein the one or more processors are further configured to:output, to the network entity, an indication of a selection of the one or more candidate attributes for the second positioning or sensing procedure; and obtain, from the network entity7, an acceptance or a denial of the selection of the one or more candidate attributes.

6. The wireless device of claim 5, wherein the one or more processors are further configured to:obtain, from the network entity, an indication of a second selection of the one or more candidate attributes, wherein the indication of the second selection is based at least in part on the denial of the selection of the one or more candidate attributes.

7. The wireless device of claim 4, wherein the one or more processors are further configured to:output, to the network entity, an indication of a rejection of at least one of the one or more candidate attributes for the second positioning or sensing procedure; andoutput, to the network entity, an indication of one or more second candidate attributes for the second positioning or sensing procedure.

8. The wireless device of claim 1, wherein the one or more processors are further configured to:communicate information indicating that a second positioning or sensing procedure is unauthorized, or indicating one or more unauthorized attributes for a second positioning or sensing procedure, the one or more unauthorized attributes comprising an unauthorized area, an unauthorized device for the positioning or sensing procedure, an unauthorized type of measurement information, an unauthorizedAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO132information granularity, an unauthorized duration, an unauthorized purpose, or any combination thereof.

9. A network node, comprising:one or more transceivers;one or more memory; andone or more processors electronically coupled to the one or more memory and the one or more transceivers, the one or more processors configured to:output, to a network entity, an authorization request for collection of information related to a measurement at a wireless device for a positioning or sensing procedure, wherein the authorization request indicates one or more parameters, the one or more parameters comprising an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a ty pe of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof; andobtain, from the network entity, an indication of whether the authorization request is accepted.

10. The network node of claim 9, wherein the indication of whether the authorization request is accepted indicates that the authorization request is not accepted and indicates one or more permitted parameters.

11. The network node of claim 9, wherein the indication of whether the authorization request is accepted indicates a prioritization or a different positioning or sensing procedure.

12. The network node of claim 9, wherein the one or more processors are further configured to:output, to the wireless device, a request to collect the information, wherein the request comprises an authorization message from the network entity.

13. The network node of claim 9. wherein the one or more processors are further configured to:Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO133obtain, from the network entity, configuration information indicating one or more candidate parameters for the positioning or sensing procedure, the one or more candidate parameters comprising a candidate area, a candidate device that is authorized to request a start or end of the positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity' event, or any combination thereof.

14. The network node of claim 9. wherein a session of the positioning or sensing procedure begins or expires by an expiration of a timer from a time of the authorization request.

15. A network entity, comprising:one or more transceivers;one or more memory; andone or more processors electronically coupled to the one or more memory' and the one or more transceivers, the one or more processors configured to:obtain an authorization inquiry related to collection of information that is based at least in part on a measurement at a wireless device for a positioning or sensing procedure;determine whether to validate the authorization inquiry' based at least in part on one or more attributes or parameters of the authorization inquiry’; andoutput an indication of whether the authorization inquiry' is validated.

16. The network entity of claim 15, wherein:the authorization inquiry is a request authorization query associated with a request from a source to the wireless device to collect the information, the one or more attributes of the request comprising an identifier of the source of the request, a period of the request, a reporting target for the information, a type of the information, an area corresponding to the request, a condition for the request, or any combination thereof, andthe determination whether to validate the authorization inquiry' is based at least in part on a satisfaction of a validation criterion by the one or more attributes.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO13417. The network entity of claim 16, wherein the indication of whether the authorization inquiry7is validated indicates that the request is not authorized and indicates one or more permitted responses to the request.

18. The network entity of claim 15, wherein, to output the indication of whether the authorization in uiry is validated, the one or more processors are configured to:output, to a network node, an authorization message for inclusion in a request from the network node to the wireless device to collect the information that is based at least in part on the measurement at the wireless device for the positioning or sensing procedure.

19. The network entity of claim 15, wherein the one or more processors are further configured to:output, to the wireless device, configuration information indicating one or more candidate attributes for a second positioning or sensing procedure, the one or more candidate attributes comprising a candidate area, a candidate device that is authorized to request a start or end of the second positioning or sensing procedure, a candidate t pe of measurement information, a candidate information granularity, a candidate validity area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

20. The network entity of claim 19, wherein the one or more processors are further configured to:obtain, from the wireless device, an indication of a selection of the one or more candidate attributes for the second positioning or sensing procedure; and output, to the wireless device, an acceptance or a denial of the selection of the one or more candidate attributes.

21. The network entity of claim 20, wherein the one or more processors are further configured to:output, to the wireless device, an indication of a second selection of the one or more candidate attributes, wherein the denial of the selection of the one or more candidate attributes is output.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO13522. The network entity of claim 19, wherein the one or more processors are further configured to:obtain, from the wireless device, an indication of a rejection of at least one of the one or more candidate attributes for the second positioning or sensing procedure; andobtain, from the wireless device, an indication of one or more second candidate attributes for the second positioning or sensing procedure.

23. The network entity of claim 15, wherein the one or more processors are further configured to:communicate information indicating that a second positioning or sensing procedure is unauthorized, or indicating one or more unauthorized attributes for a second positioning or sensing procedure, the one or more unauthorized attributes comprising an unauthorized area, an unauthorized device for the positioning or sensing procedure, an unauthorized type of measurement information, an unauthorized information granularity, an unauthorized duration, an unauthorized purpose, or any combination thereof.

24. The network entity of claim 15, wherein the authorization inquiry is an authorization request from a network node for obtaining the information that is based at least in part on a measurement at the wireless device for the positioning or sensing procedure, wherein the authorization request indicates one or more parameters, the one or more parameters comprising an identifier of the wireless device from which the information is to be requested, a period of measurement for the positioning or sensing procedure, a type of the information, a type of the information to be reported to the network node, an area corresponding to the authorization request, or any combination thereof.

25. The network entity of claim 15, wherein the indication of whether the authorization inquiry is validated indicates that the authorization inquiry is not validated and indicates one or more permitted parameters.Attorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO13626. The network entity of claim 15, wherein the indication of whether the authorization inquiry7is validated indicates a prioritization or a different positioning or sensing procedure.

27. The network entity of claim 15, wherein the one or more processors are further configured to:output, to a network node, configuration information indicating one or more candidate parameters for the positioning or sensing procedure, the one or more candidate parameters comprising a candidate area, a candidate device that is authorized to request a start or end of the positioning or sensing procedure, a candidate type of measurement information, a candidate information granularity7, a candidate validity7area, a candidate validity timer, a candidate invalidity event, or any combination thereof.

28. The network entity of claim 15, wherein the one or more processors are further configured to:initiate a timer based at least in part on a time of the authorization inquiry;obtain, from a location server, identification information of the wireless device;output, to the wireless device based on the identification information, an inquiry of whether the wireless device accepts the positioning or sensing procedure; and obtain, from the wireless device, an indication of whether the wireless device accepts the positioning or sensing procedure, wherein a session of the positioning or sensing procedure begins or expires by an expiration of the timer from the time of the authorization inquiry.

29. A method for wireless communications at a wireless device, comprising:obtaining a request to collect information that is based at least in part on a measurement for a positioning or sensing procedure;outputting, to a network entity, a request authorization query7associated with the request, wherein the request authorization query indicates one or more attributes of the request, the one or more attributes comprising an identifier of a source of the request, a period of the request, a reporting target for the information, a type ofAttorney Docket No. PB0022GR.WO (114958.TBD)Qualcomm Ref. No. 2408019 WO137the information, an area corresponding to the request, a condition for the request, or any combination thereof; andobtaining, from the network entity, an indication of whether the request is authorized.

30. The method of claim 29, wherein the indication of whether the request is authorized indicates that the request is not authorized and indicates one or more permitted responses to the request.Attorney Docket No. PB0022GR.WO (114958.TBD)

Images