Sensing service support in a wireless communication system

Abstract

Various aspects of the present disclosure relate to a first network entity for wireless communication. The first network entity may be configured to, capable of, or operable to receive, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and transmit, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

Description

SENSING SERVICE SUPPORT IN A WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including sensing service support.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise knowns as network equipment (NE) supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a Docket No. SMM920250174-GR-NPcondition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and transmit, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

[0005] A method performed or performable by the first network entity is described herein. The method may comprise: receive, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and transmit, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

[0006] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receiving, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and transmitting, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

[0007] A second network entity for wireless communication is described. The second network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the second network entity may include at least Docket No. SMM920250174-GR-NPone memory, and at least one processor coupled with the at least one memory and configured to cause the second network entity to: transmit, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and receive, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

[0008] A method performed or performable by the second network entity is described herein. The method may comprise: transmitting, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and receiving, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

[0009] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and receive, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0011] Figure 2 illustrates an example of a process flow for sensing service support in accordance with aspects of the present disclosure.

[0012] Figure 3 illustrates an example of a UE 300 in accordance with aspects of the present disclosure.Docket No. SMM920250174-GR-NP

[0013] Figure 4 illustrates an example of a processor 400 in accordance with aspects of the present disclosure.

[0014] Figure 5 illustrates an example of a NE 500 in accordance with aspects of the present disclosure.

[0015] Figure 6 illustrates a flowchart of a method 600 performed by a NE in accordance with aspects of the present disclosure.

[0016] Figure 7 illustrates a flowchart of a method 700 performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0017] A wireless communication system, including one or more UE and NE may be configured to provide Integrated Sensing and Communication (ISAC). ISAC relates to the integration of radio sensing capabilities directly into wireless communication systems (e.g., wireless communication networks) such as 5G and 6G networks. ISAC enables the wireless communication system network to transmit communication signals and sense the environment, allowing it to detect objects, measure distances, track motion, and determine spatial contexts e.g., using the same radio resources used for data transmission. ISAC may be used to support applications like autonomous driving, smart factories, and environmental monitoring, aiming for efficient spectrum use and tighter integration between communication and Sensing Functions (SFs).

[0018] In some examples described herein, ISAC is performed when a sensing service consumer (e.g., an internal or external Application Function (AF)) requests a sensing service. The sensing service may be supported by a sensing entity such as a New Radio (NR) Node B (gNB). However, the capability or status of the sensing entity may affect its ability to support the sensing service. Examples described herein tend to provide improved support to the sensing service.

[0019] Aspects of the present disclosure are described in the context of a wireless communications system.Docket No. SMM920250174-GR-NP

[0020] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0021] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0022] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In someDocket No. SMM920250174-GR-NPimplementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0023] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0024] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0025] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0026] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an Docket No. SMM920250174-GR-NPevolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a 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)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0027] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0028] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0029] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A firstDocket No. SMM920250174-GR-NPnumerology (e.g., / z=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0030] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0031] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / t=0, / t=l, =2, jtz=3, =4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extendedDocket No. SMM920250174-GR-NPcyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0032] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0033] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / / =1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / / =2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / z=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.

[0034] In some examples described herein, the NEs 102 may be configured to support a sensing service (e.g., ISAC) for a sensing service consumer (e.g., an AF). One of the NEs 102 may comprise a SF. One of the NEs 102 may include a sensing entity. The SF may receive, from a sensing entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter. The SF may transmit, to the sensing entity, a sensing response message indicating whether the SF is able to support the sensing service according to the sensing parameter.Docket No. SMM920250174-GR-NP

[0035] ISAC architecture and system level enhancements may comprise two levels of security authorization. One on the Network Exposure Function (NEF) (e.g., in the exposure) where the network authorizes an AF to access a sensing service and another in the SF or a Gateway Network Function (NF) related to sensing services related to specific sensing service parameters.

[0036] The sensing service authorization may comprise an authorisation of the AF for sensing service request is performed by the NEF, if the AF is outside the trusted domain. The sensing service authorization further includes an authorisation of the AF's sensing service request performed by the sensing authorization functionality. The sensing authorization functionality may refer to SF, Sensing Control Function or Sensing Gateway.

