Method and apparatus for supporting integrated sensing service in communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method for providing an integrated sensing service in a wireless communication system is provided. The method includes: receiving, from a first device, a request message for requesting a sensing service related to at least one sensing node; transmitting, to an access and mobility management function (AMF) associated with the at least one sensing node, a transmission request message for requesting sensing service activation based on the request message; and receiving, from the at least one sensing node, at least one sensing event notification message including a sensing result based on the request message.

Description

TECHNICAL FIELD

[0001] The disclosure relates to a method and device for providing an integrated sensing service in a wireless communication system. BACKGROUND

[0002] The 5th-Generation (5G) mobile communication technologies define broad frequency bands so as to achieve a high transmission rate beyond the 4th-Generation (4G) systems. Specifically, the 5G mobile communication technologies are being developed not only for providing the high transmission rate but also for providing new services and functions such as a high-reliability and low-latency communication, a large number of connections, and a high system capacity.

[0003] At the early stage of the development of the 5G mobile communication technologies, technologies related to beamforming, massive Multiple-Input Multiple-Output (MIMO), and a support parameter for a dynamic operation of a slot format (e.g., operating multiple subcarrier spacings) for efficiently utilizing mmWave resources have been considered. In addition, new channel coding methods such as a Low Density Check (LDPC) code for large data transmission and a polar code for high reliable transmission of control information, a definition and operation of a bandwidth part (BWP), initial access technologies for supporting multi-beam transmission and wide band, Layer 2 (L2) pre-processing, and network slicing for providing a dedicated network for a specific service have been considered.

[0004] Currently, with respect to services supported by the 5G mobile communication technologies, discussions are continuously made on improvements and performance enhancements of initial 5G mobile communication technologies, and physical layer standardization has been completed with respect to technologies such as Vehicle-to-everything (V2X) for assisting driving decisions based on information about positions and states of vehicles transmitted by the vehicles and for improving convenience of users, New Radio Unlicensed (NR-U) aiming to system operations compliant with various regulatory requirements in unlicensed bands, NR User Equipment (UE) power saving, Non-Terrestrial Network (NTN) which is direct communication of UEs with satellites for ensuring coverage in areas where communication with terrestrial networks is not possible, and positioning.

[0005] In addition, standardization for air interface architecture / protocol of the following technologies has been ongoing, such as: Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries; Integrated Access and Backhaul (IAB) for providing nodes for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner; mobility enhancement including conditional handover and dual active protocol stack (DAPS) handover; and two-step random access (two-step random access channel (RACH) for NR) for simplifying a random access procedure. At the same time, standardization for system architecture / service of the following technologies has been ongoing: 5G baseline architecture for combining network function virtualization (NFV) and software-defined networking (SDN) technologies (e.g., service-based architecture or service-based interface); and mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, exponentially increasing connected devices will access the communication network, and thus it is expected that enhanced functionality and performance of 5G mobile communication systems and integrated operations of connected devices will be necessary. For this reason, new research on the following technologies has been scheduled: extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0007] In addition, such development of 5G mobile communication systems will lay the groundwork not only for developing new waveforms for providing coverage in the terahertz bands of 6G mobile communication technologies, but also for developing multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas; metamaterial-based lenses and antennas for improving coverage of terahertz band signals; high-dimensional space multiplexing technology using orbital angular momentum (OAM); and reconfigurable intelligent surfaces (RISs), but also for developing full-duplex technologies for increasing frequency efficiency of 6G mobile communication technologies and improving system networks; AI-based communication technologies for implementing system optimization from the design stage by utilizing satellites and artificial intelligence (AI) and internalizing end-to-end AI support functions; and next-generation distributed computing technologies for implementing services by utilizing super-high-performance communication and computing resources at a complexity level exceeding the limit of UE operating capabilities.

[0008] The above information is presented as background information only to assist with an understanding of the present disclosure. It is not admitted that any of the above information constitutes prior art with respect to the present disclosure, and should not be construed as such. SUMMARY

[0009] [Technical Problem]

[0010] The aspects of this disclosure will solve at least the aforementioned problems and / or disadvantages, and provide at least the following advantages. Therefore, as one aspect of this disclosure, various sensing services are provided by utilizing entities capable of communicating in a mobile communication system (e.g., base stations and UEs).

[0011] Another aspect of this disclosure will provide integrated sensing and communication technologies in mobile communication systems.

[0012] Another aspect of this disclosure provides a service provider for providing sensing services via a UE / base station / cell in a mobile communication network.

[0013] Another aspect of this disclosure provides a scalable sensing service architecture and a sensing service delivery method to mitigate the impact of sensing information services on the quality of existing communication services.

[0014] Another aspect of this disclosure provides a method and apparatus for providing sensing services in a mobile communication network while taking scalability into account.

[0015] [Technical Solution to the Problem]

[0016] According to one aspect of this disclosure, a method is provided for providing integrated sensing services by a network entity in a wireless communication system. The method includes: receiving from a first device a request message for requesting sensing services associated with at least one sensing node; sending a transmission request message to an Access and Mobility Management Function (AMF) associated with the at least one sensing node for requesting activation of the sensing service based on the request message; and receiving from the at least one sensing node at least one sensing event notification message including sensing results based on the request message.

[0017] According to another aspect of this disclosure, a network entity for providing integrated sensing services in a wireless communication system is provided. The network entity includes a transceiver and a processor operatively connected to the transceiver, wherein the processor is configured to: receive from a first device a request message for requesting sensing services associated with at least one sensing node; send a transmission request message to an Access and Mobility Management Function (AMF) associated with at least one sensing node for requesting activation of the sensing services based on the request message; and receive from at least one sensing notification message from the at least one sensing node, the at least one sensing notification message including sensing results based on the request message.

[0018] Other aspects, advantages, and salient features of this disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments disclosed in conjunction with the accompanying drawings. Attached Figure Description

[0019] The above and other aspects, features and advantages of certain embodiments of the present disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: Figure 1 is a block diagram illustrating a configuration example of a wireless communication system according to an embodiment of the present disclosure; Figure 2 is a sequence diagram illustrating a sensing provider function (SPF) registration procedure over a network repository function (NRF) according to an embodiment of the present disclosure; Figure 3 is a sequence diagram illustrating a SPF discovery procedure over a NRF according to an embodiment of the present disclosure; Figure 4 is a sequence diagram illustrating a procedure of an AF triggering a sensing service activation according to an embodiment of the present disclosure; Figure 5 is a sequence diagram illustrating a procedure of a UE triggering a sensing service activation according to an embodiment of the present disclosure; Figure 6 is a sequence diagram illustrating a procedure of a UE triggering a sensing service activation over a user plane according to an embodiment of the present disclosure; Figure 7 is a block diagram illustrating a configuration of a UE according to an embodiment of the present disclosure; and Figure 8 is a block diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.

[0020] In all the drawings, it should be noted that the same reference numerals are used to describe the same or similar elements, features, and structures. DETAILED DESCRIPTION

[0021] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be taken as illustrating, rather than limiting, various embodiments. Accordingly, those of ordinary skill in the art will recognize that there are various changes, modifications, and implementations they can suggest to achieve the same or similar results without departing from the scope and spirit of the disclosure. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

[0022] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used to enable a clear and consistent understanding of the present disclosure. Accordingly, those of ordinary skill in the art will appreciate that the description of various embodiments of the present disclosure is merely provided for the purpose of illustration, rather than for the purpose of limitation by the claims and their equivalents.

[0023] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0024] In describing embodiments of the present disclosure, descriptions related to technical contents well known in the related art and not directly associated with the present disclosure will be omitted. The purpose of such omission of unnecessary descriptions is to prevent obscuring the main idea of the present disclosure and to more clearly convey the main idea.

[0025] For the same reason, in the drawings, some elements can be exaggerated, omitted, or schematically shown. Also, the size of each element does not completely reflect the actual size. In the respective drawings, the same or corresponding elements have the same reference numerals.

[0026] The advantages and features of the present disclosure and a method for achieving them will be apparent by referring to the embodiments described below in detail in connection with the accompanying drawings. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The embodiments are provided only to completely disclose the present disclosure and to inform the scope of the present disclosure to those skilled in the art, and the present disclosure is limited only by the scope of the claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

[0027] Here, it will be understood that each block of the flowchart, and combinations of blocks in the flowchart, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer- usable or computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer- implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0028] Also, each block in the flowchart illustrations can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending on the functionality involved.

[0029] As used in the embodiments of the disclosure, a "unit" refers to a software element or hardware element, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), which performs a predetermined function. However, the "unit" is not limited to software or hardware, and can be configured in a storage medium that can be addressed or a processor that can execute one or more processors. Therefore, the "unit" includes, for example, a software element, an object-oriented software element, a class element or a task element, a process, a function, a property, a procedure, a segment of program code, a driver, firmware, microcode, a circuit, data, a database, a data structure, a table, an array, and a parameter. Elements and functions provided by the "unit" can be combined with fewer elements and "units" or divided into a larger number of elements and "units." Also, the elements and "units" can be implemented into one or more central processing units (CPUs) in a reconfigurable device or a secure multimedia card.

