Handover method based on base station sensing, and device for supporting same

Abstract

A method for performing communication and a device for supporting same are provided. The method may comprise steps in which a first device: acquires a sensing signal; acquires, on the basis of the sensing signal, a sensing result based on a line of sight (LOS) related to a second device; and determines, on the basis of the sensing result based on the LOS related to the second device, whether handover of the second device is to be performed.

Description

Base station sensing-based handover method and device supporting the same

[0001] The present disclosure relates to a method and apparatus for communication. More specifically, the present disclosure may relate to a base station sensing-based handover method and an apparatus supporting the same.

[0002] 5G NR is a successor technology to LTE (long term evolution) and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, ranging from low frequency bands below 1 GHz to mid-frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0003] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy requirements such as those shown in Table 1 below. For example, Table 1 may represent an example of the requirements for a 6G system.

[0004] Maximum data rate per device 1 Tbps E2E latency 1 ms Maximum spectral efficiency 100 bps / Hz Mobility support up to 1000 km / hr Satellite integration Fully AI Fully autonomous driving Fully XR Fully haptic communication Fully

[0005] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: a step in which a first device acquires a sensing signal; a step in which, based on the sensing signal, the first device acquires a sensing result based on a line of sight (LOS) associated with a second device; and a step in which, based on the sensing result based on the LOS associated with the second device, the first device determines whether to perform a handover of the second device.

[0006] According to one embodiment of the present disclosure, a first device may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the first device, based on execution by the at least one processor: to acquire a sensing signal; to acquire a sensing result based on a line of sight (LOS) associated with a second device based on the sensing signal; and to determine whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

[0007] According to one embodiment of the present disclosure, a processing device (configured to control a first device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the first device, based on execution by the at least one processor: to acquire a sensing signal; to acquire a sensing result based on a line of sight (LOS) associated with a second device based on the sensing signal; and to determine whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

[0008] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the first device may: acquire a sensing signal; acquire a sensing result based on a line of sight (LOS) associated with a second device based on the sensing signal; and determine whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

[0009] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include the step of a second device receiving a radio resource control (RRC) reset message from a first device; and the step of the second device performing a handover based on the RRC reset message. For example, the RRC reset message may include information related to the handover of the second device. For example, the information related to the handover of the second device may be based on a sensing result based on a line of sight (LOS) related to the second device.

[0010] According to one embodiment of the present disclosure, a second device may be provided. For example, the second device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the second device to: receive a radio resource control (RRC) reset message from the first device; and perform a handover based on the RRC reset message, based on execution by the at least one processor. For example, the RRC reset message may include information related to the handover of the second device. For example, the information related to the handover of the second device may be based on a sensing result based on a line of sight (LOS) related to the second device.

[0011] According to one embodiment of the present disclosure, a processing device (configured to control a second device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the second device to: receive a radio resource control (RRC) reset message from the first device based on execution by the at least one processor; and perform a handover based on the RRC reset message. For example, the RRC reset message may include information related to the handover of the second device. For example, the information related to the handover of the second device may be based on a sensing result based on a line of sight (LOS) related to the second device.

[0012] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the second device may: receive a radio resource control (RRC) reset message from the first device; and perform a handover based on the RRC reset message. For example, the RRC reset message may include information related to the handover of the second device. For example, the information related to the handover of the second device may be based on a sensing result based on a line of sight (LOS) related to the second device.

[0013] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure.

[0014] FIG. 2 shows a radio protocol architecture according to one embodiment of the present disclosure.

[0015] FIG. 3 shows the structure of a wireless frame according to one embodiment of the present disclosure.

[0016] FIG. 4 shows a slot structure of a frame according to one embodiment of the present disclosure.

[0017] FIG. 5 shows an example of a BWP according to one embodiment of the present disclosure.

[0018] FIG. 6 shows a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0019] FIG. 7 illustrates an example of a communication scenario based on a 6G system according to an embodiment of the present disclosure.

[0020] FIG. 8 shows an example of a sensing operation according to one embodiment of the present disclosure.

[0021] FIG. 9 shows the relationship between RCS, distance (D), and power according to one embodiment of the present disclosure.

[0022] FIG. 10 shows an example of a protocol layer used to support the transmission of an LPP (LTE positioning protocol) message between a LMF (location management function) and a UE according to one embodiment of the present disclosure.

[0023] FIG. 11 shows an example of an ISAC service according to one embodiment of the present disclosure.

[0024] FIG. 12 illustrates various integrated sensing and communication (ISAC) systems according to one embodiment of the present disclosure.

[0025] FIG. 13 shows an example of six sensing scenarios for a sensing service according to one embodiment of the present disclosure.

[0026] FIG. 14 shows a functional framework for AI / ML (artificial intelligence and machine learning) according to one embodiment of the present disclosure.

[0027] FIG. 15 shows an example of a handover procedure between gNBs according to one embodiment of the present disclosure.

[0028] FIG. 16 shows an example of an intra-AMF / UPF handover procedure according to one embodiment of the present disclosure.

[0029] FIG. 17 illustrates an example of an intra-AMF / UPF handover procedure according to one embodiment of the present disclosure.

[0030] FIG. 18 shows an example of an intra-AMF / UPF handover procedure according to one embodiment of the present disclosure.

[0031] FIG. 19 illustrates an example of a measurement report-based handover procedure according to one embodiment of the present disclosure.

[0032] FIG. 20 illustrates an example of a procedure related to a handover delay caused by a failure to transmit a measurement report, according to one embodiment of the present disclosure.

[0033] FIG. 21 shows an example of LOS path loss due to UE movement according to one embodiment of the present disclosure.

[0034] FIG. 22 illustrates an example of a procedure related to a BS sensing-based handover without UE measurement and measurement report transmission, according to one embodiment of the present disclosure.

[0035] FIG. 23 illustrates an example of a BS monostatic sensing-based handover procedure according to one embodiment of the present disclosure.

[0036] FIG. 24 illustrates an example of a UE-BS bistatic sensing-based handover procedure according to one embodiment of the present disclosure.

[0037] FIG. 25 illustrates an example of a BS monostatic sensing-based handover procedure according to one embodiment of the present disclosure.

[0038] FIG. 26 illustrates an example of a BS monostatic sensing-based handover procedure according to one embodiment of the present disclosure.

[0039] FIG. 27 illustrates a procedure performed by a first device according to one embodiment of the present disclosure.

[0040] FIG. 28 illustrates a procedure performed by a second device according to one embodiment of the present disclosure.

[0041] FIG. 29 shows a communication system (1) according to one embodiment of the present disclosure.

[0042] FIG. 30 shows a wireless device according to one embodiment of the present disclosure.

[0043] FIG. 31 shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0044] FIG. 32 shows a wireless device according to one embodiment of the present disclosure.

[0045] FIG. 33 shows a portable device according to one embodiment of the present disclosure.

[0046] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0047] A slash ( / ) or a comma used in the present disclosure may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0048] In the present disclosure, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in the present disclosure, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0049] Additionally, in the present disclosure, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Additionally, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0050] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, the "control information" of the present disclosure is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (e.g., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0051] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0052] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.

[0053] In the present disclosure, a higher layer parameter may be a parameter that is set for the terminal, pre-set, or pre-defined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0054] In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from a base station or network (e.g., SIB, MAC, RRC, DCI (downlink control information), etc.). In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from another device (e.g., MAC, RRC, SCI (sidelink control information), control information signaled between devices, etc.). In the present disclosure, "configured or defined" may be interpreted as being pre-configured to a device.

[0055] In the present disclosure, user equipment (UE) may refer to a device, a portable device, a wireless device, etc. In the present disclosure, a base station (BS) may refer to a radio access network (RAN) node, a non-terrestrial network (NTN) cell / node, a transmission reception point (TRP), a network, an integrated access and backhaul (IAB) node, a device, a portable device, a wireless device, etc.

[0056] The technology proposed in this disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0057] The technology proposed in this disclosure can be implemented as 6G wireless technology and can be applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0058] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0059] Referring to FIG. 1, in step S101, the first device and the second device can perform synchronization. For example, the first device may be a terminal and / or at least one of the devices proposed in the present disclosure. For example, the second device may be a base station, a network, a RAN node, an NTN node / cell, a TRP, a terminal and / or at least one of the devices proposed in the present disclosure. For example, the first device may perform an initial cell search operation. For example, the first device may detect at least one synchronization signal transmitted according to a rule predefined by the second device. Here, for example, the synchronization signal may include a plurality of synchronization signals (e.g., primary synchronization signal, secondary synchronization signal, etc.) classified according to structure or use. Through this, the first device can identify the boundaries of the frame, subframe, time unit, slot, and / or symbol of the second device, and the first device can obtain information about the second device (e.g., cell identifier).

[0060] In step S103, the first device may obtain system information transmitted by the second device. For example, the system information may include information related to the attributes, characteristics, and / or capabilities of the second device that are necessary to connect to the second device and use the service. For example, the system information may be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., the channel used, whether it is provided on-demand), etc. For example, the system information may be classified into a master information block (MIB) and a system information block (SIB). For example, if necessary, the first device may transmit a signal requesting the system information prior to receiving the system information. For example, the request and provision of the system information may be performed after a random access procedure described later.

[0061] In step S105, the first device and the second device may perform a random access procedure. For example, the first device may transmit and / or receive at least one message for the random access procedure (e.g., random access preamble, random access response message, etc.) based on information related to the random access channel of the second device obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the first device may transmit a preamble (e.g., Msg1) through the random access channel, and the first device may receive a random access response message (e.g., Msg2). The first device may transmit a message (e.g., Msg3) containing information related to the first device (e.g., identification information) to the second device using scheduling information included in the random access response message, and the first device may receive a message (e.g., Msg4) for contention resolution and / or connection establishment. For example, Msg1 and Msg3 can be transmitted and received as a single message (e.g., MsgA), and / or Msg2 and Msg4 can be transmitted and received as a single message (e.g., MsgB).

[0062] In step S107, the first device and the second device may perform signaling of control information. Here, for example, the control information may be defined in various layers, such as a layer controlling the connection (e.g., a radio resource control (RRC) layer), a layer handling mapping between a logical channel and a transmission channel (e.g., a media access control (MAC) layer), and a layer handling a physical channel (e.g., a physical (PHY) layer). For example, the first device and the second device may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and / or signaling to indicate allocated resources. For example, the control information may be signaled / transmitted through a control channel. For example, the control information and / or the control channel may be used to schedule at least one of data, a data channel (e.g., a shared channel), and / or control information on the data channel.

[0063] In step S109, the first device and the second device may transmit and / or receive data. For example, the first device and the second device may process data based on signaling of control information and transmit and / or receive it. For example, when transmitting data, the first device or the second device may perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and / or resource mapping on the information bits. For example, when receiving data, the first device or the second device may perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and / or channel decoding.

[0064] For example, the layers of the radio interface protocol between the first device and the second device can be classified into L1 (layer 1), L2 (layer 2), L3 (layer 3), etc. For example, the physical layer belonging to layer 1 can provide an information transfer service using a physical channel, and the radio resource control (RRC) layer located at layer 3 can perform the role of controlling radio resources between the first device and the second device. For example, to this end, the RRC layer can exchange RRC messages between the first device and the second device.

[0065] FIG. 2 illustrates a radio protocol architecture according to one embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted. For example, FIG. 2(a) may represent a radio protocol stack in the user plane for uplink communication or downlink communication, and FIG. 2(b) may represent a radio protocol stack in the control plane for uplink communication or downlink communication. For example, FIG. 2(c) may represent a radio protocol stack in the user plane for device-to-device communication, and FIG. 2(d) may represent a radio protocol stack in the control plane for device-to-device communication.

[0066] For example, the physical layer can provide information transmission services to upper layers using a physical channel. For example, the physical layer can be connected to the upper layer, the MAC (medium access control) layer, through a transport channel. For example, data can be transmitted between the MAC layer and the physical layer through a transport channel. For example, transport channels can be classified according to how and with what characteristics data is transmitted through a wireless interface. For example, data can be transmitted through a physical channel between different physical layers, for example, between the physical layers of a first device and a second device. For example, the physical channel can be modulated using the OFDM (orthogonal frequency division multiplexing) method, and time and frequency can be utilized as wireless resources.

[0067] For example, the MAC layer can provide services to the upper layer, the RLC (radio link control) layer, through logical channels. For example, the MAC layer can provide mapping functions from multiple logical channels to multiple transmission channels. For example, the MAC layer can provide logical channel multiplexing functions through mapping from multiple logical channels to a single transmission channel. For example, the MAC sublayer can provide data transmission services over logical channels.

[0068] For example, the RLC layer can perform concatenation, segmentation, and reassembly of RLC service data units (SDUs). For example, to guarantee various quality of service (QoS) required by a radio bearer (RB), the RLC layer can provide three modes of operation: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). For example, AM RLC can provide error correction through automatic repeat requests (ARQ).

[0069] For example, the RRC (radio resource control) layer may be defined only in the control plane. For example, the RRC layer may be responsible for controlling logical channels, transmission channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers. For example, RB may refer to a logical path provided by the first layer (e.g., physical layer) and the second layer (e.g., MAC layer, RLC layer, PDCP (packet data convergence protocol) layer, SDAP (service data adaptation protocol) layer, etc.) for data transfer between a first device and a second device.

[0070] For example, the functions of the PDCP layer in the user plane may include the delivery of user data, header compression, and ciphering. For example, the functions of the PDCP layer in the control plane may include the delivery of control plane data and encryption / integrity protection.

[0071] For example, the establishment of an RB can mean the process of defining the characteristics of the wireless protocol layer and channel to provide specific services, and setting each specific parameter and method of operation. For example, an RB can be divided into two types: an SRB (signaling radio bearer) and a DRB (data radio bearer). For example, an SRB can be used as a channel to transmit RRC messages in the control plane, and a DRB can be used as a channel to transmit user data in the user plane.

[0072] For example, if an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state, and if not, it may be in the RRC_IDLE state. For example, in the case of NR, an additional RRC_INACTIVE state is defined, and a terminal in the RRC_INACTIVE state maintains a connection with the core network while releasing the connection with the base station.

[0073] For example, a downlink transmission channel may include at least one of a broadcast channel (BCH) that transmits system information and / or a shared channel (SCH) that transmits user traffic or control messages. For example, traffic or control messages for a downlink multicast or broadcast service may be transmitted via a downlink SCH or via a separate multicast channel (MCH). Meanwhile, an uplink transmission channel may include at least one of a random access channel (RACH) that transmits initial control messages and / or a shared channel (SCH) that transmits user traffic or control messages. For example, a logical channel located above the transmission channel and mapped to the transmission channel may include at least one of a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and / or a multicast traffic channel (MTCH).

[0074] FIG. 3 shows the structure of a wireless frame according to one embodiment of the present disclosure. The embodiment of FIG. 3 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0075] Referring to FIG. 3, radio frames may be used, for example, in uplink transmission, downlink transmission, and / or device-to-device transmission. For example, a radio frame may have a length of 10 ms and may be defined as two 5 ms half-frames (HF). For example, a half-frame may contain five 1 ms subframes (SF). For example, a subframe may be divided into one or more slots, and the number of slots within a subframe may be determined by subcarrier spacing (SCS). For example, each slot may contain 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).

[0076] For example, when normal CP is used, each slot may contain 14 symbols. For example, when extended CP is used, each slot may contain 12 symbols. Here, for example, the symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA (single carrier-FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0077] Table 2 below shows the number of symbols per slot (N) according to the SCS setting (u) when Normal CP or Extended CP is used. slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) exemplifies.

[0078] CP Type SCS (15*2 u )N slot symb N frame,u slot N subframe,u slotNormal CP 15kHz (u=0) 1410 130kHz (u=1) 1420 260kHz (u=2) 1440 4120kHz (u=3) 1480 8240kHz (u=4) 14160 16 Extended CP 60kHz (u=2) 1240 4

[0079] For example, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be configured differently among multiple cells merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI (transmit time interval)) composed of the same number of symbols may be configured differently among the merged cells. For example, in the present disclosure, time resources such as subframes, slots, TTI, etc. may be referred to as time units.

[0080] For example, multiple numerologies or SCSs may be supported to support various services. For example, if the SCS is 15 kHz, a wide area in traditional cellular bands may be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth may be supported. For example, if the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.

[0081] FIG. 4 shows a slot structure of a frame according to one embodiment of the present disclosure. The embodiment of FIG. 4 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0082] Referring to FIG. 4, for example, a slot may include multiple symbols in the time domain. For example, a carrier may include multiple subcarriers in the frequency domain. For example, a resource block (RB) may be defined as multiple consecutive subcarriers in the frequency domain. For example, a bandwidth part (BWP) may be defined as multiple consecutive (P)RBs ((physical) resource blocks) in the frequency domain and may correspond to a single numerology (e.g., SCS, CP length, etc.). For example, a carrier may include up to N BWPs (where N is a positive integer). For example, data communication may be performed through an active BWP. For example, each element may be referred to as a resource element (RE) in a resource grid and may be mapped to a single complex symbol.

[0083] For example, a BWP can be a continuous set of PRBs in a given numerology. For example, a PRB can be selected from a continuous subset of common resource blocks (CRBs) for a given numerology on a given carrier.

[0084] For example, the BWP may be at least one of an active BWP, an initial BWP, and / or a default BWP. For example, the terminal may not monitor downlink radio link quality on DL BWPs other than the active DL BWP on the PCell (primary cell). For example, the terminal may not receive PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), or CSI-RS (channel state information-reference signal) (except for RRM (radio resource management)) outside of the active DL BWP. For example, the terminal may not trigger CSI (channel state information) reporting for an inactive DL BWP. For example, the terminal may not transmit PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel) outside of the active UL (uplink) BWP. For example, for the downlink, the initial BWP can be given as a consecutive set of resource blocks (RBs) for the remaining minimum system information (RMSI) CORESET (control resource set) (set by the physical broadcast channel (PBCH)). For example, for the uplink, the initial BWP can be given by the system information block (SIB) for the random access procedure. For example, the default BWP can be set by the upper layer. For example, the initial value of the default BWP can be the initial DL BWP.For energy saving, if the terminal fails to detect DCI (downlink control information) for a certain period, the terminal can switch the active BWP of the terminal to the default BWP.

