Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure comprises a reception unit that receives a signal for sensing, and a control unit that, when information based on measurement of the signal satisfies a condition, controls transmission of a report of failure of the sensing.

Description

Terminal, wireless communication method and base station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered.

[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

[0005] Wireless sensing is being considered in future wireless communication systems (e.g., NR).

[0006] However, the details of wireless sensing have not been fully explored. If the details of wireless sensing are not clear, there is a risk that the sensing quality / communication quality will be degraded.

[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that improve wireless sensing performance.

[0008] A terminal according to one aspect of the present disclosure has a receiving unit that receives a signal for sensing, and a control unit that controls the transmission of a report of a sensing failure when information based on measurement of the signal satisfies a condition.

[0009] According to one aspect of the present disclosure, it is possible to improve the performance of wireless sensing.

[0010] 1A and 1B show an example of a monostatic sensing scenario at a BS or a UE. 2A and 2B show an example of a bistatic sensing scenario between BSs or between UEs. 3A and 3B show an example of a bistatic sensing scenario between a BS and a UE. 4 shows an example of an NR positioning architecture. 5 shows an example of a location service sequence. 6 shows an example of version support for multiple positioning methods. 7 shows an example of an inter-gNB handover procedure in NR. 8 shows a first part of an example of an intra-AMF / UPF handover procedure in NR. 9 shows a second part of an example of an intra-AMF / UPF handover procedure in NR. 10 shows an example of an association between options 1 and 2 of embodiment A0. 11 shows an example of a sensing architecture according to embodiment A1. 12 shows a first example of an extended NRPPa procedure. FIG. 13 shows a second example of the procedure for the extended NRPPa. FIG. 14 shows a third example of the procedure for the extended NRPPa. FIG. 15 shows a fourth example of the procedure for the extended NRPPa. FIG. 16 shows an example of an IE for the extended NRPPa. FIG. 17 shows a first example of the procedure for the extended LPP. FIG. 18 shows a second example of the procedure for the extended LPP. FIG. 19 shows a third example of the procedure for the extended LPP. FIG. 20 shows a first example of the IE for the extended LPP. FIG. 21 shows a second example of the IE for the extended LPP. FIG. 22 shows a third example of the IE for the extended LPP. FIG. 23 shows an example of a sensing architecture according to a combination of embodiments A1 and A2. FIG. 24 shows an example of a sensing architecture according to embodiment A3. FIG. 25 shows an example of a sensing architecture according to a combination of embodiments A1 and A3. FIG. 26 is a flowchart showing an example of option 1-3-1 of embodiment B1. Fig. 27 is a flowchart showing an example of option 1-3-2 of embodiment B1. Fig. 28 is a flowchart showing an example of option 1-3-3 of embodiment B1. Fig. 29 shows an example of a mobility procedure according to embodiment C2a. Fig. 30 shows an example of a mobility procedure according to a variation of embodiment C2a. Fig. 31 shows an example of a mobility procedure according to embodiment C2b.FIG. 32 illustrates an example of a mobility procedure according to embodiment C2c. FIG. 33 illustrates an example of a mobility procedure according to embodiment C2d. FIG. 34 illustrates an example of a configuration of an NW node (network node) according to an embodiment. FIG. 35 illustrates an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 36 illustrates an example of a configuration of a base station according to an embodiment. FIG. 37 illustrates an example of a configuration of a user terminal according to an embodiment. FIG. 38 illustrates an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 39 illustrates an example of a vehicle according to an embodiment.

[0011] (ISAC) The motivation for integrated sensing and communications (ISAC) is to achieve high sensing performance and new / extended services by using various frequencies and cellular network equipment, and to optimize network parameters by analyzing real-time sensing data. Use cases and possible requirements for extending 5G systems to provide sensing services to address different target industries / applications are considered, and some use cases may also include non-3GPP type (non-wireless communication type) sensors (e.g., radar, camera).

[0012] For example, use case 1 is sensing for tourist destination traffic management. For example, use case 2 is intruder detection in a smart home environment.

[0013] ISAC considers sensing-assisted communication and communication-assisted sensing. Sensing-assisted communication includes sensing-assisted beam management and sensing-assisted resource allocation. Communication-assisted sensing includes network sensing and coordinated sensing. To achieve these, waveforms, beamforming, artificial intelligence (AI) / deep learning (DL) radio access technology (RAT), frame structure, and reference signals are considered. Furthermore, shared spectrum, hardware, and algorithms for ISAC are considered, including higher frequency bands, larger antenna arrays, and similar signal processing algorithms for communication and sensing.

[0014] In ISAC, the challenges are unified waveforms that simultaneously meet the requirements of communication (e.g., OFDM signals) and sensing (e.g., chirp signals), ISAC beamforming that simultaneously realizes communication (e.g., transmit signals, receive signals) and sensing (e.g., echo signals, transmit signals, reflected signals) through beamforming, and interference suppression between them, and CSI mining by AI that uses AI / DL networks to extract sensing information from channel information for communication (e.g., UL transmit signals) and radar (e.g., DL radar signals).

[0015] Three types of radar and communication systems have been considered based on whether the communication and radar (sensing) systems share hardware / bandwidth. The three types are independent radar and communication systems (independent systems), joint radar and communication systems (joint systems), and integrated radar and communication systems (integrated systems). In the following, we focus on ISAC systems, in which hardware and bandwidth are shared between the radar and communication systems.

[0016] (Wireless Sensing) Wireless sensing based on communication radio waves is a key enabler for the vision of 6G cyber physical systems (CPS). ISAC can be realized by 5G-advanced (A) and 6G with the development of higher frequencies and wider bandwidths. The design of ISAC waveforms and sensing reference signals (RS) is a key technology for realizing wireless sensing.

[0017] Use cases for ISAC include the metaverse, high altitude platform station (HAPS) sensing, and crowd estimation. HAPS can be an aircraft with an altitude of about 20 km and can be used in non-terrestrial networks (NTNs).

[0018] HAPS sensing realizes ultra-remote distance sensing using echo signals based on the support of communication functions. Considering that the sensing distance depends on the strength of the echo signal, a sensing form or sensing sequence with an extremely low peak-to-average power ratio (PAPR) is required to improve the SNR of the echo signal under a given transmission power.

[0019] (Sensing Mode / Method) Conventional communication systems include communication between one BS (base station, gNB) and one UE, and joint transmission between multiple BSs and one UE. Conventional radar systems include monostatic radars in which one radar transmits a radar signal and receives echoes from a sensing target, and bistatic / multistatic radars in which one radar transmits a radar signal and one or more radars receive echoes from a sensing target.

[0020] Independent systems use separate hardware and separate frequency bands for radar and communications, which may be co-located or in separate locations.

[0021] A joint system uses the same hardware and separate frequency bands for radar and communications.

[0022] A unified system uses the same hardware and the same frequency bands for radar and communications.

[0023] Sensing in the ISAC system can be achieved by any of the following sensing methods: ◇Monostatic sensing: Monostatic sensing using the idea of ​​monostatic radar. This sensing method requires one BS or one UE, and sensing is performed using echo signals. In this sensing method, there is no BS-to-BS, UE-to-UE, or BS-to-UE cooperation. A use case of this sensing method is, for example, imaging using terahertz. ◇Bistatic sensing / multistatic sensing: Bistatic / multistatic sensing using bistatic radar / multistatic radar. This sensing method requires two or more BSs or two or more UEs, and sensing is performed using reflected signals. A use case of this sensing method is, for example, positioning. ◇UE-assisted sensing: UE-assisted sensing using the idea of ​​NR positioning. This sensing method requires a BS and a UE, and sensing is performed via communication (UL / DL) signals. This sensing method operates within the existing 5G NR framework. This sensing method requires a UE, and both line-of-sight (LOS) and non-line-of-sight (NLOS) sensing require high computational complexity. A use case for this sensing method is, for example, breath monitoring.

[0024] [Monostatic Sensing] This sensing method includes BS (gNB) monostatic sensing (Figure 1A) and UE monostatic sensing (Figure 1B).

[0025] A scenario suitable for monostatic sensing has the following characteristics: The sensing target is in the vicinity of the sensing BS / UE and high or medium SNR of the echo signal is required. The target may not have communication capabilities.

[0026] The capacity requirements for monostatic sensing have the following characteristics: High capacity is required due to full duplex at the BS or UE.

[0027] The performance of monostatic sensing has the following characteristics: ◇High accuracy due to no quantization. ◇Accuracy is related to the SNR of the echo signal. ◇Low latency.

[0028] [Bistatic Sensing / Multistatic Sensing] This sensing method includes bistatic sensing from BS to BS (gNB-gNB, BS-BS, BS1-BS2, gNB-to-gNB, gNB1-to-gNB2) (Figure 2A), bistatic sensing from UE to BS (UE-gNB, UE-BS, UE-to-gNB) (Figure 2B), bistatic sensing from BS to UE (gNB-UE, BS-UE, gNB-to-UE) (Figure 3A), and bistatic sensing from UE to UE (UE-UE, UE1-UE2, UE-to-UE, UE1-to-UE2) (Figure 3B).

[0029] Scenarios suitable for BS-BS bistatic sensing have the following characteristics: ◇Tight synchronization and coordination between BSs is required, and scheduling coordination among multiple BSs is required. ◇The target may not have communication capabilities.

[0030] The capacity requirements for BS-BS bistatic sensing have the following characteristics: ◇Low capacity can be realized due to half duplex. ◇High capacity is required due to synchronization between BSs.

[0031] The performance of BS-BS bistatic sensing has the following characteristics: ◇High accuracy due to no quantization ◇Accuracy is related to the SNR of the echo signal ◇Medium latency.

[0032] Scenarios suitable for UE-BS, BS-UE and UE-UE bistatic sensing have the following characteristics: ◇ It requires communicating UEs to be around the target.

[0033] The capacity requirements for UE-BS bistatic sensing have the following characteristics: ◇It can be realized even with low capacity due to half duplex. ◇High UE positioning accuracy is required.

[0034] The capacity requirements for BS-UE bistatic sensing and UE-UE bistatic sensing have the following characteristics: ◇Low capacity can be realized due to half duplex. ◇UE needs sufficient computational resources and high accuracy of reflected signal detection. ◇High UE positioning accuracy is required.

[0035] The performance of UE-BS bistatic sensing, BS-UE bistatic sensing, and UE-UE bistatic sensing has the following characteristics: ◇ Medium accuracy due to quantization of feedback values ​​◇ Accuracy is related to the configured resources and UE location ◇ Long latency

[0036] In each of the embodiments described below, the following scenarios and assumptions may be used: ◇In ISAC scenarios, communication and sensing functions are required. ◇For low complexity and backward compatibility, TDD (half duplex) may be assumed instead of full duplex at BS and UE.

[0037] In a TDD-based ISAC system, sensing signals and reflected / echo signals are preferably transmitted and received in different time resources. For example, in BS-based sensing, including monostatic BS sensing and bistatic BS1-to-BS2 sensing, sensing signals are preferably transmitted in DL time resources, and reflected / echo signals are preferably received in UL time resources. For example, in UE-based sensing, including monostatic UE sensing and bistatic UE1-to-UE2 sensing, sensing signals are preferably transmitted in UL time resources, and reflected / echo signals are preferably received in DL time resources. In bistatic BS-to-UE sensing, DL time resources are preferably used for sensing. In bistatic UE-to-DL sensing, UL time resources are preferably used for sensing.

[0038] (Location Services: 5G System (5GS) Location Services (LCS) / Architecture Model and Concepts / Functional description of LCS per network function) In this disclosure, the following abbreviations may be used. - 5G Core Network: 5GC, 5GCN - 5G System: 5GS - (Radio) Access Network: (R)AN - Next Generation-Radio Access Network: NG-RAN - Access and Mobility Management Function: AMF - Location Management Function: LMF - Non-3GPP InterWorking Function: N3IWF - Mobile Originated Location Request: MO-LR - Mobile Terminated Location Request: MT-LR - Network Induced Location Request: NI-LR - Gateway Mobile Location Center: GMLC - Network Exposure Function: NEF - Public Land Mobile Network: PLMN - Trusted Non-3GPP Access Network: TNAN - Internet Protocol: IP - IP Multimedia Subsystem: IMS - Unified Data Management: UDM - Unified Data Repository: UDR - Quality of Service: QoS

[0039] The 5G system architecture includes the following service-based interfaces: Namf: A service-based interface presented by the AMF. Nnef: A service-based interface presented by the NEF.

[0040] The 5GS LCS architecture includes the following service-based interfaces for Location Services: Nlmf: A service-based interface presented by the LMF. Ngmlc: A service-based interface presented by the GMLC.

[0041] The 5G system architecture includes the following reference points: N1: Reference point between UE and AMF. N2: Reference point between (R)AN and AMF.

[0042] The NG-RAN node is a gNB or an ng-eNB. The gNB provides protocol termination of the NR user plane and control plane for the UE and is connected to the 5GC via the NG interface. The ng-eNB provides protocol termination of the E-UTRA user plane and control plane for the UE and is connected to the 5GC via the NG interface.

[0043] The gNB may provide measurement information for the target UE and convey this information to the LMF. To support NR RAT-dependent positioning, the gNB may perform measurements of radio signals for the target UE and provide measurement results for position estimation.

[0044] The ng-eNB may provide measurements for location estimation, provide measurement information for the target UE, and convey these measurements to the LMF. The ng-eNB performs the measurements upon request (on-demand or periodic) from the LMF. The ng-eNB may provide multiple TPs. The ng-eNB may broadcast the Assistance Data information received from the LMF in Positioning System Information messages.

[0045] The UE may perform measurements on DL signals from the NG-RAN and other sources such as E-UTRAN, different GNSS and TBS systems, WLAN access points, Bluetooth beacons, and UE barometric and motion sensors. The measurements performed are determined by the selected positioning method. The UE may, for example, include an independent positioning capability (e.g., global positioning systems (GPS)) that allows it to report its location independent of NG-RAN transmissions. A UE with independent positioning capability may utilize assistance information obtained from the network.

[0046] The Access and Mobility Management Function (AMF) contains the functions responsible for managing the positioning of target UEs for all types of location requests. The AMF has access to the GMLC and NEF via the Namf interface, to the RAN via the N2 reference point, and to the UE via the N1 reference point. Functions performed by the AMF to support location services include: ◇ The AMF initiates NI-LR location requests for UEs making IMS emergency calls or to know the UE geographical area for NE satellite access for PLMN selection verification. ◇ The AMF receives and manages location requests for periodic location events, triggered location events, and UE-available location events from the GMLC for 5GC-MT-LR and delayed 5GC-MT-LR. ◇ The AMF receives and manages location requests for 5GC-MO-LR from the UE. ◇The AMF receives and manages event publication requests for location information from the NEF. ◇The AMF selects an LMF. ◇The AMF receives updated privacy requirements from the UE and forwards them to the UDR via the UDM. ◇The AMF supports cancellation of periodic or triggered location reporting for the target UE. ◇The AMF supports changing the serving LMF for periodic or triggered location reporting for the target UE. ◇If assistance data is broadcast by 5GS using an encrypted form, the AMF receives an encryption key from the LMF and forwards it to appropriately subscribed UEs using mobility management procedures. ◇The AMF stores the UE positioning capabilities received from the LMF and sends the UE positioning capabilities to the LMF together with the received location request.

[0047] The Location Management Function (LMF) manages the support of different location services for the target UE, including UE positioning and delivery of assistance data to the UE. The LMF may interact with the serving gNB or eNB to obtain location measurements for the UE, including UL measurements made by the NG-RAN and DL measurements made by the UE and provided to the NG-RAN as part of other functions, such as for handover.

[0048] The LMF manages all standby coordination and scheduling of resources required for the location of UEs registering to or accessing the 5GCN. It may also calculate or verify estimates of the final location and any velocity, and estimate the achieved accuracy. The LMF receives location requests for target UEs from the serving AMF using the Nlmf interface. The LMF interacts with the UE for location information exchange, which applies to UE-assisted and UE-based positioning methods, and interacts with the NG-RAN, N3IWF, or TNAN to obtain location information.

[0049] Additional functions that may be performed by the LMF to support location services include: ◇ The LMF supports a request for a single location received from the serving AMF for the target UE. ◇ The LMF supports a request for periodic or triggered location received from the serving AMF for the target UE. ◇ The LMF determines the type and number of positioning methods and procedures based on the UE, PLMN capabilities, QoS, UE connectivity state per access type, LCS client type, coordinate type, and optionally, service type, and an indication of requiring reliable UE location information. ◇ The LMF reports UE location estimates directly to the GMLC for periodic or triggered location of the target UE. ◇ The LMF supports cancellation of periodic or triggered location for the target UE. ◇The LMF supports the provision of broadcast assistance data via the NG-RAN using encrypted or unencrypted format and the transfer of ciphering keys to authorized UEs via the AMF. ◇The LMF supports the change of serving LMF for periodic or triggered location reporting for a target UE. ◇The LMF supports receiving stored UE positioning capabilities from the AMF and providing updated UE positioning capabilities to the AMF. ◇The LMF maps UE location to geographical areas where the PLMN is authorized or not authorized to operate based on a request from the AMF. ◇The LMF supports the determination of UE location at scheduled location times. ◇The LMF decides whether to use the user plane or the control plane for positioning.◇The LMF supports handling of 5GC-MT-LR, 5GC-NI-LR, 5GC-MO-LR, and delayed 5GC-MT-LR for periodic or triggered location across the user plane connection between the UE and the LMF.

[0050] (NR Positioning Architecture: Stage 2 functional specification of UE positioning in NG-RAN / NG-RAN UE Positioning Architecture) In this disclosure, the following abbreviations may be used:

[0051] Figure 4 shows an example of an architecture (NR positioning architecture) in 5GS applicable to the positioning of UEs using NR or E-UTRA access. In the case of a split gNB architecture as in this example, the gNB-DU may include a TRP function, and the TRP function may support functions for a TP, a RP, or both a TP and a RP. A gNB-DU including a TRP function does not need to provide cell services. The NG-RAN includes an ng-eNB and a gNB.

[0052] The AMF receives a request for some location services associated with a specific target UE from another entity (e.g., a GLMC or a UE), or the AMF itself decides to initiate some location services on behalf of a specific target UE (e.g., for an IMS emergency call from the UE). The AMF then sends a location service request to the LMF. The LMF processes the location service request, which may include at least one of transferring assistance data to the target UE to assist in UE-based / UE-assisted positioning and positioning the target UE. The LMF then returns the result of the location service (e.g., a position estimate for the UE) to the AMF.

[0053] The NR-Uu interface (UE-UTRA radio interface), which wirelessly connects the UE to the gNB, is used as one of several transport links for the NR positioning protocol for target UEs using NR access to the NG-RAN.

[0054] The LTE-Uu interface (radio interface), which wirelessly connects the UE to the ng-eNB, is used as one of several transport links for the LTE positioning protocol for target UEs with LTE access to the NG-RAN.

[0055] The NG-C interface between the gNB and the AMF, and between the ng-eNB and the AMF, is transparent to all UE positioning-related procedures. The NG-C interface is involved in these procedures only as a transport link for the NR positioning protocol.

[0056] The NL1 interface between the LMF and AMF is transparent to all UEs, gNBs, and ng-eNBs involved in the positioning procedure. The NL1 interface is only used as a transport link between the LPP and NRPPa.

[0057] As shown in Figure 5, the overall sequence of events for location services, which applies to the UE, NG-RAN, and LMF, follows several steps: ◇1a. Some entity in the 5GC (e.g., GMLC) requests some location services (e.g., positioning) for the target UE from the serving AMF. ◇1b. Or, the serving AMF for the target UE determines that some location services are needed (e.g., to locate the UE for an emergency call). ◇1c. Or, the UE requests some location services from the serving AMF at the NAS level. ◇2. The AMF forwards the location service request to the LMF. ◇3a. The LMF initiates a location procedure using the serving ng-eNB or gNB in ​​the NG-RAN, and possibly a neighboring ng-eNB or gNB in ​​the NG-RAN (e.g., to obtain position measurements or assistance data). ◇3b. In addition to or instead of step 3a, the LMF initiates a location procedure with the UE (e.g., to obtain a position estimate or position measurements, or to transfer Assistance Data to the UE). ◇4. The LMF provides a location service response to the AMF, including any required results (e.g., a success or failure indication and, if requested and obtained, a location estimate for the UE). ◇5a. If step 1a was performed, the AMF returns a location service response to the 5GC entity in step 1a, including any required results (e.g., a location estimate for the UE). ◇5b. If step 1b was performed, the AMF uses the location service response received in step 4 to support the service that triggered it in step 1b (e.g., it may provide a location estimate associated with the emergency call to the GMLC). ◇5c. If step 1c is performed, the AMF returns a location service response to the UE and includes any required results (e.g., a location estimate of the UE).

[0058] (NR Positioning Protocol: Stage 2 functional specification of UE positioning in NG-RAN / Signalling protocols and interfaces) In this disclosure, the following abbreviations may be used: ◇Enhanced Cell-ID (positioning method): E-CID ◇Observed Time Difference Of Arrival: OTDOA ◇Multi-Round Trip Time: Multi-RTT ◇Uplink Angle of Arrival: UL-AoA ◇Azimuth-Angle of Arrival: A-AoA ◇Zenith-Angle of Arrival: Z-AoA ◇Uplink Time Difference of Arrival: UL-TDOA ◇Downlink Time Difference of Arrival: DL-TDOA ◇Downlink Angle-of-Departure: DL-AoD ◇wireless local area network: WLAN ◇terrestrial beacon system: TBS ◇Metropolitan Beacon System: MBS ◇Positioning Reference Signal: PRS ◇UserPlane Location Protocol: ULP

[0059] The NR Positioning Protocol A (NRPPa) conveys information between NG-RAN nodes and LMF. It is used to support the following positioning functions: ◇ E-CID for E-UTRA, where measurements are forwarded from the ng-eNB to the LMF. ◇ Data collection from the ng-eNB or gNB for support of OTDOA for E-UTRA. ◇ Acquisition of cell ID and cell portion ID from the gNB for support of the NR cell ID positioning method. ◇ Exchange of information between the LMF and NG-RAN nodes for the purpose of broadcasting assistance data. ◇ NR E-CID, where measurements are forwarded from the gNB to the LMF. ◇ NR Multi-RTT, where measurements are forwarded from the gNB to the LMF. ◇ NR UL-AoA, where measurements are forwarded from the gNB to the LMF. ◇NR UL-TDOA where measurements are forwarded from gNB to LMF. ◇Data collection from gNB for support of DL-TDOA, DL-AoD, multi-RTT, UL-TDOA, UL-AoA. ◇Measurement pre-configuration information transfer which allows LMF to request NG-RAN nodes to pre-configure and activate / deactivate measurement gaps / PRS processing windows.

[0060] The LTE Positioning Protocol (LPP) is terminated between the target device (UE in the control plane case or SET in the user plane case) and the positioning server (LMF in the control plane case or SLP in the user plane case).

[0061] The LPP protocol aims to enable NR and LTE positioning using multiple different positioning methods while separating the details of any particular positioning method from the details of the underlying transport.

[0062] LPP procedures involve multiple message or one or more "unsolicited" message request / response pairings. Each procedure has a single purpose (e.g., transfer of Assistance Data, exchange of LPP-related capabilities, or positioning of a target device according to some QoS and one or more positioning method specifications). To achieve more complex purposes (e.g., transfer of Assistance Data and exchange of LPP-related capabilities, positioning of a target device), multiple procedures can be used in series / parallel. Multiple procedures also allow for more than one positioning attempt at the same time (e.g., to obtain a coarse location estimate using low latency and a more accurate location estimate using high latency).

[0063] (Standard UE positioning methods: Stage 2 functional specification of UE positioning in NG-RAN / Main concepts and requirements / Standard UE Positioning Methods) The standard UE positioning methods supported for NG-RAN access are the following: ◇ Network-assisted GNSS method ◇ OTDOA positioning based on LTE signals ◇ Enhanced Cell ID method (E-CID) based on LTE signals ◇ WLAN positioning ◇ Bluetooth positioning ◇ TBS positioning ◇ Sensor-based positioning: - ◇ Barometric pressure sensor - ◇ Motion sensor ◇ NR Enhanced Cell ID method (NR E-CID) based on NR signals ◇ Multi-RTT based on NR signals ◇ DL-AoD based on NR signals ◇ DL-TDOA based on NR signals ◇ UL-TDOA based on NR signals UL-AoA including A-AoA and Z-AoA based on NR signals

[0064] OTDOA includes TBS positioning based on PRS. In existing specifications, only OTDOA based on LTE signals is supported. If the UE is served by a gNB, E-CID includes the cell ID for the NR method. E-CID is an enhanced cell ID based on LTE signals. In existing specifications, only TBS positioning based on MBS signals is supported. SUPL in FIG. 6 indicates whether the positioning method is supported by the SUPL ULP.

[0065] Hybrid positioning using multiple methods from a list of multiple positioning methods is supported. Standalone (i.e., autonomous without network assistance) mode using one or more methods from a list of multiple positioning methods is also supported.

[0066] These multiple positioning methods may be supported for at least one of the following versions: a UE-based version, a UE-assisted / LMF-based version, and an NG-RAN node-assisted version. Figure 6 shows, for each multiple positioning method, whether the version is supported in the specification.

[0067] (Handover: NR and NG-RAN Overall Description / Mobility and State Transitions / Intra-NR / Mobility in RRC_CONNECTED) As shown in Figure 7, the inter-gNB handover procedure includes the following operations: ◇1: The source gNB initiates the handover and issues a HANDOVER REQUEST on the Xn interface. ◇2: The target gNB performs admission control and provides new RRC settings as part of a HANDOVER REQUEST ACKNOWLEDGE. ◇1: The source gNB provides its RRC settings to the UE by forwarding the RRC Reconfiguration message received within the HANDOVER REQUEST ACKNOWLEDGE. The RRC Reconfiguration message includes at least a cell ID and all information required to access the target cell so that the UE can access the target cell without reading system information. In some cases, the RRC Reconfiguration message may include information required for contention-based and contention-free random access. The access information to the target cell may include beam-specific information, if any. ◇S101: The source gNB initiates handover and issues a HANDOVER REQUEST via the Xn interface. ◇S102x, S102: The target gNB performs admission control and provides new RRC settings as part of a HANDOVER REQUEST ACKNOWLEDGE. ◇S103, S103x: The source gNB provides the RRC settings to the UE by forwarding the RRC Reconfiguration message received in the HANDOVER REQUEST ACKNOWLEDGE. The RRC Reconfiguration message includes at least a cell ID and all information required to access the target cell, so that the UE can access the target cell without reading the system information.In some cases, information required for contention-based and contention-free random access can be included in the RRCReconfiguration message. The access information to the target cell may include beam-specific information, if any. ◇ S104: The UE moves the RRC connection to the target gNB and returns RRCReconfigurationComplete.

[0068] As shown in Figures 8 and 9, the intra-AMF / UPF handover procedure includes the following operations: ◇S200: The UE context in the source gNB contains information about roaming and access restrictions provided at the time of connection establishment or the last TA update. ◇S201: The source gNB configures the measurement procedure for the UE, and the UE reports according to the measurement configuration. ◇S202: The source gNB decides to handover the UE based on the MeasurementReport and RRM information. ◇S203: The source gNB issues a handover request message to the target gNB, passing a transparent RRC container containing the information necessary to prepare the handover on the target side. This information includes at least the target cell ID and K gNB *, the UE's C-RNTI in the source gNB, RRM configuration including the UE's inactive time, basic AS configuration including antenna information and DL carrier frequency, current QoS flow to DRB mapping rule provided to the UE, SIB1 information from the source gNB, UE capabilities for different RATs, and PDU session-related information, including UE-reported measurement information including beam-related information if available. The PDU session-related information includes slice information and QoS flow-level QoS profiles. The source gNB may also request a DAPS handover for one or more DRBs. K gNB* is the key distributed by the ME and gNB when performing horizontal or vertical key distribution. ◇S204: Admission control may be performed by the target gNB. When slice information is sent to the target gNB, slice-aware admission control is performed. If a PDU session relates to an unsupported slice, the target gNB rejects such a PDU session. ◇S205: The target gNB prepares the handover in L1 / L2 and sends a HANDOVER REQUEST ACKNOWLEDGE to the source gNB. This HANDOVER REQUEST ACKNOWLEDGE includes a transparent container that is sent to the UE as an RRC message to perform the handover. The target gNB indicates whether it accepts the DAPS handover. ◇S206: The source gNB triggers a Uu handover by sending an RRCReconfiguration message to the UE, including information necessary to access the target cell (at least the target cell ID, the new C-RNTI, and the target gNB's security algorithm identifier for the selected security algorithm). It may also include a set of dedicated RACH resources, an association of RACH resources with SSBs, an association of RACH resources with UE-specific CSI-RS settings, shared RACH resources, and system information of the target cell. ◇S207x: The source gNB delivers buffered data and new data from one or more UPFs. ◇S207a, S207: For DRBs where DAPS is not configured, the source gNB sends an EARLY STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN reception status and downlink PDCH SN transmission status of the DRB to which PDCP status retention applies (i.e., RLC AM). The uplink PDCP SN reception status includes at least the PDCP SB of the first missing UL PDCP SDU and may include a bitmap of the reception status of any out-of-sequence UL PDCP SDUs that the UE needs to retransmit in the target cell.The downlink PDCP SN transmission status indicates the next PDCP SB that the target gNB allocates to a new PDCP SDU and does not yet have a PDCP SN. ◇S207y: The target gNB buffers user data from the source gNB. ◇S208x: The UE detaches from the old cell and synchronizes to the new cell. ◇S208: The UE synchronizes to the target cell and sends an RRCReconfigurationComplete message to the target gNB to complete the RRC handover procedure. In the case of a DAPS handover, the UE does not detach from the source cell even when it receives an RRCReconfiguration message. When the UE receives an explicit release from the target node, it releases the source resources and settings and stops DL / UL reception / transmission with the source. ◇S208a, S208b: In the case of DAPS handover, the target gNB sends a HANDOVER SUCCESS message to the source gNB to notify that the UE has successfully accessed the target cell. In response, the source gNB sends an SN STATUS TRANSFER message to multiple DRBs configured with DAPS, to which the description of S207 applies, and normal data transfer continues. ◇S209: The target gNB sends a PATH SWITCH REQUEST message to the AMF to switch the DL data path toward the target gNB and trigger the 5GC to establish an NG-C interface instance toward the target gNB. ◇S210: The 5GC switches the DL data path toward the target gNB. The UPF sends one or more "end marker" packets for the old path to the source gNB for each PDU session / tunnel, and then releases any U-plane / TNL resources toward the source gNB. ◇S211: The AMF acknowledges the PATH SWITCH REQUEST message using PATH SWITCH REQUEST ACKNOWLEDGE.S212: Upon receiving the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB sends a UE CONTEXT RELEASE to notify the source gNB of the success of the handover. The source gNB then releases the radio and C-plane related resources associated with the UE context. Ongoing data transfer may continue.

[0069] (Issue) Mobility procedures can be considered for several different cases.

[0070] In order to detect and track an object, in different sensing modes / methods, the point involved in sensing (BS / UE) may change as the object being measured or the UE moves, and the sensing mode / method may be changed in consideration of the degradation of sensing performance. The point may be the point that sends the sensing RS or the point that measures / reports the sensing result.

[0071] In a monitoring environment, as the environment changes or the UE moves, the points involved in sensing may change, and the sensing mode / method may be changed to take into account degradation of sensing performance.

[0072] In motion monitoring, as a person or a UE moves, the points involved in sensing may change, and the sensing mode / method may be changed to take into account degradation of sensing performance.

[0073] These procedures may be referred to as mobility procedures for sensing, similar to mobility procedures for communication. Mobility procedures may involve changes in BS, UE, and / or sensing method / mode.

[0074] Due to different / separate key performance indicators (KPIs) and procedures for sensing, the coverage of sensing may be different from communication. The timing / conditions that trigger mobility for sensing may be different from communication. KPIs for sensing may include at least one of the following: area or range coverage of the sensing service, resolution (distance / speed), latency, refreshing rate, probability of non-detection or detection, confidence level, and false detection.

[0075] The mobility procedures for such sensing have not been sufficiently considered, and if such consideration is insufficient, there is a risk that sensing performance will be degraded.

[0076] Therefore, the present inventors have devised a mobility procedure for sensing. In particular, mobility procedures for different sensing modes are considered, and BSs involved in the sensing modes are taken into account. Although the following embodiments mainly describe mobility procedures for the use case of object detection and tracking, the embodiments can be applied to other use cases.

[0077] Therefore, the present inventors have studied mobility procedures in sensing.

[0078] (Various Reinterpretations, etc.) Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Note that each of the following embodiments (e.g., each case) may be used alone, or at least two of them may be combined and applied.

[0079] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0080] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0081] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0082] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0083] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0084] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0085] In this disclosure, "having the capability of..." may be read interchangeably as "supporting / reporting the capability of...".

