Network node, method, sensing entity, terminal, and communication system

The network node system addresses the challenge of non-3GPP user sensing by enabling flexible data transfer and adaptive selection, improving sensing accuracy and reducing overhead in wireless sensing systems.

WO2026235093A1PCT designated stage Publication Date: 2026-11-12TOYOTA JIDOSHA KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/017131
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-04-30
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless sensing technologies face challenges in implementing suitable protocols for hierarchical processing of sensing data, particularly when the sensing target is a non-3GPP user, leading to insufficient sensing accuracy, increased communication overhead, and reduced quality of services.

Method used

A network node system is introduced with a receiving unit, control unit, and transmitting unit to manage sensing requests and responses, enabling flexible and adaptive data transfer based on Quality of Service (QoS) and network load, and supporting dynamic cooperative selection of NG-RAN and AMF nodes for non-3GPP users.

Benefits of technology

Enhances sensing accuracy and reduces communication overhead by allowing flexible data transfer and adaptive selection of sensing results, ensuring consistent and efficient wireless sensing for both 3GPP and non-3GPP users.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026017131_12112026_PF_FP_ABST
    Figure JP2026017131_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A third network node according to one aspect of the present disclosure has: a reception unit that receives sensing request information from a first network node or a second network node; a control unit that, on the basis of the sensing request information, selects a sensing entity for executing sensing; and a transmission unit that transmits, to the sensing entity via the second network node, a sensing measurement request for requesting sensing measurement data or a sensing measurement result based on the sensing measurement data. The reception unit receives, from the sensing entity via the second network node, a sensing measurement response transmitted in response to the sensing measurement request, the sensing measurement response including the sensing measurement data or the sensing measurement result. According to one aspect of the present disclosure, wireless sensing can be used appropriately.
Need to check novelty before this filing date? Find Prior Art

Description

Network node, method, sensing entity, terminal, and communication system

[0001] The present disclosure relates to a network node, a method, a sensing entity, a terminal, and a communication system.

[0002] In recent years, studies on wireless sensing technology using radio frequency signals have been progressing. For example, 5G wireless sensing that uses signals of the 5th generation mobile communication system New Radio (5G NR) in the 3rd Generation Partnership Project (3GPP (registered trademark)) (e.g., Non-Patent Document 1), and Wi-Fi sensing that uses signals of Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi (registered trademark)) are being studied.

[0003] In addition, Integrated Sensing and Communication (ISAC), which integrates communication functions and sensing functions, is under study.

[0004] Information related to object characteristics (such as shape, size, orientation, speed, position, distance between objects, or relative motion) may be acquired by wireless sensing.

[0005] 3GPP TS 22.137 V19.1.0 (2024-03), "3rd Generation Partnership Project; Technical Specification Group TSG SA; Service requirements for Integrated Sensing and Communication; Stage 1 (Release 19)"

[0006] As mentioned above, wireless sensing is being considered for 3GPP 5G NR. However, detailed protocols, signaling procedures, and signaling field designs that can suitably realize hierarchical processing of sensing data have not yet been thoroughly investigated. Furthermore, previous studies have found it difficult to handle cases where the sensing target is a non-3GPP user. If these issues are not properly addressed, wireless sensing cannot be implemented suitably, which may result in insufficient sensing accuracy (performance), increased communication overhead, and a decline in the quality of services provided by external application functions.

[0007] Therefore, one of the objectives of this disclosure is to provide network nodes, methods, sensing entities, terminals, and communication systems that can appropriately utilize wireless sensing.

[0008] A third network node according to one aspect of the present disclosure includes a receiving unit that receives sensing request information from a first network node or a second network node, a control unit that selects a sensing entity to perform sensing based on the sensing request information, and a transmitting unit that transmits a sensing measurement request to the sensing entity via the second network node to request sensing measurement data or sensing measurement results based on the sensing measurement data, wherein the receiving unit receives a sensing measurement response from the sensing entity via the second network node, which includes the sensing measurement data or sensing measurement results transmitted in response to the sensing measurement request.

[0009] According to one aspect of this disclosure, wireless sensing can be appropriately utilized.

[0010] Figure 1 is a diagram showing an example of a schematic configuration of a system according to one embodiment of the present disclosure. Figure 2 is a diagram showing an example of a schematic functional configuration of each device according to one embodiment of the present disclosure. Figure 3 is a diagram showing an example of a schematic hardware configuration of each device according to one embodiment of the present disclosure. Figure 4 is a diagram showing an example of the 5GC-MT-LR procedure for commercial location information services in the existing 3GPP standard. Figure 5 is a diagram showing an example of a protocol stack for communication between an LMF and an NG-RAN node. Figure 6 is a diagram showing an example of the NRPPa PDU transmission procedure for UE positioning between an LMF and an NG-RAN node. Figure 7 is a diagram showing an example of the NRPPa PDU transmission procedure for NG-RAN data acquisition between an LMF and an NG-RAN node. Figure 8 is a diagram showing an example of a sensing procedure according to one embodiment of the present disclosure. Figures 9A and 9B are diagrams showing examples of field-specified sensing measurement requests and sensing measurement responses in one embodiment of the present disclosure. Figures 10A and 10B show examples of signaling-separated sensing measurement result requests and sensing measurement result responses in one embodiment of the present disclosure. Figures 11A and 11B show examples of signaling-separated sensing measurement data requests and sensing measurement data responses in one embodiment of the present disclosure. Figures 12A and 12B show examples of sensing measurement requests and sensing measurement responses in one embodiment of the present disclosure where the base station determines the report content.

[0011] Embodiments of this disclosure will be described in detail below with reference to the drawings. In this specification and in the drawings, elements that can be similarly described are denoted by the same reference numerals, so that redundant explanations can be omitted.

[0012] In this disclosure, text enclosed in parentheses () may indicate an explanation of the preceding text (e.g., a spelling explanation), a paraphrase, a specific example, or supplementary information. Similarly, text enclosed in square brackets ([]) may be interpreted as part of the overall meaning of the text, or as excluding (ignoring) the brackets. Note that parentheses () and square brackets ([]) may also be used for other purposes / meanings.

[0013] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0014] In this disclosure, Network Function (NF) may include, for example, at least one of the following: • Application Function (AF): for example, a function that implements an application server outside the 5G Core Network (5GC); • Access and Mobility Management Function (AMF): for example, a function that manages UE registration, location, etc.; • Data Network (DN): for example, a function that implements a data network outside the 5GC; • Gateway Mobile Location Center (GMLC): for example, a function that serves as a window for Location Services (LCS) clients outside the 5GC to request UE location information, a function that provides an application interface for 5GC NF services to external parties; • Location Management Function (LMF): for example, a function that controls communication related to location information services; • Non-3GPP Inter-Working Function (N3IWF): For example, a function to connect 5GC with an untrusted non-3GPP access network. Network Exposure Function (NEF): For example, a function to provide the application interface of 5GC's NF services to the outside. Network Repository Function (NRF): For example, a function to register / provide information to enable the discovery of NFs (NF Producers) that provide NF services and NF services (by NFs (NF Consumers) that use NF services), notification of changes in the status of NF producers, etc. Network Slice Selection Function (NSSF): For example, a function to select a network slice.- Network Data Analytics Function (NWDAF): For example, a function to analyze network data. - Operation, Administration and Maintenance (Management) (OAM): For example, a function to provide means for maintenance and operation management. - Policy Control Function (PCF): For example, a function to control the quality and policies of data transfer paths. - Session Management Function (SMF): For example, a function to manage sessions. - Trusted Non-3GPP Gateway Function (TNGF): For example, a function to connect trusted non-3GPP access networks and 5GC. - Trusted WLAN Interworking Function (TWIF): For example, a function to connect trusted non-3GPP access networks and 5GC for non-5G compatible UEs via a wireless local area network (LAN). - Radio Access Network ((R)AN): For example, a function that provides a wireless access network. User Equipment (UE): For example, a function that allows users to access network services via a wireless interface. Unified Data Management (UDM): For example, a function that stores / manages subscriber information, UE authentication information, etc., performs user identification / access authorization based on this information, and manages the NF that provides services to the UE. Unified Data Repository (UDR): For example, a function that supports storing / reading subscriber information by UDM, storing / reading policy data by PCF, storing / reading application data by NEF, etc.- User Plane Function (UPF): For example, a function that transmits user data packets.

[0015] It should be noted that these are merely examples, and it is understood that other non-funding factors are also covered in this disclosure.

[0016] <System> Figure 1 is a diagram showing an example of a schematic configuration of a system according to one embodiment of the present disclosure. System 1 includes User Equipment (UE) 10, Base Station (BS) 20, Network Function (NF) server 30, and Application Server 40. System 1 may also be called a [wireless / information] communication system.

[0017] System 1 is, for example, a system that conforms to the 3GPP Technical Specification (TS). More specifically, for example, System 1 may be a system that conforms to the TS for 5th generation mobile communication system (5G) or New Radio (NR).

[0018] System 1 is not limited to this example and may include systems utilizing Long Term Evolution (LTE), LTE-Advanced (LTE-A), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), New Radio (NR), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these.

[0019] In other words, terms related to 5G in this disclosure can be interpreted as terms from another technology / system (e.g., 6G). Furthermore, in such cases, it will be obvious to those skilled in the art that, for example, NF can be interpreted as having a similar function (or a device having a similar function) to the NF of 5G.

[0020] In System 1, UE10 receives wireless communication services using Network (NW) 3000. NW3000 corresponds to the cellular network to which UE10 can connect.

[0021] In this disclosure, cellular network may be interpreted as mobile network, wireless communication network, 5G core network (5GC), 3GPP access network, etc. 5GC may include, for example, an optical fiber network. In this disclosure, 5GC, network, physical network, and core network (CN) may be interpreted as interchangeable.

[0022] UE10 connects to NW3000 via BS20. UE10 may be a mobile device (mobile communication terminal) such as a smartphone, tablet, or wearable device, or it may be a fixed communication terminal. UE10 may be a device mounted on a moving object (e.g., a vehicle), the moving object itself, or a device included in the moving object (held by a person riding in the moving object).

[0023] UE10 may utilize (or be equipped with) a Subscriber Identity Module (SIM) / Embedded SIM (eSIM) of an operator providing wireless communication services using NW3000. Furthermore, UE10 may switch connections to different operators' NW3000s by switching the Access Point Name (APN) configuration profile.

[0024] In System 1, the communication link going to (receiving) BS20 and going out of (transmitting) UE10 may be called the uplink (UL), and the communication link going out of (transmitting) BS20 and going to (receiving) UE10 may be called the downlink (DL).

[0025] BS20 provides a Radio Access Network (RAN) to UE10. An area on the Radio Access Network where wireless communication is possible is also called a cell. In this disclosure, BS, RAN [node], and Next Generation RAN (NG-RAN) [node] may be interpreted as mutually exclusive.

[0026] BS20 is, for example, a gNB. The gNB provides NR user plane and control plane protocol terminations towards the UE and is connected to 5GC via the NG interface. BS20 may also be an en-gNB. The en-gNB provides NR user plane and control plane protocol terminations towards the UE and operates as a secondary node in E-UTRA-NR Dual Connectivity (EN-DC).

[0027] UE10 / BS20 / NF Server 30 / Application Server 40 may have wireless sensing capabilities, for example, they may have a sensing transmitter / receiver. UE10 / BS20 may use the sensing transmitter / receiver to perform wireless sensing around its own terminal and acquire sensing data.

[0028] The UE10 / BS20 / NF server 30 / application server 40 may have devices (cameras, sensors, lasers, etc.) for sensing means other than wireless sensing (for example, image sensing, light detection and ranging (LiDAR)).

[0029] The sensing of UE10 / BS20 / NF Server 30 / Application Server 40 may be at least one of monostatic sensing, bistatic sensing, and multistatic sensing.