[0085] FIG. 5 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. In the embodiment of FIG. 5, it is assumed that there are three BWPs.

[0086] Referring to FIG. 5, for example, a common resource block (CRB) may be a numbered carrier resource block from one end of the carrier band to the other, and a PRB may be a numbered resource block within each BWP. For example, point A may indicate a common reference point for the resource block grid.

[0087] For example, BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP It can be set by ). For example, point A may be an external reference point of the PRB of a carrier where the subcarrier 0 of all numerologies (e.g., all numerologies supported by the network in that carrier) are aligned. For example, offset may be the PRB interval between the lowest subcarrier in a given numerology and point A. For example, bandwidth may be the number of PRBs in a given numerology.

[0088] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.

[0089] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, free space optical transmission (FSO) backhaul networks, massive MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0090] - Artificial Intelligence: Introducing AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. For example, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0091] - THz Communication: Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz-300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz-3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz-3 THz band is part of the optical band, it lies at the boundary of the optical band and immediately following the RF band. Therefore, this 300 GHz-3 THz band exhibits similarities to RF. Key characteristics of THz communication include (i) widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array technologies that can overcome range limitations.

[0092] - Large-scale MIMO technology

[0093] - Hologram beamforming (HBF)

[0094] - Optical wireless technology

[0095] - Free Space Optical Transmission Backhaul Network (FSO backhaul network)

[0096] - Quantum communication

[0097] - Cell-free communication

[0098] - Integration of wireless information and power transmission

[0099] - Integration of wireless communication and sensing

[0100] - Integrated access and backhaul network

[0101] - Big data analysis

[0102] - Reconfigurable intelligent metasurface

[0103] - Metaverse

[0104] - blockchain

[0105] - Advanced Air Mobility (AAM): AAM can be a broad concept encompassing Urban Air Mobility (UAM), Regional Air Mobility (RAM), and Unmanned Aerial Systems (UAS). For example, AAM may include UAM, RAM, UAS, UAVs (unmanned aerial vehicles), etc.

[0106] - Autonomous driving (self-driving): V2X (vehicle to everything), a core element of building autonomous driving infrastructure, refers to technologies that enable vehicles to communicate and share with various elements on the road to perform autonomous driving, such as wireless communication between vehicles (vehicle to vehicle, V2V) and between vehicles and infrastructure (vehicle to infrastructure, V2I).

[0107] - Non-terrestrial Network (NTN): An NTN may refer to a network or network segment that utilizes RF (radio frequency) resources mounted on a satellite (or UAS platform). The use of NTN services may be considered to secure wider coverage or to provide wireless communication services in locations where the installation of wireless communication base stations is difficult.

[0108] - Integrated Sensing and Communication (ISAC): Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc., of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment.

[0109] - Reconfigurable Intelligent Surface (RIS): An RIS can be used to manipulate and enhance signal propagation in a wireless communication environment. For example, an RIS can be composed of many small antennas or metasurfaces arranged on a surface, each of which can actively control the phase, amplitude, polarization, etc., of the reflected signal. For instance, an RIS can improve signal reception by controlling the path, phase, and / or strength of the propagating signal. For instance, power consumption can be very low because power is consumed only for controlling the phase and amplitude of the small antennas. For instance, since an RIS can be reconfigured to suit various environments, it can meet diverse communication requirements and operate effectively in dynamic network environments.

[0110] FIG. 7 illustrates an example of a communication scenario based on a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0111] Referring to FIG. 7, NTN communication can be performed based on a satellite network, HIBS (high-altitude platform stations (HAPS) as international mobile telecommunications (IMT) base stations (BS)), and an aeronautical communication-capable terminal (e.g., AAM). For example, to improve coverage, devices such as a satellite network, HIBS, and an aeronautical communication-capable terminal (e.g., AAM) can act as relays. For example, an AAM can communicate with a base station, a satellite network, etc., and / or an AAM can communicate directly with a terminal, another AAM, etc.

[0112] For example, a terminal can obtain information about the characteristics of the environment and / or objects within the environment by using radio frequency sensing to determine the instantaneous linear velocity, angle, distance (range), etc. of an object. Since radio frequency sensing capabilities do not require connecting to an object via a device within the network, they can provide services for object location determination without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Radio sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, radio sensing may use non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, e.g., sensing operation, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks into wireless communication and sensing networks.

[0113] FIG. 8 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted. Specifically, FIG. 8 (a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 8 (b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

[0114] Referring to FIG. 8, a sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or the environment surrounding the objects). For example, the sensing signal may be a radio (frequency) signal defined to be transmittable by a base station / terminal. For example, a sensing receiver may receive a signal that is scattered or reflected by one or more objects (and / or the environment surrounding the objects) from the sensing signal transmitted by the sensing transmitter. For example, at the sensing receiver, sensing data may be derived from the scattered or reflected signal, and a sensing result may be generated or obtained through processing of the sensing data. Here, for example, the sensing result may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment surrounding the objects). For example, the sensing results generated / acquired in this way may be utilized for wireless sensing services (e.g., detection, tracking of objects and / or environments, etc.) or provided / disclosed to a trusted third party.

[0115] For example, a sensing transmitter may be a base station or terminal that transmits a sensing signal to be used for the operation of a sensing service, and the sensing transmitter may be located at the same base station or terminal as the sensing receiver or at a different base station or terminal. For example, a sensing receiver may be a base station or terminal that receives a sensing signal to be used for the operation of a sensing service, and the sensing receiver may be located at the same base station or terminal as the sensing transmitter or at a different base station or terminal. For example, a sensing target may be an object to be detected by deriving the characteristics of an object within the environment from the sensing signal. For example, a background environment may be a background that is not a sensing target (e.g., clutter, environmental objects, etc.). For example, an environment object may be an object whose location is known other than that of a sensing target. For example, monostatic sensing may be a sensing in which the sensing transmitter and the sensing receiver coexist at the same base station or terminal. For example, bistatic sensing may be sensing where the sensing transmitter and the sensing receiver are located at different base stations or terminals. For example, multistatic sensing may be sensing where there are multiple sensing transmitters and / or multiple sensing receivers for a (single) sensing target. For example, monostatic sensing, bistatic sensing, and / or multistatic sensing may be distinguished based on the angle between the sensing transmitter, the sensing target, and the sensing receiver. For example, if the angle between the sensing transmitter, the sensing target, and the sensing receiver is below or equal to a threshold, it may be defined as monostatic sensing or semi-monostatic sensing. For example, if the angle between the sensing transmitter, the sensing target, and the sensing receiver is above or equal to a threshold, it may be defined as bistatic sensing or multistatic sensing.For example, the terminal can transmit a sensing signal over a wireless interface that can be used for sensing purposes. For example, the terminal can transmit a sensing signal over a 3GPP wireless interface that can be used for sensing purposes.

[0116] For example, the common framework of the ISAC channel model can be composed of components of the target channel and components of the background channel. For example, this can be obtained based on Equation 1.

[0117]

[0118] Here, for example, target channel H target It may include all [multipath] components affected by the sensing target. For example, background channel H Background It may include other [multipath] components that do not belong to the target channel.

[0119] For example, radar cross-section (RCS) may be a measure of how well a radar sensor can detect a target. Therefore, it can often be referred to as an electromagnetic characteristic of the target. For example, a larger RCS may indicate that the target can be detected more easily. For example, in radar sensor measurements, power may be transmitted toward the target, and the target may reflect some of the power back to the receiver. For example, received power may be based on the target's RCS, among other factors. For example, received power may be proportional to the RCS. For example, the target's RCS may be based on at least one of the frequency of the radar signal, the target material, the target shape, the target size, the direction of the incident and reflected waves relative to the target, the target movement, and / or the target illumination.

[0120] FIG. 9 illustrates the relationship between RCS, distance (D), and power according to one embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0121] Referring to Fig. 9, the RCS of a radar target may be a virtual area required to intercept the power density transmitted from the target. For example, the relevant radar equation can be defined as Equation 2.

[0122]

[0123] Here, for example, P TX can be transmitter power [W], and G TXε₀ can be the gain of the transmitting antenna [dimensionless], D can be the distance between the EUT (equipment under test) and the target [m], and RCS is the radar cross-section [m² 2 ] could be, and P RX can be the power [W] that the EUTT receives back from the object, and A eff is the effective area of ​​the receiving antenna [m 2 ] can be. For example, A eff It can be obtained based on mathematical formula 3.

[0124]

[0125] Here, for example, G RX λ can be the gain of the receiving antenna [dimensionless], λ can be the wavelength of the radio signal [m], λ = c / f, c can be the speed of light 299792458 [m / s], and f can be the frequency [Hz].

[0126] For example, if a transmitter and a receiver are placed together and the same antenna is used for transmission and reception (G TX = G RX = G), the related radar mathematical formula can be defined as Equation 4.

[0127]

[0128] Here, for example, P TX ε₀ can be transmitter power [W], G can be the gain of the transmitting antenna [dimensionless], D can be the distance between the EUT (equipment under test) and the target [m], and RCS is the radar cross-section [m² 2 ] could be, and P RX ≠ Power [W] received back from the object by the EUT.

[0129] FIG. 10 illustrates an example of a protocol layer used to support the transmission of LTE positioning protocol (LPP) messages between a location management function (LMF) and a UE, according to one embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.

[0130] LPP PDUs can be transmitted via NAS (non-access stratum) PDUs between the AMF (access and mobility management function) and the UE. Referring to FIG. 10, LPP can terminate between a target device (e.g., a UE in the control plane or a SET (SUPL (secure user plane location) enabled terminal)) in the user plane and a location server (e.g., an LMF in the control plane or an SLP (SUPL (secure user plane location) location platform)) in the user plane. LPP messages can be transmitted in the form of transparent PDUs through intermediate network interfaces using appropriate protocols, such as NGAP (NG application protocol) through the NG-C (NG-control plane) interface, and NAS / RRC through LTE-Uu and NR-Uu interfaces. The LPP protocol enables positioning for NR and LTE using various positioning methods.

[0131] For example, the target device and the location server can exchange capability information, auxiliary data for positioning, and / or location information through the LPP protocol. For example, error information exchange and / or instructions to stop the LPP procedure can be performed through LPP messages.

[0132] Conventionally, NR positioning up to Release 17 only supported network-based Uu positioning, which performed location search based on a connection between the target UE and the network (gNB / LMF). Meanwhile, starting with NR Release 18, sidelink positioning (SL positioning) using sidelink communication can be supported. Sidelink positioning is a new method that allows positioning operations to be performed by exchanging positioning reference signals through direct connections with anchor UEs surrounding the target UE, rather than with base stations. Positioning operations at the physical layer can be performed by determining the location through the transmission and measurement of the SL PRS (sidelink positioning reference signal) between the target UE and the anchor UE.

[0133] Uu positioning may use the LPP protocol. An LPP session can be a point-to-point communication protocol between a target UE and an LMF. Through the LPP protocol, the target UE can receive information necessary for positioning from the LMF. The LMF can establish the target UE and the base station (gNB) respectively, exchange positioning-related messages, and perform positioning operations through the LPP protocol and the NRPPa protocol. Meanwhile, in Release 18's sidelink positioning, positioning operations can be performed by exchanging sidelink positioning protocol messages with the target UE, server UE (or LMF), and anchor UE. In sidelink positioning, the sidelink positioning protocol (SLPP) can be used for establishing and exchanging messages between UEs.

[0134] Positioning methods (e.g., sidelink positioning) have the disadvantage that the target must possess a communication terminal and that signaling messages for location measurement must be exchanged between the transmitter and the target. This leads to increased overhead for signal processing between the target and the transmitter, and presents a fundamental limitation in that positioning itself is impossible if the target does not possess a separate communication terminal.

[0135] In contrast, the Integrated Sensing and Communication (ISAC) method can accurately detect the presence and movement of a target regardless of whether the target is carrying a communication terminal, and furthermore, can reliably acquire detailed sensing information such as the target's distance, speed, and angle. The ISAC method can estimate the characteristics of a target simply by analyzing the information reflected from the target after the signal radiated by the transmitter, without requiring a separate response signal or message from the target. Accordingly, ISAC has the advantage of significantly reducing the amount of signaling compared to positioning methods, thereby drastically lowering overhead, and simultaneously supporting more efficient and flexible sensing and communication operations.

[0136] FIG. 11 illustrates an example of an ISAC service according to one embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0137] Referring to FIG. 11, examples of various application fields to which ISAC can be applied are illustrated. Specifically, ISAC can support predictive maintenance and employee localization and authorization in the fields of smart manufacturing and industrial IoT, and can provide weather prediction, pollution monitoring, rain monitoring, and insect monitoring in the field of environmental monitoring.

[0138] In addition, in the field of Sensing as a Service, it can be utilized for drone monitoring and management, mobile crowd sensing, channel knowledge map construction, and cooperative localization and imaging.

[0139] Furthermore, in the field of remote sensing, it can support satellite imaging and broadcasting and drone swarm SAR imaging, and in the field of smart home, it can be utilized for human proximity detection, spatial-aware control, sensing-aided wireless charging, fall detection, vital signal monitoring, etc.

[0140] In addition, in the field of human-computer interaction (HCI), it enables gesture recognition, keystroke recognition, and arm / head activity recognition, and in the field of vehicle-to-everything communication (V2X), it enables the provision of various services such as high precision location, vehicle platooning, extended sensor, simultaneous localization and mapping, and secure hand-free access.

[0141] Recently, Integrated Sensing and Communication (ISAC) technology, which integrates target sensing and user communication functions in 6th generation (6G) mobile communication systems, is attracting attention as a key standardization target. Based on advantages such as efficient frequency usage, reuse of existing communication infrastructure, and cost savings from integrated sensing and communication sensors, ISAC technology is emerging as an essential technology in various industries such as autonomous driving, smart factories, unmanned aerial vehicles, and healthcare, as shown in Fig. 11.

[0142] For example, a support scenario for sensing services in an ISAC could be as follows. Here, for example, the network could be a gNB.

[0143] FIG. 12 illustrates various integrated sensing and communication (ISAC) systems according to an embodiment of the present disclosure. Specifically, FIG. 12(a) illustrates an example of a network-based monostatic ISAC system, FIG. 12(b) illustrates an example of a network-based bistatic ISAC system, and FIG. 12(c) illustrates an example of a network-UE-based bistatic ISAC system (①) and a network-coordinated UE bistatic ISAC system (①+②). Additionally, FIG. 12(d) illustrates an example of a terminal-based (UE-based) monostatic ISAC system, FIG. 12(e) illustrates an example of a terminal-network (UE-network) bistatic ISAC system, and FIG. 12(f) illustrates an example of a terminal-based (UE-based) bistatic ISAC system. For example, the network may be a TRP. For example, the network may be a base station. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0144] FIG. 13 illustrates an example of six sensing scenarios for a sensing service according to an embodiment of the present disclosure. Specifically, FIG. 13(a) illustrates an example of gNB monostatic, FIG. 13(b) illustrates an example of gNB bistatic, and FIG. 13(c) illustrates an example of gNB-UE bistatic. Additionally, FIG. 13(d) illustrates an example of UE-gNB bistatic, FIG. 13(e) illustrates an example of UE monostatic, and FIG. 13(f) illustrates an example of UE bistatic. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0145] Referring to Figures 12 and 13, for example, six sensing scenarios for a sensing service in an ISAC may be as follows.

[0146] For example, six principal sensing modes:

