Method and apparatus for selecting sensing function / entity considering sensing service authorization in wireless communication system

The method addresses the challenge of integrating sensing services in 5G systems by authenticating and selecting appropriate UE or gNB entities, improving system performance and supporting advanced services.

WO2026235473A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096612
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face challenges in efficiently integrating and managing sensing services across connected devices, requiring enhanced methods to authenticate and select appropriate UE or gNB entities for sensing functions.

Method used

A method and apparatus are provided to authenticate sensing service requests and select suitable UE or gNB entities using 3GPP 5GS, involving network entities with interfaces, processors, and memory to execute instructions for sensing entity selection based on service area information.

Benefits of technology

Enables effective sensing services by authenticating and selecting appropriate entities, enhancing the functionality and performance of 5G systems in managing connected devices and supporting advanced services like metaverse and drone communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096612_12112026_PF_FP_ABST
    Figure KR2026096612_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to a wireless communication system and, more particularly, to a method for receiving a sensing service request from an AF via an NEF, authorizing the sensing service request on the basis of sensing service area information, and selecting at least one sensing entity on the basis of the sensing service request, and an apparatus capable of performing same.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for selecting a sensing function / entity considering sensing service authentication in a wireless communication system

[0001] The present disclosure relates to a wireless communication network, and more specifically, to a method for providing a sensing service using 3GPP 5GS (5G System). In particular, it relates to a method and apparatus for sensing an object by utilizing terminals that can also be used for communication with base stations built for existing communication.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The present disclosure relates to a wireless communication network, and more specifically, to a method for providing a sensing service using 3GPP 5GS (5G System). In particular, it relates to a method and apparatus for sensing an object by utilizing terminals that can also be used for communication with base stations built for existing communication. To this end, a method is required to authenticate a sensing service request and, in accordance with the authenticated request, to find and select a UE or gNB that supports the sensing function by utilizing 3GPP Air technology.

[0009] As one aspect of the present disclosure, a method performed by a network entity in a wireless communication system is provided, the method may include: receiving a sensing service request from an Application Function (AF) through a Network Exposure Function (NEF); authenticating the sensing service request based on sensing service area information; and selecting at least one sensing entity based on the sensing service request.

[0010] In one aspect of the present disclosure, a network entity in a wireless communication system comprises: at least one network interface; at least one processor connected to communicate with the network interface; and at least one memory connected to communicate with at least one processor and storing instructions that can be executed by at least one processor individually or in any combination thereof, and the network entity receives a sensing service request from an Application Function (AF) through a Network Exposure Function (NEF), authenticates the sensing service request based on sensing service area information, and selects at least one sensing entity based on the sensing service request.

[0011] According to the present disclosure, Sensing Entity Selection for providing Sensing services is made possible by utilizing base stations and terminals built for communication in 3GPP 5GS (5G System).

[0012] FIG. 1 is a diagram illustrating 3GPP Integrated Sensing and Communication Modes according to one embodiment of the present disclosure.

[0013] FIG. 2 is a diagram showing the section where connection between Network Functions for 3GPP Integrated Sensing and Communication, Sensing Function selection, and Sensing Entity selection occur according to one embodiment of the present disclosure.

[0014] FIG. 3 is a flowchart illustrating a Sensing Entity Selection method for 3GPP Integrated Sensing and Communication according to one embodiment of the present disclosure.

[0015] FIGS. 4a and 4b are flowcharts illustrating the Discovery and Selection operation in which an AMF identifies a Location according to one embodiment of the present disclosure.

[0016] FIGS. 5a and 5b are flowcharts illustrating a Discovery and Selection operation in which an SF identifies a Location according to one embodiment of the present disclosure.

[0017] FIG. 6 is a block diagram of a terminal or user equipment according to one embodiment of the present disclosure.

[0018] FIG. 7 is a block diagram of a base station according to one embodiment of the present disclosure.

[0019] FIG. 8 is a block diagram of a network entity performing network functions according to one embodiment of the present disclosure.

[0020] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0021] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0022] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same or different reference numbers.

[0023] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0024] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0025] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.

[0026] As used in the embodiments of the present disclosure, the term “part” refers to a software or hardware component, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part” performs certain roles. However, the term including “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run on one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” In addition, the components and 'parts' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0027] As stated above, it should be noted that the blocks of each flowchart and combinations of flowcharts described in this disclosure may be executed by one or more computer programs including instructions. The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.

[0028] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors is a circuitry that performs processing and may include 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 network 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 (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry.

[0029] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0030] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), and said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed alone or collectively by one or more processors of an electronic device.

[0031] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program containing code for implementing a device or method according to any one of the claims of this specification, and a non-transient machine-readable storage medium storing such program.

[0032] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0033] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0034] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0035] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0036] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0037] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0038] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0039] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.

[0040] Furthermore, throughout this specification, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or essentially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same magnitude measured or applied in different situations, or may represent different magnitudes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the specification and claims.

[0041] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.

[0042] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.

[0043] Furthermore, the expressions 'if' and 'in case that' described in this disclosure or claims may be interpreted, depending on the context, as meaning 'when or upon,' 'in response to,' 'based on,' or 'according to,' and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes, provided that they do not impair the technical features of this disclosure.

[0044] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.

[0045] Additionally, the phrase "transmitting a message containing A and B" as described in this specification may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.