[0030] As used herein, each of the phrases such as "A and / or B", "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include all possible combinations of the items listed in the corresponding one of the phrases. Terms such as "1st", "2nd", "first", and "second" can be used to simply distinguish a corresponding element from another element, and do not limit the element in other aspects (e.g., importance or order).

[0031] In the following description, a base station is an entity that allocates resources to a terminal, and can be at least one of a Node B, a base station (BS), an eNode B (eNB), a gNode B (gNB), a wireless access unit, a base station controller, and a node on a network. A terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Also, the embodiments of the disclosure as described below can also be applied to other communication systems having a similar technical background or channel type as the embodiments of the disclosure. Also, the embodiments of the disclosure can be applied to other communication systems with some modifications based on the determination of those skilled in the art, without deviating from the scope of the disclosure.

[0032] In the disclosure, network technologies can refer to standards defined by the International Telecommunication Union (ITU) or the Third Generation Partnership Project (3GPP) (e.g., TS 23.501, TS 23.502, and TS 23.503), and include components in the network structure of Figure 1 Components in the network structure of can refer to physical entities, software performing individual functions, or hardware in combination with software, respectively. In the drawings, reference symbols (e.g., N1, N2, and N3) shown as Nx indicate known interfaces between NFs in a 5G core network (CN), and can refer to related descriptions in standards (TS 23.501), and thus detailed descriptions will be omitted.

[0033] In the following description, for the purpose of description convenience, terms for identifying access nodes, terms related to network entities, terms related to messages, terms related to interfaces between network entities, terms related to various identification information, and the like are used illustratively. Accordingly, the disclosure is not limited by the terms as described below, and other terms related to the subject matter having equivalent technical meanings can also be used.

[0034] In the following description, for the purpose of description convenience, some terms and names defined in the Third Generation Partnership Project Long Term Evolution (3GPP LTE) standard can be used. However, the disclosure is not limited by these terms and names, and can be applied in the same manner to systems conforming to other standards.

[0035] It should be understood that the blocks in each flowchart and combinations of the flowcharts can be executed by one or more computer programs including instructions. The whole of the one or more computer programs can be stored in a single memory device, or the one or more computer programs can be divided into different parts and stored in different multiple memory devices.

[0036] Any function or operation described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is a circuit that performs processing, and includes a circuit such as an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a micro processing unit (MPU), a system on chip (SoC), an IC, and the like.

[0037] Figure 1is a block diagram illustrating a configuration example of a wireless communication system according to an embodiment of the present disclosure. In the illustrated example, the wireless communication system can include a 5G mobile communication network 100.

[0038] Referring to Figure 1 , the 5G mobile communication network 100 can include a 5G user equipment (UE) 110, a radio access network (RAN) 120 (e.g., at least one of a base station, a 5G node B (gNB), or an evolved node B (eNB)), and a 5G core network. The 5G core network can include at least one of an access and mobility management function (AMF) 150 configured to provide a mobility management function of the UE 110, a session management function (SMF) 160 configured to provide a session management function, a user plane function (UPF) 170 responsible for forwarding data to a data network (DN) 171, a policy control function (PCF) 180 configured to provide a policy control function, a network slice selection function (NSSF) 151, an authentication server function (AUSF) 152, a unified data management (UDM) 153 configured to provide a function of managing data such as user data and policy control data, or an application function (AF) 130. Although not shown, the 5G core network can further include network functions such as a unified data repository (UDR) configured to store data related to various network functions (NFs), a network repository function (NRF), a network exposure function (NEF), or a network data analytics function (NWDAF).

[0039] In the 3GPP system, a concept link connecting NFs in the 5G system is defined as a reference point. The reference points included in the 5G system architecture shown in FIG. 1 are shown below. Figure 1

[0040] -N1: a reference point between the UE 110 and the AMF 150

[0041] -N2: a reference point between the (R)AN 120 and the AMF 150

[0042] -N3: a reference point between the (R)AN 120 and the UPF 170

[0043] -N4: a reference point between the SMF 160 and the UPF 170

[0044] -N5: a reference point between the PCF 180 and the AF 130

[0045] -N6: a reference point between the UPF 170 and the DN 171

[0046] -N7: a reference point between the SMF 160 and the PCF 180 ​

[0047] - N8: Reference point between UDM 153 and AMF 150

[0048] - N9: Reference point between two core UPFs (e.g., between UPFs 170)

[0049] - N10: Reference point between UDM 153 and SMF 160

[0050] - N11: Reference point between AMF 150 and SMF 160

[0051] - N12: Reference point between AMF 150 and AUSF 152

[0052] - N13: Reference point between UDM and AUSF 152

[0053] - N14: Reference point between two AMFs (e.g., between AMFs 150)

[0054] - N15: Reference point between PCF 180 and AMF 150 in non-roaming case; between PCF 180 and AMF 150 in visited network in roaming case

[0055] The 5G core network can also include an NF (e.g., a sensing provider function (SPF)) configured to manage a sensing service using a UE / base station that provides integrated sensing and communication (ISAC) functionality, e.g., object detection and / or map generation, based on transmitted / received wireless signals for communication. The SPF can provide the following functions: storing a request for a sensing function based on a supporting ISAC entity (e.g., RAN 120 and / or UE 110), performing signaling using an entity (e.g., RAN 120 and / or UE 110) configured to perform a sensing function for a required sensing activation and deactivation based on the request, and collecting sensing information from an entity (e.g., RAN 120 and / or UE 110) configured to perform a sensing function, and processing / forwarding the collected information. The NF providing these functions can be referred to by a term different from the SPF.

[0056] The SPF can be located as a separate NF or can be co-located with at least one of the NEF, the PCF 180, or the NWDAF.

[0057] Figure 2 FIG. 14 is a sequence diagram illustrating an SPF registration procedure over the NRF according to an embodiment of the disclosure. According to an embodiment, at least one of the following operations can be omitted, modified, or performed in a different order.

[0058] Referring to FIG. 14 Figure 2In operation 201, when an NF profile of the SPF 191 is changed or the NF profile has not been registered to the NRF 192, the SPF 191 can transmit a registration request message (e.g., Nnrf_NFManagmenet_NFRegister request) to the NRF 192. In an embodiment, the message can include at least one of the following information elements.

[0059] - NF type: can include information indicating the SPF 191.

[0060] - Sensing service type: can include one or more pieces of information indicating a type of a sensing service supported by the SPF 191. For example, at least one of spatial mapping, three-dimensional (3D) map generation, intruder detection, object detection, or ranging can be included.

[0061] - Sensing area: can include information about an area in which the SPF 191 supports a sensing function. For example, at least one of a list of timing advance (TA), a list of cells, or a geographical area can be included.

[0062] - Fully qualified domain name (FQDN) or Internet protocol (IP) address of NF: can include an address (e.g., FQDN or IP address) of the SPF 191.

[0063] - Public land mobile network (PLMN) ID: can include an ID of a PLMN to which the SPF 191 belongs (or supports).

[0064] - Single network slice selection assistance information (S-NSSAI): can include an identifier of a network slice supported by the SPF.

[0065] The NRF 192 can register / store the information included in the registration request message of operation 201. When the registration is successful, in operation 202, the NRF 192 can transmit a registration response message (e.g., Nnrf_NFRegister response) including information indicating successful registration to the SPF 191.

[0066] Figure 3 is a sequence diagram illustrating an SPF discovery procedure through an NRF according to an embodiment of the disclosure. According to an embodiment, at least one of the following operations can be omitted, modified, or performed in a different order.

[0067] Referring to Figure 3In operation 301, a user NF 193 (e.g., at least one of the NEF 194, the SMF 160, the AMF 150, or the AF 130), which is an NF requiring a sensing service, can transmit a discovery request message (e.g., Nnrf_NFDiscovery request) to the NRF 192 to obtain information about the SPF 191. In an embodiment, the message can include at least one of the following information elements.

[0068] - Target NF Type: can include information indicating the NF type of the SPF.

[0069] - Sensing Service Type: when the target NF type is the SPF, can include information indicating the type of the sensing service requested by the user NF 193.

[0070] - Requested Sensing Service Area: when the target NF type is the SPF, can include information about an area in which the sensing service is to be used.

[0071] - PLMN ID: can include a requested PLMN ID.

[0072] Based on the information included in the discovery request message of operation 301, the NRF 192 can determine information about the NFs to be included in the response message among the previously registered NFs.

[0073] When the target NF type included in the discovery request message indicates the SPF (e.g., the SPF 191), the NRF can include information (e.g., NF instance ID, IP address, and / or FQDN) about the SPF 191 in the response message (e.g., Nnrf_NFDiscovery response) in operation 302. When the NF profile of multiple SPFs is stored in the NRF 192, the discovery response message can include at least one of the NF instance ID, the IP address, or the FQDN of each SPF.