[0147] - gNB monostatic (the same gNB performs both the transmitter (Tx) and receiver (Rx)

[0148] - gNB bi-static (one gNB is the transmitter (Tx) and the other gNB is the receiver (Rx)

[0149] - gNB-to-UE bi-static (gNB is the transmitter (Tx) and UE is the receiver (Rx)

[0150] - UE-to-gNB bi-static (UE is the transmitter (Tx) and gNB is the receiver (Rx)

[0151] - UE Monostatic (The same UE performs both the transmitter (Tx) and receiver (Rx)

[0152] - UE bi-static (One UE is the transmitter (Tx) and the other UE is the receiver (Rx)

[0153] Referring to FIG. 12, for example, various ISAC systems may be considered in the present disclosure to include various ISAC service embodiments. For example, in an embodiment of the present disclosure, a base station may be represented as a BS. For example, in an embodiment of the present disclosure, a terminal may be represented as a UE. For example, a transmitter may transmit a signal for sensing, and a receiver may perform sensing based on a signal reflected from an object. FIG. 12(a) may represent a network-based monostatic ISAC system. In such a system, a BS may estimate the distance and velocity of multiple targets by transmitting an ISAC signal to them and receiving the reflected signal. Here, the target may be a UE. FIG. 12(b) may represent a network-based bistatic ISAC system. In such a system, two BSs may cooperate to estimate the distance and velocity of the same multiple targets. BS 1 may be the transmitter and BS 2 may be the receiver. BS 2 can receive signals reflected by targets from the ISAC signal transmitted by BS 1. Subsequently, BS 2 can estimate the distance and velocity of the targets. Unlike monostatic systems, bistatic ISAC systems may not have information regarding the transmitted signal. Therefore, bistatic ISAC systems can obtain a target radar information matrix through pilot signals that the transmitter and receiver already know of each other. Figure 12 (c) may be a network-UE-based bistatic ISAC system. In this system, the BS can transmit the ISAC signal. At this time, the BS can use beamforming techniques to direct most of the reflected signal toward the UE or have some of it return to the BS.In the former case, the UE can perform target distance and velocity estimation by receiving most of the signals transmitted by the BS. While the UE can quickly obtain information regarding the necessary targets, computational complexity may be high as the UE performs the entire process. On the other hand, in the latter case, the BS first estimates the target distance and velocity in the same manner as a mono-static ISAC system and can inform the UE of a suitable target estimation technique based on the estimation results. Through this, the UE can immediately perform target estimation using the technique provided by the BS, resulting in lower complexity.

[0154] Figure 12(d) may be a terminal-based (UE-based) monostatic ISAC system. The system can directly estimate the distance and velocity of targets from the UE. Figure 12(e) may be a terminal-network (UE-network) bistatic ISAC system. The BS can estimate the distance and velocity of multiple targets by receiving the signal reflected from the target after the ISAC signal transmitted by the UE. Figure 12(f) may be a terminal-based (UE-based) bistatic ISAC system. For example, the network may be a TRP. For example, the network may be a base station. In this system, the distance and velocity of targets can be estimated through bistatic between different UEs.

[0155] In the following description, various names are exemplary and may be considered to perform the same or similar functions (regardless of their names) based on the content described in each step.

[0156] In the present disclosure, for example, the following terms may be used.

[0157] - LMF: Location management function

[0158] - UE-triggered SL positioning: SL (sidelink) positioning where the procedure is triggered by the UE

[0159] - SL positioning triggered by base station / LMF: SL positioning where the procedure is triggered by base station / LMF

[0160] - UE-controlled SL positioning: SL positioning where the SL positioning group is generated by the UE

[0161] - SL positioning controlled by a base station: SL positioning where the SL positioning group is generated by the base station

[0162] - UE-based SL positioning: SL positioning where the UE location is calculated by the UE

[0163] - UE-assisted SL positioning: SL positioning where the UE location is calculated by the base station / LMF

[0164] - SL Positioning Group: UEs participating in SL positioning

[0165] - T-UE(Target UE): UE whose position is calculated

[0166] - S-UE (Server UE): A UE that assists T-UE's positioning

[0167] - Anchor UE: A UE that assists T-UE's positioning

[0168] - MG: Measurement gap where only SL PRS transmission is allowed

[0169] - MW: Measurement window where both SL data and SL PRS can be transmitted in a multiplexed way

[0170] - PRS: Positioning Reference Signal

[0171] - SL PRS: Sidelink Positioning Reference Signal

[0172] - CCH: control channel

[0173] - IUC (Inter-UE coordination) message: A message received by the TX UE from other UEs, including the RX UE, which contains information about the set of preferred resources suitable for the TX UE to transmit to the RX UE, and / or information about the set of non-preferred resources not suitable for transmission.

[0174] - UE-based: The way a UE calculates its own location is described as "UE-based".

[0175] - TP (transmission point): A set of transmission antennas (e.g., an antenna array having one or more antenna elements) placed at geographically identical locations for a cell, a part of a cell, or a DL PRS-only TP. Transmission points may include base station (ng-eNB or gNB) antennas, remote radio heads, remote antennas of base stations, antennas of DL PRS-only TPs, etc. A cell may include one or more transmission points. In the case of homogeneous placement, each transmission point may correspond to one cell.

[0176] - RP (reception point): A set of receiving antennas (e.g., antenna arrays having one or more antenna elements) placed at geographically identical locations for a cell, a part of a cell, or a UL SRS (sounding reference signal)-only RP. Reception points may include base station (ng-eNB or gNB) antennas, remote radio heads, remote antennas of base stations, antennas of UL SRS-only RPs, etc. A cell may include one or more reception points. In the case of homogeneous placement, each reception point may correspond to one cell.

[0177] - PRS-only TP: A TP that transmits only PRS signals for PRS-based TBS (terrestrial beacon system) positioning and is not connected to a cell.

[0178] - TRP (transmission-reception point): A set of antennas (e.g., an antenna array (with one or more antenna elements)) placed at the same geographical location that supports TP and / or RP functions.

[0179] - SRS-only RP: An RP that receives only SRS signals for UL-only positioning and is not associated with a cell

[0180] - Sensing devices: UE and / or TRP, and / or sensing TX devices and / or sensing RX devices

[0181] - Sensing TX device: A device that transmits a sensing reference signal

[0182] - Sensing RX device: A device that receives a sensing reference signal, and / or a device that monitors the sensing reference signal to perform a sensing measurement.

[0183] - Sensing signal: A reference signal transmitted and received for sensing; may be a transmission on the 3GPP radio interface that can be used for sensing purposes.

[0184] - Sensing transmitter: An entity that transmits a sensing signal; a sensing transmitter may be the entity that transmits the sensing signal which the sensing service will use in its operation. A sensing transmitter may be an NR RAN node or a UE. A sensing transmitter can be located in the same entity as the sensing receiver or in a different entity.

[0185] - Sensing receiver: An entity that receives a sensing signal; a sensing receiver may be an entity that receives the sensing signal which the sensing service will use in its operation. A sensing receiver may be an NR RAN node or a UE. A sensing receiver can be located in the same entity as the sensing transmitter or in a different entity.

[0186] - Sensing Server (SF (Sensing Function) or SMF (Sensing Management Function)): This is a server that controls sensing transmitters and receivers and oversees sensing operations and procedures. It can be considered to perform functions similar to those of a location management function (LMF) in positioning.

[0187] - SF (sensing function): A network entity that controls and manages the sensing procedures of a UE or TRP in the ISAC. For example, the SF can receive reports of sensing data collected by the UE or TRP and store the sensing data, and / or provide the sensing data for the sensing service to the sensing device.

[0188] - Monostatic sensing: Sensing where the sensing transmitter and sensing receiver are co-located in the same TRP or UE.

[0189] - Bistatic sensing: Sensing where the sensing transmitter and sensing receiver are located in different TRPs or different UEs.

[0190] - Multi-static sensing: Sensing in which multiple sensing transmitters and / or multiple sensing receivers exist for a single sensing target.

[0191] - BS-BS sensing: Sensing in which BS#1 transmits a sensing reference signal (sensing RS) and BS#2 receives the sensing RS. If BS#1 and BS#2 are separate BSs, it may mean BS-BS bistatic sensing operation, and if BS#1 and BS#2 are the same BS, it may mean BS-BS monostatic sensing operation. The BS may be a base station or a TRP (transmission and reception point). If BS#1 and / or BS#2 are one or more BSs, it may mean BS-BS multi-static sensing operation. The BS may mean a base station or a TRP (Transmission and Reception Point). (Sensing in which BS#1 transmits a sensing reference signal (RS) and BS#2 receives the sensing RS. When BS#1 and BS#2 are different base stations, the operation may correspond to BS-BS bistatic sensing, and when BS#1 and BS#2 are the same base station, the operation may correspond to BS-BS monostatic sensing. The BS may be a base station or a transmission and reception point (TRP). When BS#1 and / or BS#2 include one or more base stations, the operation may correspond to BS-BS multi-static sensing.)

[0192] - BS-UE bistatic sensing: Sensing in which a BS transmits a sensing reference signal (sensing RS) and a UE receives the sensing RS. The BS may be a base station or a transmission and reception point (TRP). If the BS and / or the UE include one or more BSs and / or one or more UEs, the operation may refer to BS-UE multistatic sensing. The BS may refer to a base station or a TRP.

[0193] - UE-BS bistatic sensing: Sensing in which a UE transmits a sensing reference signal (sensing RS) and a BS receives the sensing RS. The BS may be a base station or a transmission and reception point (TRP). If the BS and / or the UE include one or more BSs and / or one or more UEs, the operation may refer to UE-BS multistatic sensing. The BS may refer to a base station or a TRP.

[0194] - UE-UE sensing: Sensing in which UE#1 transmits a sensing reference signal (sensing RS) and UE#2 receives the sensing RS. If UE#1 and UE#2 are separate UEs, it may mean UE-UE bistatic sensing operation, and if UE#1 and UE#2 are the same UE, it may mean UE-UE monostatic sensing operation. The BS may be a base station or a transmission and reception point (TRP). If UE#1 and / or UE#2 are one or more UEs, it may mean UE-UE multistatic sensing operation. (Sensing in which UE#1 transmits a sensing RS and UE#2 receives the sensing RS. When UE#1 and UE#2 are different UEs, the operation may correspond to UE-UE bistatic sensing, and when UE#1 and UE#2 are the same UE, the operation may correspond to UE-UE monostatic sensing. When UE#1 and / or UE#2 include one or more UEs, the operation may correspond to UE-UE multi-static sensing.)

[0195] - Target object (TO): An object to be detected through sensing.

[0196] - TSA: Target sensing area. An area in which an object is intended to be detected through sensing.

[0197] - Moving TSA (target sensing area): A case where the target sensing service area moves according to the mobility of the target from the perspective of the sensing transmitter.

[0198] - Non-3GPP Sensing Data: Sensing data that is not collected through 3GPP communication-based sensing (e.g., camera data, video data, data collected through other RAT (e.g., Wi-Fi) based sensing, etc.)

[0199] - 3rd party entity: A server device operated by a sensing service operator (a business operator that uses / operates sensing data for a sensing service). For example, the 3rd party entity may receive and store sensing data for a sensing service from a sensing device, and / or provide sensing data for a sensing service to a sensing device.

[0200] For example, an SL PRS transmission resource may be composed of an SL PRS resource set consisting of the following information.

[0201] - SL PRS resource set ID

[0202] - SL PRS Resource ID List: List of SL PRS resource IDs within the SL PRS resource set

[0203] - SL PRS Resource Type: Can be set to periodic, aperiodic, semi-persistent, or on-demand

[0204] - Alpha for SL PRS power control

[0205] - P0 for SL PRS power control

[0206] - Path loss reference for SL PRS power control: Can be set to SL SSB, DL PRS, UL SRS, UL SRS for positioning, PSCCH DMRS, PSSCH DMRS, PSFCH, SL CSI RS, etc.

[0207] For example, the above SL PRS resource set may be composed of SL PRS resources consisting of the following information.

[0208] - SL PRS Resource ID

[0209] - SL PRS Comb Size: The interval between REs transmitted within a symbol for SL PRS.

[0210] - SL PRS Comb Offset: The RE index where the SL PRS within the first SL PRS symbol is first transmitted.

[0211] - SL PRS Comb Cyclic Shift: A cyclic shift used to generate the sequence that constitutes the SL PRS

[0212] - SL PRS start position: Index of the first symbol transmitting the SL PRS within a single slot

[0213] - Number of SL PRS symbols: The number of symbols constituting the SL PRS within a single slot

[0214] - Frequency domain shift: The lowest frequency position (index) in the frequency domain where the SL PRS is transmitted

[0215] - SL PRS BW: Frequency bandwidth used for SL PRS transmission

[0216] - SL PRS Resource Type: Can be set to periodic, aperiodic, semi-persistent, or on-demand

[0217] - SL PRS Periodicity: The period in the time domain between SL PRS resources, physical, or the unit of a logical slot in the resource pool where SL PRS is transmitted.

[0218] - SL PRS Offset: An offset in the time domain from the reference timing to the start of the first SL PRS resource, in units of physical or logical slots within the resource pool where the SL PRS is transmitted. The reference timing may be SFN=0 or DFN=0, or the time of successful reception or decoding of the RRC / MAC-CE / DCI / SCI associated with the SL PRS resource.

[0219] - SL PRS Sequence ID

[0220] - SL PRS spatial relation: Can be set to SL SSB, DL PRS, UL SRS, UL SRS for positioning, PSCCH DMRS, PSSCH DMRS, PSFCH, SL CSI RS, etc.

[0221] - SL PRS CCH: SL PRS control channel. Can signal SL PRS resource configuration information and resource locations, etc.

[0222] In this disclosure, TRP and base station may be substituted and used as the same entity. In this disclosure, the term "sensing message" may be a term that can be used interchangeably with "sensing reference signal" or "sensing measurement report." The sensing signal mentioned in this disclosure may be interpreted as having the same meaning as the sensing reference signal. The sensing data mentioned in this disclosure may be interpreted as having the same meaning as the sensing measurement data or the sensing measurement report. The bandwidth part (BWP) mentioned in this disclosure may be substituted and applied as a bandwidth setting set or a wireless resource set, etc. The wireless resource profile exemplified in this disclosure may be substituted and applied as a bandwidth part (BWP), a bandwidth setting set, or a wireless resource set, etc.

[0223] In the present disclosure, for example, the following terms may be defined to describe AI / ML.

[0224] - Data collection: Data collected from network nodes, management entities, or terminals, serving as a basis for ML model training, data analysis, and inference.

[0225] - ML Model: A data-driven algorithm that applies machine learning techniques to generate a set of outputs containing predictive information based on a set of inputs.

[0226] - ML Training: An online or offline process of training an ML model by learning features and patterns that best represent the data and acquire an ML model trained for inference.

[0227] - ML Inference: A process of making predictions or deriving decisions based on collected data and ML models using a trained ML model.

[0228] FIG. 14 illustrates a functional framework for artificial intelligence and machine learning (AI / ML) according to one embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted.

[0229] Referring to FIG. 14, for example, data collection may be a function that provides input data to model training and model inference functions. AI / ML algorithm-specific data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) may not be performed in the data collection function. Examples of input data may include measurements from terminals or other network entities, feedback from actors, and outputs from AI / ML models.

[0230] For example, training data may be data required as input for the training function of an AI / ML model.

[0231] For example, inference data may be data required as input for the inference function of an AI / ML model.

[0232] For example, model training may be a function that performs ML model training, validation, and testing to generate model performance metrics as part of the model testing procedure. If necessary, the model training function may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on training data provided by the data collection function.

[0233] For example, model deployment / update can be used to initially deploy trained, validated, and tested AI / ML models to the model inference function, or to provide updated models to the model inference function.

[0234] For example, model inference can be a function that provides AI / ML model inference outputs (e.g., predictions or decisions). Where applicable, the model inference function can provide model performance feedback to the model training function. If necessary, the model inference function can also handle data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on the inference data provided by the data collection function.

[0235] For example, the output may be the inference output of an AI / ML model generated by the model inference function. Note that the details of the inference output may vary depending on the use case.

[0236] For example, model performance feedback can be used to monitor the performance of AI / ML models.

[0237] For example, an actor can be a function that receives output from a model inference function and triggers or performs the corresponding action. An actor can trigger actions on other entities or on itself.

[0238] For example, feedback may be information that is necessary to derive training or inference data or performance feedback.

[0239] For example, in datasets used in AI / ML, the definitions of training, validation, and test data can be as follows. For instance, training data may be a dataset for training a model. For instance, validation data may be a dataset for validating a model that has already been trained. For instance, validation data is typically used to prevent overfitting of the training dataset. For instance, validation data may be a dataset for selecting the best model among several models trained during the learning process. Therefore, this can be viewed as a type of training. For instance, test data may be a dataset for final evaluation, and test data may be unrelated to training. For instance, regarding the above datasets, if the training set is divided, the training and validation data within the entire training set can typically be split in a ratio of approximately 8:2 or 7:3; if tests are included, the ratio can be split as 6:2:2 (training:validation:test).

[0240] For example, in the present disclosure, "specific threshold" may mean a threshold that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "specific set value" may mean a value that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "set by the network / base station" may mean an action in which a base station sets to a UE (pre-) through upper layer RRC signaling, sets / signals to a UE through MAC CE, or signals to a UE through DCI.

[0241] For example, in the present disclosure, a message may be interpreted as being replaced by at least one of a control message, a data message, a signal, a data signal, and / or a control signal.

[0242] For example, referring to standard documents, some procedures and technical specifications related to the present disclosure may be as follows.

[0243] In the following description, various names are exemplary and may be considered to perform the same or similar functions (regardless of their names) based on the content described in each step.

[0244] For example, in this disclosure, various names are exemplary and may be replaced or considered as other names performing the same or similar functions based on the content described in each step (regardless of the name).

[0245] For example, in the relevant technology, inter-cell handover in an NR system can be performed based on the quality measurement of signals transmitted from the UE to the Serving Base Station (gNB) and the Neighbor Base Station (gNB). For example, since handover generally occurs from the Serving Base Station to the Neighbor Base Station, the Serving Base Station can be referred to as the source base station and the Neighbor Base Station as the target base station.

[0246] For example, detailed procedures and details regarding handover may be specified in the 3GPP TS 38.300 standard document. For example, details regarding procedures for mobility and handover in a connected state as specified in TS 38.300 may be disclosed below.

[0247] 9.2.3 Mobility in RRC_CONNECTED

[0248] 9.2.3.1 Overview

[0249] For example, network-controlled mobility can be applied to UEs in the RRC_CONNECTED state and can be classified into two types: cell-level mobility and beam-level mobility. For example, beam-level mobility may include intra-cell beam-level mobility and inter-cell beam-level mobility.

[0250] FIG. 15 illustrates an example of a handover procedure between gNBs according to an embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0251] Referring to FIG. 15, for example, cell-level mobility may require being triggered by explicit RRC signaling, for example, a handover. For example, in the case of an inter-gNB handover, the signaling procedure may consist of at least the following elemental components shown in FIG. 15.

[0252] For example, 1. The source gNB can initiate a handover and send a HANDOVER REQUEST through the Xn interface.

[0253] For example, 2. The target gNB can perform admission control and provide a new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE.

[0254] For example, 3. The source gNB may provide RRC configuration to the UE by delivering an RRCReconfiguration message received from the HANDOVER REQUEST ACKNOWLEDGE. For example, the RRCReconfiguration message may include at least the cell ID and all information necessary to access the target cell so that the UE can access the target cell without reading system information. For example, in some cases, information necessary for contestion-based and contestion-free random access may be included in the RRCReconfiguration message. For example, the access information to the target cell may include beam-specific information, if present.

[0255] For example, 4. The UE can move the RRC connection to the target gNB and respond with RRCReconfigurationComplete.

[0256] For example, Note 1: If the grant allows, user data may also be transmitted in Step 4.

[0257] 9.2.3.2 Handover

[0258] 9.2.3.2.1 C-Plane Handling

[0259] FIG. 16 illustrates an example of an intra-AMF / UPF handover procedure according to one embodiment of the present disclosure. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0260] FIG. 17 illustrates an example of an intra-AMF / UPF handover procedure according to one embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0261] FIG. 18 illustrates an example of an intra-AMF / UPF handover procedure according to one embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0262] Referring to FIGS. 16, 17, and 18, for example, an intra-NR RAN handover can perform the preparation phase and execution phase of the handover procedure without the involvement of 5GC, and, for example, preparation messages can be exchanged directly between gNBs. For example, during the handover completion phase, resource release at the source gNB can be triggered by the target gNB. For example, FIGS. 16, 17, and 18 can illustrate a basic handover scenario in which both the AMF and UPF remain unchanged.

[0263] For example, 0. The UE context within the source gNB may contain information regarding roaming and access restriction, which may have been provided at the time of connection establishment or at the time of the last TA update.

[0264] For example, 1. The source gNB can configure the UE measurement procedure, and the UE can report the measurement results according to the measurement configuration.

[0265] For example, 2. The source gNB can determine the handover for the UE based on MeasurementReport and RRM information.

[0266] For example, 3. The source gNB may send a Handover Request message to the target gNB and may deliver a transparent RRC container containing information necessary for the target side to prepare for the handover. For example, such information may include at least the following: the target cell ID, the KgNB, the UE's C-RNTI in the source gNB, RRM settings including UE inactive time, basic AS settings including antenna information and DL carrier frequency, mapping rules between the current QoS flow and DRB applied to the UE, the source gNB's SIB1 information, UE capabilities for different RATs, PDU session-related information, and, if available, UE report measurement information including beam-related information. For example, PDU session-related information may include slice information and QoS profiles at the QoS flow level. For example, the source gNB may request a DAPS handover for one or more DRBs.

[0267] For example, Note 1 (NOTE 1): After sending a Handover Request, the source gNB may need not reset the UE, including performing reflective QoS flow-DRB mapping.

[0268] For example, 4. The target gNB can perform admission control. For example, when slice information is transmitted to the target gNB, slice-aware admission control needs to be performed. For example, if a PDU session is associated with an unsupported slice, the target gNB needs to reject the PDU session.

[0269] For example, 5. The target gNB can prepare for a handover at the L1 / L2 layer and send a HANDOVER REQUEST ACKNOWLEDGE to the source gNB, including a transparent container containing an RRC message to be delivered to the UE. For example, the target gNB can also indicate whether to accept the DAPS handover.

[0270] For example, Note 2: Data forwarding may be initiated as soon as the source gNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the transmission of the handover command is initiated on the downlink.

[0271] For example, Note 3: In the case of a DRB configured as DAPS, the downlink PDCP SDU can be forwarded with the SN assigned by the source gNB, and this can continue until the SN assignment is transferred to the target gNB in ​​step 8b, after which normal data forwarding can be performed.

[0272] For example, 6. The source gNB may trigger a Uu handover by sending an RRCReconfiguration message to the UE containing information necessary to access the target cell: at least the target cell ID, a new C-RNTI, and a target gNB security algorithm identifier for the selected security algorithm. For example, it may also include a dedicated RACH resource set, association information between the RACH resource and the SSB, association information between the RACH resource and the UE-specific CSI-RS configuration, common RACH resource, system information of the target cell, etc.

[0273] For example, Note 4: In the case of a DRB configured with DAPS, the source gNB may not stop transmitting downlink packets until it receives a HANDOVER SUCCESS message from the target gNB in ​​step 8a.

[0274] For example, Note 4a: CHO may not be set simultaneously with DAPS handover.

[0275] For example, in the case of a DRB configured as 7a. DAPS, the source gNB may send an EARLY STATUS TRANSFER message. For example, the DL COUNT value included in the message may indicate the PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. For example, the source gNB may not stop assigning SNs to downlink PDCP SDUs until it sends an SN STATUS TRANSFER message in step 8b.

[0276] For example, 7. For a DRB not configured with DAPS, the source gNB may send an SN STATUS TRANSFER message to the target gNB and convey the uplink PDCP SN receiver status and downlink PDCP SN transmitter status for a DRB to which PDCP state preservation applies (e.g., for an RLC AM). For example, the uplink PDCP SN receiver status may include the PDCP SN of at least the first missing UL PDCP SDU and, if necessary, a bitmap of the receiver status of out-of-order UL PDCP SDUs that the UE must retransmit from the target cell. For example, the downlink PDCP SN transmitter status may indicate the next PDCP SN that the target gNB must assign to a new PDCP SDU that has not yet been assigned a PDCP SN.

[0277] For example, Note 5: In the case of a DAPS handover, the uplink PDCP SN receiver status and downlink PDCP SN transmitter status for an RLC-AM DRB not set to DAPS may be conveyed via the SN STATUS TRANSFER message of step 8b instead of step 7.

[0278] For example, Note 6: For a DRB configured as DAPS, the source gNB may send an additional EARLY STATUS TRANSFER message between steps 7 and 8b to notify the discarding of PDCP SDUs that have already been forwarded. For example, the target gNB may not send forwarded downlink PDCP SDUs to the UE that have a COUNT smaller than the forwarded DL COUNT value, and may discard them if transmission has not yet been attempted.

[0279] For example, 8. The UE can synchronize with the target cell and complete the RRC handover procedure by sending the RRCReconfigurationComplete message to the target gNB. For example, in the case of a DAPS handover, the UE may not detach from the source cell even after receiving the RRCReconfiguration message. For example, the UE may release source resources and configurations after receiving an explicit release instruction from the target node and may stop receiving and transmitting DL / UL with the source.

[0280] For example, Note 6a: From a RAN perspective, a DAPS handover may be considered complete only after the UE has released the source cell as explicitly requested by the target node. For example, an RRC suspend, subsequent handover, or inter-RAT handover may not be initiated until the source cell is released.

[0281] For example, 8a / b. In the case of a DAPS handover, the target gNB may send a HANDOVER SUCCESS message to the source gNB to indicate that the UE has successfully accessed the target cell. For example, in response to this, the source gNB may send an SN STATUS TRANSFER message to the DRBs configured as DAPS in step 7, after which normal data forwarding may be performed.

[0282] For example, Note 7: When set to DAPS, the uplink PDCP SN receiver status and downlink PDCP SN transmitter status for a DRB having RLC-UM may also be included and transmitted in the SN STATUS TRANSFER message of step 8b.

[0283] For example, Note 8: In the case of a DRB configured with DAPS, the source gNB may not stop forwarding uplink QoS flows to the UPF until it transmits the SN STATUS TRANSFER message in step 8b. For example, the target gNB may not forward QoS flows of uplink PDCP SDUs received in normal order to the UPF until it receives the SN STATUS TRANSFER message, and the UL HFN and the first missing SN included in the uplink PDCP SN receiver state may indicate the starting point of the uplink PDCP SDU to be forwarded to the UPF. For example, the target gNB may not forward uplink PDCP SDUs having a UL COUNT lower than the provided value.

[0284] For example, 9. The target gNB can send a PATH SWITCH REQUEST message to the AMF, trigger 5GC to switch the downlink data path to the target gNB, and set up an NG-C interface instance toward the target gNB.

[0285] For example, 10.5GC can switch downlink data paths to target gNBs. For example, UPF can send one or more end marker packets along the existing path to the source gNB per PDU session / tunnel, and then release U-Plane / TNL resources toward the source gNB.

[0286] For example, 11. AMF can check the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message.

[0287] For example, 12. After receiving the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB may send UE CONTEXT RELEASE to notify the source gNB of the success of the handover. For example, the source gNB may then release the radio and C-Plane resources associated with the UE context. For example, ongoing data forwarding may continue.

[0288] For example, the UE can measure the signal quality of the serving base station and the neighbor base station based on measurement parameters set for handover, and send a Measurement Report to the serving base station. For example, the serving base station can perform a handover based on the received Measurement Report.

[0289] FIG. 19 illustrates an example of a measurement report-based handover procedure according to one embodiment of the present disclosure. The embodiment of FIG. 19 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0290] Referring to Fig. 19, for example, a handover procedure based on a measurement report based on TS 38.300 can be illustrated.