[0030] Monostatic sensing may be a type of sensing in which the system itself transmits a sensing signal (e.g., a specific reference signal) and receives an echo signal [from the object] to acquire sensing data. Bistatic sensing may be a type of sensing in which the system itself or a sensing transmitter of a cooperating UE10 / BS20 / NF server 30 / application server 40 transmits a signal, and a sensing receiver of the cooperating UE10 / BS20 / NF server 30 / application server 40 or the system itself receives the signal [affected by the object]. Multistatic sensing may be a type of sensing in which there are multiple sensing transmitters / multiple sensing receivers for an object.

[0031] The NF server 30 provides at least one of the functions of the NF described above. Figure 1 shows an NF server 30 providing AMF, an NF server 30 providing SMF, an NF server 30 providing UPF, and so on. In this disclosure, the NF server 30 and NF (e.g., AMF, NEF, NSSF, PCF, SMF, etc.) are interchangeable.

[0032] In this disclosure, NF may include a Sensing Function (SF) for managing, controlling, and analyzing sensing.

[0033] The application server 40 may correspond to the above-mentioned AF as defined for the 5G Core Network (5GC). In this disclosure, the application server 40, app, AF, etc., are interchangeable.

[0034] Furthermore, as shown in Figure 1, the application server 40 may be an external application server (external AF) belonging to a network outside the 5GC (which may also be called an untrusted AF located outside the operator's trust domain), and may communicate with the NF server 30 within the 5GC via the NEF. The application server 40 may also be an internal application server (internal AF) included within the 5GC (which may also be called a trusted AF located within the operator's trust domain), although this is not shown in the figure, and may communicate with the NF server 30 within the 5GC [without going through the NEF].

[0035] The application server 40 (e.g., an untrusted AF) may support the exchange of information by service providers other than telecommunications carriers to provide services related to UE 10 using communications, via an API that makes 5GC services (NF, especially control NF) accessible from the outside. Such exchange of information may include, for example, requesting and obtaining information about the location / state of UE 10, and specifying the quality of service (such as communication speed) for UE 10.

[0036] Any device shown in Figure 1 may also be called a network node (NW node), node, server, [wired / wireless] communication device, information processing device, etc. Furthermore, the lines between devices in Figure 1 indicate logical connections and do not necessarily have to be physically connected directly (they may be connected indirectly via another device).

[0037] <Configuration of Each Device> An example of the configuration of each device (UE10, BS20, NF Server 30, Application Server 40) according to the embodiments of this disclosure will be described below.

[0038] <<Functional Configuration>> Figure 2 is a diagram showing an example of the schematic functional configuration of each device according to one embodiment of the present disclosure. For example, UE10 includes a control unit 110, a communication unit 120, an input / output unit 130, and a storage unit 140.

[0039] Note that BS 20, NF server 30, and application server 40 may also have similar functional configurations. For this reason, in FIG. 2, as the reference numerals of the functional blocks corresponding to the respective apparatuses, numerals obtained by replacing the highest-order digit of the reference numeral indicating each apparatus (for example, for BS 20, the highest-order digit "2" of "20") with "1" are also shown. Hereinafter, the functional blocks related to UE 10 will be described, but it is understood that the same description applies to the other apparatuses.

[0040] In the present example, the functional blocks of the characteristic part in the present embodiment are mainly shown, and each apparatus may also have other functional blocks necessary for other processes. Further, a configuration that does not include some of the functional blocks may be adopted.

[0041] The control unit 110 performs control of the UE 10 and provides various functions. For example, the control unit 110 may control communication with other apparatuses via the communication unit 120. Further, the control unit 110 may acquire information necessary for processing on the basis of information received via the communication unit 120. The control unit 110 may also be referred to as a processing unit.

[0042] The communication unit 120 performs communication (transmission / reception) with other apparatuses via wired / wireless connection. The communication unit 120 may obtain information from a received signal and output the information to the control unit 110, or may convert information input from the control unit 110 into a signal and transmit the signal. The communication unit 120 may be configured as an integrated transceiving unit (a unit capable of both transmission and reception), or may be configured from separate transmitting unit and receiving unit.

[0043] The input / output unit 130 may include an input unit that receives an input by a human operation, or performs measurement (sensing) related to the surrounding environment to acquire information. The input unit may be connected to a predetermined device, a storage medium, or the like, and may receive an input of data. The input unit may output the input result to, for example, the control unit 110.

[0044] Further, the input / output unit 130 may include an output unit that outputs data, content, and the like in a form perceptible to a human. The output unit may be configured to include a display unit that displays an image, an audio output unit that outputs audio, and the like.

[0045] Any one or a combination of the communication unit 120 and the input / output unit 130 may function as a sensing transmitter / receiver. Sensing performed via the communication unit 120 may correspond to wireless sensing, and sensing performed via the input / output unit 130 may correspond to non-wireless sensing. The unit that performs sensing may be referred to as a sensing unit, a measurement unit, or the like. For example, the measurement unit may perform sensing using a sensing method described later, and acquire sensed data.

[0046] The storage unit 140 stores (holds) various types of information used by the UE 10 for processing. The control unit 110 may instruct reading and writing of data to and from the storage unit 140.

[0047] <<Hardware Configuration>> FIG. 3 is a diagram illustrating an example of a schematic hardware configuration of each apparatus according to an embodiment of the present disclosure. Each apparatus includes an antenna 910, a Radio Frequency (RF) circuit 920, a processor 930, a network interface 940, an input / output device 950, a memory 960, and a storage 970.

[0048] For example, the above-described control unit X10 (X=1, 2, 3, 4; the same applies hereinafter) may be implemented by the processor 930. The communication unit X20 may be implemented by the antenna 910 / the RF circuit 920 / the network interface 940. The input / output unit X30 may be implemented by the input / output device 950. The storage unit X40 may be implemented by the memory 960 / the storage 970.

[0049] Note that the hardware configuration of each apparatus may be configured to include one or a plurality of the elements illustrated in FIG. 3, or may be configured without some of the elements. For example, the UE 10 may not have the network interface 940.

[0050] Antenna 910 converts a signal into radio waves and radiates the radio waves into space. Antenna 910 also receives radio waves in space and converts the radio waves into signals. Multiple antennas 910 may be mounted, or they may include a transmitting antenna and a receiving antenna, or they may include a single antenna for transmitting and receiving. Antenna 910 may include a directional antenna, or it may include multiple antenna elements.

[0051] The RF circuit 920 performs analog processing on the signals transmitted and received via the antenna 910. The RF circuit 920 may include filters (e.g., high-frequency filters, low-pass filters), amplifiers, modulators, frequency synthesizers, analog-to-digital conversion circuits, digital-to-analog conversion circuits, Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT) processing circuits, and the like.

[0052] The RF circuit 920 may perform amplification, filtering, and demodulation to a baseband signal on the received radio frequency band signal and output it to the processor 930. The RF circuit 920 may also perform modulation to a radio frequency band, filtering, and amplification on the baseband signal input from the processor 930 and transmit the radio frequency band signal via the transmitting and receiving antenna 910. The RF circuit 920 may also perform physical layer processing (for example, processing of lower-level functions of the physical layer), and may perform beamforming processing such as analog beamforming and digital beamforming.

[0053] The processor 930 may control the entire device. The processor 930 may read programs (program code), software (software modules), data, etc., from the storage 970 into the memory 960 and perform various processes accordingly. For example, the processor 930 may execute an operating system (OS) program loaded into the memory 960 to perform control. The program may be transmitted from a network via a telecommunications line, for example, and may be provided to the device via an RF circuit 920 / network interface 940.

[0054] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement steps of the method described in the embodiments of this disclosure when the computer program is executed by a computer (for example, a processor 930).

[0055] The processor 930 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. The processor 930 may also include a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field-programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), and the like.

[0056] The processor 930 may perform digital processing of signals transmitted and received via the antenna 910 and the RF circuit 920. This digital processing may include processing at the physical layer (e.g., processing of higher-level functions of the physical layer), processing at layers above the Medium Access Control (MAC) layer, and processing such as modulation, demodulation, coding, decoding, and scrambling. The processor 930 also processes signals transmitted and received via the network interface 940.

[0057] The processor 930 may include multiple processors or it may be a single processor. The multiple processors may include a baseband processor that performs the digital processing and one or more processors that perform other processing (for example, overall control).

[0058] The network interface 940 may be, for example, a network adapter, which is connected to an external network via a wired connection and performs signal transmission and reception.

[0059] The RF circuit 920, processor 930, and network interface 940 may be configured as an integrated unit. The RF circuit 920, processor 930, and network interface 940 may also be referred to as a network controller, network card, communication module, etc.

[0060] The input / output device 950 includes input devices that accept input from the outside or acquire information about the surrounding environment (e.g., keyboard, mouse, microphone, switch, button, camera, sensor, etc.), output devices that perform output to the outside (e.g., display, speaker, Light Emitting Diode (LED) lamp, etc.), and devices that integrate these (e.g., touch panel). A locator for acquiring location information (e.g., a receiver compatible with Global Navigation Satellite System (GNSS)) may also be included as a sensor.

[0061] Memory 960 is a computer-readable non-temporary recording medium that stores programs executed by the processor 930, parameters related to those programs, and various other information. Memory 960 may include at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), (Electrically EPROM (EEPROM)), Random Access Memory (RAM), and flash memory. All or part of memory 960 may be contained within the processor 930. Memory 960 may also be called registers, cache, main memory, etc.

[0062] The storage 970 is a computer-readable non-temporary recording medium that stores various types of information. The storage 970 may include, for example, at least one of the following: a flexible disk, a floppy disk, an optical disk (e.g., Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray (registered trademark) disk), a magneto-optical disk, a removable disk, a hard disk drive (HDD), a smart card, or a flash memory device (e.g., a Solid State Drive (SSD)). The storage 970 may also be called an auxiliary storage device.

[0063] These recording media may be, for example, databases, servers, or other suitable media, including memory 960 / storage 970.

[0064] Furthermore, each device, such as the processor 930 and the memory 960, may be connected by a bus for communicating information. A single bus may be used within the device, or different buses may be used between the devices.

[0065] In this disclosure, the term “processor” may encompass a single processor or a group of processors, for example, a single-core processor, a multi-core processor, multiple processors in a single device, or multiple processors that can communicate with each other by wire or wireless means. Similarly, the term “computer-readable [non-temporary] recording medium” may encompass a single storage medium or a group of storage mediums, or multiple storage mediums that can communicate with each other by wire or wireless means.

[0066] The devices in this disclosure, such as processors and storage media, may be distributed locally or remotely, and may perform processing by operating cooperatively or independently using buses, networks, the internet, clouds, etc.

[0067] Furthermore, BS20 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). The RU implements RF processing and lower-level functions of the physical layer. The DU implements higher-level functions of the physical layer, MAC layer functions, and Radio Link Control (RLC) layer functions. The CU implements Packet Data Convergence Protocol (PDCP) layer, Service Data Adaptation Protocol (SDAP), and Radio Resource Control (RRC) layer functions.

[0068] In this disclosure, BS20 may include one device that implements all of the functions of RU, DU, and CU, or it may include multiple devices, each implementing some of the functions of RU, DU, and CU.

[0069] Furthermore, other devices in this disclosure may also be implemented by multiple devices that are physically separated from each other. Conversely, multiple different devices in this disclosure (for example, two or more of UE10, BS20, NF server 30, and application server 40) may be implemented as a single device.

[0070] Furthermore, all or part of the devices described herein may mean logical devices implemented by virtual machines, containers, Docker, etc., or physical devices that operate such logical devices.

[0071] <Location Information Services> The 5G system supports Location Services (LCS), which can identify and report the current location of a user entity (UE) in a standard format (e.g., geographic coordinates). This allows relevant information to be provided to users, mobile devices, network operators, service providers, value-added service providers, and operators within the PLMN.

[0072] LCS may provide means for determining the geographical location and / or speed of a UE based on measurements of radio signals. Clients associated with the UE (e.g., applications), within the core network, or connected to the core network can request location information. Positioning is performed by measuring radio signals received by the target UE, or by the access network acquiring radio signals transmitted by the target UE, and the location information is reported to the corresponding client.