[0037] The sensing authorization functionality may determine whether the sensing service request from the AF is authorised, e.g., considering the example of sensing authorisation information described in Table 1 below.Table 1: Sensing authorization information for sensing serviceDocket No. SMM920250174-GR-NP

[0038] Uncrewed Air Vehicle (UAV) sensing target uses cases may serve either the purpose of public safety, or as requested by the management entity (e.g., UAV management department, Uncrewed Aerial System (UAS) Service Supplier (USS) or UAS Traffic Management (UTM)), without the necessity to identify the object. Some examples described herein generally relate to the issue of security of sensing service authorization and sensing result exposure. The 5G system may be able to authorize a sensing service request from a sensing service consumer. A similar security requirement may relate to security protection for sensing service operations. The 5G system may be able to support authorization for sensing service operations. In some examples described herein, there is no requirement for authorisation for the gNB as the Sensing Entity, as the gNB is deployed by operator.

[0039] The gNB may serve two roles for a sensing service. The first role may be related to transmitting a wireless signal for sensing an object. The second role may be related to collecting the corresponding reflections. When transmitting a wireless signal for sensing the object, the gNB may determine whether to authorize a sensing request to either reuse an ongoing transmission signal or provide a new wireless signal (e.g., new signal, new transmission signal, new radio signal) if that is possible.

[0040] The sensing request may comprise one or more sensing parameters. The requested one or more sensing parameters may be out of range of the gNB e.g., due to technical limitations of the gNB. The one or more sensing parameters may be within different vendor specific ranges. The technical limitations of the gNB may relate to at least one of: a specific deployment of the gNB, a current load situation of the gNB, or the requested Sensing Quality of Service (SQoS). If the sensing request is supported using a new transmission signal, to the gNB may determine (e.g., check) whether the capabilities of the new transmission signal satisfy the requested SQoS (e.g., in terms of resolution).

[0041] The gNB may receive a reflected signal. The reflected signal may be the transmitted wireless signal reflected (e.g., scattered) off an object). The gNB may perform preprocessing of the reflected signal. The gNB may provide an intermediate result to the SF. This tends to reduce the resources of the network for collecting sensing data. Such processing may need resources. A second authorization may be performed by the gNB toDocket No. SMM920250174-GR-NPdetermine whether such resources are available e.g., in nearby computing facilities. The gNB may perform the second authorization by determining (e.g., checking) the available resources in the gNB and whether the sensing request can be performed.

[0042] ISAC may be based on sensing assistance information and the sensing contextual information the presence of a specific object. The specific object may match a certain criterion e.g., an object in a certain area and time. ISAC may provide detection or tracking (e.g., three dimensionally, in 3D), using the radio signals of the sensing entity (e.g., gNB). Previously, there was no check of a sensing request by the sensing entity e.g., to determine whether the sensing request (e.g., involving a sensing measurement) can be performed by the gNB.

[0043] Figure 2 illustrates an example of a process flow 200 in accordance with aspects of the present disclosure. The process flow 200 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 200 may include a Sensing Service Consumer 210, an NEF 220, a SF 230 and a Sensing Entity 240, which may be one or more examples of devices described herein with reference to Figure 1.

[0044] The process flow 200 may be referred to as a procedure, including one or more operations performed by one or more of the Sensing Service Consumer 210, NEF 220, SF 230 and Sensing Entity 240. In the example of Figure 2, the process flow 200 may include sensing service support.

[0045] In the following description of the process flow 200, the operations or signalling performed between one or more of the Sensing Service Consumer 210, NEF 220, SF 230 and Sensing Entity 240 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the Sensing Service Consumer 210, NEF 220, SF 230 and Sensing Entity 240 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 200. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.Docket No. SMM920250174-GR-NP

[0046] The Sensing Service Consumer 210 may be an entity that consumes the Sensing Result (e.g., sensing measurements). The Sensing Service Consumer 210 may also request the Sensing Result. The Sensing Service Consumer 210 may be an internal or external AF. The Sensing Entity 240 may be a Sensing Transmitter and / or to a Sensing Receiver e.g., a gNB. The SF 230 may be a logical function to support a Sensing Service. The SF 230 may comprise at least one of: a Sensing Control Function (SCF), a Sensing Processing Function (SPF) and a Sensing Gateway (SG). Sensing data (e.g., 3GPP sensing data) may comprise data derived from 3GPP radio signals impacted (e.g., reflected, refracted, diffracted, scattered) by an object or environment of interest for sensing purposes, and optionally processed within the 5G system. A sensing result may comprise processed 3GPP sensing data requested by the Sensing Service Consumer 210.

