WO2025060114A1

WO2025060114A1 - Systems and methods for sensing measurement and report

Info

Publication number: WO2025060114A1
Application number: PCT/CN2023/120906
Authority: WO
Inventors: Junpeng LOU; Chuangxin JIANG; Zhiqiang Han; Cong Wang; Qi Yang; Focai Peng; Mengzhen LI
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2023-09-23
Filing date: 2023-09-23
Publication date: 2025-03-27
Anticipated expiration: 2026-03-23

Abstract

The present arrangement relates to systems, methods, and non-transitory computer-readable media for sending, by a first wireless communication entity to a second wireless communication entity, a message to request at least one of: a sensing service, a capability, a measurement, or assistance data.

Description

SYSTEMS AND METHODS FOR SENSING MEASUREMENT AND REPORT

TECHNICAL FIELD

The disclosure relates generally to wireless communications and, more particularly, to sensing and communication.

BACKGROUND

Some wireless communication systems may utilize integrated sensing and communication (ISAC) and corresponding enabling technologies to combine sensing and communication systems.

SUMMARY

The example arrangements disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various arrangements, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these arrangements are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed arrangements can be made while remaining within the scope of this disclosure.

In some arrangements, a message is sent. A first wireless communication entity can send a message to a second wireless communication entity. The first wireless communication entity can send the message to request at least one of a sensing service, a capability, a measurement, or assistance data.

The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Various example arrangements of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example arrangements of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

FIG. 1 illustrates an example cellular communication system, according to some arrangements.

FIG. 2 illustrates block diagrams of an example base station and an example user equipment device, according to some arrangements.

FIG. 3 is a diagram illustrating an example communication procedure for sensing measurement and report, according to various arrangements.

FIGS. 4A-C are diagrams illustrating example communication procedures for sensing measurement and report, according to various arrangements.

FIG. 5 is a diagram illustrating an example communications, according to various arrangements.

FIGS. 6A-I are diagrams illustrating example request processes, according to various arrangements.

FIGS. 7A-B are diagrams illustrating example communication procedures, according to various arrangements.

FIGS. 8A-B are diagrams illustrating example communication procedures, according to various arrangements.

FIG. 9 is a diagram illustrating an example communication procedure, according to various arrangements.

FIG. 10 is a diagram illustrating an example event triggering, according to various arrangements.

FIG. 11 is a diagram illustrating an example report process, according to various arrangements.

FIG. 12 is a flowchart diagram illustrating an example method for sensing measurement and report, according to various arrangements.

FIG. 13 is a flowchart diagram illustrating an example method for sensing measurement and report, according to various arrangements.

FIG. 14 is a flowchart diagram illustrating an example method for sensing measurement and report, according to various arrangements.

DETAILED DESCRIPTION

Various example arrangements of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the example arrangements and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise.

A wireless communications system may support integrated sensing and communication (ISAC) . For example, communication and sensing systems may be integrated to use same hardware and spectrum resources. Communication signals used for sensing, target recognition, classification, and detection may be communicated by obtaining information such as angle of arrival, signal delay, Doppler frequency shift, position, and velocity. ISAC may transform target localization and tracking into parameter estimation. However, systems using ISAC may not support configurations for which signal, area, and resources can be used for sensing and communication and/or procedures for signal, area, and resource selection, request, measurement, and reporting. Additionally, the systems may not support configurations for how to trigger signal transmission for sensing or communication. In some cases, optimization strategies associated with ISAC may be deficient. For example, communication systems may assist sensing systems or sensing systems may assist communication systems.

Some ISAC systems may support various application scenarios, working modes, and working architectures. For instance, for sensing services, the working modes can be divided into mono-static A to A or bi-static A to B. The nodes A and B can be either a base station or user equipment (UE) . In some examples, six sensing types can be combined for single station sensing. Additionally, sensing services can be extended to multi-sites collaboration sensing structures. In some examples, positioning services may be similar to sensing services, which can serve as a reference for sensing services.

The arrangement disclosed herein provides systems and methods that support sensing functions and sensing measurement units. For example, the sensing function can be a logical function of a core network, such as a sensing function (SF) , or an enhancement of existing logical functions, such as an enhanced location management function (LMF) . The sensing control function can be a functional module of radio access network (RAN) , such as access and mobility management function (AMF) . In some cases, the sensing measurement unit can be a base station, a transmission reception point (TRP) , or a UE. In some cases, the sensing control unit can be core network sensing services (SSS) entities, AMF, a base station, TRP, or a UE. In some cases, the sensing unit/network unit can be a base station, TRP, or a UE. The network unit can be a core network, 5G core network SSS entities, AMF, SF, LMF, a base station, TRP, or a UE. In some cases, the first wireless communication entity, the second wireless communication entity, the device unit, the core network sensing services entity, the first core network entity, the second core network entity can be a core network unit, 5G core network SSS entities, AMF, SF, LMF, a base station, TRP, a UE or other entity/unit.

FIG. 1 illustrates an example wireless communication system 100 in which techniques disclosed herein may be implemented, in accordance with an implementation of the present disclosure. In the following discussion, the wireless communication system 100 can implement any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as system 100. Such an example system 100 includes a BS 102 and a UE 104 that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101. In FIG. 1, the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126. Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one BS operating at its allocated bandwidth to provide adequate radio coverage to its intended users.

For example, the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively. Each radio frame 118/124 may be further divided into sub- frames 120/127 which may include data symbols 122/128. In the present disclosure, the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various implementations of the present solution.

FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals, e.g., OFDM/OFDMA signals, in accordance with some implementations of the present solution. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative implementation, system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.

System 200 generally includes a BS 202 and a UE 204. The BS 202 includes a Base Station (BS) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220. The UE 204 includes a UE transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.

The system 200 may further include any number of modules other than the modules shown in FIG. 2. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the implementations disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

In accordance with some implementations, the UE transceiver 230 may be referred to herein as an uplink transceiver 230 that includes a Radio Frequency (RF) transmitter and a RF receiver each including circuitry that is coupled to the antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion. Similarly, in accordance with some implementations, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each including circuitry that is coupled to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion. The operations of the two transceiver modules 210 and 230 can be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. In some implementations, there is close time synchronization with a minimal guard time between changes in duplex direction.

The UE transceiver 230 and the BS transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme. In some illustrative implementations, the UE transceiver 210 and the BS transceiver 210 are configured to support industry standards such as the Long-Term Evolution (LTE) and emerging 5G and 6G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the BS transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.

