Method and apparatus for providing sensing service in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a base station in a wireless communication system may comprise the steps of: receiving, from a terminal, first information on a capability of the terminal related to sensing; transmitting the first information to a sensing function entity; receiving, from the sensing function entity, second information related to a configuration for the sensing; transmitting, to the terminal, third information related to a configuration of the terminal for the sensing; receiving a report on the sensing from the terminal; and transmitting the report to the sensing function entity.

Description

Method and apparatus for providing sensing services in a wireless communication system

[0001] The present disclosure generally relates to a wireless communication system, and more specifically, to a method and apparatus for providing a combined service of sensing and communication using a base station and a terminal 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 frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

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

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

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

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

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

[0008] The present disclosure aims to provide a method and apparatus for providing a combined sensing and communication service using a base station and a terminal in a wireless communication system.

[0009] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs from the description below.

[0010] According to an embodiment of the present disclosure, a method performed by a base station of a wireless communication system may include: receiving first information regarding the capability of the terminal related to sensing from a terminal; transmitting the first information to a sensing function entity; receiving second information related to a setting for the sensing from the sensing function entity; transmitting third information related to the setting of the terminal for the sensing to the terminal; receiving a report regarding the sensing from the terminal; and transmitting the report to the sensing function entity.

[0011] According to an embodiment of the present disclosure, a combined service of sensing and communication using a base station and a terminal is provided.

[0012] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

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

[0014] FIG. 2 is a diagram showing base stations and core network entities of a wireless communication system according to various embodiments of the present disclosure.

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

[0016] FIG. 4 is a drawing illustrating the structure of a terminal according to an embodiment of the present disclosure.

[0017] FIG. 5 is a diagram illustrating the structure of an SF in a wireless communication system according to various embodiments of the present disclosure.

[0018] FIG. 6 is a diagram illustrating examples in which a terminal senses a signal transmitted by a base station in a wireless communication system according to various embodiments of the present disclosure and provides an ISAC service.

[0019] FIG. 7 is a diagram illustrating examples in which a base station senses a signal transmitted by a terminal in a wireless communication system according to various embodiments of the present disclosure and provides an ISAC service.

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

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

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

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

[0024] FIG. 12 is a diagram illustrating the structure of a communication protocol between a terminal and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0025] FIG. 13 is a diagram illustrating the structure of a communication protocol between a terminal and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0026] FIG. 14 is a diagram illustrating the structure of a communication protocol between a terminal and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0027] FIG. 15 is a diagram illustrating the structure of a communication protocol between a terminal and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0028] FIG. 16 is a diagram illustrating an example of a signal flow in which a UE performs an association procedure with an SF in a wireless communication system according to various embodiments of the present disclosure.

[0029] FIG. 17 is a diagram illustrating an example of a signal flow in which a UE performs an association update procedure with an SF in a wireless communication system according to various embodiments of the present disclosure.

[0030] FIG. 18 is a diagram illustrating an example of a signal flow in which a UE performs a disassociation procedure with an SF in a wireless communication system according to various embodiments of the present disclosure.

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

[0032] FIG. 20 is a diagram illustrating an example of a signal flow in which an SF selects a terminal and a base station to perform an ISAC operation in a wireless communication system according to one embodiment of the present disclosure.

[0033] FIG. 21 is a diagram illustrating an example of a signal flow in which an SF instructs a base station and a terminal to perform an ISAC operation using a downlink ISAC reference signal in a wireless communication system according to one embodiment of the present disclosure.

[0034] FIG. 22 is a diagram illustrating an example of a signal flow in which an SF instructs a base station and a terminal to perform an ISAC operation using a downlink ISAC reference signal in a wireless communication system according to one embodiment of the present disclosure.

[0035] FIG. 23 is a diagram illustrating an example of a signal flow in which an SF instructs a base station and a terminal to perform an ISAC operation using an uplink ISAC reference signal in a wireless communication system according to one embodiment of the present disclosure.

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

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

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

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

[0040] In describing the embodiments of the present disclosure, the focus is primarily on the New Radio (NR), which is a wireless access network, and the Packet Core 5G System, 5G Core Network, or NG Core (Next Generation Core), which is a core network, as specified by the 3rd Generation Partnership Project (3GPP), a mobile communication standardization organization. However, the main point of the present disclosure is that it can be applied to other communication systems having a similar technical background with slight modifications without significantly departing from the scope of the present disclosure, and this will be possible at the judgment of a person with skilled technical knowledge in the technical field of the present disclosure.

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

[0042] The following terms used in the description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms used herein, and other terms referring to objects having equivalent technical meanings may be used.

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

[0044] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

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

[0046] In this embodiment, the term "part" refers to a software or hardware component such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and '~parts' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Also, in the embodiments, the '~part' may include one or more processors.

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

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

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

[0050] In addition, standardization is underway in the field of wireless 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) which provides nodes to expand network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) to incorporate Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

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

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

[0053] The present disclosure relates to a method and apparatus for providing a base station-based combined sensing and communication service. More specifically, the present disclosure relates to a method for exchanging messages between a base station and a sensing function (SF) to provide a base station-based combined sensing and communication service in a 3GPP system, a method for the base station and the SF to acquire 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 the sensing result, and a method and apparatus for the base station or the SF to report to an entity that requested the sensing.

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

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

[0056] In FIG. 1, the NR gNB (120) can correspond to the eNB (140) of an LTE system. The NR gNB (120) is connected to the NR UE (150) via a wireless channel and can provide a superior service compared to the eNB (140). In a wireless communication system, since all user traffic is serviced through a shared channel, a device is required to collect state information such as the buffer status, available transmission power status, and channel status of the UEs and perform scheduling, and the NR gNB (120) can handle this. A single NR gNB (120) can typically control multiple cells. To achieve ultra-high-speed data transmission compared to LTE, a bandwidth greater than the maximum bandwidth of LTE can be utilized, and beamforming technology can be additionally incorporated by using the OFDM method as the wireless access technology. Additionally, an Adaptive Modulation and Coding (AMC) method can be applied to determine the modulation scheme and channel coding rate according to the terminal's channel status. The NR CN (110) can perform functions such as mobility support and QoS settings. The NR CN (110) is a device responsible for various control functions as well as mobility management functions for terminals, and can be connected to multiple base stations. In addition, the wireless communication system can be linked with an LTE system, and the NR CN (110) can be connected to the MME (130) via a network interface. The MME (130) can be connected to the eNB (140).

[0057] FIG. 2 is a diagram showing base stations and core network entities of a wireless communication system according to various embodiments of the present disclosure.

[0058] Referring to FIG. 2, base stations and core network entities of a wireless communication system can communicate with each other through a service-based interface (SBI) and a reference point interface. Although the drawing illustrates the use of a service-based interface, the communication interface between each network entity may be a reference point interface.

[0059] Base stations and core network entities may include at least some of the following to provide location services (LCS), and in addition to the entities included in the drawings, entities to support various functions of 5G and wireless communication, such as entities related to billing and entities related to user data transmission and reception, may be included. Furthermore, the operation of the following network functions has been described primarily with respect to functions for providing LCS, and various functions not described in this disclosure may be included for wireless communication.

[0060] The NEF (network exposure function, 201) can provide location services to an internal or external AF (204). The AF (204) can access location services through the NEF (201) via an API. Based on QoS requirements, the NEF (201) can forward a location request to the GMLC (209) or request an event exposure from the AMF (206). When the NEF (201) uses event exposure to the AMF (206), it can request routing information and / or privacy information of the target UE (212) from the UDM (203).

[0061] A UDR (unified data repository, 202) may contain privacy information of UEs (212) that are subject to location services. When an AMF (206) receives new privacy information of a UE (212), it may update the privacy information of the UE (212) stored in the UDR (202) through a UDM (203).

[0062] UDM (unified data management, 203) contains the LCS privacy profile and routing information of an LCS subscriber. UDM (203) can be accessed from AMF (206), GMLC (209), and NEF (201).

[0063] The AF (application function, 204) can access the LCS service via the GMLC (209) or AMF (206). The external AF (204) can access the LCS service via the NEF (201).

[0064] NWDAF (network data analytics function, 205) can directly access GMLC (209) to collect UE (212) location information.

[0065] The AMF (access and mobility management function, 206) may include location request and positioning management functions for the target UE (212). The AMF is accessible to the GMLC (209) and NEF (201), and is accessible to the N2 reference point to the RAN (213) and to the N1 reference point to the UE (212).

[0066] The SMF (session management function, 207) may include the session management function of the UE (212) in the 5G core network. The SMF (207) manages resources in the user plane and interacts with the UPF (214) and N4 reference point to enable the UPF to properly route and forward the user's data packets.

[0067] The LMF (location management function, 208) can manage overall management and resource scheduling for location services for UEs (212) that are registered or accessing the 5G core network. Additionally, the LMF (208) can perform result calculation or verification regarding the location and velocity of the target UE (212). The LMF (208) can receive location requests from the UE (212)'s serving AMF (206). The LMF (208) can exchange information with the UE (212) for UE-assisted or UE-based location estimation, or exchange information with the RAN (213), N3IWF (non-3GPP interworking function), or TNAN (trusted non-3GPP access network) to obtain location information.

[0068] The GMLC (gateway mobile location center, 209) may include functions to support LCS. One or more GMLC entities may exist in a single PLMN. The GMLC (209) communicates with an external LCS client (211) using a Le reference point, and AFs (204) and NFs (network functions) may access the GMLC (209) directly or through NEFs (201). The GMLC (209) may request routing information and / or privacy information of the target UE (212) from the UDM (203). After performing authentication of the external LCS client (211) or AF (204) and privacy verification of the target UE (212), the GMLC (209) may forward the location request to a serving AMF (206).

[0069] The LRF (location retrieval function, 210) can be deployed (collocated) at the same location as the GMLC (209) or operated separately, and can receive and verify location information and provide routing and correlation information for the UE (212) that performed the IMS emergency session.

[0070] The LCS client (location service client, 211) can access the LCS service through the GMLC (209) and can communicate with the GMLC (209) using the Le reference point.

[0071] The UE (user equipment, 212) can support four modes: UE assisted mode (performing location measurement and transmitting the measurement result to another entity (e.g., LMF (208)) to calculate the location), UE based mode (performing location measurement and calculating the location using assistance data received from the serving PLMN), standalone mode (performing location measurement and calculating the location without assistance data received from the serving PLMN), and network based mode (the serving PLMN measures the signal transmitted by the UE (212) and calculates the location).

[0072] The RAN (radio access network, 213) can be used for various procedures to determine the location of the target UE (212) and can transmit positioning messages between the target UE (212) and the AMF (206) or LMF (208).

[0073] UPF (user plane function, 214) may include functions such as routing and forwarding user data according to configured rules, supporting terminal mobility, and reporting traffic usage.

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

[0075] Referring to FIG. 3, the base station may include a transceiver (305), a control unit (310), and a storage unit (315). Depending on the communication method of the base station, the transceiver (305), the control unit (310), and the storage unit (315) may operate. A network device may also 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 components or fewer components than the components described above. For example, the base station may include a transceiver (305) and a control unit (310). In addition, the transceiver (305), the control unit (310), and the storage unit (315) may be implemented in the form of a single chip.

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

[0077] The storage unit (315) can store programs and data necessary for the operation of the base station. Additionally, the storage unit (315) can store control information or data included in signals obtained from the base station. The storage unit (315) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the storage unit (315) can store at least one of information transmitted and received through the transmission and reception unit (305) and information generated through the control unit (310).

[0078] In the present disclosure, the control unit (310) may be defined as a circuit or an 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 applications. The control unit (310) may control the overall operation of a base station according to an 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.

[0079] FIG. 4 is a drawing illustrating the structure of a terminal according to an embodiment of the present disclosure.

[0080] Referring to FIG. 4, the terminal may include a transceiver (410), a control unit (420), and a storage unit (430). The transceiver (410), the control unit (420), and the storage unit (430) 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 components or fewer components than the components described above. In addition, the transceiver (410), the control unit (420), and the storage unit (430) may be implemented in the form of a single chip.

[0081] The transceiver (410) is a collective term for the receiving unit and the transmitting unit 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. For example, the transceiver (410) can receive system information from the base station and can receive a synchronization signal or a reference signal. To this end, the transceiver (410) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (410), and the components of the transceiver (410) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (410) may include a wired / wireless transceiver and may include various configurations for transmitting and receiving signals. Additionally, the transceiver (410) can receive a signal through a wireless channel and output it to the control unit (420), and transmit the signal output from the control unit (420) through the wireless channel. Additionally, the transceiver (410) can receive a communication signal and output it to a processor, and transmit the signal output from the processor to a network entity through a wired or wireless network.

[0082] The storage unit (430) can store programs and data necessary for the operation of the terminal. Additionally, the memory (430) can store control information or data included in signals obtained from the terminal. The storage unit (430) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD.

[0083] In the present disclosure, the control unit (420) may be defined as a circuit or an 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 applications. The control unit (420) may control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the control unit (420) may control the signal flow between each block to perform operations according to the flowchart described in the present disclosure.

[0084] FIG. 5 is a diagram illustrating the structure of an SF in a wireless communication system according to various embodiments of the present disclosure.

[0085] Referring to FIG. 5, the sensing function (SF) may include a transmitting / receiving unit (505), a control unit (510), a storage unit (515), and a calculation unit (520). However, the components of the SF are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. For example, the SF may include a transmitting / receiving unit (505) and a control unit (510). In addition, the transmitting / receiving unit (505), the control unit (510), the storage unit (515), and the calculation unit (520) may be implemented in the form of a single chip.

[0086] The transceiver (505) collectively refers to the receiver and the transmitter of the SF and can transmit and receive signals with 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 (505) can transmit and receive control information or sensing results related to a sensing function with the base station. The transceiver (505) may include a wired / wireless transceiver and may include various configurations for transmitting and receiving signals. Additionally, the transceiver (505) can receive a signal through a wired / wireless channel and output it to the control unit (510), and transmit the signal output from the control unit (510) through a wired / wireless channel. Additionally, the transceiver (505) can receive a communication signal and output it to a processor, and transmit the signal output from the processor to a network entity through a wired / wireless network.

[0087] The storage unit (515) can store programs and data necessary for the operation of the SF. Additionally, the storage unit (515) can store control information or data included in wired or wireless signals acquired by the SF. The storage unit (515) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD.

[0088] The calculation unit (520) may perform calculations by the instruction of the control unit (510) to transform information output from the control unit (510) (e.g., information of a signal measured by an ISAC operation, or information processed from a signal measured by an ISAC operation) into another form that can be understood by a person or another application. The calculation result output from the calculation unit (520) may be output to the storage unit (515) for storage or output to the control unit (510).