[0086] In the present disclosure, ceil(x), ceiling function, and ceiling function may be interchangeable. In the present disclosure, floor(x), floor function, and floor function may be interchangeable. In the present disclosure, sqrt(x) and square root may be interchangeable. In the present disclosure, x mod y, mod(x,y), mod function, and modulo operation may be interchangeable. In the present disclosure, Σ i=M M+N-1 f(i),Σ i=M M+N-1 f i , f(i) or f for i=M, M+1,..., M+N-1 i summation, f(M)+f(M+1)+...+f(M+N-1), f M +f M+1 +...+f M+N-1, may be read interchangeably. C(n,k) is the number of combinations of selecting k values ​​from n values ​​(combinatorial coefficient), binomial coefficients, n C k , C n k , may be read interchangeably.

[0087] In this disclosure, a b , a_b, and a with b added to the bottom right of a may be read interchangeably. c , a^c, and the notation of a with c added to the upper right of a may be read interchangeably. b c , a_b^c, and the notation in which b is added to the bottom right of a and c is added to the top right may be read interchangeably. ~ may be expressed by adding 〜 to the x, or may be referred to as x tilde. - may be represented by an x ​​with a - or may be called an x-bar.

[0088] In the present disclosure, the frequency range corresponding to FR1 may be 410-7125 MHz. In the present disclosure, FR2 may include FR2-1 and FR2-2, and the frequency range corresponding to FR2-1 may be 24250-52600 MHz, and the frequency range corresponding to FR2-1 may be 52600-71000 MHz.