[0074] When the discovery request message of operation 301 includes the sensing service type, the NRF 192 can include at least one of the NF instance ID, the IP address, or the FQDN of each of the SPFs supporting the sensing service type in the discovery response message.

[0075] When the discovery request message of operation 301 includes the requested sensing service area, at least one of the NF instance ID, the IP address, or the FQDN of each of the SPFs supporting the requested sensing service area can be included in the discovery response message.

[0076] Based on the information on the SPF instance (e.g., at least one of an NF instance ID, an IP address, or an FQDN) received in operation 302, the user NF 193 can select the SPF 191 through SPF selection, and can transmit a message (not shown) for a sensing service to the selected SPF 191.

[0077] Figure 4 FIG. 18 is a sequence diagram illustrating a procedure of an AF triggered sensing service activation according to an embodiment of the disclosure. According to an embodiment, at least one of the following operations can be omitted, modified, or performed in a different order.

[0078] Referring to Figure 4 In operation 401, the AF 130 can transmit a sensing request message to the NEF 194 to enable a user NF (e.g., the user NF 193) (e.g., a third party) to use a sensing service.

[0079] In an embodiment, the sensing request message can include at least one of the following information elements.

[0080] - User ID: can indicate an identifier of a user (e.g., the user NF 193) requesting a sensing service. For example, the user ID can include at least one of an AF ID (e.g., an identifier of an AF when the user NF is an AF), an App ID (information for identifying an application provider requesting a sensing service), an external group ID, or a sensing user ID.

[0081] - Requested sensing service type: can indicate a type of a sensing service requested by the AF 130.

[0082] - Requested sensing related parameters per sensing service type

[0083] - Sensing service specific parameters: can include additional parameters for each sensing service included in the requested sensing service type.

[0084] For example, when the sensing service type is object detection, the sensing service specific parameters can include information on a target object (e.g., a person or a cat).

[0085] For example, when the sensing service type is 3D map generation, the sensing service specific parameters can include information on a frequency of performing a 3D scan.

[0086] - Requested sensing time: can indicate time information for requesting activation of a sensing service. In an embodiment, the requested sensing time can include a start time and an end time of a sensing service, or a duration thereof (e.g., 30 days).

[0087] - Requested sensing service area: can indicate information related to an area in which a sensing service will be used. For example, the requested sensing service area can include at least one of a list of tracking areas (TAs), a list of cells, or information about a geographical area.

[0088] - Requested number of sensing nodes: can indicate a number of requested sensing nodes (e.g., UEs or RANs).

[0089] - Requested sensing accuracy: can indicate a required accuracy of a sensing service. The requested sensing accuracy can include different information depending on each sensing service.

[0090] For example, the “requested sensing accuracy” can include accuracy and / or recall.

[0091] - Sensing notification trigger information: can include information about sensing event notification transmission. In an embodiment, the “sensing notification trigger information” can indicate an event-based notification method (e.g., transmitting a sensing notification when a specific event occurs) or a periodic notification method.

[0092] In the periodic notification method, the sensing notification trigger information can include a time threshold (i.e., transmitting one notification per time threshold) and / or a quantity threshold (i.e., transmitting a notification when a quantity of sensing data to be included in a notification reaches the quantity threshold).

[0093] - List of UE IDs: can include UE IDs for performing a sensing service. The UE ID can include at least one of, for example, an IP address / port number, a generic public subscription identifier (GPSI), and / or a media access control (MAC) address.

[0094] - List of RAN node IDs: can include RAN node IDs or cell IDs that will perform a sensing service.

[0095] - Sensing mode per UE / RAN / Cell: can include a sensing mode for each sensing node (e.g., UE, RAN, or cell). In an embodiment, each sensing mode can indicate at least one of a sensing signal transmitter, a sensing signal receiver, or both.

[0096] In an embodiment, there is a parameter set for a sensing service, where the AF 130 has pre-agreed with a network (e.g., a 5G network), and the AF 130 stores a sensing reference ID for the agreed parameter set, the AF 130 can include the sensing reference ID in the sensing request message of operation 401, instead of including in the requested sensing parameters (e.g., at least one of a requested sensing type, a sensing service specific parameter, a requested sensing area, a requested sensing time, a number of requested sensing nodes, or a requested sensing accuracy).

[0097] In operation 402, the NEF 194 can transmit an authorization request message to perform authorization through the UDM 153 in response to the sensing request message. In an embodiment, the authorization request message can include at least one of the following information elements: - a user ID: for example, at least one of an AF ID (i.e., an identifier of the AF when the user NF is the AF), an App ID (when a specific application provider requests a sensing service), an external group ID, or a sensing user ID; or - part or all of the requested sensing parameters received in operation 401.

[0098] In an embodiment, when the UE ID is included in the sensing request message received in operation 401, the NEF 194 can transmit the authorization request message to the UDM 153 to perform authorization through the UDM 153 based on the requested sensing parameters (e.g., at least one of a requested sensing type, a sensing service specific parameter, a requested sensing area, a requested sensing time, a number of requested sensing nodes, or a requested sensing accuracy) corresponding to the sensing reference ID of each UE included in the sensing request message of operation 401.

[0099] The authorization request message can include an AF ID, a UE ID, or part or all of the requested sensing parameters of each UE.

[0100] When a plurality of UE IDs are included in the authorization request message, the requested sensing parameters for each UE ID can be included in the authorization request message.

[0101] In operation 403, the UDM 153 can include an authorization result (e.g., success or failure) in an authorization response message to be transmitted to the NEF 194 in response to the sensing request message of operation 401.

[0102] When the authorization request for the requested sensing parameters of each UE is received in operation 402, the UDM 153 can include an authorization result (e.g., success or failure) on the requested sensing parameters of each UE in an authorization response message to be transmitted to the NEF 194.

[0103] In an embodiment, when the authorization result indicating the failure of the sensing request included in the authorization response message received from the UDM 153, the NEF 194 can include information indicating the failure of the processing of the sensing request in the sensing response message (not shown) transmitted to the AF 130, and can not perform the remaining operations.

[0104] In an embodiment, when the authorization result with respect to each UE's requested sensing parameter included in the authentication response message received from the UDM 153 indicates the failure, the NEF 194 can include information indicating the failure of the sensing request for the corresponding UE (i.e., the UE for which the authorization has failed) in the sensing response message (not shown) transmitted to the AF 130, and can not perform the remaining operations for the UE. In an embodiment, the NEF 194 can not include the corresponding UE ID (the ID of the UE for which the authorization has failed) in the message (e.g., the sensing request message of operation 404) to be transmitted to the SPF 191, but can include only the UE ID of the UE that has been successfully authorized.

[0105] In operation 404, based on the sensing request message of operation 401, the NEF 194 can transmit a sensing request message including the information included in the sensing request message of operation 401 to the SPF 191 selected by the SPF discovery / selection. In an embodiment, the NEF 194 can discover and select the SPF 191 through the SPF discovery / selection procedure before operation 404.

[0106] In an embodiment, the SPF discovery / selection procedure can include the procedure of Figure 3 For example, Figure 3 The user NF 193 of

[0107] In operation 405, the SPF 191 can transmit a response message (e.g., ACK) including a sensing request result (e.g., success or failure) to the NEF 194.

[0108] Based on the previously stored sensing node information for each sensing service type, the SPF 191 can determine a list of sensing nodes. Each sensing node in the list of sensing nodes can be one of a RAN node, a cell, or a UE, and can be identified by one of a RAN node ID, a cell ID, or a UE ID.

[0109] In operation 406, the SPF 191 can first transmit a transfer request message including at least one of the following information elements to the AMF 150 to request activation from the determined sensing node.

[0110] In an embodiment, when the sensing node is a RAN node or a cell, the transfer request message can include one or more of the following information and a RAN node ID (or a cell ID).

[0111] - at least one of a sensing mode, a sensing service type, a service-specific sensing parameter, a sensing area, a sensing time, a sensing accuracy, or a sensing notification trigger condition of each sensing node.

[0112] In an embodiment, when the sensing node is a UE, the transfer request message can include one or more of the following information and a UE ID.

[0113] - at least one of a sensing mode, a sensing service type, a service-specific sensing parameter, a sensing area, a sensing time, a sensing accuracy, or a sensing notification trigger condition of each sensing node.

[0114] When the SPF 191 supports an aggregated response, in operation 404, when the first transfer request message (e.g., the transfer request message of operation 406) is transmitted to the AMF 150 in response to the sensing request, the SPF 191 can perform a timer configured with a preset timer value.

[0115] When the RAN node ID (or the cell ID) is included in the transfer request message received in operation 406, in operation 407, the AMF 150 can include information of each RAN node (or cell) received in operation 406 in an N2 message to be transmitted to a corresponding RAN (e.g., the RAN 120).