[0089] In the present disclosure, the control unit (510) may be defined as a circuit or an 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 applications. The control unit (510) can control the overall operation of the SF according to the embodiment proposed in the present disclosure. For example, the control unit (510) can control the signal flow between each block to perform operations according to the flowchart.

[0090] FIG. 6 is a diagram illustrating examples in which a terminal senses a signal transmitted by a base station in a wireless communication system according to various embodiments of the present disclosure and provides an ISAC service.

[0091] Referring to FIG. 6, a base station (610) can transmit a reference signal (611, 613, 615), and a terminal (620) can receive a signal in which the reference signal (611, 613, 615) is modified by reflection, scattering, or diffraction, etc., on a target object (e.g., 630) or an environment object (e.g., 640, 650), and such a signal may be a sensing signal (612, 614, 616). The reference signal (611, 613, 615) may be transmitted at once, or it may be transmitted for each direction of the changed beam while changing the direction of the beam transmitted by the base station (610).

[0092] The base station (610) can use the reference signals (611, 613, 615) for sensing purposes as well as for communication purposes, and the reference signals (611, 613, 615) may be signals that a terminal (620) receiving these reference signals (611, 613, 615) can use for channel estimation, time synchronization, data transmission and reception, position estimation, etc. (e.g., primary / secondary synchronization signal, synchronization signal / PBCH block, positioning reference signal, cell-specific reference signal, tracking reference signal, demodulation reference signal).

[0093] The target object (e.g., 630) may be an object to be sensed via the ISAC service, and the environment object (e.g., 640, 650) may be an object other than the target object (e.g., 630). The characteristics of each object (630, 640, 650) may be distinguished by radar cross-section (RCS) or micro-Doppler difference, etc. For example, the size, shape, material, etc. of an object may be distinguished through the sensing signal (612, 614, 616) and the reference signal (611, 613, 615).

[0094] When a base station (610) transmits reference signals (611, 613, 615) at regular intervals or for a continuous period of time, and a terminal (620) receives sensing signals (612, 614, 616) at regular intervals or for a continuous period of time, the terminal (620) can measure the velocity and direction of a target object (e.g., 630) or an environment object (e.g., 640, 650).

[0095] Depending on the bandwidth and frequency pattern of the frequency transmitting the reference signals (611, 613, 615), the resolution and range for sensing the target object (e.g., 630) or environment object (e.g., 640, 650) may vary.

[0096] A base station (610) transmits reference signals (611, 613, 615), and a terminal (620) receives sensing signals (612, 614, 616) in which the reference signals (611, 613, 615) interact with an object. Through this operation, the characteristics of an object that may not have the ability to connect to a wireless mobile communication network are identified and mapped, and the ability to detect or sense what kind of object it is can be called an ISAC (integrated sensing and communication). A wireless communication system can provide various services through ISAC without additional equipment such as sensors. For example, ISAC (integrated sensing and communication) can be used for intruder detection on private property, railways, etc., drone location tracking, flood or precipitation detection, gesture detection, driver assistance systems, etc.

[0097] FIG. 7 is a diagram illustrating examples in which a base station senses a signal transmitted by a terminal in a wireless communication system according to various embodiments of the present disclosure and provides an ISAC service.

[0098] Referring to FIG. 7, a terminal (710) can transmit a reference signal (711, 713, 715), and a base station (720) can receive a signal in which the reference signal (711, 713, 715) is modified by reflection, scattering, or diffraction, etc., on a target object (e.g., 730) or an environment object (e.g., 740, 750), and such a signal may be a sensing signal (712, 714, 716). The reference signal (711, 713, 715) may be transmitted at once, or it may be transmitted for each direction of the changed beam while changing the direction of the beam transmitted by the terminal (710).

[0099] The terminal (710) can use the reference signals (711, 713, 715) for sensing purposes as well as for communication purposes, and the reference signals (711, 713, 715) may be signals (e.g., sounding reference signal, positioning sounding reference signal, demodulation reference signal) that a base station (720) receiving these reference signals (711, 713, 715) can use for channel estimation, time synchronization, data transmission and reception, position estimation, etc.

[0100] The target object (e.g., 730) may be an object to be sensed via the ISAC service, and the environment object (e.g., 740, 750) may be an object other than the target object (e.g., 730). The characteristics of each object (730, 740, 750) may be distinguished by radar cross section (RCS) or micro-Doppler difference, etc. For example, the size, shape, material, etc. of an object may be distinguished through the sensing signal (712, 714, 716) and reference signal (711, 713, 715).

[0101] When a terminal (710) transmits reference signals (711, 713, 715) at regular intervals or for a continuous period of time, and a base station (720) receives sensing signals (712, 714, 716) at regular intervals or for a continuous period of time, the base station (720) can measure the velocity and direction of a target object (e.g., 730) or an environment object (e.g., 740, 750).

[0102] Depending on the bandwidth and frequency pattern of the frequency transmitting the reference signals (711, 713, 715), the resolution and range for sensing the target object (e.g., 730) or environment object (e.g., 740, 750) may vary.

[0103] A function that can detect or sense what kind of object it is by identifying and mapping the characteristics of an object that may not have the ability to connect to a wireless mobile communication network through the operation in which a terminal (710) transmits reference signals (711, 713, 715) and a base station (720) receives sensing signals (712, 714, 716) in which the reference signals (711, 713, 715) interact with an object can be called an ISAC. A wireless communication system can provide various services through the ISAC without additional equipment such as sensors. For example, the ISAC can be used for intruder detection on private property, railways, etc., drone location tracking, flood or precipitation detection, gesture detection, driver assistance systems, etc.

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

[0105] 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 of FIG. 2. Additionally, the SF (820) may be integrated as part of the LMF (815) function, and the LMF (815) and the SF (820) may also communicate by other methods not described in this disclosure (e.g., internal interfaces).

[0106] The base station (805) may use NRPPa (NR positioning protocol A), which is a protocol for transmitting data between the base station (805) and the LMF (815), as a method to transmit control information, signal information, or measurement information related to ISAC to the SF (820). That is, the information that the base station (805) intends to transmit to the SF (820) may be included in the form of an information element (IE) in an NRPPa PDU (protocol data unit) (832).

[0107] The NRPPa PDU (832) transmitted by the base station (805) to the LMF (815) may be included in an NGAP (NG application protocol) message (831) that transmits data between the base station (805) and the AMF (810). The NGAP message (831) may include an identifier (e.g., routing ID) of the LMF (815) to which the base station (805) transmits (or intends to transmit) the NRPPa PDU (832).

[0108] The AMF (810) can transmit an NRPPa PDU (834) to an LMF (815) corresponding to an LMF identifier included in an NGAP message (831) transmitted by a base station (805). The NRPPa PDU (834) can be transmitted via a message (833) of an interface (e.g., Nlmf) transmitting data from the AMF (810) to the LMF (815). The message (833) of the interface (e.g., Nlmf) transmitting data from the AMF (810) to the LMF (815) can include a base station (805) identifier (e.g., correlation ID) to inform the LMF (815) of the base station (805) transmitting the NRPPa PDU (834).

[0109] LMF (815) can transmit ISAC information (835) contained in the received NRPPa PDU (834) to SF (820). SF (820) can perform operations for ISAC services.

[0110] SF (820) may use NRPPa, a protocol for transmitting data between LMF (815) 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, SF (820) transmits ISAC information (836) to LMF (815) to be transmitted to base station (805), and LMF (815) may include it in the form of IE in the NRPPa PDU (838) transmitted to base station (805). The NRPPa PDU (838) transmitted by LMF (815) to base station (805) may be transmitted through a message (837) of an interface (e.g., Namf) that transmits data from LMF (815) to AMF (810). A message (837) of an interface (e.g., Namf) transmitting data from LMF (815) to AMF (810) may include an identifier (e.g., correlation ID) of the base station (805) to inform the base station (805) of the NRPPa PDU (838) to be transmitted to the AMF (810).

[0111] The AMF (810) can transmit an NRPPa PDU (840) to a base station (805) corresponding to a base station identifier (e.g., correlation ID) included in a message (837) transmitted by the LMF (815). The NRPPa PDU (840) transmitted by the AMF (810) to the base station (805) can be included in an NGAP message (839) that transmits data between the AMF (810) and the base station (805). The NGAP message (839) can include the identifier of the LMF (815) (e.g., routing ID) to inform the base station (805) of the LMF (815) that it is transmitting the NRPPa PDU (840).

[0112] The base station (805) can perform an operation for an ISAC service using the ISAC information included in the received NRPPa PDU (840).

[0113] According to various embodiments of the present disclosure, multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously on a single peer (e.g., a base station (805) and a single LMF (815)). The base station (805) and the LMF (815) may include a processing identifier (e.g., transaction ID) in the NRPPa PDUs (832, 834, 838, 840) to identify which ISAC operation each different NRPPa PDU corresponds to.

[0114] The NRPPa PDU (832) transmitted by the base station (805) to the AMF (810) and the NRPPa PDU (834) transmitted by the AMF (810) to the LMF (815) may contain equivalent information or may be the same message. The NRPPa PDU (838) transmitted by the LMF (815) to the AMF (810) and the NRPPa PDU (840) transmitted by the AMF (810) to the base station (805) may contain equivalent information or may be the same message.

[0115] The LMF (815) identifier (e.g., routing ID) and the base station (805) identifier (e.g., correlation ID) may be different values ​​or the same value that the AMF (810) can map.

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

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

[0118] The base station (905) may use a new protocol (gNB-SF protocol) PDU for transmitting data between the base station (905) and the SF (920) as a method for transmitting control information, signal information, or measurement information related to ISAC to the SF (920). That is, the information that the base station (905) intends to transmit to the SF (920) may be included in the gNB-SF PDU in the form of an IE.

[0119] The gNB-SF PDU (933) that the base station (905) transmits (or intends to transmit) to the SF (920) may be included in an NRPPa message (932) that transmits data between the base station (905) and the LMF (915). The NRPPa message (932) may include an identifier (e.g., SF routing ID) of the SF (920) to which the base station (905) transmits (or intends to transmit) the gNB-SF PDU (933).

[0120] The NRPPa PDU may be included in an NGAP message (931) that transmits data between a base station (905) and an AMF (910). The NGAP message (931) may include an identifier (e.g., routing ID) of an LMF (915) to which the base station (905) transmits (or intends to transmit) the NRPPa PDU (932). The AMF (910) may transmit the NRPPa PDU (932) to an LMF (915) corresponding to the LMF (915) identifier included in the NGAP message (931) transmitted by the base station (905).

[0121] An NRPPa PDU (935) containing a gNB-SF PDU (936) can be transmitted via a message (934) of an interface (e.g., Nlmf) transmitting data from an AMF (910) to an LMF (915). The message (934) of the interface (e.g., Nlmf) transmitting data from an AMF (910) to an LMF (915) may include an identifier (e.g., correlation ID) of the base station (905) so that the LMF (915) can identify the base station (905) transmitting the NRPPa PDU (935).

[0122] LMF (915) can transmit the gNB-SF PDU (938) to the SF (920) corresponding to the SF (920) identifier (e.g., SF routing ID) included in the NRPPa PDU (935) as a message (937) of an interface (e.g., Nsf) that transmits data from LMF (915) to SF (920).

[0123] A message (937) of an interface (e.g., Nsf) transmitting data from LMF (915) to SF (920) can inform the base station (905) that transmits the gNB-SF PDU (938) to SF (920) by including the identifier of the base station (905) (e.g., SF correlation ID).

[0124] SF (920) can receive the gNB-SF PDU (938) and perform operations for ISAC services.

[0125] SF (920) may use a gNB-SF PDU to transmit data between SF (920) and base station (905) as a method to transmit control information, signal information, or measurement information related to ISAC to base station (905). That is, the ISAC-related information that SF (920) intends to transmit to base station (905) may be included in the gNB-SF PDU in the form of IE.

[0126] The gNB-SF PDU (940) transmitted by the SF (920) to the LMF (915) can be transmitted via a message (939) of an interface (e.g., Nlmf) that transmits data between the SF (920) and the LMF (915). The message (939) of the interface (e.g., Nlmf) that transmits data from the SF (920) to the LMF (915) can identify the base station (905) to which the LMF (915) transmits the gNB-SF PDU (940) by including an identifier of the base station (905) (e.g., SF correlation ID).

[0127] The gNB-SF PDU (943) that the LMF (915) transmits to the base station (905) may be included in an NRPPa message (942) that transmits data between the LMF (915) and the base station (905). The NRPPa message (942) may include an identifier (e.g., SF correlation ID) of the base station (905) that transmits the gNB-SF PDU (943) transmitted by the LMF (915). The NRPPa message (942) may be transmitted as a message (941) of an interface (e.g., Namf) that transmits data from the LMF (915) to the AMF (910).

[0128] A message (941) of an interface (e.g., Namf) transmitting data from LMF (915) to AMF (910) includes an identifier (e.g., correlation ID) of the base station (905) so that AMF (910) can identify the base station (905) to which the NRPPa PDU (942) is being transmitted.

[0129] The NRPPa PDU (945) containing the gNB-SF PDU (946) that the AMF (910) transmits to the base station (905) may be included in an NGAP message (944) that transmits data between the AMF (910) and the base station (905). The NGAP message (944) may include an identifier (e.g., routing ID) of the LMF (915) transmitting the NRPPa PDU (945) to inform the base station (905) of the LMF (915) transmitting the NRPPa PDU (945).

[0130] The base station (905) can identify the SF (920) transmitting the gNB-SF PDU (946) through the SF (920) identifier (e.g., SF routing ID) included in the NRPPa PDU (945).

[0131] The base station (905) can receive the gNB-SF PDU (946) and perform an operation for the ISAC service.

[0132] Multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously on a single peer (e.g., a base station (905) and a LMF (915)). The base station (905) and the LMF (915) may include a processing identifier (e.g., transaction ID) in the NRPPa PDUs (932, 935, 942, 945) to identify which ISAC operation a different NRPPa PDU corresponds to.

[0133] Multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously on a single peer (e.g., a single base station (905) and a single SF (920)). The base station (905) and the SF (920) may include an SF (920) processing identifier (e.g., SF transaction ID) in the gNB-SF PDU (933, 936, 943, 946) to identify which ISAC operation each different gNB-SF PDU corresponds to.

[0134] The NRPPa PDU (932) transmitted by the base station (905) to the AMF (910) and the NRPPa PDU (935) transmitted by the AMF (910) to the LMF (915) may contain equivalent information or be the same message. The NRPPa PDU (942) transmitted by the LMF (915) to the AMF (910) and the NRPPa PDU (945) transmitted by the AMF (910) to the base station (905) may contain equivalent information or be the same message. The gNB-SF PDU (933) transmitted by the base station (905) to the AMF (910), the gNB-SF PDU (936) transmitted by the AMF (910) to the LMF (915), and the gNB-SF PDU (938) transmitted by the LMF (915) to the SF (920) may contain equivalent information or be the same message. The gNB-SF PDU (940) transmitted by SF (920) to the base station (905), the gNB-SF PDU (943) transmitted by LMF (915) to AMF (910), and the gNB-SF PDU (946) transmitted by AMF (910) to the base station (905) may contain equivalent information or may be the same message.

