Method and device for providing combined service including base station-based sensing and communication

Abstract

The present disclosure relates to a method and a device for effectively providing a combined service including base station-based sensing and communication. More specifically, the present disclosure relates to: a method for exchanging messages between a base station and a sensing function (SF) in order to provide a combined service including base station-based sensing and communication in a wireless communication system; a method for acquiring mutual information by a base station and an SF; a method for indicating a base station to perform sensing; a method for indicating a base station or an SF to calculate a sensing result; and a method and a device for making a report to an entity having requested sensing by a base station or an SF.

Description

Method and device for providing a combined service of base station-based sensing and communication

[0001] The present disclosure relates generally to wireless communication systems, and more particularly, to methods and devices for providing a combined service of base station-based sensing and communication in a wireless communication system.

[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 the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

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

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

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] As a result of the development of mobile communication systems and the aforementioned advancements in technology, various services have become available, and methods for effectively providing these services are being demanded. In particular, methods for providing combined services of base station-based sensing and communication are being demanded.

[0009] The present disclosure provides a method and device for providing a combined service of base station-based sensing and communication in a wireless communication system.

[0010] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0011] A method for processing a control signal in a wireless communication system, characterized by comprising: a step of receiving a first control signal transmitted from a base station; a step of processing the received first control signal; and a step of transmitting a second control signal generated based on the processing to the base station.

[0012] According to one embodiment of the present disclosure, a device and method capable of effectively providing a combined service of base station-based sensing and communication can be provided.

[0013] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a wireless communication system can be provided.

[0014] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0015] FIG. 1 is a diagram illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 2 is a diagram illustrating a base station and core network entities of a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 3 is a diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0018] FIG. 4 is a diagram illustrating an example of providing an integrated sensing and communication (ISAC) service using one base station in a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 5 is a diagram illustrating an example of providing an ISAC service using two base stations in a wireless communication system according to one embodiment of the present disclosure.

[0020] FIG. 6 is a diagram illustrating the structure of a sensing function (SF) in a wireless communication system according to one embodiment of the present disclosure.

[0021] FIG. 7 is a diagram illustrating a communication protocol structure of a base station and an SF in a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 8 is a diagram illustrating a communication protocol structure of a base station and an SF in a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 9 is a diagram illustrating a communication protocol structure of a base station and an SF in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 10 is a diagram illustrating a communication protocol structure of a base station and an SF in a wireless communication system according to one embodiment of the present disclosure.

[0025] FIG. 11 is a diagram illustrating an example of a signal flow in which an SF obtains TRP (transmission-reception point) information of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0026] FIG. 12 is a diagram illustrating an example of a signal flow in which a base station acquires information on SF in a wireless communication system according to one embodiment of the present disclosure.

[0027] FIG. 13 is a diagram illustrating an example of a signal flow in which an SF sets a reference signal transmission to a base station in a wireless communication system according to one embodiment of the present disclosure.

[0028] FIG. 14 is a diagram illustrating an example of a signal flow in which an SF requests sensing from a base station in a wireless communication system according to one embodiment of the present disclosure.

[0029] FIG. 15 is a diagram illustrating an example of a signal flow in which a base station requests sensing from an SF in a wireless communication system according to one embodiment of the present disclosure.

[0030] FIG. 16 is a diagram illustrating an example of a signal flow in which an external client or an access and mobility management function (AMF) requests sensing in a wireless communication system according to one embodiment of the present disclosure.

[0031] FIG. 17 is a diagram illustrating an example of a signal flow in which an external client requests sensing in a wireless communication system according to one embodiment of the present disclosure.

[0032] FIG. 18 is a diagram illustrating an example of a signal flow in which a CU acquires TRP information of a DU in a base station CU (central unit)-DU (distributed unit) separation structure of a wireless communication system according to one embodiment of the present disclosure.

[0033] FIG. 19 is a diagram illustrating an example of a signal flow in which a CU sets a reference signal transmission to a DU in a base station CU-DU separation structure of a wireless communication system according to one embodiment of the present disclosure.

[0034] FIG. 20 is a diagram illustrating an example of a signal flow in which a CU requests sensing from a DU in a base station CU-DU separation structure of a wireless communication system according to one embodiment of the present disclosure.

[0035] FIG. 21 is a diagram illustrating an example of a signal flow for SF to provide ISAC service through two base stations in a wireless communication system according to one embodiment of the present disclosure.

[0036] FIG. 22 is a diagram illustrating an example of a signal flow for providing an ISAC service through two base stations in a structure in which an SF of a wireless communication system according to one embodiment of the present disclosure is located inside a base station.

[0037] FIG. 23 is a diagram illustrating an example of a signal flow in which a base station requests SF to calculate a sensing result in a wireless communication system according to one embodiment of the present disclosure.

[0038] FIG. 24 is a diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

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

[0040] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.

[0041] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0042] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present 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. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

[0043] In describing the embodiments of the present disclosure, the main target is New Radio (NR), which is a wireless access network, and the core network, packet core 5G System, or 5G Core Network, or NG Core (Next Generation Core) in the 5G mobile communication standard specified by 3GPP (3rd Generation Partnership Project), a mobile communication standard standardization organization. However, the main gist of the present disclosure can be applied to other communication systems with similar technical backgrounds with slight modifications within a range that does not significantly deviate from the scope of the present disclosure, and this will be possible at the discretion of a person skilled in the art of the present disclosure.

[0044] For convenience of explanation, some terms and names defined in the 3GPP standards (standards for 5G, NR, LTE, or similar systems) may be used below. However, the present disclosure is not limited by these terms and names, and can be equally applied to systems conforming to other standards.

[0045] Hereinafter, terms used in the description to identify connection nodes, terms referring to network objects (network entities), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms used in the present disclosure, and other terms referring to objects with equivalent technical meanings may be used.

[0046] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station.

[0047] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0048] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0049] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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'. Additionally, the components and '~units' may be implemented to play one or more central processing units (CPUs) within the device or secure multimedia card. In addition, in an embodiment, the '~unit' may include one or more processors.

[0050] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0051] In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0052] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

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

[0054] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0055] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0056] The present disclosure relates to a method and apparatus for providing a combined service of base station-based sensing and communication. More specifically, the present disclosure relates to a method for exchanging messages between a base station and a sensing function (SF) to provide a combined service of base station-based sensing and communication in a 3GPP system, a method for the base station and the SF to obtain information from each other, a method for instructing the base station to perform sensing, a method for instructing the base station or the SF to calculate sensing results, and a method and apparatus for the base station or the SF to report to an entity that has requested sensing.

[0057] FIG. 1 is a diagram illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0058] Referring to FIG. 1, a wireless access network of a wireless communication system (hereinafter, NR or 5G) may include a next-generation base station (new radio node B) (hereinafter, NR gNB, gNB or base station) (120) and a NR CN (new radio core network) (110). A user terminal (e.g., new radio user equipment) (hereinafter, NR UE or terminal) (150) may access an external network through the NR gNB (120) and the NR CN (110).

[0059] In Fig. 1, the NR gNB (120) may correspond to the eNB (140) of the LTE system. The NR gNB (120) is connected to the NR UE (150) via a wireless channel and may provide a service superior to that of the eNB (140). In a wireless communication system, since all user traffic is serviced through a shared channel, a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and the NR gNB (120) may be responsible for this. One NR gNB (120) can typically control multiple cells. In order to implement ultra-high-speed data transmission compared to LTE, a bandwidth greater than the maximum bandwidth of LTE can be used, and beamforming technology can be additionally grafted using the orthogonal frequency division multiplexing (OFDM) method as a wireless access technology. In addition, an Adaptive Modulation and Coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel status of the terminal can be applied. The NR CN (110) can perform functions such as mobility support and QoS setting. The NR CN (110) is a device that is responsible for various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations. In addition, the wireless communication system can be linked with the LTE system, and the NR CN (110) can be connected to the MME (130) through a network interface. The MME (130) can be connected to the eNB (140).

[0060] FIG. 2 is a diagram illustrating a base station and core network entities of a wireless communication system according to one embodiment of the present disclosure.

[0061] Referring to FIG. 2, the base station and core network entities of a wireless communication system can communicate with each other via a service-based interface (SBI) and a reference point interface. While FIG. 2 illustrates the use of a service-based interface, the communication interface between each network entity is not limited thereto, and the communication interface between each network entity may be a reference point interface.

[0062] According to one embodiment, the base station and core network entities may include at least one of the entities illustrated in FIG. 2 for providing location services (LCS), entities related to billing, entities related to transmitting and receiving user data, or entities supporting various functions of 5G and wireless communications. Furthermore, the operations of the following network functions have been described primarily with respect to functions for providing LCS, and various functions not described in the present disclosure may be included for wireless communications.

[0063] According to one embodiment, a network exposure function (NEF) (201) can provide location services to an internal or external AF (204). The AF (204) can access the location services through the NEF (201) and an API. Based on QoS requirements, the NEF (201) can forward a location request to the GMLC (208) or request event exposure to the AMF (206). When the NEF (201) uses event exposure to the AMF (206), the NEF (201) can request at least one of routing information or privacy information of the target UE (211) from the UDM (203).

[0064] According to one embodiment, the unified data repository (UDR) (202) may include privacy information of UEs (211) that are targets of location services. When the AMF (206) receives new privacy information of the UE (211), the AMF (206) may update the privacy information of the UE (211) stored in the UDR (202) through the UDM (203).

[0065] According to one embodiment, a unified data management (UDM) (203) may include an LCS subscriber's LCS privacy profile and routing information. The UDM (203) may be accessible from at least one of the AMF (206), the GMLC (208), or the NEF (201).

[0066] According to one embodiment, an application function (AF) (204) can access the LCS service through at least one of a GMLC (208) or an AMF (206). An external AF (204) can access the LCS service through a NEF (201).

[0067] According to one embodiment, the network data analytics function (NWDAF) (205) can directly access the GMLC (208) to collect UE (211) location information.

[0068] According to one embodiment, an access and mobility management function (AMF) (206) may include location request and positioning management functions for a target UE (211). The AMF may have access to the GMLC (208) and the NEF (201). The AMF may have access to the N2 reference point for the RAN (212). The AMF may have access to the N1 reference point for the UE (211).

[0069] According to one embodiment, a location management function (LMF) (207) may manage overall management and resource scheduling for location services for a UE (211) registered or accessing a 5G core network. In addition, the LMF (207) may perform at least one of result calculation or verification for the location and velocity of the target UE (211). The LMF (207) may receive a location request from a serving AMF (206) of the UE (211). The LMF (207) may exchange information for UE-assisted or UE-based location estimation with the UE (211). The LMF (207) may exchange information for obtaining location information with the RAN (212), a non-3GPP interworking function (N3IWF), or a trusted non-3GPP access network (TNAN).

[0070] According to one embodiment, a gateway mobile location center (GMLC) (208) may include functions to support LCS. One or more GMLC entities may exist in a PLMN. The GMLC (208) communicates with an external LCS client (210) using an Le reference point, and the AF (204) and NF (network functions) may access the GMLC (208) directly or through the NEF (201). The GMLC (208) may request routing information and / or privacy information of a target UE (211) from the UDM (203). The GMLC (208) may perform at least one of authentication of the external LCS client (210) or the AF (204) and privacy verification of the target UE (211), and then forward the location request to the serving AMF (206).

[0071] According to one embodiment, a location retrieval function (LRF) (209) may be collocated with or operated separately from the GMLC (208). The LRF (209) may receive and verify location information and provide routing and correlation information for the UE (211) that performed the IMS emergency session.

[0072] In one embodiment, an LCS client (location service client) (210) can access an LCS service through a GMLC (208). The LCS client (210) can communicate with the GMLC (208) using an Le reference point.

[0073] According to one embodiment, a user equipment (UE) (211) can support four modes: UE-assisted mode (performs location measurement and transmits the measurement result to another entity (e.g., LMF) to calculate location), UE-based mode (performs location measurement and calculates location using assistance data received from a serving PLMN), standalone mode (performs location measurement and calculates location without assistance data received from a serving PLMN), and network-based mode (serving PLMN measures the signal transmitted by the UE and calculates location).

[0074] According to one embodiment, a radio access network (RAN) (212) may be used for various procedures for positioning a target UE (211). The radio access network (RAN) 212 may transmit a positioning message between the target UE (211) and an AMF (206) or LMF (207).

[0075] FIG. 3 is a diagram illustrating the structure of a base station according to an embodiment of the present disclosure.

[0076] Referring to FIG. 3, the base station may include a transceiver (305), a control unit (310), and a storage unit (315). The transceiver (305), the control unit (310), and the storage unit (315) may operate depending on the communication method of the base station. The network device may correspond to the structure of the base station. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. For example, the base station may include a transceiver (305) and a control unit (310). For example, the transceiver (305), the control unit (310), and the storage unit (315) of the base station may be implemented in the form of a single chip.

[0077] According to one embodiment, the transceiver (305) is a general term for the reception unit and the transmission unit of the base station, and can transmit and receive signals with terminals, other base stations, or other network devices. At this time, the transmitted and received signals may include control information and data. For example, the transceiver (305) may transmit system information to the terminal. The transceiver (305) may transmit at least one of a synchronization signal or a reference signal. To this end, the transceiver (305) may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts a received signal. However, this is only one embodiment of the transceiver (305), and the components of the transceiver (305) are not limited to the RF transmitter and the RF receiver. For example, the transceiver (305) may include a wired or wireless transceiver, and may include various configurations for transmitting and receiving signals. In addition, the transceiver (305) can receive a signal through a communication channel (e.g., a wireless channel) and output it to the control unit (310). The transceiver (305) can transmit the signal output from the control unit (310) through the communication channel. In addition, the transceiver (305) can receive the communication signal and output it to the processor. The transceiver (305) can transmit the signal output from the processor to at least one of a terminal, another base station, or another entity through a wired or wireless network.

[0078] According to one embodiment, the storage unit (315) can store programs and data required for the operation of the base station. The storage unit (315) can store control information or data included in a signal acquired from the base station. The storage unit (315) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. The storage unit (315) can store at least one of information transmitted and received through the transceiver unit (305) and information generated through the control unit (310).

[0079] In the present disclosure, the control unit (310) may be defined as a circuit, an application-specific integrated circuit, or at least one processor. In one embodiment, the processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. In one embodiment, the control unit (310) may control the overall operation of the base station according to the embodiment proposed in the present disclosure. For example, the control unit (310) may control the signal flow between each block to perform operations according to a flowchart.