[0047] Some examples described herein relate to Sensing Request Authorization in the Sensing Entity 240. The Sensing Entity 240 may authorize the Sensing Request from the SF to determine whether the measurements can be performed or not. If the measurements can be performed, the Sensing Request is authorized and the Sensing Entity 240 performs the sensing measurements and reports them back (e.g., sends, transmits them) to the SF 230. If the sensing measurements cannot be performed, then the Sensing Request is not authorized and the Sensing Entity 240 reports (e.g., sends, transmits) an error cause value back to the SF 230, the response may indicate a parameter of the Sensing Request that was not applicable to the Sensing Entity 240. The Sensing Service Consumer 210 and the NEF 220 may have a security association.

[0048] Process flow 200 starts at step 271. The Sensing Service Consumer 210 sends (e.g., transmits, outputs) a Sensing Service Request to the NEF 220 with at least one of: a sensing service type (e.g., object detection, object tracking, environment sensing), a sensing service requirement (e.g. accuracy, latency, resolution) and time information when the sensing service is requirement (e.g., a time for the sensing measurement, a time for sensing report). The Sensing Service Request may include a target sensing service area or a target UE.

[0049] In step 272, the NEF 220 selects (e.g., determines, identifies, discovers) the SF 230 for invoking (e.g., performing) the Sensing Service and to authorize the SensingDocket No. SMM920250174-GR-NPService Request. The NEF 220 sends (e.g., transmits, outputs) aNsf_Sensing Authorization Request including AF ID and the sensing information received from the Sensing Service Consumer 210 to the SF 230.

[0050] In step 273, the SF 230 authorizes the Sensing Service Request from the Sensing Service Consumer 210 and performs Sensing Entity 240 selection e.g., based on the information in the Sensing Request such as target sensing area.

[0051] In step 274, the SF 230 sends (e.g., transmits, outputs) a Sensing Request (e.g., a sensing request message) with the information to the Sensing Entity 240, e.g., a gNB.

[0052] In step 275, the Sensing Entity 240 authorizes the Sensing Request and either performs the sensing according to the instructions in the sensing request from the SF 230 or rejects the Sensing Request with an authorization failure.