[0046] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.

[0047] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the circumstances presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.

[0048] The drawings or flowcharts described below illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.

[0049] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.

[0050] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they may be understood by interchangeably, substituted, or combined.

[0051] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in the 3GPP (3rd generation partnership project) Technical Specifications (TS).

[0052] Hereinafter, the base station, as the entity performing resource allocation for terminals, may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on a network. Additionally, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for wireless resource processing of the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU as described above.

[0053] The terminal may include a UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions.

[0054] In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station.

[0055] In addition, while a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0056] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."

[0057] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, ...), RRC (radio resource control), MAC (medium access control), CE (control element), NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0058] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI (downlink control information), a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.

[0059] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0060] For the convenience of the following description, the present disclosure uses terms and names defined in the 5GS and NR specifications, which are the most recent standards defined by the 3GPP (The 3rd Generation Partnership Project) among currently existing communication standards. However, the present disclosure is not limited to the above terms and names and may be applied equally to wireless communication networks conforming to other standards. In particular, the present disclosure may be applied to 3GPP 5GS / NR (5th generation mobile communication standards).

[0061] The present disclosure relates to a wireless communication network, and more specifically, it is possible to provide sensing services using 3GPP 5GS (5G System), such as detecting intrusions in a specific area or detecting passing vehicles in a specific area and providing periodic notifications. That is, existing base stations built for communication and terminals capable of being used for communication are utilized to sense objects. For sensing, the sensing entity(s) discover the object(s) that are the target of sensing. The sensing service is implemented by the Rx Sensing Entity receiving a signal generated by the Tx Sensing Entity that is diffracted, refracted, or reflected by the object, and then transmitting, collecting, and processing these received signals to obtain a final result. To provide sensing services using 5GS, first, a method is required to find and select a UE or gNB that supports sensing functions utilizing 5G NR.

[0062] The operating principle of the present disclosure will be explained in detail below with reference to the attached drawings.

[0063] FIG. 1 is a diagram illustrating 3GPP Integrated Sensing and Communication Modes according to one embodiment of the present disclosure.

[0064] To provide Sensing services using 3GPP 5GS (5G System), a UE or gNB that supports Sensing functions utilizing 5G NR can be used as the Sensing Entity. Additionally, Sensing Entities can be broadly divided into Tx Sensing Entities that generate signals and Rx Sensing Entities that receive signals. By broadly classifying whether the Tx Sensing Entity is a UE or a gNB, and further classifying whether the Rx Sensing Entity is a UE or a gNB, six Sensing Modes can be configured.

[0065] Sensing mode 1: UE sends Tx, the same UE sends Rx, and the Rx UE sends Sensing Data to CN.

[0066] Sensing mode 2: UE2 is the transceiver, another UE is the receiver, and the receiver UE transmits sensing data to the CN.

[0067] Sensing mode 3: UE sends Sensing Data to Tx, gNB to Rx, and Rx gNB to CN.

[0068] Sensing mode 4: gNB sends Sensing Data to Tx, the same gNB sends Rx, and the Rx gNB sends Sensing Data to CN.

[0069] Sensing mode 5: gNB2 is Tx, another gNB is Rx, and the Rx gNB transmits Sensing Data to CN.

[0070] Sensing mode 6: gNB sends Sensing Data to Tx, UE to Rx, and Rx UE to CN.

[0071] FIG. 2 is a diagram showing the section where connection between Network Functions for 3GPP Integrated Sensing and Communication, Sensing Function selection, and Sensing Entity selection occur according to one embodiment of the present disclosure.

[0072] An Application Function (AF) can request a Sensing Service Request to a Network Exposure Function (NEF) to request a service for sensing a specific object. The NEF can perform Service Request Authorization to determine whether to accept this request and select a Sensing Function (SF) to handle the Sensing Service. At this time, the NEF can refer to the AF-specific allowed service information stored in the Sensing Repository Function (SRF). The SF can verify whether it has the authority to use Sensing Entities that match the conditions included in the Sensing request transmitted through the NEF, and can select the necessary Sensing Entities. At this time, the SF can refer to the AF-specific service details stored in the SRF. Once the SF completes the configuration for performing services on the Sensing Entities, Sensing Data can be transmitted from the Sensing Entities to the SF, and the SF can process this Data to generate the result of the Sensing Service requested by the AF. Sensing data from gNB Sensing Entities to SF may be transmitted via the AMF (Access and Mobility Management Function) or via a direct path from gNB to SF. Sensing data from UE Sensing Entities to SF may be transmitted via the AMF or via the UPF (User Plane Function). The generated Sensing service results may be transmitted to AF via the NEF in the manner specified in the request, such as once, periodically, or whenever an event occurs.

[0073] FIG. 3 is a flowchart illustrating a Sensing Entity Selection method for 3GPP Integrated Sensing and Communication according to one embodiment of the present disclosure.

[0074] Specifically, it is possible to provide Sensing services using 3GPP 5GS (5G System). To do this, the Sensing service may be activated by an external request, or its activation status may be specified from the beginning based on the subscriber service information. The service activation process is as follows.

[0075] - Service / requester authentication / authorization: Authorization must be successful at this stage to proceed to subsequent steps.

[0076] - Service priority: It is necessary to check if there are priority requirements within the service request.