[0135] The LMF (915) identifier (e.g., routing ID) and the base station (905) identifier (e.g., correlation ID) may be different values ​​or the same value that the AMF (910) can map. The SF (920) identifier (e.g., SF (920) routing ID) and the base station (905) identifier (e.g., SF (920) correlation ID) may be different values ​​or the same value that the LMF (915) can map. Additionally, the LMF (915) identifier and the SF (920) identifier may be the same value.

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

[0137] Referring to FIG. 10, the base station (1005) can transmit and receive data with the AMF (1010), and the AMF (1010) can transmit and receive data with the SF (1015). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example of FIG. 2. If the base station (1005) cannot directly exchange messages with the SF (1015), message transmission through the AMF (1010) may be required.

[0138] The base station (1005) may use a new protocol (gNB-SF protocol) PDU for transmitting data between the base station (1005) and the SF (1015) as a method to transmit control information, signal information, or measurement information related to ISAC to the SF (1015). That is, the information that the base station (1005) intends to transmit to the SF (1015) may be included in the gNB-SF PDU in the form of an IE.

[0139] The gNB-SF PDU (1022) that the base station (1005) transmits (or intends to transmit) to the SF (1015) may be included in an NGAP message (1021) that transmits data between the base station (1005) and the AMF (1010). The NGAP message (1021) may include an identifier (e.g., SF routing ID) of the SF (1015) to which the base station (1005) transmits (or intends to transmit) the gNB-SF PDU (1022).

[0140] The AMF (1010) can transmit a gNB-SF PDU (1024) to an SF (1015) corresponding to an SF (1015) identifier included in an NGAP message (1021) transmitted by the base station (1005). The gNB-SF PDU (1024) can be transmitted via a message (1023) of an interface (e.g., Nsf) that transmits data from the AMF (1010) to the SF (1015). The message (1023) of the interface (e.g., Nsf) that transmits data from the AMF (1010) to the SF (1015) can include a base station (1005) identifier (e.g., SF correlation ID) to inform the base station (1005) that transmits the gNB-SF PDU (1024) to the SF (1015).

[0141] SF (1015) can perform operations for ISAC services using the ISAC information included in the received gNB-SF PDU (1024).

[0142] SF (1015) may use a gNB-SF PDU to transmit data between SF (1015) and base station (1005) as a method for transmitting control information, signal information, or measurement information related to ISAC to base station (1005). That is, the information that SF (1015) intends to transmit to base station (1005) may be included in the gNB-SF PDU in the form of IE.

[0143] The gNB-SF PDU (1026) can be transmitted via a message (1025) of an interface (e.g., Namf) transmitting data from the SF (1015) to the AMF (1010). The message (1025) of the interface (e.g., Namf) transmitting data from the SF (1015) to the AMF (1010) can include a base station (1005) identifier (e.g., SF correlation ID) to inform the base station (1005) of the SF (1015) transmitting the gNB-SF PDU (1026).

[0144] AMF (1010) can transmit a gNB-SF PDU (1028) to a base station (1005) corresponding to a base station (1005) identifier included in a message (1025) of an interface (e.g., Namf) that transmits data from SF (1015) to AMF (1010).

[0145] The gNB-SF PDU (1028) transmitted by the AMF (1010) to the base station (1005) may be included in an NGAP message (1027) that transmits data between the AMF (1010) and the base station (1005). The NGAP message (1027) may include an identifier (e.g., SF routing ID) of the SF (1015) that transmits the gNB-SF PDU (1027).

[0146] The base station (1005) can perform an operation for an ISAC service using the ISAC information included in the received gNB-SF PDU (1027).

[0147] Multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously on a single peer (e.g., a base station (1005) and a SF (1015)). The base station (1005) and the SF (1015) may include a processing identifier (e.g., SF transaction ID) in the gNB-SF PDU (1022, 1024, 1026, 1028) to identify which ISAC operation each different gNB-SF PDU corresponds to.

[0148] The gNB-SF PDU (1022) transmitted by the base station (1005) to the AMF (1010) and the gNB-SF PDU (1024) transmitted by the AMF (1010) to the SF (1015) may contain equivalent information or may be the same message. The gNB-SF PDU (1026) transmitted by the SF (1015) to the AMF (1010) and the gNB-SF PDU (1028) transmitted by the AMF (1010) to the base station (1005) may contain equivalent information or may be the same message.

[0149] The SF (1015) identifier (e.g., SF routing ID) and the base station (1005) identifier (e.g., SF correlation ID) may be different values ​​or the same value that the AMF (1010) can map.

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

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

[0152] The base station (1105) may use a new protocol (gNB-SF protocol) PDU for transmitting data between the base station (1105) and the SF (1110) as a method to transmit control information, signal information, or measurement information related to ISAC to the SF (1110). That is, the information that the base station (1105) intends to transmit to the SF (1110) may be included in the gNB-SF PDU in the form of an IE.

[0153] The gNB-SF PDU (1122) transmitted by the base station (1105) to the SF (1110) may be included in the message (1121) of the interface (e.g., Nsf) that transmits data between the base station (1105) and the SF (1110).

[0154] A message (1121) of an interface (e.g., Nsf) that transmits data between a base station (1105) and an SF (1110) can inform the base station (1105) that transmits a gNB-SF PDU (1122) to the SF (1110), including an identifier (e.g., gNB ID) of the base station (1105).

[0155] SF (1110) can perform operations for ISAC services using the ISAC information included in the received gNB-SF PDU (1122).

[0156] The gNB-SF PDU (1124) that SF (1110) transmits to the base station (1105) may be included in the message (1123) of the interface (e.g., NgNB) that transmits data between SF (1110) and the base station (1105).

[0157] A message (1123) of an interface (e.g., Ngnb) that transmits data between SF (1110) and base station (1105) can inform SF (1110) that transmits a gNB-SF PDU (1124) to base station (1105), including an identifier (e.g., SF ID) of SF (1110).

[0158] The base station (1105) can perform an operation for an ISAC service using the ISAC information included in the received gNB-SF PDU (1124).

[0159] The SF (1110) identifier (e.g., SF ID) and the base station (1105) identifier (e.g., gNB ID) may be different values ​​that the base station (1105) and SF (1110) can map to, or the same value.

[0160] FIG. 12 is a diagram illustrating the structure of a communication protocol between a terminal and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0161] Referring to FIG. 12, a terminal (1205) can be connected to a base station (1210) to transmit and receive data, the base station (1210) can transmit and receive data with an AMF (1215), the AMF (1215) can transmit and receive data with an LMF (815), and the LMF (1220) can transmit and receive data with an SF (1225). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example of FIG. 2. Additionally, the SF (1225) may be integrated as part of the LMF (1220) function, and the LMF (1220) and the SF (1225) may also communicate by other methods not described in this disclosure (e.g., internal interfaces).

[0162] The terminal (1205) may use an LTE positioning protocol (LPP), which is a protocol for transmitting data between the terminal (1205) and the LMF (1220), as a method to transmit control information, signal information, or measurement information related to the ISAC to the SF (1225). That is, the information that the terminal (1205) intends to transmit to the SF (1225) may be included in the form of an information element (IE) in an LPP protocol data unit (PDU) (1233).

[0163] The LPP PDU (1233) transmitted by the terminal (1205) to the LMF (1220) may be included in a NAS (non-access stratum) message (1232) that transmits data between the terminal (1205) and the AMF (1215). The NAS message (1232) may include information (routing ID) of the LMF (1220) to which the LPP PDU (1233) is to be transmitted. To transmit the NAS message (1232) to the AMF (1215), the terminal (1205) may use an RRC message (1231) transmitted by the terminal (1205) to the base station (1210).

[0164] The base station (1210) receives an RRC message (1231) transmitted by the terminal (1205) and can transmit the NAS message (1232) included in the RRC message (1231) to the AMF (1215) using an NGAP message (1234). At this time, the NAS message (1235) and LPP PDU (1236) included in the NGAP message (1234) may be the same message as the NAS message (1232) and LPP PDU (1233) included in the RRC message (1231) transmitted by the terminal (1205) to the base station (1210), or may be a message containing information equivalent to the NAS message (1232) and LPP PDU (1233).

[0165] The AMF (1215) can transmit an LPP PDU (1236) to an LMF (1220) corresponding to the routing ID included in the NAS message (1235), and the AMF (1215) can use a message (1237) of the Nlmf interface. At this time, the LPP PDU (1238) included in the message (1237) of the Nlmf interface may be the same message as the LPP PDU (1236) included in the NGAP message (1234) transmitted by the base station (1210) to the AMF (1215), or may be a message containing information equivalent to that of the LPP PDU (1236). The Nlmf message (1237) may include information (UE correlation ID) of the terminal (1205) that transmits (intends to transmit) the LPP PDU (1238) to the LMF (1220). The UE correlation ID can be used to identify the terminal (1205) by the LMF (1220), or to identify the terminal (1205) receiving the message transmitted by the LMF (1220) in the AMF (1215).

[0166] LMF (1220) can transmit ISAC information contained in the received LPP PDU (1238) to SF (1239). SF (1225) can perform operations for ISAC services.

[0167] SF (1225) may use LPP, a protocol for transmitting data between LMF (1220) and terminal (1205), as a method for transmitting control information, signal information, or measurement information related to ISAC to terminal (1205). That is, SF (1225) transmits ISAC information (1240) to be transmitted to terminal (1205) to LMF (1220), and LMF (1220) may include the ISAC information (1240) in the form of ISAC IE in the LPP PDU (1242) transmitted to terminal (1205). The LPP PDU (1242) transmitted by LMF (1220) to terminal (1205) may be transmitted through a message (1241) of an interface (e.g., Namf) that transmits data from LMF (1220) to AMF (1215). A message (1241) of an interface (e.g., Namf) transmitting data from LMF (1220) to AMF (1215) includes an identifier (e.g., UE correlation ID) of the terminal (1205) so that AMF (1215) can identify the terminal (1205) to which the LPP PDU (1242) is to be transmitted.

[0168] The AMF (1215) can transmit a NAS message (1244) containing an LPP PDU (1245) to a terminal (1205) identified by a terminal identifier (e.g., UE correlation ID) included in a message (1241) transmitted by the LMF (1220). To transmit the NAS message (1244) to the terminal (1205), the AMF (1215) can transmit the NAS message (1244) to the base station (1210) by including the NAS message (1244) in an NGAP message (1243). At this time, the LPP PDU (1245) that the AMF (1215) transmits to the base station (1210) by including it in the NAS message (1244) may be the same message as the LPP PDU (1242) transmitted by the LMF (1220) to the AMF (1215), or may be a message containing information equivalent to that of the LPP PDU (1242). The NAS message (1244) that the AMF (1215) sends to the UE (1205) includes an identifier (e.g., routing ID) of the LMF sending the LPP PDU (1245), through which the terminal (1205) can identify the LMF (1220) sending the LPP PDU (1245).

[0169] The base station (1210) can transmit the NAS message (1244) included in the NGAP message (1243) transmitted by the AMF (1215) to the terminal (1205). The base station (1210) may include the NAS message (1247) in the RRC message (1246) transmitted to the terminal (1205). At this time, the NAS message (1247) and LPP PDU (1248) that the base station (1210) includes in the RRC message (1246) and transmits to the terminal (1205) may be the same message as the NAS message (1244) and LPP PDU (1246) transmitted by the AMF (1215) to the base station (1210), or may be a message containing information equivalent to the NAS message (1244) and LPP PDU (1246).

[0170] The terminal (1206) can perform an operation for an ISAC service using the ISAC information included in the received LPP PDU (1248).

[0171] Multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously on a single peer (e.g., a single terminal (1205) and a single LMF (1220)). The terminal (1205) and the LMF (1220) may include a processing identifier (e.g., transaction ID) in the LPP PDUs (1233, 1236, 1238, 1242, 1245, 1248) to identify which ISAC operation each different LPP PDU corresponds to.

[0172] FIG. 13 is a diagram illustrating the structure of a communication protocol between a terminal and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0173] Referring to FIG. 13, a terminal (1305) can be connected to a base station (1310) to transmit and receive data, the base station (1310) can transmit and receive data with an AMF (1315), the AMF (1315) can transmit and receive data with an LMF (815), and the LMF (1320) can transmit and receive data with an SF (1325). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example of FIG. 2. If the AMF (1315) cannot directly transmit and receive messages with the SF (1325), message delivery through the LMF (1320) may be required.

[0174] The terminal (1305) may use a new protocol (UE-SF protocol) PDU for transmitting data between the terminal (1305) and the SF (1325) as a method for transmitting control information, signal information, or measurement information related to the ISAC to the SF (1325). That is, the information that the terminal (1305) intends to transmit to the SF (1325) may be included in the UE-SF PDU (protocol data unit) (1334) in the form of an information element (IE).

[0175] The UE-SF PDU (1334) that the terminal (1305) transmits (or intends to transmit) to the SF (1325) may be included in the LPP PDU (1333) that transmits data between the terminal (1305) and the LMF (1320). The LPP PDU (1333) may include information (SF routing ID) of the SF (1325) to which the UE-SF PDU (1334) is to be transmitted.

[0176] The LPP PDU (1333) that the terminal (1305) transmits (or intends to transmit) to the LMF (1320) may be included in a NAS (non-access stratum) message (1332) that transmits data between the terminal (1305) and the AMF (1315). The NAS message (1332) may include information (routing ID) of the LMF (1320) to which the LPP PDU (1333) is to be transmitted. To transmit the NAS message (1332) to the AMF (1315), the terminal (1305) may use an RRC message (1331) that the terminal (1305) transmits to the base station (1310).

[0177] The base station (1310) receives an RRC message (1331) transmitted by the terminal (1305) and can transmit the NAS message (1332) included in the RRC message (1331) to the AMF (1315) using an NGAP message (1335). At this time, the NAS message (1336), LPP PDU (1337), and UE-SF PDU (1338) included in the NGAP message (1335) may be the same message as the NAS message (1332), LPP PDU (1333), and UE-SF PDU (1334) included in the RRC message (1331) transmitted by the terminal (1305) to the base station (1310), or may be a message containing information equivalent to the NAS message (1332), LPP PDU (1333), and UE-SF PDU (1334).