[0116] Based on the information included in the N2 message received from the AMF 150, the RAN 120 can activate a sensing service. In an embodiment, the RAN 120 can perform a sensing service, such as object detection and / or map generation, according to an ISAC function, and can generate a sensing result.

[0117] In an embodiment, when the RAN 120 supports a sensing service type and a sensing mode, the RAN 120 can activate a sensing service of the sensing service type in the sensing mode.

[0118] In an embodiment, based on information included in a service-specific sensing parameter in the N2 message, the RAN 120 can determine a sensing period.

[0119] In an embodiment, based on the sensing area and / or the sensing time included in the N2 message, the RAN 120 can activate the sensing service for the sensing time in the sensing area.

[0120] In an embodiment, when the N2 message includes a sensing accuracy, the RAN 120 can consider the accuracy to determine a signal strength for sensing and / or a signal transmission period for sensing.

[0121] In an embodiment, when the N2 message includes a sensing notification trigger condition, the RAN 120 can determine a transmission period of a sensing notification message (e.g., a sensing notification message or a notification address transmitted to the AMF 150) based on the condition.

[0122] In operation 408, the RAN 120 can include a sensing service activation result in an N2 response message to be transmitted to the AMF 150.

[0123] When the UE ID is included in the transfer request message received in operation 406, the AMF 150 can include information of each UE received in operation 406 in an N1 message to be transmitted to the corresponding UE (e.g., the UE 110) in operation 409.

[0124] Based on the information included in the N1 message received from the AMF 150, the UE 110 can activate the sensing service. In an embodiment, the UE 110 can perform the sensing service according to the ISAC function, such as object detection and / or map generation, and can generate a sensing result.

[0125] In an embodiment, when the UE 110 is capable of supporting a sensing service type and a sensing mode included in the N1 message, the UE 110 can activate the sensing service of the sensing service type in the sensing mode.

[0126] In an embodiment, based on information included in a service-specific sensing parameter in the N1 message, the UE 110 can determine a sensing period.

[0127] In an embodiment, when a sensing area and / or a sensing time are included in the N1 message, the UE 110 can activate the sensing service for the sensing time in the sensing area.

[0128] In an embodiment, when the N1 message includes a sensing accuracy, the UE 110 can consider the accuracy to determine a signal strength for sensing and / or a signal transmission period for sensing.

[0129] In an embodiment, when the N1 message includes a sensing notification trigger condition, the UE 110 can determine the sending period of the sensing notification message (e.g., a sensing notification message sent to the AMF 150 or a notification address) based on the condition.

[0130] In operation 410, UE 110 may include the sensing service activation result in the N1 response message to be sent to AMF 150.

[0131] In operation 411, AMF 150 may send a response message to SPF 191 including a sensing service activation result (e.g., success or failure). In an embodiment, based on the N2 response message for each RAN (or cell) in operation 408, AMF 150 may include the sensing service activation result of the RAN (or cell) in the response message to be sent to SPF 191. In an embodiment, based on the N1 response message for each UE in operation 410, AMF 150 may include the sensing service activation result of the corresponding UE in the response message to be sent to SPF 191. In an embodiment, AMF 150 may send the sensing service activation result to SPF 191 via one or more individual response messages or at least one integrated response message for one or more sensing nodes (e.g., RAN 120, UE 110, or cell).

[0132] When SPF 191 does not support aggregated responses, in operation 413, whenever a response message is received from each sensing node (e.g., the response message in operation 411), SPF 191 may send a response message to NEF 194 that includes the sensing activation result of each sensing node.

[0133] When SPF 191 supports aggregated responses, in operation 412, SPF 191 can aggregate the sensing service activation results of each sensing node in the response message. In operation 413, SPF 191 can send a response message (e.g., an aggregated response message) including the aggregated sensing service activation results to NEF 194.

[0134] When SPF 191 supports aggregated responses, upon the expiration of the timer started in operation 406 or upon receiving a response message from operation 411 for all sense node IDs requested in operation 406, SPF 191 may send an aggregated response message to NEF 194 including the sense activation results for each of the multiple sense nodes. In an embodiment, in operation 404, the aggregated response message may include a transaction ID generated by SPF 191 in response to a request from NEF 194.

[0135] An aggregated response message may include at least one of the following information elements: - The sensing activation result (e.g., success or failure) of each UE corresponding to the UE ID included in the transmission request message in operation 406; - The sensing activation result (e.g., success or failure) for each UE / RAN corresponding to the RAN ID included in the transmission request message in operation 406; or - The activation result (e.g., success or failure) of each UE / cell for each cell corresponding to the cell ID included in the transmission request message in operation 406.

[0136] In operation 414, NEF 194 may include all or part of the response message received in operation 413 in the sensing response message to be sent to AF 130.

[0137] In operation 415, each sensing node (e.g., RAN 120 or UE 110) may send a sensing notification message (e.g., a sensing event notification message) to SPF 191. The sensing notification message may be sent directly from each sensing node to SPF 191, or via another NF (e.g., AMF 150) to SPF 191. The sensing notification message may include at least one of the following information elements: - Timestamp: Information related to the time when the sensed information was generated; - Detection Node ID: The identifier of the detection node (e.g., UE ID, RAN ID, or cell ID); or - Sensing information: Information that indicates the sensing results. For example, in 3D map generation, sensing information may include information related to the 3D space in which the sensing was performed.

[0138] If needed, SPF 191 can aggregate the sensing notification messages received in operation 415. In operation 416, based on the sensing notification triggering conditions received in operation 401, SPF 191 can send the (aggregated) sensing event notification messages to AF 130 via NEF 194.

[0139] An aggregated sensing event notification message may include at least one of the following information elements.

[0140] - Transaction ID and / or sensing information for each sensing node (e.g., timestamp, sensing node ID, and / or sensing information)

[0141] Figure 5 This is a sequence diagram illustrating the process by which a UE triggers the activation of a sensing service according to an embodiment of this disclosure. According to the embodiment, at least one of the following operations may be omitted, modified, or performed in a different order.

[0142] Reference Figure 5 In operation 501, when a specific application (e.g., a third-party application) performing in the UE (e.g., UE 110a) requests sensing, UE 110a can send a sensing request message to the AMF 150a responsible for UE 110 via RAN 120. The sensing request message may include at least one of the following information elements.

[0143] - User ID: May include an identifier of the user (e.g., UE 110 or application) requesting the sensing service. For example, the user ID may include at least one of the following: UE ID, App ID (when a specific application provider requests the sensing service), external group ID, or sensing user ID.

[0144] - Requested sensing service type: This indicates the type of sensing service requested by the AF.

[0145] - Requested sensing-related parameters for each sensing service type.

[0146] - Sensing service specific parameters: Additional parameters can be included for each sensing service included in the requested sensing service type.

[0147] For example, when the sensing service type is object detection, specific parameters of the sensing service can include information about the target object (e.g., a person or a cat).

[0148] For example, when the sensing service type is 3D map generation, sensing service-specific parameters may include information about the frequency of performing 3D scans.

[0149] - Requested sensing time: This can indicate the time information used to request activation of the sensing service. In an embodiment, the requested sensing time may include the start and end times of the sensing service, or its duration (e.g., 30 days).

[0150] - Requested sensing service area: This can indicate information about the area in which sensing services will be used. For example, the requested sensing service area may include at least one of a list of TAs, a list of cells, or information about a geographic area.

[0151] - Number of requested sensing nodes: This can indicate the number of sensing nodes (e.g., UE or RAN) requested.

[0152] - Requested sensing accuracy: This indicates the required accuracy of the sensing service. The requested sensing accuracy may include different information depending on each sensing service.

[0153] For example, "requested sensing accuracy" may include accuracy and / or recall.

[0154] - Sensing notification trigger information: This may include information about the sending of sensing event notifications. In embodiments, "sensing notification trigger information" may indicate an event-based notification method (e.g., sending a sensing notification when a specific event occurs) or a periodic notification method.

[0155] In an embodiment, the periodic notification method may include a time threshold (i.e., a notification is sent for each time threshold) and / or a quantity threshold (i.e., a notification is sent when the amount of sensing data to be included in the notification reaches a quantity threshold).

[0156] - List of UE IDs: This may include the UE IDs used to perform sensing services. UE IDs may include at least one of, for example, an IP address / port number, a GPSI, and / or a MAC address.

[0157] - A list of RAN node IDs: This may include the RAN node IDs or cell IDs that will perform the sensing service.

[0158] - Sensing mode for each UE / RAN / cell: This may include a sensing mode for each sensing node (e.g., UE, RAN, or cell). In embodiments, each sensing mode may indicate a sensing signal transmitter, a sensing signal receiver, or at least one of both.

[0159] In an embodiment, there is a set of parameters for a sensing service that the application service provider (e.g., AF 130) has negotiated in advance with the network (e.g., a 5G network), and UE 110a stores a sensing reference ID for the negotiated parameter set. UE 110a may include the sensing reference ID in the sensing request message of operation 501, instead of including it in the requested sensing parameters (e.g., at least one of the requested sensing type, sensing service-specific parameters, requested sensing area, requested sensing time, requested number of sensing nodes, or requested sensing accuracy).