In accordance with various implementations, the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example. In some implementations, the UE 204 can be various types of user devices such as a mobile phone, a smart phone, a Personal Digital Assistant (PDA) , tablet, laptop computer, wearable computing device, etc. The processor modules 214 and 236 may be implemented, or realized, with a general purpose processor a content addressable memory, a digital signal processor an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, a processor may be realized as a microprocessor a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

Furthermore, the methods described in connection with the implementations disclosed herein may be implemented directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some implementations, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.

The network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the BS 202 that enable bi-directional communication between BS transceiver 210 and other network components and communication nodes configured to communication with the BS 202. For example, network communication module 218 may be configured to support internet or WiMAX traffic. In a typical deployment, without limitation, network communication module 218 provides an 802.3 Ethernet interface such that BS transceiver 210 can communicate with a conventional Ethernet based computer network. In this manner, the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) . The terms “configured for” “configured to” and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted and/or arranged to perform the specified operation or function.

UE Sensing Architecture

FIG. 3 is a diagram illustrating an example communication procedure 300 for sensing measurement and report, according to various arrangements. The communication procedure 300 may include an architecture and method associated with sensing services. For example, the communication procedure 300 may include various communications between a UE 302, a network node 304 (e.g., NG-RAN) , an AMF 306, a function 308 (e.g., SF, LMF) , and a network entity 310 (e.g., a fifth-generation core network (5GC) SSS entity, multiple entities) . In some cases, the sensing services can be as the vertical business same as the positioning services.

In some cases, the UE 302, the AMF 306, or the network entity 310 can initiate a sensing service request. For example, the AMF 306 can send the sensing service request to the function 308. The function 308 can generate procedures using interaction of non-access stratum (NAS) signaling with the network node 304 or the UE 302. In response to the procedures, a sensing service response is given to a request point.

At 312, the network entity 310 (e.g., a gateway mobile location center (GMLC) or another entity in the 5GC) may request a sensing/location service (e.g., sensing/positioning) for the UE 302 (e.g., a target UE) to the AMF 306 (e.g., a serving AMF) . Alternatively, at 314, the serving AMF 306 for the target UE 302 may determine a need for some sensing/location service (e.g., to locate the UE 302 for an emergency call) . Alternatively, at 316, the UE 302 may request a sensing/location service (e.g., sensing/positioning or delivery of assistance data) to the serving AMF at the NAS level. At 318, the AMF 306 may transfer the sensing service request to the function 308.

At 320, the function 308 may initiate sensing/location procedures with a serving (e.g., neighboring) BS (e.g., ng-eNB, gNB) in the communication network (e.g., NG-RAN network) . For example, the function 308 may initiate the procedures to obtain sensing/positioning measurements or assistance data. Additionally, or alternatively, at 322, the function 308 may initiate sensing/location procedures with the UE 302, for example, to obtain a sensing/location estimate or sensing/positioning measurements or to transfer sensing/location assistance data to the UE 302.

At 324, the function 308 may provide a sensing/location service response to the AMF 306 and may include various results (e.g., success or failure indication, a location/sensing estimate for the UE 302 if requested and obtained) .

At 326, the AMF 306 may return a sensing/location service response to the network entity 310, where the service response may include various results (e.g., a location/sensing estimate for the UE 302) . Alternatively, at 328, the AMF 306 may use the sensing/location service response received at 324 to assist the service that triggered 314 (e.g., may provide a sensing/location estimate associated with an emergency call to a GMLC) . Alternatively, at 330, the AMF 306 may return a sensing/location service response to the UE 302, where the service response may include various results (e.g., a sensing/location estimate for the UE 302) .

Sensing Mechanisms

FIGS. 4A-C are diagrams illustrating example communication procedures 400, 401, and 403 for sensing measurement and report, according to various arrangements. The communication procedures 400, 401, and 403 may include methods associated with sensing services. For example, the communication procedures 400, 401, and 403 may include various communications between a UE 402, a network node 404 (e.g., NG-RAN) , an AMF 406, a network entity 407 (e.g., a GMLC) , and a function 408 (e.g., SF, LMF) .

The communication procedures 400, 401, and 403 may be associated with various sensing mechanisms. For example, the sensing mechanisms may include Mobile Originated Sensing Request (MO-SR) , Mobile Terminated Sensing Request (MT-SR) and Network Induced Sensing Request (NI-SR) . UE-sensing-related services can be instigated from the 5GC for an NI-SR or MT-SR sensing service, or from the UE 402 in case of an MO-SR sensing service.

In the example of FIG. 4A, a sequence of operations for an NI-SR or MT-SR location service may be shown. The service may start where the AMF 406 initiates a service in the function 408. For example, at 410, the AMF 406 may send a sensing/location request message to the function 408. At 412, the UE 402, the network node 404, the AMF 406, and/or the function 408 perform one or more LTE positioning protocol (LPP) /other transactions. At 414, the network node 404, the AMF 406, and/or the function 408 perform one or more NR positioning protocol A (NRPPa) /other transactions. At 416, the function 408 may send a sensing/location response to the AMF 406.

In the example of FIG. 4B, a sequence of operations for an MO-SR service may be shown. The service may start where a location services (LCS) and/or a sensing service (SSS) client in the UE 402 or the user has requested some sensing/location service (e.g., retrieval of the target/UE 402 location or transfer of the target/UE 402 location to a third party) . For example, at 418, the UE 402 may send a request message (e.g., MO-LR request, LPP protocol data unit (PDU) ) to the AMF 406. The AMF 406 may send a sensing/location request (e.g., LPP PDU) to the function 408. At 422, the UE 402, the network node 404, the AMF 406, and/or the function 408 perform one or more LPP transactions. At 424, the network node 404, the AMF 406, and/or the function 408 perform one or more NRPPa transactions. At 426, the function 408 may send a sensing/location response to the AMF 406. At 428, the AMF 406 may optionally transfer to a fourth party. At 430, the AMF 406 may send an MO-LR response to the UE 402.

In the example of FIG. 4C, a sequence of operations for a deferred MT-SR event reporting may be shown. The service may start where the UE 402 reports an event to the function 408. For example, at 432, the UE 402 may send an event report to the function 408. At 434, the function 408 may determine sensing/positioning (e.g., a need for sensing/positioning) . At 436, the UE 402, the network node 404, the AMF 406, and/or the function 408 perform one or more LPP transactions. At 438, the network node 404, the AMF 406, and/or the function 408 perform one or more NRPPa transactions. At 440, the function 408 may send an event notification to the network entity 407. In some cases, the examples depicted in FIGS. 4A-C may relate to sidelink (SL) UE sensing architectures.

Sensing Message Exchange