[0080] FIG. 4 is a diagram illustrating an example of providing an integrated sensing and communication (ISAC) service using one base station in a wireless communication system according to one embodiment of the present disclosure.

[0081] Referring to FIG. 4, the base station (410) can transmit reference signals (411, 413, 415). The base station (410) can receive a signal that has been modified by reflection, scattering, or diffraction of the transmitted reference signals (411, 413, 415) from a target object (e.g., 420) or an environment object (e.g., 430, 440). The modified signal received again by the base station (410) can be a sensing signal (412, 414, 416). The base station (410) can transmit the reference signals (411, 413, 415) at one time. The base station (410) can change the direction of the transmitting beam and transmit reference signals (411, 413, 415) respectively.

[0082] According to one embodiment, the base station (410) can use the reference signals (411, 413, 415) not only for sensing purposes but also for communication purposes. The reference signals (411, 413, 415) used by the base station (410) for communication purposes may be signals (e.g., primary / secondary synchronization signal, synchronization signal / PBCH block, positioning reference signal, cell-specific reference signal, tracking reference signal, demodulation reference signal) that a terminal receiving a wireless mobile communication service can use for channel estimation, time synchronization, data transmission / reception, position estimation, etc.

[0083] According to one embodiment, the target object (e.g., 420) may be an object to be sensed via the ISAC service. The environment objects (e.g., 430, 440) may be objects other than the target object (e.g., 420). The characteristics of each object (420, 430, 440) may be distinguished by RCS (radar cross section) or micro-Doppler difference. For example, the size, shape, material, etc. of the object may be distinguished through sensing signals (412, 414, 416).

[0084] According to one embodiment, when a base station (410) transmits reference signals (411, 413, 415) at regular time intervals or for a continuous time and receives sensing signals (412, 414, 416) at regular time intervals or for a continuous time, the base station (410) can measure the velocity and direction of a target object (e.g., 420) or an environment object (e.g., 430, 440).

[0085] According to one embodiment, the resolution and range for sensing a target object (e.g., 420) or an environment object (e.g., 430, 440) may vary depending on the bandwidth and frequency pattern of the frequency transmitting the reference signal (411, 413, 415).

[0086] According to one embodiment, the function of detecting or sensing an object by identifying and mapping the characteristics of an object that may not have the ability to connect to a wireless communication network through an operation in which a base station (410) transmits reference signals (411, 413, 415) and receives sensing signals (412, 414, 416) in which the reference signals (411, 413, 415) interact with an object may be referred to as ISAC. A wireless communication system can provide various services without additional equipment such as sensors through ISAC. For example, it can be used for intruder detection in private land, railroads, etc., drone location tracking, flood or precipitation detection, gesture detection, driver assistance systems, etc.

[0087] FIG. 5 is a diagram illustrating an example of providing an ISAC service using two base stations in a wireless communication system according to one embodiment of the present disclosure.

[0088] Referring to FIG. 5, the first base station (510) can transmit reference signals (511, 513, 515). The reference signals (511, 513, 515) transmitted by the first base station (510) can be reflected, scattered, diffraction-modified signals from a sensing target object (e.g., 530) or an environment object (e.g., 540, 550), and can be received by the second base station (520). The signals received by the second base station (520) can be sensing signals (512, 514, 516). The first base station (510) can transmit the reference signals (511, 513, 515) at once. The first base station (510) can change the direction of the transmitting beam and transmit reference signals (511, 513, 515) respectively.

[0089] According to one embodiment, the first base station (510) can use the reference signals (511, 513, 515) not only for sensing purposes but also for communication purposes. The reference signals (511, 513, 515) used by the first base station (510) for communication purposes may be signals (e.g., primary / secondary synchronization signal, synchronization signal / PBCH block, positioning reference signal, cell-specific reference signal, tracking reference signal, demodulation reference signal) that a terminal receiving a wireless mobile communication service can use for channel estimation, time synchronization, data transmission / reception, position estimation, etc.

[0090] In one embodiment, the target object (e.g., 530) may be an object to be sensed via the ISAC service. The environment objects (e.g., 540, 550) may be objects other than the target object (e.g., 530). The characteristics of each object (530, 540, 550) may be distinguished by RCS (radar cross section) or micro-Doppler difference. For example, the size, shape, material, etc. of the object may be distinguished through sensing signals (512, 514, 516).

[0091] According to one embodiment, when a first base station (510) transmits a reference signal (511, 513, 515) at a predetermined time interval or for a continuous time and a second base station (520) receives a sensing signal (512, 514, 516) at a predetermined time interval or for a continuous time, the velocity and direction of a target object (e.g., 530) or an environment object (e.g., 540, 550) can be measured.

[0092] According to one embodiment, the resolution and range for sensing a target object (e.g., 530) or an environment object (e.g., 540, 550) may vary depending on the bandwidth and frequency pattern of the frequency transmitting the reference signal (511, 513, 515).

[0093] According to one embodiment, the first base station (510) transmits reference signals (511, 513, 515) and the second base station (520) receives sensing signals (512, 514, 516) that indicate that the reference signals (511, 513, 515) interact with objects. This function, which can detect or sense an object by identifying and mapping the characteristics of an object that may not have the ability to access a wireless mobile communication network, may be referred to as ISAC. A wireless communication system can provide various services through ISAC without additional equipment such as sensors. For example, it can be used for intruder detection in private land, railroads, etc., drone location tracking, flood or precipitation detection, gesture detection, driver assistance systems, etc.

[0094] FIG. 6 is a diagram illustrating the structure of a sensing function (SF) in a wireless communication system according to one embodiment of the present disclosure.

[0095] Referring to FIG. 6, the SF (sensing function) may include a transceiver (605), a control unit (610), a storage unit (615), and a calculation unit (620). However, the components of the SF are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. For example, the SF may include a transceiver (605) and a control unit (610). For example, the transceiver (605), the control unit (610), the storage unit (615), and the calculation unit (620) may be implemented in the form of a single chip.

[0096] According to one embodiment, the transceiver (605) is a general term for the SF receiving unit and the SF transmitting unit, and can transmit and receive signals with at least one of a base station, a terminal, or a network entity. The signals transmitted and received with the base station may include control information and data. For example, the transceiver (605) may transmit and receive control information or sensing results related to a sensing function with the base station. For example, the transceiver (605) may include a wired / wireless transceiver, and may include various components for transmitting and receiving signals. For example, the transceiver (605) may receive a signal through a wired / wireless channel and output it to the control unit (610). The transceiver (605) may transmit a signal output from the control unit (610) through a wired / wireless channel. For example, the transceiver (605) may receive a communication signal and output it to a processor. The transmitter / receiver (605) can transmit a signal output from the processor to a network entity via a wired or wireless network.

[0097] According to one embodiment, the storage unit (615) can store programs and data necessary for the operation of the SF. For example, the storage unit (615) can store control information or data included in wired or wireless signals acquired by the SF. The storage unit (615) can be configured as a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media.

[0098] According to one embodiment, the calculation unit (620) may perform a calculation, under the instruction of the control unit (610), to transform information output from the control unit (610) (e.g., information on a signal measured by an ISAC operation, or information processed from a signal measured by an ISAC operation) into another form understandable to a human or another application. The calculation result output from the calculation unit (620) may be output to and stored in the storage unit (615). The calculation result output from the calculation unit (620) may be output to the control unit (610).

[0099] In the present disclosure, the control unit (610) may be defined as a circuit, an application-specific integrated circuit, or at least one processor. According to one embodiment, the processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (610) may control the overall operation of the SF according to the embodiment proposed in the present disclosure. For example, the control unit (610) may control the signal flow between each block to perform operations according to a flowchart.

[0100] FIG. 7 is a diagram illustrating a communication protocol structure of a base station and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0101] Referring to FIG. 7, the base station (705) can transmit and receive data with the AMF (710), the AMF (710) can transmit and receive data with the LMF (715), and the LMF (715) can transmit and receive data with the SF (720). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example illustrated in FIG. 2. In addition, the SF (720) may be integrated as part of the LMF (715) function, and the LMF (715) and the SF (720) may communicate in another method (e.g., an internal interface) not described in the present disclosure.

[0102] According to one embodiment, the base station (705) may use NRPPa (NR positioning protocol A), which is a protocol for transmitting data between the base station (705) and the LMF (715), as a method for transmitting control information, signal information, or measurement information related to ISAC to the SF (720). That is, information that the base station (705) wishes to transmit to the SF (720) may be included in the form of an information element (IE) in an NRPPa protocol data unit (PDU) (732).

[0103] According to one embodiment, the NRPPa PDU (732) transmitted by the base station (705) to the LMF (715) may be included in an NGAP (NG application protocol) message (731) that transfers data between the base station (705) and the AMF (710). The NGAP message (731) may include an identifier (e.g., routing ID) of the LMF (715) to which the base station (705) transmits the NRPPa PDU (732).

[0104] According to one embodiment, the AMF (710) may forward an NRPPa PDU (734) to the LMF (715) corresponding to the LMF identifier included in the NGAP message (731) transmitted by the base station (705). The NRPPa PDU (734) may be transmitted in a message (733) of an interface (e.g., Nlmf) that transmits data from the AMF (710) to the LMF (715). The message (733) of the interface (e.g., Nlmf) that transmits data from the AMF (710) to the LMF (715) may include an identifier of the base station (705) (e.g., correlation ID) to inform the LMF (715) of the base station (705) that transmits the NRPPa PDU (734).

[0105] According to one embodiment, LMF (715) can forward ISAC information (735) included in the received NRPPa PDU (734) to SF (720). SF (720) can perform an operation for ISAC service.

[0106] According to one embodiment, the SF (720) may use NRPPa, which is a protocol for transmitting data between the LMF (715) and the base station (705), as a method for transmitting at least one of control information, signal information, or measurement information related to ISAC to the base station (705). That is, the SF (720) transmits ISAC information (736) to be transmitted to the base station (705) to the LMF (715), and the LMF (715) may include the ISAC information (736) in the form of an IE in an NRPPa PDU (738) transmitted to the base station (705). The NRPPa PDU (738) transmitted by the LMF (715) to the base station (705) may be transmitted as a message (737) of an interface (e.g., Namf) that transmits data from the LMF (715) to the AMF (710). A message (737) of an interface (e.g., Namf) that transmits data from an LMF (715) to an AMF (710) may include an identifier of the base station (705) (e.g., correlation ID) to inform the base station (705) to forward an NRPPa PDU (738) to the AMF (710).

[0107] According to one embodiment, the AMF (710) may forward an NRPPa PDU (740) to the base station (705) corresponding to the base station (705) identifier (e.g., correlation ID) included in the message (737) transmitted by the LMF (715). The NRPPa PDU (740) that the AMF (710) forwards to the base station (705) may be included in a NGAP message (739) that transfers data between the AMF (710) and the base station (705). The NGAP message (739) may include an identifier (e.g., routing ID) of the LMF (715) to inform the base station (705) of the LMF (715) to forward the NRPPa PDU (740).

[0108] According to one embodiment, the base station (705) can perform an operation for an ISAC service using the ISAC information included in the received NRPPa PDU (740).

[0109] In one embodiment, multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously from a single peer (e.g., a base station and an LMF). The base station (705) and the LMF (715) can include a processing identifier (e.g., a transaction ID) in the NRPPa PDUs (732, 734, 738, 740) to identify which ISAC operation each different NRPPa PDU corresponds to.

[0110] According to one embodiment, the NRPPa PDU (732) transmitted by the base station (705) to the AMF (710) and the NRPPa PDU (734) transmitted by the AMF (710) to the LMF (715) may contain equivalent information or may be the same message. The NRPPa PDU (738) transmitted by the LMF (715) to the AMF (710) and the NRPPa PDU (740) transmitted by the AMF (710) to the base station (705) may contain equivalent information or may be the same message.

[0111] In one embodiment, the LMF (715) identifier (e.g., routing ID) and the base station (705) identifier (e.g., correlation ID) may be different values ​​that the AMF (710) can map to, or may be the same value.

[0112] FIG. 8 is a diagram illustrating a communication protocol structure of a base station and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0113] Referring to FIG. 8, the base station (805) can transmit and receive data with the AMF (810), the AMF (810) can transmit and receive data with the LMF (815), and the LMF (815) can transmit and receive data with the SF (820). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example illustrated in FIG. 2. In cases where the base station (805) or the AMF (810) cannot directly exchange messages with the SF (820), message transmission through the LMF (815) may be required.

[0114] According to one embodiment, the base station (805) may utilize a new protocol for transmitting data between the base station (805) and the SF (820) as a method for transmitting control information, signal information, or measurement information related to the ISAC to the SF (820). That is, the information that the base station (805) wishes to transmit to the SF (820) may be included in the form of an IE in the new protocol PDU.

[0115] According to one embodiment, a new protocol PDU (833) transmitted by the base station (805) to the SF (820) may be included in an NRPPa message (832) that transfers data between the base station (805) and the LMF (815). The NRPPa message (832) may include an identifier (e.g., SF routing ID) of the SF (820) that transmits the new protocol PDU (833) transmitted by the base station (805).

[0116] According to one embodiment, the NRPPa PDU may be included in a NGAP message (831) that transfers data between the base station (805) and the AMF (810). The NGAP message (831) may include an identifier (e.g., routing ID) of an LMF (815) to which the base station (805) transmits the NRPPa PDU (832). The AMF (810) may forward the NRPPa PDU (832) to the LMF (815) corresponding to the LMF (815) identifier included in the NGAP message (831) transmitted by the base station (805).

[0117] According to one embodiment, an NRPPa PDU (835) including a new protocol PDU (836) may be transmitted in a message (834) of an interface (e.g., Nlmf) that transmits data from an AMF (810) to an LMF (815). The message (834) of the interface (e.g., Nlmf) that transmits data from an AMF (810) to an LMF (815) may include an identifier of the base station (805) (e.g., correlation ID) so that the LMF (815) can identify the base station (805) transmitting the NRPPa PDU (835).

[0118] According to one embodiment, the LMF (815) may forward a new protocol PDU (838) to the SF (820) corresponding to the SF (820) identifier (e.g., SF routing ID) included in the NRPPa PDU (835) as a message (837) of an interface (e.g., Nsf) that transmits data from the LMF (815) to the SF (820).

[0119] According to one embodiment, a message (837) of an interface (e.g., Nsf) that transmits data from LMF (815) to SF (820) may include an identifier of the base station (805) (e.g., SF correlation ID) to inform the base station (805) to transmit a new protocol PDU (838) to SF (820).