[0077] - Service profile / AoS (Area of ​​Service): Specifies the Service Area of ​​the RAN / UE to represent the gNBs and UEs corresponding to the Sensing Entity within the Service Area, and specifies Service Accuracy, which influences the number of gNBs and UEs required for this. Service Accuracy may include error probability, location error radius, and valid reporting time.

[0078] - Sensing mode: The six methods described in Fig. 1 can be explicitly indicated and set.

[0079] - Capability negotiation: You can further change the number of modes or gNBs / UEs.

[0080] - Sensor discovery & selection: The Sensing Entities that satisfy all the requirements of this process can be finalized.

[0081] In practice, the above steps may be completed in one go or repeated multiple times. For example, as proposed in Fig. 3, multiple steps may be repeated. After Authentication / Authorization is completed, the Coverage / Accuracy condition is checked. Subsequently, a Mode is selected, UEs and gNBs within the Coverage are selected, the number of UEs and gNBs is determined based on priority, the number of UEs and gNBs is determined to meet the Accuracy condition, and the number of UEs and gNBs is adjusted by checking the Capabilities of the UEs and gNBs. Then, depending on whether the Accuracy condition is satisfied, it is decided whether to repeat the process starting from Mode Selection or complete the Sensor discovery & selection step. Alternatively, even while performing Sensing Data Collection and generating Sensing Results through Sensing Data Processing, depending on whether the Accuracy condition is satisfied, the process may be repeated starting from Mode Selection or the Sensor discovery & selection step may be additionally performed.

[0082] FIGS. 4a and 4b are flowcharts illustrating the Discovery and Selection operation in which an AMF identifies a Location according to one embodiment of the present disclosure.

[0083] In step 0, gNBs can connect to the AMF to register information such as Sensing Entity information, Sensing Capabilities (Tx / Rx, ...), and Service Area (TAs, Ranges) in the SRF. This process may also take place during the gNBs' pre-configuration process. The SRF can be located in the UDM (Unified Data Management) or UDR (Unified Data Repository), or in the NRF (Network Repository Function), or it can be included in the SF, or it can be a separate, independent Network Function.

[0084] In step 0a, UEs can connect to the AMF and register information such as Sensing Entity information, Sensing Capabilities (Tx / Rx, ...), and Service Area (TAs, Ranges) in the SRF during the registration step.

[0085] In Step 1, the Application Function (AF) can send a Sensing Request to the NEF. At this time, location / geographical conditions, time conditions, accuracy requirements, etc., may be included. More specific parameters may be included as follows.

[0086] - Location

[0087] - Activation / deactivation time

[0088] - Service requester (for auth to provide the service)

[0089] - Installed sensors in the location (UE types, RAN node)

[0090] - Sensor IDs

[0091] - required AoS (static or dynamically)

[0092] - Min / max number of Sensors

[0093] - Assistance information

[0094] - Who will get notification

[0095] In Step 2, the NEF can convert Geographical Location conditions among the Location conditions into conditions used by 3GPP, such as Cell Location conditions. Additionally, the NEF can check with the SRF to verify whether the requesting AF is eligible to request the dl Sensing Service. The NEF may also be pre-configured to determine whether the corresponding AF is eligible to request the service. In this case, the information included is the same as that received in Step 1, but the converted Location conditions can be used. Subsequently, the NEF can select the SF responsible for the task by referring to the converted Location conditions. Alternatively, since SFs are configured for each AF, the NEF can select a configured SF. Afterward, the NEF can forward the Sensing Request received in Step 1 to the SF (Sensing Function) capable of collecting, processing, or handling Sensing information. Step 2 may be omitted if the AF has a close relationship with 5GS. If Step 2 is omitted, the Location conditions provided by the AF are conditions used by 3GPP, such as Cell Location conditions.

[0096] In Step 3, the Sensing Function (SF) can perform Sensing Entity Authorization by receiving the Service Priority and Service Profile corresponding to the AF from the SRF and comparing them with the conditions included in the request. Once SE Authorization is complete, the SF can transmit the Sensing Response (status, ...) containing the results to the AF via the NEF, as in Step 2a. Subsequently, the SF can perform the Sensing Entity Selection process. That is, it can determine the number of UEs and gNBs based on Mode, Coverage of UE and gNB, and Priority / Accuracy. Afterward, the SF can send a Subscription Request to the AMF to continuously provide information on UEs and base stations matching the Location conditions, and can receive the initial necessary information in the Response. At this time, the SF can identify the corresponding gNB ID and UE ID using the Sensor ID received from the UDM / UDR or SRF in step 1 or step 2, and add them to the candidate UEs and gNBs, or select gNBs and UEs by prioritizing the previously determined Location conditions. Whether to use only those gNBs and UEs that satisfy the Location conditions among the selected gNBs and UEs, use all gNBs and UEs that meet the Location conditions, or utilize only the intersection or union of the two can be stored in the SF or SRF, configured in the operator policy, or provided as input from the AF.

[0097] In Step 4, the AMF can retrieve Subscription information for each terminal from the UDM / UDR or SRF and verify whether it can support Sensing services. Additionally, the AMF can check the Policy Control Function (PCF) to verify Policy conditions regarding whether each UE can provide Sensing services. That is, when a UE transmits Sensing Data to the CN, it can retrieve information such as whether the data is aggregated via the Control Plane or the User Plane. Furthermore, since gNBs can also be utilized as Sensing Entities, if the ability to utilize each gNB as a Sensing Entity is recorded in the UDM / UDR or SRF, the AMF can verify and retrieve this information.