FIG. 5 is a diagram illustrating an example communication 500. The communication 500 may include a sensing message exchange 502. For example, sensing information may be exchanged between receiving and sending points. A core network unit (e.g., SF, LMF, AMF) may notify of the sensing information exchange. For instance, for better receiving, the core network unit (e.g., SF, LMF) can exchange the information from sensing sender to the sensing receiver (e.g., A2B) . Additionally, or alternatively, to avoid the receiving interference, the core network unit (e.g., SF, LMF) can control or configure the signal transmission among the sensing senders. That is, if the sensing sender A1 sends a transmission, other sensing senders may not send transmissions.

Sensing Request

FIGS. 6A-I are diagrams illustrating example request processes 600, 601, 603, 605, 607, 609, 611, 613, and 615 according to various arrangements. The request processes 600, 601, 603, 605, 607, 609, 611, 613, and 615 methods associated with sensing services. For example, the request processes 600, 601, 603, 605, 607, 609, 611, 613, and 615 may include various types of sensing requests. The request process may be one of MO-SR, MT-SR, and/or NI-SR. In some cases, a sensing measurement unit/sensing control unit may send a request to the sensing control function. For example, a UE may send the sensing service request to an AMF or 5GC SSS entities may send the sensing service request to the AMF. The AMF may send the request to a function (e.g., SF, LMF) . Additionally, or alternatively, the AMF may trigger the request sending, from the AMF to the function.

In the example of FIG. 6A, the request process 600 may include a sensing request 602. In some cases, a request process includes a sensing measurement. The sensing measurement unit may be configured by information in the sensing request 602. For example, the sensing measurement unit may receive the request 602. The sensing measurement unit may perform a related measurement (s) and report to the unit which sent the request 602.

The sensing request 602 may include at least one of the following information (the value) :

● Velocity related parameters: velocity/speed, Doppler, accelerated velocity, micro-Doppler;

● Power related parameters: power, reference signal received power (RSRP) , RSRP per path (RSRPP) , received signal strength indicator (RSSI) , RSSI per path (RSSIP) ;

● Angle related parameters: angle, angle of arrival (AOA) , zenith of arrival (ZOA) , angle of destination (AOD) , zenith of destination (ZOD) ;

● Distance related parameters: distance, round trip time (RTT) , Delay, reference signal time difference (RSTD) ;

● Resource related parameters: time, frequency, beam (spatial relation, spatial filter) ; or

● Other parameters: phase, line of sight (LOS) /non-line of sight (NLOS) , the number of path, radar cross section (material, size, angle) .

In some cases, the information in the sensing request 602 may increase accuracy in sensing aim for the sensing measurement unit, which may result in a lower payload and a lower latency. Some interference and noise effects can be eliminated through these request information/parameters.

Alternatively, the information can be the value, value range, range list, value list (s) , threshold/limit threshold, threshold/limit threshold list, variation, variance, change in value, the limit threshold of variation (variance, change in value) , variation list (s) , variance list (s) or change in value list (s) of at least one of these parameters. In some cases, the parameters may be used with horizontal and/or vertical. For example, horizontalSpeed and/or verticalSpeed. In some cases, request location/sensing information quality of service (QoS) with parameters’ accuracy may be included (e.g., accuracy information element (IE) indicates the quality of service and includes a number of sub-fields) . In the case of measurements, some of the sub-fields apply to the location/sensing estimate that could be obtained by the server from the measurements provided by the sensing target/unit and/or target device assuming that the measurements are the only sources of error.

In the example of FIG. 6B, the request process 601 may include a sensing request 604. The sensing request may include a value range. For example, the value range of the parameters may be used to request sensing measurement and/or sensing service.

For velocity 606 related parameters:

● The value range of sensing velocity/speed:

a. The value range of sensing velocity/speed is used to indicate the expected/interested target velocity/speed range.

b. This field, if present, indicates that the velocity in the range should be measured for the sensing measurement/service.

● The value range of sensing Doppler:

a. The value range of sensing Doppler is used to indicate the expected/interested Doppler range.

b. This field, if present, indicates that the Doppler in the range should be measured for the sensing measurement/service.

● The value range of sensing accelerated velocity/speed:

a. The value range of sensing accelerated velocity is used to indicate the expected/interested accelerated velocity range.

b. This field, if present, indicates that the accelerated velocity in the range should be measured for the sensing measurement/service.

● The value range of sensing micro-Doppler:

a. The value range of sensing micro-Doppler is used to indicate the expected/interested micro-Doppler range.

b. This field, if present, indicates that the micro-Doppler in the range should be measured for the sensing measurement/service.

For power 608 related parameters:

● The value range of sensing power:

a. The value range of sensing power is used to indicate the expected/interested power range.

b. This field, if present, indicates that the power in the range should be measured for the sensing measurement/service.

● The value range of sensing RSRP:

a. The value range of sensing RSRP is used to indicate the expected/interested RSRP range.

b. This field, if present, indicates that the RSRP in the range should be measured for the sensing measurement/service.

● The value range of sensing RSRPP:

a. The value range of sensing RSRPP is used to indicate the expected/interested RSRPP range.

b. This field, if present, indicates that the RSRPP in the range should be measured for the sensing measurement/service.

● The value range of sensing RSSI:

a. The value range of sensing RSSI is used to indicate the expected/interested RSSI range.

b. This field, if present, indicates that the RSSI in the range should be measured for the sensing measurement/service.

● The value range of sensing RSSIP (RSSI-per path) :

a. The value range of sensing RSSIP is used to indicate the expected/interested RSSIP range.

b. This field, if present, indicates that the RSSIP in the range should be measured for the sensing measurement/service.

For angle 610 related parameters:

● The value range of sensing angle:

a. The value range of sensing angle is used to indicate the expected/interested angle range.

b. This field, if present, indicates that the angle in the range should be measured for the sensing measurement/service.

● The value range of sensing AOA (AOA, ZOA) :

a. The value range of sensing AOA (AOA, ZOA) is used to indicate the expected/interested AOA (AOA, ZOA) range.

b. This field, if present, indicates that the AOA (AOA, ZOA) in the range should be measured for the sensing measurement/service.

● The value range of sensing ZOA:

a. The value range of sensing ZOA is used to indicate the expected/interested ZOA range.

b. This field, if present, indicates that the ZOA in the range should be measured for the sensing measurement/service.

● The value range of sensing AOD (AOD, ZOD) :

a. The value range of sensing AOD (AOD, ZOD) is used to indicate the expected/interested AOD (AOD, ZOD) range.

b. This field, if present, indicates that the AOD (AOD, ZOD) in the range should be measured for the sensing measurement/service.

For distance 612 related parameters:

● The value range of sensing distance:

a. The value range of sensing distance is used to indicate the expected/interested distance range.

b. This field, if present, indicates that the distance in the range should be measured for the sensing measurement/service.

● The value range of sensing RTT:

a. The value range of sensing RTT is used to indicate the expected/interested RTT range.

b. This field, if present, indicates that the RTT in the range should be measured for the sensing measurement/service.

● The value range of sensing Delay:

a. The value range of sensing Delay is used to indicate the expected/interested Delay range.

b. This field, if present, indicates that the Delay in the range should be measured for the sensing measurement/service.

● The value range of sensing RSTD:

a. The value range of sensing RSTD is used to indicate the expected/interested RSTD range.

b. This field, if present, indicates that the RSTD in the range should be measured for the sensing measurement/service.

For resource 614 related parameters:

● The value range of sensing time:

a. The value range of sensing time is used to indicate the expected/interested time range.

b. This field, if present, indicates that the time in the range should be measured for the sensing measurement/service.

● The value range of sensing frequency:

a. The value range of sensing frequency is used to indicate the expected/interested frequency range.

b. This field, if present, indicates that the frequency in the range should be measured for the sensing measurement/service.

● The value range of sensing beam (spatial relation, spatial filter) :

a. The value range of sensing beam (spatial relation, spatial filter) is used to indicate the expected/interested beam (spatial relation, spatial filter) range.

b. This field, if present, indicates that the beam (spatial relation, spatial filter) in the range should be measured for the sensing measurement/service.

For other parameters 616:

● The value range of sensing phase:

a. The value range of sensing phase is used to indicate the expected/interested phase range.

b. This field, if present, indicates that the phase in the range should be measured for the sensing measurement/service.

● The value range of sensing LOS/NLOS:

a. The value range of sensing LOS/NLOS is used to indicate the expected/interested LOS/NLOS range.

b. This field, if present, indicates that the LOS/NLOS in the range should be measured for the sensing measurement/service.

c. For example, the LOS/NLOS is defined in the range of [0, 1] . Value 0 means NLOS channel, and 1 means LOS channel. If the field sets a range [0.5, 1] , then a UE receiving the request information will measure/do sensing under the LOS/NLOS condition [0.5, 1] .

● The value range of sensing radar cross section (RCS) :

a. The value range of sensing RCS is used to indicate the expected/interested RCS range.

b. This field, if present, indicates that the RCS in the range should be measured for the sensing measurement/service.

● Furthermore, the RCS can be reflected in material, size and/or angle of the target:

a. The value range of sensing material of the target.

i. The value range of sensing material of the target is used to indicate the expected/interested material of the target range.

ii. This field, if present, indicates that the material of the target in the range should be measured for the sensing measurement/service.

● b. The value range of sensing size of the target.

i. The value range of sensing size of the target is used to indicate the expected/interested size of the target range.

ii. This field, if present, indicates that the size of the target in the range should be measured for the sensing measurement/service.

c. The value range of sensing angle of the target.

i. The value range of sensing angle of the target is used to indicate the expected/interested angle of the target range.

ii. This field, if present, indicates that the angle of the target in the range should be measured for the sensing measurement/service.

In the example of FIG. 6C, the request process 603 may include a sensing request 618. In some cases, the sensing request 618 may be set per path and/or per LOS/NLOS indicator (e.g., parameters of the sensing request 618 may be set per path and/or per LOS/NLOS) . For example, the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B. For the LOS channel, the sensing service may provide some advantages over the NLOS channel, and the first path or the strongest power path may carry some different information than other paths for sensing. The parameters per path may be helpful to the sensing measurements/services, and all the parameters/information (e.g., velocity, power, angle, distance, resource, and other parameters) can be set per path and/or LOS/NLOS indicator.

Using angle related parameters as an example:

● The value range of sensing angle per path:

a. The value range of sensing angle per path is used to indicate the expected/interested angle range per path.

b. This field, if present, indicates that the angle per path in the range should be measured for the sensing measurement/service.

● The value range of sensing AOA (AOA, ZOA) per path:

a. The value range of sensing AOA (AOA, ZOA) per path is used to indicate the expected/interested AOA (AOA, ZOA) range per path.

b. This field, if present, indicates that the AOA (AOA, ZOA) per path in the range should be measured for the sensing measurement/service.

● The value range of sensing ZOA per path:

a. The value range of sensing ZOA per path is used to indicate the expected/interested ZOA range per path.

b. This field, if present, indicates that the ZOA per path in the range should be measured for the sensing measurement/service.

● The value range of sensing AOD (AOD, ZOD) per path:

a. The value range of sensing AOD (AOD, ZOD) per path is used to indicate the expected/interested AOD (AOD, ZOD) range per path.

b. This field, if present, indicates that the AOD (AOD, ZOD) per path in the range should be measured for the sensing measurement/service.

In the example of FIG. 6D, the request process 605 may include a sensing request 620. In some cases, the sensing request 620 (e.g., parameters of the sensing request 620) may be set as non-preferred field/area (range) (e.g., not expected/interested sensing field) . For example, parameters/information may include the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B.

For the parameters/information, the information in the sensing request 620 could make the sensing measurement unit have accurate sensing aim. Then a lower payload and a lower latency can be obtained.

That is similarly to the non-preferred sensing measurements/services request. The parameters with non-preferred indicator may also be helpful to the sensing measurements/services. In some cases, the parameters/information can be set as the non-preferred field indicator.

Using velocity related parameters as an example:

● The value range of non-preferred sensing velocity/speed:

a. The value range of non-preferred sensing velocity/speed is used to indicate the not expected/interested target velocity/speed range.

b. This field, if present, indicates that the velocity in the range should not be measured for the sensing measurement/service.

● The value range of non-preferred sensing Doppler:

a. The value range of non-preferred sensing Doppler is used to indicate the not expected/interested Doppler range.

b. This field, if present, indicates that the Doppler in the range should not be measured for the sensing measurement/service.

● The value range of non-preferred sensing accelerated velocity/speed:

a. The value range of non-preferred sensing accelerated velocity is used to indicate the not expected/interested accelerated velocity range.

b. This field, if present, indicates that the accelerated velocity in the range should not be measured for the sensing measurement/service.

● The value range of non-preferred sensing micro-Doppler:

a. The value range of non-preferred sensing micro-Doppler is used to indicate the not expected/interested micro-Doppler range.

b. This field, if present, indicates that the micro-Doppler in the range should not be measured for the sensing measurement/service.

In the example of FIG. 6E, the request process 607 may include a sensing request 622. In some cases, the sensing request 622 (e.g., parameters of the sensing request 622) may be set as range/value list (s) which are expected/interested or not expected/interested sensing field. For example, parameters/information may include the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B.