[0291] For example, various events may exist as trigger conditions for transmitting a measurement report (e.g., MeasurementReport) for handover. For example, the following may be transmission conditions for a measurement report (e.g., MeasurementReport) set for ground UEs at a typical ground base station, as currently defined by 3GPP.

[0292] - For example, Event A1: When the serving cell becomes better than the threshold (e.g., Serving becomes better than threshold)

[0293] - For example, Event A2: When the serving cell becomes worse than the threshold (e.g., Serving becomes worse than threshold)

[0294] - For example, Event A3: The case where the Neighbour cell becomes better than SpCell by an offset amount (e.g., Neighbour becomes offset better than SpCell)

[0295] - For example, Event A4: When the Neighbour cell becomes better than the threshold (e.g., Neighbour becomes better than threshold)

[0296] - For example, Event A5: The case where SpCell becomes worse than threshold 1, and at the same time, neighbor becomes better than threshold 2 (e.g., SpCell becomes worse than threshold1 and neighbor becomes better than threshold2)

[0297] Here, for example, an A3 event may apply when the measurement value of the Naver base station is better than the measurement value of the serving base station (e.g., offset). For example, an A4 event may apply when the measurement value of the Naver base station is better than a specific threshold. For example, an A5 event may apply when the measurement value of the serving base station is worse than a specific threshold, and the measurement value of the Naver base station is better than a specific threshold.

[0298] Here, for example, the measurement value can be the RSRP measurement of the SSB or CSI-RS reference signal, and additionally, RSRQ and SINR values ​​may also be used. For example, therefore, although there are slight differences for each event, a trigger action to hand over to the Naver base station can be performed when it is determined that the RSRP value of the Naver base station is generally better than the RSRP of the current serving base station (e.g., above a certain value).

[0299] For example, in the relevant technology, 5G NR handover can be performed based on the signal quality of the serving base station and the neighbor base station measured by the UE. For example, to do this, the UE needs to continuously measure the signal and send a measurement result report (e.g., a MeasurementReport message) to the serving base station.

[0300] For example, these continuous signal measurements and measurement report transmission operations by the UE can increase the UE's power consumption and signaling overhead. Furthermore, since these measurement report transmissions mostly occur in handover areas with poor signal quality, transmission failures can occur frequently. For instance, increased retransmissions resulting from such failures can cause handover delays, ultimately leading to issues such as reduced transmission speed, increased interrupt times, and call drops.

[0301] FIG. 20 illustrates an example of a procedure related to a handover delay caused by a failure to transmit a measurement report, according to one embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0302] Referring to Fig. 20, for example, in 3GPP standards, conditional handover (CHO) technology may be introduced to resolve or improve the problem of transmitting MeasurementReport messages (e.g., also base station handover commands (e.g., RRCReconfiguration message transmission)). Unlike HO, conditional handover (CHO) allows the handover execution to take place at the UE. For example, the network can pre-configure handover settings for multiple cells. For example, the UE can perform the handover itself (e.g., without transmitting the MR (measurement report) and receiving the HO command (RRC reconfiguration)) by using these settings during the HO process. However, for such CHO operations, the UE must perform continuous measurement operations, so energy consumption by the UE may still occur.

[0303] For example, in the relevant technology, a base station can acquire the location and LOS information of a UE through LTE / NR positioning operations. For example, the base station can perform a handover based on the location and LOS information obtained through these positioning operations. However, for positioning operations, a positioning session setup may be required, and the transmission of a positioning report (e.g., LPP ProvideLocationInformation), similar to the transmission of a measurement report (e.g., MeasurementReport), may be required. For example, this may cause the handover delay problem caused by the failure to transmit the positioning report, as pointed out in the aforementioned issue.

[0304] For example, the present disclosure may propose a base station sensing-based (e.g., BS monostatic and / or UE-BS bistatic) handover method and procedure.

[0305] For example, the technical background of the present disclosure may be described below.

[0306] For example, various paths can exist in the wireless segment between a base station and a UE, which can be broadly classified into Line of Sight (LOS) paths and Non-Line of Sight (NLoS) paths. For instance, when an LOS path exists, the communication quality between the base station and the UE can be stable (compared to the case where only an NLoS path exists).

[0307] FIG. 21 illustrates an example of LOS path loss due to UE movement according to one embodiment of the present disclosure. The embodiment of FIG. 21 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0308] For example, in FIG. 21, when a UE moves from an LOS area (e.g., location 1) to an NLoS area (e.g., location 2), the UE may experience a degradation in communication quality in the NLoS area (e.g., location 2). For example, therefore, when moving from an LOS area (e.g., location 1) to an NLoS area (e.g., location 2), a handover operation to another neighbor base station can be performed to prevent a degradation in communication quality.

[0309] For example, in particular, the relationship between communication quality and such LOS characteristics (e.g., presence or absence) may be prominent in high frequency bands (e.g., FR2).

[0310] For example, the key aspects of the present disclosure may be described below.

[0311] For example, the core of the present disclosure may be that a handover decision and procedure are performed based on base station (BS) sensing results without a measurement operation and a measurement report (e.g., MeasurementReport) transmission operation of the UE.

[0312] For example, to this end, a handover method and procedure can be proposed that are performed based on the sensing results (LOS probability with UE) obtained from base station sensing (e.g., BS monostatic or UE-BS bistatic) operations.

[0313] For example, if the currently communicating serving base station anticipates that the LOS path will be lost during communication with the UE, it can request sensing of the UE from neighboring base stations and receive LOS probability values. For instance, based on the received LOS probability values ​​from neighboring base stations, a handover can be performed to a neighboring base station where an LOS path exists before the UE enters an NLoS area.

[0314] FIG. 22 illustrates an example of a procedure related to a BS sensing-based handover without UE measurement and measurement report transmission, according to one embodiment of the present disclosure. The embodiment of FIG. 22 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0315] Referring to FIG. 22, for example, through the present disclosure, a UE can perform a handover process without a signal measurement step and a measurement report transmission step of the serving base station and the neighbor base station. For example, this can reduce the energy consumption and signaling overhead of the UE required for handover in the relevant technology. For example, by omitting the measurement report transmission step, a faster handover can be performed, and the problem of handover delay caused by transmission failure can be drastically resolved.

[0316] For example, the handover method and procedure proposed in the present disclosure may be described below.

[0317] FIG. 23 illustrates an example of a BS monostatic sensing-based handover procedure according to one embodiment of the present disclosure. The embodiment of FIG. 23 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted. For example, a dotted line in FIG. 23 may indicate an operation that may be omitted.

[0318] Referring to FIG. 23, for example, the handover method and procedure proposed in the present disclosure may be as follows.

[0319] For example, the event conditions proposed in the present disclosure may be (tentative) Event S1, Event S2, Event S3, Event S4, and Event S5.

[0320] - For example, Event S1: When the serving LOS probability becomes higher than the threshold (e.g., Serving LOS probability becomes higher than threshold)

[0321] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0322] - For example, Event S2: When the Serving LOS probability becomes lower than the threshold (e.g., Serving LOS probability becomes lower than threshold)

[0323] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0324] - For example, Event S3: The case where the Neighbour LOS probability becomes higher than the Serving LOS probability by an offset amount (e.g., Neighbour LOS probability becomes offset higher than Serving LOS probability)

[0325] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0326] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0327] - For example, Event S4: When the Neighbour LOS probability becomes higher than the threshold (e.g., Neighbour LOS probability becomes higher than threshold)

[0328] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0329] - For example, Event S5: When the Serving LOS probability becomes lower than threshold 1 and the neighbor LOS probability becomes higher than threshold 2 (e.g., Serving LOS probability becomes lower than threshold 1 and neighbor LOS probability becomes higher than threshold 2)

[0330] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0331] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0332] For example, Step 0: The serving base station can transmit measurement settings to the UE. For example, it can be assumed that the serving base station and the UE are communicating, and the serving base station is in a state of BS monostatic sensing.

[0333] For example, if sensing is being performed based on a sensing session established between a sensing server and a base station, it can be assumed that a sensing session is established between the sensing server and the base station. However, since sensing operations are possible without establishing a sensing session, the establishment of a sensing session itself may not be a prerequisite for such operations.

[0334] - For example, it can be assumed that a sensing server (sensing function, SF) is located on a serving base station. For example, it can be assumed that session setup and / or parameter setup required for a sensing operation of a nearby (e.g., Naver) base station is performed before and during the sensing operation.

[0335] - Here, for example, the serving base station (or sensing server) can set the TSA (target sensing area) to the corresponding UE.

[0336] For example, Step 1: The serving base station and / or UE can transmit a sensing signal. For example, the serving base station can receive a sensing signal. For example, the serving base station can sense a specific UE communicating with it and monitor whether the LOS probability of the sensing result is below a threshold (e.g., Event S2).

[0337] - Here, for example, the sensing signal received by the serving base station may be a sensing signal based on BS monostatic sensing.

[0338] Here, for example, the serving base station can sense a specific UE communicating based on a sensing signal based on the BS monostatic sensing.

[0339] - Here, for example, the sensing signal received by the serving base station may be a sensing signal based on non-3GPP sensing.

[0340] Here, for example, a serving base station can sense a specific UE communicating based on a sensing signal based on the above-mentioned non-3GPP sensing.

[0341] - Here, for example, the operation based on the threshold may be the operation based on the above event S2.

[0342] - - For example, if the threshold value is 0.7 (e.g., 70%), it can be said that the event S2 condition is satisfied if the LOS probability is 70% or less.

[0343] - Here, for example, parameters for the operation of Event S2 (e.g., threshold value and specific time, etc.) can be set. For instance, details regarding parameter settings may be written in the common section below.