[0160] In operation 502, AMF 150a may send an authorization request message via UDM 153 to perform authorization in response to a sensing request message. In an embodiment, the authentication request message may include at least one of the following information elements: - User ID: For example, at least one of UE ID, App ID (when a specific application provider requests sensing services), external group ID, or sensing user ID; or - Some or all of the requested sensing parameters received in Operation 501.

[0161] In an embodiment, when the sensing request message received in operation 501 includes a UE ID, AMF 150a may send an authorization request message to UDM 153 to perform authorization through UDM 153 based on the requested sensing parameters (e.g., the requested sensing type, sensing service-specific parameters, the requested sensing area, the requested sensing time, the requested number of sensing nodes, or the requested sensing accuracy) corresponding to the sensing reference ID of each UE included in the sensing request message of operation 501.

[0162] The authorization request message may include AF ID, UE ID, or some or all of the requested sensing parameters for each UE.

[0163] When the authorization request message includes multiple UE IDs, the requested sensing parameters for each UE ID can be included in the authorization request message.

[0164] In operation 503, UDM 153 may include the authorization result (success or failure) of the sensing request message in response to operation 501 in the authorization response message to be sent to AMF 150a.

[0165] When an authorization request for the requested sensing parameters for each UE is received in operation 502, UDM 153 may include the authorization result (success or failure) for the requested sensing parameters for each UE in the authorization response message to be sent to AMF150a.

[0166] In an embodiment, when the authorization result of the sensing request included in the authorization response message received from UDM 153 indicates failure, AMF 150a may include information indicating failure to process the sensing request in the sensing response message (not shown) sent to UE110a and not perform any further operations.

[0167] In an embodiment, when the authorization result for the requested sensing parameters of each UE included in the authentication message received from UDM 153 indicates failure, AMF 150a may include information indicating that the sensing request failed for the corresponding UE (i.e., the UE whose authorization failed) in the sensing response message (not shown) sent to UE 110a, and may not perform the remaining operations for the UE. In an embodiment, AMF 150a may not include the corresponding UE ID (the ID of the UE whose authorization failed) in the message to be sent to SPF 191 (e.g., the sensing request message of operation 504), but may only include the UE ID of the successfully authorized UE.

[0168] In operation 504, AMF 150a can send a sensing request message, including the information included in the sensing request message of operation 501, to the selected SPF 191 via SPF discovery / selection, based on the sensing request message of operation 501. In an embodiment, AMF 150a can discover and select SPF 191 via the SPF discovery / selection process prior to operation 504.

[0169] In an embodiment, the SPF discovery / selection process may include Figure 3 The process. For example. Figure 3 User NF 193 can be AMF 150a, and the sensing service type and / or the requested sensing service area in operation 301 can be the sensing service type and / or the requested sensing service area included in the sensing request message received from UE110a in operation 501.

[0170] In operation 505, SPF 191 can send a response message (e.g., ACK) to AMF 150a that includes the result of the sensing request (success or failure).

[0171] In operation 506, SPF 191 can determine a list of sensing nodes based on previously stored sensing node information for each sensing service type.

[0172] Each sensing node in the list of sensing nodes can be a RAN node, a cell, or a UE, and can be identified by one of the RAN node ID, cell ID, or UE ID.

[0173] In operation 506, SPF 191 may first send a transmission request message to the AMF (e.g., AMF 150b) responsible for the identified sensing node, including at least one of the following information elements, in order to request activation from the identified sensing node.

[0174] In an embodiment, when the sensing node is a RAN node or a cell, the transmission request message may include one or more of the following information and the RAN node ID (or cell ID).

[0175] - At least one of the following for each sensing node: sensing mode, sensing service type, service-specific sensing parameters, sensing area, sensing time, sensing accuracy, or sensing notification triggering condition.

[0176] In an embodiment, when the sensing node is a UE (e.g., UE 110b), the transmission request message may include one or more of the following information and the UE ID.

[0177] - At least one of the following for each sensing node: sensing mode, sensing service type, service-specific sensing parameters, sensing area, sensing time, sensing accuracy, or sensing notification triggering condition.

[0178] When SPF 191 supports aggregated response, when a first transmission request message (e.g., transmission request message of operation 506) is sent to AMF 150b in response to a sensing request in operation 504, SPF 191 can execute a timer configured with a preset timer value.

[0179] When the transmission request message received in operation 506 includes the RAN node ID (or cell ID), in operation 507, AMF 150b may include the information of each RAN node (or cell) received in operation 506 in the N2 message to be sent to the corresponding RAN (e.g., RAN 120).

[0180] Based on the information included in the N2 message received from AMF 150b, RAN 120 can activate sensing services. In an embodiment, RAN 120 can perform sensing services, such as object detection and / or map generation, according to ISAC functions, and can generate sensing results.

[0181] In an embodiment, when RAN 120 supports sensing service types and sensing modes, RAN 120 can activate the sensing service of the sensing service type under the sensing mode.

[0182] In an embodiment, RAN 120 can determine the sensing period based on information included in the service-specific sensing parameters in the N2 message.

[0183] In an embodiment, based on the sensing area and / or sensing time included in the N2 message, RAN 120 may activate a sensing service for that sensing time within that sensing area.

[0184] In an embodiment, when the N2 message includes sensing accuracy, the RAN 120 may take that accuracy into account to determine the signal strength for sensing and / or the signal transmission period for sensing.

[0185] In an embodiment, when the N2 message includes a sensing notification trigger condition, the RAN 120 can determine the sending cycle of the sensing notification message (e.g., a sensing notification message or notification address sent to the AMF 150b) based on that condition.

[0186] In operation 508, RAN 120 may include the sensing service activation result in the N2 response message to be sent to AMF 150b.

[0187] When the transmission request message received in operation 506 includes a UE ID, in operation 509, AMF 150b may include information about each UE received in operation 506 in an N1 message to be sent to the corresponding UE (e.g., UE 110b). In an embodiment, UE 110b may be the same as or different from UE 110a.

[0188] Based on the information included in the N1 message received from AMF 150b, UE 110b can activate sensing services. In an embodiment, UE 110b can perform sensing services, such as object detection and / or map generation, according to ISAC functions, and can generate sensing results.

[0189] In an embodiment, when UE 110b is able to support the sensing service type and sensing mode included in the N1 message, UE 110 can activate the sensing service of the sensing service type under the sensing mode.

[0190] In this embodiment, the UE 110b can determine the sensing period based on the information included in the service-specific sensing parameters in the N1 message.

[0191] In an embodiment, when the sensing area and / or sensing time are included in the N1 message, UE 110b can activate the sensing service for the sensing time in the sensing area.

[0192] In an embodiment, when the N1 message includes sensing accuracy, the UE 110b may take that accuracy into account to determine the signal strength and / or the signal transmission period for sensing.

[0193] In an embodiment, when the N1 message includes a sensing notification trigger condition, the UE 110b can determine the sending period of the sensing notification message (e.g., a sensing notification message or notification address sent to the AMF 150b) based on the condition.

[0194] In Operation 510, UE 110b may include the sensing service activation result in the N1 response message to be sent to AMF 150b.

[0195] In operation 511, AMF 150b may send a response message to SPF 191 including a sensing service activation result (e.g., success or failure). In an embodiment, based on the N2 response message for each RAN (or cell) in operation 508, AMF 150b may include the sensing service activation result of the RAN (or cell) in the response message to be sent to SPF 191. In an embodiment, based on the N1 response message for each UE in operation 510, AMF 150b may include the sensing service activation result of the corresponding UE (e.g., UE 110b) in the response message to be sent to SPF 191. In an embodiment, AMF 150b may send the sensing service activation result to SPF 191 via one or more response messages for one or more sensing nodes (e.g., RAN 120, UE 110b, or cell).

[0196] When SPF 191 does not support aggregated responses, in operation 513, whenever a response message is received from each sensing node (e.g., the response message in operation 511), SPF 191 may send a response message to AMF 150a that includes the sensing activation result of each sensing node.

[0197] When SPF 191 supports aggregated responses, in operation 512, SPF 191 can aggregate the sensing service activation results of each sensing node in the response message. In operation 513, SPF 191 can send a response message (e.g., an aggregated response message) to AMF150a that includes the aggregated sensing service activation results.

[0198] When SPF 191 supports aggregated responses, upon the expiration of the timer started in operation 506 or upon receiving a response message from operation 511 for all sense node IDs requested in operation 506, SPF 191 may send an aggregated response message to AMF 150a, including the sense activation results for each sense node among all sense nodes. In an embodiment, in operation 504, the aggregated response message may include a transaction ID generated by SPF 191 in response to the request from AMF 150a.