[0073] Considering cases where the current location of a target UE is requested from an LCS client or AF inside or outside the PLMN, or from a control plane NF within the PLMN (e.g., NWDAF), Section 6.1.2 of the existing 3GPP TS 23.273 outlines the process for the 5GC-Mobile Terminated Location Request (5GC-MT-LR) location information service, as shown in Figure 4. Some steps of this procedure are outlined below.

[0074] An LCS client, NF, or AF issues a positioning request for location / velocity for a target UE via the (Home) Gateway Mobile Location Center ((H)GMLC) (Step 1). The target UE may be identified by a Generic Public Subscription Identifier (GPSI) or a Subscription Permanent Identifier (SUPI). The positioning request may include the required Quality of Service (QoS), supported Geographical Area Description (GAD) shapes, the scheduled location acquisition time (current time if omitted), and a service identifier (Service Identity (ID)). This request is first validated for authorization by the (H)GMLC (Steps 1a, 1c) or NEF (Step 1b). If authorization fails, the process terminates (i.e., steps 2-23 are skipped), and (H)GMLC or NEF returns an authorization failure response to the requester (LCS client, NF, or AF).

[0075] If the above authorization is successful, (H)GMLC calls the UDM's Nudm_SDM_Get service operation to retrieve the target UE's privacy settings (Step 2). If the privacy settings prohibit location access for the target UE, the process terminates and returns a response indicating that location access was denied.

[0076] According to the target UE's service network, the HGMLC, in the case of roaming, obtains the addresses of the Visited GMLC (VGLMC) and the target AMF from the UDM. If the privacy check passes, the HGMLC or VGLMC calls the AMF's Namf_Location_ProvidePositioningInfo service to request the current location of the target UE (steps 4, 5).

[0077] If the UE is in Connection Management (CM) - IDLE state, the AMF initiates a network-triggered Service Request procedure to establish a signaling connection (step 6).

[0078] If the privacy check requires user notification, the AMF sends a notification message to the target UE informing them of the source and type of service of the location request, and the user at the target UE must grant or deny location access within a limited time (step 8). If the user denies or does not respond, the AMF returns a location access denial result and the process ends.

[0079] If the user agrees, the AMF selects the appropriate LMF based on the configuration or available information and calls the Nlmf_Location_DeterminateLocation service to request the UE's current location (step 11). Network positioning is performed through the selected NG-RAN node, and the LMF returns the positioning results (location estimate, timestamp, accuracy, etc.) to the AMF (step 13), and the AMF returns the results to the HGMLC or VGMLC (step 14). Furthermore, if the target UE's users have configured different privacy settings for each geographical location, the HGMLC performs additional privacy checks (step 16).

[0080] Finally, the HGMLC returns a location service response to the requester and completes the positioning process (step 24).

[0081] <Control Plane and User Plane Protocol Stacks> 3GPP NR specifies that NG-RAN nodes are connected to the 5G core network via NG-C and NG-U interfaces, supporting the separation of the control plane and user plane. NG-C, the control plane interface, is defined between the NG-RAN node and the AMF and is primarily used for the forwarding of control signaling.

[0082] The transport network layer in the control plane's protocol stack is built on top of Internet Protocol (IP) transport and provides point-to-point transmission of signaling protocol data units (PDUs). Stream Control Transmission Protocol (SCPP) is applied on top of the IP layer, and the application layer utilizes Next Generation Application Protocol (NGAP) to ensure reliable transmission of application layer messages.

[0083] On the other hand, the user plane interface, NG-U, is defined between the NG-RAN node and the UPF and is used for the actual transfer of user data. The user plane's transport network layer is also built on top of IP transfer, with the General Packet Radio Service (GPRS) Tunneling Protocol for User Plane (GTP-U) applied over the User Datagram Protocol (UDP) / IP to enable unguaranteed transfer of user plane PDUs between the NG-RAN node and the UPF.

[0084] In LCS, the NR Positioning Protocol A (NRPPPa) protocol is used to transfer information between NG-RAN nodes and LMFs. Based on the routing ID corresponding to the relevant LMF node, the NG-RAN transfers the position measurement results to the LMF via the AMF through the NG-C interface of the control plane. In this process, the NRPPPa protocol is transparent to the AMF.

[0085] As shown in Figure 5, Section 6.5.1 of the existing 3GPP TS 38.305 describes a protocol that supports the transfer of NRPPa PDUs between LMF and NG-RAN nodes.

[0086] Furthermore, as shown in Figure 6, Section 6.5.2 of the existing 3GPP TS 38.305 describes the NRPPa PDU transfer procedure between the LMF and NG-RAN nodes to support the transfer of positioning data related to UE.

[0087] In this procedure, if the LMF needs to send an NRPPA message to the service NG-RAN node of the target UE, the LMF first calls the Namf_Communication_N1N2MessageTransfer service operation to request the AMF to transfer the NRPPA PDU to the service NG-RAN node of the UE (Step 1). This service operation includes the NRPPA PDU and the LCS-related ID in the N2 message container as defined in TS 29.518.

[0088] If the target UE is in the CM-IDLE state, the AMF first establishes a signaling connection with the UE and reassigns the service NG-RAN node (Step 2). Then, the AMF forwards the NRPPa PDU to the service NG-RAN node via the NGAP downlink and adds the routing ID associated with the LMF (Step 3).

[0089] If a service NG-RAN node needs to send an NRPPA message back to the target UE's LMF, it uses the NGAP uplink to send an NRPPA PDU to the AMF, and also sends the routing ID received from the AMF (Step 4).

[0090] The AMF invokes the Namf_Communication_N2InfoNotify service operation based on the routing ID and forwards the NRPPa PDU and LCS-related IDs to the LMF (Step 5).

[0091] This procedure is repeated as needed to support continuous positioning activities. This series of steps ensures that messages related to positioning services are smoothly transferred between multiple NFs, and that accurate routing and transfer of location data are ensured between AMFs and LMFs.

[0092] Furthermore, as shown in Figure 7, Section 6.5.3 of the existing 3GPP TS 38.305 describes the transfer procedure for NRPPa PDUs for NG-RAN data acquisition between LMFs and NG-RAN nodes. This may be used to support the transfer of positioning assistance information to all UEs supported by the NG-RAN node.

[0093] In this procedure, when the LMF needs to send an NRPPA message to an NG-RAN node for the purpose of obtaining relevant data and associated TP information of the NG-RAN node, it first calls the Namf_Communication_NonUeN2MessageTransfer service operation to the AMF and requests that it transfer the NRPPA PDU to the target NG-RAN node. This request includes the identifier of the target NG-RAN node, the NRPPA PDU, and the associated N2 message container (Step 1).

[0094] Upon receiving the above request, the AMF forwards the NRPPa PDU to the designated NG-RAN node using the NGAP protocol, and also adds a routing ID that points to the LMF (Step 2).

[0095] If an NG-RAN node needs to send relevant information back to the LMF after receiving an NRPPA message, the NG-RAN node sends an NRPPA PDU to the AMF using NGAP, attaching the previously received routing ID (Step 3).

[0096] Based on this information, the AMF calls the Namf_Communication_NonUeNInfoNotify service and forwards the NRPPa PDU to the LMF, allowing the LMF to receive the positioning information and configuration data it needs (Step 4).

[0097] This procedure may be used to ensure reliable cooperation and data exchange between LMF and NG-RAN nodes, and to support the smooth execution of positioning services. In this procedure, AMF acts as an intermediary, handling the transmission of routing information, while not maintaining the state of messages, thus guaranteeing processing flexibility and independence.

[0098] <Analysis> 3GPP is making progress in considering wireless sensing technology. For example, they are considering introducing a sensing function (SF) into the core network to perform sensing-related control, or transferring sensing data to the SF via base stations.

[0099] However, detailed protocols, signaling procedures, and signaling field designs that can suitably implement hierarchical processing of sensing data have not yet been thoroughly investigated. Furthermore, previous studies have found it difficult to address cases where the sensing target is a non-3GPP user. Unless these issues are properly defined, wireless sensing cannot be implemented suitably, which may result in insufficient sensing accuracy (performance), increased communication overhead, and a decline in the quality of services provided by external AFs.

[0100] Therefore, the inventors conceived of enabling flexible and situation-adaptive data transfer by allowing SF or NG-RAN nodes to select the type of sensing result data to transmit based on QoS and network load. According to one aspect of this disclosure, appropriate measurement data / measurement results can be reported using a control plane-based protocol PDU.

[0101] Furthermore, the inventors noted that existing technologies lack a means to guarantee that the AMF selected during sensing request processing is actually the service AMF of the NG-RAN node to be specified, and that consistency between the AMF and RAN cannot be maintained, especially in cases where the UE identifier for the sensing target is not included. Based on this, they conceived a standardized design for autonomous sensing processing that includes sensing targets with non-UE IDs. According to one aspect of this disclosure, dynamic cooperative selection processing of NG-RAN and AMF can be realized.

[0102] <Examples of Operation> Below, examples of the operation of each device / function according to the embodiments of this disclosure will be described. The communication methods (wireless communication methods, control methods) described below may be applied in the system 1 described above.

[0103] In the following descriptions of this disclosure, reference numerals may be omitted. For example, UE in the following descriptions may mean UE10.

[0104] In the following description, each device / function may be interpreted as one or more functional blocks (e.g., control unit 110, communication unit 120) or hardware configuration (e.g., RF circuit 920, processor 930) within the device / function.

[0105] In this disclosure, sensing, wireless sensing, and collaborative sensing (CS) may be interpreted interchangeably. CS may mean sensing that involves multiple BS / UEs performing overlapping area / time sensing (for example, sensing that calculates sensing results based on sensing data obtained from these sensings).

[0106] In this disclosure, SF may be interpreted as other NFs in the NW (e.g., NWDAF), or as SF / other NFs. One or more steps (processes) performed by one device / function in the following description may be interpreted as steps performed in a distributed manner by multiple devices / functions. For example, one of these devices / functions may perform part of the one or more steps, while the other performs the remainder of the one or more steps.

[0107] The following embodiments primarily focus on sensing processing by a base station when the sensing target is not a 3GPP subscriber, and further illustrate an example of a sensing procedure that takes into account situations where other 3GPP subscribers exist within the sensing area or may newly enter it. Note that the following embodiments are not limited to this situation and can also cover cases where the sensing target is a 3GPP subscriber, for example.

[0108] Figure 8 shows an example of a sensing procedure according to one embodiment of the present disclosure. In the sequence diagram of Figure 8, the sensing target is a non-UE sensing target, and the UE associated with the sensing target is also shown.

[0109] In this disclosure, the sensing target is the object to be detected and may also be called a sensing object. For example, the sensing target may be detected by deriving the properties of an object in the environment, which may be derived using a sensing signal (e.g., a sensing reference signal). The sensing target may also be detected by other means.

[0110] In this disclosure, the sensing target may be a UE (e.g., a 3GPP subscriber [or a UE of]) or a non-UE. In this disclosure, a 3GPP subscriber [or a UE of] may correspond to a device that has (or is assigned) a UE identifier (UE ID).

[0111] In this disclosure, non-UEs [as sensing targets] may include humans, objects (e.g., unmanned aerial vehicles (UAVs), automobiles, guided vehicles, objects posing a hazard on roads / railways), sensing areas, etc., or devices that do not have (or have not been assigned) a UE identifier (UE ID) (e.g., non-3GPP subscribers [of UEs]).

[0112] In this disclosure, the sensing area may mean at least one of the following: an area to be sensed, an area to be sensed, or an area where a sensing object may exist.

[0113] In this disclosure, a UE associated with (or linked to) a sensing object may, for example, be a UE that a non-UE (e.g., a human, a car) possesses (or is associated with / installed on, or is in the vicinity of) such non-UE.