[0089] In this disclosure, the following terms / abbreviations may be used: Secure User Plane Location: SUPL SUPL Location Platform: SLP Sensing function: SF LTE Positioning Protocol: LPP NR Positioning Protocol A: NRPPa Terrestrial network: TN Non-terrestrial network: NTN Distribution Unit: DU Transmission / Reception Point: TRP Transmission Point: TP Reception Point: RP Enhanced Serving Mobile Location Centre: E-SMLC SUPL Enabled Terminal: SET Non-Access Stratum: NAS Mobile equipment: ME Double active protocol stack: DAPS Data radio bearer: DRB User plane function: UPF Control plane interface between NG-RAN and 5GC: NG-C

[0090] The Xn interface is open. It supports the exchange of signaling information between two NG-RAN nodes and the transfer of PDUs to their respective tunnel endpoints. From a logical point of view, Xn is a point-to-point interface between two NG-RAN nodes. A point-to-point logical interface is possible even if there is no direct physical connection between the two NG-RAN nodes.

[0091] The F1 interface is open. It supports the exchange of signaling information between multiple endpoints and also supports data transmission to each endpoint. From a logical perspective, F1 is a point-to-point interface between two endpoints. A point-to-point logical interface is possible even when there is no direct physical connection between the two endpoints. The F1 interface supports the separation of the control plane and the user plane. The F1 interface separates the radio network layer and the transport network layer. The F1 interface allows the exchange of information associated with the UE and information not associated with the UE. The F1 interface is designed with a forward-looking perspective to meet various new requirements and support new services and new functions. One gNB-CU and one set of gNB-DUs appear to other logical nodes as a gNB or an en-gNB. The gNB terminates the Xn interface and the NG interface. The en-gNB terminates the X2 interface and the S1-U interface. The gNB-CU may be separated into a control plane (CP) and a user plane (UP).

[0092] In the present disclosure, sensing, wireless sensing, and measurement may be read interchangeably.

[0093] In the present disclosure, location, positioning, position, position measurement, position estimation, measurement value, estimated value, measurement result, sensing, sensing information, measurement quantity, measurement content, and measurement type may be read interchangeably.

[0094] In the present disclosure, the terms spatial transmit filter, spatial receive filter, spatial domain transmit filter, spatial domain receive filter, spatial domain filter, spatial filter, and beam may be interpreted interchangeably.

[0095] In the present disclosure, "setting / instructing" and "sending setting / instruction" may be read interchangeably. In the present disclosure, "sending" and "reporting" may be read interchangeably.

[0096] In the present disclosure, the RS / data used for sensing and the sensing resource may be read interchangeably.

[0097] In the present disclosure, the terms object, sensing object, sensing target, target, target, non-UE target, UE target, and sensing target may be interchangeable. In the present disclosure, the sensing target may have communication capability or may not have communication capability. In the present disclosure, the sensing target may include a UE. In the present disclosure, the terms UE target, target with communication capability, target device, and UE may be interchangeable. In the present disclosure, the terms non-UE target and target without communication capability may be interchangeable.

[0098] In the present disclosure, the terms "first signal," "communication signal," "RS," "radar signal," "communication and radar hybrid signal," "integrated signal," "ISAC signal," "sensing signal," and "signal transmitted by a transmitter" may be interchangeable. In the present disclosure, the terms "second signal," "echo signal," "signal impacted by an object," "signal reflected by an object," "signal refracted by an object," "signal diffracted by an object," "signal transmitted and received by a sensing transceiver," and "signal received by a receiver" may be interchangeable.

[0099] In the present disclosure, the terms UE, ME, base station (BS), station, node, NW node (network node), sensing station, sensing transmitting station, sensing receiving station, sensing node, sensing entity, sensing device, wireless communication device, IAB, repeater, reconfigurable intelligent surface (RIS), transmitter, receiver, transceiver, and target may be interchangeable. In the present disclosure, the terms transmit, Tx, and transmitter may be interchangeable. In the present disclosure, the terms receive, Rx, and receiver may be interchangeable. In the present disclosure, the terms transmitter, sensing transmitting station, and transmitting node may be interchangeable. In the present disclosure, the terms receiver, sensing receiving station, and receiving node may be interchangeable. In the present disclosure, the transmitter may be a BS / UE / wireless communication device / transceiver unit. In the present disclosure, the receiver may be a BS / UE / wireless communication device / transceiver unit. In the present disclosure, the transmitter and receiver may be one BS / UE / wireless communication device / transceiver / transceiver unit. In the present disclosure, a transmitter and receiver in the same location, a transceiver, an integrated transceiver, a BS, a UE, and a sensing station may be read interchangeably.

[0100] In the present disclosure, base station (BS), NG-RAN node, gNB, ng-eNB, NG-RAN, RAN, network (NW), TRP, TP, and RP may be read interchangeably.

[0101] In the present disclosure, NW node (network node), server, sensing server, positioning server, 5GC, core network, LMF, AMF, SMF, extended LMF, new SMF, new AMF, SF, SLP, BS, NW, management function, function, and node may be read as interchangeable.

[0102] In the present disclosure, mobility procedure, mobility, handover, change / switching from a source gNB to one or more target gNBs, and change / switching of sensing mode may be read interchangeably.

[0103] In the present disclosure, measurement result, processing result, processed measurement result, measurement-based processing result, reported measurement result, result, value, amount, accuracy, and probability may be read interchangeably.

[0104] In the present disclosure, the terms fault, failure, performance degradation, and condition / event being met may be read interchangeably.

[0105] In the present disclosure, sensing mode, sensing method, sensing type, gNB monostatic sensing, gNB-UE bistatic sensing, UE-gNB bistatic sensing, gNB-gNB bistatic sensing, UE-UE bistatic sensing, and UE monostatic sensing may be read interchangeably.

[0106] In the present disclosure, the wireless communication method and the sensing method may be interpreted as interchangeable.

[0107] (Wireless Communication Method) <Embodiment A0> A sensing mode / method may be defined in the specification. The mode / method may follow at least one of the following options.

[0108] - Option 1 Similar to the NR positioning mode / method, the sensing mode / method may be categorized and supported into UE-based, UE-assisted, LMF-based, SMF-based, and NG-RAN node-assisted versions.

[0109] - Option 2 Sensing modes / methods may be classified and supported in terms of at least one of the aforementioned sensing methods, the aforementioned sensing types, and the aforementioned sensing scenarios.

[0110] Using a similar definition to NR positioning, the association between options 1 and 2 may follow FIG.

[0111] In the following embodiments, the sensing method or sensing mode may refer to either option 1 or 2, or a combination of options 1 and 2.

[0112] According to this embodiment, the UE / base station can use an appropriate sensing mode / method.

[0113] <Embodiment A1> Sensing may reuse / repurpose the architecture and protocols of NR positioning, or may be an extension based on the architecture and protocols of NR positioning.

[0114] 11 shows an example of a sensing architecture. In this example, an extended AMF is used instead of the AMF in the above-described NR positioning architecture, and an extended LMF is used instead of the LMF in the above-described NR positioning architecture.

[0115] The AMF is extended for managing sensing requests, and the LMF is extended for managing coordination and scheduling resources required for sensing.

[0116] Between the NG-RAN node and the LMF, the NRPPa may be extended to support sensing functions, which may include at least one of forwarding sensing-related measurements from the ng-eNB to the LMF, collecting sensing-related data from the gNB, and sending measurement configuration information from the LMF to the NG-RAN node.

[0117] Between the UE and the LMF, the LPP may be extended to support sensing functions for sensing modes / methods related to UE assistance. Multiple sensing information message request / response pairings may be defined for different sensing methods / modes and sensing capability transfer.

[0118] For sensing methods / modes that do not involve a UE (e.g., that do not require a UE to measure DL sensing RS and feedback measurement results related to sensing, or that do not require a UE to transmit UL sensing RS), no LPP extensions may be required.

[0119] <<NRPPa Extensions>> In the NRPPa extensions, at least one of the following sensing-related procedures may be introduced: - Measurement initiation (for a sensing method): It allows an LMF to request an NG-RAN node to report measurements from a sensing method. - Measurement failure indication (for a sensing method): It is a procedure for an NG-RAN node to inform an LMF that measurements for a sensing method previously requested using the Measurement Initiation procedure cannot be reported. - Measurement report (for a sensing method): It is a procedure for an NG-RAN node to provide the LMF with measurements of a sensing method. - Measurement termination (for a sensing method): It terminates periodic measurements for a sensing method performed by an NG-RAN node. - Information exchange (for a sensing method): It allows an LMF to request an NG-RAN node to transfer information of a sensing method to the LMF. - Sensing information exchange (for a sensing method): It is a request for sensing information from the NG-RAN node and is initiated by the LMF. - Sensing information update (for a sensing method): It is an indication to the LMF that a change has occurred, for example, in the sensing RS configuration, use case, target device, environment, sensing area, or new measurement quantity and is initiated by the NG-RAN node. - Sensing activation (for a sensing method): It is a request to the NG-RAN node to activate semi-persistent sensing RS transmission or trigger aperiodic sensing RS transmission and is initiated by the LMF. - Sensing deactivation (for a sensing method): It is an indication to the NG-RAN node that sensing RS transmission should be deactivated and is initiated by the LMF.- Sensing RS configuration exchange (for a certain sensing method): It is a request to the NG-RAN node to configure or update (e.g., turn off) sensing RS transmission and is initiated by the LMF. - Measurement pre-configuration for sensing (for a certain sensing method): It is a request to the serving gNB to provide the necessary information and request the gNB to pre-configure sensing-related configuration and is performed by the LMF. - Measurement activation for sensing (for a certain sensing method): It is a request to the NG-RAN node to activate or deactivate pre-configured sensing measurement-related configuration and is initiated by the LMF. - Sensing method / mode / type update / switch: It updates / activates / deactivates sensing method / mode / use case / target device / environment, etc., with possible sensing RS configuration as well as updating / activating / deactivating measurement reports. - Assistance information transfer / control / feedback: it exchanges some assistance information for decisions regarding sensing methods / RS configuration etc. - Measurement information transfer / report / update / abort / failure indication (for certain sensing methods): it requests one or more TRPs in the NG-RAN node to perform and report sensing measurements, or notifies the NG-RAN node of changes in previously configured measurements, or allows the NG-RAN node to abort ongoing measurements, or notify the LMF that a previously requested measurement cannot be reported.

[0120] Some procedures may reuse / repurpose procedures for NR positioning, and some procedures may be newly introduced for sensing.

[0121] In each procedure, "for a certain sensing method" may be read as "for multiple sensing methods / modes," "for a certain sensing mode," or "for a certain use case / sensing area / environment / target device."

[0122] In some of the above steps, some new information required for sensing may be exchanged, such as the sensing area, the measurement area for sensing, the use case, the target device, the channel mode, the environment, or the measurement results described below.

[0123] An information element (IE) may be defined for each of the aforementioned procedures, each measurement result for each method / mode of sensing, sensing RS configuration, measurement installation, sensing area or measurement area for sensing, use case, target device, channel model, and / or environment. The measurement result may be RSRP, time difference, AoA, AoD, delay, CSI, channel impulse response, power / delay / time domain profile, measurement timing, Doppler / velocity, dropout (of measurements), probability of detection / false detection, etc.

[0124] The NRPPa extension can be applied to any method / mode of sensing in embodiment A0.

[0125] 12 shows a first example of an extended NRPPa procedure. This procedure allows an LMF to request an NG-RAN node to report measurements from sensing method A. The LMF sends a measurement start request for sensing method A to the NG-RAN node. The NG-RAN node then sends a measurement start response for sensing method A to the LMF.

[0126] 13 shows a second example of an enhanced NRPPa procedure. In this procedure, the NG-RAN node provides sensing measurements for the UE to the LMF. The NG-RAN node sends measurement reports of sensing method A to the LMF.

[0127] 14 shows a third example of an enhanced NRPPa procedure. This procedure is initiated by the LMF to request positioning information for the UE from the NG-RAN node. The LMF sends a sensing information request to the NG-RAN node. The NG-RAN node then sends a sensing information response to the LMF.

[0128] Figure 15 shows a fourth example of an extended NRPPa procedure. This procedure is initiated by the LMF to request the NG-RAN node to configure or update (e.g., turn off) sensing RS measurements. The LMF sends a sensing RS configuration request to the NG-RAN node. The NG-RAN node then sends a sensing RS configuration response to the LMF.