[0098] In step 5, AMF can identify gNBs and UEs that satisfy the Location condition by considering the conditions verified in step 4.

[0099] In step 6, the AMF can notify the SF of the gNBs and UEs identified in step 5 along with the Location condition. The SF can update the Sensing Entity Selection. That is, it can check whether the Accuracy condition is satisfied and adjust the number of UEs and gNBs.

[0100] In Step 7, the SF can send Sensing Selection requests to the gNBs, reflecting the decision results from Step 6. These requests may include the target gNBs and configuration parameters. Configuration parameters are those required for the gNBs to function as Tx / Rx Sensing Entities and may include the Tx / Rx frequency, the Sensing Data report period, whether to use the control plane for the Sensing Data Report, and the AMF ID, SMF ID, SF ID, Sensor ID, and Sensing Service ID when using the control plane. They may also include whether to use the User Plane for the Sensing Data Report, and in this case, the necessary UPF ID, SF ID, Session ID, SMF ID, Sensor ID, and Sensing Service ID. Each gNB can perform Sensing configuration based on the information received in Step 7 to operate as a Tx / Rx Sensing Entity, and can send a Sensing Selection Response to the SF to indicate that this step is complete. At this stage, the ID of each gNB can be included again by adding the parameters received in Step 7. If a situation arises where it is difficult to perform the request in Step 7 due to a change in the state of the gNB caused by reasons such as increased load, the gNB can notify the SF of this.

[0101] In Step 7a, the SF may send Sensing Selection requests to the UEs, reflecting the decision results from Step 6. These requests may include the target UEs and configuration parameters. Configuration parameters are those required for the UEs to function as Tx and Rx Sensing Entities and may include Tx / Rx frequency, sensing signal generation period, sensing data report period, whether to use the control plane for the sensing data report, and the AMF ID, SMF ID, SF ID, Sensor ID, and Sensing Service ID when using the control plane. They may also include whether to use the User Plane for the sensing data report and, in this case, the necessary UPF ID, SF ID, Session ID, SMF ID, Sensor ID, and Sensing Service ID. Each UE may perform sensing configuration based on the information received in Step 7a to operate as a Tx / Rx Sensing Entity, and may send a Sensing Selection Response to the SF to indicate that this step is complete. At this stage, the ID of each UE can be included again by adding the parameters received in step 7a. If a situation arises where it is difficult to perform the request in step 7a due to a change in the UE's state caused by increased load, movement of the UE, etc., the UE can notify the SF of this.

[0102] In step 7b, the SF may send Sensing Selection requests to gNB2s and UE2s, reflecting the decision results of step 6. (gNB2 refers to a gNB that operates exclusively as a Tx Entity, and UE2 refers to a UE that operates exclusively as a Tx Entity.) This may include the target gNB2s and UE2s and configuration parameters. Configuration parameters are those required for gNB2s and UE2s to function as Tx Sensing Entities, and may include the Tx frequency, sensing signal generation period, etc. Each gNB2 or each UE2 may perform Sensing configuration based on the information received in step 7b to enable it to operate as a Tx Sensing Entity, and may send a Sensing Selection Response to the SF to indicate that this step is complete. In this step, the ID of each gNB2 or each UE2 may be included again by adding the parameters received in step 7b. If a situation arises where it is difficult to perform the request in step 7b due to a change in the state of gNB2 caused by a load increase or a change in the state of UE2 caused by a load increase or movement of UE2, gNB2 or UE2 may notify SF of this.

[0103] In Step 8, the SF can perform the Sensing Entity Selection Update process based on the results obtained in Steps 7, 7a, and 7b. It can check the Accuracy condition and adjust the number of UEs and gNBs. If it is determined at this stage that the Accuracy condition cannot be satisfied, the process may be restarted from Step 3. Additionally, in Step 8, the SF can transmit the Sensing Response to the AF via the NEF. At this time, Status information such as "Received as Service Available" or "Service Unavailable" may be included.

[0104] In step 9, each gNB operates as an Rx Sensing Entity based on the information received in step 7 and can transmit Sensing Data to the SF. In this case, if the Control Plane is used, it can be connected to the SF via the AMF and SMF (Session Management Function). Alternatively, if the User Plane is used, it can be delivered to the SF via the UPF. Depending on the information received in step 7, additional signal transmission may be required to secure the transmission path necessary for transmitting Sensing Data.

[0105] In step 9a, each UE acts as an Rx Sensing Entity based on the information received in step 7a and can transmit Sensing Data to the SF. In this case, if the Control Plane is used, it can be connected to the SF via the RAN, AMF, and / or SMF. Alternatively, if the User Plane is used, it can be transmitted to the SF via the RAN and UPF. Depending on the information received in step 7a, additional signal transmission may be required to secure the transmission path necessary for transmitting Sensing Data.

[0106] In Step 10, the SF can collect, process, and handle the Sensing Data transmitted through Steps 9 and 9a. The SF can deliver a Sensing Result Notify message to the Notification recipient based on the processed results and conditions requested in Step 1 or Step 2. This message may include the Sensing processing results. For example, it may notify if an intrusion is detected in a specific area, or periodically notify the quantity of vehicles detected passing through a specific area. Additionally, if the accuracy check performed in Step 10 is not satisfactory, the process may restart from the Sensing Entity Selection step in Step 3.