[0120] According to one embodiment, SF (820) may receive a new protocol PDU (838) and perform an operation for the ISAC service.

[0121] According to one embodiment, SF (820) may utilize a new protocol for transmitting data between SF (820) and base station (805) as a method for transmitting control information, signal information, or measurement information related to ISAC to base station (805). That is, ISAC-related information that SF (820) wishes to transmit to base station (805) may be included in the form of IE in a new protocol PDU.

[0122] According to one embodiment, the new protocol PDU (840) that SF (820) transmits to LMF (815) may be transmitted as a message (839) of an interface (e.g., Nlmf) that transfers data between SF (820) and LMF (815). The message (839) of the interface (e.g., Nlmf) that transfers data from SF (820) to LMF (815) may include an identifier of the base station (805) (e.g., SF correlation ID) so that LMF (815) can identify the base station (805) that transmits the new protocol PDU (840).

[0123] According to one embodiment, the new protocol PDU (843) that the LMF (815) transmits to the base station (805) may be included in an NRPPa message (842) that transmits data between the LMF (815) and the base station (805). The NRPPa message (842) may include an identifier (e.g., SF correlation ID) of the base station (805) that transmits the new protocol PDU (843) that the LMF (815) transmits. The NRPPa message (842) may be transmitted as a message (841) of an interface (e.g., Namf) that transmits data from the LMF (815) to the AMF (810).

[0124] According to one embodiment, a message (841) of an interface (e.g., Namf) that transmits data from an LMF (815) to an AMF (810) may include an identifier (e.g., correlation ID) of a base station (805) so that the AMF (810) can identify the base station (805) to which the NRPPa PDU (842) is being delivered.

[0125] According to one embodiment, an NRPPa PDU (845) containing a new protocol PDU (846) that the AMF (810) transmits to the base station (805) may be included in a NGAP message (844) that transmits data between the AMF (810) and the base station (805). The NGAP message (844) may include an identifier (e.g., a routing ID) of the LMF (815) transmitting the NRPPa PDU (845) to inform the base station (805) of the LMF (815) transmitting the NRPPa PDU (845).

[0126] According to one embodiment, the base station (805) can identify the SF (820) transmitting the new protocol PDU (846) through the SF (820) identifier (e.g., SF routing ID) included in the NRPPa PDU (845).

[0127] According to one embodiment, the base station (805) may receive a new protocol PDU (846) and perform an operation for the ISAC service.

[0128] In one embodiment, multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously from a single peer (e.g., a base station and an LMF). The base station (805) and the LMF (815) can include a processing identifier (e.g., a transaction ID) in the NRPPa PDUs (832, 835, 842, 845) to identify which ISAC operation each different NRPPa PDU corresponds to.

[0129] In one embodiment, multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously by a single peer (e.g., a base station and a SF). The base station (805) and the SF (820) can include an SF (820) processing identifier (e.g., an SF transaction ID) in the new protocol PDUs (833, 836, 843, 846) to identify which ISAC operation each different new protocol PDU corresponds to.

[0130] According to one embodiment, the NRPPa PDU (832) transmitted by the base station (805) to the AMF (810) and the NRPPa PDU (835) transmitted by the AMF (810) to the LMF (815) may include equivalent information or may be the same message. According to one embodiment, the NRPPa PDU (842) transmitted by the LMF (815) to the AMF (810) and the NRPPa PDU (845) transmitted by the AMF (810) to the base station (805) may include equivalent information or may be the same message. According to one embodiment, the new protocol PDU (833) that the base station (805) transmits to the AMF (810), the new protocol PDU (836) that the AMF (810) transmits to the LMF (815), and the new protocol PDU (838) that the LMF (815) transmits to the SF (820) may include equivalent information or may be the same message. According to one embodiment, the new protocol PDU (840) that the SF (820) transmits to the base station (805), the new protocol PDU (843) that the LMF (815) transmits to the AMF (810), and the new protocol PDU (846) that the AMF (810) transmits to the base station (805) may include equivalent information or may be the same message.

[0131] In one embodiment, the LMF (815) identifier (e.g., routing ID) and the base station (805) identifier (e.g., correlation ID) may be different values ​​that the AMF (810) can map to, or may be the same value. In one embodiment, the SF (820) identifier (e.g., SF (820) routing ID) and the base station (805) identifier (e.g., SF (820) correlation ID) may be different values ​​that the LMF (815) can map to, or may be the same value. Additionally, the LMF (815) identifier and the SF (820) identifier may be the same value.

[0132] FIG. 9 is a diagram illustrating a communication protocol structure of a base station and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0133] Referring to FIG. 9, the base station (905) can transmit and receive data with the AMF (910), and the AMF (910) can transmit and receive data with the SF (915). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example illustrated in FIG. 2. In cases where the base station (905) cannot directly exchange messages with the SF (915), message transmission through the AMF (910) may be required.

[0134] According to one embodiment, the base station (905) may utilize a new protocol for transmitting data between the base station (905) and the SF (915) as a method for transmitting control information, signal information, or measurement information related to the ISAC to the SF (915). That is, information that the base station (905) wishes to transmit to the SF (915) may be included in the form of an IE in the new protocol PDU.

[0135] According to one embodiment, the new protocol PDU (922) that the base station (905) transmits to the SF (915) may be included in a NGAP message (921) that transfers data between the base station (905) and the AMF (910). The NGAP message (921) may include an identifier (e.g., SF routing ID) of the SF (915) to which the base station (905) transmits the new protocol PDU (922).

[0136] According to one embodiment, the AMF (910) may forward a new protocol PDU (924) to the SF (915) corresponding to the SF (915) identifier included in the NGAP message (921) transmitted by the base station (905). The new protocol PDU (924) may be transmitted in a message (923) of an interface (e.g., Nsf) that transmits data from the AMF (910) to the SF (915). The message (923) of the interface (e.g., Nsf) that transmits data from the AMF (910) to the SF (915) may include an identifier of the base station (905) (e.g., SF correlation ID) to inform the SF (915) that the base station (905) transmits the new protocol PDU (924).

[0137] According to one embodiment, SF (915) can perform an operation for an ISAC service using ISAC information included in the received new protocol PDU (924).

[0138] According to one embodiment, SF (915) may utilize a new protocol for transferring data between SF (915) and base station (905) as a method for transferring control information, signal information, or measurement information related to ISAC to base station (905). That is, information that SF (915) wishes to transfer to base station (905) may be included in the form of IE in the new protocol PDU.

[0139] According to one embodiment, the new protocol PDU (926) may be transmitted in a message (925) of an interface (e.g., Namf) that transmits data from the SF (915) to the AMF (910). The message (925) of the interface (e.g., Namf) that transmits data from the SF (915) to the AMF (910) may include a base station (905) identifier (e.g., SF correlation ID) to inform the base station (905) that the SF (915) is transmitting the new protocol PDU (926).

[0140] According to one embodiment, the AMF (910) may forward a new protocol PDU (928) to the base station (905) corresponding to the base station (905) identifier included in the message (925) of an interface (e.g., Namf) that transmits data from the SF (915) to the AMF (910).

[0141] According to one embodiment, the new protocol PDU (928) that the AMF (910) transmits to the base station (905) may be included in a NGAP message (927) that transmits data between the AMF (910) and the base station (905). The NGAP message (927) may include an identifier (e.g., SF routing ID) of the SF (915) transmitting the new protocol PDU (927).

[0142] According to one embodiment, the base station (905) can perform an operation for the ISAC service using the ISAC information included in the received new protocol PDU (927).

[0143] In one embodiment, multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously by a single peer (e.g., a base station and a SF). The base station (905) and the SF (915) can include a processing identifier (e.g., an SF transaction ID) in the new protocol PDUs (922, 924, 926, 928) to identify which ISAC operation each new protocol PDU corresponds to.

[0144] According to one embodiment, the new protocol PDU (922) transmitted by the base station (905) to the AMF (910) and the new protocol PDU (924) transmitted by the AMF (910) to the SF (915) may include equivalent information or may be the same message. According to one embodiment, the new protocol PDU (926) transmitted by the SF (915) to the AMF (910) and the new protocol PDU (928) transmitted by the AMF (910) to the base station (905) may include equivalent information or may be the same message.

[0145] In one embodiment, the SF (915) identifier (e.g., SF routing ID) and the base station (905) identifier (e.g., SF correlation ID) may be different values ​​that the AMF (910) can map to, or may be the same value.

[0146] FIG. 10 is a diagram illustrating a communication protocol structure of a base station and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0147] Referring to FIG. 10, the base station (1005) can directly transmit and receive data with the SF (1010). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example illustrated in FIG. 2.

[0148] According to one embodiment, the base station (1005) may utilize a new protocol for transferring data between the base station (1005) and the SF (1010) as a method for transferring control information, signal information, or measurement information related to the ISAC to the SF (1010). That is, information that the base station (1005) wishes to transfer to the SF (1010) may be included in the form of an IE in the new protocol PDU.

[0149] According to one embodiment, a new protocol PDU (1022) transmitted by the base station (1005) to the SF (1010) may be included in a message (1021) of an interface (e.g., Nsf) that transfers data between the base station (1005) and the SF (1010).

[0150] According to one embodiment, a message (1021) of an interface (e.g., Nsf) that transfers data between a base station (1005) and a SF (1010) may include an identifier of the base station (1005) (e.g., gNB ID) to inform the base station (1005) to transmit a new protocol PDU (1022) to the SF (1010).

[0151] According to one embodiment, SF (1010) can perform an operation for an ISAC service using ISAC information included in a received new protocol PDU (1022).

[0152] According to one embodiment, the new protocol PDU (1024) that SF (1010) transmits to base station (1005) may be included in a message (1023) of an interface (e.g., NgNB) that transfers data between SF (1010) and base station (1005).

[0153] According to one embodiment, a message (1023) of an interface (e.g., Ngnb) that transfers data between a SF (1010) and a base station (1005) may include an identifier (e.g., SF ID) of the SF (1010) to inform the base station (1005) that the SF (1010) is to transmit a new protocol PDU (1024).

[0154] According to one embodiment, the base station (1005) can perform an operation for the ISAC service using the ISAC information included in the received new protocol PDU (1024).

[0155] According to one embodiment, the SF (1010) identifier (e.g., SF ID) and the base station (1005) identifier (e.g., gNB ID) may be different values ​​that the base station (1005) and the SF (1010) can map to, or may be the same value.

[0156] FIG. 11 is a diagram illustrating an example of a signal flow in which an SF obtains TRP (transmission-reception point) information of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0157] Referring to FIG. 11, the base station (1105) can directly or indirectly transmit and receive messages or information with the SF (1110). As in the example illustrated in FIG. 7, the SF (1110) may have its functionality integrated into the LMF. When the base station (1105) transmits and receives ISAC information with the LMF, the messages or information transmitted and received between the base station (1105) and the SF (1110) may be messages or information transmitted and received between the base station (1105) and the LMF. The method by which the base station (1105) exchanges messages or information with the LMF or the SF (1110) may be the examples illustrated in FIGS. 7, 8, 9, and 10, or other methods not described in the present disclosure.

[0158] According to one embodiment, SF (1110) can transmit a predetermined message (e.g., TRP information request) to BS (1105) to obtain information about a BS (1105) and a TRP (transmission-reception point) managed by BS (1105). The TRP information request (1121) can be triggered for transmission by a periodic update procedure for a TRP from which SF (1110) previously collected information, or can be triggered by OAM (operations, administration, maintenance). SF (1110) can include a request for information to be obtained from at least one TRP in TRP information request (1121). The information that SF (1110) requests BS (1105) can include at least some of the following. Of course, the present invention is not limited to the following examples.

[0159] - TRP list: The TRP list may include one or more TRP IDs (unique identifiers that can distinguish TRPs within the base station or on the network), and the base station may respond with information corresponding to the TRP IDs included in the TRP list. If the TRP list is not included, the base station may respond with all TRP information it manages.

[0160] - TRP information type: An indicator indicating that ISAC information is being requested.

[0161] - TRP geographical coordinates: You can request the location of the TRP.

[0162] - TRP spatial direction information: You can request the direction of the TRP or the angle per beam.

[0163] - TRP type: You can request the characteristics of TRP including tp, rp, and trp.

[0164] - Tx power: Current and maximum transmission power of TRP

[0165] - ISAC capability: You can request information on the ability to perform ISAC operations for each TRP.

[0166] - ISAC RS type: You can request which type of RS can be transmitted or received for ISAC purposes. For example, DL-PRS (downlink positioning reference signal), SSB (synchronization signal block), CSI-RS (channel state information reference signal), SRS (sounding reference signal), etc. can be responded to.

[0167] - ISAC RS bandwidth: You can request the bandwidth for transmitting or transmitting RS for ISAC purposes. For example, the absolute radio frequency channel number (ARFCN), carrier bandwidth, point A, and subcarrier spacing (SCS) can be responded to.

[0168] - ISAC RS frequency-scale pattern: You can request the frequency characteristics or pattern of RS for ISAC purposes. For example, comb size, offset, cyclic shift, and frequency hopping can be responded to.

[0169] - ISAC RS time-scale pattern: You can request the temporal characteristics or patterns of RS for ISAC purposes. For example, the number of symbols, repetition factor, resource set periodicity, etc. can be responded to.

[0170] - On-demand ISAC RS pattern: TRP can request the bandwidth, frequency, time characteristics or pattern of RS for ISAC purposes that can be transmitted. For example, the allowed values ​​can be responded in the form of a list or a bit string, and in the case of a bit string, the value corresponding to each bit can be expressed as 1 if it is settable and 0 if it is not settable.

[0171] - ISAC processing capability: The base station can request the ability to compute measurement results acquired through ISAC operations. For example, whether the measurement results are computed as final results (e.g., size, speed, material of an object) or as intermediate results with a predefined level, calculation accuracy, calculation delay time, measurable range, etc. can be responded to, and each capability can be responded to with a level (e.g., 0 (highest) to 9 (lowest)) or a predefined value.

[0172] - Supported event: You can request whether the base station can determine whether a specific condition related to ISAC is satisfied. The specific condition may be, for example, whether the ISAC operation can be performed at a specific time, whether the ISAC operation can be performed at a specific cycle, whether the operating state of a specific TRP is a condition, whether a specific object is sensed after the ISAC operation is performed, whether a specific timer expires, or whether a specific action (e.g., position, direction, speed, gesture) on an object is satisfied after the ISAC operation is performed.