[0129] Figure 16 shows an example of an IE for the extended NRPPa. This example shows the IE / group name, the presence of the IE ("M" if mandatory), the number range of the IE (x, or x to y (x..y), where <maxno> indicates the maximum number), the type (e.g., integer or enumeration) and reference of the IE, and a description of the meaning of the IE. The sensing RS resource set list, which is an IE for configuring the sensing RS, includes one or more sensing RS resource set items. Each sensing RS resource set item includes a sensing RS resource set ID, subcarrier spacing, sensing RS bandwidth, starting PRB, period, and repetition factor.

[0130] In the LPP extension, at least one of the following procedures related to sensing may be introduced: Capability transfer procedure for sensing (for a certain sensing method) (e.g. capability transfer procedure, capability indication procedure, receiving LPP requested capabilities, sending LPP offered capabilities): it allows the transfer of capabilities from the UE / target to the server. - Procedures related to Assistance Data Transfer (for certain sensing methods) (e.g. Assistance Data Transfer Procedure, periodic (P) / semi-persistent (SP) / aperiodic (AP)-Assistance Data Transfer Procedure, P / SP / AP-Assistance Data Transfer Procedure with Update Procedure, Assistance Data Delivery Procedure, P / SP / AP-Assistance Data Delivery Procedure, Send LPP Request Assistance Data, Receive LPP Provide Assistance Data): it allows a UE / target to request Assistance Data from a server to assist in sensing and allows the server to transfer the Assistance Data to the UE / target. - Procedures related to sensing information transfer (for a certain sensing method) (e.g., sensing information transfer procedure, sensing information delivery procedure, receiving a location information request message, sending a location information provide message): it allows a server to request sensing measurement data / sensing result estimates from a UE / target and for the UE / target to transfer the sensing measurement data / sensing result estimates to the server. - Error handling procedure: it is how a receiving entity (UE / target or server) behaves when it receives erroneous or unexpected data or detects that certain data is missing. - Abort procedure: it allows a UE / target or server to abort an ongoing procedure due to some unexpected event. It can be used to stop an ongoing procedure.

[0131] Some procedures may reuse / repurpose procedures for NR positioning, and some procedures may be newly introduced for sensing.

[0132] In each procedure, "for a certain sensing method" may be read as "for multiple sensing methods / modes," "for a certain sensing mode," or "for a certain use case / sensing area / environment / target device."

[0133] For a method / mode of sensing or multiple methods / modes of sensing (methods / modes involving a UE, e.g., scenario 3, or scenario 6, or the UE-based version in embodiment A0), multiple associated IEs may be defined in the LPP.

[0134] Different / separate associated IEs may be defined for different methods / modes of sensing. As in the existing LPP specifications, different IEs may be defined for different versions. In the existing LPP specifications, the NR-PositionCalculationAssistance-r16 field in NR-DL-TDOA-ProvideAssistanceData or NR-DL-AoD-ProvideAssistanceData is present for UE-based NR DL-TDOA and is absent otherwise. In this way, a certain IE may be provided only for positioning / sensing of a specific version (e.g., UE-based).

[0135] The extension of LPP may be primarily for sensing methods involving the UE.

[0136] Figure 17 shows a first example of an extended LPP procedure. This procedure is the LPP Capabilities Transfer procedure. The server sends a capabilities request message (RequestCapabilities) to the UE / target. The UE / target then sends a capabilities provision message (ProvideCapabilities) to the server.

[0137] Figure 18 shows a second example of an extended LPP procedure. This procedure is an Assistance Data transfer procedure. The UE / target sends a Request Assistance Data message (RequestAssistenceData) to the server. The server then sends a Provide Assistance Data message (ProvideAssistanceData) to the UE / target. The Provide Assistance Data message may be transferred periodically, semi-persistently, or aperiodically.

[0138] Figure 19 shows a third example of an extended LPP procedure. This procedure is a sensing information transfer procedure. A UE / target sends a sensing information request message (RequestSensingInformation) to a server. The server then sends a sensing information provide message (ProvideSensingInformation) to the UE / target. The sensing information provide message may be transferred periodically, semi-persistently, or aperiodically.

[0139] 20 shows a first example of an IE for an extended LPP. In this example, RequestSensingInformation, which is an IE for requesting sensing information, includes an IIE common to multiple sensing methods (commonIEsRequestSensingInformation), an IE for sensing method A (method-A-RequestSensingInformation), an IE for sensing method B (method-B-RequestSensingInformation), and an IE for sensing method C (method-C-RequestSensingInformation).

[0140] 21 shows a second example of an IE for an extended LPP. In this example, ProvideSensingInformation, which is an IE for providing sensing information, includes an IIE common to multiple sensing methods (commonIEsProvideSensingInformation), an IE for sensing method A (method-A-ProvideSensingInformation), an IE for sensing method B (method-B-ProvideSensingInformation), and an IE for sensing method C (method-C-ProvideSensingInformation).

[0141] 22 shows a third example of an IE for an extended LPP. In this example, METHOD-A-ProvideSensingInformation may include METHOD-A-SignalMeasurementInformation and ecid-Error. METHOD-A-SignalMeasurementInformation may include primaryCellMeasuredResults and measuredResultsList.

[0142] According to this embodiment, the UE / base station can use an appropriate architecture / protocol that is extended for sensing.

[0143] <Embodiment A2> The new architecture and protocol for sensing differ from the architecture and protocol for NR positioning and may include at least one of the following features: - A new AMF is introduced for managing sensing requests. - A new function, sensing management function (SMF), is introduced for managing coordination and scheduling resources required for sensing. - A new protocol (such as NRPPa or based on NRPPa) between the NG-RAN node and the new SMF may be introduced. - A new protocol (such as LPP or based on LPP) between the UE and the new SMF may be introduced.

[0144] Some architectures / protocols may be reused / repurposed / extended (as in embodiment A1), and some architectures / protocols may be newly introduced (as in embodiment A2). Figure 23 shows an example of a sensing architecture related to a combination of embodiment A1 and embodiment A2. In this example, the extended AMF of embodiment A1 is used instead of the AMF in the above-described NR positioning architecture, and a new SMF of embodiment A2 is added and connected to the extended AMF.

[0145] The details of the procedures and IEs for the new protocol may be similar to those in embodiment A1.

[0146] According to this embodiment, the UE / base station may use an appropriate architecture / protocol implemented for sensing.

[0147] <Embodiment A3> The new architecture and protocol for sensing are different from the architecture and protocol for NR positioning, but are connected / interacted with the architecture and protocol for NR positioning and may include at least one of the following features: An additional AMF is introduced to manage sensing requests and their relationship / adaptation to positioning requests. For example, a sensing request may trigger a positioning request, and the positioning results may be reused / repurposed for sensing. For example, a new interface between the existing AMF and the additional AMF may be introduced. An additional (new) sensing management function (SMF) is introduced to manage coordination, scheduling of resources required for sensing, and their relationship / adaptation to positioning. For example, some resources / configurations for positioning (e.g., PRS) and measurements of RSRP / RSRQ / AoA / AoD / time difference may be reused / repurposed for sensing. For example, a new interface between the existing LMF and the additional AMF may be introduced. For example, a new interface between the existing LMF and the additional SMF may be introduced. - A new protocol (such as or based on NRPPa) between the NG-RAN node and the additional SMF may be introduced. - A new protocol (such as or based on LPP) between the UE and the additional SMF may be introduced.

[0148] 24 illustrates an example of a sensing architecture according to embodiment A3. In this example, an additional SMF is connected to the LMF in the above-described NR positioning architecture, and an additional AMF is connected to the AMF, the LMF, and the additional SMF.

[0149] A combination of at least two of the embodiments A1, A2 and A3 may be possible. Different architectures / protocols may be applied in different embodiments.

[0150] 25 illustrates an example of a sensing architecture according to a combination of embodiment A1 and embodiment A3. In this example, an additional SMF is connected to the AMF and LMF in the above-described NR positioning architecture.

[0151] According to this embodiment, the UE / base station can use an appropriate architecture / protocol for positioning-based sensing.

[0152] <Analysis B1> In BS (gNB)-UE bistatic sensing, a base station (e.g., gNB) transmits RS / data (DL sensing resources) used for DL ​​sensing, for example. Then, the UE performs measurements of the RS / data received via the target and reports the sensing results to the NW (e.g., gNB).

[0153] Depending on the use case, different measurement quantities (measurement contents / measurement results) may be applied. However, the UE is not clear about what measurement quantities to measure and report. Therefore, the present inventors have devised a method for appropriately measuring / reporting sensing resources.

[0154] <Embodiment B1> The UE receives sensing RS / data (DL sensing resources) transmitted from the base station (gNB) via a target, such as in BS (gNB)-UE bistatic sensing, and measures (controls measurement). The UE may receive settings / instructions regarding this measurement amount (measurement content / measurement results) from the NW (base station) in advance. For example, the measurement amount may be at least one of the following types:

[0155] [Embodiment B1.1] The UE may measure sensing resources (RS / data) and transmit (report) direct measurement results to the NW (base station). The measurement results may be, for example, at least one of the following Type 1 (1-0 to 1-5):

[0156] Type 1-0: At least one of the following may be included in the NR positioning measurement results for the UE-assisted positioning method: code phase measurement (also called pseudorange), Doppler measurement, carrier phase measurement (also called cumulative delta range), carrier-to-noise ratio of the received signal, measurement quality parameters for each measurement, measurement information for additional paths (non-Global Navigation Satellite system (GNSS) related measurement information), measured cell ID, RS ID, measurement timing, Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Received Signal Strength Indicator (RSSI), absolute radio-frequency channel number (ARFCN), UE receive-transmit time difference, timestamp, barometric pressure sensor measurement, round-trip time, measurement characteristics, reference position, reference time, quality for each measurement, and line-of-sight (LOS) / non-line-of-sight (NLOS) information.

[0157] Type 1-1: At least one of L3-RSRP, L3-RSRQ, L3-RSSI, L1-RSRP, L1-Signal to Interference plus Noise Ratio (SINR), codebook setting (e.g., Type I / II / port selection), Doppler, Non-Coherent Joint Transmission (NCJT) CSI, Coherent Joint Transmission (CJT) CSI, and time domain correlation profile (TDCP).

[0158] Type 1-2: Channel Impulse Response (CIR) and other transforms.

[0159] Type 1-2': Radar cross section (RCS) and other transformations.

[0160] Types 1-3: power delay profile (PDP), or delay profile (DP), or range / delay-Doppler / angle map.

[0161] Type 1-4: At least one of power, delay, phase, and timing of channel response.

[0162] Type 1-5: At least one metric from Types 1-1 to 1-4 may be measured for one or more paths. For example, the strongest X paths may be selected for reporting. "Strongest" may mean that the value of each type of metric is large.

[0163] Each type of measurement may be reported along with other information (e.g., cell ID, RSID, measurement timing, timestamp, LOS / NLOS, quality / reliability of each measurement, etc.).

[0164] According to embodiment B1.1, the UE can determine an appropriate reporting amount for the DL sensing resource and perform appropriate measurements / reports.

[0165] [Embodiment B1.2] The UE may perform measurements on sensing resources (RS / data) according to a use case and transmit (report) the measurement results. The measurement results may be, for example, at least one of the following Type 2 (2-0 to 2-4).

[0166] Type 2-0: At least one of latitude / longitude / altitude (with uncertainty shape), velocity (with uncertainty shape), reference time (e.g., with time correlation from GNSS to NG-RAN and uncertainty shape), indication of positioning / sensing method used, measured cell ID, RSID, ARFCN, measurement timing, UE position estimate (with uncertainty shape), timestamp, reference position, reference time, quality per measurement, LOS / NLOS information. This information may be included in the NR positioning measurement results for UE-based positioning methods.

[0167] Type 2-1: One or more detected objects.

[0168] Type 2-1': Presence or absence of a detected object. In other words, the reported number may be 0.

[0169] Type 2-2: Range of the object to be detected. In other words, it may be not only a specific location, but also a range corresponding to a specific location.

[0170] Type 2-2': Size of the object to be detected.

[0171] Type 2-3: State of the detected object (e.g., speed, direction of movement, path, distance to the object, angle, object identification result, shape identification result, posture identification result, material identification result).

[0172] Types 2-4: Reliability.

[0173] The UE may measure / report statistics (e.g., mean / cumulative distribution function (CDF) / probability density function (PDF) etc.) of the measurement quantities (e.g., each of the above types of information).

[0174] It should be noted that each type of measurement quantity may be measured / reported together with other information (e.g., at least one of cell ID, RS ID, measurement timing, timestamp, LOS / NLOS, and quality / reliability of each measurement).

[0175] The UE may transmit the supported use cases as UE capability information. The UE may receive in advance via higher layer signaling / physical layer signaling a configuration / instruction of measurement quantities to be measured for each use case, and perform measurements / reports based on the configuration / instruction.

[0176] According to embodiment B1.2, the UE can perform appropriate measurement / reporting on the DL sensing resource depending on the use case, thereby achieving the best communication for each use case.

[0177] [Embodiment B1.3] The UE may transmit (report) at least one direct measurement result (Type 1, i.e., any type of embodiment B1.1) and at least one use case-dependent measurement result (Type 2, i.e., any type of embodiment B1.2) separately or together.

[0178] Option 1-3-1: The UE may measure and transmit (report) only measurement quantities of type 1 (any type in embodiment B1.1).

[0179] 26 is a flowchart showing an example of Option 1-3-1. The UE measures DL sensing resources (RS / data) (S101). The UE transmits (reports) direct measurement results (Type 1 measurement results, e.g., related to CSI) based on the measurements of S101 to the gNB / LMF (S102). The gNB / LMF performs calculations / processing / measurements according to the use case based on the reported measurement results to obtain final sensing results (S103). The sensing results of S103 correspond to Type 2 measurement results (any of the types in embodiment B1.2).

[0180] According to option 1-3-1, the UE's processing load can be reduced by limiting the UE's measurements to Type 1 only.

[0181] Option 1-3-2: The UE may obtain and transmit (report) a measurement result of Type 2 (any type of embodiment B1.2) based on a measurement result of Type 1 (any type of embodiment B1.1).

[0182] 27 is a flowchart showing an example of Option 1-3-2. The UE measures DL sensing resources (RS / data) (S201). The UE obtains direct measurement results (Type 1 measurement results, e.g., related to CSI) based on the measurement of S201 (S202). The UE performs calculations / processing / measurements according to the use case based on the measurement results of S202, obtains final sensing results, and reports them to the gNB / LMF (S203). The sensing results of S203 correspond to Type 2 measurement results (any of the types in embodiment B1.2).

[0183] According to Option 1-3-2, the UE can also acquire Type 2 measurement results, allowing it to quickly perform processing according to the measurement results.The UE can also select transmission content according to the Type 2 measurement results.

[0184] Option 1-3-3: The UE may transmit (report) both measurement results of type 1 (any type of embodiment B1.1) (all or part of the measurement results) and measurement results of type 2 (any type of embodiment B1.2) (all or part of the measurement results).

[0185] 28 is a flowchart showing an example of Option 1-3-3. The UE measures DL sensing resources (RS / data) (S301). The UE obtains direct measurement results (Type 1 measurement results, e.g., related to CSI) based on the measurements of S301 (S302). The UE performs calculations / processing / measurements according to the use case based on the measurement results of S302 and obtains measurement results (all or part of the measurement results) (S303). The sensing results of S303 correspond to Type 2 (any type of embodiment B1.2) measurement results. The UE reports the direct measurement results of S302 (all or part of the measurement results) and the measurement results according to the use case of S303 (all or part of the measurement results) to the gNB / LMF (S304).