[0178] The AMF (1315) can transmit an LPP PDU (1340) containing a UE-SF PDU (1341) to an LMF (1320) corresponding to the routing ID included in the NAS message (1336), and can use the message (1339) of the Nlmf interface. At this time, the LPP PDU (1340) and UE-SF PDU (1341) included in the message (1339) of the Nlmf interface may be the same message as the LPP PDU (1337) and UE-SF PDU (1338) included in the NGAP message (1335) transmitted by the base station (1310) to the AMF (1315), or may be a message containing information equivalent to the LPP PDU (1337) and UE-SF PDU (1338). The Nlmf message (1339) may include information (UE correlation ID) of the terminal (1305) that transmits the LPP PDU (1340) to the LMF (1320). The UE correlation ID may be used by the LMF (1320) to identify the terminal (1305), or may be used by the AMF (1315) to identify the terminal (1305) that receives the message transmitted by the LMF (1320).

[0179] The LMF (1320) can transmit the UE-SF PDU (1343) to the SF (1325) corresponding to the SF routing ID included in the LPP PDU (1340), and the LMF (1320) can use the message (1342) of the Nsf interface. The UE-SF PDU (1343) included in the message (1342) of the Nsf interface may be the same message as the UE-SF PDU (1341) included in the LPP PDU (1340) transmitted by the AMF (1315) to the LMF (1320), or may be a message containing information equivalent to the UE-SF PDU (1341). The Nsf message (1342) may include information (UE correlation ID) of the terminal (1305) transmitting the UE-SF PDU (1343) to the SF (1325). The UE correlation ID can be used by the SF (1325) to identify the terminal (1305), or by the LMF (1320) to identify the terminal (1305) that receives the message transmitted by the SF (1325). The UE correlation ID used by the LMF (1320) to identify the terminal (1305) and the UE correlation ID used by the SF (1325) to identify the terminal (1305) may be the same value or different values, and the LMF (1320) may support mapping of different UE correlation IDs.

[0180] SF (1325) can perform operations for ISAC services using information from the UE-SF PDU (1343) received from the UE (1305).

[0181] SF (1325) may use a new protocol (UE-SF protocol) PDU for transmitting data between the terminal (1305) and LMF (1320) as a method for transmitting control information, signal information, or measurement information related to ISAC to the terminal (1305). That is, the information that SF (1325) intends to transmit to the terminal (1305) may be included in the UE-SF PDU (1345) in the form of an information element (IE). SF (1325) may transmit the UE-SF PDU (1345) to the LMF (1320) as a message (1344) of the Nlmf interface in order to transmit the UE-SF PDU (1345) to the terminal (1305). A message (1344) of an interface (e.g., Nlmf) transmitting data from SF (1325) to LMF (1320) includes an identifier (e.g., UE correlation ID) of the terminal (1305) so that LMF (1320) can identify the terminal (1305) to which the LPP PDU (1347) is to be transmitted.

[0182] LMF (1320) may use LPP, a protocol for transmitting data between LMF (1320) and terminal (1305), to transmit a UE-SF PDU to terminal (1305). That is, SF (1325) transmits the UE-SF PDU (1345) to be transmitted to terminal (1305) to LMF (1320) as a message (1344) of the Nlmf interface, and LMF (1320) may include the UE-SF PDU (1348) in the LPP PDU (1347) transmitted to terminal (1305). The LPP PDU (1347) transmitted by LMF (1320) to terminal (1305) may be transmitted as a message (1346) of an interface (e.g., Namf) that transmits data from LMF (1320) to AMF (1315). A message (1346) of an interface (e.g., Namf) transmitting data from LMF (1320) to AMF (1315) may include an identifier of the terminal (1305) (e.g., UE correlation ID) so that AMF (1315) can identify the terminal (1305) to which it will transmit the LPP PDU (1342). At this time, the UE-SF PDU (1348) that LMF (1320) transmits to AMF (1315) by including it in the LPP PDU (1347) may be the same message as the UE-SF PDU (1345) that SF (1325) transmitted to LMF (1320), or may be a message containing information equivalent to that of the UE-SF PDU (1345). The LPP PDU (1347) that the LMF (1320) transmits to the UE (1305) includes an identifier (e.g., SF routing ID) of the SF (1325) that transmits the UE-SF PDU (1348), so that the terminal (1305) can identify the SF (1325) that transmits the LPP PDU (1351).

[0183] The AMF (1315) can transmit a NAS message (1350) containing an LPP PDU (1351) to a terminal (1305) identified by a terminal identifier (e.g., UE correlation ID) included in a message (1346) transmitted by the LMF (1320). The AMF (1315) can transmit the NAS message (1350) to the base station (1310) by including the NAS message (1350) in an NGAP message (1349) in order to transmit the NAS message (1350) to the terminal (1305). At this time, the LPP PDU (1351) and UE-SF PDU (1352) that the AMF (1315) includes in the NAS message (1350) and transmits to the base station (1310) may be the same message as the LPP PDU (1347) and UE-SF PDU (1348) that the LMF (1320) transmits to the AMF (1315), or may be messages containing equivalent information. The NAS message (1350) that the AMF (1315) transmits to the UE (1305) may include an identifier (e.g., routing ID) of the LMF (1320) transmitting the LPP PDU (1351), so that the terminal (1305) can identify the LMF (1320) transmitting the LPP PDU (1351).

[0184] The base station (1310) can deliver the NAS message (1350) included in the NGAP message (1349) transmitted by the AMF (1315) to the terminal (1305). The base station (1310) can include the NAS message (1354) in the RRC message (1353) transmitted to the terminal (1305). At this time, the NAS message (1354), LPP PDU (1355), and UE-SF PDU (1356) that the base station (1310) includes in the RRC message (1353) and transmits to the terminal (1305) may be the same message as the NAS message (1350), LPP PDU (1351), and UE-SF PDU (1352) transmitted by the AMF (1315) to the base station (1310), or may be a message containing information equivalent to the NAS message (1350), LPP PDU (1351), and UE-SF PDU (1352).

[0185] The terminal (1305) can perform an operation for an ISAC service using the ISAC information included in the received UE-SF PDU (1356).

[0186] Multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously on a single peer (e.g., one terminal (1305) and one LMF (1320), or one terminal (1305) and one SF (1325)). The terminal (1305) and the LMF (1320) may include a processing identifier (e.g., transaction ID) in the LPP PDU (1333, 1337, 1341, 1347, 1351, 1355) to identify which ISAC operation each different LPP PDU corresponds to. Additionally, the terminal (1305) and the SF (1325) may include an SF processing identifier (e.g., SF transaction ID) in the UE-SF PDU (1334, 1338, 1341, 1343, 1345, 1348, 1352, 1356) to identify which ISAC operation each different UE-SF PDU corresponds to.

[0187] FIG. 14 is a diagram illustrating the structure of a communication protocol between a terminal and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0188] Referring to FIG. 14, the terminal (1405) can be connected to the base station (1410) to transmit and receive data, the base station (1410) can transmit and receive data with the AMF (1415), and the AMF (1415) can transmit and receive data with the SF (1420). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example of FIG. 2.

[0189] The terminal (1405) may use a new protocol (UE-SF protocol) PDU for transmitting data between the terminal (1405) and the SF (1420) as a method for transmitting control information, signal information, or measurement information related to the ISAC to the SF (1420). That is, the information that the terminal (1405) intends to transmit to the SF (1420) may be included in the form of an information element (IE) in the UE-SF PDU (protocol data unit) (1433).

[0190] The UE-SF PDU (1433) that the terminal (1405) transmits (or intends to transmit) to the SF (1420) may be included in a NAS message (1432) that transmits data between the terminal (1405) and the AMF (1415). The NAS message (1432) may include information (SF routing ID) of the SF (1420) to which the UE-SF PDU (1433) is to be transmitted. To transmit the NAS message (1432) to the AMF (1415), the terminal (1405) may use an RRC message (1431) that the terminal (1405) transmits to the base station (1410).

[0191] The base station (1410) receives an RRC message (1431) transmitted by the terminal (1405) and can transmit the NAS message (1432) included in the RRC message (1431) to the AMF (1415) using an NGAP message (1434). At this time, the NAS message (1435) and UE-SF PDU (1436) included in the NGAP message (1434) may be the same message as the NAS message (1432) and UE-SF PDU (1433) included in the RRC message (1431) transmitted by the terminal (1405) to the base station (1410), or may be a message containing information equivalent to the NAS message (1432) and UE-SF PDU (1433).

[0192] The AMF (1415) can transmit the UE-SF PDU (1438) to the SF (1420) corresponding to the SF routing ID included in the NAS message (1435), and at this time, the AMF (1415) can use the message (1437) of the Nsf interface. At this time, the UE-SF PDU (1438) included in the message (1437) of the Nsf interface may be the same message as the UE-SF PDU (1436) included in the NGAP message (1434) transmitted by the base station (1410) to the AMF (1415), or may be a message containing information equivalent to the UE-SF PDU (1436). The Nsf message (1437) may include information (UE correlation ID) of the terminal (1405) transmitting the UE-SF PDU (1438) to the SF (1420). The UE correlation ID can be used to identify the terminal (1405) by the SF (1420), or to identify the terminal (1405) receiving the message transmitted by the SF (1420) in the AMF (1415).

[0193] SF (1420) can perform operations for ISAC services using information from the UE-SF PDU (1438) received from the UE (1405).

[0194] SF (1420) may use a new protocol (UE-SF protocol) PDU to transmit data between the terminal (1405) and SF (1420) as a method to transmit control information, signal information, or measurement information related to ISAC to the terminal (1405). That is, the information that SF (1420) intends to transmit to the terminal (1405) may be included in the UE-SF PDU (1440) in the form of an information element (IE). To transmit the UE-SF PDU (1440) to the terminal (1405), SF (1420) may transmit the UE-SF PDU (1440) to AMF (1415) by including it in a message (1439) of the Namf interface. A message (1439) of an interface (e.g., Namf) transmitting data from SF (1420) to AMF (1415) includes an identifier of the terminal (1405) (e.g., UE correlation ID) so that AMF (1415) can identify the terminal (1405) to which the UE-SF PDU (1440) is to be delivered.

[0195] AMF (1415) can transmit a NAS message (1442) containing a UE-SF PDU (1443) to a terminal (1405) identified by a terminal identifier (e.g., UE correlation ID) included in a message (1439) transmitted by SF (1420). AMF (1415) can transmit the NAS message (1442) to the base station (1410) by including the NAS message (1442) in an NGAP message (1441) to transmit the NAS message (1442) to the terminal (1405). At this time, the UE-SF PDU (1443) that AMF (1415) transmits to the base station (1410) by including it in the NAS message (1442) may be the same message as the UE-SF PDU (1440) transmitted by SF (1420) to AMF (1415), or may be a message containing information equivalent to that of the UE-SF PDU (1440). The NAS message (1442) that the AMF (1415) sends to the UE (1405) includes an identifier (e.g., SF routing ID) of the SF (1420) that sends the UE-SF PDU (1443), so that the terminal (1405) can identify the SF (1420) that sends the UE-SF PDU (1443).

[0196] The base station (1410) can deliver the NAS message (1442) included in the NGAP message (1441) transmitted by the AMF (1415) to the terminal (1405). The base station (1410) can include the NAS message (1445) in the RRC message (1444) transmitted to the terminal (1405). At this time, the NAS message (1445) and UE-SF PDU (1446) that the base station (1410) includes in the RRC message (1444) and transmits to the terminal (1405) may be the same message as the NAS message (1442) and UE-SF PDU (1443) transmitted by the AMF (1415) to the base station (1410), or may be a message containing information equivalent to the NAS message (1442) and UE-SF PDU (1443).

[0197] The terminal (1405) can perform an operation for an ISAC service using the ISAC information included in the received UE-SF PDU (1446).

[0198] Multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously on a single peer (e.g., a single terminal (1405) and a single SF (1420)). The terminal (1405) and the SF (1420) may include an SF processing identifier (e.g., SF transaction ID) in the UE-SF PDU (1433, 1436, 1438, 1440, 1443, 1446) to identify which ISAC operation each different UE-SF PDU corresponds to.

[0199] FIG. 15 is a diagram illustrating the structure of a communication protocol between a terminal and an SF in a wireless communication system according to various embodiments of the present disclosure.

[0200] Referring to FIG. 15, the terminal (1505) can be connected to the base station (1510) to transmit and receive data, the base station (1510) can transmit and receive data with the UPF (1515), and the UPF (1515) can transmit and receive data with the SF (1520). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example of FIG. 2.

[0201] The terminal (1505) may use a new protocol (UE-SF protocol) PDU for transmitting data between the terminal (1505) and the SF (1520) as a method for transmitting control information, signal information, or measurement information related to the ISAC to the SF (1520). That is, the information that the terminal (1505) intends to transmit to the SF (1520) may be included in the form of an information element (IE) in the UE-SF PDU (protocol data unit) (1532).

[0202] The UE-SF PDU (1532) that the terminal (1505) transmits to the SF (1520) may be included in the user data (1531) that the terminal (1505) transmits to the base station (1510).

[0203] The base station (1510) can transmit the user data (1531) transmitted by the terminal (1505) to the SF by transmitting the message (1533) of the N6 interface to the UPF (1515). The user data (1534) and UE-SF PDU (1535) transmitted by the base station (1510) to the UPF (1515) may be the same message as the user data (1531) and UE-SF PDU (1532) transmitted by the terminal (1505) to the base station (1510), or may be a message containing information equivalent to the data (1531) and UE-SF PDU (1532).

[0204] UPF (1515) can transmit user data (1534) included in the message (1533) of the N6 interface received from the base station (1510) to SF (1520), which is the destination of the user data (1534). At this time, UPF (1515) can use a data network or an interface within the core network to transmit the user data (1534) to SF (1520). A new data plane or network slice may be used to distinguish the data transmitted and received by SF (1520) and the terminal (1505) from other network entities or entities of other data networks. The user data (1536) and UE-SF PDU (1537) that UPF (1515) transmits to SF (1520) may be the same message as the user data (1534) and UE-SF PDU (1535) that base station (1510) transmits to UPF (1515), or may be a message containing information equivalent to the user data (1534) and UE-SF PDU (1535).

[0205] SF (1520) can perform operations for ISAC services using information from the UE-SF PDU (1537) received from the UE (1505).

[0206] SF (1520) may use a UE-SF protocol PDU to transmit data between the terminal (1505) and SF (1520) as a method for transmitting control information, signal information, or measurement information related to ISAC to the terminal (1505). That is, the information that SF (1520) intends to transmit to the terminal (1505) may be included in the UE-SF PDU (1539) in the form of an information element (IE).

[0207] SF (1520) can transmit the UE-SF PDU (1539) to UPF (1515) as user data (1538) in order to transmit the UE-SF PDU (1539) to the terminal (1505).

[0208] UPF (1515) can transmit a message (1540) of an N6 interface containing user data (1541) to a base station (1510) in order to transmit data to a terminal that is the recipient of the user data (1538) transmitted by SF (1520). The user data (1541) and UE-SF PDU (1542) transmitted by UPF (1515) to the base station (1510) may be the same message as the user data (1538) and UE-SF PDU (1539) transmitted by SF (1520) to UPF (1515), or may be a message containing information equivalent to the user data (1538) and UE-SF PDU (1539).