[0173] According to one embodiment, the base station (1105) may transmit a predetermined message (e.g., a TRP information response) to the SF (1110) in order to respond to the information requested by the TRP information request (1121). The TRP information response (1122) may include at least a portion of the information requested by the TRP information request (1121). If the base station (1105) cannot respond to a portion of the information requested by the TRP information request (1121) or does not support the requested function, the base station (1105) may notify the SF (1110) by including at least one of: no value in the TRP information response (1122), an indication that the requested information cannot be responded to or is not supported, or a reason for not being able to respond (e.g., TRP does not support ISAC, wrong TRP ID requested).

[0174] According to one embodiment, if the base station (1105) cannot respond to some of the information requested in the TRP information request (1121) or does not support the requested functionality, it may respond to the SF (1110) with a predetermined message (e.g., TRP information failure). The base station (1105) may inform the SF (1110) of the TRP information failure (1123) by including at least one of an indication that the requested information cannot be responded to or is not supported, or a reason for the inability to respond (e.g., TRP does not support ISAC, wrong TRP ID requested).

[0175] According to one embodiment, when a portion of the information responded with the TRP information response (1122) is updated, the base station (1105) may transmit a predetermined message (e.g., TRP information update) to the SF (1110) to inform the SF (1110) of the updated information. The base station (1105) may include the updated information in a previously transmitted TRP information response or TRP information update. The base station (1105) may include all information requested in the TRP information request in the TRP information update (1124).

[0176] FIG. 12 is a diagram illustrating an example of a signal flow in which a base station acquires information on SF in a wireless communication system according to various embodiments of the present disclosure.

[0177] Referring to FIG. 12, the base station (1205) can directly or indirectly transmit and receive messages or information with the SF (1210). As in the example illustrated in FIG. 7, the SF may have its functions integrated into the LMF. When the base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and the SF may be messages or information transmitted and received by the base station and the LMF. The method by which the base station exchanges messages or information with the LMF or the SF may be the examples illustrated in FIGS. 7, 8, 9, and 10, or other methods not described in the present disclosure. In other words, there is no limitation on the method by which the base station exchanges messages or information with the LMF or the SF.

[0178] According to one embodiment, the base station (1205) may transmit a predetermined message (e.g., an SF information request) to the SF (1210) to obtain information about the SF (1210). The transmission of the SF information request (1221) may be triggered by a periodic update procedure for the SF from which the base station (1205) previously collected information. The SF information request (1221) may be triggered by OAM. The information that the base station (1205) requests from the SF (1210) may include at least some of the following, but is not limited to the following examples.

[0179] - SF load: This can indicate the load level of SF. The base station can consider SF load information when selecting SF.

[0180] - SF location: You can request the physical location or network location of the SF. The base station can consider the SF's location information when selecting the SF.

[0181] - ISAC capability: Information on the SF's ability to perform ISAC operations can be requested. The base station can consider the SF's ISAC operation capability when selecting an SF.

[0182] - supported event: You can request whether SF can determine whether a specific condition related to ISAC is satisfied. The specific condition may be, for example, that an ISAC operation can be performed at a specific time, that an ISAC operation can be performed at a specific cycle, that a specific object is sensed after an ISAC operation is performed, that a specific timer expires, or that a specific action (e.g., position, direction, speed, gesture) on an object is satisfied after an ISAC operation is performed.

[0183] - Object sensing capability: This can represent the ability of SF to compute measurement results obtained through ISAC operations. This can be expressed in terms of the shape, size, speed, material, etc. of the sensed object, and can be a value representing a predefined object (e.g., a person, a car, etc.).

[0184] - ISAC processing capability: SF can request the ability to compute the measurement results obtained by the ISAC operation. For example, whether the measurement results are computed as a final result (e.g., size, speed, material of an object) or as intermediate results with a predefined level, the computational accuracy, computational delay time, measurable area, etc. can be responded to, and each capability can be responded to as a level (e.g., 0 (highest) to 9 (lowest)) or a predefined value.

[0185] According to one embodiment, SF (1210) may transmit a predetermined message (e.g., SF information response) to base station (1205) in order to respond to information requested by SF information request (1221). SF information response (1222) may include at least a portion of the information requested by SF information request (1221). If SF (1210) cannot respond to a portion of the information requested by SF information request (1221) or does not support a requested function, SF information response (1222) may not include a value, may include at least one of an indicator that SF (1210) cannot respond to or does not support the requested information, or a reason for not being able to respond (e.g., SF temporarily does not support ISAC operation) and may be transmitted to base station (1205).

[0186] According to one embodiment, if SF (1210) cannot respond to some of the information requested in SF information request (1221) or does not support the requested functionality, SF (1210) may respond to base station (1205) with a predetermined message (e.g., SF information failure). SF (1210) may transmit SF information failure (1223) to base station (1205) including at least one of an indication that SF (1210) cannot respond to or does not support the requested information, or a reason for not being able to respond (e.g., SF temporarily does not support ISAC operation).

[0187] According to one embodiment, when a portion of the information responded with the SF information response (1222) is updated, the SF (1210) may transmit a predetermined message (e.g., SF information update) to the base station (1205) to inform the base station (1205) of the updated information. The SF (1210) may include information updated in the previously transmitted SF information response (1222) or SF information update (1224). The SF (1210) may include all information requested in the SF information request (1221) in the SF information update (1224).

[0188] FIG. 13 is a diagram illustrating an example of a signal flow in which an SF sets a reference signal transmission to a base station in a wireless communication system according to various embodiments of the present disclosure.

[0189] Referring to FIG. 13, the base station (1305) can directly or indirectly transmit and receive messages or information with the SF (1310). As in the example illustrated in FIG. 7, the SF may have its functions integrated into the LMF. When the base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and the SF may be messages or information transmitted and received by the base station and the LMF. The method by which the base station exchanges messages or information with the LMF or SF may be the examples illustrated in FIGS. 7, 8, 9, and 10, or other methods not described in the present disclosure.

[0190] According to one embodiment, the SF (1310) may transmit a predetermined message (e.g., an RS configuration request) to the BS (1305) to configure or request the BS (1305) to transmit an RS that can be used for ISAC purposes, to obtain information about the RS currently being transmitted, or to configure or request the BS (1305) to stop transmitting an RS. The RS configuration request (1321) may include at least some of the following information for the SF (1310) to control the RS of the BS (1305) or to obtain information. Of course, the present invention is not limited to the following examples.

[0191] - RS transmission or interrupt indicator

[0192] - TRP identifier: You can request RS transmission or suspension by TRP.

[0193] - Beam identifier: You can request RS transmission or suspension for each beam.

[0194] - RS identifier: The identifier of the RS for which the SF requests RS transmission or termination, and can be a unique value within the base station or TRP. The SF can request transmission of multiple RSs with a single RS configuration request to the base station, and may include one or more RS identifiers and request information for each identifier.

[0195] - RS on-demand information: The base station can select an appropriate value for ISAC operation from among the on-demand values ​​(e.g., RS type, frequency-scale pattern, time-scale pattern, etc.) responded to in the TRP info response and instruct RS transmission. If more than one value is requested, the base station can select an appropriate value.

[0196] - RS characteristics: SF instructs the base station on the characteristics of RS (e.g., RS type, bandwidth, pattern, etc.), and the base station can transmit RS based on the requested characteristics.

[0197] - RS transmission start time

[0198] - Number of RS transmission repetitions and repetition cycle

[0199] - ISAC operation QoS: When the characteristics or QoS of an object requiring sensing (e.g., object size resolution, speed accuracy, material accuracy, measurement frequency, etc.) are provided to the base station, the base station can transmit an RS that satisfies the QoS among the RSs that can be transmitted based on the requested QoS.

[0200] - An indicator requesting information about the RS currently being transmitted: The base station can respond with information about the RS currently being transmitted (e.g., RS type, frequency-scale pattern, time-scale pattern, etc.).

[0201] According to one embodiment, the base station (1305) may receive an RS transmission request from the SF (1310) through an RS configuration request (1321), and may respond by transmitting a predetermined message (e.g., an RS configuration response) to the SF (1310) if RS transmission for a certain RS identifier can be performed normally. The RS configuration response (1322) may include an RS identifier for performing RS transmission normally, and may include information on an RS selected by the base station (1305) if RS transmission is requested with one or more on-demand values, RS characteristics, or QoS (e.g., RS type, frequency-scale pattern, time-scale pattern, etc.).

[0202] According to one embodiment, when the base station (1305) receives a request for RS information being transmitted from the SF (1310) as an RS configuration request (1321), the base station (1305) may respond by transmitting a predetermined message (e.g., RS configuration response) to the SF (1310). The RS configuration response (1322) may include information about the RS being transmitted (e.g., RS type, frequency-scale pattern, time-scale pattern, etc.).

[0203] According to one embodiment, the base station (1305) may receive a request for RS transmission suspension from the SF (1310) through an RS configuration request (1321), and may respond by transmitting a predetermined message (e.g., an RS configuration response) to the SF (1310) if the RS transmission suspension for a certain RS identifier can be performed normally. The RS configuration response (1322) may include the RS identifier for which the RS transmission was normally suspended.

[0204] According to one embodiment, the base station (1305) may receive an RS configuration request (1321) from the SF (1310) and, if it is unable to perform or abort an RS transmission for an identifier for at least a portion of the requested RS transmissions, may respond by transmitting a predetermined message (e.g., an RS configuration response) to the SF (1310). The RS configuration response (1322) may include at least one of a TRP identifier or an RS identifier for which the RS transmission cannot be performed. The base station (1305) may include a reason for not performing the RS transmission (e.g., TRP unavailable, unavailable due to TRP load, RS being used for another purpose, etc.) in the RS configuration response (1322).

[0205] According to one embodiment, the base station (1305) may receive an RS configuration request from the SF (1310) and, if it is unable to perform RS transmission for an identifier for at least a portion of the requested RS transmissions, may respond by transmitting a predetermined message (e.g., RS configuration failure) to the SF (1310). The RS configuration failure (1323) may include at least one of the TRP identifier or the RS identifier for which the RS transmission cannot be performed. The base station (1305) may include a reason for failing to perform the RS transmission (e.g., TRP unavailable, unavailable due to TRP load, RS being used for another purpose, etc.) in the RS configuration failure (1323).

[0206] FIG. 14 is a diagram illustrating an example of a signal flow in which an SF requests sensing from a base station in a wireless communication system according to various embodiments of the present disclosure.

[0207] Referring to FIG. 14, the base station (1405) can directly or indirectly transmit and receive messages or information with the SF (1410). As in the example illustrated in FIG. 7, the SF may have its functions integrated into the LMF. When the base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and the SF may be messages or information transmitted and received by the base station and the LMF. The method by which the base station exchanges messages or information with the LMF or SF may be the examples illustrated in FIGS. 7, 8, 9, and 10, or other methods not described in the present disclosure.

[0208] According to one embodiment, SF (1410) may perform procedures such as TRP information request (1421) and TRP information response (1422) to obtain base station (1405) and TRP information. These procedures may follow the example illustrated in FIG. 11.

[0209] According to one embodiment, the SF (1410) may perform at least one of an RS configuration request (1423) or an RS configuration response (1424) procedure to set up ISAC RS transmission to the base station (1405). This procedure may follow the example illustrated in FIG. 13.

[0210] According to one embodiment, the procedures of TRP information request (1421), TRP information response (1422), RS configuration request (1423), and RS configuration response (1424) are illustrated in FIG. 14 to be performed before SF (1410) requests sensing from base station (1405), but may be performed before SF (1410) requests sensing from base station (1405), during the process of requesting sensing, or after requesting sensing, as needed.

[0211] According to one embodiment, the SF (1410) may transmit a predetermined message (e.g., an ISAC measurement request) to the BS (1405) to instruct the BS (1405) and the TRP to transmit, receive, and measure ISAC RSs. The ISAC measurement request (1425) may include at least some of the following information to control the ISAC operation of the BS (1405) or obtain information. Of course, the present invention is not limited to the following examples.

[0212] - Transaction ID

[0213] - Information indicating ISAC RS transmission: This may be information included in an RS configuration request (e.g., information as exemplified in FIG. 13), and may indicate transmission of ISAC RS.

[0214] - Information indicating ISAC RS reception: ISAC RS transmission information (e.g., frequency-scale pattern, time-scale pattern, RS type, etc.) is included so that the receiving TRP can perform ISAC RS measurement. At this time, the TRP receiving the ISAC RS and the beam identifier may be included.

[0215] - Event-based reporting conditions: The base station can perform the ISAC measurement reporting procedure if the reporting conditions indicated by the SF are met. Reporting conditions can include the conditions below, and two or more conditions can be combined.

[0216] * response time: You can request that SF receive measurement reports by a certain point in time.

[0217] * periodic: SF can be requested to receive measurement reports at specific intervals.

[0218] * TRP sensing availability: The base station can notify the SF when the indicated TRP becomes available for ISAC RS transmission or reception.

[0219] * Target object availability: The base station can notify the SF when an object detected in the measurement area enters or leaves the measurement area. The target object can be distinguished by a combination of shape, size, speed, material, etc., or can be an object corresponding to a predefined value (e.g., a person or a car).

[0220] * Motion event: When the motion of an object detected in the measurement area satisfies certain conditions, the base station can notify the SF. Motion can be identified by a combination of the object's shape, location, direction, and speed, or it can be an object corresponding to a predefined value (e.g., a fist clenching or unclenching motion).

[0221] - ISAC QoS: QoS required when the base station reports measurement results to the SF. QoS may include the time taken to report measurement results after receiving ISAC RS (response time), accuracy of measurement result reporting, etc.

[0222] - Measurement report characteristics: This can indicate the level of measurement results the base station includes in its measurement reports. For example, a request can be made to include raw measurement results in the measurement report, to include the measurement results in the measurement report in their entirety or in a processed form (e.g., RCS or micro-Doppler) for each data point, or to include object characteristics and locations calculated and included in the measurement report.

[0223] - Measurement characteristic indication: You can request the characteristics of the measurement results that the base station includes in the measurement report. For example, you can request that only the target object information (e.g., whether it is line of sight (LOS) or non-line of sight (NLOS), number of scattering points, shape, size, direction and speed of movement, material) that is the sensing target among the objects detected by the ISAC operation be reported, you can request that all objects detected by the ISAC operation be included in the measurement results, or you can request that only objects that satisfy specific conditions (e.g., whether it is line of sight (LOS) or non-line of sight (NLOS), number of scattering points, shape, size, direction and speed of movement, material) that are detected by the ISAC operation be included in the measurement results.

