System and method for perceptual measurement and reporting

Abstract

The present configuration relates to systems, methods, and non-transitory computer-readable media for sending, by a first wireless communication entity, a message to a second wireless communication entity requesting at least one of awareness services, capabilities, measurements, or assistance data.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, and more specifically to sensing and communication. BACKGROUND

[0002] Some wireless communication systems can utilize integrated sensing and communication (ISAC) and corresponding enabling technologies to combine sensing systems and communication systems. SUMMARY

[0003] The example configurations disclosed herein are intended to address problems associated with one or more of the problems existing in the prior art and provide additional features that will become apparent to those of ordinary skill in the art upon reading the following detailed description in conjunction with the accompanying drawings. In accordance with various configurations, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these configurations exist in a manner of example and not limitation, and it will be apparent to those of ordinary skill in the art reading the present disclosure that various modifications to the disclosed configurations can be made while remaining within the scope of the present disclosure.

[0004] In some configurations, a message is transmitted. A first wireless communication entity can transmit a message to a second wireless communication entity. The first wireless communication entity can transmit the message to request at least one of a sensing service, capability, measurement, or assistance data.

[0005] The above and other aspects and implementations thereof are described in more detail in the drawings and specific embodiments and claims. BRIEF DESCRIPTION OF DRAWINGS

[0006] Various example configurations of the technical solutions of the present disclosure are described in detail below with reference to the following drawings. These drawings are provided only for illustrative purposes and only depict example configurations of the technical solutions of the present disclosure in order to facilitate the reader's understanding of the technical solutions of the present disclosure. Therefore, these drawings should not be regarded as limiting the breadth, scope, or applicability of the technical solutions of the present disclosure. It should be noted that, for the sake of clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0007] Figure 1 An example cellular communication system according to some configurations is shown.

[0008] Figure 2 Block diagrams of an example base station and an example user equipment according to some configurations are shown.

[0009] Figure 3 A diagram showing an example communication procedure for sensing measurement and reporting according to various configurations is shown.

[0010] Figures 4A to 4CFIG. 1 is a diagram illustrating an example communication process for perception measurement and reporting, in accordance with various configurations.

[0011] Figure 5 FIG. 2 is a diagram illustrating an example communication, in accordance with various configurations.

[0012] Figures 6A to 6I FIG. 3 is a diagram illustrating an example request process, in accordance with various configurations.

[0013] Figures 7A to 7B FIG. 4 is a diagram illustrating an example communication process, in accordance with various configurations.

[0014] Figures 8A to 8B FIG. 5 is a diagram illustrating an example communication process, in accordance with various configurations.

[0015] Figure 9 FIG. 6 is a diagram illustrating an example communication process, in accordance with various configurations.

[0016] Figure 10 FIG. 7 is a diagram illustrating an example event trigger, in accordance with various configurations.

[0017] Figure 11 FIG. 8 is a diagram illustrating an example reporting process, in accordance with various configurations.

[0018] Figure 12 FIG. 9 is a flow diagram illustrating an example method for perception measurement and reporting, in accordance with various configurations.

[0019] Figure 13 FIG. 10 is a flow diagram illustrating an example method for perception measurement and reporting, in accordance with various configurations.

[0020] Figure 14 FIG. 11 is a flow diagram illustrating an example method for perception measurement and reporting, in accordance with various configurations. DETAILED DESCRIPTION

[0021] Various example configurations of the present solution are described below with reference to the accompanying drawings, in order to enable a person having ordinary skill in the art to implement and use the present solution. Various changes or modifications to the examples described herein can be made by a person having ordinary skill in the art, after reading this disclosure, without departing from the scope of the present solution. Therefore, the present solution is not limited to the example configurations and applications described and illustrated herein. Moreover, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based on the description herein, a person having ordinary skill in the art can recognize that steps in the disclosed methods or processes can be re-ordered or added to, without departing from the scope of the present solution. Therefore, a person having ordinary skill in the art will understand that the methods and techniques disclosed herein are presented by way of example only, and that the present solution is not limited to the specific order or hierarchy presented.

[0022] Wireless communication systems can support integrated sensing and communication (ISAC). For example, a communication system and a sensing system can be integrated to use the same hardware and spectrum resources. Communication signals for sensing, target identification, classification, and detection can communicate by acquiring information such as angle of arrival, signal delay, Doppler shift, location, and velocity. ISAC can transform target positioning and tracking into parameter estimation. However, systems using ISAC can not support configurations of which signals, areas, and resources are available for sensing and communication; and / or processes of selecting, requesting, measuring, and reporting signals, areas, and resources. Furthermore, these systems can not support configurations on how to trigger signal transmission for sensing or communication. In some cases, optimization strategies related to ISAC can be insufficient. For example, a communication system can assist a sensing system, or a sensing system can assist a communication system.

[0023] Some ISAC systems can support various application scenarios, operating modes, and operating architectures. For example, for sensing services, operating modes can be divided into single-station A-to-A or double-station A-to-B. Node A and node B can be base stations or user equipment (UE). In some examples, six sensing types can be combined for single-station sensing. Furthermore, sensing services can be extended to a multi-station cooperative sensing structure. In some examples, positioning services can be similar to sensing services, which can serve as a reference for sensing services.

[0024] The configurations disclosed herein provide systems and methods that support a sensing function and a sensing measurement unit. For example, the sensing function can be a logical function of a core network (e.g., a sensing function (SF)), or an enhancement of an existing logical function (e.g., an enhanced location management function (LMF)). The sensing control function can be a functional module of a radio access network (RAN), such as an 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 a core network sensing service (SSS) entity, an AMF, a base station, a TRP, or a UE. In some cases, the sensing unit / network unit can be a base station, a TRP, or a UE. The network unit can be a core network, a 5G core network SSS entity, an AMF, an SF, an LMF, a base station, a TRP, or a UE. In some cases, the first wireless communication entity, the second wireless communication entity, the device unit, the core network sensing service entity, the first core network entity, the second core network entity can be a core network unit, a 5G core network SSS entity, an AMF, an SF, an LMF, a base station, a TRP, a UE, or other entity / unit.

[0025] Figure 1 An example wireless communication system 100 in which implementations according to the present disclosure can implement the techniques disclosed herein is shown. 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 referred to herein as system 100. Such an example system 100 includes BSs 102 and UEs 104, which can communicate with each other by way of a communication link 110, such as a wireless communication channel, and further includes a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. In Figure 1 In the example system 100, the BSs 102 and UEs 104 are within the respective geographic boundaries of the cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 can include at least one BS that operates on its assigned bandwidth to provide adequate wireless coverage for its intended users.

[0026] For example, the BS 102 can operate on an allocated channel transmission bandwidth to provide sufficient coverage to the UEs 104. The BS 102 and the UEs 104 can communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 can also be divided into subframes 120 / 127, which can include data symbols 122 / 128. In this disclosure, the BS 102 and the UEs 104 are described herein as “communication nodes” that can generally practice the methods disclosed herein as non-limiting examples. According to various implementations of the present solution, such communication nodes can communicate wirelessly and / or wired.