[0209] The base station (1510) can transmit user data (1541) included in the N6 interface message (1540) transmitted by the UPF (1515) to the terminal (1505). At this time, the user data (1543) and UE-SF PDU (1544) transmitted by the base station (1510) to the terminal (1505) may be the same message as the user data (1541) and UE-SF PDU (1542) transmitted by the UPF (1515) to the base station (1510), or may be a message containing information equivalent to the user data (1541) and UE-SF PDU (1542).

[0210] The terminal (1505) can perform an operation for an ISAC service using the ISAC information included in the received UE-SF PDU (1544).

[0211] Multiple ISAC operations (e.g., sensing via ISAC services in different regions) can be performed simultaneously on a single peer (e.g., a single terminal (1505) and a single SF (1520)). The terminal (1505) and the SF (1520) may include an SF processing identifier (e.g., SF transaction ID) in the UE-SF PDU (1532, 1535, 1537, 1539, 1542, 1544) to identify which ISAC operation each different UE-SF PDU corresponds to.

[0212] FIG. 16 is a diagram illustrating an example of a signal flow in which a UE performs an association procedure with an SF in a wireless communication system according to various embodiments of the present disclosure.

[0213] Referring to FIG. 16, the terminal (1605) can transmit and receive data with the SF (1620) through the base station (1610) and the AMF (1615). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example of FIG. 2. The method by which the terminal (1605), the base station (1610), the AMF (1615), and the SF (1620) exchange messages with each other may be the same as described in FIGs. 12, 13, 14, and 15.

[0214] The terminal (1605) can perform a UE association procedure to transmit information related to the ISAC performance of the terminal (1605) to the SF (1620) and to notify the connection status.

[0215] In one embodiment, the terminal (1605) can transmit information related to ISAC execution to the SF (1620) via the base station (1610) and / or AMF (1615).

[0216] The terminal (1605) can transmit a NAS message (1631) to the AMF (1615) to request that the AMF (1615) transmit a UE association request to the SF (1620). The NAS message (1631) may include a message (e.g., a UE-AMF UE association request) containing information that the terminal (1605) must transmit to the SF (1620) to perform an ISAC operation, and the information that the terminal (1605) must transmit to the SF (1620) to perform an ISAC operation may include at least one of the following.

[0217] - SF routing ID: The terminal may include one or more SF identifiers (SF routing IDs) to perform the UE association procedure.

[0218] - UE ISAC capabilities: May include information on the ability of a terminal to perform ISAC operations, and the capability information may include at least one of the following.

[0219] * supported RS type: Can indicate the type of reference signal (RS) that the terminal can measure or transmit (e.g., SSB, CSI-RS, PRS, SRS, DMRS, etc.).