[0224] According to one embodiment, the base station (1405) may report the measurement result by transmitting a predetermined message (e.g., ISAC measurement report) to the SF (1410) when the SF (1410) requests measurement with an ISAC measurement request (1425) and a reporting condition is not set or the reporting condition is satisfied.

[0225] The ISAC measurement report (1426) may include information requested by SF (1410). It may also include at least some of the following information:

[0226] - transaction ID

[0227] - Accuracy of measurement results: It can be expressed as the accuracy of the measurement results, range of accuracy, confidence level, uncertainty, etc.

[0228] - Additional measurement-related information: This may include the type of ISAC RS used in the measurement, the time the ISAC RS was received (timestamp), and the received strength of the ISAC RS (e.g., RSRP, RSSI, SINR).

[0229] According to one embodiment, when measurement using a requested TRP is impossible (e.g., when the setting of the TRP is changed, or when the ISAC RS is no longer received, etc.), the base station (1405) may notify the SF (1410) by transmitting a predetermined message (e.g., ISAC measurement failure). The ISAC measurement failure (1427) may include at least one of a measurement identifier (e.g., transaction ID) or a reason why measurement is impossible (e.g., TRP not available, configuration not available, resource not available, sensing signal not detected, etc.).

[0230] In one embodiment, SF (1410) may instruct base station (1405) to stop measurement by sending a predetermined message (e.g., ISAC measurement abort) when measurement is no longer needed. ISAC measurement abort (1428) may include a measurement identifier (e.g., transaction ID).

[0231] FIG. 15 is a diagram illustrating an example of a signal flow in which a base station requests sensing from an SF in a wireless communication system according to various embodiments of the present disclosure.

[0232] Referring to FIG. 15, the base station (1505) can directly or indirectly transmit and receive messages or information with the SF (1510). As in the example illustrated in FIG. 7, the SF may have its functions integrated into the LMF. When the base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and the SF may be messages or information transmitted and received by the base station and the LMF. The method by which the base station exchanges messages or information with the LMF or SF may be the examples illustrated in FIGS. 7, 8, 9, and 10, or other methods not described in the present disclosure.

[0233] According to one embodiment, the base station (1505) may perform at least one of an SF information request (1521) or an SF information response (1522) procedure to obtain information of an SF (1510). This procedure may follow the example illustrated in FIG. 12.

[0234] According to one embodiment, when the base station (1505) is triggered by an OAM or the like to perform an ISAC operation (e.g., when the base station receives an ISAC measurement result and needs to use the result or needs to report the result to another entity), the base station (1505) may transmit a predetermined message (e.g., a gNB ISAC measurement request) requesting an ISAC operation to the SF (1510). The base station (1505) may perform procedures such as an SF information request (1521) and an SF information response (1522) to select an SF (1510). The base station (1505) may select an SF (1510) to request an ISAC measurement based on information of the SF it has or information provided by the OAM or the like.

[0235] According to one embodiment, the base station (1505) may include at least some of the following information in the gNB ISAC measurement request (1523) to request measurement instructions from the SF (1510).

[0236] - High-level requirement: Some of the following may be included: measurement target area, measurement accuracy, measurement response time, measurement target object (e.g., shape, size, movement direction and speed, material, or object corresponding to a predefined value (e.g., a person or a car)), event condition (e.g., event-based reporting condition as exemplified in Fig. 14).

[0237] - Measurement characteristic indication: You can request the characteristics of the measurement results to be included in the measurement report that the SF transmits to the base station. For example, you can request that only the target object information (e.g., whether it is line of sight (LOS) or non-line of sight (NLOS), number of scattering points, shape, size, direction and speed of movement, material) detected by the ISAC operation be reported, or you can request that all objects detected by the ISAC operation be included in the measurement results, or you can request that only objects that satisfy specific conditions (e.g., whether it is line of sight (LOS) or non-line of sight (NLOS), number of scattering points, shape, size, direction and speed of movement, material) detected by the ISAC operation be included in the measurement results.

[0238] According to one embodiment, if the SF (1510) fails to perform the ISAC measurement requested by the base station (1505), the SF may respond by sending a predetermined message (e.g., gNB ISAC measurement failure) to the base station. The gNB ISAC measurement failure (1524) may include an appropriate cause (e.g., LMF / SF overload, unknown area, Target object not supported, QoS not guaranteed). The base station (1505) may stop the measurement or request the ISAC measurement from another SF.

[0239] According to one embodiment, SF (1510) may perform at least one of a TRP information request (1525) or a TRP information response (1526) procedure to obtain base station (1505) and TRP information. This procedure may follow the example illustrated in FIG. 11.

[0240] According to one embodiment, the SF (1510) may perform at least one of an RS configuration request (1527) or an RS configuration response (1528) procedure to set up ISAC RS transmission to the base station (1505). This procedure may follow the example illustrated in FIG. 13.

[0241] According to one embodiment, SF (1510) may perform at least one procedure among ISAC measurement request (1529) or ISAC measurement response (1530) to perform an ISAC operation requested from base station (1505) through gNB ISAC measurement request (1523). This procedure may follow the example illustrated in FIG. 14.

[0242] According to one embodiment, when the SF (1510) can respond to the base station (1505) with the measurement result requested from the base station (1505) through the gNB ISAC measurement request (1523), the SF (1510) can report the measurement result by transmitting a predetermined message (e.g., gNB ISAC measurement report) to the base station.

[0243] According to one embodiment, the gNB ISAC measurement report (1531) may include information about the measured object (e.g., shape, size, direction and speed of movement, material, or object corresponding to a predefined value (e.g., a person or a car)), and accuracy of the measured object (e.g., accuracy, range, confidence level, uncertainty for each of object type / shape / velocity / location, etc.).

[0244] According to one embodiment, procedures such as SF information request (1521), SF information response (1522), TRP information request (1525), TRP information response (1526), ​​RS configuration request (1527), and RS configuration response (1528) are illustrated in the drawing to be performed before or during the base station (1505) and the SF (1510) performing sensing-related operations (e.g., 1523, 1529, 1530, 1531), but may be performed at at least one of before the base station (1505) and the SF (1510) perform sensing-related operations, during the process of performing sensing-related operations, or after performing sensing-related operations, as needed.

[0245] FIG. 16 is a diagram illustrating an example of a signal flow in which an external client or AMF requests sensing in a wireless communication system according to various embodiments of the present disclosure.

[0246] According to one embodiment, internal or external clients of a mobile communication core network can apply the results measured using the ISAC service in various ways. To this end, a procedure may be defined in which an internal client (e.g., AMF) or an external client (e.g., GMLC or client) requests the ISAC service and receives the ISAC service result. In this case, the client (1625) may need to perform authentication and security procedures through the GMLC (1620) before requesting the ISAC service. The GMLC (1620) may need to go through the AMF (1610) to communicate with the base station (1605). The GMLC (1620) may communicate directly with the base station (1605).

[0247] According to one embodiment, GMLC (1620) may receive an ISAC service request from a client (1625). For example, a service such as target object sensing or event detection in a specific area may be requested by the client through a predetermined message (e.g., sensing request (1631)) including the QoS (e.g., latency, accuracy) required by the client.

[0248] According to one embodiment, SF (1615) may perform at least one of a TRP information request (1632) or a TRP information response (1633) procedure to obtain base station (1605) and TRP information. This procedure may follow the example illustrated in FIG. 11.

[0249] According to one embodiment, the base station (1605) may perform at least one of an SF information request (1634) or an SF information response (1635) procedure to obtain information of the SF (1615). This procedure may follow the example illustrated in FIG. 12.

[0250] According to one embodiment, the GMLC (1620) may transmit a predetermined message (e.g., gNB-GMLC sensing request) to the base station (1605) or a predetermined message (e.g., AMF-GMLC sensing request) to the AMF (1610) to provide an ISAC service. The gNB-GMLC sensing request (1636) or the AMF-GMLC sensing request (1637) may include service requirements received from the client (1625).

[0251] According to one embodiment, the AMF (1610) may collect information using the ISAC service or provide it to other network functions according to regulations of a specific region, requests from telecommunication companies, etc. In order to provide the ISAC service, the AMF (1610) may request the ISAC service by transmitting a predetermined message (e.g., gNB-AMF sensing request) to the base station (1605) or a predetermined message (e.g., AMF-SF sensing request) to the SF (1615). The gNB-AMF sensing request (1638) and the AMF-SF sensing request (1640) may include information such as services such as target object sensing or event detection in a specific region and QoS (e.g., latency, accuracy) required by the services.

[0252] According to one embodiment, when the AMF (1610) receives a request for provision of an ISAC service (e.g., an AMF-GMLC sensing request) from the GMLC (1620), the AMF (1610) may transmit a predetermined message (e.g., a gNB-AMFsensing request) to the base station (1605) or transmit a predetermined message (e.g., an AMF-SF sensing request) to the SF (1615) to perform a procedure for providing an ISAC service. The gNB-AMF sensing request (1638) and the AMF-SF sensing request (1640) may include requirements of the service received from the GMLC (1620).

[0253] According to one embodiment, when the base station (1605) receives a request for provision of an ISAC service (e.g., gNB-GMLC sensing request, gNB-AMF sensing request) from the GMLC (1620) or the AMF (1610), the base station (1605) may transmit a predetermined message (e.g., gNB ISAC measurement request) requesting sensing to the SF (1615). This procedure may follow the example illustrated in FIG. 15.

[0254] According to one embodiment, the SF (1615) may perform at least one of an RS configuration request (1641) or an RS configuration response (1642) procedure to set up ISAC RS transmission to the base station (1605). This procedure may follow the example illustrated in FIG. 13.

[0255] According to one embodiment, the SF (1615) may perform at least one procedure among the ISAC measurement request (1643) or the ISAC measurement response (1644) to perform an ISAC operation requested from the AMF (1610) or the base station (1605) through a predetermined message (e.g., an AMF-SF sensing request) or a gNB ISAC measurement request). This procedure may follow the example illustrated in FIG. 14.

[0256] According to one embodiment, when the SF (1615) can respond to the base station (1605) with the measurement result requested from the base station (1605) through the gNB ISAC measurement request (1639), the SF (1615) may report the measurement result by transmitting a predetermined message (e.g., a gNB ISAC measurement report) to the base station. The information included in the gNB ISAC measurement report (1645) may include the information exemplified in the gNB ISAC measurement report of FIG. 15.

[0257] According to one embodiment, when the SF (1615) can report the measurement result requested from the AMF (1610) through the AMF-SF sensing request (1640) to the AMF (1610) by a procedure such as receiving the measurement result from the base station (1605), the SF (1615) can report the measurement result by transmitting a predetermined message (e.g., AMF-SF sensing report) to the AMF (1610). The information included in the AMF-SF sensing report (1648) may include the information exemplified in the ISAC measurement report of FIG. 14. The information included in the AMF-SF sensing report (1648) may include the information exemplified in the gNB ISAC measurement report of FIG. 15.

[0258] According to one embodiment, the base station (1605) may report the measurement results requested from the AMF (1610) or the GMLC (1620) through the gNB-AMF sensing request (1638) or the gNB-GMLC sensing request (1636) to the AMF (1610) or the GMLC (1620), by transmitting a predetermined message (e.g., gNB-AMF sensing report, gNB-GMLC sensing report) to the AMF (1610) or the GMLC (1620) to report the results. Information included in the gNB-AMF sensing report (1646) or the gNB-GMLC sensing report (1647) may include at least some of the information exemplified in the ISAC measurement report of FIG. 14. Information included in the gNB-AMF sensing report (1646) or the gNB-GMLC sensing report (1647) may include at least some of the information exemplified in the gNB ISAC measurement report of FIG. 15.

[0259] According to one embodiment, the AMF (1610) can receive a gNB-AMF sensing report (1646) and an AMF-SF sensing report (1648) from the base station (1605) or the SF (1615). When the AMF (1610) can report a measurement result requested from the GMLC (1620) through the AMF-GMLC sensing request (1637) to the GMLC (1620), the AMF (1610) can report the result by transmitting a predetermined message (e.g., AMF-GMLC sensing report). The information included in the AMF-GMLC sensing report (1649) can include at least some of the information exemplified in the ISAC measurement report of FIG. 14. The information included in the AMF-GMLC sensing report (1649) can include at least some of the information exemplified in the gNB ISAC measurement report of FIG. 15. Information included in the AMF-GMLC sensing report (1649) may include at least some of the information included in the gNB-AMF sensing report (1646) received from the base station (1605). Information included in the AMF-GMLC sensing report (1649) may include at least some of the information included in the AMF-SF sensing report (1648) received from the SF (1615).

[0260] According to one embodiment, the GMLC (1620) can receive a gNB-GMLC sensing report (1647) and an AMF-GMLC sensing report (1649) from the base station (1605) or the AMF (1610). If the GMLC (1620) can report a measurement result requested from the client (1625) through a sensing request (1631) to the client (1625), the GMLC (1620) can report the result by transmitting a predetermined message (e.g., a sensing report) to the client (1625). Information included in the sensing report (1650) may include at least some of the information exemplified in the ISAC measurement report of FIG. 14. Information included in the sensing report (1650) may include at least some of the information exemplified in the gNB ISAC measurement report of FIG. 15. Information included in the sensing report (1650) may include at least some of the information included in the gNB-GMLC sensing report (1647) received from the base station (1605). Information included in the sensing report (1650) may include at least some of the information included in the AMF-GMLC sensing report (1649) received from the AMF (1610).

[0261] Procedures such as TRP information request (1632), TRP information response (1633), SF information request (1634), SF information response (1635), RS configuration request (1641), and RS configuration response (1642) are illustrated in FIG. 16 to be performed before or during the base station (1605) and the SF (1615) performing sensing-related operations (e.g., 1639, 1643, 1644, 1645), but may be performed at at least one of the following points in time: before the base station (1605) and the SF (1615) perform sensing-related operations, during the process of performing sensing-related operations, or after performing sensing-related operations, if necessary.

[0262] FIG. 17 is a diagram illustrating an example of a signal flow in which an external client requests sensing in a wireless communication system according to various embodiments of the present disclosure.