[0186] According to Option 1-3-3, the UE can select and transmit (report) measurement results of Type 1 and Type 2 depending on the use case, etc.

[0187] Regarding the transmission method when the UE transmits (reports) measurement results, the following options 1-3-4 and 1-3-5 may be applied.

[0188] Option 1-3-4: The UE may transmit the measurement results to the NW using PUCCH / PUSCH as UCI (CSI or other UL control information) or MAC CE or Radio Resource Control (RRC) information element (IE).

[0189] Option 1-3-5: The UE may transmit to the extended LMF for sensing or the new SMF / Sensing Function (SF) using the extended LPP protocol for sensing or the new LPP protocol for sensing, or a protocol based on the LPP protocol. The extended LMF, the new SMF, the LPP protocol, or the protocol based on the LPP protocol may correspond to the sensing architecture and protocols (1) and (2) described above.

[0190] [Variation] The UE may transmit (report) the amount of reporting when at least one of the reporting amounts of each type exceeds a threshold. The threshold may be preset / indicated by higher layer signaling / physical layer signaling. The threshold may be different for each target / path.

[0191] The Type 1 measurement results and the Type 2 measurement results may be transmitted using different methods or the same method. For example, the UE may transmit Type 1 measurement results on the PUCCH and Type 2 measurement results on the PUSCH. The protocols for transmitting Type 1 and Type 2 may be different.

[0192] According to this embodiment, the measurement quantity / measurement method in sensing between the BS (gNB) and the UE is clarified. This allows the UE to appropriately measure / report DL sensing resources, thereby preventing degradation of sensing accuracy / communication quality.

[0193] <Analysis B2> As described in embodiment B1, when measurement quantities and measurement methods for DL ​​sensing resources are applied, it is unclear what configurations are made to the UE and what operations the UE performs. For example, the configurations / selections of spatial transmit filters / spatial receive filters are unclear. Therefore, the present inventors have devised a configuration / operation method for appropriately receiving / measuring / reporting sensing resources.

[0194] <Embodiment B2> The following options may be applied to the configuration related to measurement of DL sensing resources and the corresponding report of the configuration. The UE may receive a configuration / instruction from the NW (e.g., a base station) indicating that the same measurement RS resource (DL sensing resource) is repeatedly transmitted R times (R>=1) in consecutive symbols / slots / specific time units. Then, the UE may receive and measure (control the measurement) the repeatedly transmitted RS resource (DL sensing resource) via a target based on the configuration / instruction.

[0195] This embodiment may be applied in combination with embodiment B1. That is, the UE may receive downlink (DL) sensing resources repeatedly transmitted from the base station (gNB) and received via the target, and control measurement of the repeatedly transmitted DL sensing resources.

[0196] [Embodiment B2.1] The same spatial transmit filter may be used for each of the repeatedly transmitted RS resources (DL sensing resources). The UE may receive from the NW a configuration / instruction regarding the RS resources to be repeatedly transmitted using the same spatial transmit filter (e.g., the same TCI state / QCL-D source RS). For example, if the base station can identify / estimate the target location (range), the measurement accuracy of the UE can be improved by repeatedly transmitting using the same spatial transmit filter (beam).

[0197] <<Option 1>> The UE may change the spatial receive filter for each measurement. The UE may determine the spatial receive filter without using any configuration / instruction. In this case, the UE may apply the following options 1-1 to 1-3. When reporting the measurement quantities (measurement results) of embodiment B1, the following options 1-1 to 1-3 may also be applied.

[0198] Option 1-1: The UE may select / report one (best) measurement result for one measurement sample for reporting, and may further report information / assumptions about the selected spatial receive filter (e.g., TCI state, RS ID of QCL resource, beam ID, RS ID of DL / UL, etc.) corresponding to the selected / reported measurement result.

[0199] Option 1-2: The UE may select up to X (best) measurement results / measurement RSs for reporting, where X<=R, and X may be configured by RRC based on the UE capabilities transmitted by the UE. Then, the UE may report the selected measurement results and also report information / assumptions about spatial receive filters for receiving the selected measurement RSs.

[0200] Option 1-2-1: The UE reports measurements for X resources, in which case the overhead increase is X times that of one resource.

[0201] Option 1-2-2: If some measurement quantities for X resources are the same, the UE may report the same measurement quantity only once. If the measurement quantities for X resources are different, the UE may report the measurement quantities for the X resources. This reduces the number of times the same measurement quantities are reported, thereby reducing overhead.

[0202] Option 1-3: The UE may average / filter X (e.g., best X) measurements and report one processed measurement result. The UE may send this X as UE capability information or it may be configured by RRC signaling.

[0203] The selection of the UE in options 1-1 and 1-2 may be based on calculation results such as the highest / lowest / average strength / range / quality / probability of the measurement results, or may be based on specific rules.

[0204] The UE may assume that the spatial transmit filter for RS transmission and the spatial receive filter for RS reception are the same.

[0205] Option 2: The spatial receive filter of the UE for each measurement may be configured by the network. In this case, Options 1-1 to 1-3 may also be applied. However, in Option 2, the UE does not need to report information / assumptions about its spatial receive filter.

[0206] Note that option 2 may only be applied when R=1.

[0207] If a particular spatial receive filter is applied, the UE may not detect the sensing RS.

[0208] The UE may transmit in advance, as UE capability information, capabilities related to a spatial receive filter for receiving measurement RSs.

[0209] [Embodiment B2.2] A different spatial transmit filter may be used for each of the repeatedly transmitted RS resources (DL sensing resources). The UE may receive from the NW a configuration / instruction of R sensing resources to be repeatedly transmitted using different spatial transmit filters (e.g., via RS in the TCI state / QCL-D). For example, if it is difficult for the base station to identify / estimate the location (range) of the target, repeatedly transmitting using different spatial transmit filters (beams) allows the UE to perform accurate measurements regardless of the target's location.

[0210] <<Option 1>> The UE may use the same spatial receive filter for each measurement. The UE may determine the spatial receive filter without using any configuration / instruction. In this case, the UE may apply the following options 1-1 to 1-3. When reporting the measurement quantity (measurement result) of embodiment B1, the following options 1-1 to 1-3 may also be applied.

[0211] Option 1-1: The UE may select one (best) measurement result for one measurement sample for reporting. Then, the UE may further report information / assumptions about the selected spatial transmit filter (e.g., TCI state, RS ID of QCL resource, beam ID, reordered RS index, etc.) corresponding to the selected / reported measurement result. The UE may or may not report information / assumptions about the spatial receive filter.

[0212] Option 1-2: The UE may select up to X (best X) measurement results for reporting, where X<=R, and X may be configured by RRC based on the UE capabilities transmitted by the UE. Then, the UE may further report information / assumptions about the selected RS / spatial transmit filters corresponding to the selected / reported measurement results. The UE may not report information / assumptions about the spatial receive filters.

[0213] Option 1-2-1: The UE reports measurements for X resources, in which case the overhead increase is X times that of one resource.

[0214] Option 1-2-2: If some measurement quantities for X resources are the same, the UE may report the same measurement quantity only once. If the measurement quantities for X resources are different, the UE may report each measurement quantity for the X resources. This reduces the number of times the same measurement quantities are reported, thereby reducing overhead.

[0215] Option 1-3: The UE may average / filter X (e.g., best X) measurements and report one processed measurement result. The UE may transmit this X as UE capability information or it may be configured by RRC signaling, etc.

[0216] The selection of the UE in options 1-1 and 1-2 may be based on calculation results such as the highest / lowest / average strength / range / quality / probability of the measurement results, or may be based on specific rules.

[0217] <<Option 2>> The UE may use the same spatial receive filter for each measurement. The spatial receive filter of the UE for each measurement may be configured by the network through higher layer signaling / physical layer signaling, etc. The UE may report the configured reporting amount in the same manner as in embodiment B1. In option 2, options 1-1 to 1-3 may also be applied. However, in option 2, the UE may not need to report information / assumptions regarding the spatial receive filter.

[0218] <<Option 3>> The UE may use a different spatial receive filter for each measurement. The spatial receive filter of the UE for each measurement may be determined by the UE. The UE may report the configured reporting amount in the same manner as in embodiment B1. In option 3, options 1-1 to 1-3 may be similarly applied.

[0219] <<Option 4>> The UE may use a different spatial receive filter for each measurement. The spatial receive filter of the UE for each measurement may be configured by the network through higher layer signaling / physical layer signaling, etc. The UE may report the configured reporting amount in the same manner as in embodiment B1. In option 4, options 1-1 to 1-3 may also be applied. However, in option 4, the UE may not need to report information / assumptions regarding the spatial receive filter.

[0220] If a particular spatial receive filter is applied, the UE may not detect the sensing RS.

[0221] The UE may transmit in advance, as UE capability information, capabilities related to a spatial receive filter for receiving measurement RSs.

[0222] According to this embodiment, the method of setting / selecting a spatial transmit filter / spatial receive filter in sensing between the BS (gNB) and the UE becomes clear. This allows the UE to properly receive, measure, and report DL sensing resources (beams), thereby preventing degradation of sensing accuracy / communication quality.

[0223] <Analysis B3> In UE-BS (gNB) bistatic sensing, the UE transmits RS / data (UL sensing resources) used for UL sensing, and the base station (e.g., gNB) measures the RS / data received via the target and reports the sensing results.

[0224] Depending on the use case, different measurement quantities (measurement contents) may be applied. However, it is not clear to the gNB what measurement quantities to measure and report. Therefore, the present inventors have devised a method for appropriately measuring / reporting sensing resources.

[0225] <Embodiment B3> The base station (gNB) receives and measures sensing RS / data (UL sensing resources) transmitted from the UE via a target, such as in UE-BS (gNB) bistatic sensing. The gNB may transmit (report) the measurement quantity (measurement result) to the UE, the extended LMF for sensing, or the new SMF / SF using a protocol based on the NR Positioning Protocol A (NRPPa) protocol for sensing or the new NRPPa protocol for sensing. This measurement quantity (measurement result) may be, for example, at least one of the following types:

[0226] [Embodiment B3.1] A base station (gNB) may measure sensing resources (RS / data) and transmit (report) direct measurement results. The measurement results may be, for example, at least one of the following Type 3 (3-0 to 3-4):

[0227] Type 3-0: Cell ID, timing advance, angle of arrival (azimuth, elevation), RSRP, RSRQ, RSSI, ARFCN, timing information of cell / TRP / RS, DL / UL sensing RS (SSB / CSI-RS / Positioning Reference Signal (PRS) / SRS / new RS) configuration of cell / TRP, reception-transmission time difference at gNB, timestamp, quality of each measurement, beam information of each measurement, LoS / NLoS At least one of these may be included in the NR positioning measurement results for gNB-based positioning methods.

[0228] Type 3-1: CIR and other conversions.

[0229] Type 3-1': Radar cross section (RCS) and other transformations.

[0230] Type 3-2: Power delay profile (PDP), or delay profile (DP), or range / delay-Doppler / angle map.

[0231] Type 3-3: At least one of power, delay, phase, and timing of channel response.

[0232] Type 3-4: At least one of the measurements of types 3-1 to 3-3 may be measured for one or more paths. For example, the strongest X paths may be selected for reporting.

[0233] Each type of measurement may be reported along with other information (e.g., cell ID, RSID, measurement timing, timestamp, LOS / NLOS, quality / reliability of each measurement, etc.).

[0234] According to embodiment B3.1, the gNB can determine the appropriate reporting amount for the UL sensing resource and perform appropriate measurements / reporting.

[0235] [Embodiment B3.2] The gNB may perform measurements on UL sensing resources (RS / data) according to the use case and transmit (report) the measurement results. The measurement results may be, for example, at least one of the following types 4 (4-1 to 4-4).

[0236] Type 4-1: Number of detected targets, one or more.

[0237] Type 4-1': Presence or absence of a detected object. In other words, the reported number may be 0.

[0238] Type 4-2: Range of the object to be detected. In other words, it may be not only a specific location, but also a range corresponding to a specific location.

[0239] Type 4-2': Size of the object to be detected.

[0240] Type 4-3: State of the detected object (e.g., speed, direction of movement, path, distance to the object, angle, object identification result, shape identification result, posture identification result, material identification result).

[0241] Type 4-4: Reliability.

[0242] The UE may measure / report statistics (eg, mean / Cumulative Distribution Function (CDF) / Probability Density Function (PDF) etc.) of the measurement quantities (eg, each of the above types of information).

[0243] The gNB may transmit (report) at least one direct measurement result of the measurement (type 3, i.e., any type of embodiment B3.1) and at least one measurement result according to the use case (type 4, i.e., any type of embodiment B3.2) separately or together.

[0244] Each type of measurement may be reported along with other information (e.g., cell ID, RSID, measurement timing, timestamp, LOS / NLOS, quality / reliability of each measurement, etc.).

[0245] The example of embodiment B1.3 may be similarly used for embodiments B3.1 and B3.2. That is, in embodiment B1.3, Type 1 may be replaced with Type 3, Type 2 with Type 4, DL with UL, UE with gNB, and gNB / LMF (destination) with LMF / SMF / SF.

[0246] The gNB may receive in advance via upper layer signaling / physical layer signaling settings / instructions on the measurement quantities to be measured for each use case, and perform measurements / reports based on those settings / instructions.

[0247] According to embodiment B3.2, the gNB can perform appropriate measurement / reporting on the UL sensing resource depending on the use case, thereby enabling the best communication for each use case.

[0248] <Analysis B4> As described in embodiment B3, when the measurement quantity and measurement method for the UL sensing resource are applied, it is not clear what settings are made to the gNB and what operations the gNB / UE performs. For example, the settings / selection of the spatial transmit filter / spatial receive filter are not clear. Therefore, the present inventors have conceived a setting / operation method for properly receiving / measuring / reporting the sensing resource.

[0249] <Embodiment B4> The following options may be applied to the settings related to measurement of UL sensing resources, reports corresponding to the settings, RS transmission from the UE, etc. The NW (base station, gNB) may transmit to the UE a setting / instruction indicating that the same UL RS resource (UL sensing resource) is to be repeatedly transmitted R times (R>=1) in consecutive symbols / slots / specific time units. The gNB may receive the UL RS resource (UL sensing resource) repeatedly transmitted from the UE via an object and measure it (may control the measurement).

[0250] Option A: The NW may configure the UE with RS resources that are repeatedly transmitted in the same spatial transmission filter, which may be determined by the UE.

[0251] Option B: The NW may configure the UE with RS resources that are repeatedly transmitted in the same spatial transmit filter, which may be configured / instructed by the NW (e.g., using the TCI state ID or QCL-D source RS).

[0252] Option C: The NW may configure the UE with RS resources that are repeatedly transmitted in different spatial transmission filters, which may be determined by the UE.

[0253] Option D: The NW may configure the UE with RS resources that are repeatedly transmitted in different spatial transmit filters, which may be determined by the NW.

[0254] In options A to D, the NW (gNB) may use the same or different spatial receive filters. When the gNB measures the sensing resource (RS / data) and reports the measurement results as in embodiment B3, the following options 1 to 3 may be applied.

[0255] Option 1: The gNB may select one (best) measurement result for one measurement sample for reporting. The gNB may report information / assumptions about the selected RS / spatial transmit filter (e.g., TCI state, RS ID of QCL resource, beam ID, reordered RS index, etc.) corresponding to the selected / reported measurement result. The gNB may or may not report information / assumptions about the spatial receive filter.

[0256] Option 2: The gNB may select up to X (best X) measurement results to report, where X<=R, and X may be set by RRC based on the UE capabilities transmitted by the UE. The gNB may then further report information / assumptions regarding the selected RS / spatial transmit filters corresponding to the selected / reported measurement results.

[0257] Option 2-1: The gNB reports measurements of X resources. In this case, the overhead increase is X times that of one resource.