[0027] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) is shown in accordance with some implementations of the present solution. The system 200 can include components and elements configured to support known or conventional operational features not described in detail herein. In one example implementation, the system 200 can communicate (e.g., transmit and receive) data symbols in a wireless communication environment, such as the wireless communication environment 100 described above. Figure 1

[0028] The system 200 generally includes a BS 202 and a UE 204. The BS 202 includes a Base Station (BS) transceiver module 210 (hereinafter also referred to as: BS transceiver 210, transceiver 210), a BS antenna 212 (hereinafter also referred to as: antenna 212, antenna configuration 212), a BS processor module 214 (hereinafter also referred to as: processor module 214), a BS memory module 216 (hereinafter also referred to as: memory module 216), and a network communication module 218, each of which is coupled and interconnected to each other as needed via a data communication bus 220. The UE 204 includes a UE transceiver module 230 (hereinafter also referred to as: UE transceiver 230, transceiver 230), a UE antenna 232 (hereinafter also referred to as: antenna 232, antenna configuration 232), a UE memory module 234 (hereinafter also referred to as: memory module 234), and a UE processor module 236, each of which is coupled and interconnected to each other as needed via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250 (hereinafter also referred to as: wireless transmission link 250 and wireless data communication link 250), which can be any wireless channel or other medium suitable for data transmission described herein.

[0029] The system 200 can also include components and elements other than those shown in FIG. 2, such as a BS 202 and a UE 204, each of which can include one or more of the following components and elements: a BS processor module 214, a BS memory module 216, a BS transceiver module 210, a BS antenna 212, a network communication module 218, a UE processor module 236, a UE memory module 234, a UE transceiver module 230, a UE antenna 232, and a user interface module 238. Figure 2 ​Any number of modules other than those shown. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the implementations disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate the interchangeability and compatibility of the hardware, firmware, and software, various exemplary components, blocks, modules, circuits, and steps are described in general terms of the functionality of such hardware, firmware, and software. Whether this functionality is implemented as hardware, firmware, or software can depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art described herein can implement this functionality appropriately for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0030] According to some implementations, UE transceiver 230 may be referred to herein as an uplink transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some implementations, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the uplink receiver circuitry is coupled to the uplink antenna 232 so that transmissions on the radio transmission link 250 can be received while the downlink transmitter is coupled to the downlink antenna 212. In some implementations, there is tight time synchronization with a minimum protection time between changes in the duplex direction.

[0031] UE transceiver 230 and BS transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna configurations 212 / 232 that are appropriately configured to support specific wireless communication protocols and modulation schemes. In some exemplary implementations, UE transceiver 210 and BS transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G and 6G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0032] Depending on the implementation, BS 202 can be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some implementations, UE 204 can be various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 can be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, 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. Thus, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other combination of such configurations.

[0033] Furthermore, the methods described in conjunction with the implementations disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Memory modules 216 and 234 can be implemented as RAM (Random Access Memory), flash memory, ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, hard disks, removable disks, CD-ROMs (CompactDisc Read-Only Memory), or any other form of storage medium known in the art. In this respect, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some implementations, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions executed by processor modules 210 and 230, respectively.

[0034] Network communication module 218 typically represents the implementation of BS 202, BS transceiver 210, and other components configured to communicate with BS 202 for bidirectional communication between hardware, software, firmware, processing logic, and / or other network components and communication nodes. For example, network communication module 218 may be configured to support Internet or WiMAX services. In a typical deployment, but without limitation, network communication module 218 provides an 802.3 Ethernet interface, enabling BS transceiver 210 to communicate with conventional Ethernet-based computer networks. Thus, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and their variations, used herein in relation to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., which is physically constructed, programmed, formatted, and / or configured to perform a specified operation or function.

[0035] UE awareness architecture Figure 3 This is a diagram illustrating example communication procedures 300 for sensing measurement and reporting according to various configurations. Communication procedures 300 may include architectures and methods associated with sensing services. For example, communication procedures 300 may include various communications between UE 302, network node 304 (e.g., Next Generation Radio Access Network, NG-RAN), AMF 306, functional entity 308 (e.g., SF, LMF), and network entity 310 (e.g., fifth-generation core network (5GC) SSS entity, multiple entities). In some cases, sensing services may be offered as a vertical service similar to location services.

[0036] In some cases, UE 302, AMF 306, or network entity 310 may initiate a sense service request. For example, AMF 306 may send a sense service request to functional entity 308. Functional entity 308 may use non-access stratum (NAS) signaling to interact with network node 304 or UE 302 to generate a process. In response to these processes, a sense service response is provided to the requesting point.

[0037] At 312, network entity 310 (e.g., a gateway mobile location center (GMLC) or another entity in the 5GC) may request sensing / location services (e.g., sensing / location) for UE 302 (e.g., the target UE) from AMF 306 (e.g., the serving AMF). Alternatively, at 314, the serving AMF 306 for the target UE 302 may determine certain sensing / location service requirements (e.g., locating UE 302 for an emergency call). Alternatively, at 316, UE 302 may request sensing / location services (e.g., sensing / location or transmission of auxiliary data) from the serving AMF at the NAS layer. At 318, AMF 306 may transmit the sensing service request to functional entity 308.

[0038] At 320, functional entity 308 may initiate sensing / location procedures with serving (e.g., neighboring) base stations (e.g., ng-eNB, gNB) in a communication network (e.g., NG-RAN network). For example, functional entity 308 may initiate these procedures to obtain sensing / location measurements or auxiliary data. Alternatively, at 322, functional entity 308 may initiate sensing / location procedures with UE 302, for example, to obtain sensing / location estimation or sensing / location measurements, or to transmit sensing / location auxiliary data to UE 302.

[0039] At 324, functional entity 308 can provide a sensing / location service response to AMF 306, and the response can include various results (e.g., success or failure indication, location / sensing estimate of UE 302 (if requested and obtained)).

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

[0041] Awareness mechanisms Figures 4A to 4CThis diagram illustrates example communication procedures 400, 401, and 403 for sensing measurement and reporting according to various configurations. Communication procedures 400, 401, and 403 may include methods associated with sensing services. For example, communication procedures 400, 401, and 403 may include various communications between UE 402, network node 404 (e.g., NG-RAN), AMF 406, network entity 407 (e.g., GMLC), and functional entity 408 (e.g., SF, LMF).

[0042] Communication procedures 400, 401, and 403 can be associated with various sensing mechanisms. For example, sensing mechanisms may include Mobile Originated Sensing Request (MO-SR), Mobile Terminated Sensing Request (MT-SR), and Network Induced Sensing Request (NI-SR). For NI-SR or MT-SR sensing services, UE sensing-related services can be initiated from 5GC; or, in the case of MO-SR sensing services, UE sensing-related services can be initiated from UE 402.

[0043] exist Figure 4A The example illustrates the sequence of operations for NI-SR or MT-SR positioning services. The service can begin with AMF 406 initiating the service in functional entity 408. For example, at 410, AMF 406 may send a sensing / positioning request message to functional entity 408. At 412, UE 402, network node 404, AMF 406, and / or functional entity 408 perform one or more LTE positioning protocol (LPP) / other transactions. At 414, network node 404, AMF 406, and / or functional entity 408 perform one or more NR positioning protocol A (NRPPa) / other transactions. At 416, functional entity 408 may send a sensing / positioning response to AMF 406.