[0263] External clients of a mobile communication core network can utilize the ISAC service for various applications. To this end, a procedure can be defined for an external client (e.g., a GMLC or client) to request the ISAC service and receive the ISAC service results. In this case, the client (1720) can request the ISAC service after performing authentication and security procedures through the GMLC (1715). The GMLC (1715) can communicate directly with the SF (1710).

[0264] According to one embodiment, GMLC (1715) may receive an ISAC service request from a client (1720). For example, a service such as target object sensing or event detection in a specific area may be requested through a predetermined message (e.g., sensing request (1731)) including a QoS (e.g., latency, accuracy) requested by the client (1720).

[0265] According to one embodiment, SF (1710) may perform at least one of a TRP information request (1732) or a TRP information response (1733) procedure to obtain base station (1705) and TRP information. This procedure may follow the example illustrated in FIG. 11.

[0266] According to one embodiment, GMLC (1715) may transmit a predetermined message (e.g., SF-GMLC sensing request) to SF (1710) to provide ISAC service. SF-GMLC sensing request (1734) may include service requirements received from client (1720).

[0267] According to one embodiment, SF (1710) may perform at least one of an RS configuration request (1735) or an RS configuration response (1736) procedure to set up ISAC RS transmission to base station (1705). This procedure may follow the example illustrated in FIG. 13.

[0268] According to one embodiment, SF (1710) may perform at least one procedure among ISAC measurement request (1737) or ISAC measurement response (1738) to perform an ISAC operation requested through a predetermined message (e.g., SF-GMLC sensing request) from GMLC (1715). This procedure may follow the example illustrated in FIG. 14.

[0269] According to one embodiment, when SF (1710) can report a measurement result requested from GMLC (1715) via SF-GMLC sensing request (1734) by a procedure such as receiving a measurement result from base station (1705), SF (1710) can report the measurement result by transmitting a predetermined message (e.g., SF-GMLC sensing report) to GMLC (1715).

[0270] According to one embodiment, the GMLC (1715) can receive an SF-GMLC sensing report (1739) from the SF (1710). If the GMLC (1715) can report the measurement result requested from the client (1720) through the sensing request (1731) to the client (1720), the GMLC (1715) can report the result by sending a predetermined message (e.g., a sensing report) to the client (1720). Information included in the sensing report (1740) may include at least some of the information exemplified in the ISAC measurement report of FIG. 14. Information included in the sensing report (1740) may include at least some of the information exemplified in the gNB ISAC measurement report of FIG. 15. Information included in the sensing report (1740) may include at least some of the information included in the SF-GMLC sensing report (1739) received from the SF.

[0271] Procedures such as TRP information request (1732), TRP information response (1733), RS configuration request (1735), and RS configuration response (1736) are illustrated in the drawing to be performed before or during the base station (1705) and the SF (1710) performing sensing-related operations (e.g., 1737, 1738), but may be performed at at least one of the following points in time: before the base station (1705) and the SF (1710) perform sensing-related operations, during the process of performing sensing-related operations, or after performing sensing-related operations, if necessary.

[0272] FIG. 18 is a diagram illustrating an example of a signal flow in which a CU acquires TRP information of a DU in a base station CU (central unit)-DU (distributed unit) separation structure of a wireless communication system according to one embodiment of the present disclosure.

[0273] Referring to FIG. 18, the CU (1805) is connected to the first DU (1810) and the second DU (1815). The method by which the CU (1805) communicates with the first DU (1810) or the second DU (1815) may utilize the F1AP (F1 application protocol) or may be a method not defined in the standard, such as OAM. The CU (1805) may be connected to a smaller or larger number of DUs. One or more DUs (1810, 1815) serviced by one CU (1805) may be combined and referred to as a base station, and communication between the base station and the SF (1820) and other core network entities (e.g., AMF) may be performed by the CU (1805). The base station may directly or indirectly transmit and receive messages or information with the SF (1820). As illustrated in the example of FIG. 7, SF can integrate functions into LMF. When a base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and SF can be the messages or information transmitted and received by the base station and LMF. The method by which the base station exchanges messages or information with the LMF or SF can be the examples illustrated in FIG. 7, FIG. 8, FIG. 9, and FIG. 10, or another method not described in the present disclosure.

[0274] According to one embodiment, the CU (1805) can transmit a predetermined message (e.g., a CU-DU TRP information request) to at least one of the first DU (1810) or the second DU (1815) to obtain information about a DU and information about a transmission-reception point (TRP) managed by the DU. The transmission of the CU-DU TRP information request (1831, 1835) can be triggered by a periodic update procedure for a DU from which the CU has previously collected information. The CU-DU TRP information request (1831, 1835) can be triggered by an OAM. The CU (1805) can include a request for information to be obtained from at least one TRP in the CU-DU TRP information request (1831, 1835). The information that the CU requests from the DU can include at least some of the following:

[0275] - TRP list: The TRP list may contain one or more TRP IDs (unique identifiers that can distinguish TRPs within a base station or in a DU), and the DU may respond with information corresponding to the TRP IDs included in the TRP list. If the TRP list is not included, the DU may respond with all TRP information it manages.

[0276] - TRP information type: An indicator indicating that ISAC information is being requested.

[0277] - TRP geographical coordinates: You can request the location of the TRP.

[0278] - TRP spatial direction information: You can request the direction of the TRP or the angle per beam.

[0279] - TRP type: You can request the characteristics of TRP including tp, rp, and trp.

[0280] - Tx power: Current and maximum transmission power of TRP

[0281] - ISAC capability: You can request information on the ability to perform ISAC operations for each TRP.

[0282] - ISAC RS type: You can request which type of RS can be transmitted or received for ISAC purposes. For example, DL-PRS (downlink positioning reference signal), SSB (synchronization signal block), CSI-RS (channel state information reference signal), SRS (sounding reference signal), etc. can be responded to.

[0283] - ISAC RS bandwidth: You can request the bandwidth for transmitting or transmitting RS for ISAC purposes. For example, the absolute radio frequency channel number (ARFCN), carrier bandwidth, point A, and subcarrier spacing (SCS) can be responded to.

[0284] - ISAC RS frequency-scale pattern: You can request the frequency characteristics or pattern of RS for ISAC purposes. For example, comb size, offset, cyclic shift, and frequency hopping can be responded to.

[0285] - ISAC RS time-scale pattern: You can request the temporal characteristics or patterns of RS for ISAC purposes. For example, the number of symbols, repetition factor, resource set periodicity, etc. can be responded to.

[0286] - On-demand ISAC RS pattern: TRP can request the bandwidth, frequency, time characteristics or pattern of RS for ISAC purposes that can be transmitted. For example, the allowed values ​​can be responded in the form of a list or a bit string, and in the case of a bit string, the value corresponding to each bit can be expressed as 1 if it is settable and 0 if it is not settable.

[0287] - ISAC processing capability: DU can request the ability to compute measurement results obtained through ISAC operations. For example, whether the measurement results are computed as final results (e.g., size, speed, material of an object) or as intermediate results with a predefined level, calculation accuracy, calculation delay time, measurable range, etc. can be responded to, and each capability can be responded to with a level (e.g., 0 (highest) to 9 (lowest)) or a predefined value.

[0288] - supported event: A DU can request whether it has the ability to determine that a specific condition related to ISAC is satisfied. The specific condition may be, for example, that an ISAC operation can be performed at a specific time, that an ISAC operation can be performed at a specific cycle, that a specific TRP is in an operational state, that a specific object is sensed after an ISAC operation is performed, that a specific timer expires, or that a specific action (e.g., position, direction, speed, gesture) on an object is satisfied after an ISAC operation is performed.

[0289] According to one embodiment, the first DU (1810) or the second DU (1815) may transmit a predetermined message (e.g., a CU-DU TRP information response) to the CU (1805) in response to information requested by the CU-DU TRP information request (1831, 1835). The CU-DU TRP information response (1832, 1836) may include at least a portion of the information requested by the CU-DU TRP information request (1831, 1835). If the first DU (1810) or the second DU (1815) cannot respond to some of the information requested in the CU-DU TRP information request (1831, 1835) or does not support the requested functionality, the CU-DU TRP information response (1832, 1836) may notify the CU by including at least one of: no value, an indication that the requested information cannot be responded to or is not supported, or a reason for not being able to respond (e.g., TRP does not support ISAC, wrong TRP ID was requested).

[0290] According to one embodiment, if the first DU (1810) or the second DU (1815) cannot respond to some of the information requested in the CU-DU TRP information request (1831, 1835) or does not support the requested functionality, the first DU (1810) or the second DU (1815) may respond to the CU (1805) with a predetermined message (e.g., CU-DU TRP information failure). The DU may inform the CU of the CU-DU TRP information failure (1833, 1837) by including at least one of an indication that the DU cannot respond to or does not support the requested information, or a reason for not being able to respond (e.g., TRP does not support ISAC, wrong TRP ID requested).

[0291] According to one embodiment, when a part of the information responded with the CU-DU TRP information response (1832, 1836) is updated, the first DU (1810) or the second DU (1815) may transmit a predetermined message (e.g., CU-DU TRP information update) to the CU (1805) to notify the CU (1805) of the updated information. The DU may include at least one of the information updated in the previously transmitted CU-DU TRP information response (1832, 1836) or the CU-DU TRP information update (1834, 1838). The DU may include all information requested in the CU-DU TRP information request (1831, 1835) in the CU-DU TRP information update (1834, 1838).

[0292] According to one embodiment, the SF (1820) and the base station may perform at least one of the following procedures as needed: TRP information request (1839), TRP information response (1840), TRP information failure (1841), and TRP information update (1842). These procedures may follow the example illustrated in FIG. 11.

[0293] Procedures such as CU-DU TRP information request (1831, 1835), CU-DU TRP information response (1832, 1836), CU-DU TRP information failure (1833, 1837), and CU-DU TRP information update (1834, 1838) are depicted in the drawing to be performed before the base station and SF (1820) perform the TRP information exchange operation (1839, 1840, 1841, 1842), but may be performed during the process of performing the TRP information exchange operation (1839, 1840, 1841, 1842), or during the process of performing the TRP information exchange operation (1839, 1840, 1841, 1842), before the base station and SF (1820) perform the TRP information exchange operation (1839, 1840, 1841, 1842), if necessary. It can be performed at at least one point after performing the TRP information exchange operation (1839, 1840, 1841, 1842). For example, the CU-DU TRP information exchange operation (1831, 1832, 1833, 1834, 1835, 1836, 1837, 1838) can be triggered by the TRP information exchange operation (1839, 1840, 1841, 1842). For example, the CU-DU TRP information exchange operation (1831, 1832, 1833, 1834, 1835, 1836, 1837, 1838) can be performed after the TRP information exchange operation (1839, 1840, 1841, 1842) to update the information.

[0294] FIG. 19 is a diagram illustrating an example of a signal flow in which a CU sets a reference signal transmission to a DU in a base station CU-DU separation structure of a wireless communication system according to various embodiments of the present disclosure.

[0295] Referring to FIG. 19, a CU (1905) is connected to a first DU (1910) and a second DU (1915). The CU (1905) may communicate with the first DU (1910) or the second DU (1915) using F1AP (F1 application protocol) or a method not defined in a standard, such as OAM. The CU (1905) may be connected to fewer or more DUs. One or more DUs (1910, 1915) serviced by a single CU (1905) may be combined and referred to as a base station, and communication between the base station and the SF (1920) and other core network entities (e.g., AMF) may be performed by the CU (1905). The base station may directly or indirectly transmit and receive messages or information with the SF (1920). As illustrated in the example of FIG. 7, SF can integrate functions into LMF. When a base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and SF can be the messages or information transmitted and received by the base station and LMF. The method by which the base station exchanges messages or information with the LMF or SF can be the examples illustrated in FIG. 7, FIG. 8, FIG. 9, and FIG. 10, or another method not described in the present disclosure.

[0296] In one embodiment, the SF may transmit a predetermined message (e.g., an RS configuration request) to the base station to configure or request the base station to transmit an RS that can be used for ISAC purposes, to obtain information about the RS currently being transmitted, or to configure or request the base station to stop transmitting an RS. This procedure may follow the example illustrated in FIG. 13.

[0297] According to one embodiment, the CU (1905) may be configured or requested to transmit an RS for ISAC purposes to one or more TRPs, or may be configured or requested to obtain RS information currently being transmitted, or may be configured or requested to stop transmitting an RS, through communication with the SF (1920), other network entities, or through an undisclosed method (e.g., a request from a carrier or a base station manager). The CU (1905) may transmit a predetermined message (e.g., a CU-DU RS configuration request) to the first DU (1910) or the second DU (1915) to perform an action related to the associated TRP. The CU-DU RS configuration request (1932, 1935) may include at least some of the information included in the RS configuration request (1931) received from the SF (1920). The CU-DU RS configuration request (1932, 1935) may include at least some of the information of the RS configuration request illustrated in FIG. 13.

[0298] According to one embodiment, the first DU (1910) or the second DU (1915) may be requested to transmit RS from the CU (1905) through a CU-DU RS configuration request (1932, 1935), and may respond by transmitting a predetermined message (e.g., a CU-DU RS configuration response) to the CU (1905) if RS transmission for a certain RS identifier can be normally performed. The CU-DU RS configuration response (1933, 1936) may include an RS identifier for normally performing RS transmission. The CU-DU RS configuration response (1933, 1936) may include information on an RS selected by the DU (e.g., an RS type, a frequency-scale pattern, a time-scale pattern, etc.) if RS transmission is requested with one or more on-demand values, RS characteristics, or QoS.

[0299] According to one embodiment, when the first DU (1910) or the second DU (1915) receives a request for RS information being transmitted from the CU (1905) through a CU-DU RS configuration request (1932, 1935), the first DU (1910) or the second DU (1915) may respond by transmitting a predetermined message (e.g., CU-DU RS configuration response) to the CU (1905). The CU-DU RS configuration response (1933, 1936) may include information about the RS being transmitted (e.g., RS type, frequency-scale pattern, time-scale pattern, etc.).

[0300] According to one embodiment, the first DU (1910) or the second DU (1915) may receive a request to stop RS transmission from the CU (1905) through a CU-DU RS configuration request (1932, 1935), and may respond by transmitting a predetermined message (e.g., a CU-DU RS configuration response) to the CU (1905) if the RS transmission stop for a certain RS identifier can be performed normally. The CU-DU RS configuration response (1933, 1936) may include the RS identifier for which RS transmission was normally stopped.