[0107] FIGS. 5a and 5b are flowcharts illustrating a Discovery and Selection operation in which an SF identifies a Location according to one embodiment of the present disclosure.

[0108] In step 0, gNBs can connect to the AMF to register information such as Sensing Entity information, Sensing Capabilities (Tx / Rx, ...), and Service Area (TAs, Ranges) in the SRF. This process may also take place during the gNBs' pre-configuration process. The SRF can be located in the UDM (Unified Data Management) or UDR (Unified Data Repository), or in the NRF (Network Repository Function), or it can be included in the SF, or it can be a separate, independent Network Function.

[0109] In step 0a, UEs can connect to the AMF and register information such as Sensing Entity information, Sensing Capabilities (Tx / Rx, ...), and Service Area (TAs, Ranges) in the SRF during the registration step.

[0110] In Step 1, the Application Function (AF) can send a Sensing Request to the NEF. At this time, location / geographical conditions, time conditions, accuracy requirements, etc., may be included. More specific parameters may be included as follows.

[0111] - Location

[0112] - Activation / deactivation time

[0113] - Service requester (for auth to provide the service)

[0114] - Installed sensors in the location (UE types, RAN node)

[0115] - Sensor IDs

[0116] - required AoS (static 혹은 Dynamically)

[0117] - Min / max number of Sensors

[0118] - Assistance information

[0119] - Who will get notification

[0120] In Step 2, the NEF can convert Geographical Location conditions among the Location conditions into conditions used by 3GPP, such as Cell Location conditions. Additionally, the NEF can check with the SRF to verify whether the requesting AF is eligible to request the dl Sensing Service. The NEF may also be pre-configured to determine whether the corresponding AF is eligible to request the service. In this case, the information included is the same as that received in Step 1, but the converted Location conditions can be used. Subsequently, the NEF can select the SF responsible for the task by referring to the converted Location conditions. Alternatively, since SFs are configured for each AF, the NEF can select a configured SF. Afterward, the NEF can forward the Sensing Request received in Step 1 to the SF (Sensing Function) capable of collecting, processing, or handling Sensing information. Step 2 may be omitted if the AF has a close relationship with 5GS. If Step 2 is omitted, the Location conditions provided by the AF may be conditions used by 3GPP, such as Cell Location conditions.

[0121] In Step 3, the Sensing Function (SF) can perform Sensing Entity Authorization by receiving the Service Priority and Service Profile corresponding to the AF from the SRF and comparing them with the conditions included in the request. Once SE Authorization is complete, the SF can transmit the Sensing Response (status, ...) containing the results to the AF via the NEF, as in Step 2a. Subsequently, the SF can perform the Sensing Entity Selection process. That is, it can determine the number of UEs and gNBs based on Mode, Coverage of UEs and gNBs, and Priority / Accuracy. At this stage, the SF can use the Sensor ID received from the UDM / UDR or SRF in Step 1 or 2 to identify the corresponding gNB ID and UE ID; it may add candidate UEs and gNBs, or it may select gNBs and UEs by prioritizing the previously determined Location conditions. Whether to use only those gNBs and UEs that satisfy the Location condition among those selected in this way, to use all gNBs and UEs that meet the Location condition, or to use only the intersection or union of the two, can be stored in SF or SRF, configured in the operator policy, or provided as input from AF.

[0122] In step 4, SF can send a Subscription Request to AMF to continue providing location information of the UE and base station confirmed in step 3, and can receive the information initially needed in the Response.

[0123] In step 5, AMF can verify the location of the gNB and UEs identified in step 4 and notify SF.

[0124] In step 6, the SF can re-verify whether the gNBs and UEs identified in step 5 meet the Location condition. The SF can update the Sensing Entity Selection. That is, it can check whether the Accuracy condition is satisfied and adjust the number of UEs and gNBs.

[0125] In Step 7, the SF can send a Sensing Selection request to the gNBs, reflecting the decision results from Step 6. This may include the target gNBs and configuration parameters. Configuration parameters are those required for the gNBs to function as Tx / Rx Sensing Entities and may include the Tx / Rx frequency, the Sensing Data report period, whether to use the control plane for the Sensing Data Report, and the AMF ID, SMF ID, SF ID, Sensor ID, and Sensing Service ID when using the control plane. It may also include whether to use the User Plane for the Sensing Data Report, and in this case, the necessary UPF ID, SF ID, Session ID, SMF ID, Sensor ID, and Sensing Service ID. Each gNB can perform Sensing configuration based on the information received in Step 7 to operate as a Tx / Rx Sensing Entity, and can send a Sensing Selection Response to the SF to indicate that this step is complete. At this stage, the ID of each gNB can be included again by adding the parameters received in Step 7. If a situation arises where it is difficult to perform the request in Step 7 due to a change in the state of the gNB caused by reasons such as increased load, the gNB can notify the SF of this.