[0258] Option 2-2: If some measurement quantities for X resources are the same, the gNB may report the same measurement quantity only once. If the measurement quantities for X resources are different, the gNB may report each measurement quantity for the X resources. This reduces the number of times the same measurement quantity is reported, thereby reducing overhead.

[0259] Option 3: The gNB may average / filter X (e.g., best X) measurements and report one processed measurement, where X may be configured by RRC signaling, etc.

[0260] The selection of a gNB in ​​options 1 and 2 may be based on calculation results such as the highest / lowest / average strength / range / quality / probability of the measurement results, or may be based on specific rules.

[0261] When the NW configures a UE with a different spatial transmission filter, it may configure a gap for repeated transmission of the UL sensing resource. The gap may be defined in the specification or may be transmitted by the UE as UE capability information. The gap is the time interval between transmissions of RSs using different spatial transmission filters.

[0262] According to this embodiment, the method of setting / selecting the spatial transmit filter / spatial receive filter in sensing between the UE and the BS (gNB) is clarified. As a result, the gNB can properly receive the UL sensing resource (beam) and measure / report, thereby preventing a deterioration in sensing accuracy / communication quality.

[0263] <Analysis C1> In gNB monostatic sensing, as an object moves, the gNB may lose track of the object. Before that happens, the gNB may trigger a mobility procedure to find another gNB to continue sensing the object, or may trigger a mobility procedure to change to another sensing method with higher accuracy.

[0264] Details are described in embodiment C1 / embodiment C2 for the gNB monostatic sensing method, and differences from embodiment C1 / embodiment C2 for other sensing methods are described.

[0265] In the present disclosure, signaling between the gNB / UE and the SMF may follow embodiment A. In the present disclosure, signaling from the gNB to the UE may follow signaling based on the RRC IE / MAC CE / DCI.

[0266] <Embodiment C1> This embodiment relates to a mobility procedure for sensing.

[0267] The definition of sensing mobility may include changes in at least one of the gNB, UE, and sensing method / mode.

[0268] In the present disclosure, source / target gNB / UE, TRP, IAB, NCR, RIS, and network controlled access point (NCAP) may be interchangeable.

[0269] The triggering of a mobility procedure may be determined by a node from at least one of the following options: ◇Option 1: Enhanced LMF / New SMF / New AMF. In the present disclosure, SMF may represent enhanced LMF / new SMF / new AMF / SF. The SMF may trigger the mobility procedure based on measurement results reported from the gNB or results processed in the SMF. ◇Option 2: Source gNB. The source gNB may trigger the mobility procedure based on results measured or processed by the source gNB.

[0270] One or more target gNBs for mobility may be determined by the node from at least one of the following options. The node may or may not determine the target sensing method / mode: ◇Option 3: SMF. ◇Option 4: Source gNB. A source gNB is more suitable than an SMF for determining the sensing method / mode.

[0271] The combination of options 1 and 4 is not preferred. When the SMF determines the mobility procedure, the SMF may determine one or more target gNBs.

[0272] The one or more target gNBs may follow at least one of the following cases: ◇Case 1: One target gNB using gNB monostatic sensing. ◇Case 2: One gNB-gNB pair using gNB-gNB bistatic sensing. The pair may be two target gNBs, or one main gNB and one cooperative gNB. ◇Case 3: One gNB-UE pair using gNB-UE bistatic sensing. ◇Case 4: One gNB-UE pair using UE-gNB bistatic sensing. ◇Case 5: One target gNB using gNB-UE bistatic sensing. After the mobility procedure, the UE may be selected and configured by the target gNB. ◇Case 6: One target gNB using UE-gNB bistatic sensing. After the mobility procedure, the UE may be selected and configured by the target gNB. Multiple targets in each case, and multiple targets from a combination of different cases may be possible.

[0273] There may or may not be a constraint between the node that decides on the triggering of a mobility procedure (option 1 / 2) and the node that determines one or more target gNBs (option 3 / 4). The constraint may be at least one of the following examples: ◇ The node that decides on the triggering of a mobility procedure is the same as the node that determines one or more target gNBs. ◇ If the node that decides on the triggering of a mobility procedure is a gNB, the node that determines one or more target gNBs may be an SMF or a gNB. If the node that decides on the triggering of a mobility procedure is an SMF, the node that determines one or more target gNBs may also be an SMF.

[0274] The conditions / events for the SMF / gNB to determine mobility / handover procedures / triggering may follow at least one of the following options: ◇ Option 1: The conditions / events depend on the implementation of the SMF / gNB. ◇ Option 2: The conditions / events are defined in the specifications for sensing. The conditions / events may follow at least one of the following options 2-x: - ◇ Option 2-1: For Type 3 measurements directly related to sensing resource measurement results, the event is met if the result / value / quantity / accuracy / probability of the measurement is lower or higher than a defined / configured threshold or within a defined / configured range. The Type 3 measurements may follow at least one of embodiments B1 to B4. The Type 3 measurements may be measured / calculated by the gNB. ◇Option 2-2: For a Type 4 measurement related to a sensing result for a certain use case, the event occurs when the measurement result / value / quantity / accuracy / probability is lower or higher than a defined / configured threshold or within a defined / configured range. The Type 4 measurement may be according to at least one of embodiments B1 to B4. The Type 4 measurement may be measured / calculated by the gNB / SMF. ◇Variation 1: The event may occur when the measurement result / value / quantity / accuracy / probability is lower (bad) or higher (good) than a defined / configured threshold or within a defined / configured range for a specific period of time or occurs a specific number of times. The specific period of time or the specific number of times (threshold) may be defined in the specification or configured by an RRC IE. ◇Variation 2: The event occurs taking into account one or more objects. The number of objects may be defined in the specification or configured by an RRC IE. - Variation 3: A single common condition / event may be applied to a plurality of different measured quantities, or a plurality of individual conditions / events may be applied to each of the different measured quantities.

[0275] According to this embodiment, mobility procedures can be performed properly.

[0276] <Embodiment C2a> This embodiment relates to a case in gNB monostatic sensing that combines options 2 and 3 of embodiment C1 (a case in which the mobility procedure is triggered by the source gNB and the target gNB is determined by the SMF).

[0277] As shown in the example of FIG. 29, when a condition / event in embodiment C1 occurs in a gNB (S301), the source gNB may send a sensing handover request (SENSING HANDOVER REQUEST) message to the SMF (S302). The SMF identifies at least one of one or more target gNBs and one or more corresponding target sensing modes (S303) and may forward the SENSING HANDOVER REQUEST to one or more target gNBs, or may send a new sensing request involving reconfiguration of sensing-related settings to one or more target gNBs (S304). The SMF may then send a sensing handover request acknowledgement (SENSING HANDOVER REQUEST ACKNOWLEDGE) message to the source gNB (S306). The source gNB may continue or stop sensing-related behavior based on information from the SMF (S307). The continuation may include updating. The target gNB may process the request from the SMF (S305).

[0278] In the present disclosure, sensing-related settings may be settings for sensing mode / measurement RS / object / use case / measurement / report / cooperative gNB / paired UE.

[0279] Variation: As in the example of Figure 30, after S305, the SMF may receive a message such as a confirmation / feedback from one or more target gNBs (S406) and then send a SENSING HANDOVER REQUEST ACKNOWLEDGE to the source gNB (S407). One or more target gNBs may determine sensing-related settings themselves and send the sensing-related settings to the SMF in a message such as a confirmation / feedback. The source gNB may continue or stop sensing-related behavior based on information from the SMF (S408). The continuation may include updating.

[0280] If the SMF receives a failure / failure message from one or more target gNBs for a specific time, or fails to receive any message from one or more target gNBs, and the source gNB receives a NACK from the SMF for a specific time, or fails to receive any message from the SMF, the source gNB fails to proceed with the mobility procedure to one or more target gNBs. The failure / failure may be requested / transferred / executed in the source gNB or the SMF. If the request (SENSING HANDOVER REQUEST) fails, the procedure may follow at least one of the following options: ◇ Option 1: The procedure depends on the implementation of the network. ◇ Option 2: The SMF resends the request to the same one or more target gNBs. ◇ Option 3: The SMF re-determines one or more target gNBs and sends the request to a new one or more target gNBs. ◇Option 4: The source gNB resends the request to the SMF.

[0281] The SENSING HANDOVER REQUEST may include at least one of the following pieces of information: ◇At least one of one or more sensing object IDs, information related to other objects, environment IDs, environment-related information, motion IDs, and motion-related information; ◇At least one of an ID related to a sensing use case and a sensing service category; ◇Sensing source gNB ID; ◇At least one of one or more sensing target gNB IDs and a sensing mode at one or more target gNBs; ◇One or more IDs of the sensing mode / method being used (at the source gNB); ◇Sensing RS configuration (at the source gNB); ◇Sensing measurement / reporting configuration (at the source gNB); ◇One or more sensing measurement quantities of one or more objects (IDs) (at the source gNB); ◇Sensing measurement results for at least one of the corresponding measurement quantities and measurement timings (at the source gNB); ◇Sensing measurement result history and corresponding sensing modes / methods. ◇ID of triggered condition / event. ◇Other settings / information related to one or more sensing tasks for one or more object IDs (at the source gNB). ◇Estimated sensing error related information. For example, imperfect calibration error between transmit and receive antennas at the gNB. ◇Current sensing resolution.

[0282] The SENSING HANDOVER REQUEST ACKNOWLEDGE may include at least one of the following pieces of information: ◇ An indicator for at least one of releasing the original sensing configuration, stopping the original sensing behavior, and continuing / updating the original sensing behavior. ◇ At least one of one or more sensing object IDs, information related to other objects, environment IDs, environment-related information, motion IDs, and motion-related information. ◇ At least one of an ID related to a sensing use case and a sensing service category. ◇ One or more sensing target gNB IDs, which may include one gNB ID for monostatic sensing, two gNB IDs for gNB-gNB bistatic sensing, or a gNB ID with or without a paired UE ID for gNB-UE bistatic sensing or UE-gNB bistatic sensing. The two gNB IDs may be one main gNB ID and one cooperating gNB ID. ◇One or more IDs of the sensing mode / method being used (at the target gNB). ◇Sensing RS configuration (at the target gNB). ◇Sensing measurement / reporting configuration (at the target gNB). ◇One or more sensing measurements of one or more objects (IDs) (at the target gNB). ◇Other configurations / information related to one or more sensing tasks for one or more object IDs (at the target gNB). ◇Estimated sensing error related information. For example, imperfect calibration error between the transmit and receive antennas at the target gNB. ◇Current sensing resolution.

[0283] According to this embodiment, in gNB monostatic sensing, in cases where a mobility procedure is triggered by a source gNB and a target gNB is determined by an SMF, the mobility procedure can be performed appropriately.

[0284] <Embodiment C2b> This embodiment relates to a case in gNB monostatic sensing that combines option 2 and option 4 of embodiment C1 (a case in which the mobility procedure is triggered by the source gNB and the target gNB is determined by the source gNB).

[0285] As shown in the example of FIG. 31 , the SMF may send a configuration (pre-configuration) for a sensing / mobility procedure to a source gNB (S501). When a condition / event in embodiment C1 occurs in the gNB (S502), the source gNB may determine at least one of one or more target gNBs and one or more corresponding target sensing modes (S503). The determination may follow at least one of the following options: ◇ Option 1: The determination depends on the implementation. For example, the determination is based on an estimation of the movement path of the object. ◇ Option 2: The determination is based on a configuration / instruction from the SMF. The configuration / instruction may be a configuration / instruction for at least one of a use case and an object.

[0286] The source gNB may send a SENSING HANDOVER REQUEST message directly to one or more target gNBs (S504). One or more target gNBs may process the information in the SENSING HANDOVER REQUEST, take over and participate in the sensing task for the indicated object ID (S505), and send a SENSING HANDOVER REQUEST ACKNOWLEDGE message to the source gNB (S506). The source gNB may continue or stop the transmission / measurement behavior of the sensing measurement RS (S507). The continuation may include updating.

[0287] The contents of the SENSING HANDOVER REQUEST and SENSING HANDOVER REQUEST ACKNOWLEDGE may be similar to those of embodiment C2a. The SENSING HANDOVER REQUEST ACKNOWLEDGE may include a message such as confirmation / feedback, or may include sensing-related settings from one or more target gNBs.

[0288] According to this embodiment, in gNB monostatic sensing, in cases where a mobility procedure is triggered by a source gNB and a target gNB is determined by the source gNB, the mobility procedure can be performed appropriately.

[0289] <Embodiment C2c> This embodiment relates to a case in gNB monostatic sensing that combines option 1 and option 3 of embodiment C1 (a case in which a mobility procedure is triggered by the SMF and the target gNB is determined by the SMF).

[0290] As shown in the example of Figure 32, the source gNB may send a sensing measurement report to the SMF (S601). When a condition / event in embodiment C1 occurs in the SMF (S602), the SMF determines at least one of one or more target gNBs and one or more corresponding target sensing modes (S603) and may send a SENSING HANDOVER REQUEST message to one or more target gNBs, or may send a new sensing request involving reconfiguration of sensing-related settings to one or more target gNBs (S604). The SMF may then send a SENSING HANDOVER CONFIG RELEASE message to the source gNB (S607). The source gNB may continue or stop sensing-related behavior based on the SMF configuration (S608). The continuation may include updating.

[0291] Variation: After S605, the SMF may receive a message such as confirmation / feedback from one or more target gNBs (S606) and send a SENSING CONFIG to the source gNB (S607).

[0292] The content of the SENSING HANDOVER REQUEST may be similar to that of embodiment C2a. The content of the SENSING HANDOVER REQUEST may include sensing configuration information for one or more target gNBs. The sensing configuration information may include, for example, at least one of the following: a sensing mode / method being used (for the target gNB), a sensing RS configuration, a sensing measurement / reporting configuration, one or more sensing measurements for sensing of one or more object IDs, and other configurations / information related to the sensing task for one or more object IDs (e.g., IDs of cooperating gNBs or IDs of paired UEs).

[0293] The contents of SENSING CONFIG / SENSING HANDOVER CONFIG RELEASE may include instructions to the source gNB on whether to continue / release / update sensing-related settings / behaviors, or may include sensing configuration information of one or more target gNBs.

[0294] According to this embodiment, in gNB monostatic sensing, in cases where a mobility procedure is triggered by an SMF and a target gNB is determined by the SMF, the mobility procedure can be executed appropriately.

[0295] <Embodiment C2d> This embodiment relates to a case in which, in gNB monostatic sensing, options 1 and 3 of embodiment C1 are combined (a case in which a mobility procedure is triggered by the SMF and the target gNB is determined by the SMF).

[0296] As shown in the example of Figure 33, the source gNB may send a sensing measurement report to the SMF (S701). When a condition / event in embodiment C1 occurs in the SMF (S702), the SMF may determine at least one of one or more target gNBs and one or more corresponding target sensing modes (S703) and send a sensing handover configuration (SENSING HANDOVER CONFIG) message to the source gNB (S704). The source gNB may send a SENSING HANDOVER REQUEST directly to one or more target gNBs (S705). Here, the source gNB may directly forward some information from the SENSING HANDOVER CONFIG via the SENSING HANDOVER REQUEST. After processing the information in the SENSING HANDOVER REQUEST, one or more target gNBs may take over and participate in sensing tasks for the indicated one or more object IDs (S706) and send a SENSING HANDOVER REQUEST ACKNOWLEDGE message to the source gNB (S707). The source gNB may continue or stop the transmission / measurement behavior of the sensing measurement RS based on the instruction of the SMF from the SENSING HANDOVER CONFIG (S708). The continuation may include updating.