[0301] According to one embodiment, the first DU (1910) or the second DU (1915) may receive a CU-DU RS configuration request (1932, 1935) from the CU (1905), and, if it is unable to perform or abort RS transmission for an identifier for at least a portion of the requested RS transmission, it may respond by transmitting a predetermined message (e.g., a CU-DU RS configuration response) to the CU (1905). The CU-DU RS configuration response (1933, 1936) may include a TRP identifier and an RS identifier for which the RS transmission cannot be performed. The first DU (1910) or the second DU (1915) may include a reason for not performing the RS transmission (e.g., TRP unavailable, unavailable due to TRP load, RS being used for another purpose, etc.) in the CU-DU RS configuration response (1933, 1936).

[0302] According to one embodiment, the first DU (1910) or the second DU (1915) may receive a CU-DU RS configuration request (1932, 1935) from the CU (1905), and if it is unable to perform or abort RS transmission for an identifier for at least a portion of the requested RS transmission, it may respond by transmitting a predetermined message (e.g., CU-DU RS configuration failure) to the CU (1905). The CU-DU RS configuration failure (1934, 1937) may include a TRP identifier and an RS identifier for which the RS transmission cannot be performed. The first DU (1910) or the second DU (1915) may include a reason for which the RS transmission cannot be performed (e.g., TRP unavailable, unavailable due to TRP load, RS being used for another purpose, etc.) in the CU-DU RS configuration failure (1934, 1937).

[0303] According to one embodiment, a base station may be requested to transmit an RS with an RS configuration request (1931), and may respond to the SF (1920) with a predetermined message (e.g., an RS configuration response) if RS transmission for a certain RS identifier can be performed normally. The RS configuration response (1938) may include an RS identifier for performing RS transmission normally. The RS configuration response (1938) may include information on an RS selected by the base station when RS transmission is requested based on one or more on-demand values, RS characteristics, or QoS.

[0304] According to one embodiment, when a base station receives a request for RS information being transmitted via an RS configuration request (1931), the base station may respond to the SF (1920) with a predetermined message (e.g., an RS configuration response). The RS configuration response (1938) may include information about the RS being transmitted.

[0305] According to one embodiment, the base station may be requested to stop RS transmission with an RS configuration request (1931), and if the RS transmission stop for a certain RS identifier can be normally performed, the base station may respond to the SF (1920) with a predetermined message (e.g., an RS configuration response). The RS configuration response (1938) may include an RS identifier for which RS transmission is normally performed.

[0306] According to one embodiment, the base station may receive an RS configuration request (1931) from the SF (1920) and, if the base station is unable to perform or abort an RS transmission for an identifier for at least a portion of the requested RS transmissions, may respond to the SF (1920) with a predetermined message (e.g., an RS configuration response). The RS configuration response (1938) may include a TRP identifier and an RS identifier for which the RS transmission cannot be performed. The base station may include a reason for not performing the RS transmission (e.g., TRP unavailable, unavailable due to TRP load, RS being used for another purpose, etc.) in the RS configuration response (1938).

[0307] According to one embodiment, the base station may receive an RS configuration request (1931) from the SF (1920) and, if the base station fails to perform RS transmission for an identifier for at least a portion of the requested RS transmissions, may respond to the SF (1920) with a predetermined message (e.g., RS configuration failure). The RS configuration failure may include a TRP identifier and an RS identifier for which the RS transmission cannot be performed. The base station may include a reason for failing to perform the RS transmission (e.g., TRP unavailable, unavailable due to TRP load, RS being used for another purpose, etc.) in the RS configuration failure (1939).

[0308] Procedures such as CU-DU RS configuration request (1932, 1935), CU-DU RS configuration response (1933, 1936), and CU-DU RS configuration failure (1934, 1937) are illustrated in the drawing to be performed while the base station and the SF (1920) are performing RS configuration operations (1931, 1938, 1939), but may be performed at least at one of the following points in time: before the base station and the SF (1920) perform the RS configuration operations (1931, 1938, 1939), during the process of performing the RS configuration operations (1931, 1938, 1939), or after performing the RS configuration operations (1931, 1938, 1939), if necessary.

[0309] FIG. 20 is a diagram illustrating an example of a signal flow in which a CU requests sensing from a DU in a base station CU-DU separation structure of a wireless communication system according to various embodiments of the present disclosure.

[0310] Referring to FIG. 20, the CU (2005) is connected to the first DU (2010) and the second DU (2015). The CU (2005) may communicate with the first DU (2010) or the second DU (2015) using F1AP (F1 application protocol) or may use a method not defined in the standard, such as OAM. The CU (2005) may be connected to fewer or more DUs. One or more DUs (2010, 2015) serviced by one CU (2005) may be combined and referred to as a base station, and communication between the base station and the SF (2020) and other core network entities (e.g., AMF) may be performed by the CU (2005). The base station may directly or indirectly transmit and receive messages or information with the SF (2020). As illustrated in the example of FIG. 7, SF can integrate functions into LMF. When a base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and SF can be the messages or information transmitted and received by the base station and LMF. The method by which the base station exchanges messages or information with the LMF or SF can be the examples illustrated in FIG. 7, FIG. 8, FIG. 9, and FIG. 10, or another method not described in the present disclosure.

[0311] In one embodiment, the SF (2020) may transmit a predetermined message (e.g., an ISAC measurement request) to the base station to instruct the base station and TRP to transmit, receive, and measure ISAC RSs. This procedure may follow the example illustrated in FIG. 14.

[0312] According to one embodiment, the CU (2005) may transmit a predetermined message (e.g., CU-DU ISAC measurement request) to the first DU (2010) and the second DU (2015) to instruct the first DU (2010), the second DU (2015) and the TRP managed by the DU to transmit ISAC RS, receive ISAC RS, and measure. The CU-DU ISAC measurement request (2032, 2035) may include at least some of the information included in the ISAC measurement request (2031) received from the SF to control the ISAC operation of the DU or obtain information. The CU-DU ISAC measurement request (2032, 2035) may include at least some of the information exemplified in the ISAC measurement request of FIG. 14.

[0313] According to one embodiment, the first DU (2010) and the second DU (2015) may report the measurement results by transmitting a predetermined message (e.g., CU-DU ISAC measurement report) to the CU (2005) when the CU (2005) requests measurement with a CU-DU ISAC measurement request (2032, 2035) and when a reporting condition is not set or the reporting condition is satisfied.

[0314] According to one embodiment, the CU-DU ISAC measurement report (2033, 2036) may include information requested by the CU (2005) in the CU-DU ISAC measurement request (2032, 2035). It may also include at least a portion of the following information:

[0315] - Accuracy of measurement results: It can be expressed as the accuracy of the measurement results, range of accuracy, confidence level, uncertainty, etc.

[0316] - Additional measurement-related information: This may include the type of ISAC RS used in the measurement, the time the ISAC RS was received (timestamp), and the received strength of the ISAC RS (e.g., RSRP, RSSI, SINR).

[0317] According to one embodiment, when measurement using the requested TRP is impossible (e.g., when the setting of the TRP is changed, or when the ISAC RS is no longer received, etc.), the first DU (2010) and the second DU (2015) may notify the CU (2005) by transmitting a predetermined message (e.g., CU-DU ISAC measurement failure). The CU-DU ISAC measurement failure (2034, 2037) may include a reason why measurement is impossible (e.g., TRP not available, configuration not available, resource not available, sensing signal not detected, etc.).

[0318] According to one embodiment, the CU (2005) may report the measurement result requested from the SF (2020) via an ISAC measurement request (2031) in a procedure for receiving the measurement result (e.g., CU-DU ISAC measurement failure) from the first DU (2010) and the second DU (2015), and may report the measurement result by transmitting a predetermined message (e.g., ISAC measurement report) to the SF (2020).

[0319] According to one embodiment, when a measurement using a TRP for which a measurement has been requested is impossible (e.g., when the setting of the TRP has changed, or when an ISAC RS is no longer received, or when a CU-DU ISAC measurement failure is received, etc.), the CU (2005) may transmit a predetermined message (e.g., ISAC measurement failure) to the SF (2020) to notify the SF. The ISAC measurement failure (2039) may include at least one of a measurement identifier (e.g., transaction ID) or a reason why the measurement is impossible (e.g., TRP not available, configuration not available, resource not available, sensing signal not detected, etc.). The ISAC measurement failure (2039) may include at least a part of the information included in the CU-DU ISAC measurement failure (2034, 2037).

[0320] In one embodiment, the SF (2020) may instruct the base station to stop the measurement by sending a predetermined message (e.g., ISAC measurement abort) when the measurement is no longer needed.

[0321] FIG. 21 is a diagram illustrating an example of a signal flow for SF to provide ISAC service through two base stations in a wireless communication system according to various embodiments of the present disclosure.

[0322] Referring to FIG. 21, the first base station and the second base station can directly or indirectly transmit and receive messages or information with the SF. As in the example illustrated in FIG. 7, the SF may have its functions integrated into the LMF. When the base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and the SF may be messages or information transmitted and received by the base station and the LMF. The method by which the base station exchanges messages or information with the LMF or the SF may be the examples illustrated in FIGS. 7, 8, 9, and 10, or other methods not described in the present disclosure.

[0323] According to one embodiment, SF (2115) may perform at least one of a TRP information request (2121, 2123) or a TRP information response (2122, 2124) to obtain TRP information of the first base station (2105), the second base station (2110), or the base station. This procedure may follow the example illustrated in FIG. 11.

[0324] According to one embodiment, SF (2115) may perform at least one of RS configuration request (2125) or RS configuration response (2126) procedures to configure ISAC RS transmission to the first base station (2105). Such procedures may follow the example illustrated in FIG. 13. In FIG. 21, it is assumed that SF determines that the first base station performs ISAC RS transmission.

[0325] According to one embodiment, the SF (2115) may transmit a predetermined message (e.g., an ISAC measurement request) to the second base station (2110) to instruct the second base station (2110) and the TRP to receive and measure ISAC RS. The ISAC measurement request (2127) may include at least some of the following information to control the ISAC operation of the second base station (2110) or to obtain information.

[0326] - Transaction ID

[0327] - Information indicating ISAC RS reception: ISAC RS transmission information (e.g., frequency-scale pattern, time-scale pattern, RS type, etc.) is included so that the receiving TRP can perform measurement of the ISAC RS. At this time, the TRP and beam identifier for receiving the ISAC RS may be included. The ISAC RS transmission information may be part of the RS transmission information that the SF (2115) instructed to the first base station (2105) through an RS configuration request (2125) (or may be an ISAC measurement request as in the example illustrated in FIG. 14), or may include part of the RS transmission information that the first base station (2105) transmitted to the SF (2115) through an RS configuration response (2126) (or may be an ISAC measurement report as in the example illustrated in FIG. 14).

[0328] - Event-based reporting conditions: The base station can perform the ISAC measurement reporting procedure if the reporting conditions indicated by the SF are met. Reporting conditions can include the conditions below, and two or more conditions can be combined.

[0329] * response time: You can request that SF receive measurement reports by a certain point in time.

[0330] * periodic: SF can be requested to receive measurement reports at specific intervals.

[0331] * TRP sensing availability: The base station can notify the SF when the indicated TRP becomes available for ISAC RS transmission or reception.

[0332] * Target object availability: The base station can notify the SF when an object detected in the measurement area enters or leaves the measurement area. The target object can be distinguished by a combination of shape, size, speed, material, etc., or can be an object corresponding to a predefined value (e.g., a person or a car).

[0333] * Motion event: When the motion of an object detected in the measurement area satisfies certain conditions, the base station can notify the SF. Motion can be identified by a combination of the object's shape, location, direction, and speed, or it can be an object corresponding to a predefined value (e.g., a fist clenching or unclenching motion).

[0334] - ISAC QoS: QoS required when the base station reports measurement results to the SF. QoS may include the time taken to report measurement results after receiving ISAC RS (response time), accuracy of measurement result reporting, etc.

[0335] - Measurement report characteristics: This can indicate the level of measurement results the base station includes in its measurement reports. For example, a request can be made to include raw measurement results in the measurement report, to include the measurement results in the measurement report in their entirety or in a processed form (e.g., RCS or micro-Doppler) for each data point, or to include object characteristics and locations calculated and included in the measurement report.

[0336] - Measurement characteristic indication: You can request the characteristics of the measurement results that the base station includes in the measurement report. For example, you can request that only the target object information (e.g., whether it is line of sight (LOS) or non-line of sight (NLOS), number of scattering points, shape, size, direction and speed of movement, material) that is the sensing target among the objects detected by the ISAC operation be reported, you can request that all objects detected by the ISAC operation be included in the measurement results, or you can request that only objects that satisfy specific conditions (e.g., whether it is line of sight (LOS) or non-line of sight (NLOS), number of scattering points, shape, size, direction and speed of movement, material) that are detected by the ISAC operation be included in the measurement results.

[0337] According to one embodiment, the second base station (2110) may report the measurement result by transmitting a predetermined message (e.g., an ISAC measurement report) to the SF (2115) when the SF (2115) requests measurement with an ISAC measurement request (2121) and if a reporting condition is not set or the reporting condition is satisfied. The measurement result may include the information requested by the ISAC measurement request (2121). In addition, the measurement result may include at least a portion of the following information.

[0338] - transaction ID

[0339] - Accuracy of measurement results: It can be expressed as the accuracy of the measurement results, range of accuracy, confidence level, uncertainty, etc.

[0340] - Additional measurement-related information: This may include the type of ISAC RS used in the measurement, the time the ISAC RS was received (timestamp), and the received strength of the ISAC RS (e.g., RSRP, RSSI, SINR).

[0341] According to one embodiment, when SF (2115) determines that ISAC RS transmission operation of the first base station (2105) is no longer necessary, it may perform at least one procedure among RS configuration request (2129) or RS configuration response (2130) to instruct the first base station (2105) to stop ISAC RS transmission. This procedure may follow the example illustrated in FIG. 13.

[0342] FIG. 22 is a diagram illustrating an example of a signal flow for providing an ISAC service through two base stations in a structure in which an SF of a wireless communication system according to various embodiments of the present disclosure is located inside a base station.

[0343] Referring to FIG. 22, the first base station (2205) and the second base station (2210) can transmit and receive messages or information between each other. The method by which the first base station (2205) and the second base station (2210) communicate can use the XnAP (Xn application protocol) of 3GPP, or a separate method not described such as OAM. The first base station (2205) and the second base station (2210) can embed the function of SF within the base station. The first base station (2205) and the second base station (2210) can transmit and receive messages or information for performing ISAC-related operations with an entity having the function of SF that exists in a separate location other than the core network. The SF function of the first base station (2205) and the second base station (2210) can use an inter-base station communication protocol (e.g., XnAP) to communicate with other base stations.