[0199] An aggregated response message may include at least one of the following information elements: - The sensing activation result (e.g., success or failure) of each UE (e.g., UE 110b) corresponding to the UE ID included in the transmission request message in operation 506. - The sensing activation result (e.g., success or failure) for each UE / RAN corresponding to the RAN ID included in the transmission request message in operation 506 for each RAN (e.g., RAN120); or - The activation result (e.g., success or failure) of each UE / cell for each cell corresponding to the cell ID included in the transmission request message in operation 506.

[0200] In operation 514, AMF 150a may include all or part of the response message received in operation 513 in the sensing response message to be sent to UE 110a.

[0201] In operation 515, each sensing node (e.g., RAN 120 or UE 110b) may send a sensing notification message to SPF 191. The sensing notification message may be sent directly from each sensing node to SPF 191, or via another NF (e.g., AMF 150b) to SPF 191. The sensing notification message may include at least one of the following information elements: - Timestamp: Information related to the time when the sensed information was generated; - Detection Node ID: The identifier of the detection node (e.g., UE ID, RAN ID, or cell ID); or - Sensing information: Information that indicates the sensing results. For example, in 3D map generation, sensing information may include information related to the 3D space in which the sensing was performed.

[0202] If needed, SPF 191 can aggregate the sensing notification messages received in operation 515. In operation 516, based on the sensing notification triggering conditions received in operation 501, SPF 191 can send (aggregated) sensing event notification messages to UE 110a via AMF 150a.

[0203] (Aggregated) sensing notification messages may include at least one of the following information elements.

[0204] - Transaction ID and / or sensing information for each sensing node (e.g., timestamp, sensing node ID, and / or sensing information)

[0205] Figure 6 This is a sequence diagram illustrating the process by which a UE triggers sensing service activation via the user plane according to an embodiment of the present disclosure. According to the embodiment, at least one of the following operations may be omitted, modified, or performed in a different order.

[0206] Reference Figure 6 In operation 601, the UE (e.g., UE 110a) may send a request message to the AMF (e.g., AMF 150a) that includes information indicating that sensing services are available.

[0207] In operation 602, AMF 150a may send a response message to UE 110a, which includes at least one of the following: an SPF address, the supported sensing service type of the corresponding SPF, or a sensing area. In an embodiment, the SPF address may indicate the user plane address (e.g., FQDN and / or IP address / port number) of the NF (e.g., SPF-UP 191a) managing the sensing service. In an embodiment, the SPF address may include an address accessible via the Internet (e.g., DN 171). In an embodiment, SPF-UP 191a may co-address with NEF 194, PCF 180, or NWDAF. In an embodiment, AMF 150a may discover and select SPF-UP 191a via an SPF discovery / selection process prior to operation 602.

[0208] In operation 603, when a specific application (e.g., a third-party application) performing in UE 110a requests sensing and UE 110a has previously stored SPF information (e.g., the SPF-UP address, sensing service type, and / or sensing area provided in operation 602), UE 110a can select the SPF to which the sensing request should be sent (e.g., SPF-UP191a) based on the SPF information, and can send a sensing request message to SPF-UP191a by using the SPF-UP address.

[0209] In this embodiment, a sensing request message can be sent via a Packet Data Unit (PDU) session. When UE 110a does not have a PDU session, UE 110a can perform a PDU session establishment procedure (not shown) to send a sensing request message.

[0210] In an embodiment, the sensing request message may include at least one of the following information elements.

[0211] - User ID: May include an identifier of the user (e.g., UE 110 or application) requesting the sensing service. For example, the user ID may include at least one of the following: UE ID, App ID (when a specific application provider requests the sensing service), external group ID, or sensing user ID.

[0212] - Requested sensing service type: This indicates the type of sensing service requested by the AF.

[0213] - Requested sensing-related parameters for each sensing service type.

[0214] - Sensing service specific parameters: Additional parameters can be included for each sensing service included in the requested sensing service type.

[0215] For example, when the sensing service type is object detection, specific parameters of the sensing service can include information about the target object (e.g., a person or a cat).

[0216] For example, when the sensing service type is 3D map generation, sensing service-specific parameters may include information about the frequency of performing 3D scans.

[0217] - Requested sensing time: This can indicate the time information used to request activation of the sensing service. In an embodiment, the requested sensing time may include the start and end times of the sensing service, or its duration (e.g., 30 days).

[0218] - Requested sensing service area: This can indicate information about the area in which sensing services will be used. For example, the requested sensing service area may include at least one of a list of TAs, a list of cells, or information about a geographic area.

[0219] - Number of requested sensing nodes: This can indicate the number of requested sensing nodes (e.g., UE or RAN).

[0220] - Requested sensing accuracy: This indicates the required accuracy of the sensing service. The requested sensing accuracy may include different information depending on each sensing service.

[0221] For example, "requested sensing accuracy" may include accuracy and / or recall.

[0222] - Sensing notification trigger information: This may include information about the sending of sensing event notifications. In embodiments, "sensing notification trigger information" may indicate an event-based notification method (e.g., sending a sensing notification when a specific event occurs) or a periodic notification method.

[0223] In an embodiment, the periodic notification method may include a time threshold (i.e., a notification is sent for each time threshold) and / or a quantity threshold (i.e., a notification is sent when the amount of sensing data to be included in the notification reaches a quantity threshold).

[0224] - List of UE IDs: This may include the UE IDs used to perform sensing services. UE IDs may include at least one of, for example, an IP address / port number, a GPSI, and / or a MAC address.

[0225] List of RAN node IDs: may include RAN node IDs or cell IDs that will perform sensing services.

[0226] - Sensing mode for each UE / RAN / cell: This may include a sensing mode for each sensing node (e.g., UE, RAN, or cell). In embodiments, each sensing mode may indicate a sensing signal transmitter, a sensing signal receiver, or at least one of both.

[0227] In an embodiment, there is a set of parameters for a sensing service that the application service provider has negotiated with the network in advance, and UE 110a stores a sensing reference ID for the negotiated parameter set. UE 110a may include the sensing reference ID in the sensing request message of operation 601 instead of including it in the requested sensing parameters (e.g., at least one of the requested sensing type, sensing service-specific parameters, requested sensing area, requested sensing time, requested number of sensing nodes, or requested sensing accuracy).

[0228] In operation 604, SPF-UP 191a may send a sensing request message to an entity (e.g., SPF control plane (CP) 191b) that provides the interface between the 5G core network and SPF-UP 191a.

[0229] In operation 605, in response to a sensing request message, SPF-CP 191b can send a response message (e.g., ACK) to SPF-UP 191a.

[0230] Based on the previously stored sensor node information for each sensing service type, SPF-CP 191b can determine a list of sensor nodes.

[0231] Each sensing node in the list of sensing nodes can be a RAN node, a cell, or a UE, and can be identified by one of the RAN node ID, cell ID, or UE ID.

[0232] In operation 606, SPF-CP 191b may send a request message (e.g., a transmission request message) to the AMF (e.g., AMF 150b) responsible for the identified sensing node, including at least one of the following information elements, in order to request activation from the identified sensing node.

[0233] In an embodiment, when the sensing node is a RAN node or a cell, the request message may include one or more of the following information and the RAN node ID (or cell ID).

[0234] - At least one of the following for each sensing node: sensing mode, sensing service type, service-specific sensing parameters, sensing area, sensing time, sensing accuracy, or sensing notification triggering condition.

[0235] In an embodiment, when the sensing node is a UE, the request message may include one or more of the following information and the UE ID.

[0236] - At least one of the following for each sensing node: sensing mode, sensing service type, service-specific sensing parameters, sensing area, sensing time, sensing accuracy, or sensing notification triggering condition.

[0237] When the SPF-CP 191b supports aggregated responses, it can execute a timer configured with a preset timer value when a first request message (e.g., the request message of operation 606) is sent to the AMF 150b in response to the request in operation 604.

[0238] When the request message received in operation 606 includes a RAN node ID (or cell ID), in operation 607, AMF 150b may include the information of each RAN node (or cell) received in operation 606 in the N2 message to be sent to the corresponding RAN (e.g., RAN 120).

[0239] Based on the information included in the N2 message received from AMF 150b, RAN 120 can activate the sensing service.

[0240] In an embodiment, when RAN 120 supports sensing service types and sensing modes, RAN 120 can activate the sensing service of that sensing service type under that sensing mode. In an embodiment, RAN 120 can perform sensing services according to ISAC functions, such as object detection and / or map generation, and can generate sensing results.

[0241] In an embodiment, RAN 120 can determine the sensing period based on information included in the service-specific sensing parameters in the N2 message.

[0242] In an embodiment, based on the sensing area and / or sensing time included in the N2 message, RAN 120 may activate a sensing service for that sensing time within that sensing area.

[0243] In an embodiment, when the N2 message includes sensing accuracy, the RAN 120 may take that accuracy into account to determine the signal strength for sensing and / or the signal transmission period for sensing.