[0044] exist Figure 4BIn the example, an operational sequence for the MO-SR service can be illustrated. The service may begin when a client or user in UE 402 requests some sensing / location services (e.g., retrieving the target / UE 402 location or transmitting the target / UE 402 location to a third party). For example, at 418, UE 402 may send a request message to AMF 406 (e.g., MO-LR request, LPP protocol data unit (PDU)). AMF 406 may send a sensing / location request (e.g., LPP PDU) to functional entity 408. At 422, UE 402, network node 404, AMF 406, and / or functional entity 408 perform one or more LPP transactions. At 424, network node 404, AMF 406, and / or functional entity 408 perform one or more NRPPa transactions. At 426, functional entity 408 can send a sensing / location response to AMF 406. At 428, optionally, AMF 406 can transmit it to a fourth party. At 430, AMF 406 can send an MO-LR response to UE 402.

[0045] exist Figure 4C In the example, the sequence of operations for delayed MT-SR event reporting can be shown. The service can begin with UE 402 reporting an event to functional entity 408. For example, at 432, UE 402 can send an event report to functional entity 408. At 434, functional entity 408 can determine sensing / location (e.g., sensing / location requirements). At 436, UE 402, network node 404, AMF 406, and / or functional entity 408 perform one or more LPP transactions. At 438, network node 404, AMF 406, and / or functional entity 408 perform one or more NRPPa transactions. At 440, functional entity 408 can send an event notification to network entity 407. In some cases, Figures 4A to 4C The examples depicted can be associated with sidelink (SL) UE-aware architectures.

[0046] Awareness message exchange Figure 5This diagram illustrates an example communication 500. Communication 500 may include sensing message exchange 502. For example, sensing information may be exchanged between a receiving point and a sending point. Core network units (e.g., SF, LMF, AMF) may notify the sensing information exchange. For example, for better reception, core network units (e.g., SF, LMF) may exchange information from a sensing sender to a sensing receiver (e.g., A2B). Alternatively, to avoid reception interference, core network units (e.g., SF, LMF) may control or configure signal transmission between the sensing senders. That is, if sensing sender A1 transmits, other sensing senders may not transmit.

[0047] Awareness request Figures 6A to 6I The diagram illustrates example request procedures 600, 601, 603, 605, 607, 609, 611, 613, and 615 according to various configurations. Request procedures 600, 601, 603, 605, 607, 609, 611, 613, and 615 are methods associated with sensing services. For example, request procedures 600, 601, 603, 605, 607, 609, 611, 613, and 615 can include various types of sensing requests. The request procedure can be one of MO-SR, MT-SR, and / or NI-SR. In some cases, the sensing measurement unit / sensing control unit can send a request to the sensing control function. For example, the UE can send a sensing service request to the AMF, or the 5GC SSS entity can send a sensing service request to the AMF. The AMF can send the request to a functional entity (e.g., SF, LMF). Alternatively, the AMF can trigger the transmission of a request from the AMF to a functional entity.

[0048] exist Figure 6A In the example, request process 600 may include sensing request 602. In some cases, the request process includes sensing measurement. The sensing measurement unit can be configured using information from sensing request 602. For example, the sensing measurement unit may receive request 602. The sensing measurement unit may perform relevant measurements and report to the unit that sent request 602.

[0049] The perception request 602 may include at least one of the following information (values): • Velocity-related parameters: velocity / rate, Doppler, acceleration, micro-Doppler; • Power-related parameters: power, reference signal received power (RSRP), RSRP per path (RSRPPP), received signal strength indicator (RSSI), RSSI per path (RSSIP). • Angle-related parameters: Angle, Angle of arrival (AOA), Zenith of arrival (ZOA), Angle of departure (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 relationship, spatial filter); or Other parameters: phase, line of sight (LOS) / non-line of sight (NLOS), number of paths, radar cross section (material, size, angle).

[0050] In some cases, the information in Sensing Request 602 can improve the accuracy of the sensing target perceived by the sensing measurement unit, which may result in lower load and lower latency. Some interference and noise effects can be eliminated through this request information / parameters.

[0051] Alternatively, this information may be the value of at least one of these parameters, a range of values, a list of ranges, a list of values, a threshold / limit value, a list of threshold / limit values, a change, variance, value change, a threshold value for change (variance, value change), a list of changes, a list of variances, or a list of value changes. In some cases, these parameters may be used in conjunction with horizontal and / or vertical directions. For example, horizontal speed and / or vertical speed. In some cases, it may include requested location / awareness information with parameter accuracy, quality of service (QoS) (e.g., an accuracy information element (IE) indicating QoS and including a number of subfields). In the case of measurement, assuming the measurement result is the only source of error, and some subfields are applicable to location / awareness estimation, the server can obtain this location / awareness estimation from measurements provided by the sensing target / unit and / or the target device.

[0052] exist Figure 6B In the example, request process 601 may include perception request 604. This perception request may include a range of values. For example, a range of parameter values ​​may be used to request perception measurements and / or perception services.

[0053] Regarding the parameters related to speed 606: • Range of perceived speed / rate values: a. The range of perceived speed / rate values ​​is used to indicate the range of desired / interested target speed / rate.

[0054] b. This field (if present) indicates that speeds within this range should be measured for perception measurement / service.

[0055] • Range of perceived Doppler values: a. The range of perceived Doppler values ​​is used to indicate the desired / interested Doppler range.

[0056] b. This field (if present) indicates that Doppler measurements should be taken within this range for sensing measurements / services.

[0057] • Range of perceived acceleration / velocity values: a. The range of perceived acceleration values ​​is used to indicate the range of acceleration desired / of interest.

[0058] b. This field (if present) indicates that acceleration within this range should be measured for sensing measurements / services.

[0059] • Range of values ​​for perceived micro-Doppler: a. The range of perceived microDoppler values ​​is used to indicate the desired / interested microDoppler range.

[0060] b. This field (if present) indicates that micro-Doppler measurements should be taken within this range for sensing measurements / services.

[0061] Regarding the parameters related to the power 608: • Range of sensing power values: a. The range of perceived power values ​​is used to indicate the desired / interested power range.

[0062] b. This field (if present) indicates that power within this range should be measured for sensing measurement / service.

[0063] • The range of values ​​for the perceived RSRP: a. The perceived RSRP value range is used to indicate the expected / interested RSRP range.

[0064] b. This field (if present) indicates that RSRPs within this range should be measured for sense measurement / service.

[0065] • The range of values ​​for perceived RSRPP: a. The perceived range of RSRPP values ​​is used to indicate the range of RSRPPs expected / of interest.

[0066] b. This field (if present) indicates that RSRPPs within this range should be measured for sense measurement / service.

[0067] • Range of perceived RSSI values: a. The range of perceived RSSI values ​​is used to indicate the range of RSSI expected / of interest.

[0068] b. This field (if present) indicates that RSSI within this range should be measured for sensing measurement / service.

[0069] • Range of perceived RSSIP (RSSI per path) values: a. The perceived RSSIP value range is used to indicate the range of RSSIPs expected / interested in.

[0070] b. This field (if present) indicates that RSSIPs within this range should be measured for sense measurement / service.