[0297] When the SMF determines the target gNB, it is preferable that the SMF directly configures the target gNB (embodiment C2c).

[0298] The contents of the SENSING HANDOVER CONFIG may be similar to those of embodiment C2c, or may include at least one of the following pieces of information: ◇At least one of one or more sensing object IDs, information related to other objects, environment IDs, environment-related information, motion IDs, and motion-related information. The motion may be the motion of an object. ◇An ID related to a sensing use case. ◇One or more sensing target gNB IDs. This may include one gNB ID for monostatic sensing, two gNB IDs for gNB-gNB bistatic sensing, or a gNB ID with or without a paired UE ID for gNB-UE bistatic sensing or UE-gNB bistatic sensing. The two gNB IDs may be one main gNB ID and one cooperating gNB ID. ◇One or more IDs of sensing modes / methods used in one or more target gNBs. ◇Sensing RS configuration (at the target gNB). ◇Sensing measurement / reporting configuration (at the target gNB). ◇One or more sensing measurements of one or more objects (IDs) (at the target gNB). ◇Other configurations / information related to one or more sensing tasks for one or more object IDs (at the target gNB). ◇Estimated sensing error related information. For example, imperfect calibration error between transmit and receive antennas at the target gNB. ◇Continuing / updating / stopping at least one of sensing related configuration for the source gNB and updated sensing related configuration for the source gNB. The updated sensing related configuration may include a change in sensing resolution within a specific sensing service category. ◇Sensing service category.

[0299] The SENSING HANDOVER CONFIG may include the contents in the SENSING HANDOVER REQUEST or may include the contents in the SENSING HANDOVER REQUEST ACKNOWLEDGE.

[0300] If the source gNB receives a NACK / failure / failure from the SMF or fails to receive any message from the SMF for a specific time, the source gNB fails to proceed with the mobility procedure to the target gNB. The failure / failure may be requested / transferred / performed in the SMF or the source gNB. If the request (SENSING HANDOVER CONFIG / SENSING HANDOVER REQUEST) fails, the procedure may follow at least one of the following options: ◇ Option 1: The procedure depends on the NW implementation. ◇ Option 2: The SMF resends the request to the same target gNB(s). ◇ Option 3: The SMF re-determines one or more target gNBs and sends the request to a new target gNB(s).

[0301] According to this embodiment, in gNB monostatic sensing, in cases where a mobility procedure is triggered by an SMF and a target gNB is determined by the SMF, the mobility procedure can be executed appropriately.

[0302] <Analysis C2> In gNB-UE bistatic sensing involving object / UE movement, the following operations are possible:

[0303] ◇When a UE loses sight of an object (fails to track an object), the following cases are possible: - ◇Case 1: If the gNB can recognize that the UE has failed to track based on at least one of the periodic measurement reports of the sensing RS by the UE, the position of the object, and the position of the UE, the gNB can configure another UE for sensing by configuring periodic sensing for that UE. - ◇Case 2: A new report regarding tracking failure / failure by the UE may be introduced (embodiment C3 described below).

[0304] ◇ (When the gNB can distinguish between a gNB's failure to track and a UE's failure to track) If the gNB loses sight of an object (fails to track an object), the gNB may discover one or more target gNBs with or without a new sensing mode and trigger a mobility procedure to continue sensing functions for the object (embodiment C4 described below). Even if the gNB cannot distinguish between a gNB's failure to track and a UE's failure to track, the gNB can decide whether / how to trigger a mobility procedure as long as the conditions for the UE in embodiment 3 are met and the UE reports to the gNB or the conditions for the gNB in ​​embodiment C4 are met.

[0305] A relationship between existing handover for communication and mobility for sensing may be defined (embodiment C5 described below).

[0306] In UE-gNB bistatic sensing involving object / UE movement, several operations are possible:

[0307] If the UE loses sight of the object (fails to track the object), the gNB can recognize the sensing state based on measurements by the gNB, and can configure another UE for sensing by periodic sensing configuration for that UE.

[0308] ◇If the gNB loses sight of an object (fails to track the object) (when the gNB can distinguish between the gNB failing to track and the UE failing to track), the gNB may discover one or more target gNBs with or without a new sensing mode and trigger a mobility procedure to continue sensing functions for the object (embodiment C4 described below).

[0309] A relationship between existing handover for communication and mobility for sensing may be defined (embodiment C5 described below).

[0310] <Embodiment C3> This embodiment relates to a procedure when a UE fails to be tracked in gNB-UE bistatic sensing (sensing / tracking failure / performance degradation occurs in the UE).

[0311] The condition / event that triggers the UE to report at least one of the following possibilities: sensing failure, sensing fluctuation, UE change, indication of failure to track a configured object, and indication of reduced accuracy of a sensing task may follow at least one of several options 3-x below: Option 3-1: For Type 1 measurements directly related to sensing resource measurement results, the event is met if the result / value / quantity / accuracy / probability of the measurement is lower or higher than a defined / configured threshold or within a defined / configured range. The Type 1 measurements may follow at least one of embodiments B1 to B4. The Type 1 measurements may be measured / calculated by the UE. Option 3-2: For Type 2 measurements related to sensing results for a use case, the event is met if the result / value / quantity / accuracy / probability of the measurement is lower or higher than a defined / configured threshold or within a defined / configured range. The Type 2 measurements may follow at least one of embodiments B1 to B4. Type 2 measurements may be measured / calculated by the UE. - ◇Variation 1: An event may be when the measurement result / value / quantity / accuracy / probability is lower (bad) or higher (good) than a defined / configured threshold, or within a defined / configured range, for a specific time or a specific number of times. The specific time or number of times (threshold) may be defined in the specification or may be configured by an RRC IE. - ◇Variation 2: An event occurs taking into account one or multiple objects. The number of objects may be defined in the specification or may be configured by an RRC IE. - ◇Variation 3: A common condition / event may apply to multiple different measurements, or multiple individual conditions / events may apply to each of them.

[0312] After the event is triggered, the UE may send a new report to the gNB to report the possible sensing failure. The report may follow at least one of the following characteristics:

[0313] ◇The report may include at least one of the following pieces of information: -◇Sensing failure indicator. -◇At least one of one or more sensing object IDs, information related to other objects, environment ID, environment related information, motion ID, and motion related information. The motion may be object motion. -◇At least one of an ID related to the sensing use case and a sensing service category. -◇Sensing measurement results. -◇L1 / L3 measurement results for existing communications. -◇Trigger event ID. -◇IDs of candidate target gNBs and L1 / L3 measurement results for existing communications. -◇Operated sensing resolution.

[0314] The content of the report may be the same as the measurement / reporting behavior of the UE to the sensing RS in at least one of embodiments B1 to B4. Here, a new event may be introduced to trigger the event-triggered sensing result report.

[0315] The reporting format may be RRC IE / MAC CE / UCI.

[0316] According to this embodiment, in gNB-UE bistatic sensing, the UE can properly report tracking failure / failure.

[0317] <Embodiment C4a> This embodiment relates to triggering a mobility procedure by a source gNB when the gNB fails tracking in bistatic sensing (sensing / tracking failure / performance degradation occurs in the UE).

[0318] The source gNB may trigger a mobility procedure based on at least one of a report by the UE and measurements / estimations by the gNB. The triggering may follow at least one of the following options: ◇ Option 1: The source gNB reconfigures another UE within its coverage area using a sensing measurement / report configuration for gNB-UE bistatic sensing. ◇ Option 2: The source gNB sends a SENSING HANDOVER REQUEST to the SMF or one or more target gNBs using a procedure similar to embodiment C2a / embodiment C2b. The one or more target gNBs may follow any of cases 1 to 6 in embodiment C1. After receiving feedback / instruction from the SMF, the SMF may instruct the gNB to reconfigure another UE for gNB-UE bistatic sensing or may instruct another gNB to communicate with the same source UE.

[0319] The content of the SENSING HANDOVER REQUEST may be the same as that of embodiment C2a / embodiment C2b. Its content may follow some of the following characteristics:

[0320] ◇In gNB-UE bistatic sensing, the content may further include at least one of the following pieces of information: -◇ID of the UE performing the sensing measurement. -◇Sensing measurement report from the UE or processed measurement results from the source gNB. -◇L1 / L3 measurement results for existing communications. -◇Information related to estimated sensing errors in this case, for example, errors of imperfect synchronization between the gNB and the UE.

[0321] ◇In UE-gNB bistatic sensing, the content may further include at least one of the following pieces of information: - ◇ID of the UE transmitting the sensing RS. - ◇Sensing measurement results or processed measurement results by the source gNB. - ◇Information related to estimated sensing errors in this case, for example, errors of imperfect synchronization between the gNB and the UE.

[0322] The content of the SENSING HANDOVER REQUEST ACKNOWLEDGE may be the same as in embodiment C2a / embodiment C2b. The procedure for failure / failure (upon receiving a NACK or waiting for a specific time) may be the same as in embodiment C2a / embodiment C2b. If it is decided to maintain gNB-UE bistatic sensing, the content of the SENSING HANDOVER REQUEST ACKNOWLEDGE may include at least one of discovering another UE using the source gNB for gNB-UE bistatic sensing, handing over from the source gNB / UE to another target gNB (via an existing RRCReconfiguration message in the SENSING HANDOVER REQUEST ACKNOWLEDGE), and corresponding configuration signaling.

[0323] According to this embodiment, if the gNB fails to track during bistatic sensing, the source gNB can appropriately trigger a mobility procedure.

[0324] <Embodiment C4b> This embodiment relates to triggering a mobility procedure by an SMF when a gNB fails tracking in bistatic sensing.

[0325] The SMF may decide to trigger a mobility procedure and determine a target gNB based on a report by the UE or the gNB using a procedure similar to that of embodiment C2c / embodiment C2d. One or more target gNBs may follow any of cases 1 to 6 in embodiment C1. The SMF may decide a source gNB to reconfigure another UE for gNB-UE bistatic sensing, or may decide to have the source gNB perform a handover from the source gNB / UE to the target gNB (if it decides to maintain gNB-UE bistatic sensing).

[0326] The content of the SENSING HANDOVER REQUEST may be the same as in embodiment C2c. The content of the SENSING HANDOVER CONFIG may be the same as in embodiment C2d. The procedure for failure / failure (upon receiving a NACK or waiting for a specific time) may be the same as in embodiment C2d. The content of the SENSING HANDOVER REQUEST / SENSING HANDOVER CONFIG may further include additional information of the IDs of the involved sensing UEs.

[0327] According to this embodiment, if the gNB fails to track during bistatic sensing, the SMF can appropriately trigger a mobility procedure.

[0328] <Embodiment C5> This embodiment relates to the relationship between existing handover for communication and mobility for sensing.

[0329] In the case where one UE is configured for both communication and sensing (one UE has received configurations for both communication and sensing), the UE may be configured separately for measurement reporting for communication and measurement reporting for sensing.

[0330] Mobility procedures / signaling for communication and sensing may follow at least one of several options: ◇Option 1: Separate / individual procedures / signaling. In this case, individual handover signaling / procedures may be introduced for communication and sensing based on corresponding measurement reports. ◇Option 2: Common procedures / signaling. In this case, the gNB / UE may perform a common handover based on joint consideration of measurement reports for communication and sensing. The gNB / UE may perform a common handover for communication and sensing based on measurement reports for at least one of communication and sensing.

[0331] Whether the gNB triggers a sensing mobility procedure may follow at least one of the following options: ◇ Option 1: Whether the gNB triggers a sensing mobility procedure is based on a joint consideration of measurement reports (conditions / events) for communication and sensing. ◇ Option 2: Whether the gNB triggers a sensing mobility procedure is based on measurement reports (conditions / events) for sensing. ◇ Option 3: If an existing communication mobility procedure is triggered by a UE, the sensing mobility procedure is also triggered / performed by the UE.

[0332] According to this embodiment, the relationship between existing handover for communication and mobility for sensing can be clarified.

[0333] <Analysis C3> In gNB-gNB bistatic sensing involving the movement of an object / UE, the gNB may lose sight of the object / UE (fail to track the object). Before this happens, the gNB may trigger a mobility procedure. This triggering may follow at least one of the following cases: ◇Case 1: The cooperative gNB is changed (see embodiment C6 below). This may mean that the source gNB and the gNB-gNB bistatic sensing mode are maintained. ◇Case 2: The source gNB, or at least one of the source gNB, cooperative gNB, and sensing mode, is changed (see embodiment C7 below). This may not mean that the target gNB is in gNB-gNB bistatic sensing mode.

[0334] <Embodiment C6> This embodiment relates to mobility procedures for gNB-gNB bistatic sensing.

[0335] The triggering of the mobility procedure may be determined by at least one of the following options: ◇Option 1: SMF. ◇Option 2: Source gNB. The decision may be implementation dependent or may be based on the conditions / events of embodiment C1. ◇Option 3: Cooperative gNB. The decision may be implementation dependent or may be based on the conditions / events of embodiment C1.

[0336] For mobility, the target gNB and the target sensing method / mode may be determined by at least one of the following options: ◇Option 4: SMF. ◇Option 5: Source gNB. ◇Option 6: Cooperative gNB.

[0337] ◇ In determining the sensing method / mode, SMF is more preferable.

[0338] ◇When the SMF decides to trigger a mobility procedure, it is preferable that the SMF also decides the target gNB.

[0339] ◇One or more target gNBs may follow any of cases 1 to 6 of embodiment C1.

[0340] In the case of option 1, the SMF may determine one or more new target cooperating gNBs. The SMF may send an indication / configuration of (IDs of) one or more new target gNBs for cooperation with one or more gNBs to the source gNB. The indication / configuration may be similar to the SENSING HANDOVER CONFIG in embodiment C2d. The mobility procedure may follow at least one of several options 1-x below.

[0341] ◇Option 1-1: The source gNB may send a SENSING HANDOVER REQUEST to one or more new target gNBs to establish a new gNB sensing pair, or may send a reconfiguration of sensing-related settings to one or more new target gNBs. The signaling / procedure may be the same as in embodiment C2d. Prior to that, the source gNB may send a configuration / instruction to release the sensing configuration to the original cooperating gNB.

[0342] ◇Option 1-2: The SMF may send a SENSING HANDOVER REQUEST to one or more new target gNBs together with the ID of the source gNB and the sensing-related configuration from the source gNB, or may send a reconfiguration of the sensing-related configuration to one or more new target gNBs. The signaling / procedure may be the same as in embodiment C2c.

[0343] In the case of option 2 / 3, a procedure similar to embodiment C2a / embodiment C2b may be adapted / reused. The content of the SENSING HANDOVER REQUEST may further include an estimated sensing error in this case (e.g., an error of imperfect synchronization between the source gNB and the cooperating gNB).

[0344] According to this embodiment, the mobility procedure of gNB-gNB bistatic sensing can be performed properly.

[0345] <Embodiment C7> This embodiment relates to another form of mobility procedure for gNB-gNB bistatic sensing.

[0346] The triggering of the mobility procedure may be determined by at least one of options 1 to 3 of embodiment C6.

[0347] For mobility, the target gNB and the target sensing method / mode may be determined by at least one of options 4 to 6 of embodiment C6.

[0348] In the case of option 1, the SMF may determine one or more new target cooperating gNBs and a sensing mode for the corresponding object. The SMF may send an indication / configuration of (the IDs of) one or more new target gNBs to the source gNB. The indication / configuration may be similar to the SENSING HANDOVER CONFIG in embodiment C2d. The mobility procedure may follow at least one of the following options 1-x.

[0349] ◇Option 1-1: The source gNB may send a SENSING HANDOVER REQUEST to one or more new target gNBs. After receiving a SENSING HANDOVER REQUEST ACKNOWLEDGE from one or more new target gNBs, the source gNB may continue / stop / update sensing-related behavior.