[0114] Note that the interfaces shown in Figure 8 (service-based interfaces, such as Nsf) are examples only, and the names are not limited to these. Also, the service operation names shown in Figure 8 (e.g., Ngmlc_Sensing_ProvideSensing) are examples only, and the names are not limited to these. For example, Ngmlc_Sensing_ProvideSensing in Figure 8 may be interpreted interchangeably with service operations for sensing gateways (e.g., Nsg_Sensing_ProvideSensing).

[0115] Furthermore, in this disclosure, a protocol name (e.g., NR Sensing Protocol A (NRSPa)) may be written at the beginning of the signaling to indicate that it is a signaling for a specific protocol, but this protocol name may be omitted. Note that NRSPa may be an application layer protocol intended for the transfer of sensing measurement requests and measurement data / results. NRSPa may be implemented as an extension of NRPPa when SF operates as an extension of LMF.

[0116] The following describes in detail each step of the sensing procedure shown in Figure 8.

[0117] <<Step 1>> In Step 1, the AF / sensing client sends a sensing service request message to the sensing gateway and starts the sensing service processing.

[0118] A sensing client may also be called a sensing service client, and may be a UE, for example. The above AF / sensing client will also be referred to as a sensing requester below. A sensing gateway is an NF / device that serves as the window for sensing service requests, and may be a [H / V]GMLC, for example, or any NF.

[0119] A sensing requester may, for example, call the Ngmlc_Sensing_ProvideSensing service operation on the sensing gateway via the Ngmlc interface to request sensing results.

[0120] In this disclosure, "sensing results" may mean sensing measurement data / sensing measurement results. These will be described later. In this disclosure, "sensing measurement" may simply be expressed as "measurement." Also, in this disclosure, "sensing results" may be interpreted interchangeably with "sensing measurement results" and "information regarding sensing results."

[0121] In this disclosure, calling a service operation may include sending (or receiving) messages / information for input to that service operation, or receiving (or sending) messages / information for output to that service operation. For example, calling the Ngmlc_Sensing_ProvideSensing service operation may correspond to sending a sensing service request message.

[0122] Sensing service request messages may be sent via a Network Exposure Function (NEF). The NEF or sensing gateway may perform the authorization process for sensing services to the sensing requester.

[0123] The sensing gateway may function as the first node in the PLMN accessed by external clients. The address of the sensing gateway may be pre-configured in the sensing requester or obtained through a Domain Name System (DNS) lookup or a request to the NRF. This address may include an IP address, a fully qualified domain name (FQDN), or the like.

[0124] The sensing gateway can be deployed alongside the SF as a sub-functional module of the SF. Furthermore, considering that telecommunications operators may want existing network elements (LMFs) in their 5G architecture to be compatible with performing sensing tasks, the SF can be used as a functional extension of the LMF to meet this requirement.

[0125] The sensing service request message may include sensing request information to accommodate different sensing services.

[0126] The sensing request information may include one or more of the following: • Sensing target information, • Sensing service information, • Sensing mode information.

[0127] The sensing target information may include, for example, one or more pieces of information relating to the sensing target, such as: • UE identifier (UE ID) corresponding to the sensing target, • sensing area information, • application layer ID, and • descriptive information about the sensing target.

[0128] The UE ID may be any information used to identify the UE being sensed, and may include, for example, at least one of the following regarding the UE: • Generic Public Subscription Identifier (GPSI), • Subscription Permanent Identifier (SUPI), • NR Cell Global Identifier (NCGI), • NR Cell Identify (NCI) or cell identifier (Identifier (ID)), • gNB ID, • Internet Protocol (IP) address (e.g., Internet Protocol Version 4 (IPv4) address, Internet Protocol Version 6 (IPv6) address, IPv6 prefix), • MAC address, • External Group Identifier, • Internal Group Identifier, • Any other arbitrary identifier to identify the UE (e.g., UE ID), the UE's telephone number itself, or information related to the telephone number (e.g., Mobile Station International Subscriber Directory Number (MSISDN))).

[0129] Furthermore, if the UE ID is a different [proprietary / external] ID from the ID (under 5GS management) of the 3GPP domain (for example, GPSI), the UE ID may be converted to the ID of the 3GPP domain by the NEF or another NF (e.g., a sensing gateway). In this disclosure, UE ID may mean a UE ID that has been converted to a 3GPP internal ID by the NEF or another NF (e.g., a sensing gateway).

[0130] The sensing area may be identified by the UE ID, in which case the UE ID may be included in the sensing area information.

[0131] The sensing area information may include, for example, one or more pieces of information about the sensing area (the area to be sensed), such as: • Sensing area ID, • Coordinates of the sensing area (e.g., latitude / longitude / altitude), and • A 3D model of the sensing area (e.g., how the 3D model is defined).

[0132] The sensing area may be identified by a sensing area ID. The sensing area may be indicated by at least one of the following: a range of coordinates [from a reference point], a distance [from a reference point], a geographical area, a tracking area (TA), or it may be predefined in the SF.

[0133] Furthermore, if the sensing area information (e.g., sensing area ID) is different from the information (under 5GS management) of the 3GPP domain (which may be called 3GPP internal information, e.g., physical cell ID, TA, etc.) (which may be called proprietary / external information), the sensing area information may be converted to 3GPP domain information by the NEF or another NF (e.g., sensing gateway). In this disclosure, sensing area information [any information contained therein] may mean sensing area information [any information contained therein] that has been converted to 3GPP internal information by the NEF or another NF (e.g., sensing gateway).

[0134] The application layer ID may be an ID for the application layer of a UE and may be used to identify that UE. For example, a sensing gateway / any NF (e.g., (H)GMLC) may have mapping information between the application layer ID and the UE ID (e.g., GPSI). This mapping information allows the UE ID to be derived from the application layer ID. Furthermore, a sensing gateway / any NF (e.g., (H)GMLC) for one PLMN may request the sensing gateway / any NF (e.g., (H)GMLC) for a UE belonging to another PLMN to retrieve the above mapping information for that UE.

[0135] The descriptive information of the sensing object may include, for example, one or more pieces of information about the sensing object, such as: shape, position, movement route (path), and possibility of deviation from the above movement route.

[0136] In this disclosure, descriptions, details, features, characteristics, etc., may be interpreted interchangeably.

[0137] Of the above information, for example, the description information of the sensing target and the application layer ID may be used for authorization processing, base station selection, target determination, etc. Information such as sensing area information, travel route, and the possibility of deviation from said travel route may be used for authorization of the sensing area. The sensing service ID may be used to identify different sensing services.

[0138] If the sensing target or sensing requester is not a 3GPP subscriber, the sensing target information in the sensing request information does not have to include the UE ID, but may include at least one of the following: sensing area information, application layer ID, or description information of the sensing target.

[0139] If the sensing target or sensing requester is a UE, the request information may include the UE ID corresponding to the UE, or it may include sensing area information or the location / shape of the sensing target.

[0140] Sensing service information may include an identifier for identifying the sensing service (e.g., sensing service ID), service level QoS parameters required for the sensing service, etc. In this disclosure, service level QoS parameters, service level QoS parameters of a sensing service, original service level QoS parameters, primitive service level QoS parameters, service level QoS information, etc., may be interpreted interchangeably. A sensing service may be associated with a specific sensing method. A specific sensing method may include at least one of the following, for example, 3GPP sensing, non-3GPP sensing, etc.

[0141] 3GPP sensing may be sensing as defined in the 3GPP standard, or sensing that uses the wireless communication technology / frequency of the 3GPP standard. 3GPP sensing can detect the effects (reflection, refraction, diffraction, etc.) that a 3GPP wireless signal receives from a target object, environment, etc.

[0142] Non-3GPP sensing may be sensing defined outside of the 3GPP standard, and may be sensing using non-3GPP wireless communication technologies / frequencies such as Wi-Fi, or sensing using technologies other than wireless communication technologies. Non-3GPP sensing may include at least one of the following: Wi-Fi sensing, image sensing, light detection and ranging (LiDAR), cameras, radar, sonar, ultrasonic waves, infrared.

[0143] The service level QoS parameters required for sensing services may be closely related to the type of sensing service. Types of sensing services may include intrusion detection, rainfall monitoring, flood detection, vehicle control, navigation, detection / tracking within factories, drone flight path tracking, health monitoring, and positioning augmentation. These different use cases may each have different QoS requirements.

[0144] Service level QoS parameters may represent requirements related to the quality of sensing (i.e., quality conditions, requirements for realizing a specified sensing service). For example, service level QoS parameters may indicate at least one of the following: signal frequency / frequency band for sensing, allocation of radio resources (resource blocks, reference signals), estimated time for object detection, sensing delay, sensing accuracy, and acceptable false positive rate.

[0145] Service level QoS parameters may be controlled during the execution of a sensing service through a specific standardized template. Specifically, a list of QoS identifiers for each sensing service may be mapped to radio sensing QoS-related metrics in 3GPP. This QoS mapping process may be performed jointly by one or more network nodes, such as sensing gateways, NEFs, and SFs, by referring to a local QoS mapping policy identified by local configuration information, or by referring to a policy obtained from a PCF (which may be called a PCF policy, operator policy, etc.).

[0146] Sensing mode information indicates the mode of sensing (sensing mode). The sensing mode may indicate which entity transmits a signal (e.g., a sensing measurement signal) and which entity receives the signal for sensing. For example, the sensing mode may include a base station autonomous transmit / receive mode, a base station A transmits base station B receive (multiple base stations involved) mode, etc. The sensing mode information may also include information to identify at least one of the entity that transmits the signal and the entity that receives the signal.

[0147] Note that the base station spontaneous-sensing mode may be interpreted interchangeably with the TRP monostatic [sensing] mode. The base station A transmitting base station B receiving mode may be interpreted interchangeably with the TRP-TRP bistatic [sensing] mode.

[0148] <<Step 2>> In Step 2, the sensing gateway performs a privacy check (which may also be called a privacy verification) based on the received sensing request information. The sensing gateway, for example, based on sensing area information, calls the UDM's Nudm_SDM_Get service operation via the Nudm interface to obtain privacy information (e.g., sensing authorization information) about the sensing target (which may include non-3GPP subscribers). To support this process, the UDM must have the ability to hold the above privacy information about non-3GPP subscribers or area-based sensing targets.

[0149] If the privacy check determines that sensing is not permitted, the following steps (e.g., step 3-18) may be skipped. In this disclosure, the terms privacy check, authorization, authorization check, authorization confirmation, authorization determination, and authorization process may be interpreted interchangeably.

[0150] <<Step 3>> Step 3 may be performed if the sensing gateway and the SF are located separately (this may also be called a separate location or distributed location). In Step 3, the sensing gateway selects an SF based on the received sensing request information. Sensing area information / service level QoS information included in the sensing request information may be used for SF selection. The sensing gateway also transmits the above sensing request information to the selected SF.

[0151] If the sensing gateway and SF are deployed together (which may also be called an integrated deployment), the SF selection process is unnecessary, and step 3 may be omitted (in this case, the SF can be considered to have already been selected). In the case of an integrated deployment, the sensing gateway and SF may be the same device (they may be implemented in the same device), or they may be multiple devices integrated together. In the case of an integrated deployment, the sensing gateway and SF in each step of Figure 8 may be interpreted as each other.

[0152] This step is optional, and either step 3 or step 11 may be performed. If SF is not selected in step 3, step 11 is performed.

[0153] <<Step 4-5>> The SF / sensing gateway selects AMF.

[0154] If no SF is selected in step 3, the sensing gateway selects an AMF. For example, the sensing gateway requests an AMF assignment from the NRF based on the received sensing area information / service level QoS information (step 4). In response, the NRF returns a unique identifier for the AMF to be assigned (a globally unique AMF identifier (GUAMI)) (step 5). The sensing gateway may select an AMF corresponding to the GUAMI.

[0155] If an SF has already been selected in step 3, that SF selects an AMF. For example, the SF itself may request an AMF allocation from the NRF, and a GUAMI may be returned in the same way (step 4). The SF may then select an AMF corresponding to that GUAMI (step 5).