For the parameters/information, the information with the range/value list (s) in the sensing request 622 could make the sensing measurement unit have accurate sensing aim. Then a lower payload and a lower latency can be obtained. The parameters with the range/value list (s) indicator may also be helpful to the sensing measurements/services, and all the parameters/information can be set as the range/value list (s) field indicator.

In some cases, the rand/value list (s) can be working at a dedicated and/or cooperated state. For example, as the cooperated state working mode, an area is configured based on two lists or two parameters in a list, and the area is the intersection of the two parameters. Such as one area is given by a distance related parameter, and another area is given by a velocity related parameter.

In some cases, as the dedicated state working mode, two areas are configured based on two lists or two parameters in a list, and the first area may have the intersection with another area. Such as one area is given by a distance related parameter, and another area is given by a velocity related parameter.

In some cases related to velocity, there can be two sets configuration of Doppler and micro-Doppler associated with different/same/related areas/granularities. Such as the Doppler measurement is configured in a big area/granularity, and for a certain small area/granularity the micro-Doppler is measured.

In the example of FIG. 6F, the request process 609 may include a sensing request 624. In some cases, the sensing request 624 (e.g., parameters of the sensing request 624) may be set as threshold/limit threshold, threshold/limit list (s) , the limit threshold of variation (variance, change in value) , which may be expected/interested or not expected/interested sensing field. For example, parameters/information may include the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B.

For the parameters/information, the information with the threshold/limit threshold, threshold/limit threshold list (s) in the sensing request could make the sensing measurement unit have accurate sensing aim. Then a lower payload and a lower latency can be obtained. The parameters with threshold/limit threshold and/or threshold/limit threshold list (s) indicator may also be helpful to the sensing measurements/services, and all the parameters/information can be set as the threshold/limit threshold, threshold/limit threshold list (s) field indicator.

In the example of FIG. 6G, the request process 611 may include a sensing request 626. In some cases, the sensing request 626 (e.g., parameters of the sensing request 626) may be set as variation, variance, change in value, variation list (s) , variance list (s) , or change in value list (s) , which may be expected/interested or not expected/interested sensing field. For example, parameters/information may include the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B.

For the parameters/information, the information with the variation, variance, change in value, variation list (s) , variance list (s) or change in value list (s) in the sensing request could make the sensing measurement unit have accurate sensing aim. Then a lower payload and a lower latency can be obtained. The parameters with the variation, variance, change in value, variation list (s) , variance list (s) or change in value list (s) indicator may also be helpful to the sensing measurements/services, and all the parameters/information can be set as the variation, variance, change in value, variation list (s) , variance list (s) or change in value list (s) field indicator.

In the example of FIG. 6H, the request process 613 may include a sensing request 628. In some cases, the sensing request 628 (e.g., parameters of the sensing request 628) may be set as radial parameter (e.g. velocity) and/or non-radial parameter (e.g. velocity) . For example, parameters/information may include the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B.

In the example of FIG. 6I, the request process 615 may include a sensing request 630. In some cases, the sensing request 630 (e.g., parameters of the sensing request 630) may be set as horizontal parameter and/or vertical parameter. For example, parameters/information may include the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B.

Sensing Capability

FIGS. 7A-B are diagrams illustrating example communication procedures 700 and 701, according to various arrangements. The communication procedures 700 and 701 may include a sensing unit 702 and a server 704. In the example of FIG. 7A, the server 704 may send a request message 706 (e.g., RequestCapabilities) to the sensing unit 702. The server 704 may indicate the types of capabilities needed. The sensing unit 702 may respond with a message 708 (e.g., ProvideCapabilities) to the server 704. The capabilities may correspond to any capability types specified by the request message 706. In the example of FIG. 7B, a capability indication procedure may be shown. For example, the procedure may allow the sensing unit 702 to provide unsolicited capabilities to the server 704. To do so, the sensing unit 702 may send a message 710 (e.g., ProvideCapabilities) to the server 704.

In some cases, the capability can be one of the measurement capability or sensing method capability. Parameters/information (e.g., the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B) may correspond to a capability. Including the value, value range, range list, value list (s) , threshold/limit threshold, threshold/limit threshold list, variation, variance, change in value, variation list (s) , variance list (s) or change in value list (s) of at least one of these parameters.

In some examples, the velocity related parameters may correspond to the capability of velocity related measurements. Such as the capability of micro-Doppler measurement. If the core network unit requests a micro-Doppler measurement, the core network unit may know if the measurement unit has the capability to measure micro-Doppler. For example:

● A core network unit (SF/LMF/AMF) requests the capability of a sensing unit (UE/gNB/TRP) as the sensing transmission point.

a. For example, SF/AMF requests the capability of gNB/TRP as the sensing transmission point.

● A core network unit (SF/LMF/AMF) requests the capability of a sensing unit (UE/gNB/TRP) as the sensing receiving point.

a. For example, SF/AMF requests the capability of gNB/TRP as the sensing receiving point.

● A sensing unit (UE/gNB/TRP) transmits feedback of the sensing capability of a sensing unit (UE/gNB/TRP) to SF/AMF.

a. For example, UE replies/reports/feedbacks the sensing capability to SF/AMF.

b. For example, UEA replies/reports/feedbacks the sensing capability of UEB to SF/AMF.

c. For example, gNB/TRP replies/reports/feedbacks the sensing capability of UE to SF/AMF. If a gNB/TRP/UE has been told/configured/reported the sensing capability of other gNB/TRP/UE, it can feedback/reply/report these sensing capabilities.

Sensing Assistance Data

FIGS. 8A-B are diagrams illustrating example communication procedures 800 and 801, according to various arrangements. The communication procedures 800 and 801 may include a sensing unit 802 and a server 804. In the example of FIG. 8A, the sensing unit 802 may send a request message 806 (e.g., RequestAssistanceData) to the server 804. The server 804 may respond with a message 808 (e.g., ProvideAssistanceData) to the sensing unit 802, the message 808 including assistance data. The transferred assistance data should match or be a subset of the assistance data requested by the message 806. The server 804 may also provide any not requested information that it considers useful to the sensing unit 802. The server 804 may transmit one or more additional messages 810 (e.g., ProvideAssistanceData) to the sensing unit 802 containing further assistance data. The transferred assistance data should match or be a subset of the assistance data requested in step 1. The server 804 may also provide any not requested information that it considers useful to the sensing unit 802.

In the example of FIG. 8B, the server 804 may send a message 812 (e.g., ProvideAssistanceData) to the target containing assistance data (e.g., the sensing unit 802) . The server 804 may transmit one or more additional messages 814 (e.g., ProvideAssistanceData) to the target containing additional assistance data.