[0126] In Step 7a, the SF may send Sensing Selection requests to the UEs, reflecting the results of the decision in Step 6. This may include the target UEs and configuration parameters. Configuration parameters are those required for the UEs to function as Tx and Rx Sensing Entities and may include Tx / Rx frequency, sensing signal generation period, sensing data report period, whether to use the control plane for the sensing data report, and the AMF ID, SMF ID, SF ID, Sensor ID, and Sensing Service ID when using the control plane. It may also include whether to use the User Plane for the sensing data report, and in this case, the necessary UPF ID, SF ID, Session ID, SMF ID, Sensor ID, and Sensing Service ID. Each UE may perform sensing configuration based on the information received in Step 7a to operate as a Tx / Rx Sensing Entity, and may send a Sensing Selection Response to the SF to indicate that this step is complete. At this stage, the ID of each UE can be included again by adding the parameters received in step 7a. If a situation arises where it is difficult to perform the request in step 7a due to a change in the UE's state caused by increased load, movement of the UE, etc., the UE can notify the SF of this.

[0127] In step 7b, the SF may send a Sensing Selection request to gNB2s and UE2s, reflecting the decision results of step 6. (gNB2 refers to a gNB that operates exclusively as a Tx Entity, and UE2 refers to a UE that operates exclusively as a Tx Entity.) This may include the target gNB2s and UE2s and configuration parameters. Configuration parameters are those required for gNB2s and UE2s to function as Tx Sensing Entities, and may include the Tx frequency and the Sensing signal generation period. Each gNB2 or each UE2 may perform Sensing configuration based on the information received in step 7b to enable it to operate as a Tx Sensing Entity, and may send a Sensing Selection Response to the SF indicating that this step is complete. In this step, the ID of each gNB2 or each UE2 may be included again by adding the parameters received in step 7b. If a situation arises where it is difficult to perform the request in step 7b due to a change in the state of gNB2 caused by a load increase or a change in the state of UE2 caused by a load increase or movement of UE, gNB2 or UE2 may notify SF of this.

[0128] In Step 8, the SF can perform the Sensing Entity Selection Update process based on the results obtained in Steps 7, 7a, and 7b. It can check the Accuracy condition and adjust the number of UEs and gNBs. If it is determined at this stage that the Accuracy condition cannot be satisfied, the process may be restarted from Step 3. Additionally, in Step 8, the SF can transmit the Sensing Response to the AF via the NEF. At this time, Status information such as "Received as Service Available" or "Service Unavailable" may be included.

[0129] In step 9, each gNB can operate as an Rx Sensing Entity based on the information received in step 7 and transmit Sensing Data to the SF. In this case, if the Control Plane is used, it can be connected to the SF via the AMF and SMF. Alternatively, if the User Plane is used, it can be transmitted to the SF via the UPF. Depending on the information received in step 7, additional signal transmission may be required to secure the transmission path necessary for transmitting Sensing Data.

[0130] In step 9a, each UE can act as an Rx Sensing Entity based on the information received in step 7a and transmit Sensing Data to the SF. In this case, if the Control Plane is used, it can be connected to the SF via the RAN, AMF, and / or SMF. Alternatively, if the User Plane is used, it can be transmitted to the SF via the RAN and UPF. Depending on the information received in step 7a, additional signal transmission may be required to secure the transmission path necessary for transmitting Sensing Data.

[0131] In Step 10, the SF can collect, process, and handle the Sensing Data transmitted through Steps 9 and 9a. The SF can deliver a Sensing Result Notify message to the Notification recipient based on the processed results and conditions requested in Step 1 or Step 2. This message may include the Sensing processing results. For example, it may notify if an intrusion is detected in a specific area, or periodically notify the quantity of vehicles detected passing through a specific area. Additionally, if the accuracy check performed in Step 10 is not satisfactory, the process may restart from the Sensing Entity Selection step in Step 3.

[0132] FIG. 6 is a block diagram of a terminal or user equipment (600) according to one embodiment of the present disclosure.

[0133] The terminal (600) is an electronic device capable of wireless communication and may include user equipment (UE), mobile phones, smartphones, tablets, Internet of Things (IoT) devices having various form factors, and can perform wireless communication with a base station through a wireless channel.

[0134] Referring to FIG. 6, the terminal (600) may include at least one transceiver (601) (hereinafter, transceiver), at least one processor (602) (hereinafter, processor), and at least one memory (603) (hereinafter, memory). The transceiver (601), processor (602), and memory (603) of the terminal (600) may be operated according to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure. However, the components of the terminal (600) are not limited to the examples of components shown in FIG. 6. In other embodiments, the terminal (600) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (601), processor (602), or memory (603) may be integrated into a single component.

[0135] The transceiver (601) may be a basic communication circuit or communication circuitry that enables the terminal (600) to perform wireless communication with a node or entity of a network. For example, the transceiver (601) may enable the terminal (600) to transmit and receive signals to and from a base station via cellular wireless communication, or to transmit and receive signals to and from another terminal via cellular wireless communication. For example, the transceiver (601) may be 3G (3rd generation), 4G (4th generation), LTE (long-term evolution), 5G (5th generation), NR (new radio), 6G (6th It can support at least one of various cellular wireless communication technologies including (generation), and the various cellular wireless communication technologies supported by the transceiver (601) may include all subsequent evolved generations of wireless communication.

[0136] According to one embodiment, the terminal (600) may include a plurality of transceivers, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access)-NR dual connectivity), it may include a first transceiver supporting 4G LTE wireless communication and a second transceiver supporting 5G NR wireless communication. According to another embodiment, when the terminal (600) supports NR-DC (NR Dual Connectivity), the terminal (600) may include a plurality of transceivers supporting 5G NR wireless communication. According to another embodiment, if the terminal (600) supports short-range wireless communication, the terminal (600) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).