[0071] For parameters related to angle 610: • Range of perceived angle values: a. The range of perceived angle values ​​is used to indicate the range of angles desired / of interest.

[0072] b. This field (if present) indicates that angles within this range should be measured for sensing measurements / services.

[0073] • The range of values ​​for perceived AOA (AOA, ZOA): a. The range of perceived AOA (AOA, ZOA) values ​​is used to indicate the range of AOA (AOA, ZOA) of interest.

[0074] b. This field (if present) indicates that AOA (AOA, ZOA) within this range should be measured for perception measurement / service.

[0075] • The range of perceived ZOA values: a. The perceived ZOA value range is used to indicate the expected / interested ZOA range.

[0076] b. This field (if present) indicates that ZOA measurements should be performed within this range for perception measurement / service.

[0077] • The range of perceived AOD (AOD, ZOD) values: a. The range of perceived AOD (AOD, ZOD) values ​​is used to indicate the range of desired / interested AOD (AOD, ZOD).

[0078] b. This field (if present) indicates that AOD (AOD, ZOD) within this range should be measured for perception measurement / service.

[0079] For parameters related to distance 612: • Range of perceived distance values: a. The range of values ​​for perceived distance is used to indicate the range of distances desired / of interest.

[0080] b. This field (if present) indicates that distances within this range should be measured for perception measurement / service.

[0081] • Range of perceived RTT values: a. The perceived RTT range is used to indicate the range of RTT expected / interested in.

[0082] b. This field (if present) indicates that RTT within this range should be measured for perceived measurement / service.

[0083] • Range of perceived delay values: a. The range of perceived delay values ​​is used to indicate the range of expected / interested delay.

[0084] b. This field (if present) indicates that latency within this range should be measured for perceived measurement / service.

[0085] • The range of values ​​for perceived RSTD: a. The perceived range of RSTD values ​​is used to indicate the range of RSTDs expected / of interest.

[0086] b. This field (if present) indicates that RSTDs within this range should be measured for sense measurement / service.

[0087] Regarding the parameters related to resource 614: • Range of perceived time values: a. The range of perceived time values ​​is used to indicate the expected / interested time range.

[0088] b. This field (if present) indicates the time range for which measurements should be taken for perceived measurement / service.

[0089] • Range of perceived frequencies: a. The range of perceived frequencies is used to indicate the range of frequencies desired / of interest.

[0090] b. This field (if present) indicates the frequency range that should be measured for perception measurement / service.

[0091] • Range of values ​​for sensing beam (spatial relationship, spatial filter): a. The range of values ​​for the perceived beam (spatial relation, spatial filter) is used to indicate the range of the desired / interested beam (spatial relation, spatial filter).

[0092] b. This field (if present) indicates that measurements should be taken of the beams (spatial relationships, spatial filters) within this range for sensing measurements / services.

[0093] For other parameter 616: • Range of perceived phase values: a. The range of perceived phase values ​​is used to indicate the desired / interested phase range.

[0094] b. This field (if present) indicates that the phase within this range should be measured for sensing measurement / service.

[0095] • Perceived LOS / NLOS value range: a. The perceived range of LOS / NLOS values ​​is used to indicate the expected / interested range of LOS / NLOS.

[0096] b. This field (if present) indicates that LOS / NLOS within this range should be measured for perception measurement / service.

[0097] c. For example, LOS / NLOS is defined in the range [0, 1]. A value of 0 indicates an NLOS channel, and a value of 1 indicates a LOS channel. If this field is set to the range [0.5, 1], the UE receiving the request information will perform measurement / sensing under the LOS / NLOS condition [0.5, 1].

[0098] • Range of values ​​for radar cross section (RCS): a. The range of perceived RCS values ​​is used to indicate the range of expected / interested RCS.

[0099] b. This field (if present) indicates that the RCS within this range should be measured for sensing measurement / service.

[0100] Furthermore, RCS can be reflected in the target's material, size, and / or angle: a. The range of values ​​for the target's perceived material.

[0101] i. The range of values ​​for the perceived material of the target is used to indicate the range of target material that is desired / of interest.

[0102] ii. This field (if present) indicates that the target material within this range should be measured for sensing measurement / service.

[0103] b. The range of values ​​for the perceived size of the target.

[0104] i. The range of values ​​for the perceived size of the target is used to indicate the range of target sizes expected / of interest.

[0105] ii. This field (if present) indicates that the target dimensions within this range should be measured for perception measurement / service.

[0106] c. The range of values ​​for the perceived angle of the target.

[0107] i. The range of values ​​for the perceived angle of the target is used to indicate the range of target angles that are desired / of interest.

[0108] ii. This field (if present) indicates that the target angle within this range should be measured for perception measurement / service.

[0109] exist Figure 6C In the example, request process 603 may include a sensing request 618. In some cases, sensing request 618 may be set per path and / or per LOS / NLOS indicator (e.g., the parameters of sensing request 618 may be set per path and / or per LOS / NLOS). For example, refer to Figures 6A to 6BThe described parameters include speed, power, angle, distance, resources, and others. For LOS channels, sensing services may have some advantages over NLOS channels, and the first path or the strongest power path can carry some sensing information that differs from other paths. Parameters for each path may be helpful for sensing measurements / services, and all parameters / information (e.g., speed, power, angle, distance, resources, and others) can be set per path and / or LOS / NLOS indicators.

[0110] Taking angle-related parameters as an example: • Range of perceived angle values ​​for each path: a. The range of perceived angle values ​​for each path is used to indicate the range of angles expected / of interest for each path.

[0111] b. This field (if present) indicates that the angle of each path within this range should be measured for perception measurement / service.

[0112] • Range of perceived AOA (AOA, ZOA) values ​​per path: a. The range of perceived AOA (AOA, ZOA) values ​​for each path is used to indicate the range of AOA (AOA, ZOA) for each path of interest.

[0113] b. This field (if present) indicates that AOA (AOA, ZOA) should be measured for each path within this range for use in perception measurement / service.

[0114] • Range of perceived ZOA values ​​per path: a. The range of perceived ZOA values ​​per path is used to indicate the range of ZOA expected / of interest per path.

[0115] b. This field (if present) indicates that ZOA should be measured for each path within this range for perception measurement / service.

[0116] • Range of values ​​for path-aware AOD (AOD, ZOD): a. The range of values ​​for per-path-aware AOD (AOD, ZOD) is used to indicate the range of AOD (AOD, ZOD) for each path of interest.

[0117] b. This field (if present) indicates that AOD (AOD, ZOD) should be measured for each path within this range for perception measurement / service.

[0118] exist Figure 6DIn the example, request process 605 may include perception request 620. In some cases, perception request 620 (e.g., parameters of perception request 620) may be set as a non-preferred field / region (range) (e.g., a perception field that is not desired / of interest). For example, parameters / information may include references Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters.

[0119] The information in the perception request 620, based on these parameters / information, enables the perception measurement unit to accurately perceive the target. This results in lower load and lower latency.

[0120] This is similar to non-preferred sensing measurement / service requests. Parameters with non-preferred indicators can also be helpful for sensing measurements / services. In some cases, parameters / information can be set as non-preferred field indicators.