[0053] The following cause values / error codes may cause an authorization failure: parameter (e.g., sensing parameter) not supported (e.g., due to technical limitations or specific deployments of the Sensing Entity 240), the Sensing Entity 240 may indicate which parameter(s) is not supported; parameter out of range (e.g., the parameter range may not be supported due to implementation, technical limitations or due to a specific deployment of the Sensing Entity), the Sensing Entity 240 may indicate which parameter(s) are out of range and what are the parameter ranges; Sensing Entity 240 (e.g., Temporary) Overload (e.g., the Sensing Entity 240 may be under a heavy load condition, serving many UEs, or cannot (e.g., temporarily) carry out a Sensing Request (load conditions may refer to communication load or computing depending on whether the gNB is a transmitter or receiver); SQoS not supported or (e.g., temporarily) not possible (e.g., the requested SQoS may not be supported by the Sensing Entity 240, the required bandwidth may be temporarily unavailable (e.g., due to the current load situation)) (the Sensing Entity 240 may indicate the possible SQoS, the QoS may include parameters such as resolution, accuracy, frequency of reporting); unknown Error (e.g., an internal error in the Sensing Entity such that the Sensing Request cannot be performed).

[0054] In step 276, the Sensing Entity 240 either sends (e.g., transmits, outputs) (e.g., via a sensing response, a sensing response message) the sensing measurements to the SFDocket No. SMM920250174-GR-NP230 or includes the authorization failure result including the cause value / error code in the sensing response. The cause value / error code may include additional information about the specific cause value / error code.

[0055] In step 277, if the authorization is successful and the Sensing Entity 240 returned the sensing measurements, the SF 230 performs the relevant processing according to normal procedures.

[0056] If the authorization is not successful, the SF 230 performs at least one of: parameter not supported: the SF 230 may update the Sensing Entity 240 Capabilities in its database for a future selection of the Sensing Entity 240. The SF 230 may select another suitable Sensing Entity 240 and reattempt the Sensing Request there; parameter out of range: the SF 230 may update the Sensing Entity Capabilities in its database for a future selection of the Sensing Entity 240. The SF 230 may select another suitable Sensing Entity 240 and reattempt the Sensing Request; Sensing Entity (Temporary) Overload: if the Sensing Request is not a real-time request, the SF 230 may resend the Sensing Request after a pre-configured time, otherwise if it is a real-time request, then the SF 230 may select another suitable Sensing Entity 240 and reattempt the Sensing Request; SQoS not supported or (temporarily) not possible: this may occur if the SQoS requires a higher bandwidth for performing the sensing measurements as the Sensing Entity 240 can temporarily provide; if the Sensing Request is not a real-time request, the SF 230 may resend the Sensing Request after a pre-configured time, otherwise if it is a real-time request, then the SF 230 may select another suitable Sensing Entity 240 and reattempt the Sensing Request there; Unknown Error: if the cause value / error code keeps occurring also for other Sensing Requests, the SF 230 may update the Sensing Entity Capabilities in its database and remove the Sensing Entity 240 for a future selection; and the SF 230 may select another suitable Sensing Entity 240 and reattempt the Sensing Request.

[0057] In step 278, the SF 230 responds to the NEF 220 with the sensing information result from the sensing procedure or with the authorization failure from the Sensing Entity 240.

[0058] In step 279, the NEF 220 forwards the sensing information result from the SF 230 to the AF.Docket No. SMM920250174-GR-NP

[0059] Figure 3 illustrates an example of a UE 300 in accordance with aspects of the present disclosure. The UE 300 may include a processor 302, a memory 304, a controller 306, and a transceiver 308. The processor 302, the memory 304, the controller 306, or the transceiver 308, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0060] The processor 302, the memory 304, the controller 306, or the transceiver 308, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0061] The processor 302 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 302 may be configured to operate the memory 304. In some other implementations, the memory 304 may be integrated into the processor 302. The processor 302 may be configured to execute computer-readable instructions stored in the memory 304 to cause the UE 300 to perform various functions of the present disclosure.

[0062] The memory 304 may include volatile or non-volatile memory. The memory 304 may store computer-readable, computer-executable code including instructions when executed by the processor 302 cause the UE 300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 304 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0063] In some implementations, the processor 302 and the memory 304 coupled with the processor 302 may be configured to cause the UE 300 to perform one or more of the Docket No. SMM920250174-GR-NPfunctions described herein (e.g., executing, by the processor 302, instructions stored in the memory 304). For example, the processor 302 may support wireless communication at the UE 300 in accordance with examples as disclosed herein. The UE 300 may be configured to support the arrangements described herein.

[0064] The controller 306 may manage input and output signals for the UE 300. The controller 306 may also manage peripherals not integrated into the UE 300. In some implementations, the controller 306 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 306 may be implemented as part of the processor 302.

[0065] In some implementations, the UE 300 may include at least one transceiver 308. In some other implementations, the UE 300 may have more than one transceiver 308. The transceiver 308 may represent a wireless transceiver. The transceiver 308 may include one or more receiver chains 310, one or more transmitter chains 312, or a combination thereof.

[0066] A receiver chain 310 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 310 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 310 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 310 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 310 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0067] A transmitter chain 312 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 312 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 312 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable Docket No. SMM920250174-GR-NPfor transmission over the wireless medium. The transmitter chain 312 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0068] Figure 4 illustrates an example of a processor 400 in accordance with aspects of the present disclosure. The processor 400 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 400 may include a controller 402 configured to perform various operations in accordance with examples as described herein. The processor 400 may optionally include at least one memory 404, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 400 may optionally include one or more arithmetic-logic units (ALUs) 406. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0069] The processor 400 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 400) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0070] The controller 402 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 400 to cause the processor 400 to support various operations in accordance with examples as described herein. For example, the controller 402 may operate as a control unit of the processor 400, generating control signals that manage the operation of various components of the processor 400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.Docket No. SMM920250174-GR-NP

[0071] The controller 402 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 404 and determine subsequent instruction(s) to be executed to cause the processor 400 to support various operations in accordance with examples as described herein. The controller 402 may be configured to track memory address of instructions associated with the memory 404. The controller 402 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 402 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 400 to cause the processor 400 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 402 may be configured to manage flow of data within the processor 400. The controller 402 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 400.