[0244] In an embodiment, when the N2 message includes a sensing notification trigger condition, the RAN 120 can determine the sending cycle of the sensing notification message (e.g., a sensing notification message or notification address sent to the AMF 150b) based on that condition.

[0245] In operation 608, RAN 120 may include the sensing service activation result in the N2 response message to be sent to AMF 150b.

[0246] When the request message received in operation 606 includes the UE ID, in operation 609, AMF 150b may include the information of each UE received in operation 606 in the N1 message to be sent to the corresponding UE (e.g., UE 110b).

[0247] Based on the information included in the N1 message received from AMF 150b, UE 110b can activate sensing services. In an embodiment, UE 110b can perform sensing services, such as object detection and / or map generation, according to ISAC functions, and can generate sensing results.

[0248] In an embodiment, when UE 110b is able to support the sensing service type and sensing mode included in the N1 message, UE 110b can activate the sensing service of the sensing service type under the sensing mode.

[0249] In this embodiment, the UE 110b can determine the sensing period based on the information included in the service-specific sensing parameters in the N1 message.

[0250] In an embodiment, when the sensing area and / or sensing time are included in the N1 message, UE 110b can activate the sensing service for the sensing time in the sensing area.

[0251] In an embodiment, when the N1 message includes sensing accuracy, the UE 110b may take that accuracy into account to determine the signal strength and / or the signal transmission period for sensing.

[0252] In an embodiment, when the N1 message includes a sensing notification trigger condition, the UE 110b can determine the sending period of the sensing notification message (e.g., a sensing notification message or notification address sent to the AMF 150b) based on the condition.

[0253] In operation 610, UE 110b may include the sensing service activation result in the N1 response message to be sent to AMF 150b.

[0254] In operation 611, AMF 150b may send a response message to SPF-CP 191b that includes a sensing service activation result (e.g., success or failure). In an embodiment, based on the N2 response message for each RAN (or cell) in operation 608, AMF 150b may include the sensing service activation result of the RAN (or cell) in the response message to be sent to SPF-CP 191b. In an embodiment, based on the N1 response message for each UE in operation 610, AMF 150b may include the sensing service activation result of the corresponding UE in the response message to be sent to SPF-CP 191b. In an embodiment, AMF 150b may send the sensing service activation result to SPF-CP 191b via one or more individual response messages or at least one integrated response message for one or more sensing nodes (e.g., RAN 120, UE 110b, or cell).

[0255] When SPF-CP 191b does not support aggregated responses, in operation 613, whenever a response message is received from each sensing node (e.g., the response message of operation 611), SPF-CP 191b may send a response message to SPF-UP 191a that includes the sensing activation result of each sensing node.

[0256] When SPF-CP 191b supports aggregated responses, in operation 612, SPF-CP 191b can aggregate the sensing service activation request results of each sensing node in the response message. In operation 613, SPF-CP 191b can send a response message (e.g., an aggregated response message) to SPF-UP 191a that includes the aggregated sensing service activation results.

[0257] When SPF-CP 191b supports aggregated responses, upon the expiration of the timer started in operation 606 or upon receiving a response message from operation 611 for all sense node IDs requested in operation 606, SPF-CP 191b may send an aggregated response message to SPF-UP 191a, including the sense activation results for each of the all sense nodes. In an embodiment, in operation 604, the aggregated response message may include a transaction ID generated by SPF-CP 191b in response to the request from SPF-UP 191a.

[0258] An aggregated response message may include at least one of the following information elements: - The sensing activation result (e.g., success or failure) for each UE corresponding to the UE ID included in the request message in operation 606; - The sensing activation result (e.g., success or failure) for each UE / RAN corresponding to the RAN ID included in the request message in Operation 606; or - The activation result (e.g., success or failure) of each UE / cell for each cell corresponding to the cell ID included in the request message in Operation 606.

[0259] In operation 614, SPF-UP 191a may include all or part of the response message received in operation 613 in the sensing response message to be sent to UE 110a.

[0260] In operation 615, each sensing node (e.g., RAN 120 or UE 110b) may send a sensing notification message to SPF-UP 191a. The sensing notification message may be sent directly from each sensing node to SPF-UP 191a, or via another NF (e.g., AMF 150b) to SPF-UP 191a. The sensing notification message may include at least one of the following information elements.

[0261] - Timestamp: Information related to the time when the sensed information was generated.

[0262] -Detection Node ID: The identifier of the detection node (e.g., UE ID, RAN ID, or cell ID).

[0263] - Sensing information: Information that indicates the sensing results. For example, in 3D map generation, sensing information may include information related to the 3D space in which the sensing was performed.

[0264] If needed, SPF-UP 191a can aggregate the sensing notification messages received in operation 615. In operation 616, based on the sensing notification triggering conditions received in operation 601, SPF-UP 191a can send (aggregated) sensing event notification messages to UE 110a via AMF 150a.

[0265] The (aggregated) sensing messages may include the following information.

[0266] - Transaction ID and / or sensing information for each sensing node (e.g., timestamp, sensing node ID, and / or sensing information)

[0267] Figure 7 This is a block diagram illustrating the configuration of a UE according to an embodiment of the present disclosure.

[0268] Reference Figure 7The UE (e.g., UE 110, UE 110a, or UE 110b) may include at least one of processor 701, transceiver 703, or memory 705. The UE is not limited to including only the components shown, and may include more or fewer components than those shown.

[0269] According to embodiments of this disclosure, transceiver 703 can transmit signals to and receive signals from at least one network entity (e.g., RAN 120, AMF150, or SPF-UP 191a) and / or at least one other UE. Signals transmitted and received between the network entity and the UE may include at least one of control information or data. Transceiver 703 can receive signals via a wireless channel to transmit those signals to processor 701, and can also transmit signals received from processor 701 via a wireless channel.

[0270] According to embodiments of this disclosure, processor 701 can control the operation of the UE to perform actions related to... Figures 4 to 6 The operation corresponding to at least one of the embodiments.

[0271] At least one of the processor 701, transceiver 703, or memory 705 need not be configured as a separate module, but can be configured as a single component in the form of a single chip. The processor 701 and transceiver 703 can be electrically connected. The processor 701 may include an application processor (AP) and / or a communication processor (CP).

[0272] According to embodiments of this disclosure, memory 705 may store data for operation of the UE, such as basic programs, application programs, and configuration information. Memory 705 may provide the stored data upon request from processor 701. Memory 705 may be configured as a storage medium, such as read-only memory (ROM), random access memory (RAM), hard disk, optical disc read-only memory (CD-ROM), and digital versatile disc (DVD), or a combination of storage media. Memory 705 may include multiple memories. Based on a program stored in memory 705 for performing at least one operation corresponding to an embodiment of this disclosure, processor 701 may perform at least one operation corresponding to an embodiment of this disclosure.

[0273] Figure 8 This is a block diagram illustrating the configuration of a network entity according to an embodiment of the present disclosure.

[0274] refer to Figure 8Network entities (e.g., at least one of SPF 191, SPF-UP 191a, SPF-CP 191b, RAN 120, AMF150, NRF 192, user NF 193, or NEF 194) may include at least one of processor 801, transceiver 803 including a transmitter and / or receiver, or memory 805. Network entities are not limited to including only the components shown and may include more or fewer components than those shown.

[0275] According to embodiments of this disclosure, transceiver 803 can transmit signals to and receive signals from at least one other network entity (e.g., at least one of SPF 191, SPF-UP 191a, SPF-CP 191b, RAN 120, AMF 150, NRF 192, user NF 193, NRF 192, or NEF 194) and / or at least one UE (e.g., UE 110). Signals transmitted and received between at least one other network entity and / or at least one UE may include at least one of control information or data. Figure 8 When the network entity shown is a base station (e.g., RAN 120), transceiver 803 may include a transceiver configured to send and receive radio signals to and from a UE (e.g., UE 110), and a transceiver or communication interface configured to send and receive signals to and from other network entities in the core network.

[0276] According to embodiments of this disclosure, processor 801 can control network entities to perform operations related to... Figures 2 to 6 At least one of the corresponding operations in the embodiments. The processor 801, transceiver 803, and memory 805 need not be configured as separate modules, but can be configured as a single component in the form of a single chip. The processor 801 and transceiver 803 can be electrically connected. The processor 801 may include an access point (AP) and / or a contention point (CP).

[0277] According to embodiments of this disclosure, memory 805 may store data for operations of network entities, such as basic programs, application programs, and configuration information. Memory 805 may provide the stored data upon request from processor 801. Memory 805 may be configured as a storage medium, such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Memory 805 may include multiple memories. Based on programs stored in memory 805 for performing at least one of the operations corresponding to embodiments of this disclosure, processor 801 may perform at least one of the operations corresponding to embodiments of this disclosure.

[0278] The UE (e.g., UE 110) according to embodiments of this disclosure can be one of various types of devices. The UE may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. The UE according to embodiments of this disclosure is not limited to those described above.