[0121] Taking speed-related parameters as an example: • Range of non-optimal sensing speed values: a. The range of values ​​for non-preferred perceived speeds is used to indicate the range of speeds for targets that are not desired or of interest.

[0122] b. This field (if present) indicates that speeds within this range should not be measured for perception measurement / service.

[0123] Non-optimal sensing Doppler value range: a. The range of values ​​for non-preferred perceived Doppler is used to indicate the range of Doppler values ​​that are not desired or of interest.

[0124] b. This field (if present) indicates that Doppler measurements within this range should not be performed for sensing measurements / services.

[0125] • The range of values ​​for non-optimal sensing acceleration: a. The range of values ​​for non-preferred perceived acceleration is used to indicate the range of accelerations that are not desired or of interest.

[0126] b. This field (if present) indicates that acceleration within this range should not be measured for sensing measurements / services.

[0127] • Range of values ​​for non-optimal sensing micro-Doppler: a. The range of values ​​for non-preferred sensing micro-Doppler is used to indicate the range of micro-Dopplers that are not desired or of interest.

[0128] b. This field (if present) indicates that micro-Doppler measurements within this range should not be performed for sensing measurements / services.

[0129] exist Figure 6EIn the example, request process 607 may include perception request 622. In some cases, perception request 622 (e.g., parameters of perception request 622) may be set as a range / value list, which are expected / interested or unexpected / uninterested perception fields. For example, parameters / information may include references Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters.

[0130] For these parameters / information, the information in Sensing Request 622 with a range / value list enables the sensing measurement unit to have an accurate sensing target. This results in lower load and lower latency. Parameters with range / value list indicators can also be helpful for sensing measurement / service, and all parameters / information can be set as range / value list field indicators.

[0131] In some cases, range / value lists can operate in dedicated and / or collaborative states. For example, in collaborative mode, a region is configured based on two lists or two parameters within those lists, where the region is the intersection of the two parameters. For instance, one region might be given by a distance-related parameter, while the other is given by a velocity-related parameter.

[0132] In some cases, as a dedicated state operating mode, two regions are configured based on two lists or two parameters in the lists, and the first region may overlap with the other. For example, one region is given by distance-related parameters, while the other region is given by velocity-related parameters.

[0133] In some velocity-related cases, there can be two sets of configurations: Doppler and microDoppler, associated with different / same / related regions / granularities. For example, Doppler measurements can be configured for large regions / granularities, while microDoppler measurements can be taken for a small region / granularity.

[0134] exist Figure 6F In the example, request process 609 may include perception request 624. In some cases, perception request 624 (e.g., parameters of perception request 624) may be set as a threshold / limit value, a list of thresholds / limits, or a threshold value for a change (variance, value change), which may be expected / interesting or unexpected / uninteresting. For example, parameters / information may include references. Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters.

[0135] For these parameters / information, information in the perception request containing threshold / limit values ​​and threshold / limit value lists can enable the perception measurement unit to have accurate perception targets. This can result in lower load and lower latency. Parameters with threshold / limit values ​​and / or threshold / limit value list indicators can also be helpful for perception measurement / service, and all parameters / information can be set as threshold / limit values ​​and threshold / limit value list field indicators.

[0136] exist Figure 6G In the example, request process 611 may include perception request 626. In some cases, perception request 626 (e.g., parameters of perception request 626) may be set as a change, variance, value change, list of changes, list of variances, or list of value changes, which may be expected / interesting or unexpected / uninteresting. For example, parameters / information may include references. Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters.

[0137] For these parameters / information, information in the perception request containing variable amount, variance, value change, list of variable amount, list of variance, or list of value change can enable the perception measurement unit to have an accurate perception target. This can result in lower load and lower latency. Parameters with variable amount, variance, value change, list of variable amount, list of variance, or list of value change indicators can also be helpful for perception measurement / service, and all parameters / information can be set as variable amount, variance, value change, list of variable amount, list of variance, or list of value change field indicators.

[0138] exist Figure 6H In the example, request process 613 may include sensing request 628. In some cases, sensing request 628 (e.g., parameters of sensing request 628) may be set to radial parameters (e.g., velocity) and / or non-radial parameters (e.g., speed). For example, parameters / information may include references. Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters.

[0139] exist Figure 6I In the example, request process 615 may include sensing request 630. In some cases, sensing request 630 (e.g., parameters of sensing request 630) may be set as horizontal and / or vertical parameters. For example, parameters / information may include references. Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters.

[0140] Awareness capabilities Figures 7A to 7BThese are diagrams illustrating example communication processes 700 and 701 according to various configurations. Communication processes 700 and 701 may include a sensing unit 702 and a server 704. Figure 7A In the example, server 704 can send a request message 706 (e.g., requesting capability) to sensing unit 702. Server 704 can indicate the required capability type. Sensing unit 702 can respond to server 704 via message 708 (e.g., providing capability). These capabilities can correspond to any capability type specified in request message 706. Figure 7B In the example, a capability indication process can be shown. For instance, this process could allow sensing unit 702 to provide unrequested capabilities to server 704. Thus, sensing unit 702 could send message 710 (e.g., providing capabilities) to server 704.

[0141] In some cases, capability can be either a measurement capability or a perceptual capability. Parameters / information (e.g., reference) Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters can correspond to capabilities. This includes the value of at least one of these parameters, the range of values, a list of ranges, a list of values, a threshold / limit value, a list of threshold / limit values, the amount of variation, variance, value variation, a list of variations, a list of variance, or a list of value variations.

[0142] In some examples, velocity-related parameters can correspond to the capability of velocity-related measurements. For instance, the capability of micro-Doppler measurements. If a core network unit requests a micro-Doppler measurement, the core network unit can determine whether the measurement unit has the capability to perform micro-Doppler measurements. For example: • The core network unit (SF / LMF / AMF) requests the ability of the sensing unit (UE / gNB / TRP) to act as a sensing transmission point.

[0143] a. For example, the SF / AMF request serves as the gNB / TRP capability of a sensing transmission point.

[0144] • The core network unit (SF / LMF / AMF) requests the ability to act as a sensing unit (UE / gNB / TRP) as a sensing receiver point.

[0145] a. For example, SF / AMF requests the capability of gNB / TRP as a sensing receiver point.

[0146] • The sensing unit (UE / gNB / TRP) sends feedback on the sensing capabilities of the sensing unit (UE / gNB / TRP) to the SF / AMF.

[0147] a. For example, the UE responds to / reports / feeds back to the SF / AMF regarding its perception capabilities.

[0148] b. For example, UE A responds to / reports / feedbacks to SF / AMF regarding UE B's perception capabilities.

[0149] c. For example, the gNB / TRP responds to / reports / feeds back to the SF / AMF regarding the UE's sensing capabilities. If the gNB / TRP / UE has already been informed of / configured / reported the sensing capabilities of other gNB / TRP / UEs, it can provide feedback / respond / report these sensing capabilities.