[0072] The memory 404 may include one or more caches (e.g., memory local to or included in the processor 400 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 404 may reside within or on a processor chipset (e.g., local to the processor 400). In some other implementations, the memory 404 may reside external to the processor chipset (e.g., remote to the processor 400).

[0073] The memory 404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 400, cause the processor 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 402 and / or the processor 400 may be configured to execute computer-readable instructions stored in the memory 404 to cause the processor 400 to perform various functions. For example, the processor 400 and / or the controller 402 may be coupled with or to the memory 404, the processor 400, the controller 402, and the memory 404 may be configured to perform various functions described herein. In some examples, the processor 400 may include multiple processors and the memory 404 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multipleDocket No. SMM920250174-GR-NPmemories, which may, individually or collectively, be configured to perform various functions herein.

[0074] The one or more ALUs 406 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 406 may reside within or on a processor chipset (e.g., the processor 400). In some other implementations, the one or more ALUs 406 may reside external to the processor chipset (e.g., the processor 400). One or more ALUs 406 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 406 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 406 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 406 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 406 to handle conditional operations, comparisons, and bitwise operations.

[0075] The processor 400 may support wireless communication in accordance with examples as disclosed herein. The processor 400 may be configured to support a means for receiving, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and transmitting, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter. The processor 400 may be configured to or operable to support a means for transmitting, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and receiving, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

[0076] Figure 5 illustrates an example of a NE 500 in accordance with aspects of the present disclosure. The NE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or theDocket No. SMM920250174-GR-NPtransceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0077] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0078] The processor 502 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the NE 500 to perform various functions of the present disclosure.

[0079] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the NE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 504 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0080] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the NE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the NE 500 in accordance with examples as disclosed herein. The NE 500 may be configured Docket No. SMM920250174-GR-NPto support a means for receiving, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and transmitting, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter. Alternatively, the NE 500 may be configured to or operable to support a means for transmitting, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and receiving, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

[0081] The controller 506 may manage input and output signals for the NE 500. The controller 506 may also manage peripherals not integrated into the NE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0082] In some implementations, the NE 500 may include at least one transceiver 508. In some other implementations, the NE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

[0083] A receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 510 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 510 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0084] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 may include at least one Docket No. SMM920250174-GR-NPmodulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0085] Figure 6 illustrates a flowchart of a method 600 in accordance with aspects of the present disclosure. The operations of the method 600 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0086] At 602, the method 600 may include receiving, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter. The operations of 602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 602 may be performed by a NE as described with reference to Figure 5.

[0087] At 604, the method 600 may include transmitting, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter. The operations of 604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 604 may be performed by a NE as described with reference to Figure 5.

[0088] It should be noted that the method 600 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0089] Figure 7 illustrates a flowchart of a method 700 in accordance with aspects of the present disclosure. The operations of the method 700 may be implemented by a NE asDocket No. SMM920250174-GR-NPdescribed herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0090] At 702, the method 700 may include transmitting, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter. The operations of 702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 702 may be performed by a NE as described with reference to Figure 5.

[0091] At 704, the method 700 may include receiving, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter. The operations of 704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 704 may be performed by a NE as described with reference to Figure 5.

[0092] It should be noted that the method 700 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0093] There is further provided herein a first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and transmit, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter. Such a first network entity tends to provide improved support to the sensing service.

[0094] The first network entity may be part of a wireless communication network. The wireless communication network may comprise a wireless communication system. The wireless communication network may comprise a 5G network. The wireless communication network may comprise a 6G network. The first network entity mayDocket No. SMM920250174-GR-NPcomprise a sensing entity. The first network entity may comprise a base station. The first network entity may comprise a gNB. The second network entity may be part of the wireless communication network. The second network entity may comprise a sensing function.

[0095] The sensing request message may comprise a sensing request. The sensing response message may comprise a sensing response. The sensing service consumer may comprise an AF. The sensing service may comprise sensing of a specific object by the first network entity. Sensing of the specific object may comprise determining at least one of a location, an altitude, a height, an angle, an elevation, an azimuth of the specific object. Sensing of the specific object may comprise detecting the specific object. Sensing of the specific object may comprise tracking the specific object. Sensing of the specific object by the first network entity may comprise transmitting a radio signal from the first network entity and receiving a reflected radio signal.