[0344] For example, Step 2: The serving base station and / or SF may perform a sensing trigger. For example, the serving base station and / or SF may perform a sensing trigger based on Event S2. For example, the serving base station and / or SF may send a sensing request to a neighbor base station. For example, the serving base station and / or SF may send a (tentative) SENSING REQUEST message to the neighbor base station. For example, if the LOS probability of the sensing result is below a threshold (e.g., Event S2), the serving base station and / or SF may request a neighbor (neighbor) base station to sense the corresponding UE.

[0345] - Here, for example, the serving base station and / or SF can send a (tentative) SENSING REQUEST message to request nearby (e.g., neighbor) base stations to sense the UE.

[0346] Here, for example, the serving base station and / or SF send a sensing request message to the neighbor base station and wait for the sensing result, and can predict the time to enter the NLoS interval based on the movement of the UE. For example, therefore, the serving base station and / or SF can specify the expected sensing response time from the neighbor base station when making a sensing request. For example, in Step 3 below, the neighbor base station can provide the sensing result within the set sensing response time.

[0347] For example, Step 3: The neighbor base station and / or UE may transmit a sensing signal. For example, the neighbor base station may receive a sensing signal. For example, the neighbor base station may transmit a sensing response to the sensing base station. For example, the neighbor base station may transmit a (tentative) SENSING RESPONSE message to the sensing base station. For example, the neighbor base station that receives a sensing request (e.g., SENSING REQUEST message) may sense the corresponding UE and transmit the sensing result (e.g., SENSING RESPONSE message) to the serving base station. For example, it can be assumed that the neighbor base station and the UE are communicating, and the neighbor base station is in a state of BS monostatic sensing.

[0348] - Here, for example, the Naver base station can sense the corresponding UE.

[0349] - Here, for example, the sensing signal received by the Naver base station may be a sensing signal based on BS monostatic sensing.

[0350] Here, for example, the Naver base station can sense a specific UE communicating based on a sensing signal based on the above BS monostatic sensing.

[0351] - Here, for example, the sensing signal received by the Naver base station may be a sensing signal based on non-3GPP sensing.

[0352] Here, for example, the Naver base station can sense a specific UE communicating based on a sensing signal based on the above-mentioned non-3GPP sensing.

[0353] - Here, for example, the Naver base station can transmit the sensing result of the corresponding UE to the serving base station as a (tentative) SENSING RESPONSE message.

[0354] - Here, for example, the sensing result of the corresponding UE may refer to the measured LOS probability between the corresponding UE and each Naver base station.

[0355] Here, for example, the LOS probability can be expressed as a hard value, e.g., LOS or NLOS. For example, or as a soft value, e.g., a probability number. For example, 0.1 can mean that the probability of LOS is 10%. For example, if this value is 1.0, it can mean that the probability of LOS is 100%.

[0356] - Here, for example, the Naver base station can send the sensing result within the sensing response time received upon the sensing request.

[0357] For example, Step 4: The serving base station and / or SF may make a handover decision based on sensing. For example, the serving base station and / or SF may make a handover decision based on event S3. For example, the serving base station and / or SF may make a handover decision based on event S4. For example, the serving base station and / or SF may make a handover decision based on event S5. For example, the serving base station and / or SF may make a handover by comparing the LOS probability of the serving base station with the LOS probability of the neighbor base station (e.g., events S3 / S4 / S5).

[0358] - Here, for example, the handover operation decision can be performed by comparing the serving base station LOS probability and the neighbor base station LOS probability. For example, the event used for the operation decision can be determined by event S3 and / or event S4 and / or event S5.

[0359] Here, for example, parameter settings for events S3 / S4 / S5 can be set by the serving base station, the upper network, or the sensing server.

[0360] Here, for example, a handover is determined based on configured events. If one or more events are configured, the handover can be performed if at least one of the configured events is satisfied.

[0361] - Here, for example, the description for events S3 / S4 / S5 may be as follows.

[0362] For example, Event S3 may be a case where the LOS probability of the Naver base station is higher than the LOS probability of the serving base station by more than an offset.

[0363] For example, Event S4 is the case where the LOS probability of the Naver base station is higher than a specific threshold.

[0364] For example, Event S5 may be a case where the LOS probability of the serving base station is lower than a specific threshold, and the LOS probability of the Naver base station is higher than a specific threshold.

[0365] Here, for example, different values ​​can be used for the threshold compared with the serving base station LOS probability and the threshold compared with the Naver base station LOS probability.

[0366] For example, Step 5: The serving base station may transmit a handover request to the neighbor base station. For example, the serving base station may transmit a (tentative) HANDOVER REQUEST message to the neighbor base station. When a handover is determined, the serving base station (or sensing server) may send a handover request message to the appropriate neighbor base station. For example, subsequent operations may be similar or identical to the handover operations in the relevant technology. For example, therefore, a detailed description of subsequent operations including Step 5 may be omitted in this disclosure.

[0367] For example, during the handover operation utilizing the above-mentioned BS monostatic sensing, it is possible to monitor whether a case occurs where the LOS probability of the sensing result becomes higher than a specific threshold (e.g., Event S1). For example, if Event S1 occurs (e.g., if the LOS probability of the corresponding UE improves above the threshold), the ongoing handover procedure may be stopped or terminated. For example, in such a case, the serving base station may send a sensing stop message (tentative name) SENSING STOP message to the neighbor base station. For example, the neighbor base station that receives the SENSING STOP message may stop the currently operating sensing operation and not perform subsequent procedures.

[0368] For example, the common items applicable to the above procedure may be as follows.

[0369] - For example, the various event-specific thresholds used in the above procedure can be set to different values.

[0370] - For example, in the above procedure, to compensate for instantaneously changing LOS probabilities, the operation may be configured to take an average over a specific period, or to trigger an event only when the state above or below a threshold is maintained for a specific period. For example, to this end, when setting the threshold value, a specific time for taking the average and / or a specific time for maintaining the state above or below the threshold may be set together.

[0371] - For example, in the above procedure, parameters such as thresholds and specific times may be set by the Serving / Naver base station or the sensing server. For example, they may be defined as specific values ​​(e.g., explicitly) in a standard document. For example, they may be set by varying to optimized values ​​calculated by AI / ML. For example, additionally, when a sensing request is made to the Naver base station, the Serving / Naver base station or the sensing server may transmit a message including these parameter values.

[0372] For example, in the present disclosure, a base station (BS) may include one or more TRPs. For example, although the present disclosure is based on handover between different base stations, handover between TRPs within a single base station may be supported in the same way.

[0373] For example, in the above method and procedure, it may be assumed that the base station can pair information about a UE currently communicating (e.g., requiring a handover) with sensing results for that UE. For example, it may be assumed that the base station can determine the location of the UE (e.g., absolute or relative) and distinguish the sensing results of the UE from the sensing results. For example, this information may be utilized when the serving base station requests sensing of the UE from the neighbor base station. For example, the serving base station (or sensing server) may set the target sensing area (TSA) to the UE. Here, for example, the method of distinguishing the UE (e.g., setting the TSA) and the pairing of sensing results are not core matters of the present disclosure, so a detailed description may be omitted.

[0374] For example, the base station can use BS monostatic sensing mode. For example, the base station can use UE-BS bistatic sensing mode. For example, the base station can use a combination of BS monostatic sensing mode and UE-BS bistatic sensing mode (e.g., joint / hybrid).

[0375] For example, the sensing results used in the present disclosure (e.g., LOS information obtained by sensing measurement) may utilize sensing results obtained from non-3GPP sensing, such as radar / camera / lidar, as well as 3GPP sensing using 3GPP signals. For example, parameters such as thresholds and specific times used in the procedure may also be set differently depending on the type of sensor used (e.g., 3GPP sensing or non-3GPP sensing).

[0376] For example, in the above procedure, the serving base station may trigger a 3GPP sensing operation based on non-3GPP sensing results. For example, if the LOS probability decreases based on the non-3GPP sensing results, a 3GPP sensing operation may be performed to obtain more accurate sensing results. For example, conversely, a non-3GPP sensing operation may be triggered based on 3GPP sensing results. For example, this may be configured by considering the difference in accuracy between the 3GPP sensing operation and the non-3GPP sensing operation, as well as the required current consumption. For example, additionally, this operation may be used as a trigger condition for a sensing operation between the serving base station and the neighbor base station.

[0377] FIG. 24 illustrates an example of a UE-BS bistatic sensing-based handover procedure according to one embodiment of the present disclosure. The embodiment of FIG. 24 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted. For example, a dotted line in FIG. 24 may indicate an operation that may be omitted.

[0378] Referring to FIG. 24, for example, a handover procedure based on UE-BS bistatic sensing may be illustrated. For example, the method and procedure may be written based on BS monostatic sensing mode. For example, however, the proposed disclosure is not limited to the BS monostatic sensing mode and may also operate in the UE-BS bistatic sensing mode. For example, in the UE-BS bistatic sensing mode, the UE can transmit a sensing signal and the BS can measure the sensing signal. For example, even in this case, since the UE does not require measurement and transmission of a measurement report, the core content of the method and procedure proposed in this disclosure can be applied in the same way.

[0379] Referring to FIG. 24, for example, the handover method and procedure proposed in the present disclosure may be as follows.

[0380] For example, the event conditions proposed in the present disclosure may be (tentative) Event S1, Event S2, Event S3, Event S4, and Event S5.

[0381] - For example, Event S1: When the serving LOS probability becomes higher than the threshold (e.g., Serving LOS probability becomes higher than threshold)

[0382] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0383] - For example, Event S2: When the Serving LOS probability becomes lower than the threshold (e.g., Serving LOS probability becomes lower than threshold)

[0384] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0385] - For example, Event S3: The case where the Neighbour LOS probability becomes higher than the Serving LOS probability by an offset amount (e.g., Neighbour LOS probability becomes offset higher than Serving LOS probability)

[0386] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0387] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0388] - For example, Event S4: When the Neighbour LOS probability becomes higher than the threshold (e.g., Neighbour LOS probability becomes higher than threshold)

[0389] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0390] - For example, Event S5: When the Serving LOS probability becomes lower than threshold 1 and the neighbor LOS probability becomes higher than threshold 2 (e.g., Serving LOS probability becomes lower than threshold 1 and neighbor LOS probability becomes higher than threshold 2)

[0391] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0392] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0393] For example, Step 0: The serving base station can transmit measurement settings to the UE. For example, it can be assumed that the serving base station and the UE are communicating, and the serving base station is in a state of UE-BS bistatic sensing.

[0394] For example, if sensing is being performed based on a sensing session established between a sensing server and a base station, it can be assumed that a sensing session is established between the sensing server and the base station. However, since sensing operations are possible without establishing a sensing session, the establishment of a sensing session itself may not be a prerequisite for such operations.

[0395] - For example, it can be assumed that a sensing server (sensing function, SF) is located on a serving base station. For example, it can be assumed that session setup and / or parameter setup required for a sensing operation of a nearby (e.g., Naver) base station is performed before and during the sensing operation.

[0396] - Here, for example, the serving base station (or sensing server) can set the TSA (target sensing area) to the corresponding UE.

[0397] For example, Step 1: The serving base station and / or UE can transmit a sensing signal. For example, the serving base station can receive a sensing signal. For example, the serving base station can sense a specific UE communicating with it and monitor whether the LOS probability of the sensing result is below a threshold (e.g., Event S2).

[0398] - Here, for example, the sensing signal received by the serving base station may be a sensing signal based on UE-BS bistatic sensing.

[0399] Here, for example, a serving base station can sense a specific UE communicating based on a sensing signal based on the UE-BS bistatic sensing.

[0400] - Here, for example, the sensing signal received by the serving base station may be a sensing signal based on non-3GPP sensing.

[0401] Here, for example, a serving base station can sense a specific UE communicating based on a sensing signal based on the above-mentioned non-3GPP sensing.

[0402] - Here, for example, the operation based on the threshold may be the operation based on the above event S2.

[0403] - - For example, if the threshold value is 0.7 (e.g., 70%), it can be said that the event S2 condition is satisfied if the LOS probability is 70% or less.

[0404] - Here, for example, parameters for the operation of Event S2 (e.g., threshold value and specific time, etc.) can be set. For instance, details regarding parameter settings may be written in the common section below.

[0405] For example, Step 2: The serving base station and / or SF may perform a sensing trigger. For example, the serving base station and / or SF may perform a sensing trigger based on Event S2. For example, the serving base station and / or SF may send a sensing request to a neighbor base station and / or UE. For example, the serving base station and / or SF may send a (tentative) SENSING REQUEST message to the neighbor base station and / or UE. For example, if the LOS probability of the sensing result is below a threshold (e.g., Event S2), the serving base station and / or SF may request the neighbor (neighbor) base station and / or UE to sense the UE.

[0406] - Here, for example, the serving base station and / or SF may send a (tentative) SENSING REQUEST message to request nearby (e.g., neighbor) base stations and / or UEs to sense the UE.

[0407] Here, for example, the serving base station and / or SF sends a sensing request message to the neighbor base station and / or UE and waits for the sensing result, and can predict the time to enter the NLoS interval based on the movement of the UE. For example, therefore, the serving base station and / or SF can specify the expected sensing response time from the neighbor base station when making a sensing request. For example, in Step 3 below, the neighbor base station can provide the sensing result within the set sensing response time.

[0408] For example, Step 3: The UE can transmit a sensing signal. For example, the neighbor base station can receive the sensing signal. For example, the neighbor base station can transmit a sensing response to the sensing base station. For example, the neighbor base station can transmit a (tentative) SENSING RESPONSE message to the sensing base station. For example, the neighbor base station that receives a sensing request (e.g., SENSING REQUEST message) can sense the corresponding UE and transmit the sensing result (e.g., SENSING RESPONSE message) to the serving base station. For example, it can be assumed that the neighbor base station and the UE are communicating, and the neighbor base station is in a state of UE-BS bistatic sensing.

[0409] - Here, for example, the Naver base station can sense the corresponding UE.

[0410] - Here, for example, the sensing signal received by the Naver base station may be a sensing signal based on UE-BS bistatic sensing.

[0411] Here, for example, the Naver base station can sense a specific UE communicating based on a sensing signal based on the above-mentioned UE-BS bistatic sensing.

[0412] - Here, for example, the sensing signal received by the Naver base station may be a sensing signal based on non-3GPP sensing.

[0413] Here, for example, the Naver base station can sense a specific UE communicating based on a sensing signal based on the above-mentioned non-3GPP sensing.

[0414] - Here, for example, the Naver base station can transmit the sensing result of the corresponding UE to the serving base station as a (tentative) SENSING RESPONSE message.

[0415] - Here, for example, the sensing result of the corresponding UE may refer to the measured LOS probability between the corresponding UE and each Naver base station.

[0416] Here, for example, the LOS probability can be expressed as a hard value, e.g., LOS or NLOS. For example, or as a soft value, e.g., a probability number. For example, 0.1 can mean that the probability of LOS is 10%. For example, if this value is 1.0, it can mean that the probability of LOS is 100%.

[0417] - Here, for example, the Naver base station can send the sensing result within the sensing response time received upon the sensing request.

[0418] For example, Step 4: The serving base station and / or SF may make a handover decision based on sensing. For example, the serving base station and / or SF may make a handover decision based on event S3. For example, the serving base station and / or SF may make a handover decision based on event S4. For example, the serving base station and / or SF may make a handover decision based on event S5. For example, the serving base station and / or SF may make a handover by comparing the LOS probability of the serving base station with the LOS probability of the neighbor base station (e.g., events S3 / S4 / S5).

[0419] - Here, for example, the handover operation decision can be performed by comparing the serving base station LOS probability and the neighbor base station LOS probability. For example, the event used for the operation decision can be determined by event S3 and / or event S4 and / or event S5.

[0420] Here, for example, parameter settings for events S3 / S4 / S5 can be set by the serving base station, the upper network, or the sensing server.

[0421] Here, for example, a handover is determined based on configured events. If one or more events are configured, the handover can be performed if at least one of the configured events is satisfied.

[0422] - Here, for example, the description for events S3 / S4 / S5 may be as follows.

[0423] For example, Event S3 may be a case where the LOS probability of the Naver base station is higher than the LOS probability of the serving base station by more than an offset.

[0424] For example, Event S4 is the case where the LOS probability of the Naver base station is higher than a specific threshold.

[0425] For example, Event S5 may be a case where the LOS probability of the serving base station is lower than a specific threshold, and the LOS probability of the Naver base station is higher than a specific threshold.

[0426] Here, for example, different values ​​can be used for the threshold compared with the serving base station LOS probability and the threshold compared with the Naver base station LOS probability.

[0427] For example, Step 5: The serving base station may transmit a handover request to the neighbor base station. For example, the serving base station may transmit a (tentative) HANDOVER REQUEST message to the neighbor base station. When a handover is determined, the serving base station (or sensing server) may send a handover request message to the appropriate neighbor base station. For example, subsequent operations may be similar or identical to the handover operations in the relevant technology. For example, therefore, a detailed description of subsequent operations including Step 5 may be omitted in this disclosure.

[0428] For example, during a handover utilizing the above-mentioned UE-BS bistatic sensing, it is possible to monitor whether a case occurs where the LOS probability of the sensing result exceeds a specific threshold (e.g., Event S1). For example, if Event S1 occurs (e.g., if the LOS probability of the corresponding UE improves above the threshold), the ongoing handover procedure may be stopped or terminated. For example, in such a case, the serving base station may send a sensing stop message (tentative name) SENSING STOP message to the neighbor base station. For example, the neighbor base station that receives the SENSING STOP message may stop the currently operating sensing operation and not perform subsequent procedures.

[0429] For example, the common items applicable to the above procedure may be as follows.

[0430] - For example, the various event-specific thresholds used in the above procedure can be set to different values.