[0156] Alternatively, the SF / sensing gateway may select an AMF based on the GUAMI identified by the local configuration information, instead of requesting an AMF assignment from the NRF (Steps 4-5).

[0157] The SF / sensing gateway / NRF may be controlled to select an AMF capable of providing services to the sensing entity. This ensures that the selected AMF is a service AMF (an AMF that provides services) for the sensing entity, even if the UE ID is not present in the sensing request information.

[0158] In this disclosure, the sensing entity may mean a node that performs sensing or a node associated with sensing (e.g., a base station (NG-RAN node)). In this disclosure, the sensing entity, NG-RAN node, base station, etc., may be interpreted interchangeably.

[0159] For example, an SF / sensing gateway / NRF may pre-store location information / service area information of base stations and AMFs included in the service area of ​​the SF. In this disclosure, the service area may mean the area where the service is provided, and may include areas geographically distant from the area where the device is located, or areas geographically close to it. The service area of ​​a certain device may be interpreted as at least one of the areas where the device provides the service, the area where the device is located, etc.

[0160] Furthermore, in this disclosure, the inclusion of a device in an area may mean that the service area of ​​the device is included in that area.

[0161] The SF / sensing gateway / NRF may obtain (receive) the above location information / service area information from local configuration information or other NFs (e.g., AMF, NRF, UDR). The SF / sensing gateway / NRF may also obtain (receive) information from an NG-RAN node about AMFs that can provide services to that NG-RAN node. Based on the location information / service area information of each base station and each AMF within the SF's service area, and / or the information of AMFs that can provide services to each NG-RAN node, the SF / sensing gateway / NRF may select an AMF to provide services to a base station whose service area is included in the area indicated by the above sensing area information. This ensures that even if there is no information that can identify the base station (e.g., cell ID, RAN information), the base station selected in a later step (step 13) is within the service area of ​​that AMF.

[0162] <<Step 6>> The SF / sensing gateway may send sensing request information [including a message] to the selected AMF. The SF / sensing gateway may, for example, call the Namf_Sensing_ProvideSensingInfo service operation to the sensing gateway via the Namf interface to request sensing results.

[0163] If no SF is selected in step 3, the sensing gateway may send a message containing sensing request information to the selected AMF. If an SF is selected in step 3, the SF may send a message containing sensing request information to the selected AMF.

[0164] The sensing request information transmitted to the AMF may include the sensing request information received by the SF / sensing gateway from the sensing requester in step 1.

[0165] <<Step 7-9>> In certain cases, considering the possibility that a user may change their privacy settings within the sensing area, it is preferable for the AMF to perform a privacy check before the sensing operation. For this reason, step 7-9 may be performed in the above-mentioned specific cases. Such specific cases may be, for example, cases where the sensing target is not a UE (for example, it may be a person or an object) but is linked to a UE (for example, sensing for health monitoring, sensing-enhancing positioning, etc.).

[0166] The AMF may determine the UE associated with the sensing target based on local configuration information or information obtained from other NFs (e.g., SF, UDR).

[0167] In step 7, if the UE is in the CM-IDLE state, the AMF initiates a Network Triggered Service Request procedure based on 3GPP TS 23.502 4.2.3.3 to establish a signaling connection with the UE. This allows the network to signal to the UE via NG-RAN.

[0168] In step 8, the AMF may, if necessary, send a Sensing Notification Invoke Request to the UE to request information regarding privacy settings (e.g., information regarding changes to privacy settings). The Sensing Notification Invoke Request may be sent using Non-Access Stratum (NAS) signaling (e.g., a NAS Sensing Notification Invoke Request message).

[0169] In step 9, the UE may, if necessary, send a sensing notification return result to the AMF to return information about the privacy settings. The sensing notification return result may be sent using NAS signaling (e.g., the NAS Sensing Notification Return Result message).

[0170] Steps 7-9 may be skipped if the case does not fall under any of the specified categories (for example, if the sensing target is not associated with a UE, or if the sensing target is associated with a UE but the UE itself is the sensing requester).

[0171] <<Step 10>> The AMF performs a privacy check based on the latest privacy settings and operator policy regarding the sensing target and determines whether to continue with the subsequent sensing procedure. The latest privacy settings may be determined based on the privacy settings information received from the UE in Step 9, or obtained from the UDM.

[0172] The AMF may decide to continue with the following steps if privacy is permitted for the object being sensed (i.e., sensing is permitted), or it may skip the following steps (e.g., steps 11-16, 18) if privacy is not permitted (i.e., if it is denied).

[0173] The AMF may call the Nudm_ParameterProvision_Update service operation to save information about the updated privacy settings as privacy information in the UDM. The UDM may save the updated privacy information of the sensed object in the UDR.

[0174] <<Step 11>> If no SF is selected in Step 3, the AMF may select an SF based on the sensing request information received from the sensing gateway in Step 6 (Step 11). The AMF may request the NRF to allocate an SF based on the received sensing area information / service level QoS information, and the NRF may return a unique identifier for the selected SF, and the AMF may select an SF based on that unique identifier.

[0175] Alternatively, instead of requesting an SF allocation from the NRF, the AMF may select an SF based on the unique identifier of the SF identified by the local configuration information.

[0176] The AMF may pre-store location information / service area information for base stations and service fans (SFs). The AMF may obtain (receive) the above location information / service area information from local configuration information or other NFs (e.g., SFs, NRFs, UDRs). Based on the location information / service area information of each base station and each SF, the AMF may select SFs to provide service to base stations within its own service area. This ensures that even if there is no information that can identify a base station (e.g., cell ID, RAN information), the base station selected in a later step is within the AMF's service area.

[0177] Step 11 is performed exclusively with Step 3, and only one of them is selected.

[0178] <<Step 12>> If the selection of the SF is performed by the AMF in step 11, in step 12 the AMF sends sensing request information to the selected SF. In other words, in this case, the sensing request information is transferred from the sensing requester → sensing gateway → AMF → SF.

[0179] The AMF may, for example, call the Nsf_Sensing_DetermineSensing service operation on the SF via the Nsf interface to request sensing results.

[0180] The sensing request information transmitted to the AMF may include the sensing request information received by the AMF from the SF / sensing gateway in step 6.

[0181] If the selection of the SF is performed by the sensing gateway in step 3, the transmission of sensing request information in step 12 may be omitted. In other words, in this case, the sensing request information is transferred from the sensing requester to the sensing gateway to the SF.

[0182] <<Step 13>> In step 13, first, the SF selects a sensing mode / sensing entity based on the sensing request information received in step 1, 3, or 11.

[0183] The SF may select the sensing mode based on one or more of the following: - Sensing area information included in the sensing request information; - Service level QoS parameters included in the sensing request information; - Sensing mode information included in the sensing request information; - Network load status.

[0184] For example, the SF may select a sensing mode specified by the sensing mode information described above. Alternatively, the SF may select a sensing mode based on the sensing area information / service level QoS parameters and network load status information obtained from the base station / AMF.

[0185] In this disclosure, network load may include, for example, at least one of the following: base station load, core network load, AMF load, SF load, and link load [between UE and base stations]. Network load may also be indicated by the amount of available [radio] resources. Network load in this disclosure may also include network communication quality. SF or NG-RAN nodes may receive information regarding network load from UEs, base stations, arbitrary NFs, etc.

[0186] The SF may select sensing entities based on one or more of the following: • Sensing area information included in the sensing request information above; • Description information of the object to be sensed included in the sensing request information above; • Geographic location information of the sensing entity.

[0187] The service facilitator (SF) may pre-store location information / service area information for base stations and AMFs included in its service area. The SF may acquire (receive) the above location information / service area information from local configuration information or other NFs (e.g., AMF, NRF, UDR). Based on the location information / service area information of each base station and each AMF within its service area, the SF may select base stations included in the area indicated by the sensing area information.

[0188] For example, in cases where the sensing target is not a 3GPP subscriber, or where the sensing requester does not provide a UE ID when transmitting sensing request information, the AMF cannot provide the SF with a Cell ID associated with the UE. In these cases, cell ID-based base station selection by the SF becomes impossible. These cases can occur in certain sensing modes (e.g., base station self-receiving sensing mode). In these cases, the SF may autonomously select a base station, which is the sensing entity, based on the sensing area information / sensing target description information included in the sensing request information.

[0189] On the other hand, if sensing request information is transmitted from a UE, or if the sensing request information includes a UE ID, the AMF can provide the SF with the UE's current serving cell ID, details of the connected access network, etc. The SF may obtain its own service area and geographical location information of each base station in advance. The SF may request and obtain the above service area and geographical location information of each base station from other NFs (e.g., AMF, NRF, UDR), or it may obtain them based on local configuration information. The SF may obtain (receive) information from a sensing entity (e.g., an NG-RAN node) about which AMFs can provide services to that sensing entity. Based on this information, the SF may select a base station that is a sensing entity.

[0190] The SF may ensure that the sensing entity is within the service area of ​​the AMF selected in step 4-5 (it may perform an AMF integrity check). In other words, the SF may control the selection of sensing entities that are within the service area of ​​the selected AMF based on the above information. That is, the SF may select sensing entities that are included in both the area corresponding to the sensing area information and the service area of ​​the selected AMF.

[0191] If there are no sensing entities that are included in both the area corresponding to the sensing area information and the service area of ​​the selected AMF, the SF may, based on the NRF / local configuration information, obtain preferred AMF candidates (candidate AMFs that provide service to sensing entities whose service area is included in the area indicated by the sensing area information), select one of these AMF candidates as the new AMF, and repeat the process from step 6 using this as the AMF selected in step 4-5.

[0192] Furthermore, in step 13, the SF sends a Sensing Measurement Request (NRSPa Sensing Measurement Request) to the selected sensing entity to request a sensing measurement based on the selected sensing mode. For example, if a base station A transmitting base station B receiving sensing mode is selected, the SF may set sensing measurement signals to the selected base stations (base stations A / B) via the sensing measurement request to ensure synchronization of the sensing measurement signals between the base stations.

[0193] The SF invokes the Namf_Communication_NonUeN2MessageTransfer service operation on the AMF, requesting that the specified NG-RAN node send a protocol data unit (NRSPa PDU). The message contains the identifier of the target NG-RAN node and the NRSPa PDU encapsulated within an N2 message container.

[0194] Subsequently, the AMF uses the NGAP Downlink Non UE Associated NRSPa Transport message to forward the NRSPa PDU to the designated NG-RAN node and adds the SF's routing ID. This routing ID may be added by the NG-RAN node to the NRSPa Sensing Measurement Response (NRSPa Sensing Measurement Response) corresponding to the sensing measurement request, as described below, and used for signaling forwarding to the SF.

[0195] Details of the information fields (which may simply be called fields) of each signaling in the sensing measurement request and sensing measurement response will be described later.

[0196] <<Step 14>> In step 14, the NG-RAN node may perform sensing processing and generate / acquire corresponding sensing measurement data or sensing measurement results.

[0197] In this disclosure, sensing measurement data may refer to sensing data obtained directly by sensing, that is, raw data that has not undergone any processing, and may also be called sensing data. Raw data related to 3GPP sensing may, for example, be data representing the delay time of the reflected signal corresponding to the sensing signal, or data representing the phase difference corresponding to the direction from which the reflected signal is arriving. Raw data related to image sensing may, for example, be pixel data.

[0198] The sensing measurement results may correspond to intermediate results obtained by performing preliminary analysis / processing on the sensing data. In 3GPP sensing, the sensing measurement results may include, for example, the distance to the object, the direction in which the object is located, or information indicating at least one of the features extracted from the raw data (e.g., feature quantities, feature points, point clouds, etc.). In image sensing, the sensing measurement results may indicate, for example, what the object is (e.g., car, bicycle, pedestrian), or information indicating at least one of the features extracted from the raw data. When sensing measurement results are used, the sensing measurement data may be processed hierarchically in a node other than the NG-RAN node (e.g., SF, sensing requester).