[0096] The sensing response message may indicate that the sensing service is authorized. If the sensing service is authorized, the first network entity may perform (e.g., support) the sensing service. The sensing response message may indicate that the sensing service is not authorized. If the sensing service is not authorized, the first network entity may not perform (e.g., support) the sensing service. Authorization of the sensing service may be based on whether the first network entity is able to support the sensing parameter.

[0097] The at least one processor may be further configured to cause the first network entity to: determine that the first network entity is not able to support the sensing service according to the sensing parameter. To determine that the first network entity is not able to support the sensing service according to the sensing parameter, the at least one processor may be configured to cause the first network entity to: determine a cause value, wherein the cause value indicates at least one of: the sensing parameter is not supported; the sensing parameter is out of range; the first network entity is in an overload state; a sensing quality of service, QoS, is not supported; or an unknown error. The overload state may comprise a transmission overload state or a processing overload state. The cause value may comprise an error code.

[0098] The sensing response message may comprise an indication of the cause value. The at least one processor may be further configured to cause the first network entity to: Docket No. SMM920250174-GR-NPdetermine that the first network entity is able to support the sensing service according to the sensing parameter. The at least one processor may be further configured to cause the first network entity to: perform a sensing measurement for the sensing service and according to the sensing parameter. The at least one processor may be further configured to cause the first network entity to: perform a sensing measurement associated with the sensing service and according to the sensing parameter. The sensing response message may comprise an indication of the sensing measurement.

[0099] The sensing parameter may comprise at least one of: a sensing service type; a sensing service requirement; or time information. The sensing service type may comprise at least one of: object detection, object tracking, or environment sensing. The sensing service requirement may comprise at least one of: an accuracy, a latency, or a resolution. The time information may indicate a time when the sensing service required. The time information may comprise a time for a sensing measurement or a time for a sensing report.

[0100] There is further provided herein a method performed or performable by a first network entity, the method comprising: receiving, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and transmitting, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter. Such a method performed or performable by the first network entity tends to provide improved support to the sensing service.

[0101] The method may further comprise determining that the first network entity is not able to support the sensing service according to the sensing parameter. Determining that the first network entity is not able to support the sensing service according to the sensing parameter may comprise determining a cause value, wherein the cause value indicates at least one of: the sensing parameter is not supported; the sensing parameter is out of range; the first network entity is in an overload state; a SQoS is not supported; or an unknown error.

[0102] The overload state may comprise a transmission overload state or a processing overload state. The cause value may comprise an error code. The sensing response message Docket No. SMM920250174-GR-NPmay comprise an indication of the cause value. The method may further comprise determining that the first network entity is able to support the sensing service according to the sensing parameter. The method may further comprise performing a sensing measurement for the sensing service and according to the sensing parameter. The sensing response message may comprise an indication of the sensing measurement. The sensing parameter may comprise at least one of: a sensing service type; a sensing service requirement; or time information.

[0103] There is further provided herein a second network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network entity to: transmit, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and receive, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter. Such a second network entity tends to provide improved support to the sensing service.

[0104] The sensing response message may comprise an indication of the cause value. The sensing response message may comprise an indication of the sensing measurement. The sensing parameter may comprise at least one of: a sensing service type; a sensing service requirement; or time information.

[0105] There is further provided herein a method performed or performable by a second network entity, the method comprising: transmitting, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; and receiving, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter. Such a method performed or performable by the second network entity tends to provide improved support to the sensing service.

[0106] The sensing response message may comprise an indication of the cause value. The sensing response message may comprise an indication of the sensing measurement.Docket No. SMM920250174-GR-NPThe sensing parameter may comprise at least one of: a sensing service type; a sensing service requirement; or time information.

[0107] In some examples described herein, the gNB may not be able to perform the sensing request as instructed by the SF. There may be technical limitations that the requested parameters are out of range of the gNB and within different vendor specific ranges, or due to a specific deployment or due to the current load situation and the requested SQoS. Previously, there was no authorization failure available to the SF e.g., if the measurements cannot be performed.