[0431] - For example, in the above procedure, to compensate for instantaneously changing LOS probabilities, the operation may be configured to take an average over a specific period, or to trigger an event only when the state above or below a threshold is maintained for a specific period. For example, to this end, when setting the threshold value, a specific time for taking the average and / or a specific time for maintaining the state above or below the threshold may be set together.

[0432] - For example, in the above procedure, parameters such as thresholds and specific times may be set by the Serving / Naver base station or the sensing server. For example, they may be defined as specific values ​​(e.g., explicitly) in a standard document. For example, they may be set by varying to optimized values ​​calculated by AI / ML. For example, additionally, when a sensing request is made to the Naver base station, the Serving / Naver base station or the sensing server may transmit a message including these parameter values.

[0433] For example, in the present disclosure, a base station (BS) may include one or more TRPs. For example, although the present disclosure is based on handover between different base stations, handover between TRPs within a single base station may be supported in the same way.

[0434] For example, in the above method and procedure, it may be assumed that the base station can pair information about a UE currently communicating (e.g., requiring a handover) with sensing results for that UE. For example, it may be assumed that the base station can determine the location of the UE (e.g., absolute or relative) and distinguish the sensing results of the UE from the sensing results. For example, this information may be utilized when the serving base station requests sensing of the UE from the neighbor base station. For example, the serving base station (or sensing server) may set the target sensing area (TSA) to the UE. Here, for example, the method of distinguishing the UE (e.g., setting the TSA) and the pairing of sensing results are not core matters of the present disclosure, so a detailed description may be omitted.

[0435] For example, the base station can use BS monostatic sensing mode. For example, the base station can use UE-BS bistatic sensing mode. For example, the base station can use a combination of BS monostatic sensing mode and UE-BS bistatic sensing mode (e.g., joint / hybrid).

[0436] For example, the sensing results used in the present disclosure (e.g., LOS information obtained by sensing measurement) may utilize sensing results obtained from non-3GPP sensing, such as radar / camera / lidar, as well as 3GPP sensing using 3GPP signals. For example, parameters such as thresholds and specific times used in the procedure may also be set differently depending on the type of sensor used (e.g., 3GPP sensing or non-3GPP sensing).

[0437] For example, in the above procedure, the serving base station may trigger a 3GPP sensing operation based on non-3GPP sensing results. For example, if the LOS probability decreases based on the non-3GPP sensing results, a 3GPP sensing operation may be performed to obtain more accurate sensing results. For example, conversely, a non-3GPP sensing operation may be triggered based on 3GPP sensing results. For example, this may be configured by considering the difference in accuracy between the 3GPP sensing operation and the non-3GPP sensing operation, as well as the required current consumption. For example, additionally, this operation may be used as a trigger condition for a sensing operation between the serving base station and the neighbor base station.

[0438] FIG. 25 illustrates an example of a BS monostatic sensing-based handover procedure according to one embodiment of the present disclosure. The embodiment of FIG. 25 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted. For example, a dotted line in FIG. 25 may indicate an operation that may be omitted.

[0439] FIG. 26 illustrates an example of a BS monostatic sensing-based handover procedure according to one embodiment of the present disclosure. The embodiment of FIG. 26 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted. For example, a dotted line in FIG. 26 may indicate an operation that may be omitted.

[0440] Referring to FIGS. 25 and 26, a handover procedure based on BS monostatic sensing can be illustrated, for example, when a sensing server is located on a core network.

[0441] For example, the event conditions proposed in the present disclosure may be (tentative) Event S1, Event S2, Event S3, Event S4, and Event S5.

[0442] - For example, Event S1: When the serving LOS probability becomes higher than the threshold (e.g., Serving LOS probability becomes higher than threshold)

[0443] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0444] - For example, Event S2: When the Serving LOS probability becomes lower than the threshold (e.g., Serving LOS probability becomes lower than threshold)

[0445] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0446] - For example, Event S3: The case where the Neighbour LOS probability becomes higher than the Serving LOS probability by an offset amount (e.g., Neighbour LOS probability becomes offset higher than Serving LOS probability)

[0447] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0448] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0449] - For example, Event S4: When the Neighbour LOS probability becomes higher than the threshold (e.g., Neighbour LOS probability becomes higher than threshold)

[0450] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0451] - For example, Event S5: When the Serving LOS probability becomes lower than threshold 1 and the neighbor LOS probability becomes higher than threshold 2 (e.g., Serving LOS probability becomes lower than threshold 1 and neighbor LOS probability becomes higher than threshold 2)

[0452] Here, the serving LOS can be the LOS between the serving base station and the UE.

[0453] Here, Naver LOS can be the LOS between the Naver base station and the UE.

[0454] For example, in the disclosures related to FIG. 21 and FIG. 21, a procedure may be described in which a sensing server (sensing function, SF) is located at a serving base station, or in which direct communication between a serving base station supporting sensing and a neighbor base station is performed without a special sensing server. For example, in the disclosures related to FIG. 22 and FIG. 22, a procedure may be described in which a sensing server (sensing function, SF) is located at a serving base station, or in which direct communication between a serving base station supporting sensing and a neighbor base station is performed without a special sensing server. For example, additionally, the sensing server may be located on the core network. For example, in this case, the BS sensing-based handover procedure may be as shown in FIG. 23. For example, in such a procedure, sensing-related processing, such as processing sensing requests and sensing responses, may be performed by a sensing server located on the core network (e.g., not through direct communication between a serving base station and a neighbor base station). For example, the message sender / receiver may vary depending on the location of the sensing server, but there may be no difference in the essential method of the present disclosure.

[0455] Referring to FIG. 23, for example, the handover method and procedure proposed in the present disclosure may be as follows.

[0456] For example, Step 0: The serving base station can transmit measurement settings to the UE. For example, it can be assumed that the serving base station and the UE are communicating, and the serving base station is in a state of BS monostatic sensing.

[0457] For example, if sensing is being performed based on a sensing session established between a sensing server and a base station, it can be assumed that a sensing session is established between the sensing server and the base station. However, since sensing operations are possible without establishing a sensing session, the establishment of a sensing session itself may not be a prerequisite for such operations.

[0458] - For example, it can be assumed that a sensing server (sensing function, SF) is located on the core network. For example, it can be assumed that session setup and / or parameter setup required for the sensing operation of a nearby (e.g., Naver) base station is performed before and during the sensing operation.

[0459] - Here, for example, the serving base station (or sensing server) can set the TSA (target sensing area) to the corresponding UE.

[0460] For example, Step 1: The serving base station and / or UE may transmit a sensing signal. For example, the serving base station may receive a sensing signal. For example, the serving base station may transmit a sensing report to the SF. For example, the serving base station may transmit a (tentative) SENSING REPORT message to the SF. For example, the serving base station may sense a specific UE that is communicating and monitor whether the LOS probability of the sensing result is below a threshold (e.g., Event S2).

[0461] - Here, for example, the sensing signal received by the serving base station may be a sensing signal based on BS monostatic sensing.

[0462] Here, for example, the serving base station can sense a specific UE communicating based on a sensing signal based on the BS monostatic sensing.

[0463] - Here, for example, the sensing signal received by the serving base station may be a sensing signal based on non-3GPP sensing.

[0464] Here, for example, a serving base station can sense a specific UE communicating based on a sensing signal based on the above-mentioned non-3GPP sensing.

[0465] - Here, for example, the operation based on the threshold may be the operation based on the above event S2.

[0466] - - For example, if the threshold value is 0.7 (e.g., 70%), it can be said that the event S2 condition is satisfied if the LOS probability is 70% or less.

[0467] - Here, for example, parameters for the operation of Event S2 (e.g., threshold value and specific time, etc.) can be set. For instance, details regarding parameter settings may be written in the common section below.

[0468] For example, Step 2: SF can perform a sensing trigger. For example, SF can perform a sensing trigger based on Event S2. For example, SF can send a sensing request to a neighbor base station. For example, SF can send a (tentative) SENSING REQUEST message to a neighbor base station. For example, if the LOS probability of the sensing result is below a threshold (e.g., Event S2), SF can request a nearby (neighbor) base station to sense the corresponding UE.

[0469] - Here, for example, SF can send a (tentative) SENSING REQUEST message to request sensing of the UE from nearby (e.g., Naver) base stations.

[0470] Here, for example, the SF sends a sensing request message to the Naver base station and waits for the sensing result, and can predict the time it takes to enter the NLoS interval based on the movement of the UE. For example, therefore, the SF can specify the expected sensing response time from the Naver base station when making a sensing request. For example, in Step 3 below, the Naver base station can provide the sensing result within the set sensing response time.

[0471] For example, Step 3: The neighbor base station and / or UE may transmit a sensing signal. For example, the neighbor base station may receive a sensing signal. For example, the neighbor base station may transmit a sensing response to the sensing base station. For example, the neighbor base station may transmit a (tentative) SENSING RESPONSE message to the sensing base station. For example, the neighbor base station that receives a sensing request (e.g., SENSING REQUEST message) may sense the corresponding UE and transmit the sensing result (e.g., SENSING RESPONSE message) to the serving base station. For example, it can be assumed that the neighbor base station and the UE are communicating, and the neighbor base station is in a state of BS monostatic sensing.

[0472] - Here, for example, the Naver base station can sense the corresponding UE.

[0473] - Here, for example, the sensing signal received by the Naver base station may be a sensing signal based on BS monostatic sensing.

[0474] Here, for example, the Naver base station can sense a specific UE communicating based on a sensing signal based on the above BS monostatic sensing.

[0475] - Here, for example, the sensing signal received by the Naver base station may be a sensing signal based on non-3GPP sensing.

[0476] Here, for example, the Naver base station can sense a specific UE communicating based on a sensing signal based on the above-mentioned non-3GPP sensing.

[0477] - Here, for example, the Naver base station can transmit the sensing result of the corresponding UE to the serving base station as a (tentative) SENSING RESPONSE message.

[0478] - Here, for example, the sensing result of the corresponding UE may refer to the measured LOS probability between the corresponding UE and each Naver base station.

[0479] Here, for example, the LOS probability can be expressed as a hard value, e.g., LOS or NLOS. For example, or as a soft value, e.g., a probability number. For example, 0.1 can mean that the probability of LOS is 10%. For example, if this value is 1.0, it can mean that the probability of LOS is 100%.

[0480] - Here, for example, the Naver base station can send the sensing result within the sensing response time received upon the sensing request.

[0481] For example, Step 4: The SF can trigger a handover. For example, the SF can trigger a handover based on Event S3. For example, the SF can trigger a handover based on Event S4. For example, the SF can trigger a handover based on Event S5. For example, the SF can trigger a handover by comparing the LOS probability of the serving base station with the LOS probability of the neighbor base station (e.g., Events S3 / S4 / S5). For example, the SF can transmit a sensing analysis to the serving base station. For example, the SF can transmit a (tentative) SENSING ANALYSIS message to the serving base station. For example, the sensing base station can perform a handover decision. For example, the sensing base station can perform a handover decision based on the above sensing analysis.

[0482] - Here, for example, the handover trigger can be performed by comparing the serving base station LOS probability and the neighbor base station LOS probability. For example, the event used to determine the corresponding action can be determined by event S3 and / or event S4 and / or event S5.

[0483] Here, for example, parameter settings for events S3 / S4 / S5 can be set by the serving base station, the upper network, or the sensing server.

[0484] Here, for example, a handover is triggered based on configured events. If one or more events are configured, the handover can be performed if at least one of the configured events is satisfied.

[0485] - Here, for example, the description for events S3 / S4 / S5 may be as follows.

[0486] For example, Event S3 may be a case where the LOS probability of the Naver base station is higher than the LOS probability of the serving base station by more than an offset.

[0487] For example, Event S4 is the case where the LOS probability of the Naver base station is higher than a specific threshold.

[0488] For example, Event S5 may be a case where the LOS probability of the serving base station is lower than a specific threshold, and the LOS probability of the Naver base station is higher than a specific threshold.

[0489] Here, for example, different values ​​can be used for the threshold compared with the serving base station LOS probability and the threshold compared with the Naver base station LOS probability.

[0490] For example, Step 5: The serving base station may transmit a handover request to the neighbor base station. For example, the serving base station may transmit a (tentative) HANDOVER REQUEST message to the neighbor base station. When a handover is determined, the serving base station (or sensing server) may send a handover request message to the appropriate neighbor base station. For example, subsequent operations may be similar or identical to the handover operations in the relevant technology. For example, therefore, a detailed description of subsequent operations including Step 5 may be omitted in this disclosure.

[0491] For example, during the handover operation utilizing the above-mentioned BS monostatic sensing, it is possible to monitor whether a case occurs where the LOS probability of the sensing result becomes higher than a specific threshold (e.g., Event S1). For example, if Event S1 occurs (e.g., if the LOS probability of the corresponding UE improves above the threshold), the ongoing handover procedure may be stopped or terminated. For example, in such a case, the serving base station may send a sensing stop message (tentative name) SENSING STOP message to the neighbor base station. For example, the neighbor base station that receives the SENSING STOP message may stop the currently operating sensing operation and not perform subsequent procedures.

[0492] For example, the common items applicable to the above procedure may be as follows.

[0493] - For example, the various event-specific thresholds used in the above procedure can be set to different values.

[0494] - For example, in the above procedure, to compensate for instantaneously changing LOS probabilities, the operation may be configured to take an average over a specific period, or to trigger an event only when the state above or below a threshold is maintained for a specific period. For example, to this end, when setting the threshold value, a specific time for taking the average and / or a specific time for maintaining the state above or below the threshold may be set together.

[0495] - For example, in the above procedure, parameters such as thresholds and specific times may be set by the Serving / Naver base station or the sensing server. For example, they may be defined as specific values ​​(e.g., explicitly) in a standard document. For example, they may be set by varying to optimized values ​​calculated by AI / ML. For example, additionally, when a sensing request is made to the Naver base station, the Serving / Naver base station or the sensing server may transmit a message including these parameter values.

[0496] For example, in the present disclosure, a base station (BS) may include one or more TRPs. For example, although the present disclosure is based on handover between different base stations, handover between TRPs within a single base station may be supported in the same way.

[0497] For example, in the above method and procedure, it may be assumed that the base station can pair information about a UE currently communicating (e.g., requiring a handover) with sensing results for that UE. For example, it may be assumed that the base station can determine the location of the UE (e.g., absolute or relative) and distinguish the sensing results of the UE from the sensing results. For example, this information may be utilized when the serving base station requests sensing of the UE from the neighbor base station. For example, the serving base station (or sensing server) may set the target sensing area (TSA) to the UE. Here, for example, the method of distinguishing the UE (e.g., setting the TSA) and the pairing of sensing results are not core matters of the present disclosure, so a detailed description may be omitted.

[0498] For example, the base station can use BS monostatic sensing mode. For example, the base station can use UE-BS bistatic sensing mode. For example, the base station can use a combination of BS monostatic sensing mode and UE-BS bistatic sensing mode (e.g., joint / hybrid).

[0499] For example, the sensing results used in the present disclosure (e.g., LOS information obtained by sensing measurement) may utilize sensing results obtained from non-3GPP sensing, such as radar / camera / lidar, as well as 3GPP sensing using 3GPP signals. For example, parameters such as thresholds and specific times used in the procedure may also be set differently depending on the type of sensor used (e.g., 3GPP sensing or non-3GPP sensing).

[0500] For example, in the above procedure, the serving base station may trigger a 3GPP sensing operation based on non-3GPP sensing results. For example, if the LOS probability decreases based on the non-3GPP sensing results, a 3GPP sensing operation may be performed to obtain more accurate sensing results. For example, conversely, a non-3GPP sensing operation may be triggered based on 3GPP sensing results. For example, this may be configured by considering the difference in accuracy between the 3GPP sensing operation and the non-3GPP sensing operation, as well as the required current consumption. For example, additionally, this operation may be used as a trigger condition for a sensing operation between the serving base station and the neighbor base station.

[0501] Combinations of various embodiments of the present disclosure may be applied differently depending on the payload type of the satellite (e.g., regenerative payload or transparent payload).

[0502] Combinations of various embodiments of the present disclosure may be applied differently to the type of non-geostational network node (e.g., GEO (geostationary earth orbit), NGEO (non-geostationary earth orbit), LEO (low earth orbit), MEO (medium earth orbit), HASP (high altitude satellite platform), drone) or altitude or fixed beam footprint or cell-moving beam footprint.

[0503] For example, in the embodiments of the present disclosure, the TDD setting and utilization are not limited to the TDD band, and can be extended to the FDD band and / or a combination of specific DL band and / or UL band.

[0504] For example, in an embodiment of the present disclosure, a base station or network node may be a satellite. For example, a base station or network node may be associated with a transparent payload. For example, a base station or network node may be associated with a regenerated payload.

[0505] A combination of embodiments of the present disclosure may operate in conjunction with each other.

[0506] Various embodiments of the present disclosure may be applied differently depending on the link type (DL, UL, SL) and / or the data type (SIB, group cast, unicast) and / or the search space type (CSS (common search space), USS (UE-specific search space)) where the scheduling PDCCH is detected and / or the base station node type and / or altitude and / or whether there is a power constraint. For example, a combination of various embodiments of the present disclosure may be applied only when involved in SIB transmission.

[0507] For example, in the present disclosure, the machine learning model may be an AI / ML model.

[0508] For example, in the present disclosure, a base station or network may be a TRP and / or an NB and / or an AMF and / or a (system) core. For example, in the present disclosure, an NB may be an AMF and / or a (system) core. For example, in the present disclosure, a system core may be an AMF and / or a (system) core.

[0509] For example, in the present disclosure, a sensing signal may be interpreted as having the same meaning as a sensing reference signal.

[0510] For example, in the present disclosure, sensing data may be interpreted as having the same meaning as sensing measurement data or sensing measurement report.