[0344] In one embodiment, the first base station (2205) and the second base station (2210) may receive a request to perform ISAC services through communication with other network entities or through an undisclosed method (e.g., a request from a telecommunications carrier or a base station manager).

[0345] FIG. 22 may be a diagram illustrating a case where the SF function of the second base station (2210) determines that the first base station (2205) transmits an ISAC RS and the second base station (2210) receives the ISAC RS to perform ISAC measurement. In other scenarios, such as a case where the SF function of the first base station (2205) determines that the first base station (2205) transmits an ISAC RS and the second base station (2210) receives the ISAC RS to perform ISAC measurement, ISAC service can be provided through a combination of similar procedures and existing procedures.

[0346] According to one embodiment, the second base station (2210) may transmit a predetermined message (e.g., a TRP information request) to the first base station (2205) to obtain information of the first base station (2205) and information of TRPs managed by the first base station (2205). The transmission of the TRP information request (2221) may be triggered by a periodic update procedure for base stations from which the second base station (2210) has previously collected information. The TRP information request (2221) may be triggered by OAM. The second base station (2210) may include in the TRP information request (2221) an information request to be obtained from at least one or more TRPs. The TRP information request (2221) may include at least some of the information exemplified in the TRP information request of FIG. 11.

[0347] According to one embodiment, the first base station (2205) may transmit a predetermined message (e.g., a TRP information response) to the second base station (2210) in response to information requested by the TRP information request (2221). The TRP information response (2222) may include at least some of the information illustrated in the TRP information response of FIG. 11.

[0348] According to one embodiment, the second base station (2210) may transmit a predetermined message (e.g., an RS configuration request) to the first base station (2205) to configure or request the first base station (2205) to transmit an RS that can be used for ISAC purposes, to obtain information about the RS currently being transmitted, or to configure or request the first base station (2205) to stop transmitting an RS. The RS configuration request (2223) may include at least some of the information illustrated in the RS configuration request of FIG. 13.

[0349] According to one embodiment, the first base station (2205) may receive an RS transmission request from the second base station (2210) through an RS configuration request (2223), and may respond by transmitting a predetermined message (e.g., an RS configuration response) to the second base station (2210) if RS transmission for a certain RS identifier can be performed normally. The RS configuration response (2224) may include an RS identifier for performing RS transmission normally. The RS configuration response (2224) may include information on an RS selected by the first base station (2205) when RS transmission is requested with one or more on-demand values, RS characteristics, or QoS (e.g., RS type, frequency-scale pattern, time-scale pattern, etc.).

[0350] According to one embodiment, the second base station (2210) can measure the ISAC RS transmitted by the first base station (2205) based on the RS configuration response (2224) of the first base station (2205).

[0351] In one embodiment, the second base station (2210) may transmit a predetermined message (e.g., an RS configuration request) to the first base station (2205) to instruct the first base station (2205) to stop measurement when the ISAC RS transmission of the first base station (2205) is no longer needed. The first base station (2205) may transmit an RS configuration response (2227) to the second base station (2210) in response to the RS configuration request (2226). The RS configuration request (2226) and the RS configuration response (2227) may include at least a portion of the information illustrated in FIG. 13.

[0352] FIG. 23 is a diagram illustrating an example of a signal flow in which a base station requests SF to calculate a sensing result in a wireless communication system according to various embodiments of the present disclosure.

[0353] Referring to FIG. 23, the base station (2305) can directly or indirectly transmit and receive messages or information with the SF (2310). As in the example illustrated in FIG. 7, the SF may have its functionality integrated with the LMF. When the base station transmits and receives ISAC information with the LMF, the messages or information received by the base station and the SF may be messages or information transmitted and received by the base station and the LMF. The method by which the base station exchanges messages or information with the LMF or SF may be the examples illustrated in FIGS. 7, 8, 9, and 10, or other methods not described in the present disclosure.

[0354] In one embodiment, the base station (2305) may request ISAC services through communication with another network entity or through an undisclosed method (e.g., a request from a telecommunications carrier or a base station manager). The base station (2305) may retain the results of measuring the ISAC RS through operations such as the examples described above. The base station (2305) may calculate the measurement results on its own through operations such as the examples described above to derive sensing results of objects such as target objects. The base station (2305) may not have the ability to calculate the measurement results and may therefore request calculation of the measurement results from another entity (e.g., SF (2310)).

[0355] According to one embodiment, the base station (2305) may perform at least one of an SF information request (2321) or an SF information response (2322) to obtain information of an SF (2310). This procedure may follow the example illustrated in FIG. 12.

[0356] According to one embodiment, the base station (2305) may select the SF (2310) to request calculation by considering the sensing result calculation capability (e.g., ISAC processing capability of FIG. 12) of the SF (2310) obtained through a method such as an SF information exchange procedure (e.g., 2321, 2322) or OAM.

[0357] In one embodiment, the base station (2305) may transmit a measurement result or an intermediate calculation result to the selected SF (2310) and may transmit a predetermined message (e.g., an ISAC calculation request) to the SF (2310) to request the SF to obtain the final calculation result. For example, the ISAC calculation request (2323) may include at least a portion of the following information:

[0358] - transaction ID

[0359] - Target object information, sensing object information: This can be an object that can be distinguished by combining shape, size, speed, material, etc., or can correspond to a predefined value (e.g., a person or a car).

[0360] - Measurement results: Measurement results held by the base station, which may be information such as RCS or micro-doppler.

[0361] Intermediate Results: Intermediate results calculated using measurement results held by the base station, which may be an intermediate step toward calculating the final result. The base station may include intermediate results instead of measurement results to reduce the amount of information included in the ISAC calculation request (2323), or may include all information to increase accuracy.

[0362] - Intermediate result level: The intermediate result level can be, for example, 0 (highest) to 9 (lowest) or a predefined value. SF can refer to the intermediate result level to calculate the final result from the intermediate result calculated by the base station.

[0363] - RS transmission information: May include RS information for deriving measurement results, such as RS type, frequency-scale pattern, and time-scale pattern. SF may refer to RS transmission information to calculate measurement results or intermediate results into final results.

[0364] - QoS: This may include the time the base station expects to receive the final result calculated by the SF (e.g., latency), and the accuracy of the final result calculated by the SF (e.g., accuracy).

[0365] According to one embodiment, when SF (2310) receives an ISAC calculation request (2323) from base station (2305) and can provide the requested calculation result to base station (2305), SF (2310) may respond by transmitting a predetermined message (e.g., ISAC calculation response) to base station (2305). For example, ISAC calculation response (2324) may include at least a portion of the following information:

[0366] - Transaction ID

[0367] - Sensing object information: This can be information about a sensing object requested by the base station, or an object that was not requested but can be identified through calculations. It can be distinguished by combining the object's shape, size, speed, material, etc., or it can be a predefined value (e.g., a person or a car). It can include the object's location, speed, direction, etc.

[0368] - Target object information: Information about the target object requested by the base station. This can be distinguished by combining the shape, size, speed, material, etc. of the target object, or it can be a predefined value (e.g., a person or a car). It can include the object's location, speed, direction, etc.

[0369] - Accuracy of measurement results: It can be expressed as the accuracy of the measurement results, range of accuracy, confidence level, uncertainty, etc.

[0370] According to one embodiment, when SF (2310) receives an ISAC calculation request (2323) from base station (2305) and cannot provide the requested calculation result to base station (2305), SF (2310) may respond by transmitting a predetermined message (e.g., ISAC calculation failure) to base station (2305). For example, ISAC calculation failure (2325) may include at least a portion of the following information:

[0371] - Transaction ID

[0372] - Failure cause: The reason why the calculation result cannot be provided to the base station, which may include, for example, overload of SF, inability to satisfy the requested QoS, or lack of requested calculation capability.

[0373] According to one embodiment, the base station (2305) may request a new SF to calculate the measurement result if the previously selected SF (2310) transmits an ISAC calculation failure (2325) and cannot proceed with the calculation.

[0374] FIG. 24 is a diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0375] Referring to FIG. 24, the terminal may include a transceiver (2410), a control unit (2420), and a storage unit (2430). The transceiver (2410), the control unit (2420), and the storage unit (2430) may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver (2410), the control unit (2420), and the storage unit (2430) may be implemented in the form of a single chip.

[0376] The transceiver (2410) is a general term for the receiver and transmitter of a terminal, and can transmit and receive signals with a base station, another terminal, or a network entity. The signals transmitted and received with the base station may include control information and data. The transceiver (2410) may, for example, receive system information from the base station and receive a synchronization signal or a reference signal. To this end, the transceiver (2410) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts the received signal. However, this is only one embodiment of the transceiver (2410), and the components of the transceiver (2410) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (2410) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals. In addition, the transceiver (2410) can receive a signal through a wireless channel and output it to the control unit (2420), and transmit the signal output from the control unit (2420) through the wireless channel. In addition, the transceiver (2410) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a network entity through a wired or wireless network.

[0377] The storage unit (2430) can store programs and data necessary for the operation of the terminal. In addition, the memory (2430) can store control information or data included in signals acquired from the terminal. The storage unit (2430) can be configured as a storage medium or a combination of storage media, such as a ROM, RAM, hard disk, CD-ROM, and DVD.

[0378] In the present invention, the control unit (2420) may be defined as a circuit or application-specific integrated circuit, or at least one processor. The processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (2420) may control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the control unit (2420) may control the signal flow between each block to perform operations according to the flowchart described in the present disclosure.

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

[0380] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0381] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0382] The 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.

[0383] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The 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 disclosure.

[0384] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0385] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0386] In the specific embodiments of the present disclosure described above, components included in the invention are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0387] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. At the base station: At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor so that the base station: Receive a TRP information request message from a sensing function (SF) entity to request transmission-reception point (TRP) information, To the above SF entity, a TRP information response message including the TRP information is transmitted, Receive an RS configuration request message for setting a reference signal (RS) from the above SF entity, To the above SF entity, send an RS configuration response message containing information about the RS, Receive an ISAC (integrated sensing and communication) measurement request message for requesting sensing from the above SF entity, Based on the above ISAC measurement request message, perform ISAC measurement, A base station that transmits an ISAC measurement report message to the SF entity to report the results of the ISAC measurement.

2. In paragraph 1, A base station, wherein the ISAC measurement request message includes at least one piece of information from among information indicating transmission of the RS, information indicating reception of the RS, and information regarding transmission conditions of the ISAC measurement report message.

3. In paragraph 1, A base station, wherein the ISAC measurement report message includes at least one of information regarding the accuracy of the ISAC measurement, information regarding the type of RS used in the ISAC measurement, or information regarding the reception strength of the RS.

4. In paragraph 1, A base station, wherein the TRP information response message includes at least one of information regarding the ability to perform the ISAC measurement, location information of the TRP, type information of the TRP, object sensing capability information, or information regarding the ability to calculate the result of the ISAC measurement.

5. In paragraph 1, The above instructions are executed individually or in any combination by the at least one processor so that the base station: Send a message to the SF entity through the access and mobility management function (AMF) entity, A base station that receives messages from the SF entity through the AMF entity.

6. For sensing function (SF) entities: at least one processor; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor, such that the SF entity: Transmit a TRP information request message to the base station to request transmission-reception point (TRP) information, Receive a TRP information response message including the TRP information from the base station, To the above base station, transmit an RS configuration request message for setting a reference signal (RS), Receive an RS configuration response message including information about RS from the base station, To the above base station, transmit an ISAC (integrated sensing and communication) measurement request message to request sensing, An SF entity that receives an ISAC measurement report message from the base station to report the results of ISAC measurements performed by the base station.

7. In paragraph 6, The ISAC measurement request message is an SF entity that includes at least one piece of information from among information indicating transmission of the RS, information indicating reception of the RS, and information regarding transmission conditions of the ISAC measurement report message.

8. In paragraph 6, The ISAC measurement report message is an SF entity that includes at least one of information regarding the accuracy of the ISAC measurement, information regarding the type of RS used in the ISAC measurement, or information regarding the reception strength of the RS.

9. In paragraph 6, An SF entity in which the TRP information response message includes at least one of information regarding the ability to perform the ISAC measurement, location information of the TRP, type information of the TRP, object sensing capability information, or information regarding the ability to calculate the result of the ISAC measurement.

10. In paragraph 1, The above commands cause the SF entity to: Transmit a message to the base station through the access and mobility management function (AMF) entity, An SF entity that receives messages from the base station through the AMF entity.

11. In the operating method of the base station, A step of receiving a transmission-reception point (TRP) information request message for requesting TRP information from a sensing function (SF) entity; A step of transmitting a TRP information response message including the TRP information to the SF entity; A step of receiving an RS configuration request message for setting a reference signal (RS) from the above SF entity; A step of transmitting an RS configuration response message including information about RS to the above SF entity; A step of receiving an integrated sensing and communication (ISAC) measurement request message for requesting sensing from the above SF entity; A step of performing ISAC measurement based on the above ISAC measurement request message; and A method of operating a base station, comprising the step of transmitting an ISAC measurement report message for reporting the results of the ISAC measurement to the SF entity.

12. In paragraph 11, A method of operating a base station, wherein the ISAC measurement request message includes at least one piece of information from among information indicating transmission of the RS, information indicating reception of the RS, and information regarding transmission conditions of the ISAC measurement report message.

13. In paragraph 11, A method of operating a base station, wherein the ISAC measurement report message includes at least one of information regarding the accuracy of the ISAC measurement, information regarding the type of RS used in the ISAC measurement, or information regarding the reception strength of the RS.

14. In paragraph 11, A method of operating a base station, wherein the TRP information response message includes at least one of information regarding the ability to perform the ISAC measurement, location information of the TRP, type information of the TRP, object sensing capability information, or information regarding the ability to calculate the result of the ISAC measurement.

15. In the operation method of the sensing function (SF) entity, A step of transmitting a TRP information request message to a base station to request transmission-reception point (TRP) information; A step of receiving a TRP information response message including the TRP information from the base station; A step of transmitting an RS configuration request message to the above base station for setting a reference signal (RS); A step of receiving an RS configuration response message including information about RS from the base station; A step of transmitting an ISAC measurement request message to the base station to request sensing; and An operating method of an SF entity, comprising the step of receiving an ISAC measurement report message for reporting the results of ISAC measurements performed by the base station from the base station.

Images