[0108] In some examples described herein, the Sensing Entity performs authorization of a Sensing Request and returns an authorization failure with a cause value / error code back to the SF in case the Sensing Entity cannot (e.g., temporarily) perform the Sensing Request according to the parameters. In previous systems, the security between the sensing entity and the SF had not been addressed and there was no check of the sensing request in the Sensing Entity e.g., to determine whether the measurement can be performed or not.

[0109] In some examples described herein, the Sensing Entity authorizes the Sensing Request and either performs the sensing according to the instructions in the sensing request from the SF or rejects the request with an authorization failure. In some examples described herein, the following cause values / error codes may cause an authorization failure:Parameter not supported, Parameter out of range, Sensing Entity (e.g., Temporary) Overload, Sensing Quality of Service not supported or (e.g., temporarily) not possible, unknown error.

[0110] There is further provided herein, an apparatus for wireless communication [e.g., a Sensing Entity], comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the apparatus to: receive a sensing request message from a first network function [e.g., an SF] comprising a list of parameters to perform a sensing measurement; authorize the sensing request message by verifying whether the parameters in the sensing request are valid in the apparatus by verifying at least one of the following conditions: whether the parameters in the sensing request message are all supported by the apparatus whether the parameter ranges of all parameters in the sensing request message are all supported by the apparatus whether the transmission and procession Docket No. SMM920250174-GR-NPload in the apparatus is not in overload state whether the bandwidth for performing sensing measurements is available in the apparatus; generate an authorization failure message if at least one of the conditions cannot be fulfilled; respond to the sensing request message from the first network function with an authorization failure message, comprising the cause value of the authorization failure.[OHl] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0112] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Docket No. SMM920250174-GR-NP

Claims

CLAIMSWhat is claimed is:

1. A first network entity for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the first network entity to:receive, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; andtransmit, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

2. The first network entity of claim 1, wherein the at least one processor is further configured to cause the first network entity to:determine that the first network entity is not able to support the sensing service according to the sensing parameter.

3. The first network entity of claim 2, wherein to determine that the first network entity is not able to support the sensing service according to the sensing parameter, the at least one processor is configured to cause the first network entity to:determine a cause value, wherein the cause value indicates at least one of:the sensing parameter is not supported;the sensing parameter is out of range;the first network entity is in an overload state;a sensing quality of service, QoS, is not supported; oran unknown error.

4. The first network entity of claim 3, wherein the sensing response message comprises an indication of the cause value.Docket No. SMM920250174-GR-NP5. The first network entity of claim 1, wherein the at least one processor is further configured to cause the first network entity to:determine that the first network entity is able to support the sensing service according to the sensing parameter.

6. The first network entity of claim 5, wherein the at least one processor is further configured to cause the first network entity to:perform a sensing measurement associated with the sensing service and according to the sensing parameter.

7. The first network entity of claim 6, wherein the sensing response message comprises an indication of the sensing measurement.

8. The first network entity of any one of claims 1 to 7, wherein the sensing parameter comprises at least one of:a sensing service type;a sensing service requirement; ortime information.

9. A method performed or performable by a first network entity, the method comprising:receiving, from a second network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; andtransmitting, to the second network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

10. The method of claim 9, further comprising:Docket No. SMM920250174-GR-NPdetermining that the first network entity is not able to support the sensing service according to the sensing parameter.

11. The method of claim 10, wherein determining that the first network entity is not able to support the sensing service according to the sensing parameter comprises determining a cause value, wherein the cause value indicates at least one ofthe sensing parameter is not supported;the sensing parameter is out of range;the first network entity is in an overload state;a sensing quality of service, QoS, is not supported; oran unknown error.

12. A second network entity for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the second network entity to:transmit, to a first network entity, a sensing request message indicating a request to support a sensing service for a sensing service consumer according to a sensing parameter; andreceive, from the first network entity, a sensing response message indicating whether the first network entity is able to support the sensing service according to the sensing parameter.

13. The second network entity of claim 12, wherein the sensing response message comprises an indication of a cause value.

14. The second network entity of claim 12 or claim 13, wherein the sensing response message comprises an indication of a sensing measurement.

15. The second network entity of any one of claims 12 to 14, wherein the sensing parameter comprises at least one of:Docket No. SMM920250174-GR-NPa sensing service type;a sensing service requirement; or time information.Docket No. SMM920250174-GR-NP

Images