In some cases, the assistance data can correspond to parameters/information (e.g., the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B) . Including the value, value range, range list, value list (s) , threshold/limit threshold, threshold/limit threshold list, variation, variance, change in value, variation list (s) , variance list (s) or change in value list (s) of at least one of these parameters.

In some examples, the velocity related parameters may correspond to the assistance data of velocity related measurements. Such as the capability of micro-Doppler measurement. If the core network unit requests sensing service, based on the assistance data, the measurement unit can aim to a major measurement for the sensing service.

Sensing Measurement

FIG. 9 is a diagram illustrating an example communication procedure 900, according to various arrangements. The communication procedure 900 may include a sensing unit 902 and a server 904. In some cases, the communication procedure 900 may include sensing measurements. The sensing measurements may correspond to parameters/information (e.g., the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B) . Including the value, value range, range list, value list (s) , threshold/limit threshold, threshold/limit threshold list, variation, variance, change in value, variation list (s) , variance list (s) or change in value list (s) of at least one of these parameters. In some cases, the parameters may be used with horizontal and/or vertical parameters (e.g., horizontalSpeed: INTEGER (0 ... 2047) , verticalSpeed: INTEGER (0 ... 255) .

In some cases, based on the measurement, it could make the sensing measurement unit have generalized sensing results, and the multiple dimensions observation of the measurements can bring more information about the sensing services. Then a more accurate sensing service and/or positioning service can be obtained. These measurements are also useful in positioning service. For each measurement IE, the IE is associated with another IE quality (e.g., MeasQuantity) including QualityValues and/or QualityResolution. The quality IE can include three sub-IEs (e.g., uncertainty, confidence, and resolutions) . For example, a timing quality may include a timingQualityValue (e.g., provides an estimate of uncertainty of the timing value for which the IE NR-TimingQuality is provided in units of meters) and/or a timingQualityResolution (e.g., provides the resolution used in the timingQualityValue field, where enumerated values mdot1, m1, m10, m30 correspond to 0.1, 1, 10, 30, meters, respectively) .

uncertaintyIE INTEGER (0.. 127) ,

orientationIE INTEGER (0.. 179) ,

confidence INTEGER (0.. 100)

In some cases, parameters may associated with the horizontal, vertical parameter.

horizontalUncertaintyDoppler INTEGER (0.. 255) ,

verticalUncertaintyDoppler INTEGER (0.. 255)

In some cases, the parameters may be per sensing target, per sensing target group/list (s) , or per UE/TRP.

In some cases, the beam predictions can be used for the transmissions based on the measurement of velocity. It can make the sensing transmission point send the beams in different time with direction to the sensing target. For example, the micro-Doppler measurement can be used to eliminate some interference and noise effects. What is more, it is useful to distinguish the targets or gesture recognition. Such as the regular changes in the micro-Doppler can be seen as the interference of an instruction gesture recognition.

The measurement can also be a variance of these measurement parameters. For example, the variance of RSRP measurement which is the difference of two RSRP measurements. For a target, the variance of RSRP contains the changes information of the target or the link of the target, which is useful for target tracking.

In some cases, the sensing unit 902 and the server 904 may exchange sensing measurement responses. For example, the server 904 may send a request message 906 (e.g., RequestSensingInformation) to the sensing unit 902. The sensing unit 902 may send a message 908 (e.g., ProvideSensingInformation) to the server 904. The sensing unit 902 may send a message 910 (e.g., ProvideSensingInformation) to the server 904. The RequestSensingInformation and/or ProvideSensingInformation may correspond to parameters/information (e.g., the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B) . Including the value, value range, range list, value list (s) , threshold/limit threshold, threshold/limit threshold list, variation, variance, change in value, variation list (s) , variance list (s) or change in value list (s) of at least one of these parameters. In some cases, the parameters may be used with horizontal and/or vertical parameters (e.g., horizontalSpeed: INTEGER (0 .. 2047) , verticalSpeed: INTEGER (0 .. 255) .

FIG. 10 is a diagram illustrating an example event triggering 1000, according to various arrangements. The event triggering 1000 may include one or more triggering conditions 1002 that can trigger one or more sensing events 1004 (e.g., for sensing) . The events 1004 can be a request, reporting, replying, feedback, recommendation, (pre-) configuration, process (measurement) , or sensing service.

In some examples, the condition 1002 may be from a communication, and the triggered event 1004 may be associated with a sensing service. On the contrary, the condition 1002 can be one of the sensing, and the event 1004 may be associated with communication. For example, some events 1004 may be based on the measurement of a sensing unit or a communication unit can be used for the sensing service.

In some cases, the trigger condition (s) 1002 can be (pre-) configured by the network unit and sent to the sensing unit. Alternatively, the trigger condition (s) 1002 can be (pre-) configured by the sensing unit. The trigger condition (s) 1002 can be associated with at least one of parameters/information (e.g., the velocity, power, angle, distance, resource, and other parameters described with reference to FIGS. 6A-B) . Alternatively, the trigger condition (s) 1002 can be the value, value range, range list, value list (s) , threshold/limit threshold, threshold/limit threshold list, variation, variance, change in value, the limit threshold of variation (variance, change in value) , variation list (s) , variance list (s) , or change in value list (s) of at least one of these parameters.

In some examples, the variation threshold of LOS/NLOS indicator may be a condition 1002 to trigger a sensing service. The LOS/NLOS may be defined in the range of [0, 1] . Value 0 means NLOS channel, and 1 means LOS channel. The variation threshold is configured as 0.2. When a UE measures the LOS/NLOS from 0.3 to 0.6, then a sensing service is triggered, because the variation 0.3 is bigger than the variation threshold 0.2.

In some examples, the variation threshold of RSRP/velocity may be a condition 1002 to trigger a sensing service. A road-side unit (RSU) may measure the signal from a TRP. In a period of time, if the variation exceeds the configured variation threshold, an event 1004 of sensing service may be triggered.

In some examples including a request, the request can also be an event triggering. Such as a sensing service request or a measurement request. A measurement can trigger a sensing service. The measurement is associated with the triggering condition (s) . Alternatively, the trigger condition (s) can be the variation of a (measurement) period, or the variation of a resource. For example, a period of measurement may be changed from 10ms to 5ms. An event of sensing service can be triggered to assist the measurement. The variation of the frequency, phase, amplitude, or beam can also as an event trigger condition.

FIG. 11 is a diagram illustrating an example report process 1100, according to various arrangements. In some cases, the request, measurement, report (e.g., sensing measurement report) , reply, feedback/provision procedures may have similarly schemes as report/reporting process (es) .

The report process 1100 may include a sensing report 1102. The report process 1100 may be associated with one or more schemes of reporting, request, recommendation, (pre-) configuration, process, feedback, or event triggering. For example, request/reporting/feedback a sensing service, a measurement, a UE capability, an assistance data, or process the sensing measurement.

In some cases, reporting the sensing report 1102 can be persistent periodic, semi-persistent periodic or aperiodic. The transmission conditions may be changed occasionally, frequently, or hardly. The reporting can be persistent periodic, semi-persistent periodic or aperiodic. The measurement/request/sensing service triggering may be the same as the reporting. The persistent periodic, semi-persistent periodic, or aperiodic schemes for an appropriate service/event/case can bring a lower delay and/or lower payload.

In some cases, the reporting can be periodic or aperiodic. For different sensing service, the reporting schemes can be different. For example, the periodic reporting can reduce the payload of the request signal, and the aperiodic reporting schemes can reduce the feedback/reporting payload. What’s more a lower delay can be also obtained.

In some cases, tor a periodic reporting, it can be persistent or semi-persistent. For a periodic reporting, if the transmission conditions hardly change, the period of reporting can be persistent. If the transmission conditions are changed occasional, a semi-persistent periodic reporting is more appropriate.

In a period of time, the total number of reporting times may be (pre-) configured. In a period of time, there can be many times of sensing/measurements. If all the measurement are reported, there will be more repeat information and a heavy payload. In a period of time, the measurements may have some associations, only one or n times measurement result (s) are reported. The n times measurement results can be reported together with once reporting. Alternatively:

● Only once reporting are executed in a period of time.

● In a period of time, M times reporting are executed by the sensing unit/network unit, wherein the M is the integer including zero.

● A reporting of measurement (s) contains at least one measurement result.

Based on the method, there can be no/less congestion in reporting procedures.

The reporting can be deferred. For example, the sensing service results reporting can be reported after a period of time when the sensing service results are obtained. For another example, the measurement results reporting can be reported after a period of time when the measurement results are obtained.

In some cases, the request, measurement, report (e.g., sensing measurement report) , reply, feedback/provision procedures can be associated with priority/priorities.

The reporting can be associated with the priority/priorities. The request, measurement, reporting, feedback/provision procedures/contents can be also associated with priority/priorities. For example, if many sensing/measurements are waiting to be reported, the priorities of these sensing/measurements can be used to decided which sensing/measurements or the order of these sensing/measurements should be reported. Based on method, there can be no/less congestion in reporting procedures.

The reporting can be triggered by an event/condition or events/condition (s) (some events/condition combined triggering) . For example, a power related parameter triggers a reporting. A UE is (pre-) configured by a RSRP threshold. If a RSRP measurement is bigger than the RSRP threshold, it will report a measurement event. For another example, a power related parameter and the variation is configured to trigger the reporting. A UE is (pre-) configured by a RSRP threshold and a variation threshold. If a RSRP measurement is bigger than the RSRP threshold and the value change is over the variation threshold, it will report a measurement event.

The sensing unit can be configured to measure all the information, but for different requests partial measurement/sensing/positioning results can be feedback/report ed. For example, a sensing service A may include a partial area of another sensing service B. If the sensing service B have been done, and the sensing results contain service A can be report only. For another example, a list of measurement results may be reported to the core network unit. But only some measurement results are reported.

FIG. 12 is a flowchart diagram illustrating an example method 1200 for sensing measurement and report, according to various arrangements. In some cases, the method 1200 may include a request message.

At 1202, a first wireless communication entity may send, to a second wireless communication entity, a message to request at least one of: a sensing service, a capability, a measurement, or assistance data. In some embodiments, the first wireless communication entity and the second wireless communication entity includes a core network SSS, a first core network entity, a second core network entity, or a device unit. In some embodiments, the first core network entity includes an LMF entity, and the second core network entity includes an AMF entity. In some embodiments, the sensing service includes an MO-SR, an MT-SR, an NI-SR, or another type of sensing request.

In some embodiments, the message includes at least one of information corresponding to the capability, the measurement, or the assistance data. For example, the information may include a velocity related parameter, a power related parameter, an angle related parameter, a distance related parameter, a resource related parameter, or one or more other parameters. In some embodiments, the information in the message is indicated as at least one of a value, a value range, a range list, a value list, a threshold, a threshold list, a variation, a variance, a change in value, a limit threshold of variation, a variation list, a variance list, or a change in value list. In some embodiments, the information in the message is indicated par path, per LOS indicator, or per NLOS indicator. In some embodiments, the information in the message is indicated with a radial (velocity) and/or a non-radial (velocity) . In some embodiments, the information is indicated horizontally and/or vertically. In some embodiments, the information is indicated as a non-preferred field, a non-preferred area, or non-preferred range. In some embodiments, the information is indicated as an expected field, expected area, or expected range.

FIG. 13 is a flowchart diagram illustrating an example method 1300 for sensing measurement and report, according to various arrangements. In some cases, the method 1300 may include a message.

At 1302, a first wireless communication entity may send, to a second wireless communication entity, a message indicating at least one of: a sensing service, a capability, a measurement, or assistance data. In some embodiments, the first and second wireless communication entities each include a core network sensing services entity, a first core network entity, a second core network entity, or a device unit. In some embodiments, the first core network entity includes an LMF entity, and the second core network entity includes an AMF entity.

In some embodiments, the message further comprises at least one of the following information corresponding to the capability, the measurement, or the assistance data: a velocity related parameter, a power related parameter, an angle related parameter, a distance related parameter, a resource related parameter, or one or more other parameter. In some embodiments, the information in the message is indicated as at least one of a value, a value range, a range list, a value list, a threshold, a threshold list, a variation, a variance, a change in value, a limit threshold of variation, a variation list, a variance list, or a change in value list. In some embodiments, the information in the message is indicated per path, an LOS indicator, or an NLOS indicator. In some embodiments, the information in the message is indicated with a radial (velocity) and/or a non-radial (velocity) . In some embodiments, the information in the message is indicated horizontally and/or with vertically. In some embodiments, the information in the message is indicated as a non-preferred field, non-preferred area, or non-preferred range. In some embodiments, the information in the message is indicated as an expected field, expected area, or expected range.

FIG. 14 is a flowchart diagram illustrating an example method 1400 for sensing measurement and report, according to various arrangements. In some cases, the method 1400 may include an event.

At 1402, a second wireless communication entity may initiate an event triggered by one or more conditions. The one or more conditions may include information in a message received by the second wireless communication entity. The event may include a request, a reporting (process) , a feedback (process) , a recommendation (process) , a measurement (process) , a (sensing) service, a replying (process) , or a (pre-) configuration (process) .

In some embodiments, the conditions include at least one of a variation of a period of the event, a variation of a resource, a variation of a frequency, a variation of a phase, a variation of an amplitude, or a variation of a beam. In some embodiments, the event is persistent periodic, semi-persistent periodic, or aperiodic. In some embodiments, in a period of time, a total number of the event is (pre-) configured. In some embodiments, the event can be deferred. In some embodiments, the event is associated with a priority. In some embodiments, the second wireless communication entity is configured to perform measurements on all the information, but partially feedback the measurements.

While various arrangements of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand example features and functions of the present solution. Such persons would understand, however, that the solution is not restricted to the illustrated example architectures or configurations but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of some arrangements can be combined with one or more features of another arrangement described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative arrangements.

It is also understood that any reference to an element herein using a designation such as “first, ” “second, ” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.

Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

A person of ordinary skill in the art would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software module) , or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

Furthermore, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor but in the alternative, the processor can be any conventional processor controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this document, the term “module” as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according to arrangements of the present solution.

Additionally, memory or other storage, as well as communication components, may be employed in arrangements of the present solution. It will be appreciated that, for clarity purposes, the above description has described arrangements of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.

Claims

A wireless communication method, comprising:

sending, by a first wireless communication entity to a second wireless communication entity, a message to request at least one of: a sensing service, a capability, a measurement, or assistance data.
The wireless communication method of claim 1, wherein the first and second wireless communication entities each include a core network sensing services entity, a first core network entity, a second core network entity, or a device unit.
The wireless communication method of claim 2, wherein the first core network entity includes a Location Management Function (LMF) entity, and the second core network entity includes an Access and Mobility Management Function (AMF) entity.
The wireless communication method of claim 1, wherein the sensing service includes a Mobile Originated Sensing Request (MO-SR) .
The wireless communication method of claim 1, wherein the sensing service includes a Mobile Terminated Sensing Request (MT-SR) .
The wireless communication method of claim 1, wherein the sensing service includes a Network Induced Sensing Request (NI-SR) .
The wireless communication method of claim 1, wherein the message further comprises at least one of the following information corresponding to the capability, the measurement, or the assistance data: a velocity related parameter, a power related parameter, an angle related parameter, a distance related parameter, a resource related parameter, or one or more other parameter.
The wireless communication method of claim 7, wherein the information in the message is indicated as at least one of a value, a value range, a range list, a value list, a threshold, a threshold list, a variation, a variance, a change in value, a limit threshold of variation, a variation list, a variance list, or a change in value list.
The wireless communication method of claim 7, wherein the information in the message is indicated per path, a Line-Of-Sight (LOS) indicator, or a Non-Line-Of-Sight (NLOS) indicator.
The wireless communication method of claim 7, wherein the information in the message is indicated with a radial (velocity) and/or a non-radial (velocity) .
The wireless communication method of claim 7, wherein the information in the message is indicated horizontally and/or with vertically.
The wireless communication method of claim 7, wherein the information in the message is indicated as a non-preferred field, non-preferred area, or non-preferred range.
The wireless communication method of claim 7, wherein the information in the message is indicated as an expected field, expected area, or expected range.
A wireless communication method, comprising:

sending, by a first wireless communication entity to a second wireless communication entity, a message indicating at least one of: a sensing service, a capability, a measurement, or assistance data.
The wireless communication method of claim 14, wherein the first and second wireless communication entities each include a core network sensing services entity, a first core network entity, a second core network entity, or a device unit.
The wireless communication method of claim 15, wherein the first core network entity includes a Location Management Function (LMF) entity, and the second core network entity includes an Access and Mobility Management Function (AMF) entity.
The wireless communication method of claim 14, wherein the message further comprises at least one of the following information corresponding to the capability, the measurement, or the assistance data: a velocity related parameter, a power related parameter, an angle related parameter, a distance related parameter, a resource related parameter, or one or more other parameter.
The wireless communication method of claim 17, wherein the information in the message is indicated as at least one of a value, a value range, a range list, a value list, a threshold, a threshold list, a variation, a variance, a change in value, a limit threshold of variation, a variation list, a variance list, or a change in value list.
The wireless communication method of claim 17, wherein the information in the message is indicated per path, a Line-Of-Sight (LOS) indicator, or a Non-Line-Of-Sight (NLOS) indicator.
The wireless communication method of claim 17, wherein the information in the message is indicated with a radial (velocity) and/or a non-radial (velocity) .
The wireless communication method of claim 17, wherein the information in the message is indicated horizontally and/or vertically.
The wireless communication method of claim 17, wherein the information in the message is indicated as a non-preferred field, non-preferred area, or non-preferred range.
The wireless communication method of claim 17, wherein the information in the message is indicated as an expected field, expected area, or expected range.
A wireless communication method, comprising:

initiating, by a second wireless communication entity, an event triggered by one or more conditions;

wherein the one or more conditions include information in a message received by the second wireless communication entity, and wherein the event includes a request, a reporting (process) , a feedback (process) , a recommendation (process) , a measurement (process) , a (sensing) service, a replying (process) , or a (pre-) configuration (process) .
The wireless communication method of claim 24, wherein the conditions include at least one of a variation of a period of the event, a variation of a resource, a variation of a frequency, a variation of a phase, a variation of an amplitude, or a variation of a beam.
The wireless communication method of claim 24, wherein the event is persistent periodic, semi-persistent periodic, or aperiodic.
The wireless communication method of claim 24, wherein, in a period of time, a total number of the event is (pre-) configured.
The wireless communication method of claim 24, wherein the event can be deferred.
The wireless communication method of claim 24, wherein the event is associated with a priority.
The wireless communication method of claim 24, wherein the second wireless communication entity is configured to perform measurements on all the information, but partially feedback the measurements.
The wireless communication method of claim 24, wherein the conditions are related to at least one of: a velocity related parameter, a power related parameter, an angle related parameter, a distance related parameter, a resource related parameter, one or more other parameter, a value, a value range, a range list, a value list, a threshold, a threshold list, a variation, a variance, a change in value, a limit threshold of variation, a variation list, a variance list, a change in value list, a Line-Of-Sight (LOS) indicator, a Non-Line-Of-Sight (NLOS) indicator, a radial (velocity) , or a non-radial (velocity) .
The wireless communication method of claim 24, wherein the conditions are indicated horizontally and/or vertically.
A wireless communications apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement a method recited in any of claims 1 to 32.
A computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 32.