[0199] In this disclosure, the sensing process may include one or more of the following: sensing measurement, generation / acquisition of sensing measurement data, and processing of sensing measurement data (generation / acquisition of sensing measurement results).

[0200] In this disclosure, a sensing entity that has received a sensing measurement request may transition to a state in which it executes a sensing task. An NG-RAN node executing a sensing task may continue to perform the instructed sensing (and send sensing measurement responses) until the sensing stop conditions are met.

[0201] The sensing stop conditions may include at least one of the following: being instructed to stop / modify / release / cancel this sensing (which may be called a sensing stop request); or a certain amount of time elapsed since receiving a sensing measurement request.

[0202] The SF or NG-RAN node itself may decide whether to generate / acquire / return sensing measurement data or sensing measurement results, based on sensing service level QoS parameters, network load status, etc. The SF or NG-RAN node may receive information regarding network load status from UE, base stations, any NF, etc.

[0203] For example, if an NG-RAN node determines that it has sufficient network resources, it may decide to pre-process the measurement data and return the processed measurement results. On the other hand, if an NG-RAN node determines that resources are limited, it may decide to return the unprocessed raw measurement data as is, or it may delegate the processing of the measurement data to the core network.

[0204] An NG-RAN node selected as a sensing entity may use broadcast information (e.g., system information) to notify other UEs entering the cell it forms that the sensing service is operational in the cell (or that the sensing service is being provided). If a UE receives this notification and its user's privacy settings do not allow sensing activity (i.e., do not allow privacy), the UE may report its privacy settings to the network.

[0205] The operator (or NG-RAN node) may perform a privacy check based on the reported privacy settings and operator policy to determine whether to continue with the subsequent sensing procedure.

[0206] The NG-RAN node may decide to continue processing if, for example, the number of UEs in a cell that do not tolerate privacy is less than a threshold (e.g., 1), otherwise (e.g., the number is greater than or equal to the threshold), the subsequent steps (e.g., step 18) may be skipped.

[0207] <<Step 15>> In Step 15, the NG-RAN node sends a Sensing Measurement Response (NRSPa Sensing Measurement Response) to report the sensing measurement data / measurement results to the SF.

[0208] The sensing measurement response may be included in the NRSPa PDU. When the sensing measurement response is sent to the SF using the NRSPa PDU, the NG-RAN node sends the PDU to the AMF via an NGAP Uplink Non UE Associated NRSPa Transport message, based on the sensing measurement request received previously. This message may include the routing ID of the SF obtained in step 13.

[0209] Based on the received routing ID, the AMF invokes the Namf_Communication_NonUeNInfoNotify service operation and forwards the NRSPa PDU in the N2 message container to the SF.

[0210] The NG-RAN node transmits the corresponding measurement result or data in the signaling field in response to the received sensing measurement request. If the sensing measurement request / sensing request information includes a UE ID, it is also possible to transmit the measurement data or result via the user plane.

[0211] If, as a result of the privacy check performed in step 14, the procedure is skipped (in other words, sensing results cannot be returned due to privacy reasons), then in step 15, the NG-RAN node may send a sensing measurement response [including a statement that sensing will not be performed (or sensing has been refused) [due to privacy reasons]] to the SF via the AMF instead of sensing measurement data / measurement results. The sensing measurement response [including a statement that sensing will not be performed (or sensing has been refused) [due to privacy reasons]] may also include information indicating the reason why sensing was not performed (cause of error).

[0212] <<Step 16>> If the SF selection was made by the AMF in Step 11, in Step 16 the SF sends the sensing measurement data / measurement results [including a response message] to the AMF. If not applicable, this step is skipped.

[0213] The SF may send the sensing measurement data / measurement result [including a response message] to the AMF as output to the Nlmf_Sensing_DetermineSensing service operation call in step 12.

[0214] If, as a result of the privacy check performed in step 14, the procedure is skipped (in other words, sensing results cannot be returned due to privacy reasons), then in step 16, the SF may send a [Response] message to the AMF stating that sensing will not be performed (or sensing has been refused) [due to privacy reasons] instead of sensing measurement data / measurement results. The [Response] message stating that sensing will not be performed (or sensing has been refused) [due to privacy reasons] may also include information indicating the reason (cause of error) why sensing was not performed.

[0215] <<Step 17>> If the SF selection was made by the AMF in Step 11, in Step 17 the AMF sends the sensing measurement data / measurement results [including a response message] to the sensing gateway. If not applicable, this step is skipped.

[0216] The AMF may send a [response] message containing sensing measurement data / measurement results to the SF / sensing gateway as output to the Namf_Sensing_ProvideSensingInfo service operation call in step 6.

[0217] Furthermore, if the procedure is skipped as a result of the privacy check performed in step 10 / 14 (in other words, if the sensing results cannot be returned due to privacy reasons), in step 17, the NG-RAN node may send a sensing measurement response to the SF [including a statement that sensing will not be performed (or sensing has been refused) [due to privacy reasons]] instead of sensing measurement data / measurement results. Furthermore, the sensing measurement response [including a statement that sensing will not be performed (or sensing has been refused) [due to privacy reasons]] may include information indicating the reason why sensing was not performed (cause of error).

[0218] <<Step 18>> If further verification is required during the privacy check in Step 2 (for example, if the sensing target has separate privacy settings in different areas), in Step 18, the sensing gateway performs another privacy check to determine whether it can send the sensing measurement data / measurement results to the sensing requester. If the second privacy check is approved (in other words, permission is granted to send the sensing measurement data / measurement results back), the sensing requester can obtain the sensing measurement data / measurement results in the next step 19.

[0219] Cases requiring a second privacy check include, for example, when the sensing target moves to an area where different privacy settings apply than those used in the privacy check in step 2. Note that the sensing target does not need to be notified whether a second privacy check is necessary.

[0220] If a further privacy check is not required, this step will be skipped.

[0221] If the results of the second privacy check are not approved (in other words, if the return of sensing measurement data / measurement results is not permitted, or if verification of the current location is required), at least part of steps 6 to 18 (for example, steps 6-10, 17) may be repeated.

[0222] <<Step 19>> In Step 19, the sensing gateway sends a sensing service response containing the received sensing measurement data or sensing measurement results to the sensing requester. This transmission may also be made via the NEF, completing the provision of the final sensing results.

[0223] The sensing gateway may send sensing measurement data / measurement results to the sensing requester as output to the call to the Ngmlc_Sensing_ProvideSensing service operation in step 1.

[0224] Furthermore, if a procedure is skipped as a result of a privacy check performed in steps 2, 10, 14, 18, etc. (in other words, if sensing results cannot be returned due to privacy reasons), in step 19, the sensing gateway may send a sensing service response to the sensing requester stating that sensing will not be performed (or sensing has been refused) [due to privacy reasons] instead of sensing measurement data / measurement results. The sensing service response [due to privacy reasons] [due to privacy reasons] may also include information indicating the reason why sensing was not performed (cause of error).

[0225] <<Signaling Design>> The following describes the details of the NRSPa protocol signaling to support the transmission of sensing measurement requests and the uplink transfer of sensing results mentioned above.

[0226] Furthermore, if SF operates as an extension of LMF, signaling for the NRSPa protocol may be implemented by designing an extension based on the NRPPa protocol.

[0227] Considering the hierarchical processing (step-by-step data processing) of sensing measurement data, the NG-RAN node (sensing entity) transmits either the sensing measurement data or the sensing measurement result to the SF. As mentioned above, the decision of whether to transmit the sensing measurement data or the sensing measurement result via the uplink rests with the SF or the NG-RAN node. The following describes the details of the signals suitable for each case.

[0228] The Sensing Measurement Request (described below) (which appeared in step 13 above) may be sent from the SF to a sensing entity such as an NG-RAN node selected by the SF, and may be used to explicitly instruct the execution of sensing operations, the type of information to be returned (measurement data / measurement results), etc.

[0229] The Sensing Measurement Response (described below) (which appeared in step 15 above) corresponds to the response signaling that works in conjunction with the Sensing Measurement Request, and may be transmitted by the NG-RAN node and used to report the sensing results.

[0230] Note that the same description may be used for information fields with the same name below. Information fields with the same name will not be described repeatedly.

[0231] <<<Cases where the SF determines the content of the report>>> When the SF determines what type of data to return (raw sensing measurement data or processed sensing measurement results) based on sensing request information / network load status, the NRSPa protocol signaling can be one of the following methods: - Field-specified type: A common signaling is used when requesting the return of measurement data from an NG-RAN node and when requesting the return of measurement results. This signaling includes a dedicated field that specifies the type of data (measurement data / measurement results) that the NG-RAN node should return. - Signaling-separated type: Different signaling is used when requesting the return of measurement data from an NG-RAN node and when requesting the return of measurement results. The NG-RAN node performs appropriate processing according to the received signaling and transmits the corresponding sensing result.

[0232] <<<<Field-Specific Type>>>> Figures 9A and 9B show an example of a field-specific sensing measurement request and sensing measurement response in one embodiment of the present disclosure. In this example, the names (information element / group names) of each field included in the signaling are shown (the same applies to subsequent drawings).

[0233] As shown in Figure 9A, a sensing measurement request in the field-specified type may include information fields for one or more of the following: message type, NRSPa transaction ID, SF measurement ID, sensing target information, measurement result / data transmission identifier, sensing measurement request item, sensing mode, and report characteristics.

[0234] The message type may indicate a summary of the message, such as an opening message, success result, or failure result.

[0235] The NRSPa transaction ID may be an ID used to uniquely identify the sensing measurement process and associate it with all associated signaling. The sensing measurement request and the corresponding sensing measurement response may contain the same NRSPa transaction ID.

[0236] The SF measurement ID may be an ID used in the SF to identify a sensing service or an individual measurement [request]. For example, the SF measurement ID may be associated with a sensing service and may be used to identify the corresponding sensing area information, application layer ID, description information of the sensing target, etc.

[0237] The information to be sensed and the sensing mode have already been explained. The sensing mode may be the sensing mode selected by the SF / sensing gateway, or it may be the sensing mode specified by the sensing requester.

[0238] The measurement result / data transmission identifier indicates the type of data (measurement result or measurement data) that the NG-RAN node should transmit (in other words, that the SF requires). In this disclosure, the measurement result / data transmission identifier may be interpreted as a measurement result / data [transfer] identifier, sensing result type, request type, [requested] sensing measurement type, report type, data type, etc.

[0239] A sensing measurement request item may specify one or more parameters related to the measurement, such as the format of the measurement results and accuracy requirements.

[0240] The reporting features may also indicate parameters related to reporting, such as the reporting method (e.g., event-triggered, periodic).

[0241] As shown in Figure 9B, the sensing measurement response in the field-specified type sends back the measurement result or measurement data corresponding to the measurement result / data transmission identifier specified in the sensing measurement request to the SF. The sensing measurement response may include information fields for one or more of the following: message type, NRSPa transaction ID, SF measurement ID, RAN measurement ID, sensing target information, sensing measurement result, and criticality diagnostics.

[0242] The RAN measurement ID may be an ID used to identify a sensing service or an individual measurement [request] in the RAN. For example, the RAN measurement ID may be associated with a sensing service and may be used to identify the corresponding sensing area information, application layer ID, description information of the sensing target, etc. The RAN measurement ID may also be associated with the SF measurement ID.

[0243] The sensing measurement results included in the sensing measurement response may be called sensing results, or they may be called measurement results or measurement data.

[0244] The severity diagnosis may include diagnostic information when unknown items, omissions, or logical inconsistencies are detected in the signaling.

[0245] When an NG-RAN node receives a sensing measurement request in which the measurement result / data transmission identifier indicates a measurement result, it may derive the sensing measurement result from the sensing measurement data and transmit a sensing measurement response that includes the said sensing measurement result.

[0246] When an NG-RAN node receives a sensing measurement request in which the measurement result / data transmission identifier indicates measurement data, it may send a sensing measurement response containing the sensing measurement data.