[0150] Awareness assistance data Figures 8A to 8B This is a diagram illustrating example communication processes 800 and 801 according to various configurations. Communication processes 800 and 801 may include a sensing unit 802 and a server 804. Figure 8A In the example, sensing unit 802 may send a request message 806 (e.g., requesting auxiliary data) to server 804. Server 804 may respond to sensing unit 802 with a message 808 (e.g., providing auxiliary data), which includes the auxiliary data. The transmitted auxiliary data should match or be a subset of the auxiliary data requested by message 806. Server 804 may also provide sensing unit 802 with any non-requested information it deems useful. Server 804 may send one or more additional messages 810 (e.g., providing auxiliary data) to sensing unit 802 containing further auxiliary data. The transmitted auxiliary data should match or be a subset of the auxiliary data requested in step 1. Server 804 may also provide sensing unit 802 with any non-requested information it deems useful.

[0151] exist Figure 8B In the example, server 804 may send a message 812 containing auxiliary data (e.g., providing auxiliary data) to a target (e.g., sensing unit 802). Server 804 may send one or more additional messages 814 containing additional auxiliary data (e.g., providing auxiliary data) to the target.

[0152] In some cases, auxiliary data can correspond to parameters / information (e.g., combined with...) Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters. This includes the value of at least one of these parameters, the range of values, a list of ranges, a list of values, a threshold / limit value, a list of threshold / limit values, the amount of variation, the variance, the value change, a list of changes, a list of variance, or a list of value changes.

[0153] In some examples, velocity-related parameters can correspond to auxiliary data for velocity-related measurements. For instance, the capability of micro-Doppler measurements. If a core network unit requests a sensing service, the measurement unit can target a primary measurement for that sensing service based on this auxiliary data.

[0154] Awareness measurements Figure 9 This is a diagram illustrating an example communication process 900 according to various configurations. The communication process 900 may include a sensing unit 902 and a server 904. In some cases, the communication process 900 may include sensing measurements. These sensing measurements may correspond to parameters / information (e.g., combined with...). Figures 6A to 6B The described speed, power, angle, distance, resources, and other parameters. This includes the value of at least one of these parameters, the range of values, a list of ranges, a list of values, a threshold / limit value, a list of threshold / limit values, the amount of variation, the variance, the value change, a list of changes, a list of variances, or a list of value changes. In some cases, parameters may be used in conjunction with horizontal and / or vertical parameters (e.g., horizontal speed: integers (0 ... 2047), vertical speed: integers (0 ... 255)).

[0155] In some cases, based on measurements, sensing measurement units can have a wide range of sensing results, and multi-dimensional observations of measurements can provide more information about the sensing service. This allows for more accurate sensing and / or positioning services. These measurements are also useful in positioning services. For each measurement IE, it is associated with another quality IE (e.g., MeasQuantity), which includes QualityValues ​​and / or QualityResolution. A quality IE can include three sub-IEs (e.g., uncertainty, confidence, and resolution). For example, timing quality can include timingQualityValue (e.g., providing an estimate of the uncertainty of the timing value, where the IE NR-TimingQuality is provided in meters) and / or timingQualityResolution (e.g., providing the resolution for the timingQualityValue field, where enumerated values ​​mdot1, m1, m10, m30 correspond to 0.1, 1, 10, and 30 meters, respectively).

[0156] uncertaintyIE integers (0..127), uncertaintyIE integers (0..127), orientationIE (orientation IE) is an integer (0..179). confidence integer (0..100).

[0157] In some cases, parameters can be associated with horizontal and vertical parameters.

[0158] horizontalUncertaintyDoppler (horizontal uncertainty Doppler) integers (0..255), verticalUncertaintyDoppler (vertical uncertainty Doppler) integers (0..255).

[0159] In some cases, the parameters can be per perceived target, per perceived target group / list, or per UE / TRP.

[0160] In some cases, beam prediction can be used for velocity-based transmissions. This allows the sensing transmitter to send beams toward the sensing target in different directions at different times. For example, micro-Doppler measurements can be used to eliminate some interference and noise effects. Furthermore, this is useful for distinguishing targets or recognizing gestures. For instance, regular variations in micro-Doppler can be considered interference with command gesture recognition.

[0161] Measurements can also be the variances of these measurement parameters. For example, the variance of an RSRP measurement is the difference between two RSRP measurements. For a target, the RSRP variance contains information about the target's changes or its link information, which is useful for target tracking.

[0162] In some cases, sensing unit 902 and server 904 can exchange sensing measurement responses. For example, server 904 can send a request message 906 (e.g., requesting sensing information) to sensing unit 902. Sensing unit 902 can send a message 908 (e.g., providing sensing information) to server 904. Sensing unit 902 can send a message 910 (e.g., providing sensing information) to server 904. Requesting sensing information and / or providing sensing information may correspond to parameters / information (e.g., references). Figures 6A to 6B Describe the speed, power, angle, distance, resources, and other parameters. Include the value of at least one of these parameters, the range of values, a list of ranges, a list of values, a threshold / limit value, a list of threshold / limit values, the amount of variation, the variance, the value change, a list of changes, a list of variances, or a list of value changes. In some cases, parameters may be used in conjunction with horizontal and / or vertical parameters (e.g., horizontal speed: integers (0. . 2047), vertical speed: integers (0. . 255)).

[0163] Figure 10This is a diagram illustrating example event triggering 1000 according to various configurations. Event triggering 1000 may include one or more triggering conditions 1002, which may trigger one or more sensing events 1004 (e.g., for sensing). Event 1004 may be a request, report, response, feedback, recommendation, (pre)configuration, process (measurement), or sensing service.

[0164] In some examples, condition 1002 may originate from communication, and the triggered event 1004 may be associated with a sensing service. Conversely, condition 1002 may be a sensing event, and event 1004 may be associated with communication. For example, some events 1004 may be based on measurements from sensing units, or communication units may be used for sensing services.

[0165] In some cases, trigger condition 1002 can be (pre)configured by the network unit and sent to the sensing unit. Alternatively, trigger condition 1002 can be (pre)configured by the sensing unit. Trigger condition 1002 can be associated with at least one of the parameters / information (e.g., reference). Figures 6A to 6B (Described speed, power, angle, distance, resources, and other parameters). Alternatively, trigger condition 1002 can be a value, value range, range list, value list, threshold / limit value, threshold / limit value list, change, variance, value change, change (variance, value change) threshold value, change list, variance list, or value change list of at least one of these parameters.

[0166] In some examples, the change threshold of the LOS / NLOS indicator can be condition 1002 for triggering the awareness service. LOS / NLOS can be defined within the range [0, 1]. A value of 0 represents an NLOS channel, while a value of 1 represents a LOS channel. The change threshold is configured to 0.2. When the LOS / NLOS measured by the UE is between 0.3 and 0.6, the awareness service is triggered because the change of 0.3 is greater than the change threshold of 0.2.

[0167] In some examples, the change threshold of RSRP / speed can be a condition 1002 that triggers the sensing service. The roadside unit (RSU) can measure signals from the TRP. If, over a period of time, the change exceeds the configured change threshold, an event 1004 of the sensing service can be triggered.

[0168] In some examples that include a request, the request can also be an event trigger. For example, a sensing service request or a measurement request. A measurement can trigger the sensing service. This measurement is associated with one or more triggering conditions. Alternatively, the triggering condition can be a change in the (measurement) period, or a change in a resource. For example, the measurement period could change from 10 milliseconds (ms) to 5 milliseconds (ms). Events can trigger the sensing service to assist in the measurement. Changes in frequency, phase, amplitude, or beam can also serve as event triggering conditions.