[0220] * ISAC computing capabilities: The ability of a terminal to measure and compute ISAC RS (e.g., raw data (measurement result), whether the measurement result is computed to a final result (e.g., size, speed, material of an object), or whether the measurement result is computed to an intermediate result of a predefined level, computational accuracy, computational delay time, measurable area, etc., may be responded to SF (1620), and each capability may be responded to SF (1620) by a level (e.g., 0 (highest) to 9 (lowest)) or a predefined value.

[0221] * supported BW: May indicate the bandwidth (bandwidth, BW) over which the terminal can measure or transmit ISAC RS.

[0222] * Tx / Rx type: Can indicate whether the terminal can only receive ISAC RS, only transmit, or both transmit and receive.

[0223] * IDLE / INACTIVE measurement availability: May indicate whether the terminal can perform ISAC RS measurements or ISAC RS transmissions in the RRC IDLE or RRC INACTIVE state.

[0224] - Location information (if known, location coordinates and stationary information): May include the terminal's location information.

[0225] - Serving LMF (e.g., routing ID): May include the terminal's serving LMF information.

[0226] - PRU on / off state (if it is PRU): If the terminal is a PRU (Passive Radio Unit), it may include the operating state of the PRU.

[0227] - TAC, gNB ID, Cell ID: May include the tracking area code (TAC), gNB ID, and cell ID of the cell the terminal is currently camping in.

[0228] The AMF (1620) may select one of the SF identifiers (SF routing IDs) included in the NAS message (1631) received from the terminal (1605), or transmit an AMF-SF UE association request message (1632) to one of the selected SFs (1620) among the SFs pre-configured by the service provider. The AMF-SF UE association request may include all or part of the information transmitted by the terminal in the NAS message (1631), and the AMF (1615) may additionally include in the AMF-SF UE association request the tracking area code, gNB ID, cell ID, and terminal identifier (e.g., SUPI (Subscription Permanent Identifier)) of the cell or base station (1610) that the terminal (1605) is currently camping in. Additionally, the AMF (1615) may include a terminal identifier (UE correlation ID) to inform the SF (1620) which terminal (1605) is performing the association operation.

[0229] SF (1620) receives an AMF-SF UE association request (1632) message, and if it can accept the association procedure of the terminal (1605) corresponding to the AMF-SF UE association request (1632) message, it can send an AMF-SF UE association accept message (1633) to the AMF (1615).

[0230] The AMF (1615) receives an AMF-SF UE association accept message (1633) from the SF (1620) and can transmit a UE-AMF UE association accept message to a terminal (1605) corresponding to the UE correlation ID included in the AMF-SF UE association accept message (1633) using a NAS message (1634). The AMF (1615) can include an SF routing ID in the NAS message (1634) so ​​that the terminal can identify the SF (1620) transmitting the UE association accept.

[0231] SF (1620) receives an AMF-SF UE association request (1632) message, and if SF (1620) cannot accept the association procedure of the terminal (1605) corresponding to the AMF-SF UE association request (1632) message (e.g., if the terminal (1605) does not have sufficient capability for ISAC operation, or if SF (1620) cannot accept a new terminal due to overload, etc.), it can send an AMF-SF UE association reject message (1635) to AMF (1615). At this time, SF (1620) performs an operation to determine whether it can accept the association procedure of the terminal (1605) corresponding to (associated with) the AMF-SF UE association request (1632) message, and depending on the result of the operation, it may be determined whether or not it can accept the association procedure of the terminal (1605) corresponding to (associated with) the AMF-SF UE association request (1632) message.

[0232] The AMF (1615) receives an AMF-SF UE association reject message (1635) from the SF (1620) and can transmit the UE-AMF UE association reject message to the terminal (1605) corresponding to the included UE correlation ID using a NAS message (1636).

[0233] SF (1620) may instruct the terminal (1605) to perform a new SF identifier (SF routing ID) for the UE association procedure, and the terminal (1605) may perform the UE association procedure again for the SF corresponding to the new SF identifier included in the UE-AMF UE association reject message. Additionally, SF (1620) may determine that there is a new SF to perform the UE association procedure, but at the time the AMF-SF UE association reject message (1635) is transmitted to the terminal (1605), it may determine that the new SF cannot immediately accept the terminal (1605). In this case, information regarding the time when the UE association procedure with the terminal (1605)'s new SF can be started may be included in the AMF-SF UE association reject message (1635) along with the new SF identifier (SF routing ID). In this case, the terminal (1605) that receives the AMF-SF UE association reject message (1635) can start the UE association procedure with the new SF at the time indicated by the information regarding the time when the start of the UE association procedure with the new SF becomes possible.

[0234] Additionally, although the SF (1620) has determined that there is no new SF to perform the UE association procedure, it may be determined that the SF (1620) will be able to accept the terminal (1605) at a specific point in time after the time when the AMF-SF UE association reject message (1635) is transmitted to the terminal (1605). In this case, information regarding the time when the start of the UE association procedure with the SF (1620) of the terminal (1605) becomes possible may be included in the AMF-SF UE association reject message (1635). In this case, the terminal (1605) that receives the AMF-SF UE association reject message (1635) may retry the UE association procedure with the SF (1620) at the time indicated by the information regarding the time when the start of the UE association procedure with the SF (1620) becomes possible. When the terminal (1605) receives an AMF-SF UE association reject message (1635) that contains only information regarding the time when the UE association procedure with the SF (1620) can be started, the terminal (1605) may interpret the AMF-SF UE association reject message (1635) as requiring a retry of the UE association procedure with the SF (1620) at the time indicated by the information regarding the time when the UE association procedure with the SF (1620) can be started. Alternatively, an identifier for the SF (1620) may be included in the AMF-SF UE association reject message (1635) along with the information regarding the time when the UE association procedure with the SF (1620) can be started.

[0235] Additionally, SF (1620) may include information regarding the time when the next UE association procedure can be performed again in the AMF-SF UE association reject message (1635) to prevent the terminal (1605) from frequently performing the UE association procedure. In this case, the terminal (1605) that receives the AMF-SF UE association reject message (1635) may not retry the UE association procedure with SF (1620) until the time indicated by the information regarding the time when the start of the UE association procedure with SF (1620) becomes possible again. When a terminal (1605) receives an AMF-SF UE association reject message (1635) containing only information regarding the time when the UE association procedure with SF (1620) can be started, the terminal (1605) may interpret the AMF-SF UE association reject message (1635) as allowing a retry of the UE association procedure with SF (1620) if a retry is required at the time indicated by the information regarding the time when the UE association procedure with SF (1620) can be started (e.g., if a UE association procedure with another SF has not been performed). Alternatively, an identifier for SF (1620) may be included in the AMF-SF UE association reject message (1635) along with the information regarding the time when the UE association procedure with SF (1620) can be started.

[0236] FIG. 17 is a diagram illustrating an example of a signal flow in which a UE performs an association update procedure with an SF in a wireless communication system according to various embodiments of the present disclosure.

[0237] Referring to FIG. 17, the terminal (1705) can transmit and receive data with the SF (1720) through the base station (1710) and the AMF (1715). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example of FIG. 2. The method by which the terminal (1705), the base station (1710), the AMF (1715), and the SF (1720) exchange messages with each other may be the same as described in FIGs. 12, 13, 14, and 15.

[0238] The terminal (1705) can perform a UE association update procedure to notify updates to information related to ISAC execution, such as when information transmitted is changed after performing an association procedure with the SF (1720) as in the example of FIG. 16 (e.g., changes in UE ISAC capabilities, changes in location information, changes in serving LMF, changes in PRU on / off state, changes in TAC, gNB ID, cell ID).

[0239] The terminal (1705) can send a NAS message (1731) to the AMF (1715) to request that the AMF (1715) send a UE association update request to the SF (1720). The NAS message (1731) may include a UE-AMF UE association update request. The UE-AMF UE association update request may include only parts that are different from the information previously transmitted through the UE association procedure or the UE association update procedure, or it may include the entire information that includes both the same information and different information as previously transmitted through the UE association procedure or the UE association update procedure.

[0240] The AMF (1720) can send an AMF-SF UE association update request message (1732) to the SF (1720) corresponding to the SF identifier (SF routing ID) included in the NAS message (1731) received from the terminal (1705). The AMF-SF UE association update request may include all or part of the information transmitted by the terminal in the NAS message (1731), and the AMF (1715) may additionally include the tracking area code, gNB ID, and cell ID of the cell where the terminal is currently camping. Additionally, the AMF (1715) may include a UE identifier (UE correlation ID) to inform the SF (1720) which terminal (1705) is performing the association update operation.

[0241] The terminal (1705) can transmit a UE association update request to the SF (1720) as a message (UE-SF UE association update request, 1733) in which the AMF (1715) is not involved. The message (UE-SF UE association update request, 1733) in which the AMF (1715) is not involved may be a message in which the gNB (1710) / AMF (1715) simply forwards the message to the SF (1720) without performing any form of processing after receiving the message. Alternatively, the message (UE-SF UE association update request, 1733) in which the AMF (1715) is not involved may be a message in which the terminal (1705) can transmit directly to the SF (1720) without going through the gNB (1710) and AMF (1715).

[0242] SF (1720) receives an AMF-SF UE association update request (1732) message, and if it can accept the association update procedure of the corresponding (associated) terminal (1705) for the AMF-SF UE association update request (1732) message, it can send an AMF-SF UE association update accept message (1734) to the AMF (1715).

[0243] The AMF (1715) receives an AMF-SF UE association update accept message (1734) from the SF (1720) and can transmit a UE-AMF UE association update accept message to a terminal (1705) corresponding to the UE correlation ID included in the AMF-SF UE association update accept message (1734) using a NAS message (1735). The AMF (1715) can include an SF routing ID in the NAS message (1735) so that the terminal can identify the SF (1720) transmitting the UE association update accept.

[0244] SF (1720) receives a UE-SF UE association update request (1733) message, and if SF (1720) can accept the association update procedure of the terminal (1705) corresponding to the UE-SF UE association update request (1733) message, it can send a UE-SF UE association update accept message (1736) to the terminal (1705).

[0245] SF (1720) receives an AMF-SF UE association update request (1732) message, and if SF (1720) cannot accept the association update procedure of the terminal (1705) corresponding to the UE-SF UE association update request (1733) message (e.g., if the terminal (1705) does not have sufficient capability for ISAC operation, or if SF (1720) cannot accept the new terminal due to overload, etc.), it may send an AMF-SF UE association update reject message (1737) to AMF (1715). At this time, SF (1720) performs an operation to determine whether it can accept the association procedure of the terminal (1675) corresponding to (associated with) the AMF-SF UE association request (1732) message, and depending on the result of the operation, it may be determined whether or not it can accept the association procedure of the terminal (1705) corresponding to (associated with) the AMF-SF UE association request (1732) message.

[0246] AMF (1715) receives an AMF-SF UE association update reject message (1737) from SF (1720) and can transmit the UE-AMF UE association update reject message to a terminal (1705) corresponding to the included UE correlation ID using a NAS message (1738).

[0247] SF (1720) receives a UE-SF UE association update request (1733) message and, if it can accept the association update procedure of the corresponding terminal (1705), can send a UE-SF UE association update reject message (1739) to the terminal (1705).

[0248] SF (1720) may instruct the terminal (1705) to perform a new SF identifier (SF routing ID) for the UE association update procedure after rejecting the UE association update, and the terminal (1705) may perform the UE association update procedure again for the SF corresponding to the new SF identifier included in the UE association update reject message. Additionally, SF (1720) may determine that there is a new SF to perform the UE association update procedure, but at the time when the UE-SF UE association update reject message (1739) is transmitted to the terminal (1705), it may determine that the new SF cannot immediately accommodate the terminal (1705). In this case, information regarding the time when the UE association update procedure with the terminal (1705)'s new SF can be started may be included in the AMF-SF UE association reject message (1635), along with the new SF identifier (SF routing ID). In this case, the terminal (1705) that receives the UE-SF UE association update reject message (1739) can start the UE association update procedure with the new SF at the time indicated by the information regarding the time when the start of the UE association update procedure with the new SF becomes possible.

[0249] Additionally, although the SF (1720) has determined that there is no new SF to perform the UE association update procedure, it may be determined that the SF (1720) will be able to accept the terminal (1705) at a specific time thereafter when the UE-SF UE association update reject message (1739) is transmitted to the terminal (1705). In this case, information regarding the time when the start of the UE association update procedure with the SF (1720) of the terminal (1705) becomes possible may be included in the UE-SF UE association update reject message (1739). In this case, the terminal (1705) that receives the UE-SF UE association update reject message (1739) may retry the UE association update procedure with the SF (1720) at the time indicated by the information regarding the time when the start of the UE association procedure with the SF (1720) becomes possible. When the terminal (1705) receives an AMF-SF UE association reject message (1735) containing only information regarding the time when the UE association update procedure with the SF (1720) can be started, the terminal (1705) may interpret the UE-SF UE association update reject message (1739) as indicating that the UE association update procedure with the SF (1720) must be retried at the time indicated by the information regarding the time when the UE association update procedure with the SF (1720) can be started. Alternatively, along with the information regarding the time when the UE association update procedure with the SF (1720) can be started, an identifier for the SF (1720) may also be included in the UE-SF UE association update reject message (1739).

[0250] Additionally, SF (1720) may include information regarding the time when the next UE association update procedure can be performed again in the AMF-SF UE association update reject message (1739) to prevent the terminal (1705) from frequently performing the UE association update procedure. In this case, the terminal (1705) that receives the AMF-SF UE association reject message (1739) may not retry the UE association update procedure with SF (1720) until the time indicated by the information regarding the time when the start of the UE association update procedure with SF (1720) becomes possible again. When a terminal (1705) receives a UE-AMF UE association update reject message (1739) containing only information regarding the time when the UE association update procedure with SF (1720) can be started, the terminal (1705) may interpret the UE-AMF UE association update reject message (1739) as allowing a retry of the UE association procedure with SF (1720) when a retry is required at the time indicated by the information regarding the time when the UE association update procedure with SF (1720) can be started (for example, when the change in the terminal's information is maintained and the UE association update procedure is continuously required). Alternatively, an identifier for SF (1720) may be included in the AMF-SF UE association update reject message (1739) along with the information regarding the time when the UE association update procedure with SF (1720) can be started.

[0251] FIG. 18 is a diagram illustrating an example of a signal flow in which a UE performs a disassociation procedure with an SF in a wireless communication system according to various embodiments of the present disclosure.

[0252] Referring to FIG. 18, the terminal (1805) can transmit and receive data with the SF (1820) through the base station (1810) and the AMF (1815). The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as in the example of FIG. 2. The method by which the terminal (1805), the base station (1810), the AMF (1815), and the SF (1820) exchange messages with each other may be the same as described in FIGs. 12, 13, 14, and 15.

[0253] If the terminal (1805) no longer wishes to perform ISAC operations after performing an association procedure with the SF (1820) as in the example of FIG. 16 (e.g., user operation, software upgrade, power off, etc.), it may perform a UE-initiated UE disassociation procedure.

[0254] The terminal (1805) can send a NAS message (1831) to the AMF (1815) to request the AMF (1815) to send a UE disassociation request to the SF (1820). The NAS message (1831) may include a UE-AMF UE disassociation request. The UE-AMF UE disassociation request may include the reason for requesting disassociation (e.g., user operation, software upgrade, power shutdown, etc.).

[0255] The AMF (1820) may send an AMF-SF UE disassociation request message (1832) to the SF (1820) corresponding to the SF identifier (SF routing ID) included in the NAS message (1831) received from the terminal (1805). The AMF-SF UE disassociation request may include all or part of the information transmitted by the terminal in the NAS message (1831). Additionally, the AMF (1815) may include a UE identifier (UE correlation ID) to inform the SF (1820) which terminal (1805) is performing the disassociation operation.

[0256] The terminal (1805) can transmit a UE disassociation request to the SF (1820) as a message (UE-SF UE disassociation request, 1833) in which the AMF (1815) is not involved. The message (UE-SF UE disassociation request, 1833) in which the AMF (1815) is not involved may be a message in which the gNB (1810) / AMF (1815) simply forwards the message to the SF (1820) without performing any form of processing after receiving the message. Alternatively, the message (UE-SF UE disassociation request, 1833) in which the AMF (1815) is not involved may be a message in which the terminal (1805) can transmit directly to the SF (1820) without going through the gNB (1810) and the AMF (1815).

[0257] SF (1820) receives an AMF-SF UE disassociation request (1832) message, and if it needs to respond to the received AMF-SF UE disassociation request (1832) message with a disassociation accept message (e.g., if the disassociation request includes an acknowledge indicator), it can send an AMF-SF UE disassociation accept message (1834) to AMF (1815).

[0258] The AMF (1815) receives an AMF-SF UE disassociation accept message (1834) from the SF (1820) and can transmit a UE-AMF UE disassociation accept message to a terminal (1805) corresponding to the UE correlation ID included in the AMF-SF UE disassociation accept message (1834) using a NAS message (1835). The AMF (1815) can include an SF routing ID in the NAS message (1835) so that the terminal (1805) can identify the SF (1820) that transmitted the UE disassociation accept.

[0259] SF (1820) receives a UE-SF UE disassociation request (1833) message, and if it is to respond to the UE-SF UE disassociation request (1833) message with disassociation accept (e.g., if the disassociation request includes an acknowledge indicator), it can send a UE-SF UE disassociation accept message (1836) to the terminal (1805).

[0260] SF (1820) may perform an SF-initiated UE disassociation procedure if it no longer wishes to perform the ISAC operation transmitted after performing the association procedure with the terminal (1805) as described in FIG. 16 (e.g., user operation, software upgrade, power off, etc.).

[0261] SF (1820) can send an AMF-SF UE disassociation request (1837) to AMF (1815) to request that AMF (1815) send a UE disassociation request to SF (1820). A NAS message (1838) may include a UE-AMF UE disassociation request. The AMF-SF UE disassociation request may include the reason for requesting disassociation (e.g., user operation, software upgrade, power shutdown, etc.).

[0262] SF (1820) can send a UE disassociation request to the UE (1805) as a message in which the AMF (1815) is not involved (UE-SF UE disassociation request, 1839).

[0263] SF (1820) may instruct the terminal (1805) to provide an identifier (SF routing ID) of the SF to be replaced after UE disassociation, and the terminal (1805) may perform the UE association procedure again on the SF corresponding to the new SF identifier included in the UE disassociation request or UE disassociation request accept message. A message in which the AMF (1815) is not involved (UE-SF UE disassociation request, 1839) may be a message in which the gNB (1810) / AMF (1815) simply forwards the message to the UE (1805) without performing any form of processing after receiving the message. Alternatively, a message in which the AMF (1815) is not involved (UE disassociation request AMF (1815)) may be a message in which the SF (1820) can send directly to the UE (1805) without going through the gNB (1810) and AMF (1815).

[0264] If the terminal (1805) receives a UE-AMF UE disassociation request (1838) message and needs to respond with disassociation accept (e.g., if the disassociation request includes an acknowledge indicator), it can send a UE-AMF UE disassociation accept message (1834) to the AMF (1815). The AMF (1815) can forward the UE-AMF UE disassociation accept message as an AMF-SF UE disassociation accept message (1841) to the SF corresponding to the SF identifier (SF routing ID) included in the UE-AMF UE disassociation accept message (1834).

[0265] The terminal (1805) can transmit the UE disassociation accept to the SF (1820) as a message (UE-SF UE disassociation accept, 1842) in which the AMF (1815) is not involved. The message (UE-SF UE disassociation accept, 1842) in which the AMF (1815) is not involved may be a message in which the gNB (1810) / AMF (1815) simply forwards the message to the SF (1820) without performing any form of processing after receiving the message. Alternatively, the message (UE-SF UE disassociation accept, 1842) in which the AMF (1815) is not involved may be a message in which the terminal (1805) can transmit directly to the SF (1820) without going through the gNB (1810) and AMF (1815).

[0266] SF (1820) receives UE disassociation accept messages (1841, 1842) and can confirm that the UE disassociation procedure with the terminal (1805) has been successfully completed.

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

[0268] Referring to FIG. 19, the base station (1905) may transmit or receive messages or information directly or indirectly with the SF (1910). The method by which the base station (1905) transmits or receives messages or information with the SF (1910) may be that described in FIG. 8, 9, 10, and 11, or other methods not described in the present disclosure.

[0269] SF (1910) may transmit a specific message (e.g., a TRP information request) to a base station (1905) to obtain information about a base station (1905) and a transmission-reception point (TRP) managed by the base station (1905). The transmission of the TRP information request (1921) may be triggered by a periodic update procedure for a TRP from which SF (1910) has previously collected information, or by an orchestration and management (OAM). SF (1910) may include a request for information to be obtained from at least one TRP in the TRP information request (1921). The information that SF (1910) requests from the base station (1905) may include at least one of the following. Of course, it is not limited to the examples below.

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

[0271] - TRP information type: An indicator representing a request for ISAC information

[0272] - TRP geographical coordinates: SF(1910) can request the location of the TRP.

[0273] - TRP spatial direction information: SF(1910) can request the direction of the TRP or the angle per beam.

[0274] - TRP type: SF(1910) can request TRP characteristics including tp, rp, and trp.

[0275] - Tx power: SF(1910) can request the current and maximum transmission power characteristics of the TRP.

[0276] - ISAC capability: SF(1910) can request information on the capability to perform ISAC operations per TRP.

[0277] - ISAC RS type: SF (1910) may request what 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), DMRS (demodulation reference signal), etc. may be responded to the request of SF (1910).

[0278] - ISAC RS bandwidth: SF (1910) may request a bandwidth that is transmitting or can transmit RS for ISAC purposes. For example, ARFCN (absolute radio frequency channel number), carrier bandwidth, point A, SCS (subcarrier spacing), etc. may be responded to in response to SF (1910)'s request.

[0279] - ISAC RS frequency-scale pattern: SF (1910) may request frequency characteristics or patterns of RS for ISAC use. For example, comb size, offset, cyclic shift, frequency hopping, etc. may be responded to the request of SF (1910).

[0280] - ISAC RS time-scale pattern: SF (1910) may request the time characteristics or pattern of the RS for ISAC use. For example, the number of symbols, repetition factor, resource set periodicity, etc. may be responded to the request of SF (1910).

[0281] - on-demand ISAC RS pattern: SF(1910) may request the bandwidth, frequency, and temporal characteristics or pattern of the RS for ISAC that the TRP can transmit. For example, the allowed values ​​may be responded to in the form of a list or a bit string, and in the case of a bit string, the value corresponding to each bit may be represented as 1 if configurable and 0 if not configurable.

[0282] - ISAC processing capability: SF (1910) may request the capability of the base station to calculate the measurement results obtained through ISAC operation. For example, the capability to calculate the measurement results into a final result (e.g., size, speed, material of an object), or the capability to calculate intermediate results of a predefined level, calculation accuracy, calculation latency, measurable area, etc., may be responded to, and each capability may respond to the request of SF (1910) with a level (e.g., 0 (highest) to 9 (lowest)) or a predefined value.

[0283] - supported event: SF(1910) may request whether the base station has the ability to determine whether it satisfies a specific condition related to ISAC. 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 period, that a condition is a condition of the operating state of a specific TRP, that a condition is a condition that a specific object is sensed after an ISAC operation is performed, that a condition is a condition that a specific timer expires, or that a condition is a condition that a specific action (e.g., position, orientation, speed, gesture) on an object is satisfied after an ISAC operation is performed.

[0284] According to one embodiment, a base station (1905) may transmit a predetermined message (e.g., TRP information response) to SF (1910) to respond to SF (1910) with information requested by a TRP information request (1921) from SF (1910). The TRP information response (1922) may include at least a portion of the information requested by the TRP information request (1921) from SF (1910). If the base station (1905) cannot respond to a portion of the information requested by the TRP information request (1921) from SF (1910) or does not support the requested function, it may notify SF (1910) by including at least one of the following in the TRP information response (1922): not including a value, an indicator 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, an incorrect TRP ID was requested).

[0285] According to one embodiment, if the base station (1905) is unable to respond to part of the information requested by the TRP information request (1921) from the SF (1910) or does not support the requested function, it may respond to the SF (1910) with a predetermined message (e.g., TRP information failure). The base station (1905) may notify the SF (1910) in the TRP information failure (1923) by including at least one of an indicator that it is unable to respond to or does not support the information requested by the SF (1910), or a reason for the inability to respond (e.g., the TRP does not support ISAC, or an incorrect TRP ID was requested).

[0286] According to one embodiment, if a portion of the information responded to in the TRP information response (1922) is updated, the base station (1905) may notify the SF (1910) of the updated information by transmitting a predetermined message (e.g., TRP information update) to the SF (1910). The base station (1905) may include the information updated at the time of transmitting the TRP information update compared to the TRP information response or TRP information update that the base station (1905) previously transmitted to the SF (1910). The base station (1905) may include all information requested in the TRP information request or updated information in the TRP information update (1924).

[0287] FIG. 20 is a diagram illustrating an example of a signal flow in which an SF selects a terminal and a base station to perform an ISAC operation in a wireless communication system according to one embodiment of the present disclosure.

[0288] Referring to FIG. 20, a terminal (2005), a base station (2010), an AMF (2015), an LMF (2020), and an SF (2025) can transmit and receive data to and from each other. The interface through which each entity communicates may be a service-based interface or a reference point-based interface as described in FIG. 2. The method by which the terminal (2005) and the base station (2010), the AMF (2015), the LMF (2020), and the SF (2025) exchange messages with each other may be the same as described in FIGs. 8, 9, 10, 11, 12, 13, 14, and 15.