[0137] According to one embodiment, the transceiver (601) may include various circuit structures used to transmit and receive signals to and from a base station via a wireless channel. The signals may include control information and data. For example, the transceiver (601) may be configured to include a radio frequency (RF) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (601) may output the signal received via the wireless channel to a processor (602) and transmit the signal output from the processor (602) via the wireless channel.

[0138] The processor (602) can control the overall operation of the terminal (600) according to an embodiment of the present disclosure. The processor (602) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (602) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (603) individually, collectively, or in any combination. Additionally, the processor (602) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0139] The processor (602) is electrically, operatively, or communicatively coupled to the transceiver (601) so as to control the transceiver (601).

[0140] The processor (602) may include at least one processor (or, processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (602) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (602) may be included in one chip, and another part of the processor (602) may be included in a separate chip. Alternatively, at least one processor may be included in other components, e.g., a transceiver (601) or a memory (603).

[0141] The processor (602) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (602) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (602) may control other components of the terminal (600) to perform various operations by executing computer programs, code, or instructions stored in memory (603).

[0142] Memory (603) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (603) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0143] The memory (603) can be electrically, operatively, or communically coupled with the processor (602) and can be accessed by the processor (602).

[0144] A computer program, code, or instruction that can be executed by a processor (602) may be stored in the memory (603). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (602) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (602) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (603).

[0145] According to one embodiment of the present disclosure, the operation of the terminal (600) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (603), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0146] FIG. 7 is a block diagram of a base station (700) according to one embodiment of the present disclosure.

[0147] The base station (700) can perform wireless communication with at least one terminal within the area of ​​the base station (700) through a wireless channel.

[0148] Referring to FIG. 7, a base station (700) may include at least one transceiver (701) (hereinafter, transceiver), at least one processor (702) (hereinafter, processor), and at least one memory (703) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (701), processor (702), and memory (703) of the base station (700) may be operated. However, the components of the base station (700) are not limited to the examples of components shown in FIG. 7. In other embodiments, the base station (700) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (701), processor (702), or memory (703) may be integrated into a single component.

[0149] The transceiver (701) may be a communication circuit or communication circuitry that enables the base station (700) to perform wireless communication with a node or entity of the network. For example, the transceiver (701) may enable the base station (700) to transmit and receive signals to and from a terminal (600) via cellular wireless communication or to transmit and receive signals to and from other network entities via wireless communication. For example, the transceiver (701) may be 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation) Various cellular wireless communication technologies, including (generation), etc., can be supported, and the various cellular wireless communication technologies supported by the transceiver (701) may include all subsequent evolved generations of wireless communication. According to one embodiment, the transceiver (701) may include various circuit structures used to transmit and receive signals to and from a terminal via a wireless channel. The signals may include control information and data. For example, the transceiver (701) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (701) may output the signal received via the wireless channel to a processor (702) and transmit the signal output from the processor (702) via the wireless channel.

[0150] Meanwhile, according to one embodiment of the present disclosure, a base station (700) may communicate with an entity or node of a network via wired or wireless communication. For example, the base station (700) may communicate via wired or wireless communication with an entity or node of an adjacent base station or core network via a backhaul network. Although not shown in the drawings, when the base station (700) performs wired communication, the base station (700) may include a separate network interface for wired communication in addition to the transceiver (701). The network interface may be referred to as network interface circuitry, communication interface circuitry, etc.

[0151] The processor (702) can control the overall operation of the base station (700) according to an embodiment of the present disclosure. The processor (702) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (702) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (703) individually, collectively, or in any combination. Additionally, the processor (702) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0152] The processor (702) is electrically, operatively, or communicatively coupled to the transceiver (YY01) so as to control the transceiver (701).

[0153] The processor (702) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (702) may be included in one chip, and another part of the processor (702) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a transceiver (701) or memory (703).

[0154] The processor (702) may perform, cause, or control the operation of a base station to execute at least one or a combination of methods according to embodiments of the present disclosure. For example, the processor (702) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (702) may control other components of the base station (700) to perform various operations by executing computer programs, codes, and instructions stored in memory (703).

[0155] Memory (703) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (703) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0156] The memory (703) can be electrically, operatively, or communically coupled with the processor (702) and can be accessed by the processor (702).

[0157] A computer program, code, or instruction that can be executed by a processor (702) may be stored in the memory (703). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (702) may be stored in a single memory device or may be separated and distributed among two or more memory devices. The processor (702) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (703).

[0158] According to one embodiment of the present disclosure, the operation of the base station (700) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (703), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0159] A terminal or a base station can perform various communication procedures related to the control plane or user plane by interacting with network entities based on communication through a wireless channel. For example, a terminal can communicate with network entities such as an access and mobility management function (AMF) or a session management function (SMF) through a base station. Alternatively, the base station can perform at least one communication procedure by directly transmitting and receiving signals or relaying them with network entities. The structure of the above-mentioned network entities will be explained in more detail through the drawings below.

[0160] FIG. 8 is a block diagram of a network entity (800) that performs network functions according to one embodiment of the present disclosure.