[0511] For example, the embodiments of the present disclosure may be extended to all of the above six sensing scenarios. For example, the embodiments of the present disclosure may be applicable to all of the above six sensing scenarios.

[0512] For example, the methods proposed in this disclosure can be applied to both 3GPP sensing data and non-3GPP sensing data.

[0513] For example, in the present disclosure, sensing data may be data derived by a sensing radio measurement entity based on radio signals (e.g., reflected, refracted, diffracted) affected by an object or environment of interest for the purpose of sensing. For example, this data may be raw measurements and may optionally be further processed within the sensing radio measurement entity. For example, the sensing data may include at least one of 3GPP sensing data or non-3GPP sensing data.

[0514] For example, in the present disclosure, 3GPP sensing data is data obtained from 3GPP radio signals that have been affected (e.g., reflected, refracted, diffracted) by an object or environment of interest for the purpose of sensing, and may optionally be processed within a 5G system.

[0515] For example, in the present disclosure, non-3GPP sensing data may be data provided by a non-3GPP sensor (e.g., video, LiDAR, sonar) regarding an object or environment of interest for the purpose of sensing.

[0516] For example, in the present disclosure, 5G / 6G radio sensing may be a 5GS / 6GS function that provides a function to acquire information about the characteristics of an environment and / or objects within the environment (e.g., shape, size, orientation, speed, location, distance, relative movement between objects, etc.) using NR radio frequency signals, and may, in some cases, be extended by information generated through a previously defined function in the EPC and / or E-UTRAN.

[0517] For example, in the present disclosure, sensing auxiliary information may be information provided to a 5G system from a trusted third party and may be used to support the derivation of sensing results. This information may not include 3GPP sensing data. For example, examples of sensing auxiliary information may include map information, location information, a UE identifier (ID) attached to or located near a sensing target, UE location information, UE velocity information, etc.

[0518] For example, in the present disclosure, sensing context information may be information that a 5G / 6G system exposes to a trusted third party along with the sensing results, and may provide context regarding the conditions under which the sensing results were derived. This information may not include 3GPP sensing data. For example, examples of sensing context information may include map information, location information, time of capture, UE location, and ID. This context information may be required in scenarios where the sensing results need to be combined with data from other sources outside of 5GS.

[0519] For example, in the present disclosure, a sensing group may be a set of sensing transmitters and sensing receivers whose locations are known and capable of synchronously collecting sensing data.

[0520] For example, in the present disclosure, a sensing receiver may be an entity that receives a sensing signal used by a sensing service in operation. The sensing receiver may be a RAN node or part of a UE. The sensing receiver may be located in the same entity as the sensing transmitter or in a different entity.

[0521] For example, in the present disclosure, the sensing result may be processed 3GPP sensing data requested by a service consumer.

[0522] For example, in the present disclosure, a sensing signal may be a transmission signal on a 3GPP radio interface that can be used for sensing purposes. For example, this definition may refer to NR radio frequency signals and, in some cases, may be extended to information generated from existing functions of the EPC and / or E-UTRAN.

[0523] For example, a sensing transmitter may be an entity that transmits a sensing signal used by a sensing service in an operation. A sensing transmitter may be part of a RAN node or a UE. A sensing transmitter may be located in the same entity as a sensing receiver or in a different entity.

[0524] For example, the target sensing service area may be an orthogonal coordinate location area that satisfies a specific sensing service quality and is to be sensed by deriving the characteristics of the environment and / or objects within the environment from 3GPP radio signals that have been affected (e.g., reflected, refracted, diffracted). This may include both indoor and outdoor environments.

[0525] For example, the present disclosure may be applied to base stations (e.g., TRP) and / or terminal monostatics. For example, the present disclosure may also be applied to base station-base station (e.g., TRP-TRP), base station-UE (e.g., TRP-UE), UE-base station (e.g., UE-TRP), and / or UE-UE bistatics.

[0526] For example, in the present disclosure, "specific threshold" may mean a threshold that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "specific set value" may mean a value that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "set by the network / base station" may mean an action in which a base station sets to a UE (pre-) through upper layer RRC signaling, sets / signals to a UE through MAC CE, or signals to a UE through DCI.

[0527] For example, in the present disclosure, a message may be interpreted as being replaced by at least one of a control message, a data message, a signal, a data signal, and / or a control signal.

[0528] For example, in this disclosure, various names are exemplary and may be replaced or considered as other names performing the same or similar functions based on the content described in each step (regardless of the name).

[0529] For example, in the present disclosure, the bandwidth part (BWP) may be replaced with a bandwidth setting set or a wireless resource set, etc.

[0530] For example, in the present disclosure, the wireless resource profile exemplified may be applied as a BWP (bandwidth part), a bandwidth setting set, a wireless resource set, etc.

[0531] For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to the resource pool (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to the congestion level (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to the service priority (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to the service type (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically to QoS requirements (e.g., latency, reliability) (or differently or independently). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) to PQI (5QI (5G QoS identifier) ​​for PC5). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) to traffic types (e.g., periodic generation or non-periodic generation). For example, the applicability of (some) proposed methods / rules of the present disclosure and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) to SL transmission resource allocation modes (e.g., Mode 1 or Mode 2).For example, whether the (some) proposed methods / rules of the present disclosure apply and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set to a Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not support sidelink DRX operation).

[0532] For example, the applicability of the proposed rules of the present disclosure and / or the related parameter setting values ​​may be specifically (or differently or independently) set depending on whether PUCCH setting is supported (e.g., when a PUCCH resource is set or when a PUCCH resource is not set). For example, the applicability of the proposed rules of the present disclosure and / or the related parameter setting values ​​may be specifically (or differently or independently) set for a resource pool (e.g., a resource pool where PSFCH is set or a resource pool where PSFCH is not set). For example, the applicability of the proposed rules of the present disclosure and / or the related parameter setting values ​​may be specifically (or differently or independently) set for the type of service / packet. For example, the applicability of the proposed rules of the present disclosure and / or the related parameter setting values ​​may be specifically (or differently or independently) set for the priority of the service / packet. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be set specifically (or differently or independently) to a QoS profile or QoS requirements (e.g., URLLC / EMBB traffic, reliability, latency). For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be set specifically (or differently or independently) to a PQI. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be set specifically (or differently or independently) to a PFI. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be set specifically (or differently or independently) to a cast type (e.g., unicast, groupcast, broadcast). For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be set specifically (or differently or independently) to a (resource pool) congestion level (e.g., CBR).For example, whether the proposed rule of the present disclosure applies and / or the related parameter setting value may be set specifically (or differently or independently) to an SL HARQ feedback method (e.g., NACK-only feedback, ACK / NACK feedback). For example, whether the proposed rule of the present disclosure applies and / or the related parameter setting value may be set specifically (or differently or independently) to HARQ Feedback Enabled MAC PDU transmission. For example, whether the proposed rule of the present disclosure applies and / or the related parameter setting value may be set specifically (or differently or independently) to HARQ Feedback Disabled MAC PDU transmission. For example, whether the proposed rule of the present disclosure applies and / or the related parameter setting value may be set specifically (or differently or independently) depending on whether a PUCCH-based SL HARQ feedback reporting operation is enabled. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be specifically (or differently or independently) set depending on whether pre-emption or pre-emption-based resource reselection is performed. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be specifically (or differently or independently) set depending on whether re-evaluation or re-evaluation-based resource reselection is performed. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be specifically (or differently or independently) set to the (L2 or L1) (source and / or destination) identifier. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting values ​​may be specifically (or differently or independently) set to the (L2 or L1) (combination of source ID and destination ID) identifier.For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) to the identifier (L2 or L1) (combination of the pair of source ID and destination ID and cast type). For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) to the direction of the pair of source layer ID and destination layer ID. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) to the PC5 RRC connection / link. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) depending on whether SL DRX is performed. For example, the applicability of the proposal rule of the present disclosure and / or the related parameter setting value may be set specifically (or differently or independently) depending on whether SL DRX is supported. For example, whether the proposed rules of the present disclosure apply and / or the related parameter setting values ​​may be set specifically (or differently or independently) to an SL mode type (e.g., resource allocation mode 1 or resource allocation mode 2). For example, whether the proposed rules of the present disclosure apply and / or the related parameter setting values ​​may be set specifically (or differently or independently) to cases where (non)periodic resource reservation is performed. For example, whether the proposed rules of the present disclosure apply and / or the related parameter setting values ​​may be set specifically (or differently or independently) to a Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not support sidelink DRX operation).

[0533] The applicability of the proposals and proposal rules of the present disclosure (and / or related parameter setting values) may also apply to mmWave sidelink operations.

[0534] For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to the service type (or differently or independently). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to the priority (LCH or service) (or differently or independently). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to QoS requirements (e.g., latency, reliability, minimum communication range) (or differently or independently). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to the PQI parameter (or differently or independently). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to the SL HARQ feedback ENABLED LCH / MAC PDU (transmission) (or differently or independently). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL HARQ feedback DISABLED LCH / MAC PDU (transmission). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to CBR measurement values ​​of the resource pool. For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL cast type (e.g., unicast, groupcast, broadcast).For example, the application status of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL GroupCast HARQ feedback options (e.g., NACK only feedback, ACK / NACK feedback, TX-RX distance-based NACK only feedback). For example, the application status of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL Mode 1 CG type (e.g., SL CG type 1 or SL CG type 2). For example, the application status of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to SL Mode type (e.g., Mode 1 or Mode 2). For example, the application status of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to resource pool. For example, the parameter values ​​regarding the applicability of the above rule and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) depending on whether the PSFCH resource is a resource pool where it is configured. For example, the parameter values ​​regarding the applicability of the above rule and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) depending on the source (L2) ID. For example, the parameter values ​​regarding the applicability of the above rule and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) depending on the destination (L2) ID. For example, the parameter values ​​regarding the applicability of the above rule and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) depending on the PC5 RRC connection link.For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to the SL link (or differently or independently). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to the connection status (e.g., RRC CONNECTED status, IDLE status, INACTIVE status) (or differently or independently). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to the SL HARQ process (ID) (or differently or independently). For example, the applicability of the above rule and / or parameter values ​​related to the proposed method / rule of the present disclosure may be set / allowed specifically to the SL DRX operation (of the TX UE or RX UE) (or differently or independently). For example, the parameter values ​​regarding whether the above rule applies and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to the power saving (TX or RX) UE. For example, the parameter values ​​regarding whether the above rule applies and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to the case where PSFCH TX and PSFCH RX overlap (and / or multiple PSFCH TXs exceeding the UE's capability) (and / or where PSFCH TX (and / or PSFCH RX) are omitted) from the perspective of a specific UE. For example, the parameter values ​​regarding whether the above rule applies and / or the proposed method / rule of the present disclosure may be set / allowed specifically (or differently or independently) to the case where the RX UE actually (successfully) receives a PSCCH (and / or PSSCH) (re)transmission from the TX UE.

[0535] For example, the setting (or designation) wording in the present disclosure may be interpreted in an extended manner, such as a form in which a base station informs a terminal through a predefined (physical layer or upper layer) channel / signal (e.g., SIB, RRC, MAC CE) (and / or a form provided through pre-configuration and / or a form in which a terminal informs another terminal through a predefined (physical layer or upper layer) channel / signal (e.g., SL MAC CE, PC5 RRC)).

[0536] For example, the PSFCH wording in the present disclosure may be extended to (NR or LTE) PSSCH (and / or (NR or LTE) PSCCH) (and / or (NR or LTE) SL SSB (and / or UL channel / signal)). Additionally, the proposed methods of the present disclosure may be combined with each other and extended (in a new form).

[0537] For example, in the present disclosure, a specific threshold value may refer to a threshold value that is predefined or set (in advance) by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, a specific setting value may refer to a value that is predefined or set (in advance) by an upper layer (including the application layer) of a network, base station, or terminal. For example, an operation set by a network / base station may refer to an operation in which the base station sets (in advance) to the UE through upper layer RRC signaling, sets / signals to the UE through MAC CE, or signals to the UE through DCI.

[0538] The operation of the present disclosure can be applied to all side-link unicast / group cast / broadcast operations.

[0539] In an embodiment of the present disclosure, the message may be interpreted as being replaced with a control message or a data message or a signal or a data signal or a control signal.

[0540] In an embodiment of the present disclosure, a beam management operation may be interpreted as being replaced by beam selection or spatial filter selection or beam pairing or spatial filter pairing or beam failure recovery or spatial filter recovery or beam sweeping or spatial filter sweeping or beam switching or spatial filter switching or measurement of a reference signal resource or measurement of a reference signal resource reporting operation or beam reporting or spatial filter reporting, etc.

[0541] In an embodiment of the present disclosure, the beam may be interpreted by replacing it with an RS or an RS resource or a spatial filter resource.

[0542] In an embodiment of the present disclosure, RS can be interpreted as being replaced by an RS resource or a spatial filter resource.

[0543] In an embodiment of the present disclosure, the transmission terminal may be interpreted as being replaced with a terminal that transmits a beam, a terminal that transmits a beam RS, or a terminal that transmits a beam RS resource.

[0544] In an embodiment of the present disclosure, the receiving terminal may be interpreted as being replaced with a terminal receiving a beam, a terminal receiving a beam RS, or a terminal receiving a beam RS resource.

[0545] In an embodiment of the present disclosure, the transmission beam or reception beam information transmitted and received by the terminal may be interpreted as being replaced with resource information of a reference signal (RS) associated with the transmission beam and resource information of a reference signal (RS) associated with the reception beam.

[0546] In the embodiments of the present disclosure, the DCR (direct communication request) and / or DCA (direct communication accept) messages may be interpreted as being replaced by the PC5-S DCR and / or PC5-S DCA messages, etc.

[0547] In embodiments of the present disclosure, spatial setting and / or transmission configuration indication (TCI) information and / or quasi-co-location (QCL) information and / or beams, etc., may refer to each other and / or may be interpreted as being replaced by beam-related information, beam direction, spatial domain transmission or reception filter, etc.

[0548] In an embodiment of the present disclosure, the beam may be interpreted as being replaced by a transmitting beam or a receiving beam or a spatial filter or a spatial transmission (TX) filter or a spatial area transmission (TX) filter or a spatial reception (RX) filter or a spatial area reception (RX) filter.

[0549] In an embodiment of the present disclosure, the transmit / transmit beam may be interpreted as being replaced by a spatial transmission (TX) filter or a spatial area transmission (TX) filter.

[0550] In an embodiment of the present disclosure, the receiving beam may be interpreted as being replaced by a spatial receiving (RX) filter or a spatial area receiving (RX) filter.

[0551] In an embodiment of the present disclosure, the fact that the spatial setting information (or beam information) for transmission is identical may mean that the spatial area TX filter of the terminal is identical for two different transmission signals. In an embodiment of the present disclosure, the fact that the spatial setting information (or beam information) for reception is identical may mean that two different reception signals are in a QCL 'TypeD' relationship and / or have a relationship using the same spatial RX parameter.

[0552] For example, the control message (or signal) and / or data message (or signal) in the present disclosure may mean a control message (or signal) and / or data message (or signal) for wireless communication (e.g., LTE communication, NR communication, 6G communication, Wi-Fi communication, Bluetooth communication, and / or other wireless communication) that is not a radar signal.

[0553] For example, the source ID and destination ID disclosed in the present disclosure may mean a source layer 1 ID and a destination layer 1 ID and / or a source layer 2 ID and a destination layer 2 ID.

[0554] FIG. 27 illustrates a procedure performed by a first device according to one embodiment of the present disclosure. The embodiment of FIG. 27 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0555] Referring to FIG. 27, in step S2710, the first device can acquire a sensing signal. In step S2720, based on the sensing signal, the first device can acquire a sensing result based on a line of sight (LOS) associated with the second device. In step S2730, based on the sensing result based on the LOS associated with the second device, the first device can determine whether to perform a handover of the second device.

[0556] For example, the handover of the second device may be determined not to be performed based on the fact that the LOS probability between the first device and the second device becomes higher than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE (user equipment).

[0557] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE.

[0558] For example, the handover of the second device may be determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a neighbor base station.

[0559] For example, the handover of the second device may be determined to be performed based on the LOS probability between the third device and the second device becoming higher than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0560] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0561] For example, the above sensing signal can be acquired based on a BS (base station) monostatic.

[0562] For example, the above sensing signal can be acquired based on UE-BS bistatic.

[0563] For example, the above sensing signal may be a non-3GPP (non-3rd generation partnership project) sensing signal.

[0564] For example, the sensing function may be located on the first device. For example, the first device may be a serving base station. For example, the second device may be a UE.

[0565] For example, based on the fact that the LOS probability between the first device and the second device becomes lower than a threshold value, the first device may transmit a sensing request to the third device. For example, based on the transmission of the sensing request, the first device may obtain the LOS probability between the third device and the second device. For example, the handover of the second device may be determined to be performed based on at least one of the LOS probability between the first device and the second device and the LOS probability between the third device and the second device. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0566] For example, the handover of the second device may be determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device.

[0567] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2.

[0568] The proposed method above may be applied to a device according to various embodiments of the present disclosure. For example, a processor (102) of a first device (100) may acquire a sensing signal (for example, the processor (102) of the first device (100) may control a transceiver (106) to acquire a sensing signal). For example, the processor (102) of the first device (100) may acquire a sensing result based on a line of sight (LOS) related to a second device based on the sensing signal (for example, the processor (102) of the first device (100) may control a transceiver (106) to acquire a sensing result based on a line of sight (LOS) related to a second device based on the sensing signal). For example, the processor (102) of the first device (100) may determine whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device (for example, the processor (102) of the first device (100) may control the transceiver (106) to determine whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device).

[0569] According to one embodiment of the present disclosure, a first device may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the first device, based on execution by the at least one processor: to acquire a sensing signal; to acquire a sensing result based on a line of sight (LOS) associated with a second device based on the sensing signal; and to determine whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