[0169] Figure 11 This is a diagram illustrating an example reporting process 1100 according to various configurations. In some cases, the request, measurement, reporting (e.g., perception measurement report), response, and feedback / providing processes can have similar schemes to the reporting / reporting process.

[0170] Reporting process 1100 may include perception report 1102. Reporting process 1100 may be associated with one or more scenarios triggered by reporting, requesting, recommending, (pre)configuring, process, feedback, or event (e.g., requesting / reporting / feedback on perception services, measurements, UE capabilities, ancillary data, or processing the perception measurement).

[0171] In some cases, the reporting of this awareness report 1102 can be continuous periodic, semi-continuous periodic, or aperiodic. Transmission conditions may vary occasionally, frequently, or almost never. The report can be continuous periodic, semi-continuous periodic, or aperiodic. Measurement / request / awareness service triggers can be the same as the reporting. Continuous periodic, semi-continuous periodic, or aperiodic schemes for appropriate services / events / conditions can result in lower latency and / or lower load.

[0172] In some cases, reporting can be periodic or non-periodic. Reporting schemes can differ for different sensing services. For example, periodic reporting can reduce the load on request signals, while non-periodic reporting schemes can reduce feedback / reporting load. Furthermore, lower latency can be achieved.

[0173] In some cases, periodic reporting can be either continuous or semi-continuous. For periodic reporting, if transmission conditions hardly change, the reporting period can be continuous. If transmission conditions change occasionally, semi-continuous periodic reporting is more appropriate.

[0174] The total number of reports over a period of time can be (pre)configured. Multiple perceptions / measurements can exist within a given timeframe. Reporting all measurements would result in more duplicate information and a heavier workload. These measurements may be related over a period of time, with only one or n measurement results reported. These n measurement results can be reported together in a single report. Alternatively: • Only one report is generated within a certain period of time; • Within a certain time period, the sensing unit / network unit executes M reports, where M is an integer including zero; • A single measurement report should include at least one measurement result.

[0175] Based on this method, there may be little or no congestion during the reporting process.

[0176] Reports can be delayed. For example, a report on perceived service results can be issued some time after the perceived service results are obtained. Similarly, a report on measurement results can be issued some time after the measurement results are obtained.

[0177] In some cases, requests, measurements, reports (e.g., perception measurement reports), responses, and feedback / providing processes can be associated with priorities.

[0178] Reports can be associated with priorities. Requests, measurements, reports, and feedback / providing processes / content can also be associated with priorities. For example, if many perceptions / measurements are waiting to be reported, their priorities can be used to determine which perceptions / measurements should be reported or the order in which they should be reported. Based on this method, there can be little or no congestion during the reporting process.

[0179] Reports can be triggered by a single event / condition or a combination of events / conditions. For example, a power-related parameter might trigger a report. The UE is (pre-)configured with an RSRP threshold. If the measured RSRP value is greater than this threshold, a measurement event will be reported. As another example, power-related parameters and their changes might be configured to trigger reports. The UE is (pre-)configured with both an RSRP threshold and a change threshold. If the measured RSRP value is greater than the RSRP threshold and the change exceeds the change threshold, a measurement event will be reported.

[0180] A sensing unit can be configured to measure all information, but for different requests, it can feed back / report only the measurement / sensing / location results. For example, sensing service A may include a portion of an area of ​​another sensing service B. If sensing service B has already been completed, only the sensing results containing service A can be reported. As another example, a list of measurement results can be reported to the core network unit, but only some measurement results are reported.

[0181] Figure 12 This is a flowchart illustrating an example method 1200 for sensing measurement and reporting according to various configurations. In some cases, method 1200 may include a request message.

[0182] At 1202, the first wireless communication entity may send a message to the second wireless communication entity to request at least one of the following: sensing services, capabilities, measurement, or auxiliary data. In some embodiments, the first and second wireless communication entities include 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 MO-SR, MT-SR, NI-SR, or another type of sensing request.

[0183] In some embodiments, the message includes information corresponding to at least one of capability, measurement, or auxiliary data. For example, the information may include speed-related parameters, power-related parameters, angle-related parameters, distance-related parameters, resource-related parameters, or one or more other parameters. In some embodiments, the information in the message is indicated as at least one of the following: value, value range, range list, value list, threshold, threshold list, variation, variance, value change, variation threshold, variation list, variance list, or value change list. In some embodiments, the information in the message is indicated per path, per LOS indicator, or per NLOS indicator. In some embodiments, the information in the message is indicated as having radial (velocity) and / or non-radial (velocity). In some embodiments, the information is indicated in a horizontal and / or vertical direction. In some embodiments, the information is indicated as a non-preferred field, non-preferred region, or non-preferred range. In some embodiments, the information is indicated as a desired field, desired region, or desired range.

[0184] Figure 13 This is a flowchart illustrating an example method 1300 for sensing measurement and reporting according to various configurations. In some cases, method 1300 may include messages.

[0185] At 1302, the first wireless communication entity may send a message to the second wireless communication entity indicating at least one of the following: sensing services, capabilities, measurement, or auxiliary data. In some embodiments, the first and second wireless communication entities each include a core network sensing service 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.

[0186] In some embodiments, the message further includes at least one of the following information corresponding to capability, measurement, or auxiliary data: speed-related parameters, power-related parameters, angle-related parameters, distance-related parameters, resource-related parameters, or one or more other parameters. In some embodiments, the information in the message is indicated as at least one of the following: value, value range, range list, value list, threshold, threshold list, variation, variance, value change, variation threshold, variation list, variance list, or value change list. In some embodiments, the information in the message is indicated per path, per LOS indicator, or per NLOS indicator. In some embodiments, the information in the message is indicated as having radial (velocity) and / or non-radial (velocity). In some embodiments, the information in the message is indicated as in the horizontal and / or vertical direction. In some embodiments, the information in the message is indicated as a non-preferred field, non-preferred region, or non-preferred range. In some embodiments, the information in the message is indicated as a desired field, desired region, or desired range.

[0187] Figure 14 This is a flowchart illustrating an example method 1400 for sensing measurement and reporting according to various configurations. In some cases, method 1400 may include events.

[0188] At point 1402, the second wireless communication entity can initiate an event triggered by one or more conditions. These conditions may include information from messages received by the second wireless communication entity. Events may include requests, reports (processes), feedback (processes), recommendations (processes), measurements (processes), (sensing) services, responses (processes), or (pre)configurations (processes).

[0189] In some embodiments, the conditions include at least one of the following: changes in the period of the event, changes in resources, changes in frequency, changes in phase, changes in amplitude, or changes in beam. In some embodiments, the event is persistent periodic, semi-persistent periodic, or aperiodic. In some embodiments, the total number of events over a period of time is (pre)configured. In some embodiments, the event may be delayed. In some embodiments, the event is associated with a priority. In some embodiments, the second wireless communication entity is configured to perform all measurements on this information, but partially feedback the measurement results.