[0161] A network entity (800) may include one or more network functions (NF) that constitute a core network (e.g., 5G (5th generation) core, 5GC) in a communication system, or entities (devices, devices, nodes, or servers, etc.) that perform part of a network function. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across multiple network entities. Additionally, when an NF is implemented within a network entity, the NF may be implemented in the form of software, and in such cases, a program for running the NF may be loaded into the memory of the network entity (800).

[0162] A single NF can be implemented as one or more instances and can operate by being distributed across the same network entity or multiple network entities. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.

[0163] The above NF may include any one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), a data network (DN), a Sensing Function (SF), or a Sensing Repository Function (SRF).

[0164] Referring to FIG. 8, a network entity (800) may include at least one network interface (801), at least one processor (802) (hereinafter, processor), and at least one memory (803) (hereinafter, memory). As described above, the NF may be implemented in the form of a physical device such as the network entity (800), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as illustrated in FIG. 8. In such cases, the instance may be composed of one or more logical functional units and may be logically represented.

[0165] According to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure, the network interface (801), processor (802), and memory (803) of the network entity (800) may be operated. However, the components of the network entity (800) are not limited to the examples of components shown in FIG. 8. In other embodiments, the network entity (800) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in one embodiment, the network interface (801), processor (802), or memory (803) may be implemented as a single component.

[0166] The network interface (801) is a collective term for the transmitting and receiving parts of a network entity and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or other network entities. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the network interface (801) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network entities via wireless or wired communication. The network interface (801) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol). Depending on the convenience of explanation and technical implementation, the network interface (801) may be referred to as a transceiver, a communication circuitry, a network interface circuitry, or a communication interface circuitry.

[0167] A processor (802) may control the overall operation of a network entity (800) according to an embodiment of the present disclosure. In one embodiment, the processor (802) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (802) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (803) individually, collectively, or in any combination. Additionally, the processor (802) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (802) may not necessarily be composed of physical hardware when the network function (800) is implemented in an instance form according to another embodiment.

[0168] According to one embodiment, the processor (802) is electrically, operatively, or communicatively coupled to the network interface (801) so as to control the network interface (801).

[0169] The processor (802) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a specific embodiment, at least one part of the processor (802) may be included in one chip, and another part of the processor (802) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a network interface (801) or memory (803).

[0170] The processor (802) may perform or control the operation of a network entity (800) to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (802) may control the operation of the network entity (800) to exchange control plane messages or user plane messages with terminals, base stations, or other core network entities via wireless or wired communication using various protocols (e.g., NAS protocols). To this end, the processor (802) may control other components of the network entity (800) to perform various operations by executing computer programs, code, or instructions stored in memory (803).

[0171] Memory (803) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (803) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0172] According to one embodiment, the memory (803) may be electrically, operatively, or communically coupled with the processor (802) and may be accessed by the processor (802).

[0173] A computer program, code, or instruction that can be executed by a processor (802) may be stored in the memory (803). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (802) may be stored in a single memory or separated and distributed across two or more memories. The processor (802) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (803).

[0174] According to one embodiment of the present disclosure, the operation of a network entity (800) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (803), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions.

[0175] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0176] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present invention.

[0177] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0178] In addition, the above program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present invention through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present invention.

[0179] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0180] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. A method performed by a network entity in a wireless communication system, A step of receiving a sensing service request from an Application Function (AF) through a Network Exposure Function (NEF); A step of authenticating the sensing service request based on sensing service area information; and A method comprising the step of selecting at least one sensing entity based on the above-mentioned sensing service request.

2. The method of claim 1, wherein the network entity is selected by the NEF based on the sensing service area information.

3. In Paragraph 1, A method further comprising the step of updating the selection of at least one sensing entity.

4. In Paragraph 1, A method further comprising the step of processing sensing data obtained from at least the sensing entity.

5. In Paragraph 1, The step of selecting at least one sensing entity is, A method comprising the step of selecting at least one sensing entity based on the above sensing service area information.

6. The method of claim 1, wherein the at least one sensing entity comprises at least one base station.

7. In claim 2, the method wherein the network entity is selected by the NEF based on set information.

8. In Paragraph 1, A method further comprising the step of transmitting a sensing selection request including setting parameters to at least one sensing entity.

9. Regarding network entities in wireless communication systems, At least one network interface; At least one processor connected to communicate with the above network interface; and It includes at least one memory connected to communicate with the at least one processor and storing instructions that can be executed by the at least one processor individually or in any combination thereof. The above network entity is, Receives a sensing service request from the AF (Application Function) through the NEF (Network Exposure Function), and Authenticate the above sensing service request based on the sensing service area information, and A network entity that selects at least one sensing entity based on the above sensing service request.

10. In claim 9, the network entity is a network entity selected by the NEF based on the sensing service area information.

11. In Paragraph 9, The above network entity is, A network entity that updates the selection of at least one sensing entity.

12. In Paragraph 9, The above network entity is, A network entity that processes sensing data obtained from at least the above-mentioned sensing entity.

13. In Paragraph 9, The above network entity is, A network entity that selects at least one sensing entity based on the above sensing service area information.

14. In claim 9, the at least one sensing entity is a network entity comprising at least one base station.

15. In claim 10, the network entity is a network entity selected by the NEF based on set information.