[0247] <<

[0248] Since the Sensing Measurement Result Request and Sensing Measurement Data Request are signaling that explicitly request either Sensing Measurement Result or Sensing Measurement Data, they do not need to include a Measurement Result / Data Transmission Identifier, unlike the Sensing Measurement Request described above.

[0249] In a signaling separation type, the sensing measurement response may be defined to include a sensing measurement results response for reporting measurement results and a sensing measurement data response for reporting measurement data.

[0250] Figures 10A and 10B show an example of a signaling-separated sensing measurement result request and sensing measurement result response in one embodiment of the present disclosure.

[0251] As shown in Figure 10A, a sensing measurement result request may include information fields for one or more of the following: message type, request type, NRSPa transaction ID, SF measurement ID, sensing target information, sensing measurement request item, sensing mode, and reporting features.

[0252] As shown in Figure 10B, the sensing measurement result response may include information fields for one or more of the following: message type, request type, NRSPa transaction ID, SF measurement ID, RAN measurement ID, sensing target information, sensing measurement result, and severity diagnosis.

[0253] The request type may indicate the type of sensing request handled by the NG-RAN node, for example, either a sensing measurement result request or a sensing measurement data request, or both. The request type included in the sensing measurement result response may indicate either a sensing measurement result request or a sensing measurement data request, or both, corresponding to the request, or it may indicate that this response is a sensing measurement result response among sensing measurement result responses and sensing measurement data responses. The request type included in the sensing measurement result response may also be called the response type.

[0254] The sensing measurement result included in the sensing measurement result response contains only the measurement result and does not include the measurement data.

[0255] Figures 11A and 11B show an example of a signaling-separated sensing measurement data request and sensing measurement data response in one embodiment of the present disclosure.

[0256] As shown in Figure 11A, a sensing measurement data request may include information fields for one or more of the following: message type, request type, NRSPa transaction ID, SF measurement ID, sensing target information, sensing measurement request item, sensing mode, and reporting features.

[0257] As shown in Figure 11B, the sensing measurement data response may include information fields for one or more of the following: message type, request type, NRSPa transaction ID, SF measurement ID, RAN measurement ID, sensing target information, sensing measurement data, and severity diagnosis.

[0258] The request type included in the sensing measurement data response may indicate either a sensing measurement result request or a sensing measurement data request, or both, or it may indicate that this response is a sensing measurement data response among sensing measurement result responses and sensing measurement data responses. The request type included in the sensing measurement data response may also be called the response type.

[0259] The sensing measurement data included in the sensing measurement data response contains only the measurement data, and does not include the measurement results.

[0260] When an NG-RAN node receives a sensing measurement result request, it may derive the sensing measurement result from the sensing measurement data and send a sensing measurement result response that includes the said sensing measurement result.

[0261] When an NG-RAN node receives a sensing measurement data request, it may send a sensing measurement data response containing the sensing measurement data.

[0262] A sensing measurement result request and a sensing measurement data request may correspond to different types of sensing measurement requests, and the NG-RAN node may decide whether to send a sensing measurement result response or a sensing measurement data response based on the type of sensing measurement result request and sensing measurement data request it has received.

[0263] In addition, a signaling-separated sensing measurement response (sensing measurement result response and sensing measurement data response) may be used for the field-specified sensing measurement request described above.

[0264] <<<Cases where the base station determines the report content>>> This section describes the sensing measurement request and sensing measurement response when an NG-RAN node determines what type of data to return (raw sensing measurement data or processed sensing measurement results) based on sensing request information / network load status.

[0265] Figures 12A and 12B show examples of sensing measurement requests and sensing measurement responses in one embodiment of the present disclosure, where the base station determines the content of the report.

[0266] As shown in Figure 12A, in cases where the base station determines the report content, the sensing measurement request may include information fields for one or more of the following: message type, NRSPa transaction ID, SF measurement ID, sensing target information, recommended sensing measurement type, sensing measurement request item, sensing mode, and reporting features.

[0267] The recommended sensing measurement type may indicate the type of sensing result (measurement result and / or measurement data) that the SF (Sensing Firmware) would like to acquire. In other words, the recommended sensing measurement type may correspond to information indicating which of the sensing measurement data and sensing measurement result the SF recommends. "Recommended" may be read interchangeably with "preferred."

[0268] An NG-RAN node may decide which type of data to return, taking into account the recommended sensing measurement type. For example, if the network load conditions allow for either a measurement result or measurement data to be returned, the NG-RAN node may decide to report whichever is specified in the recommended sensing measurement type.

[0269] Furthermore, if there is no particular recommended sensing measurement type (for example, either measurement results or measurement data is acceptable), both may be indicated as the recommended sensing measurement type, or the recommended sensing measurement type field may not be included in the sensing measurement request.

[0270] In cases where the base station determines the content of the report, the sensing measurement response sends the measurement result or measurement data back to the SF. As shown in Figure 12B, the sensing measurement response may include information fields for one or more of the following: message type, NRSPa transaction ID, SF measurement ID, RAN measurement ID, sensing target information, sensing measurement type, sensing measurement result, and severity diagnosis.

[0271] The sensing measurement type indicates the data type (measurement result or measurement data) of the sensing measurement result included in this sensing measurement response.

[0272] The sensing measurement results included in the sensing measurement response may be called sensing results, or they may be called measurement results or measurement data.

[0273] When an NG-RAN node receives a sensing measurement request and decides to return the sensing measurement result, it may derive the sensing measurement result from the sensing measurement data, indicate the sensing measurement result as the sensing measurement type, and send a sensing measurement response that includes the sensing measurement result.

[0274] When an NG-RAN node receives a sensing measurement request and decides to return sensing measurement data, it may send a sensing measurement response that includes sensing measurement data, with sensing measurement data as the sensing measurement type.

[0275] Furthermore, in cases where the base station determines the content of the report, the signaling-separated sensing measurement response (sensing measurement result response and sensing measurement data response) described above may be used instead of the sensing measurement response in Figure 12B. This is because the type of data to be reported (measurement result or measurement data) can be indicated by different signaling without using a sensing measurement type field.

[0276] Furthermore, the above sensing measurement response, sensing measurement result response, and sensing measurement data response may include fields indicating that sensing was not performed (or that sensing was rejected), or fields indicating the reason why sensing was not performed (or that sensing was rejected). If these fields are included, the sensing measurement result / measurement data fields do not need to be included (or may be empty).

[0277] <<Effects>> According to the sensing procedure described above, by using control plane signaling based on the NRSPa protocol (or the extended NRPPa protocol) for sending sensing measurement requests to sensing entities and returning sensing results from sensing entities, hierarchical processing of sensing data and selective transfer of measurement data or measurement results as sensing results can be achieved. This transfer method allows for flexible hierarchical processing of sensing processes, taking into account the network load of each layer, such as base stations and core networks, and enables stable transfer of sensing information that supports various scenarios (e.g., without UE ID).

[0278] When the sensing target is a non-3GPP user, the sensing request does not include a UE ID, making it difficult to apply existing UE-related signaling via the N2 interface or transfer mechanisms via the user plane. On the other hand, according to one aspect of this disclosure, by utilizing the NGAP protocol on the control plane of the N2 interface and transferring NRSPa / NRPPA protocol data units (NRSPA PDU / NRPPA PDU) encapsulated in an N2 information container through non-UE-related signaling, it is possible to return sensing information (sensing results) even in the absence of a UE ID.

[0279] Furthermore, according to one aspect of this disclosure, with respect to the hierarchical processing of sensing data, the SF or sensing entity can decide whether to return processed measurement results or unprocessed data.

[0280] <Supplement> In this disclosure, the first NW node and the sensing gateway may be interpreted as interchangeable. In this disclosure, the second NW node and the AMF may be interpreted as interchangeable. In this disclosure, the third NW node and the SF may be interpreted as interchangeable. In this disclosure, the fourth NW node and the UDM may be interpreted as interchangeable.

[0281] In this disclosure, the terms index, identifier (ID), identity (ID), indicator, and indication may be interpreted interchangeably.

[0282] <Notes> The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A third network node (e.g., SF) having: a receiving unit that receives sensing request information from a first network node (e.g., a sensing gateway) or a second network node (e.g., an AMF); a control unit that selects a sensing entity (e.g., an NG-RAN node) to perform sensing based on the sensing request information; and a transmitting unit that transmits a sensing measurement request to the sensing entity via the second network node to request sensing measurement data or sensing measurement results based on the sensing measurement data, wherein the receiving unit receives a sensing measurement response, including the sensing measurement data or the sensing measurement results, transmitted in response to the sensing measurement request, from the sensing entity via the second network node. [Note 2] The third network node according to Note 1, wherein the control unit selects the sensing entity based on sensing area information included in the sensing request information. [Note 3] The control unit is a third network node according to Note 1 or Note 2 that selects the sensing entity based on the sensing area information included in the sensing request information which does not include a user device identifier (e.g., UE ID). [Note 4] The control unit is a third network node according to any one of Notes 1 to 3 that selects the sensing entity which is located within the service area of ​​the second network node. [Note 5] The sensing measurement request is a third network node according to any one of Notes 1 to 4 that includes a field (e.g., a measurement result / data transmission identifier field) indicating whether the sensing entity should transmit the sensing measurement data or the sensing measurement result. [Note 6] The sensing measurement request is a third network node according to any one of Notes 1 to 5 which is a sensing measurement result request requesting the sensing measurement result or a sensing measurement data request requesting the sensing measurement data.[Note 7] The sensing measurement request is a third network node according to any one of Notes 1 to 6, which includes information indicating which of the sensing measurement data and the sensing measurement result is recommended by the third network node. [Note 8] The sensing measurement request is a third network node according to any one of Notes 1 to 7, which includes sensing mode information indicating which entity transmits a signal for the sensing and which entity receives the signal. [Note 9] The receiving unit is a third network node according to any one of Notes 1 to 8, which receives the sensing request information transmitted from the first network node that receives a sensing service request from a sensing requester. [Note 10] A third network node according to any one of Notes 1 to 9, selected by the first network node. [Note 11] The control unit is a third network node according to any one of Notes 1 to 10, which selects the second network node. [Note 12] The second network node is a third network node according to any one of Notes 1 to 11, selected by the first network node. [Note 13] A third network node as described in any of Notes 1 to 12, selected by the second network node. [Note 14] A method for a third network node, comprising: receiving sensing request information from a first network node or a second network node; selecting a sensing entity to perform sensing based on the sensing request information; transmitting a sensing measurement request to the sensing entity via the second network node to request sensing measurement data or sensing measurement results based on the sensing measurement data; and receiving a sensing measurement response from the sensing entity via the second network node, which includes the sensing measurement data or sensing measurement results transmitted in response to the sensing measurement request.[Note 15] A first network node comprising: a receiving unit that receives a sensing service request from a sensing requester; and a transmitting unit that transmits sensing request information to one of the second and third network nodes based on the sensing service request, wherein the receiving unit receives sensing measurement data or sensing measurement results based on the sensing measurement data transmitted from a sensing entity selected by the third network node based on the sensing request information via the one node, and the transmitting unit transmits a sensing service response including the sensing measurement data or the sensing measurement results to the sensing requester. [Note 16] A second network node having: a receiving unit that receives sensing request information from one of the first and third network nodes, and a receiving unit that receives a sensing measurement request from the third network node for requesting sensing measurement data or sensing measurement results based on the sensing measurement data, and a transmitting unit that transmits the sensing measurement request to a sensing entity selected by the third network node based on the sensing request information, wherein the receiving unit receives a sensing measurement response from the sensing entity, which includes the sensing measurement data or the sensing measurement results transmitted in response to the sensing measurement request, and the transmitting unit transmits the sensing measurement response to the third network node. [Note 17] A sensing entity having: a receiving unit that receives a sensing measurement request from a second network node for requesting sensing measurement data or sensing measurement results based on the sensing measurement data; a control unit that determines whether to respond with the sensing measurement data or generate and respond with the sensing measurement results based on the sensing measurement request; and a transmitting unit that transmits a sensing measurement response including the sensing measurement data or the sensing measurement results to the second network node.[Note 18] A terminal (e.g., UE) having: a receiving unit that receives a sensing notification call request (e.g., a notification to request information about privacy settings) from a second network node in a specific case (e.g., a case where the sensing target is not itself (the terminal) but is associated with itself); and a transmitting unit that, in response to the sensing notification call request, transmits to the second network node, using non-access layer (NAS) signaling, information [including] about privacy settings relating to itself or the sensing target associated with itself. [Note 19] A communication system having: a third network node as described in any of Notes 1 to 13; a first network node as described in Note 15; a second network node as described in Note 16; and a sensing entity as described in Note 17.