[0350] ◇Option 1-2: The SMF may send a SENSING HANDOVER REQUEST to one or more new target gNBs. The source gNB may continue / stop / update sensing-related behavior.

[0351] ◇One or more target gNBs may follow any of cases 1 to 6 of embodiment C1. That is, the one or more new target gNBs may be only the new target gNB (the sensing mode may be determined to be gNB monostatic sensing), new multiple target gNBs (both the new main gNB and the new cooperative gNBs) (the sensing mode may be maintained at gNB-gNB bistatic sensing), or the new target gNB and paired UE (the sensing mode may be determined to be gNB-UE or UE-gNB bistatic sensing).

[0352] ◇In the above-mentioned option 1-x, the SENSING HANDOVER REQUEST or SENSING HANDOVER CONFIG may include indication / configuration of only the new target gNB, may include indication / configuration of multiple new target gNBs (both the new main gNB and the new cooperating gNBs), or may include indication / configuration of the new target gNB and the UE to be paired.

[0353] In the case of option 2 / 3, the same procedure as in embodiment C2a / embodiment C2b may be adapted / reused. One or more target gNBs may follow any of cases 1 to 6 of embodiment C1. That is, the one or more new target gNBs may be only the new target gNB (the sensing mode may be determined to be gNB monostatic sensing), new multiple target gNBs (both the new main gNB and the new cooperative gNBs) (the sensing mode may be maintained at gNB-gNB bistatic sensing), or the new target gNB and paired UEs (the sensing mode may be determined to be gNB-UE or UE-gNB bistatic sensing). The content of the SENSING HANDOVER REQUEST may further include an estimated sensing error in this case (e.g., an error due to imperfect synchronization between the source gNB and the cooperative gNBs).

[0354] According to this embodiment, the mobility procedure of gNB-gNB bistatic sensing can be performed properly.

[0355] <Embodiment C8> This embodiment relates to restrictions on changing the sensing mode in a mobility procedure.

[0356] When changing to a sensing mode (target sensing mode, target mode, second mode) different from the sensing mode of the source gNB, the target gNB determined by the source gNB or SMF may be at least one of the following options: ◇ Option 1: One or more gNBs with (supporting / configured / using) the same sensing mode as the sensing mode of the source gNB. ◇ Option 2: One or more gNBs with (supporting / configured / using) the same or different sensing mode as the sensing mode of the source gNB.

[0357] In the sensing mode of a mobility procedure, there may be a rule for the sensing mode of the source gNB and the sensing mode of one or more target gNBs. The rule may be defined in a specification, configured / indicated, or reported as capability information. The rule may follow at least one of the following example options: ◇Example 1: If the sensing mode of the source gNB is gNB monostatic sensing, the sensing mode of one or more target gNBs is either gNB monostatic sensing or gNB-gNB bistatic sensing. ◇Example 2: If the sensing mode of the source gNB is gNB-UE bistatic sensing, the sensing mode of one or more target gNBs is either gNB-UE bistatic sensing or UE-gNB bistatic sensing. ◇Example 3: When the sensing mode of the source gNB is gNB monostatic sensing, the sensing mode of one or more target gNBs is either gNB monostatic sensing, gNB-gNB bistatic sensing, gNB-UE bistatic sensing, or UE-gNB bistatic sensing. ◇Example 4: When the sensing mode of the source gNB is gNB-UE bistatic sensing, the sensing mode of one or more target gNBs is either gNB-gNB bistatic sensing, gNB-UE bistatic sensing, UE-gNB bistatic sensing, or gNB-gNB bistatic sensing. ◇Example 5: The sensing mode of one or more target gNBs depends on the capability of the target gNB. The capability may be to support gNB monostatic sensing / full-duplex communication.

[0358] According to this embodiment, an appropriate sensing mode can be applied in the mobility procedure.

[0359] <NW Node (Network Node)> As in the example of Fig. 34 , the NW node 31 may have a control unit 310 and a transceiver unit 320. The control unit 310 performs the procedures / operations in each embodiment and controls the transceiver unit 320. The transceiver unit 320 has a transmission path interface with at least one of the core network 30, the base station 10, and another NW node 31. The hardware configuration of the NW node 31 may be the same as the hardware configuration of the base station 10 and the user terminal 20 described below. The NW node 31 may include an extended LMF / new SMF / new AMF / SMF / SF / base station 10 (gNB).

[0360] The control unit 310 may control at least one change (e.g., mobility procedure) of the base station 10 for sensing, the terminal 20 for sensing, and the sensing mode (e.g., sensing mode / method) when information (e.g., measurement result, processing result) based on measurement of a signal for sensing (e.g., sensing RS) satisfies a condition (e.g., condition / event). The transceiver unit 320 may perform at least one of transmission and reception of a message for the change (e.g., at least one of SENSING HANDOVER REQUEST, SENSING HANDOVER REQUEST ACKNOWLEDGE, SENSING HANDOVER CONFIG, and SENSING HANDOVER CONFIG RELEASE).

[0361] The base station 10 may transmit and receive the signals (e.g., gNB monostatic sensing). The change may change the base station to one or more other target base stations.

[0362] A transmitter (e.g., a gNB / UE, a main gNB / UE) may transmit the signal, and a receiver (e.g., another gNB / UE, a cooperative gNB / UE) may receive the signal (e.g., bistatic sensing). The change may change the source base station (e.g., a source gNB) 10 of at least one of the transmitter and the receiver to one or more other target base stations (e.g., target gNBs) 10.

[0363] When the base station (e.g., source gNB) 10 is changed to a target base station (e.g., target gNB) 10, the change may change the mode to the second mode based on a constraint between the mode (e.g., the sensing mode before the change) and a second mode of sensing at the target base station (e.g., the sensing mode after the change).

[0364] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0365] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0366] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0367] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0368] [Notification of Information from UE] In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0369] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0370] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0371] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0372] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling (RRC IE / MAC CE / UCI).

[0373] The specific condition may indicate at least one of the following: ◇ At least one of the above-mentioned embodiments is enabled.

[0374] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0375] The specific UE capability may indicate at least one of the following: ◇ That the UE supports specific procedures / processes / operations / controls / information for at least one of the above embodiments. ◇ Use cases supported by the UE. ◇ Sensing modes / methods supported by the UE. ◇ At least one of sensing measurement quantities and corresponding accuracies supported by the UE. ◇ Sensing measurement reporting configurations supported by the UE. ◇ The maximum number of sensing objects per use case supported by the UE. ◇ At least one of conditions / events for mobility procedures supported by the UE and reports triggered by the conditions / events. ◇ At least one of sensing RSs supported by the UE and sensing RS configurations supported by the BS. ◇ Sensing RS measurement capabilities supported by the UE. ◇ Sensing error improvement methods supported by the UE. ◇ At least one of UE support of mobility procedures for sensing and mobility procedures supported by the BS.

[0376] UE capabilities may be read as BS capabilities. UE capabilities may be reported to a server / LMF / SF / BS / another UE. BS capabilities may be reported to a server / LMF / SF / UE / another BS.

[0377] The specific BS capability may indicate at least one of the following: ◇BS support of specific procedures / processes / operations / control / information for at least one of the above embodiments; ◇Use cases supported by the BS; ◇Sensing modes / methods supported by the BS; ◇At least one of sensing measurement quantities and corresponding accuracies supported by the BS; ◇Sensing measurement reporting configurations supported by the BS; ◇The maximum number of sensing objects per use case supported by the BS; ◇At least one of conditions / events for mobility procedures supported by the BS and reports triggered by the conditions / events; ◇At least one of sensing RSs supported by the BS and sensing RS configurations supported by the BS; ◇Sensing RS measurement capabilities supported by the BS; ◇Sensing error improvement methods supported by the BS; ◇BS support of identifying one or more target BSs for mobility procedures; ◇At least one of mobility procedures for sensing supported by the BS and mobility procedures supported by the BS.

[0378] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0379] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0380] Furthermore, at least one of the above-described embodiments may be applied when a UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer signaling / physical layer signaling. The specific information may indicate at least one of the following: ◇ Information indicating enabling / disabling the operations of the above-described embodiments. ◇ RRC parameters for a specific release or a specific RAT. In Rel. YY (e.g., YY is 18 or greater), the RRC parameters enabling operation XXX may be represented as XXX_rYY (XXX-rYY).

[0381] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, Rel. 15 / 16 behavior.

[0382] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A network node having: a control unit that controls a base station for sensing, a terminal for sensing, and at least one change of the sensing mode when information based on measurement of a signal for sensing satisfies a condition; and a transceiver unit that performs at least one of transmitting and receiving a message for the change. [Supplementary Note 2] The network node according to Supplementary Note 1, wherein the base station transmits and receives the signal, and the change involves changing the base station to one or more other target base stations. [Supplementary Note 3] The network node according to Supplementary Note 1 or Supplementary Note 2, wherein a transmitter transmits the signal and a receiver receives the signal, and the change involves changing at least one of a source base station of the transmitter and the receiver to one or more other target base stations. [Supplementary Note 4] The network node according to any of Supplements 1 to 3, wherein, when the base station is changed to a target base station, the change involves changing the mode to the second mode based on a constraint between the mode and a second mode of sensing in the target base station.

[0383] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A terminal having: a receiving unit that receives a signal for sensing; and a control unit that controls transmission of a report of a failure in the sensing when information based on measurement of the signal satisfies a condition. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the condition is deterioration of performance of tracking an object in the sensing. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein, after the report, the control unit changes one or more base stations that transmit the signal for sensing. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the report includes at least one of the failure, the object, the sensing environment, movement of the object, a use case of the sensing, a category of the sensing, a result of the measurement, a measurement result of a communication signal, the condition, candidate base stations that transmit the signal for sensing, and a resolution of the sensing.

[0384] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A terminal having: a receiving unit that receives communication and sensing configuration; and a control unit that controls transmission of a first report of measurement for the communication and transmission of a second report of measurement for the sensing. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein, after at least one of the first report and the second report, the control unit changes one or more base stations associated with at least one of the communication and the sensing. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit executes a procedure for changing one or more base stations associated with the sensing separately from a procedure for changing one or more base stations associated with the communication. [Supplementary Note 4] The terminal according to any of Supplementary Notes 1 to 3, wherein the control unit executes a procedure for changing one or more base stations associated with the communication and the sensing.

[0385] (Wireless Communication System) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0386] 35 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) specified by the Third Generation Partnership Project (3GPP), 5th generation mobile communication system New Radio (5G NR), or the like.

[0387] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0388] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0389] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0390] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0391] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

[0392] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.

[0393] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0394] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0395] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0396] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

[0397] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0398] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0399] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0400] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0401] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.

[0402] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

[0403] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0404] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0405] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0406] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0407] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0408] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0409] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0410] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0411] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0412] The core network 20 (a server in the core network 20) ​​may transmit a request or assistance data related to sensing. Based on the request, the base station 10 may control at least one of reporting a result of the sensing, activating or deactivating transmission of a reference signal for the sensing, configuring or updating the reference signal, activating or deactivating measurements for the sensing, and updating the sensing method. Based on the request or assistance data, the user terminal 20 may transfer either the capability for the sensing or the result of the sensing.

[0413] (Base Station) Fig. 36 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0414] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0415] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0416] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0417] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0418] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0419] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0420] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0421] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0422] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0423] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0424] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

[0425] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.

[0426] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0427] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0428] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0429] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0430] The transceiver 120 may perform at least one of transmitting and receiving a signal for sensing (e.g., a sensing RS). The controller 110 may control at least one change (e.g., mobility procedure) between the base station for sensing, the terminal for sensing, and the sensing mode (e.g., sensing mode / method) when information based on measurement of the signal (e.g., measurement result, processing result) satisfies a condition (e.g., condition / event).

[0431] The transceiver 120 may transmit a signal for sensing (e.g., a sensing RS). The controller 110 may control reception of a report of a sensing failure when a measurement result (e.g., a measurement result, a processing result) of the signal satisfies a condition (e.g., a condition / event).

[0432] The transceiver 120 may transmit communication and sensing settings. The controller 110 may control reception of a first report of measurement for the communication and reception of a second report of measurement for the sensing.

[0433] (User terminal) Fig. 37 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0434] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0435] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

[0436] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transceiver unit 220.

[0437] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0438] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0439] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0440] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0441] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0442] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0443] The transmitter / receiver unit 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0444] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

[0445] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

[0446] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.

[0447] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0448] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0449] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0450] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0451] The transceiver 220 may receive a signal for sensing (e.g., a sensing RS). The controller 210 may control the transmission of a report of a sensing failure when information based on measurement of the signal (e.g., a measurement result, a processing result) satisfies a condition (e.g., a condition / event) (embodiment C3).

[0452] The condition may be a deterioration in performance of tracking an object in the sensing.

[0453] After the report, the controller 210 may change one or more base stations that transmit the signal for sensing.

[0454] The report may include at least one of the obstacle, the object, the sensing environment, the movement of the object, the sensing use case, the sensing category, the measurement results, the measurement results of the communication signal, the conditions, candidate base stations for transmitting signals for the sensing, and the sensing resolution.

[0455] The transceiver 220 may receive communication and sensing settings. The controller 210 may control the transmission of a first report of the measurement for the communication and the transmission of a second report of the measurement for the sensing (embodiment C5).

[0456] After at least one of the first report and the second report, the controller 210 may change one or more base stations associated with at least one of the communication and the sensing.

[0457] The control unit 210 may execute a procedure to change one or more base stations associated with the sensing, separately from the procedure to change one or more base stations associated with the communication.

[0458] The controller 210 may execute a procedure to change one or more base stations involved in the communication and the sensing.

[0459] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0460] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

[0461] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 38 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0462] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0463] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0464] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0465] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0466] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0467] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0468] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0469] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0470] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0471] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0472] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0473] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0474] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0475] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

[0476] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.

[0477] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0478] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0479] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0480] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0481] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0482] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0483] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0484] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0485] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0486] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0487] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0488] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0489] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0490] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0491] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0492] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0493] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0494] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0495] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0496] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0497] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0498] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0499] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0500] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0501] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0502] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0503] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0504] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0505] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0506] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0507] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0508] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0509] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0510] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0511] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0512] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0513] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0514] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0515] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

[0516] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0517] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0518] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0519] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0520] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0521] 39 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0522] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

[0523] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0524] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0525] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0526] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0527] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0528] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0529] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0530] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0531] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0532] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

[0533] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0534] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0535] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0536] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0537] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0538] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0539] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0540] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0541] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0542] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0543] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0544] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...." "does not expect ..." may be interchangeably read as "be not expected ...." Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (e.g., if apparatus A is a UE, apparatus B may be a base station).

[0545] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0546] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0547] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0548] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0549] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0550] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0551] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0552] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0553] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0554] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0555] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal comprising: a receiving unit that receives a signal for sensing; and a control unit that controls transmission of a report of a sensing failure when information based on measurement of the signal satisfies a condition.

2. The terminal according to claim 1, wherein the condition is deterioration of performance of object tracking in the sensing.

3. The terminal according to claim 1, wherein after the report, the control unit changes one or more base stations that transmit a signal for the sensing.

4. The report includes at least one of the failure, the object, the sensing environment, the movement of the object, the sensing use case, the sensing category, the measurement result, the measurement result of a communication signal, the condition, candidates for a base station that transmits a signal for the sensing, and the sensing resolution.

5. A wireless communication method for a terminal, comprising: receiving a signal for sensing; and controlling transmission of a report of a sensing failure when information based on measurement of the signal satisfies a condition.

6. A base station comprising: a transmitting unit that transmits a signal for sensing; and a control unit that controls reception of a report of a sensing failure when information based on measurement of the signal satisfies a condition.

Images