[0190] While various configurations of this solution have been described above, it should be understood that these implementations are presented as examples only and not as limitations. Similarly, various diagrams may depict example architectures or configurations to enable those skilled in the art to understand the example features and functionality of this solution. However, such individuals should understand that this solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art should understand, one or more features of one configuration can be combined with one or more features of another configuration described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the example configurations described above.

[0191] It should also be understood that any references to elements in this document using names such as "first," "second," etc., generally do not restrict the number or order of these elements. Rather, these names may simply be used as a convenient means of distinguishing two or more elements or multiple instances of an element. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0192] Furthermore, those skilled in the art will understand that various techniques and skills can be used to represent information and signals. For example, the data, instructions, commands, information, signals, bits, and symbols that may be mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0193] Those skilled in the art will also recognize that the various example logic blocks, modules, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, and various forms of program or design code containing instructions (which may be referred to herein as "software" or "software module" for convenience). To clearly illustrate the interchangeability of hardware, firmware, and software, the various exemplary components, blocks, modules, circuits, and steps described above are generally described in terms of their functionality. Whether such functionality is implemented in hardware, firmware, or software, or a combination thereof, depends on the specific application and design constraints on the overall system. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.

[0194] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by integrated circuits (ICs). Integrated circuits (ICs) can include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a DSP and microprocessors, multiple microprocessors, a combination of one or more microprocessors integrated with a DSP core, or any other suitable configuration performing the functions described herein.

[0195] If implemented in software, these functions can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media includes any medium capable of transferring a computer program or code from one location to another. Storage media can be any available medium accessible to a computer. For example, but not limited to, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can store the required program code in the form of instructions or data structures and is accessible to a computer.

[0196] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements used to perform the relevant functions described herein. Furthermore, for the purposes of discussion, individual modules are described as separate modules; however, it will be apparent to those skilled in the art that two or more modules can be combined to form a single module that performs the relevant functions configured according to this solution.

[0197] Furthermore, memory or other storage devices and communication components may be employed in the configuration of this solution. It should be understood that, for clarity, the above description has described the configuration of this solution by referring to different functional units and processors. However, it will be apparent that any suitable distribution of functionality among different functional units, processing logic elements, or domains can be used without compromising the solution. For example, a function shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing said functionality and do not indicate a strict logical or physical structure or organization.

[0198] Various modifications to the implementations described herein will be 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. Therefore, as stated in the following claims, the scope of this disclosure is not intended to be limited to the implementations shown herein, but rather to be the widest scope permitted by the novel features and principles disclosed herein.

Claims

1. A method of wireless communication, comprising: transmitting, 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.

2. The wireless communication method according to claim 1, wherein, the first and second wireless communication entities each comprise a core network sensing service entity, a first core network entity, a second core network entity, or a device unit.

3. The wireless communication method according to claim 2, wherein, the first core network entity comprises a location management function (LMF) entity and the second core network entity comprises an access and mobility management function (AMF) entity.

4. The wireless communication method according to claim 1, wherein, the sensing service comprises a mobile originated sensing request (MO-SR).

5. The wireless communication method according to claim 1, wherein, the sensing service comprises a mobile terminated sensing request (MT-SR).

6. The wireless communication method according to claim 1, wherein the sensing service comprises a network initiated sensing request (NI-SR).

7. The wireless communication method according to 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 speed related parameter, a power related parameter, an angle related parameter, a distance related parameter, a resource related parameter, or one or more other parameters.

8. The wireless communication method according to 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 value variation, a variation threshold, a variation list, a variance list, or a value variation list.

9. The wireless communication method according to claim 7, wherein, the information in the message is indicated as per path, per line of sight (LOS) indicator, or per non-line of sight (NLOS) indicator.

10. The wireless communication method according to claim 7, wherein the information in the message is indicated as having radial (speed) and / or non-radial (speed).

11. The wireless communication method according to claim 7, wherein the information in the message is indicated as in a horizontal direction and / or a vertical direction.

12. The wireless communication method according to claim 7, wherein, the information in the message is indicated as a non-preferred field, a non-preferred area, or a non-preferred range.

13. The wireless communication method according to claim 7, wherein, the information in the message is indicated as a desired field, a desired area, or a desired range.

14. A method of wireless communication, comprising: transmitting, 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.

15. The wireless communication method according to claim 14, wherein, the first and second wireless communication entities each comprise a core network sensing service entity, a first core network entity, a second core network entity, or a device unit.

16. The wireless communication method of claim 15, wherein, the first core network entity comprises a location management function entity (LMF) and the second core network entity comprises an access and mobility management function entity (AMF).

17. 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 speed related parameter, a power related parameter, an angle related parameter, a distance related parameter, a resource related parameter, or one or more other parameters.

18. 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 value variation, a variation threshold, a variation list, a variance list, or a value variation list.

19. The wireless communication method of claim 17, wherein, the information in the message is indicated as per path, per line of sight (LOS) indicator, or per non-line of sight (NLOS) indicator.

20. The wireless communication method of claim 17, wherein, The information in the message is indicated as radial (velocity) and / or non-radial (velocity).

21. The wireless communication method of claim 17, wherein, The information in the message is indicated as horizontal and / or vertical.

22. The wireless communication method of claim 17, wherein, The information in the message is indicated as non-preferred field, non-preferred area, or non-preferred range.

23. The wireless communication method of claim 17, wherein, The information in the message is indicated as desired field, desired area, or desired range.

24. A method of wireless communication, comprising: initiating, by a second wireless communication entity, an event triggered by one or more conditions; wherein the one or more conditions comprise information in a message received by the second wireless communication entity, and wherein the event comprises a request, a report (procedure), a feedback (procedure), a recommendation (procedure), a measurement (procedure), a (perception) service, a reply (procedure), or a (pre-)configuration (procedure).

25. The wireless communication method of claim 24, wherein, The conditions comprise at least one of a change in periodicity of the event, a change in resource, a change in frequency, a change in phase, a change in amplitude, or a change in beam.

26. The wireless communication method of claim 24, wherein, The event is persistent periodic, semi-persistent periodic, or aperiodic.

27. The wireless communication method of claim 24, wherein, A total number of the events over a period of time is (pre-)configured.

28. The wireless communication method of claim 24, wherein, The event can be delayed.

29. The wireless communication method of claim 24, wherein, The event is associated with a priority.

30. The wireless communication method of claim 24, wherein, The second wireless communication entity is configured to perform measurements on all of the information, but to feedback on the measurements partially.

31. The wireless communication method of claim 24, wherein, The conditions relate to at least one of a speed-related parameter, a power-related parameter, an angle-related parameter, a distance-related parameter, a resource-related parameter, one or more other parameters, a value, a range of values, a list of ranges, a list of values, a threshold value, a list of threshold values, a change amount, a variance, a change in value, a change amount threshold value, a list of change amounts, a list of variances, a list of changes in value, a line-of-sight (LOS) indicator, a non-line-of-sight (NLOS) indicator, a radial (velocity), or a non-radial (velocity).

32. The wireless communication method of claim 24, wherein, The conditions are indicated as horizontal and / or vertical.

33. A wireless communication device comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method of any of claims 1-32.

34. A computer program product comprising a computer readable program medium, code stored on the computer readable program medium, the code, when executed by a processor, causing the processor to implement the method of any of claims 1-32.

Images