[0283] <Variations> Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings.

[0284] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable.

[0285] The information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or corresponding other information. For example, wireless resources may be indicated by a given index.

[0286] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those explicitly disclosed in this disclosure.

[0287] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0288] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0289] Any information described in this disclosure (e.g., variables, constants, parameters) may be notified from any first device (e.g., UE / BS) to any second device (e.g., BS / UE), even if not specifically stated in the embodiments described above. Notification of any information may be interpreted as notification of information indicating / specifying (or relating to) the value of such any information.

[0290] In this disclosure, the words “notify,” “request,” “activate,” “deactivate,” “indicate,” “select,” “configure,” “update,” and “determine” may be interpreted as interchangeable.

[0291] In this disclosure, the terms "support," "control / operate / use," and "control / operate / are available" may be interpreted as interchangeable.

[0292] In this disclosure, notification of information is not limited to the manner / embodiments described herein and may be carried out by other means. For example, notification of information in this disclosure may be carried out by radio access-related signaling, RAN-related signaling, core network-related signaling, other signals, or a combination thereof. In this disclosure, signaling, messages, parameters, fields, information elements (IEs), settings, etc., may be interpreted interchangeably.

[0293] Wireless access-related signaling may include signaling related to wireless access (wireless interface) between UE-RAN, and may also fall under Access Stratum (AS) signaling. Wireless access-related signaling may also include physical layer signaling, higher layer signaling, etc.

[0294] Physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI). Upper layer signaling may include, for example, Radio Resource Control (RRC) signaling and Medium Access Control (MAC) signaling.

[0295] RRC signaling may include broadcast information (e.g., Master Information Block (MIB), System Information Block (SIB)). MAC signaling may include MAC Control Element (MAC CE), MAC Protocol Data Unit (MAC PDU), etc.

[0296] RAN-related signaling may include signaling for control between RANs, such as Xn Application Protocol (XnAP) signaling.

[0297] Core network-related signaling may include signaling for control between UE and CN, such as Non-Access Stratum (NAS) signaling. Core network-related signaling may also include signaling for control between CN and CN, such as HyperText Transfer Protocol (HTTP) messages.

[0298] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0299] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0300] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0301] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "relay station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably.

[0302] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

[0303] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0304] Any device in this disclosure may also be called a server, device, transmitter, receiver, wireless communication device, information processing device, etc., and these terms may be interchangeable. Any device in this disclosure may be a device mounted on a moving object, a device contained within a moving object (held by a person riding in the moving object), or the moving object itself. Such moving objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items mounted on them. Such moving objects may also be autonomous / autonomous. In this disclosure, a moving object may also be interchangeable with a non-moving object (for example, a non-moving object that a person can ride in).

[0305] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. This disclosure also provides embodiments in which some / all of one embodiment is combined with some / all of another embodiment. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged or some steps may be omitted, as long as they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0306] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0307] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0308] In this disclosure, a radio resource may be defined as a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.

[0309] For example, a resource in the time domain (which may also be called a time resource) may be defined by one or more time units. These one or more time units may include, for example, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), and so on. Any time unit in this disclosure may be interpreted as being interchangeable with another time unit.

[0310] For example, a resource in the frequency domain (which may also be called a frequency resource) may be defined by one or more frequency units. These one or more frequency units may include, for example, a subcarrier, a resource block (RB), a bandwidth part (BWP), a carrier bandwidth, and so on. Any frequency unit in this disclosure may be interpreted as being interchangeable with another frequency unit.

[0311] Furthermore, resources in both the time domain and the frequency domain (time / frequency resources) may be defined, for example, by one or more time / frequency units composed of time units and frequency units. Such one or more time / frequency units may include, for example, resource elements (RE), resource element groups (REG), control resource sets (CORESET), and so on.

[0312] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. The coupling or connection between elements may be via at least one of wired and wireless connections.

[0313] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0314] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0315] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0316] In this disclosure, the words "decide," "determine," "judge," "select," "specify," "compute," "calculate," "process," "derive," "look up / search / inquiry," "confirm," "assume," "expect," and "consider" may be interpreted interchangeably. Also, in this disclosure, performing a certain process (e.g., sending, receiving) may be interpreted interchangeably with deciding to perform that process. Furthermore, in this disclosure, "do not assume that..." may be interpreted interchangeably with "assume that..."

[0317] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0318] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0319] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0320] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0321] In this disclosure, "X's number," "X number," "the number of X(s)," and "a number of X(s)" may be interpreted as interchangeable. Herein, X may be replaced with a noun, gerund, or ordinary sentence as appropriate, depending on the context. In this disclosure, "number" may be interpreted as maximum number, minimum number, average number, total number, etc. Furthermore, in this disclosure, terms related to "value," "index," "number," and "quantity" may be interpreted as interchangeable.

[0322] Values / ranges in this disclosure may be interpreted as approximations, as if preceded by the words “about” or “near.” In this disclosure, “[A and B] [are] the same” (where A and B are any words) may mean “[A and B] [are] identical,” “[A and B] [are] almost the same,” “[A and B] [are] partly the same (or [partly] overlapped),” or “[There is] an error within a certain range [between A and B]” (i.e., these words may be interpreted as interchangeable). Furthermore, in this disclosure, "A and B are the same" may mean that at least part of A and at least part of B are the same (or overlapped).

[0323] In this disclosure, “one embodiment,” “several embodiments,” and “another embodiment” may be used interchangeably. In this disclosure, the terms “one embodiment,” “several embodiments,” and “another embodiment” do not necessarily all refer to the same embodiment, nor do they necessarily mean that they are mutually exclusive.

[0324] In this disclosure, expressions such as “at least one of A and B,” “at least one of A or B,” “A and / or B,” and “A / B” may be interpreted as including “only A,” “only B,” or “both A and B.” Furthermore, in this disclosure, expressions such as “at least one of A, B or C,” “at least one of A, B or C,” “A, B and / or C,” and “A / B / C” may be interpreted as including “only A,” “only B,” “only C,” “A and B,” “B and C,” “C and A,” or “all of A, B and C.” Similar reinterpretations may be applied to any expression in this disclosure that means "at least X of ..." (where the number of elements in "..." and X are arbitrary numbers).

[0325] In this disclosure, expressions such as “A, [and] B, and the like” / ”such as A [and] B”,” “A, [or] B, or the like” / ”such as A [or] B”,” “A, B, etc.” / ”A, B, and so on” / ”A, B, and so forth”,” and “A, B, [and / or] the others” may be interpreted as one another.

[0326] In this disclosure, expressions representing one / singular X (e.g., "a X," "one X," "a single X"), expressions representing one or more X (e.g., "one or more X(s)," "at least one of X(s)"), and expressions representing multiple X (e.g., "Xs," "more than one X(s)," "multiple X(s)," "a plurality of X(s)") may be interpreted as one another. These expressions may also be interpreted as one another with expressions that include specific wording (e.g., "pieces of," "amount of," etc., when X is an uncountable noun). For example, "a plurality of pieces of spatial relation information" may be interpreted as "a plurality of spatial relation information."

[0327] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0328] This application is based on Japanese Patent Application No. 2025-078215, filed on May 8, 2025. All of its contents are included herein.

Claims

1. A third network node comprising: a receiving unit that receives sensing request information from a first network node or a second network node; a control unit that selects a sensing entity to perform sensing based on the sensing request information; and a transmitting unit that transmits a sensing measurement request to the sensing entity via the second network node to request sensing measurement data or sensing measurement results based on the sensing measurement data, wherein the receiving unit receives a sensing measurement response, including the sensing measurement data or the sensing measurement results, transmitted in response to the sensing measurement request, from the sensing entity via the second network node.

2. The third network node according to claim 1, wherein the control unit selects the sensing entity based on the sensing area information included in the sensing request information.

3. The third network node according to claim 2, wherein the control unit selects the sensing entity based on the sensing area information included in the sensing request information which does not include a user device identifier.

4. The third network node according to claim 1, wherein the control unit selects the sensing entity located within the service area of ​​the second network node.

5. The third network node according to claim 1, wherein the sensing measurement request includes a field indicating whether the sensing entity should transmit the sensing measurement data or the sensing measurement result.

6. The third network node according to claim 1, wherein the sensing measurement request is a sensing measurement result request for the sensing measurement result or a sensing measurement data request for the sensing measurement data.

7. The third network node according to claim 1, wherein the sensing measurement request includes information indicating which of the sensing measurement data and the sensing measurement result is recommended by the third network node.

8. The third network node according to claim 1, wherein the sensing measurement request includes sensing mode information indicating which entity transmits a signal and which entity receives the signal for the sensing.

9. The receiving unit receives the sensing request information transmitted from the first network node that receives a sensing service request from a sensing requester, according to claim 1.

10. The third network node according to claim 1, selected by the first network node.

11. The control unit selects the second network node, the third network node according to claim 10.

12. The third network node according to claim 1, wherein the second network node is selected by the first network node.

13. The third network node according to claim 12, selected by the second network node.

14. A method for a third network node, comprising: receiving sensing request information from a first network node or a second network node; selecting a sensing entity to perform sensing based on the sensing request information; transmitting a sensing measurement request to the sensing entity via the second network node to request sensing measurement data or sensing measurement results based on the sensing measurement data; and receiving a sensing measurement response from the sensing entity via the second network node, which includes the sensing measurement data or sensing measurement results transmitted in response to the sensing measurement request.

15. A first network node comprising: a receiving unit that receives a sensing service request from a sensing requester; and a transmitting unit that transmits sensing request information to one of a second network node and a third network node based on the sensing service request, wherein the receiving unit receives sensing measurement data or sensing measurement results based on the sensing measurement data transmitted from a sensing entity selected by the third network node based on the sensing request information via the one node, and the transmitting unit transmits a sensing service response including the sensing measurement data or the sensing measurement results to the sensing requester.

16. A second network node having: a receiving unit that receives sensing request information from one of a first network node and a third network node, and a receiving unit that receives a sensing measurement request from the third network node for requesting sensing measurement data or sensing measurement results based on the sensing measurement data; and a transmitting unit that transmits the sensing measurement request to a sensing entity selected by the third network node based on the sensing request information, wherein the receiving unit receives a sensing measurement response from the sensing entity, which includes the sensing measurement data or the sensing measurement results transmitted in response to the sensing measurement request; and the transmitting unit transmits the sensing measurement response to the third network node.

17. A sensing entity having: a receiving unit that receives a sensing measurement request from a second network node for requesting sensing measurement data or sensing measurement results based on the sensing measurement data; a control unit that determines, based on the sensing measurement request, whether to respond with the sensing measurement data or generate and respond with the sensing measurement results; and a transmitting unit that transmits a sensing measurement response including the sensing measurement data or the sensing measurement results to the second network node.

18. A terminal having, in a specific case, a receiving unit that receives a sensing notification call request from a second network node, and a transmitting unit that, in response to the sensing notification call request, transmits to the second network node, using non-access layer (NAS) signaling, information relating to privacy settings concerning itself or a sensing object associated with it.

19. A communication system comprising a third network node according to any one of claims 1 to 13, a first network node according to claim 15, a second network node according to claim 16, and a sensing entity according to claim 17.