[0570] For example, the handover of the second device may be determined not to be performed based on the fact that the LOS probability between the first device and the second device becomes higher than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE (user equipment).

[0571] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE.

[0572] For example, the handover of the second device may be determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a neighbor base station.

[0573] For example, the handover of the second device may be determined to be performed based on the LOS probability between the third device and the second device becoming higher than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0574] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0575] For example, the above sensing signal can be acquired based on a BS (base station) monostatic.

[0576] For example, the above sensing signal can be acquired based on UE-BS bistatic.

[0577] For example, the above sensing signal may be a non-3GPP (non-3rd generation partnership project) sensing signal.

[0578] For example, the sensing function may be located on the first device. For example, the first device may be a serving base station. For example, the second device may be a UE.

[0579] For example, based on the fact that the LOS probability between the first device and the second device becomes lower than a threshold value, the first device may transmit a sensing request to the third device. For example, based on the transmission of the sensing request, the first device may obtain the LOS probability between the third device and the second device. For example, the handover of the second device may be determined to be performed based on at least one of the LOS probability between the first device and the second device and the LOS probability between the third device and the second device. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0580] For example, the handover of the second device may be determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device.

[0581] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2.

[0582] According to one embodiment of the present disclosure, a processing device (configured to control a first device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the first device, based on execution by the at least one processor: to acquire a sensing signal; to acquire a sensing result based on a line of sight (LOS) associated with a second device based on the sensing signal; and to determine whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

[0583] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the first device may: acquire a sensing signal; acquire a sensing result based on a line of sight (LOS) associated with a second device based on the sensing signal; and determine whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

[0584] FIG. 28 illustrates a procedure performed by a second device according to one embodiment of the present disclosure. The embodiment of FIG. 28 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0585] Referring to FIG. 28, at step S2810, the second device may receive a radio resource control (RRC) reset message from the first device. At step S2820, the second device may perform a handover based on the RRC reset message. For example, the RRC reset message may include information related to the handover of the second device. For example, the information related to the handover of the second device may be based on sensing results based on the line of sight (LOS) associated with the second device.

[0586] For example, the handover of the second device may be determined not to be performed based on the fact that the LOS probability between the first device and the second device becomes higher than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE (user equipment).

[0587] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE.

[0588] For example, the handover of the second device may be determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a neighbor base station.

[0589] For example, the handover of the second device may be determined to be performed based on the LOS probability between the third device and the second device becoming higher than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0590] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0591] For example, the above sensing signal can be acquired based on a BS (base station) monostatic.

[0592] For example, the above sensing signal can be acquired based on UE-BS bistatic.

[0593] For example, the above sensing signal may be a non-3GPP (non-3rd generation partnership project) sensing signal.

[0594] For example, the sensing function may be located on the first device. For example, the first device may be a serving base station. For example, the second device may be a UE.

[0595] For example, based on the fact that the LOS probability between the first device and the second device becomes lower than a threshold value, the first device may transmit a sensing request to the third device. For example, based on the transmission of the sensing request, the first device may obtain the LOS probability between the third device and the second device. For example, the handover of the second device may be determined to be performed based on at least one of the LOS probability between the first device and the second device and the LOS probability between the third device and the second device. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0596] For example, the handover of the second device may be determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device.

[0597] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2.

[0598] The proposed method above may be applied to a device according to various embodiments of the present disclosure. For example, a processor (202) of a second device (200) may receive a radio resource control (RRC) reset message from a first device (for example, the processor (202) of the second device (200) may control a transceiver (206) to receive a radio resource control (RRC) reset message from the first device). For example, the processor (202) of the second device (200) may perform a handover based on the RRC reset message (for example, the processor (202) of the second device (200) may control a transceiver (206) to perform a handover based on the RRC reset message). For example, the RRC reset message may include information related to the handover of the second device. For example, information related to the handover of the second device may be based on sensing results based on the line of sight (LOS) related to the second device.

[0599] According to one embodiment of the present disclosure, a second device may be provided. For example, the second device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the second device to: receive a radio resource control (RRC) reset message from the first device; and perform a handover based on the RRC reset message, based on execution by the at least one processor. For example, the RRC reset message may include information related to the handover of the second device. For example, the information related to the handover of the second device may be based on a sensing result based on a line of sight (LOS) related to the second device.

[0600] For example, the handover of the second device may be determined not to be performed based on the fact that the LOS probability between the first device and the second device becomes higher than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE (user equipment).

[0601] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE.

[0602] For example, the handover of the second device may be determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a neighbor base station.

[0603] For example, the handover of the second device may be determined to be performed based on the LOS probability between the third device and the second device becoming higher than a threshold value. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0604] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0605] For example, the above sensing signal can be acquired based on a BS (base station) monostatic.

[0606] For example, the above sensing signal can be acquired based on UE-BS bistatic.

[0607] For example, the above sensing signal may be a non-3GPP (non-3rd generation partnership project) sensing signal.

[0608] For example, the sensing function may be located on the first device. For example, the first device may be a serving base station. For example, the second device may be a UE.

[0609] For example, based on the fact that the LOS probability between the first device and the second device becomes lower than a threshold value, the first device may transmit a sensing request to the third device. For example, based on the transmission of the sensing request, the first device may obtain the LOS probability between the third device and the second device. For example, the handover of the second device may be determined to be performed based on at least one of the LOS probability between the first device and the second device and the LOS probability between the third device and the second device. For example, the first device may be a serving base station. For example, the second device may be a UE. For example, the third device may be a Naver base station.

[0610] For example, the handover of the second device may be determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device.

[0611] For example, the handover of the second device may be determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2.

[0612] According to one embodiment of the present disclosure, a processing device (configured to control a second device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the second device to: receive a radio resource control (RRC) reset message from the first device based on execution by the at least one processor; and perform a handover based on the RRC reset message. For example, the RRC reset message may include information related to the handover of the second device. For example, the information related to the handover of the second device may be based on a sensing result based on a line of sight (LOS) related to the second device.

[0613] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the second device may: receive a radio resource control (RRC) reset message from the first device; and perform a handover based on the RRC reset message. For example, the RRC reset message may include information related to the handover of the second device. For example, the information related to the handover of the second device may be based on a sensing result based on a line of sight (LOS) related to the second device.

[0614] According to the present disclosure, the following effects may be provided.

[0615] For example, through the present disclosure, a UE can perform a handover process without a signal measurement step and a measurement report transmission step between a serving base station and a neighbor base station. For example, this can reduce the energy consumption and signaling overhead of the UE required for handover in related technologies. For example, by omitting the measurement report transmission step, a faster handover can be performed, and the problem of handover delay caused by transmission failure can be significantly resolved.

[0616] Various embodiments of the present disclosure may be combined with one another. For example, various embodiments of the present disclosure may be combined with one another, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the various embodiments may be omitted.

[0617] The present disclosure describes a 5G wireless communication system as an example. This can be similarly applied and used in 6G wireless communication systems, etc.

[0618] The proposed method above may be applied to the device described below. First, the processor (202) of the receiving terminal may set at least one partial bandwidth (e.g., BWP; bandwidth part). Then, the processor (202) of the receiving terminal may control the transceiver (206) of the receiving terminal to receive a physical channel related to terminal-to-terminal communication (e.g., SL communication) and / or a reference signal related to terminal-to-terminal communication (e.g., SL communication) from the transmitting terminal on at least one partial bandwidth (e.g., BWP).

[0619] The following describes an apparatus to which various embodiments of the present disclosure may be applied.

[0620] Although not limited to, the various descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G, 6G, etc.) between devices.

[0621] Examples are provided in more detail below with reference to the drawings. In the following drawings and descriptions, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise described.

[0622] FIG. 29 illustrates a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 29 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods and / or operations of the embodiments may be omitted.

[0623] Referring to FIG. 29, a communication system (1) to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution), 6G) and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication functions, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., Advanced Air Mobility). The XR device includes an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, a base station and a network may be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0624] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include LTE, NR, and 6G, as well as NB-IoT (Narrowband Internet of Things) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0625] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. Wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0626] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR, 6G, etc.), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on the various proposals of the present disclosure, at least some of the following may be performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.

[0627] FIG. 30 shows a wireless device according to one embodiment of the present disclosure. The embodiment of FIG. 30 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods and / or operations of the embodiments may be omitted.

[0628] Referring to FIG. 30, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), base station (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 29.

[0629] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0630] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0631] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.

[0632] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be contained in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0633] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0634] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0635] FIG. 31 shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure. The embodiment of FIG. 31 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0636] Referring to FIG. 31, the signal processing circuit (1000) may include a scrambler (1010), a modulator (1020), a layer mapper (1030), a precoder (1040), a resource mapper (1050), and a signal generator (1060). Although not limited thereto, the operation / function of FIG. 31 may be performed in the processor (102, 202) and / or transceiver (106, 206) of FIG. 30. The hardware elements of FIG. 31 may be implemented in the processor (102, 202) and / or transceiver (106, 206) of FIG. 30. For example, blocks 1010 through 1060 may be implemented in the processor (102, 202) of FIG. 30. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 30, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 30.

[0637] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 31. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transmission block (e.g., UL-SCH transmission block, DL-SCH transmission block). The wireless signal can be transmitted through various physical channels (e.g., PUSCH, PDSCH).

[0638] Specifically, a codeword can be converted into a scrambled bit sequence by a scrambler (1010). The scrambled sequence used for scrambling is generated based on an initialization value, which may include ID information of a wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by an N*M precoding matrix W. Here, N is the number of antenna ports and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on the complex modulation symbols. Additionally, the precoder (1040) can perform precoding without performing transform precoding.

[0639] A resource mapper (1050) can map the modulation symbols of each antenna port to a time-frequency resource. The time-frequency resource may include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. A signal generator (1060) generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to another device through each antenna. To this end, the signal generator (1060) may include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0640] The signal processing process for a received signal in a wireless device can be configured as the inverse of the signal processing process (1010–1060) of FIG. 31. For example, a wireless device (e.g., 100, 200 in FIG. 30) can receive a wireless signal from the outside through an antenna port / transceiver. The received wireless signal can be converted into a baseband signal through a signal restorer. To this end, the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a Fast Fourier Transform (FFT) module. Subsequently, the baseband signal can be restored into a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scrambling process. The codeword can be restored into the original information block through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.

[0641] FIG. 32 illustrates a wireless device according to one embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use-example / service (see FIG. 29). The embodiment of FIG. 32 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0642] Referring to FIG. 32, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 30 and may be composed of various elements, components, units / parts, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 30. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 30. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and additional elements (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).

[0643] The additional element (140) can be configured in various ways depending on the type of wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 29, 100a), a vehicle (Fig. 29, 100b-1, 100b-2), an XR device (Fig. 29, 100c), a portable device (Fig. 29, 100d), a home appliance (Fig. 29, 100e), an IoT device (Fig. 29, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 29, 400), a base station (Fig. 29, 200), a network node, etc. Wireless devices can be used in a movable or fixed location depending on the use—e.g., service.

[0644] In FIG. 32, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least partially connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be connected via a wire, and the control unit (120) and the first unit (e.g., 130, 140) may be connected wirelessly via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory and / or a combination thereof.

[0645] Hereinafter, an implementation example of FIG. 32 will be described in more detail with reference to the drawings.

[0646] FIG. 33 illustrates a portable device according to one embodiment of the present disclosure. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a portable computer (e.g., a laptop, etc.). The portable device may be referred to as a Mobile Station (MS), a User Terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT). The embodiment of FIG. 33 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0647] Referring to FIG. 33, the portable device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140a), an interface unit (140b), and an input / output unit (140c). The antenna unit (108) may be configured as part of the communication unit (110). Blocks 110 to 130 / 140a to 140c each correspond to blocks 110 to 130 / 140 of FIG. 32.

[0648] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with other wireless devices and base stations. The control unit (120) can control the components of the portable device (100) to perform various operations. The control unit (120) may include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / code / commands required for the operation of the portable device (100). Additionally, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the portable device (100) and may include wired / wireless charging circuits, batteries, etc. The interface unit (140b) can support the connection between the portable device (100) and other external devices. The interface unit (140b) may include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can receive or output video information / signals, audio information / signals, data, and / or information input by a user. The input / output unit (140c) may include a camera, a microphone, a user input unit, a display unit (140d), a speaker and / or a haptic module, etc.

[0649] For example, in the case of data communication, the input / output unit (140c) acquires information / signals (e.g., touch, text, voice, image, video) input from the user, and the acquired information / signals can be stored in the memory unit (130). The communication unit (110) converts the information / signals stored in the memory into wireless signals and can directly transmit the converted wireless signals to another wireless device or to a base station. Additionally, the communication unit (110) can receive wireless signals from another wireless device or base station and then restore the received wireless signals to their original information / signals. The restored information / signals can be stored in the memory unit (130) and then output in various forms (e.g., text, voice, image, video, haptic) through the input / output unit (140c).

[0650] The claims described in this disclosure may be combined in various ways. For example, the technical features of the method claims of this disclosure may be combined to be implemented as a device, and the technical features of the device claims of this disclosure may be combined to be implemented as a method. Additionally, the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure may be combined to be implemented as a device, and the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure may be combined to be implemented as a method.

Claims

1. Regarding the method, The first device acquires a sensing signal; Based on the above sensing signal, the first device obtains a sensing result based on a line of sight (LOS) associated with the second device; and A method comprising the step of determining whether the first device performs a handover of the second device based on the sensing result based on the LOS associated with the second device.

2. In Paragraph 1, It is determined that the handover of the second device is not performed based on the LOS probability between the first device and the second device becoming higher than a threshold value, and The above-mentioned first device is a serving base station, and The above second device is a UE (user equipment), a method.

3. In Paragraph 1, It is determined that the handover of the second device is performed based on the LOS probability between the first device and the second device becoming lower than a threshold value, and The above-mentioned first device is a serving base station, and The above second device is a UE, method.

4. In Paragraph 1, It is determined that the handover of the second device is performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device, and The above-mentioned first device is a serving base station, and The above second device is a UE, and The above third device is a Naver base station, method.

5. In Paragraph 1, It is determined that the handover of the second device is performed based on the LOS probability between the third device and the second device becoming higher than a threshold value, and The above-mentioned first device is a serving base station, and The above second device is a UE, and The above third device is a Naver base station, method.

6. In Paragraph 1, It is determined that the handover of the second device is performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2, and The above-mentioned first device is a serving base station, and The above second device is a UE, and The above third device is a Naver base station, method.

7. In Paragraph 1, A method in which the above sensing signal is acquired based on a BS (base station) monostatic.

8. In Paragraph 1, A method in which the above sensing signal is acquired based on UE-BS bistatic.

9. In Paragraph 1, A method in which the above sensing signal is a non-3GPP (non-3rd generation partnership project) sensing signal.

10. In Paragraph 1, The sensing function is located on the first device, and The above-mentioned first device is a serving base station, and The above second device is a UE, method.

11. In Paragraph 1, Based on the fact that the LOS probability between the first device and the second device becomes lower than a threshold value, the first device transmits a sensing request to the third device; and Based on the transmission of the sensing request, the first device obtains the LOS probability between the third device and the second device; wherein It is determined that the handover of the second device is performed based on at least one of the LOS probability between the first device and the second device and the LOS probability between the third device and the second device, and The above-mentioned first device is a serving base station, and The above second device is a UE, and The above third device is a Naver base station, method.

12. In Paragraph 11, A method in which the handover of the second device is determined to be performed based on the fact that the LOS probability between the third device and the second device becomes higher than the offset relative to the LOS probability between the first device and the second device.

13. In Paragraph 11, A method in which the handover of the second device is determined to be performed based on the LOS probability between the first device and the second device becoming lower than threshold 1 and based on the LOS probability between the third device and the second device becoming higher than threshold 2.

14. In the first device, At least one transmitter / receiver; At least one processor; and The first device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: Acquire a sensing signal; Based on the above sensing signal, a sensing result based on the line of sight (LOS) associated with the second device is obtained; and A first device that determines whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

15. In a processing device, At least one processor; and The first device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: Acquire a sensing signal; Based on the above sensing signal, a sensing result based on the line of sight (LOS) associated with the second device is obtained; and A processing device that determines whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

16. A non-transient computer-readable storage medium that records instructions, When executed, the above instructions cause the first device: Acquire a sensing signal; Based on the above sensing signal, a sensing result based on the line of sight (LOS) associated with the second device is obtained; and A non-transient computer-readable storage medium that determines whether to perform a handover of the second device based on the sensing result based on the LOS associated with the second device.

17. Regarding the method, The step of the second device receiving an RRC (radio resource control) reset message from the first device; and The second device comprises the step of performing a handover based on the RRC reset message; The above RRC reset message includes information related to the handover of the second device, and A method in which information related to the handover of the second device is based on a sensing result based on the line of sight (LOS) related to the second device.

18. In the second device, At least one transmitter / receiver; At least one processor; and The second device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: Receiving an RRC (radio resource control) reset message from the first device; and Perform a handover based on the above RRC reset message, but The above RRC reset message includes information related to the handover of the second device, and Information related to the handover of the second device is based on a sensing result based on the line of sight (LOS) related to the second device.

19. In a processing device, At least one processor; and A second device comprising at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: Receiving an RRC (radio resource control) reset message from the first device; and Perform a handover based on the above RRC reset message, but The above RRC reset message includes information related to the handover of the second device, and A processing device for information related to the handover of the second device, based on a sensing result based on the line of sight (LOS) related to the second device.

20. A non-transient computer-readable storage medium that records instructions, When executed, the above commands cause the second device: Receiving an RRC (radio resource control) reset message from the first device; and Perform a handover based on the above RRC reset message, but The above RRC reset message includes information related to the handover of the second device, and Information related to the handover of the second device is a non-transient computer-readable storage medium based on a sensing result based on a line of sight (LOS) related to the second device.

Images