[0279] It should be understood that the embodiments of this disclosure and the terminology used therein are not intended to limit the technical features described herein to specific embodiments, and this disclosure includes various changes, equivalents, or alternatives to the corresponding embodiments. Regarding the description of the drawings, similar reference numerals may be used to denote similar or related elements. As used herein, each of phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” may include all possible combinations of items listed together in the corresponding phrase. Terms such as “first,” “second,” “first,” and “second” may be used simply to distinguish the corresponding element from another element and do not limit the element in other respects (e.g., importance or order). When the terms “operably” or “communically” are used, or when the terms “operably” or “communically” are not used, if an element (e.g., a first element) is referred to as “combined with another element (e.g., a second element),” “combined to another element (e.g., a second element),” “connected to another element (e.g., a second element),” or “connected to another element (e.g., a second element),” it means that the element can be directly (e.g., wired) connected to the other element, wirelessly connected to the other element, or connected to the other element via a third element.

[0280] As used in embodiments of this disclosure, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "component," or "circuit"). A "module" may be a single integrated component adapted to perform one or more functions, or its smallest unit or portion thereof. For example, according to an embodiment, a "module" may be implemented as an application-specific integrated circuit (ASIC).

[0281] Embodiments of this disclosure can be implemented as software (e.g., a program) comprising one or more instructions stored in a machine-readable storage medium (e.g., a UE). For example, a processor of the machine (e.g., a UE) can invoke and execute at least one of the one or more instructions stored in the storage medium. This allows the machine to be operated to perform at least one function according to the invoked at least one instruction. Each of the one or more instructions may include code generated by a compiler or code executed by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term "non-transitory" means only that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between locations where data is semi-permanently stored in the storage medium and locations where data is temporarily stored in the storage medium.

[0282] According to embodiments, methods according to various embodiments of this disclosure can be included and provided in a computer program product. The computer program product can be traded as a product between a seller and a buyer. The computer program product can be distributed in the form of a machine-readable storage medium (e.g., an optical disc read-only memory (CD-ROM)) or via an app store (e.g., the Play Store). TM The computer program product may be distributed online (e.g., downloaded or uploaded) or directly between two user devices (e.g., smartphones). If distributed online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium, such as the memory of a manufacturer's server, an app store's server, or a relay server.

[0283] According to embodiments, each of the above-described elements (e.g., a module or program) may include a single entity or multiple entities, and some of the multiple entities may also be separately located in another element. According to embodiments, one or more of the above-described elements may be omitted, or one or more other elements may be added. Alternatively or additionally, multiple elements (e.g., modules or programs) may be integrated into a single element. In this case, according to various embodiments, the integrated element may still perform one or more functions of each of the multiple elements in the same or similar manner as if one or more functions had been performed by a corresponding one of the multiple elements prior to integration. According to various embodiments, operations performed by a module, program, or other element may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more operations may be performed in a different order or omitted, or one or more other operations may be added.

[0284] Furthermore, the various embodiments described above can be used in combination as needed. For example, the methods proposed in this disclosure can be partially combined with each other to operate network entities and UEs. Moreover, although embodiments of this disclosure have been described based on 5G or NR systems, other variations of the technical ideas based on these embodiments can also be implemented in other communication systems such as LTE, LTE-A, or LTE-A-Pro systems.

[0285] It should be understood that various embodiments of the present disclosure as described in the claims and specification may be implemented in hardware, software, or a combination of hardware and software.

[0286] Any such software may be stored in a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores one or more computer programs (software modules), the one or more computer programs including computer-executable instructions that, when executed individually or jointly by one or more processors of an electronic device, cause the electronic device to perform the methods of this disclosure.

[0287] Any such software may be stored in the form of volatile or non-volatile memory, such as a storage device like read-only memory (ROM) (whether erasable or rewritable); or in the form of memory, such as random access memory (RAM), memory chips, devices, or integrated circuits; or stored on an optical or magnetically readable medium, such as an optical disc (CD), a digital versatile disc (DVD), a magnetic disk, or magnetic tape. It should be understood that storage devices and storage media are various embodiments of non-transitory machine-readable storage suitable for storing computer programs or storing computer programs including instructions that, when executed, implement various embodiments of this disclosure. Therefore, various embodiments provide a program comprising code for implementing the apparatus or method as described in any one of the claims of this specification, and a non-transitory machine-readable storage medium for storing such a program.

[0288] Although this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method for providing integrated sensing services by a network entity in a wireless communication system, the method comprising: Receive a request message from the first device for requesting sensing services related to at least one sensing node; Send a transmission request message to the Access and Mobility Management Function (AMF) associated with the at least one sensing node for requesting the activation of the sensing service based on the request message; as well as Receive at least one sensing event notification message from the at least one sensing node, the at least one sensing event notification message including sensing results based on the request message.

2. The method according to claim 1, wherein, The request message includes at least one of the following: user ID, requested sensing service type, requested sensing-related parameters for each sensing service type, parameters for each sensing service, requested sensing time, requested sensing service area, requested number of sensing nodes, requested sensing accuracy, sensing notification trigger information, list of sensing nodes, or sensing mode of each sensing node.

3. The method according to claim 1, further comprising: Receive at least one sensing response message from the AMF, the at least one sensing response message indicating the sensing service activation result of the at least one sensing node; as well as A sensing response message is sent to the first device, the sensing response message including the sensing service activation result of the at least one sensing node.

4. The method according to claim 3, further comprising: One or more sensing response messages received from the AMF are aggregated into a single aggregated response message; as well as Send the aggregated response message to the first device.

5. The method according to claim 1, wherein, The transmission request message includes at least one of the following: the Radio Access Network RAN ​​Node ID corresponding to the first sensing node of the RAN or cell, the cell ID, the sensing mode of each sensing node, the sensing service type, the sensing parameters of each service, the sensing area, the sensing time, the sensing accuracy, or the sensing notification triggering condition.

6. The method according to claim 1, wherein, The transmission request message includes at least one of the following for each sensing node corresponding to the second sensing node of the user equipment (UE): sensing mode, sensing service type, sensing parameters of each service, sensing area, sensing time, sensing accuracy, or sensing notification triggering condition.

7. The method according to claim 1, wherein, The first device includes at least one of a Network Exposure Function (NEF), a First AMF, or a User Equipment (UE).

8. The method according to claim 1, further comprising: Send a sensing event notification message, including the at least one sensing notification message, to the first device. The at least one sensing notification message includes at least one of a timestamp, a sensing node ID, or sensing information. The sensing event notification message includes at least one of the transaction ID or sensing information of each sensing node, and The sensing information of each sensing node includes at least one of the timestamp, the sensing node ID, or the sensing information.

9. A network entity for providing integrated sensing services in a wireless communication system, the network entity comprising: transceiver; as well as A processor, operatively connected to the transceiver, The processor is configured as follows: Receive a request message from the first device for requesting sensing services associated with at least one sensing node. Send a transport request message to the Access and Mobility Management Function (AMF) associated with the at least one sensing node to request the activation of the sensing service based on the request message, and Receive at least one sensing notification message from the at least one sensing node, the at least one sensing notification message including sensing results based on the request message.

10. The network entity according to claim 9, wherein, The request message includes at least one of the following: user ID, requested sensing service type, requested sensing-related parameters for each sensing service type, parameters for each sensing service, requested sensing time, requested sensing service area, requested number of sensing nodes, requested sensing accuracy, sensing notification trigger information, list of sensing nodes, or sensing mode of each sensing node.

11. The network entity according to claim 9, wherein, The processor is also configured to: Receive at least one sensing response message from the AMF, the at least one sensing response message indicating the sensing service activation result of the at least one sensing node; as well as A sensing response message is sent to the first device, the sensing response message including the sensing service activation result of the at least one sensing node.

12. The network entity according to claim 11, wherein, The processor is also configured to: Aggregate one or more sensing response messages received from the AMF into a single aggregated response message; and Send the aggregated response message to the first device.

13. The network entity according to claim 9, wherein, The transmission request message includes at least one of the following: the Radio Access Network RAN ​​Node ID corresponding to the first sensing node of the RAN or cell, the cell ID, the sensing mode of each sensing node, the sensing service type, the sensing parameters of each service, the sensing area, the sensing time, the sensing accuracy, or the sensing notification triggering condition.

14. The network entity according to claim 9, wherein, The transmission request message includes at least one of the following for each sensing node corresponding to the second sensing node of the user equipment (UE): sensing mode, sensing service type, sensing parameters of each service, sensing area, sensing time, sensing accuracy, or sensing notification triggering condition.

15. The network entity according to claim 9, in, The processor is further configured to send a sensing event notification message to the first device, including the at least one sensing notification message. The at least one sensing notification message includes at least one of a timestamp, a sensing node ID, or sensing information. The sensing event notification message includes at least one of the transaction ID or sensing information of each sensing node, and The sensing information of each sensing node includes at least one of the timestamp, the sensing node ID, or the sensing information.

Images