[0289] SF (2025) may need information of the terminal (2005) (e.g., the terminal's ISAC capability information, location information, current status, etc.) to select the terminal (2005) to perform the ISAC operation, and the terminal (2005) may transmit information to SF (2025) for the ISAC operation (to be used by SF (2025) to select the terminal (2005) to perform the ISAC operation) through a UE association procedure or a UE association update procedure (e.g., FIG. 16, 17).

[0290] SF (2025) may need information of the base station (2010) (e.g., ISAC capability information, location information, current status, etc.) to select the base station (2010) to perform ISAC operations, and the base station (2010) may transmit information for ISAC operations to SF (2025) through a TRP information exchange procedure (e.g., FIG. 19).

[0291] When SF (2025) needs to obtain location information of a terminal (2005) to perform an ISAC operation, it may request (2033) the location information of the terminal (2005) from AMF (2015) using a terminal identifier such as a UE correlation ID or SUPI. At this time, to obtain the location information of the terminal (2005), SF (2025) may send a location request directly to AMF (2015) or request it from another network entity such as GMLC.

[0292] AMF (2015) can perform a network triggered service request (2034) procedure to perform a location estimation operation in the CM CONNECTED state when the terminal (2005) is in the CM (connection management) IDLE state.

[0293] The AMF (2015) can select the LMF (2020) for estimating the location of the terminal (2005) (2035).

[0294] The AMF (2015) can request the LMF (2020) to estimate the location of the terminal (2005) (2036).

[0295] LMF (2020) can perform a location estimation operation (2037) of the terminal (2005).

[0296] The LMF (2020) can respond (2038) to the AMF (2015) with the location of the terminal (2005) estimated through the location estimation operation (2037).

[0297] The AMF (2015) can respond (2039) to the SF (2025) with the location of the terminal (2005) received from the LMF (2020). At this time, the network entity receiving the response with the location of the terminal (2005) may be a network entity other than the SF (2025) (e.g., GMLC).

[0298] SF (2025) can perform selection (2040) of the terminal (2005) and base station (2010) to perform ISAC operations based on information of the terminal (2005) and base station (2010) (e.g., ISAC RS transmission / reception information, location information, computing capability, etc. of the terminal (2005) and base station (2010).

[0299] FIG. 21 is a diagram illustrating an example of a signal flow in which an SF instructs a base station and a terminal to perform an ISAC operation using a downlink ISAC reference signal in a wireless communication system according to one embodiment of the present disclosure.

[0300] Referring to FIG. 21, a terminal (2105), a base station (2110), an AMF (2115), and an SF (2120) can transmit and receive data to and from each other. The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as described in FIG. 2. The method by which the terminal (2105), the base station (2110), the AMF (2115), and the SF (2120) exchange messages with each other may be the same as described in FIGs. 8, 9, 10, 11, 12, 13, 14, and 15.

[0301] SF (2120) can select (2131) a terminal (2105) and a base station (2110) to perform an ISAC operation using a downlink ISAC reference signal, and the selection (2131) of the terminal (2105) and the base station (2110) may be as described in FIG. 20.

[0302] SF (2120) may transmit a measurement request message (e.g., gNB-SF ISAC measurement request) to the base station (2110) for ISAC RS settings, measurement settings, and reporting settings of the selected terminal (2105) and the base station (2110). SF (2120) may transmit the gNB-SF ISAC measurement request to the base station (2110), or SF (2120) may transmit the gNB-SF ISAC measurement request to the AMF (2115), and the AMF may refer to the contents of the message and transmit it to the base station (2110). The gNB-SF ISAC measurement request may be in the form of a gNB-SF PDU or may be part of a message (2132) transmitted by SF (2120) to the AMF (2115). The gNB-SF ISAC measurement request transmitted by SF (2120) to the AMF (2115) may include at least one of the following information.

[0303] - Terminal Identifier: The AMF can identify the terminal to perform the ISAC operation in the form of a UE correlation ID or SUPI, etc.

[0304] - Base Station Identifier: The AMF can identify the base station to perform ISAC operations in the form of a gNB correlation ID or gNB ID.

[0305] - RS configuration information: May include RS information required to perform ISAC operations.

[0306] Among the on-demand values ​​(e.g., RS type, frequency-scale pattern, time-scale pattern, etc.) that the base station responded to in the TRP info response, the SF may select a value appropriate for ISAC operation and instruct the base station to transmit RS. If the SF requests one or more values, the base station may select an appropriate value.

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

[0308] * RS transmission start time and / or period: May include the start time and / or period of RS transmission or ISAC sensing.

[0309] * RS transmission repetition count and repetition period: May include the repetition count and repetition period of RS transmission or ISAC sensing.

[0310] * ISAC Operation QoS: When SF provides the base station with the characteristics or QoS of an object that requires sensing (e.g., resolution of object size, accuracy of speed, accuracy of material, measurement frequency, etc.), the base station can transmit an RS that satisfies the QoS among the RSs that can be transmitted based on the requested QoS.

[0311] - Base Station Report Result Level: This may indicate the level of ISAC sensing reports that the base station reports to the SF (e.g., raw data, intermediate result, sensing result). For the intermediate result, it may be, for example, 0 (highest) to 9 (lowest) or a predefined value, depending on the calculation level of the result. The SF may refer to the intermediate result level to calculate the intermediate result calculated by the base station as the final result.

[0312] - Terminal Report Result Level: This may indicate the level of ISAC sensing report that the terminal reports to the base station (e.g., raw data, intermediate result, sensing result). In the case of an intermediate result, it may be, for example, 0 (highest) to 9 (lowest) or a predefined value depending on the calculation level of the result. The base station may calculate the ISAC sensing result received from the terminal at the base station report result level.

[0313] - Event-based reporting conditions: The ISAC measurement reporting procedure may be performed if the reporting conditions indicated by the SF are satisfied. Reporting conditions may include the following conditions, and one condition or a combination of two or more conditions may be used.

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

[0315] * periodic: You can request that SF receive measurement reports at specific intervals.

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

[0317] * motion event: If the motion of an object detected in the measurement area satisfies the conditions, the base station may notify the SF. The motion can be distinguished by a combination of the object's shape, position, direction, speed, etc., or it may be an object corresponding to a predefined value (e.g., clenching a fist, opening a fist, etc.).

[0318] - ISAC QoS: The QoS required for ISAC operation. QoS can include the time taken from receiving the ISAC RS to reporting the measurement result (response time) and the accuracy of the measurement result report.

[0319] AMF (2115) can perform a network triggered service request (2133) procedure to perform an ISAC RS measurement operation in the CM CONNECTED state when the terminal (2105) is in the CM (connection management) IDLE state.

[0320] The AMF (2115) can transmit the gNB-SF ISAC measurement request included in the message (2132) transmitted by the SF (2120) to the base station (2110) via an NGAP message (2134). The NGAP message (2134) may include an identifier of the terminal (2105) that will perform the ISAC operation.

[0321] The base station (2110) can transmit downlink ISAC RS information to the terminal (2105) via a broadcast (e.g., SIB) message or an RRC message (2135) (e.g., RRCReconfiguration). The downlink ISAC RS information may include at least one of the following.

[0322] - RS Identifier: An identifier that distinguishes different RS based on the type of RS (e.g., PRS, DMRS, CSI-RS, SSB).

[0323] - ISAC RS Indicator: Indicates whether the corresponding RS can be measured for ISAC purposes.

[0324] - ISAC RS Identifier: An identifier capable of distinguishing different RS types or RS measured for ISAC purposes within the entire RS system.

[0325] - RS Settings: RS frequency bandwidth, RS pattern (frequency, time-repeating information), hopping pattern, TRP identifier, beam identifier, RS transmission start time (e.g., specific SFN (subframe number), specific slot, specific symbol, or specific time (absolute or relative time)), RS transmission period (e.g., in units of milliseconds to minutes), number of RS transmissions

[0326] - RS transmission information: periodic (RS transmission every RS transmission cycle after setting), semi-persistent (periodical RS transmission starts via additional signals such as DCI or MAC CE after setting), aperiodic (RS transmission via additional signals such as DCI or MAC CE after setting)

[0327] The base station (2110) can instruct the terminal (2105) to measure and report the downlink ISAC RS through an RRC message (e.g., RRCReconfiguration) (2136).

[0328] For the measurement and reporting of downlink ISAC RS, the RRC message (2136) may include at least one of the following information.

[0329] - ISAC Measurement Report Identifier: Can identify different ISAC measurement reports.

[0330] - RS Identifier, ISAC RS Identifier: Can identify the RS being measured.

[0331] - Terminal report result level: This may indicate the level of ISAC sensing report that the terminal reports to the base station (e.g., raw data, intermediate result, sensing result). For the intermediate result, depending on the calculation level of the result, it may be, for example, 0 (highest) to 9 (lowest) or a predefined value.

[0332] - Event-based reporting conditions: The ISAC measurement reporting procedure may be performed if the reporting conditions are satisfied. The reporting conditions may include the conditions below, and one condition or a combination of two or more conditions may be used.

[0333] * Response time: You can request that the base station receive the measurement report by a specific point in time.

[0334] * periodic: You can request that SF receive measurement reports at specific intervals.

[0335] * Target Object Availability: The terminal may notify the base station if an object detected in the measurement area enters or leaves the measurement area. The target object may be distinguishable by a combination of shape, size, speed, material, etc., or may be an object corresponding to a predefined value (e.g., a person or a car).

[0336] * Motion event: If the motion of an object detected in the measurement area satisfies the conditions, the terminal may notify the base station. The motion can be distinguished by a combination of the object's shape, position, direction, speed, etc., or it may be an object corresponding to a predefined value (e.g., clenching a fist, opening a fist, etc.).

[0337] - ISAC QoS: The QoS required for ISAC operation. QoS can include the time taken from receiving the ISAC RS to reporting the measurement result (response time) and the accuracy of the measurement result report.

[0338] - Measurement Trigger: The base station can instruct the terminal to take a measurement via DCI or MAC CE, and the terminal can measure and report the instructed ISAC RS.

[0339] When the base station (2110) instructs the terminal (2105) to take a measurement using a measurement trigger (e.g., DCI or MAC CE), it may transmit a signal (2137) containing information of the measurement target ISAC RS (e.g., RS identifier) ​​to the terminal. At this time, the base station (2110) may simultaneously transmit semi-persistent or aperiodic signal transmission information and the measurement instruction to the terminal (2105) via DCI or MAC CE.

[0340] The terminal (2105) can measure the ISAC RS (2138) indicated by periodic measurements or measurement triggers.

[0341] The terminal (2105) can report ISAC measurement results by transmitting an RRC message (e.g., an ISAC measurement report) (2139) to the base station (2110). The RRC ISAC measurement report (2139) may include at least one of the following information. Of course, the ISAC measurement report may also be transmitted via layer messages other than the RRC message.

[0342] - ISAC Measurement Report Identifier: May include a measurement report identifier.

[0343] - RS Identifier, ISAC RS Identifier: May include the identifier of the measured ISAC RS.

[0344] - Measurement result and terminal report result level: This may indicate the level of ISAC sensing report that the terminal reports to the base station (e.g., raw data, intermediate result, sensing result). In the case of an intermediate result, depending on the calculation level of the result, it may be, for example, 0 (highest) to 9 (lowest) or a predefined value.

[0345] The base station (2110) may transmit a gNB-SF ISAC measurement report to the SF (2120) via the AMF (2115) in order to report the measurement result (2139) reported by the terminal (2105) to the SF. The base station (2110) may transmit an NGAP message (2140) containing the gNB-SF ISAC measurement report to the AMF (2115). The gNB-SF ISAC measurement report may be one in which additional calculations are performed based on the information reported by the terminal (2105) to the base station (2110), or it may contain the same information reported by the terminal (2105) to the base station (2110). The gNB-SF ISAC measurement report may be included in the NGAP message (2140) in the form of a gNB-SF PDU, or it may be transmitted to the AMF (2115) and then transmitted by the AMF (2115) to the SF (2120) via a new message. The NGAP message (2140) may include an identifier (e.g., SF routing ID) of the SF (2120) to which the gNB-SF ISAC measurement report is transmitted.

[0346] The AMF (2115) can transmit a gNB-SF PDU containing a gNB-SF ISAC measurement report to the SF (2120) as an Nsf message (2141). The Nsf message (2141) may include an identifier of the terminal (2105) that measured the ISAC RS (e.g., UE correlation ID) and an identifier of the base station (2110) (e.g., gNB correlation ID).

[0347] FIG. 22 is a diagram illustrating an example of a signal flow in which an SF instructs a base station and a terminal to perform an ISAC operation using a downlink ISAC reference signal in a wireless communication system according to one embodiment of the present disclosure.

[0348] Referring to FIG. 22, a terminal (2205), a base station (2210), an AMF (2215), and an SF (2220) can transmit and receive data to and from each other. The interface through which each entity communicates may be a service-based interface or a reference point-based interface as described in FIG. 2. The method by which the terminal (2205), the base station (2210), the AMF (2215), and the SF (2220) exchange messages with each other may be the same as described in FIGs. 8, 9, 10, 11, 12, 13, 14, and 15.

[0349] SF (2220) can select (2231) a terminal (2205) and a base station (2210) to perform an ISAC operation using a downlink ISAC reference signal, and the selection (2231) of the terminal (2205) and the base station (2210) may be the same as described in FIG. 20.

[0350] SF (2220) may transmit a Namf message (e.g., gNB-SF ISAC RS configuration request (2232)) to AMF (2215) to configure or request the base station (2210) to transmit downlink ISAC RS. The Namf message (2232) may include an identifier of the terminal to measure ISAC RS (e.g., UE correlation ID) and an identifier of the base station to transmit ISAC RS (e.g., gNB correlation ID). The gNB-SF ISAC RS configuration request (2232) may include at least one of the following information.

[0351] - RS transmission or interruption indicator

[0352] - TRP Identifier: SF can request RS transmission or interruption per TRP.

[0353] - Beam Identifier: SF can request RS transmission or interruption on a per-beam basis.

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

[0355] - RS on-demand information: Among the on-demand values ​​(e.g., RS type, frequency-scale pattern, time-scale pattern, etc.) that the base station responded to in the TRP info response, the SF may select a value appropriate for ISAC operation and instruct RS transmission. If one or more values ​​are requested, the base station may select an appropriate value.

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

[0357] - RS transmission start time

[0358] - RS transmission repetition count and repetition period

[0359] - ISAC Operation QoS: If the characteristics or QoS of an object requiring sensing (e.g., resolution of object size, accuracy of speed, accuracy of material, 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.

[0360] - Indicator requesting information of the RS currently being transmitted: The base station can respond to the SF (via AMF) with information of the RS currently being transmitted (e.g., RS type, frequency-scale pattern, time-scale pattern, etc.).

[0361] AMF (2215) can perform a network triggered service request (2233) procedure to perform an ISAC RS measurement operation in the CM CONNECTED state when the terminal (2205) is in the CM (connection management) IDLE state.

[0362] The AMF (2215) can transmit the gNB-SF ISAC RS configuration request included in the message (2232) transmitted by the SF (2220) to the base station (2210) via an NGAP message (2234). The NGAP message (2234) may include an identifier of the terminal (2205) to perform the ISAC operation and an identifier of the SF (2220) transmitting the gNB-SF PDU (e.g., SF routing ID).

[0363] The base station (2210) can transmit downlink ISAC RS information to the terminal (2205) via a broadcast (e.g., SIB) message or an RRC message (2235) (e.g., RRCReconfiguration). The downlink ISAC RS information may include at least one of the following.

[0364] - RS Identifier: An identifier that distinguishes different RS based on the type of RS (e.g., PRS, DMRS, CSI-RS, SSB).

[0365] - ISAC RS Indicator: Indicates whether the corresponding RS can be measured for ISAC purposes.

[0366] - ISAC RS Identifier: An identifier capable of distinguishing different RS types or RS measured for ISAC purposes within the entire RS system.

[0367] - RS settings: May include settings such as RS frequency bandwidth, RS pattern (frequency, time-repeating information), hopping pattern, TRP identifier, beam identifier, RS transmission start time (e.g., a specific SFN (subframe number), a specific slot, a specific symbol, or a specific time (absolute or relative time)), RS transmission period (e.g., in units of milliseconds to minutes), and the number of RS transmissions.

[0368] - RS transmission information: periodic (RS transmission every RS transmission cycle after setting), semi-persistent (periodical RS transmission starts via additional signals such as DCI or MAC CE after setting), aperiodic (RS transmission via additional signals such as DCI or MAC CE after setting)

[0369] The base station (2210) receives a request for RS transmission from the SF (2220) via an RS configuration request (2232), and if RS transmission for any RS identifier is successfully performed, it may send a Namf message (e.g., gNB-SF ISAC RS configuration response (2236)) to the AMF (2215) to respond with RS configuration information to the SF (2220). The gNB-SF ISAC RS configuration response (2236) may include an RS identifier for which RS transmission is successfully performed, and if the base station (2210) receives a request for RS transmission with one or more on-demand values, RS characteristics, or QoS, it may include information on the RS selected by the base station (2210) (e.g., RS type, frequency-scale pattern, time-scale pattern, etc.).

[0370] The AMF (2215) can transmit information or a message (e.g., gNB-SF PDU) contained in an NGAP message (2234) received from the base station (2210) to the SF (2220) via an Nsf message (2237). The Nsf message (2237) may include an identifier of the terminal (2205) measuring the ISAC RS (e.g., UE correlation ID), and an identifier of the base station (2210) transmitting the ISAC RS (e.g., gNB correlation ID).

[0371] SF (2220) can instruct the terminal (2205) to measure and report downlink ISAC RS via a UE-SF PDU (e.g., UE-SF measurement request) (2238).

[0372] For the measurement and reporting of downlink ISAC RS, the UE-SF PDU (2238) may include at least one of the following information.

[0373] - ISAC Measurement Report Identifier: Can direct different ISAC measurement reports.

[0374] - RS Identifier, ISAC RS Identifier: Can indicate the RS to be measured.

[0375] - Terminal report result level: This may indicate the level of ISAC sensing report that the terminal reports to the base station (e.g., raw data, intermediate result, sensing result). For the intermediate result, depending on the calculation level of the result, it may be, for example, 0 (highest) to 9 (lowest) or a predefined value.

[0376] - Event-based reporting conditions: The ISAC measurement reporting procedure may be performed if the reporting conditions are satisfied. The reporting conditions may include the following conditions, and one or more conditions may be used in combination.

[0377] * Response time: You can request that the base station receive the measurement report by a specific point in time.

[0378] * periodic: You can request that SF receive measurement reports at specific intervals.

[0379] * Target Object Availability: The terminal may notify the base station if an object detected in the measurement area enters or leaves the measurement area. The target object may be distinguishable by a combination of shape, size, speed, material, etc., or may be an object corresponding to a predefined value (e.g., a person or a car).

[0380] * Motion event: If the motion of an object detected in the measurement area satisfies the conditions, the terminal may notify the base station. The motion can be distinguished by a combination of the object's shape, position, direction, speed, etc., or it may be an object corresponding to a predefined value (e.g., clenching a fist, opening a fist, etc.).

[0381] - ISAC QoS: The QoS required for ISAC operation. QoS can include the time taken from receiving the ISAC RS to reporting the measurement result (response time) and the accuracy of the measurement result report.

[0382] - Measurement Trigger: The base station can instruct the terminal to take a measurement via DCI or MAC CE, and the terminal can measure and report the instructed ISAC RS.

[0383] When the base station (2210) instructs the terminal (2205) to take a measurement using a measurement trigger (e.g., DCI or MAC CE), it may transmit a signal (2239) containing information of the measurement target ISAC RS (e.g., RS identifier) ​​to the terminal. The base station (2210) may transmit semi-persistent or aperiodic signal transmission information to the terminal (2205) via DCI or MAC CE.

[0384] The terminal (2205) can measure the ISAC RS (2240) indicated by a periodic measurement or a measurement trigger.

[0385] The terminal (2205) can report ISAC measurement results by transmitting a UE-SF PDU (e.g., UE-SF ISAC measurement report) (2241) to the base station (2210). The UE-SF ISAC measurement report (2241) may include at least one of the following information.

[0386] - ISAC Measurement Report Identifier: May include a measurement report identifier.

[0387] - RS Identifier, ISAC RS Identifier: May include the identifier of the measured ISAC RS.

[0388] - Measurement result and terminal report result level: This may indicate the level of ISAC sensing report that the terminal reports to the base station (e.g., raw data, intermediate result, sensing result). In the case of an intermediate result, depending on the calculation level of the result, it may be, for example, 0 (highest) to 9 (lowest) or a predefined value.

[0389] FIG. 23 is a diagram illustrating an example of a signal flow in which an SF instructs a base station and a terminal to perform an ISAC operation using an uplink ISAC reference signal in a wireless communication system according to one embodiment of the present disclosure.

[0390] Referring to FIG. 23, a terminal (2305), a base station (2310), an AMF (2315), and an SF (2320) can transmit and receive data to and from each other. The interface through which each entity communicates may be a service-based interface or a reference point-based interface, as described in FIG. 2. The method by which the terminal (2305), the base station (2310), the AMF (2315), and the SF (2320) exchange messages with each other may be the same as described in FIGs. 8, 9, 10, 11, 12, 13, 14, and 15.

[0391] SF (2320) can select (2331) a terminal (2305) and a base station (2310) to perform an ISAC operation using an uplink ISAC reference signal, and the selection (2331) of the terminal (2305) and the base station (2310) may be as described in FIG. 20.

[0392] SF (2320) may transmit a measurement request message (e.g., gNB-SF ISAC measurement request) to the base station (2310) for ISAC RS settings, measurement settings, and reporting settings of the selected terminal (2305) and the base station (2310). At this time, SF (2320) may transmit the gNB-SF ISAC measurement request to the base station (2310), or SF (2320) may transmit the gNB-SF ISAC measurement request to the AMF (2315), and the AMF may refer to the contents of the message and transmit it to the base station (2310). The gNB-SF ISAC measurement request may be in the form of a gNB-SF PDU or may be part of a message (2332) transmitted by SF (2320) to the AMF (2315). The gNB-SF ISAC measurement request transmitted by SF (2320) to the AMF (2315) may include at least one of the following information.

[0393] - Terminal Identifier: The AMF can identify the terminal to perform the ISAC operation in the form of a UE correlation ID or SUPI, etc.

[0394] - Base Station Identifier: The AMF can identify the base station to perform ISAC operations in the form of a gNB correlation ID or gNB ID.

[0395] - RS configuration information: May include RS information required to perform ISAC operations.

[0396] Among the on-demand values ​​(e.g., RS type, frequency-scale pattern, time-scale pattern, etc.) that the base station responded to in the TRP info response, the SF may select a value appropriate for ISAC operation and instruct RS transmission. If the SF requests one or more values, the base station may select an appropriate value.

[0397] * RS characteristics: SF instructs the base station on RS characteristics (e.g., RS type, bandwidth, pattern, etc.), and the base station can instruct the terminal to transmit RS based on the requested characteristics.

[0398] * RS transmission start time: May include the start time of RS transmission or ISAC sensing.

[0399] * RS transmission repetition count and repetition period: May include the repetition count and repetition period of RS transmission or ISAC sensing.

[0400] * ISAC Operation QoS: If the characteristics or QoS of an object requiring sensing (e.g., resolution of object size, accuracy of speed, accuracy of material, 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.

[0401] - Base Station Report Result Level: This may indicate the level of ISAC sensing reports that the base station reports to the SF (e.g., raw data, intermediate result, sensing result). For the intermediate result, it may be, for example, 0 (highest) to 9 (lowest) or a predefined value, depending on the calculation level of the result. The SF may refer to the intermediate result level to calculate the intermediate result calculated by the base station as the final result.

[0402] - Event-based reporting conditions: The ISAC measurement reporting procedure may be performed if the reporting conditions specified by the SF are satisfied. Reporting conditions may include the following conditions, and one or more conditions may be used in combination.

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

[0404] * periodic: You can request that SF receive measurement reports at specific intervals.

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

[0406] * motion event: If the motion of an object detected in the measurement area satisfies the conditions, the base station may notify the SF. The motion can be distinguished by a combination of the object's shape, position, direction, speed, etc., or it may be an object corresponding to a predefined value (e.g., clenching a fist, opening a fist, etc.).

[0407] - ISAC QoS: The QoS required for ISAC operation. QoS can include the time taken from receiving the ISAC RS to reporting the measurement result (response time) and the accuracy of the measurement result report.

[0408] AMF (2315) can perform a network triggered service request (2333) procedure so that when the terminal (2305) is in a CM (connection management) IDLE state, the terminal (2305) can perform an ISAC RS transmission operation in a CM CONNECTED state.

[0409] The AMF (2315) can transmit the gNB-SF ISAC measurement request included in the message (2332) transmitted by the SF (2320) to the base station (2310) via an NGAP message (2334). The NGAP message (2334) may include an identifier of the terminal (2305) to perform the ISAC operation.

[0410] The base station (2310) can transmit uplink ISAC RS information to the terminal (2305) via an RRC message (2335) (e.g., RRCReconfiguration). The uplink ISAC RS information may include at least one of the following. It goes without saying that the uplink ISAC RS information may also be transmitted to the terminal via layer messages other than the RRC message.

[0411] - RS Identifier: An identifier that distinguishes different RSs based on their type (e.g., SRS, positioning SRS, DMRS).

[0412] - ISAC RS Identifier: An identifier capable of distinguishing different RS types or RS measured for ISAC purposes within the entire RS system.

[0413] - RS Settings: RS frequency bandwidth, RS pattern (frequency, time-repeating information), hopping pattern, TRP identifier, beam identifier, RS transmission start time (e.g., specific SFN (subframe number), specific slot, specific symbol, or specific time (absolute or relative time)), RS transmission period (e.g., in units of milliseconds to minutes), number of RS transmissions

[0414] - RS transmission information: periodic (RS transmission every RS transmission cycle after setting), semi-persistent (periodical RS transmission starts via additional signals such as DCI or MAC CE after setting), aperiodic (RS transmission via additional signals such as DCI or MAC CE after setting)

[0415] The base station (2310) can measure the uplink ISAC RS (2336) that instructed the terminal (2305) to transmit.

[0416] The base station (2310) may transmit a gNB-SF ISAC measurement report to the SF (2320) via the AMF (2315) to report the measurement results to the SF. The base station (2310) may transmit an NGAP message (2337) containing the gNB-SF ISAC measurement report to the AMF (2315). The gNB-SF ISAC measurement report may be included in the NGAP message (2337) in the form of a gNB-SF PDU, or it may be transmitted to the AMF (2315) and then transmitted by the AMF (2315) to the SF (2320) via a new message. The NGAP message (2337) may include an identifier (e.g., SF routing ID) of the SF (2320) to which the gNB-SF ISAC measurement report is transmitted.

[0417] The AMF (2315) can transmit a gNB-SF PDU containing a gNB-SF ISAC measurement report to the SF (2320) as an Nsf message (2338). The Nsf message (2338) may include an identifier of the terminal (2305) that transmitted the ISAC RS (e.g., UE correlation ID) and an identifier of the base station (2310) (e.g., gNB correlation ID).

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

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

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

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

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

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

Claims

1. A method performed by a base station of a wireless communication system, A step of receiving first information from a terminal regarding the capability of the terminal related to sensing; A step of transmitting the first information to a sensing function entity; A step of receiving second information related to the setting for the sensing from the above-mentioned sensing function entity; A step of transmitting to the terminal a third information related to the settings of the terminal for the sensing; A step of receiving a report on the sensing from the terminal; and A method comprising the step of transmitting the report to the sensing function entity.

2. In Paragraph 1, The first information above includes at least one of a measurement range, resources, delay time, accuracy, or the role of the terminal related to the sensing, in a method 3. In Paragraph 1, The method, wherein the second information comprises at least one of the type of signal, transmission period, or reporting criteria associated with the sensing.

4. In Paragraph 1, The above report is transmitted to the above sensing function entity via the AMF (access and mobility management function) entity, and A method in which the above third information is transmitted to the terminal based on RRC (radio resource control) signaling.

5. A method performed by a sensing function entity of a wireless communication system, A step of receiving first information from a base station regarding the terminal's capability related to sensing; A step of selecting the terminal for the sensing based on the first information above; A step of transmitting second information related to the settings for the sensing to the base station; A method comprising the step of receiving a report on the sensing from the base station.

6. In Paragraph 5, The above first information comprises at least one of a measurement range, resources, delay time, accuracy, or the role of the terminal related to the sensing, in a method.

7. In Paragraph 5, The method, wherein the second information comprises at least one of the type of signal, transmission period, or reporting criteria associated with the sensing.

8. In Paragraph 5, A method in which a report on the above sensing is received via an AMF (access and mobility management function) entity.

9. Regarding base stations: At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the base station: From the terminal, receiving first information regarding the capability of the terminal related to sensing, and Transmit the first information to the sensing function entity, and From the above sensing function entity, receive second information related to the settings for the sensing, and Transmitting third information related to the settings of the terminal for the sensing to the terminal, and From the above terminal, a report regarding the sensing is received, and A base station that causes the above-mentioned sensing function entity to transmit the above-mentioned report.

10. In Paragraph 9, The above first information comprises at least one of the measurement range, resources, latency, accuracy, or the role of the terminal associated with the sensing, a base station.

11. In Paragraph 9, The above second information comprises at least one of the type of signal, transmission period, or reporting criteria associated with the sensing, of a base station.

12. In Paragraph 9, A report on the above sensing is transmitted to the above sensing function entity via the AMF (access and mobility management function) entity, and The above third information is a base station that transmits to the terminal based on RRC (radio resource control) signaling.

13. Regarding the sensing function entity: At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the at least one processor, so that the sensing function entity: Receive first information regarding the terminal's capability related to sensing from a base station, and Based on the first information above, select the terminal for the sensing, and Transmit second information related to the settings for the sensing to the above base station, and A sensing function entity that receives a report on the sensing from the base station.

14. In Paragraph 13, The first information above is a sensing function entity comprising at least one of a measurement range, resources, latency, accuracy, or the role of the terminal related to the sensing.

15. In Paragraph 13, The second information above includes at least one of the type of signal, transmission period, or reporting criteria related to the sensing, and A sensing function entity that receives a report on the above sensing via an access and mobility management function (AMF) entity.

Images